Skip to main content

​
Website Platform Overview

The Website platform in Scriptonia produces a blueprint for content-focused, static or SSG sites with no backend or user accounts. Outputs include PRD, PLAN, SEO strategy, frontend specs, LLM prompts to generate the actual site, and infra for Vercel or Netlify.
  • Agents: ProductManager, FrontendDev, ToolManager
  • Execution: ~45 s
  • Cost: Same as other platforms (unified $SCRIPT / USD)

​
Use Cases

Use caseFit
Landing pagesProduct, app, or waitlist; hero, features, CTA, footer
Marketing sitesMulti-page: About, Pricing, FAQ, Contact; SEO-oriented
PortfoliosProjects, case studies, CV; optional blog
BlogsMDX / Markdown posts, listing, tags; static generation
DocumentationDocs structure, navigation, code blocks; feeds into Docusaurus, Nextra, or plain Next.js
Event or campaign pagesOne-off or seasonal; fast to ship

​
Generated Structure

<ProjectName>/
├── README.md
├── docs/
│   ├── PRD.md
│   ├── PLAN.md
│   └── SEO_CONTENT.md____
├── frontend/
│   ├── nextjs.md
│   ├── pages.md
│   ├── components.md
│   └── prompts/
│       └── generate_static_site.txt
├── content/
│   ├── blog/
│   └── assets/
├── infra/
│   ├── hosting.md
│   └── cdn_caching.md
├── meta/
│   ├── github_push.yaml
│   └── export.zip
├── FOLDER_STRUCTURE.md
└── REVIEW_REPORT.md
  • docs/ — PRD, PLAN, SEO strategy and content plan
  • frontend/ — Next.js config, page structure, component specs; prompts/ holds the LLM prompt to generate the static site
  • content/ — Placeholders for blog and assets
  • infra/ — Hosting (Vercel) and CDN / caching
  • meta/ — github_push.yaml for repo / CI; export reference

​
Tech Stack

LayerStack
FrontendNext.js (Static / SSG), Markdown / MDX, TailwindCSS
HostingVercel (primary), Netlify (optional)
ExtrasSEO layer, meta tags, sitemap
  • Next.js SSG — getStaticProps / getStaticPaths or App Router static export for fast, CDN-friendly HTML
  • MDX — Markdown + JSX for blog and docs
  • TailwindCSS — Utility-first styling in specs and prompts
  • SEO — SEO_CONTENT.md and meta / sitemap guidance

​
Deployment Guide

​
1. Generate runnable code

  • Use frontend/prompts/generate_static_site.txt with your LLM and the frontend specs (nextjs, pages, components)
  • Add content under content/ (blog, assets) and wire it to the generated pages
  • infra/hosting.md describes setup
  • Connect GitHub repo (or upload project) and import as Next.js
  • Vercel runs next build; for static export, set output: 'export' in next.config.js
  • Set env vars if needed (NEXT_PUBLIC_*)
  • Custom domain via Vercel Dashboard → Settings → Domains

​
3. Netlify

  • infra/hosting.md may outline Netlify
  • Build: next build
  • Publish: .next (server) or out (static export)
  • For static export, set publish directory to out
  • Add redirects / headers in netlify.toml if needed

​
4. CDN and caching

  • infra/cdn_caching.md covers CDN and caching
  • Vercel / Netlify include CDN by default
  • Optional extra CDN (e.g. Cloudflare) in front of hosting origin

​
5. SEO

  • Use docs/SEO_CONTENT.md for titles, descriptions, structure
  • In app: meta tags, Open Graph, Twitter cards, sitemap.xml
  • Submit sitemap to Search Console