Starter Templates
FrontAlign ships a set of free starter templates so you can go from nothing to a running project in a single command — no manual setup, no wiring the runtime by hand.
Every template is generated with a small scaffolding tool. It copies the template, injects your project name, and installs dependencies automatically.
For the full, up-to-date list of templates and previews, see the Templates page.
Quick Start
npx @frontalign/create-app@1.0.0 my-app --template agency
This creates a new folder named my-app in your current directory, scaffolded from the agency template.
Usage
npx @frontalign/create-app@1.0.0 <project-name> --template <template> [--framework <framework>]
The project name is the first argument. --template is required. --framework is optional — the default, and currently the only supported target, is nextjs.
| Flag | Required | Description |
|---|---|---|
project-name | Yes | Name of the folder to create. Letters, numbers, hyphens, and underscores only. |
--template | Yes | The starter template to scaffold from. See Available Templates or browse the full list on the Templates page. |
--framework | No | The framework target to generate. Defaults to |
| No | Prints usage instructions and exits. |
Available Templates
| Template | Best for |
|---|---|
agency | Marketing and portfolio sites — landing pages, service pages, and case studies. |
blog | Content-driven sites with post listings, article pages, and tags. |
More starter templates are added over time — check the Templates page for the current catalog.
Framework Support
| Framework | Status | Description |
|---|---|---|
nextjs | Default · Available | The only supported framework target today. Dependencies are installed automatically after scaffolding. |
Additional framework targets (including a plain HTML output) are planned. They aren't available yet — once released, they'll get their own setup notes here.
Examples
npx @frontalign/create-app@1.0.0 my-site --template agency
Since nextjs is the default, the --framework flag can be omitted in both examples above.
What Happens Behind the Scenes
Running the command triggers a fixed sequence of steps.
| Step | Description |
|---|---|
| 1. Validate | The project name, template, and framework are checked before anything is written to disk. |
| 2. Resolve template | The tool locates the matching
|
| 3. Copy files | The template is copied recursively into a new folder named after your project. |
| 4. Inject project name | Every |
| 5. Install dependencies |
|
If a folder with the requested project name already exists, the process stops and asks you to choose a different name rather than overwriting it.
Next Steps Output
Once scaffolding finishes, you'll see the commands needed to get running — using whichever package manager is detected on your system (pnpm, yarn, or npm, in that order).
cd my-site # only shown if dependencies were not installed automatically
npm run dev
Getting Help
npx @frontalign/create-app@1.0.0 --help
Prints the full list of flags, available templates, and available frameworks.