Blueprints on Liftoff

SaaS landing page

Mon, 01 Jan 0001 00:00:00 +0000

The most common product page: convince, prove, price, close. Copy the front matter and the body below into content/_index.md, then replace the copy with your own.

Front matter

The hero is configured, not written. Everything below it is markdown.

 yaml
 
 
---
title: "Acme"
description: "Ship your first workflow in five minutes."
hero:
 title: "Automate the boring half of"
 titleAccent: "your deployments."
 subtitle: "One config file. No agents to install."
 highlights:
 - icon: "mdi:lightning-bolt-outline"
 label: "Zero downtime"
 - icon: "mdi:lock-outline"
 label: "SOC 2"
 primary:
 label: "Start free"
 url: "/signup"
 secondary:
 label: "Read the docs"
 url: "/docs"
 code:
 language: yaml
 content: |
 deploy:
 target: production
 strategy: rolling
---

Body

 markdown
 
 
{{< section >}}
## Everything you need to ship

{{< feature-grid >}}
 {{< feature-card title="Rollbacks" icon="mdi:backup-restore" >}}
 One command back to the last known good release.
 {{< /feature-card >}}
 {{< feature-card title="Audit log" icon="mdi:history" >}}
 Every change attributed, exportable as JSON.
 {{< /feature-card >}}
 {{< feature-card title="Secrets" icon="mdi:key-outline" >}}
 Encrypted at rest, injected at runtime.
 {{< /feature-card >}}
{{< /feature-grid >}}
{{< /section >}}

{{< section width="narrow" >}}
## Works with your stack

{{< icon-grid data="integrations" >}}
{{< /section >}}

{{< section >}}
## Pricing

{{< pricing data="editions" >}}
{{< /section >}}

{{< section width="narrow" >}}
{{< testimonial author="Jane Doe" role="VP Engineering, Northwind" >}}
We replaced three internal tools with this and stopped thinking about
deploys entirely.

metrics:
- 80% less deploy time
- 40+ teams onboarded
{{< /testimonial >}}
{{< /section >}}

{{< cta title="Ready to ship faster?" primary="Start free|/signup" secondary="Talk to sales|/contact" >}}
No credit card. Cancel whenever.
{{< /cta >}}

What to change

Piece	Replace with
`hero.code.content`	Your actual config or CLI invocation
`feature-card`	Three to six cards, one benefit each
`data/integrations.yaml`	The tools your customers already run
`data/editions.yaml`	Two or three plans, one marked `featured`

Open source project page

Mon, 01 Jan 0001 00:00:00 +0000

An open source project page has one job: get someone from “what is this” to a working install before they lose interest. Cut everything that does not serve that.

Front matter

Put the install command in the hero. It is the single most-copied string on the page.

 yaml
 
 
---
title: "Widget"
description: "A single-binary task runner for small teams."
hero:
 title: "Task running without"
 titleAccent: "the YAML sprawl."
 subtitle: "One binary, no runtime, MIT licensed."
 highlights:
 - icon: "mdi:package-variant-closed"
 label: "Single binary"
 - icon: "mdi:scale-balance"
 label: "MIT"
 primary:
 label: "Get started"
 url: "/docs/installation"
 secondary:
 label: "Source"
 url: "https://codeberg.org/you/widget"
 code:
 tabs:
 - name: "macOS"
 icon: "simple-icons:apple"
 language: bash
 content: |
 brew install widget
 - name: "Linux"
 icon: "simple-icons:linux"
 language: bash
 content: |
 curl -sSf https://widget.dev/install.sh | sh
---

Body

 markdown
 
 
{{< section >}}
## What it does

{{< feature-grid >}}
 {{< feature-card title="No daemon" icon="mdi:power-plug-off-outline" >}}
 Runs and exits. Nothing left behind on your machine.
 {{< /feature-card >}}
 {{< feature-card title="Readable config" icon="mdi:file-document-outline" >}}
 Twenty lines of TOML, not two hundred of YAML.
 {{< /feature-card >}}
 {{< feature-card title="Docs" icon="mdi:book-open-page-variant" url="/docs" >}}
 Every flag documented, with examples.
 {{< /feature-card >}}
{{< /feature-grid >}}
{{< /section >}}

{{< section width="narrow" >}}
## Try it

{{< steps >}}
 {{< step number="1" title="Install" >}}
 Pick your platform above.
 {{< /step >}}
 {{< step number="2" title="Initialise" >}}
 Run `widget init` in your project root.
 {{< /step >}}
 {{< step number="3" title="Run" >}}
 Run `widget run build` and watch it exit cleanly.
 {{< /step >}}
{{< /steps >}}
{{< /section >}}

{{< cta title="Found a rough edge?" primary="Good first issues|https://codeberg.org/you/widget/issues" secondary="Contributing guide|/docs/contributing" >}}
Bug reports are contributions too.
{{< /cta >}}

Docs-only site

Mon, 01 Jan 0001 00:00:00 +0000

Some projects are the documentation. The home page exists only to get people into the docs, and everything else in the theme comes off.

Front matter

A short hero, no code block. The landing page is a signpost, not a pitch.

 yaml
 
 
---
title: "Widget Handbook"
description: "Everything Widget can do, in one place."
hero:
 title: "The complete"
 titleAccent: "Widget handbook."
 subtitle: "Install, configure, extend. Updated with every release."
 primary:
 label: "Start reading"
 url: "/docs/installation"
 secondary:
 label: "Source"
 url: "https://codeberg.org/you/widget"
---

Body

 markdown
 
 
{{< section width="narrow" >}}
{{< feature-grid >}}
 {{< feature-card title="Install" icon="mdi:download-outline" url="/docs/installation" >}}
 Package managers, binaries, and building from source.
 {{< /feature-card >}}
 {{< feature-card title="Configure" icon="mdi:cog-outline" url="/docs/configuration" >}}
 Every option, with defaults and examples.
 {{< /feature-card >}}
 {{< feature-card title="Extend" icon="mdi:puzzle-outline" url="/docs/plugins" >}}
 Write a plugin in about thirty lines.
 {{< /feature-card >}}
{{< /feature-grid >}}
{{< /section >}}

Removing the other sections

Deleting a content folder is only half the job. The menu entries survive and turn into dead links, so remove those too.

Public changelog

Mon, 01 Jan 0001 00:00:00 +0000

A changelog is the articles layout with different vocabulary: one page per release, newest first, tagged by change type. Point it at its own section so your actual writing stays separate.

Section front matter

Create content/releases/_index.md. The articles layout is reused by matching the section name in your own layouts/ folder, or by keeping the content under content/articles/ if you have no blog.

 yaml
 
 
---
title: "Releases"
description: "Every change to Widget, newest first."
hero:
 title: "What changed, and"
 titleAccent: "when it changed."
 subtitle: "Every release since 1.0, with upgrade notes."
 highlights:
 - icon: "mdi:tag-outline"
 label: "Semantic versioning"
 - icon: "mdi:rss"
 label: "RSS feed"
---

One page per release

Name the file after the version. The date drives the ordering, the tags drive the filtering.