Start from a template

Quant provides ready-to-deploy templates for popular frameworks. The template wizard creates a GitHub repository, configures your Quant project, sets up secrets, generates a deployment workflow, and triggers the first build — all in one step.

Available templates

Templates are public repositories in the quantcdn-templates GitHub organisation. The dashboard lists only templates from that organisation. There are three kinds:

Kind	What runs	How it deploys
App (app-*)	Your container on Quant Cloud	GitHub Actions builds the image and deploys it with the Quant Cloud actions
Static (ssg-*)	Nothing: Quant serves the built files	GitHub Actions builds the site and uploads it with quantcdn/deploy-action
Static + edge (ssg-astro-edge-saas)	Edge functions and KV stores; no server or database	deploy-action uploads the site, the functions and the rules

Static site templates

Template	Framework	Output directory
ssg-astro	Astro	dist
ssg-astro-studio	Astro with Studio visual editing	dist
ssg-astro-studio-civictheme	CivicTheme design system on Astro, with Studio editing	dist
ssg-astro-edge-saas	Orbit: a workspace dashboard with login and saved data, built on edge functions and KV	dist
ssg-docusaurus	Docusaurus	build
ssg-eleventy	Eleventy	_site
ssg-gatsby	Gatsby	public
ssg-hugo	Hugo	public
ssg-jekyll	Jekyll	_site
ssg-nextjs	Next.js static export	out
ssg-nuxt	Nuxt static generation	.output/public
ssg-sveltekit	SvelteKit static adapter	build

Cloud application templates

Template	Stack	Database
app-nextjs	Next.js with server rendering	-
app-nuxt	Nuxt 3 with server rendering	-
app-sveltekit	SvelteKit with adapter-node	-
app-remix	Remix	-
app-astro	Astro with server rendering	-
app-ai-chat	Streaming AI chat interface (Hono + Preact)	-
app-payloadcms	Payload CMS 3 on Next.js	Postgres
app-emdash	EmDash CMS on Astro	SQLite (Postgres optional)
app-drupal	Drupal 10	MySQL
app-drupal-cms	Drupal CMS	MySQL
app-wordpress	WordPress	MySQL
app-craft-cms	Craft CMS	MySQL
app-laravel	Laravel	MySQL
app-symfony	Symfony	Optional
app-statamic	Statamic (flat-file)	Not needed

app-node and app-apache-php are the base images the other app templates build on. If your framework is not listed, start from the closest template or import your repository.

Note

Each template includes a working docker-compose.yml and Dockerfile (cloud apps) or build configuration (static sites) plus a GitHub Actions workflow. To copy a template by hand or write your own, see Template files and your own templates.

Create a static site from a template

1. In the Quant dashboard, go to Projects → New Project
2. Select Start from a template
3. Choose a template — browse the available static site templates and select one
4. Connect GitHub — if you haven’t connected yet, you’ll be prompted to install the GitHub App. If you have multiple installations, select the one to use.
5. Configure your project:
   • Repository name — name for the new GitHub repository (auto-generated from template name, e.g., my-astro-site)
   • Project name — name for your Quant project
   • Visibility — public or private repository
6. Click Create and watch the progress

The wizard shows real-time status as it works through each step. When complete, you’ll see links to your new GitHub repository, the Quant project, and your live site URL.

Create a cloud application from a template

1. In the Quant dashboard, go to Cloud Apps → New → Starter Kit
2. Choose a template — select from the available cloud application templates
3. Connect GitHub — connect or select a GitHub installation
4. Configure your application:
   • Repository name — name for the new GitHub repository
   • Application name — name for your Quant Cloud application
   • Visibility — public or private repository
5. Click Create and monitor the progress

Note

If the template includes a database (e.g., WordPress, Laravel), Quant automatically provisions a managed database instance. This may add a few minutes to the setup time while the database becomes available.

What happens behind the scenes

When you create a project from a template, the wizard performs these steps automatically:

Step	What happens
1. Create repository	A new GitHub repository is created in your account from the selected template
2. Create project/app	A Quant project (static) or Cloud application is created in your organisation
3. Generate token	A deployment token is created with the necessary permissions
4. Set secrets	Deployment credentials are encrypted and stored as GitHub repository secrets
5. Add workflow	A GitHub Actions workflow is committed to .github/workflows/deploy.yml
6. Trigger deployment	The first deployment is triggered automatically

The wizard also applies the template’s quant/meta.json: it provisions a managed database when the template needs one, generates the secrets the template declares, and for static templates creates the declared KV stores. It removes the template’s own maintenance workflow (ci.yml) from your copy.

For static sites, the secrets and variables stored are:

Secret/Variable	Purpose
QUANT_TOKEN	Deployment token (secret)
QUANT_CUSTOMER	Organisation ID (variable)
QUANT_PROJECT	Project name (variable)
QUANT_API_TOKEN	Project-scoped token for edge rules (secret; templates with quant/edge-rules.json only)
QUANT_BASE_URL	Platform API for edge rules, {dashboard}/api/v2 (variable; with QUANT_API_TOKEN)

For cloud applications, the secrets and variables stored are:

Secret/Variable	Purpose
QUANT_API_KEY	API deployment token (secret)
QUANT_ORGANIZATION	Organisation name (secret)
QUANT_APPLICATION	Application name (variable)
QUANT_BASE_URL	API endpoint, {dashboard}/api/v3 (variable)

QuantGov

On QuantGov, the deploy and purge steps of a static site must send uploads to https://api.quantgov.cloud/v1. Check that both steps have endpoint: https://api.quantgov.cloud/v1, and add it if they do not. The deploy buttons in the template READMEs open the public dashboard; on QuantGov, start from the template wizard in https://dash.quantgov.cloud.

Customising after creation

Once the wizard completes, the new repository is a standard GitHub repo that you own. To make changes:

1. Clone the repository:

   git clone https://github.com/your-username/your-repo-name.git
   cd your-repo-name

2. Make your changes — edit content, add pages, update styles

3. Push to redeploy:

   git add .
   git commit -m "Update site content"
   git push

Every push to the default branch triggers a new deployment automatically via the GitHub Actions workflow.

Next steps

• Add a custom domain — Point your own domain to your new site
• Import a repository — Already have a repo? Import it instead
• Framework guides — Framework-specific configuration tips