Statify

Statify is an agent-friendly static-site generator for documentation, landing pages, product sites, catalogues, FAQs, and step-by-step guides. It is designed so a coding agent can turn a brief into a complete branded website, then build and verify the result without inventing a new frontend architecture for every project.

Instead of generating an opaque application, the agent or developer works with compact, documented contracts: readable Markdown, structured JSON, metadata, local styles, and ordinary assets. The resulting source remains easy for people to inspect, revise, enhance, change, diff, and keep in version control.

While Statify can directly be used by developers without any assitance, the included Codex website-authoring skill teaches Codex its page models and validation workflow, so it can create, style and maintain full websites from user prompts.

Sites generated by Statify are GDPR-compliant, compact and responsive. They work in desktop computers, tablets and mobile devices, are integrated with accounts in Google Analytics, include extensive SEO and structured metadata and have a very small footprint, without any external dependencies on third party libraries (other than Google Analytics if you choose to enable the functionality)

Statify turns hierarchical JSON and MD files into responsive, deployable websites with one command. The fully themable page models provide more focused functionality than a generic page builder:

  • Documentation supports nested sections, responsive navigation, breadcrumbs, media, and image carousels—ideal for product manuals, documentation centres, and legal documents.
  • Landing and product pages combine heroes, responsive sections, cards, calls to action, backgrounds, custom fonts, local video, and embedded YouTube™ videos.
  • FAQ and HowTo pages generate responsive interactive pages and structured data for search engines.
  • Catalogue pages load JSON collections dynamically and can publish an indexable static detail page for every item, including descriptions, features, media, and action links.
  • Download pages provide specific functionality for sites distriburing applications, like multi-platform versioned downloads and license distribution.
  • Site-wide foundations cover navigation, responsive layouts, light and dark presentation, SEO and structured metadata, and GDPR-compliant cookie consent dialogs.

The output is ordinary HTML, CSS, JavaScript, fonts, images, and media. It has no server-side runtime or client-side dependencies, and can be hosted by any web server, CDN, object-storage service, or static hosting provider.

Online Examples

Check out some examples created with Statify and Codex, All brands and products are fiction.

Why use Statify?

Many websites are publishing systems rather than applications: a product needs a distinctive landing page, a project needs durable documentation, or an organization needs a catalogue and permanent support information. They should be quick to create, pleasant to use, easy to update, and simple to deploy. Statify occupies that middle ground without introducing a CMS, database, or production application server, while allowing a very simple workflow to update the site content without the need of a HTML editor.

  • Start from a complete foundation. Templates provide the shared page shell, responsive navigation, presentation modes, metadata, and legal-page examples without dictating the finished site's identity.
  • Choose the right authoring model per page. Use Markdown for prose and documentation, structured JSON for visual or schema-driven pages, and mix both forms within one site.
  • Keep content portable and reviewable. Pages, metadata, and assets remain ordinary files that can be searched, diffed, backed up, generated by tools, reviewed in pull requests, and moved between hosting providers.
  • Turn dynamic data into discoverable pages. Browser-side catalogues can share their normalized items with the static publisher, producing stable detail URLs for visitors and search engines.
  • Automate repetitive publishing. The predictable source format and small command set work naturally in npm scripts, CI jobs, and agent-assisted workflows while preserving each site's branding and content.
  • Deploy almost anywhere. The finished directory contains only static web files and requires neither Statify nor Node.js in production.

Statify is particularly useful when the alternative is copying an old website yet again, rebuilding the same navigation and policy pages, or introducing a full application framework for content that ultimately needs to become a set of reliable static files.

Requirements

  • Node.js 18 or newer (NodeJS Download Site)
  • npm (included with Node JS) - or another package manager capable of installing npm packages!

Statify works in MacOS, Linux and Windows. On Windows, you must use powershell to interact with statify.

Installation

Install globally

A global installation makes statify available from any directory and is a convenient choice when creating and maintaining several sites:

npm install --global @nebularstreams/statify

Confirm the installation:

statify --help

Mind that installing globally may require administration privileges in some systems.

You can also install Statify as a development dependency in an existing project. This is interesting for advanced users and is out of the scope of this document.

npm install --save-dev @nebularstreams/statify

Quick start

Create a documentation website, build it, and open the result:

statify init my-documentation documentation
cd my-documentation
npm start

or create a full website with landing, documentation pages, faq, howto and product catalogues

statify init my-site site
cd my-site
npm start

or create a full website for an application with landing, download, license and documentation pages.

statify init my-application-site application
cd my-application-site
npm start

Every bundled template includes a package.json with these useful scripts:

{
  "scripts": {
    "start": "npm run build && npm run preview",
    "build": "statify folder .",
    "preview": "statify preview .build --open",
    "serve": "statify preview .build"
  }
}

Statify includes a lightweight local preview server, so a globally installed copy needs no additional project dependencies. The available scripts are:

Command Purpose
npm start Build the complete site and start its preview.
npm run build Build the complete site into .build/.
npm run preview Preview the most recent build.
npm run serve Start the preview server, but do not open a browser

Templates at a glance

  • documentation — a Markdown-first documentation tree with responsive navigation and legal-page examples;
  • landing — a concise JSON-authored landing page;
  • product — a product-focused landing site with its own visual treatment;
  • site — a complete site covering rich media, structured pages, and dynamic product lists.
  • game — a modern game promo template
  • application — a template for a website distributing downloadable applications

Template companies, people, URLs, policies, and media are examples. Replace them before publishing a real site.

Continue with the usage guide

The complete usage guide owns the authoring and command reference: source layout, metadata, every page model, media, catalogue publication, styling, npm workflows, lower-level CLI commands, deployment, and verification.

Codex website-authoring skill

The npm package includes an optional Codex skill that teaches Codex how to author and verify Statify websites.

Install it from a global or project-local Statify command:

statify skill install

Or install directly without keeping a global package:

npx @nebularstreams/statify@latest skill install

The skill is copied to $CODEX_HOME/skills/statify-site, falling back to ~/.codex/skills/statify-site. Existing installations are protected by default. Replace one deliberately with:

statify skill install --force

Restart or refresh Codex, then invoke the skill with $statify-site.

What the skill adds

The skill gives Codex Statify-specific authoring context: how the templates are structured; when to use documentation, FeatureList, list, FAQ, or HowTo pages; which fields belong at each level; how media, metadata, canonical URLs, consent, and local styling work; and how to build and verify the complete result. This lets you describe the site you want instead of first explaining Statify's file contracts.

It is equally useful for new sites and existing ones. When working on an existing site, the skill directs Codex to inspect the current metadata, pages, assets, styles, and custom widgets rather than reinitializing the project.

Example: create a documentation site

Use $statify-site to create a documentation website in ./product-manual. Start from the documentation template and add Getting Started, Configuration, and Troubleshooting sections. Use our existing logo from ./brand/logo.svg, apply a blue accent in both skins, then build and verify the complete site.

This gives Codex the destination, template, content hierarchy, existing asset, and visual direction while leaving the implementation details to the skill.

Example: create a richer landing page

Use $statify-site to build a landing page for Acme Relay in ./relay-site. Use the ordinary landing template, with a hero, three benefit cards, a product screenshot carousel, a YouTube demonstration, an FAQ page, and links to our documentation.

Mention real video IDs, destination URLs, company details, and supplied assets when they are available. Codex should leave unknown production details as clearly identified placeholders rather than inventing them.

Example: extend an existing site safely

Use $statify-site to update the Statify site in ./website. Preserve its current branding and custom widgets. Add a Migration Guide beneath pages/guides/, link it from the existing documentation index, and add a two-image carousel using the screenshots already in pages/res/. Build the full folder and check that the generated links and assets resolve.

The explicit preservation request is useful when the site already contains local conventions or custom presentation that should remain unchanged.

Example: review before changing anything

Use $statify-site to review ./website without editing it. Check metadata and canonical URLs, placeholder template content, page and asset references, heading structure, image attribution, and light/dark presentation. Report the problems you find and recommend the smallest useful corrections.

Codex can therefore be used as either an author or a reviewer. Ask explicitly for review-only work when you want findings before any files are modified.

For the strongest results, include the source directory, desired template or existing-site constraint, real content and links, available assets, branding preferences, and the intended build destination. The skill builds and checks the site locally; publishing remains a separate step unless you request it.

Content trust

Statify is an authoring and build tool. It treats Markdown, JSON, metadata, remote list feeds, templates, and embedded HTML as trusted project input. Do not build untrusted content without validating and sanitizing it first.

License

Statify is distributed under the MIT license