Static exports
Generate and consume static site exports.
Static exports produce a portable artifact for teams that need to host or archive a Mini Agency site outside the normal renderer.
What an export contains
An export should include rendered HTML routes, required assets, CSS, metadata, and enough path structure for the target host to serve the site. The exact artifact shape can evolve, so inspect the generated archive for each release before building automation around it.
What needs attention
Static hosting is not the same as the live Mini Agency renderer. Review these before relying on an export:
- Forms may need the embeddable forms script or a remote submission endpoint.
- CMS pages must be present for every exported item route.
- Images and generated assets must resolve from the exported path.
- Dynamic behavior that depends on server routes may need a replacement.
- Rewrites and redirects must be recreated in the target host.
Export workflow
- Publish or prepare the site state you want to export.
- Trigger export from the app.
- Download the artifact.
- Serve it locally or in a preview host.
- Click through key routes.
- Test forms and assets.
- Deploy to the target host.
Developer handoff
When handing an export to another team, include the original Mini Agency site name, export date, included routes, form behavior, known limitations, and any required environment URLs.