In the right side bar, under the page data tab, you can set the path of the page there. If you want something to appear right at the domain instead of at the domain.com/home, then set its path to be / instead of /home.
This is documented here https://docs.plasmic.app/learn/pages/#paths
If you are new to plasmic then you can also check out the Plasmic Levels tutorial
Thank you so much
Hi, I couldn’t find the “A Record” instructions like the screenshot above. I want no-www to work for my website. Is there any instruction to this? Thank you
@moses_febrian @yang Any solution on how to find the A Record?
Did you find a solution? I tried several ways without success.
Seems like we can’t have both vercel domains and plasmic domains this way? Not sure what am I missing, but seems the only way of achieving this is if we go through the code route. Is not that bad, but seems like unecessary overhead that should be avoidable, retaining both the flexibility of managing from both places: vercel, and “overwriting” some places with plasmic.
My own context:
I had vercel dns enabled which allows me to create and to point to apps with subdomains easy, I just wanted to publish a static page, which seems it shouldn’t need to pass through vercel, but that I would still benefit in the future if I’d wanted to move it into code. Plasmic subdomain works fine, but then if I try to add CNAME that points to plasmic, It would error as an invalid config If I added such CNAME in vercel dns; since my domain came from another provider (that is, I did not transfer it to vercel (just pointed to their IP address when I setup vercel DNS) I tried adding the CNAME there, then it kind of worked, but it complained about certificates, and then if you skip that, it goes to a non existing deployment (message from vercel). Then tried aliasing to the plasmic.run subdomain, and finally fully removed my domain from vercel. Nothing changed the 404 with the non existing deployment message.