Two creation paths. One publishing system.
Build the page here. Publish the static HTML anywhere.
Build by hand with proven components or use AI with Liquid templates. Both paths create the same editable page and portable output.
StaticPagesApi connects your creation workflow to WordPress, Shopify, S3, Lambda, Rails, or any URL that can receive an authenticated request.
Manual, AI, or both
Choose the building path that fits the job
Use either workflow on its own or combine them on the same page.
Manual + built-in components
Choose heroes, cards, pricing, images, sliders, FAQs, navigation, and CTAs in the visual editor. Add content, reorder blocks, preview, and publish without prompts or code.
AI + Liquid templates
Give AI a detailed brief for custom layouts. Liquid, scoped CSS, editable fields, sections, and rows keep the result reusable and human-editable.
A practical hybrid
Build the reliable skeleton manually and use AI for distinctive sections—or generate a draft and finish every detail by hand.
Edit, render, publish, and receive
StaticPagesApi renders approved content into static HTML and pipes it into the system you already own.
Edit: people or AI update structured content.
Render: components and Liquid templates produce HTML, CSS, and approved behavior.
Publish: export a complete document or body-only markup.
Receive: your signed endpoint stores, deploys, or transforms the payload.
Publish into what you already own
Your system decides what happens after publish
StaticPagesApi does not replace your CMS or infrastructure. It supplies clean static HTML to the destination you configure.
WordPress or Shopify
A receiver plugin accepts the payload and writes the rendered page into the destination while StaticPagesApi remains the editable source of truth.
S3, Lambda, or a CDN
A function or worker can store the HTML, publish assets, invalidate caches, and make the page available globally without application rendering on every request.
Rails or any URL
The Rails engine can store and serve imports, or any authenticated endpoint can route the payload through your own publishing pipeline.
Why this architecture is useful
Move faster without surrendering control of the content, destination, application code, or final output.
Faster production
Start with reliable components or let AI accelerate custom layout work, then refine everything in one editor.
Portable HTML
The final page can live outside this application and move when your CMS, host, or publishing stack changes.
Clear ownership
Marketing owns content, AI and designers shape templates, and engineers own integrations and live fragments.
Less runtime load
Static marketing traffic can hit files and caches instead of your production database on every request.
Technical FAQ
Overlays and fragments keep static pages interactive
Keep the page fast and editable while engineers deploy only the application code that needs to be live.
An overlay presents a form, calculator, configurator, signup flow, or app-like experience above the static page while the surrounding content stays editable.
Matching sections or rows share a stable organization-scoped key. CI can ship identical React, Vue, Svelte, or plain JavaScript HTML to every match across pages—or more than once on one page—in one atomic deployment.
WordPress, Shopify, S3, Lambda, Rails, a CDN worker, a private CMS, or any URL that can authenticate and process the payload.