Prompt for a content site
An example prompt for a content site
A good prompt for a content site names who uses it, the main things they create or manage, the rule that must never break, and what to leave out for now. Here is one you can paste and edit: "Build a magazine-style site for a local food writer. It needs: posts, pages and collections, editor and revisions, publish, schedule and revalidate, slugs and redirects, seo and structured data and image pipeline. Rule that must always hold: generate public pages statically, cache them at the edge with stale-while-revalidate, and revalidate by tag and path (and purge the edge) at publish, edit, unpublish and slug change. Leave out for now: no raw-HTML or arbitrary script/iframe embeds in post content and no per-reader server rendering of anonymous pages."
Last checked
Starter prompt
Build a magazine-style site for a local food writer. It needs: posts, pages and collections, editor and revisions, publish, schedule and revalidate, slugs and redirects, seo and structured data and image pipeline. Rule that must always hold: generate public pages statically, cache them at the edge with stale-while-revalidate, and revalidate by tag and path (and purge the edge) at publish, edit, unpublish and slug change. Leave out for now: no raw-HTML or arbitrary script/iframe embeds in post content and no per-reader server rendering of anonymous pages.
Replace the first sentence with your own idea. The list of needs stays useful whatever the niche, because it comes from what a content site has to do.
Two variations
- Build a podcast and show-notes site with episode pages. Start with posts, pages and collections and editor and revisions, and add publish, schedule and revalidate once those work.
- Build a newsletter archive with premium articles. People should be able to stable URLs: no 404s after renames, no duplicate content.
Words that help Forge AI recognise the category
Forge AI picks a reference architecture from how you describe the app. These phrases point to a content site: blog, blogging platform, ghost, substack, medium clone, wordpress, newsletter and newsletter platform.
What the plan decides for you
- Static/ISR rendering with on-demand revalidation behind the edge cache.
- Teaser in cached HTML, gated body from an authed no-store endpoint.
- Pre-generate image variants at upload; no per-request transforms.
- Slugs are stable identifiers with automatic 301 redirects on change.
What to ask for in a later prompt
This is a reference design for the category, not a promise that every item is generated today. Built-ins such as email, background jobs, file uploads and search are coming soon, so anything here that needs them is something you add yourself for now.
- Dedicated search engine (OpenSearch/Typesense): Postgres FTS plus trigram is sufficient for most sites.
- Read replicas for studio, search and analytics: the edge cache keeps primary load low.
- Translations (hreflang) and versioned docs: single language and version ship first.
- Collaborative real-time editing: needs a websocket tier and CRDT or OT layer.
FAQ
- How detailed should a prompt for a content site be?
- Name the users, the main objects, one rule that must always hold and one thing to leave out. The plan fills in the rest, and you can change it before generation.
- Which words tell Forge64 this is a content site?
- Phrases such as blog, blogging platform, ghost and substack point to this category.
- Can I change the app after the first build?
- Yes. Describe the change in plain English and Forge AI edits the app; the quality gate checks the code again.
Build your app with Forge64
One prompt to a running app with auth, database, hosting and payments. Start free, no credit card required.
Start building for free