AI Studio - CMS website builder

🔍 Problem Statement

As a Pelcro news client, I experience an AI Studio that only builds paywalls, which forces me to build and host my website elsewhere.

💡 User Story

• As a Pelcro news client, I want to build and host my website in the AI Studio by prompting, so that my site and paywall run on one platform.

• As Pelcro, I want get.pelcro.com built in the Studio, so that we validate the builder as its first client.

🎯 Definition of Done (DoD)

✔ Given the AI Studio, when a user starts a project, then “Website” is selectable alongside the paywall template.

✔ Given a website project, when a user selects or uploads a design template, then generated pages use its styles.

✔ Given a website project, when a user adds an API key in environment settings, then it is stored encrypted and available to the site.

✔ Given any prompt, when the Studio builds, then Pelcro’s built-in standards (content structure, PageSpeed, SEO) apply automatically.

✔ Given a website project, when a user imports from a public URL or a connected GitHub repo (supported stacks only), then the Studio rebuilds/loads the site and the normal prompt → preview → publish flow applies. get.pelcro.com is imported this way and published to Cloudflare as the first client.

✔ Given a published website (live on its Pelcro hostname), when a user connects their own domain, then the Studio:

• (1) verifies ownership with a non-disruptive TXT record and prepares TLS in advance, then

• (2) presents the single CNAME change as an explicit final “switch” step with a warning that it replaces whatever currently answers on that hostname, and

• (3) detects the switch and reports the site live. Nothing changes on the client’s domain until they consciously perform step 2. We never take over the client’s DNS.

✔ Given a website project, when a user creates, prompts, previews, or publishes, then each action runs through a documented, tested Pelcro API endpoint.

Open Questions