Getting started on Liftoff

Site settings

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

Everything here is in hugo.toml.

Name and address

baseURL = "https://yourdomain.com/"
title = "Your product"

baseURL must be your real address. Search engines and share previews use it.

Description and tagline

[params]
  description = "One sentence about your product, shown in Google."
  tagline = "A short line for the footer."
  email = "hello@yourdomain.com"

Accent colour

One colour restyles the whole theme, including the rocket:

accent = "#3f5bf0"

White text sits on this colour, so pick a fairly dark shade to keep buttons readable.

Home page

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

The whole home page comes from data/home.yaml, so you can change the words without touching any code.

A note on YAML

Keep the indentation as it is. It uses spaces, not tabs.
If text contains a comma inside { curly brackets }, wrap it in “double quotes”, or it will be cut off.

- { title: "Fewer, better alerts", text: "A daily digest." }

Hero

hero:
  eyebrow: New in Liftoff 2.0
  title: Get your next launch *off the ground*
  text: One or two sentences about what you do.
  primary: { label: Start free, url: /pricing/ }
  secondary: { label: See how it works, url: /features/ }
  note: Free for up to 5 people. No card needed.

Wrap words in *asterisks* to show them in your accent colour. This works in every section title.

Features page

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

The page text is in data/features.yaml. The heading and description are at the top of content/features.md.

Feature rows

Each row has a title, some text, an icon and a list of points. Rows alternate from side to side automatically.

sections:
  - eyebrow: Plan
    title: Roadmaps that *keep themselves current*
    text: A sentence or two about this feature.
    icon: map
    points: ["Timeline, board and list views", Shareable links]

Extra cards

more holds the three smaller cards beneath the rows.

Pricing

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

Plans are in data/pricing.yaml. They appear on both the Pricing page and the home page.

Plans

currency: "$"
plans:
  - name: Team
    monthly: 12
    yearly: 10
    text: For teams shipping every week.
    popular: true
    features: [Unlimited people, Unlimited projects]
    cta: { label: Start 14-day trial, url: /contact/ }

monthly and yearly are the prices per month shown by the Monthly/Yearly switch.
popular: true adds the badge and highlight.
cta.url is where the button goes, such as your sign-up page or a Stripe or Lemon Squeezy checkout.

To change the switch’s label, such as “Yearly, 2 months free”, edit layouts/_partials/plans.html. The same file holds “per person / month”.

Blog

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

Each post is a Markdown file in content/blog/. To add one, create a file such as my-first-post.md:

---
title: My first post
description: One sentence shown on the blog page and in Google.
date: 2026-11-01
category: Launches
author: Your Name
---

Your post starts here.

## A heading

Some text and a [link](https://example.com).

The file name becomes the address: /blog/my-first-post/.

Newest posts appear first.
A post with a future date stays hidden until then, and draft: true keeps it out of the finished site.
Code blocks are highlighted automatically.
The RSS feed and sitemap update by themselves.

Delete the three sample posts when you’re ready. The heading of the blog page is in content/blog/_index.md.

Contact form

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

Your site has no server, so a free form service delivers messages to your inbox. Vega works with Web3Forms out of the box.

Connect Web3Forms

Enter your email address at web3forms.com to get an access key.
Paste it into formKey in hugo.toml.
Publish your site, send yourself a test message and check your inbox.

formKey = "your-access-key"

The sample key won’t send anything, so remember this step before you go live.

Using another service

To use Formspree or similar, change formAction in hugo.toml to its address. Then adjust the hidden access_key field in layouts/contact.html to match its instructions.

Going live

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

First, set baseURL in hugo.toml to your real address. Then put your project in a GitHub repository, so your host can rebuild the site whenever you make a change.

Cloudflare Pages

In the Cloudflare dashboard, create a Pages project and connect your repository.
Use the build settings below.
Deploy, then add your domain under Custom domains.

Setting	Value
Build command	`npm run build`
Output directory	`public`

Netlify

Add a new site from your repository with the same two settings.

FAQ and support

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

Common questions

Can I use Vega for a client?

Yes. One license covers one website, either your own or one you build for a client. Buy one license per site.

Can I remove the “Vega by Tortoiz Themes” credit?

Yes. It’s in layouts/_partials/footer.html. We appreciate it if you keep it, but you don’t have to.

Do I need to know how to code?

No. Everyday changes are made in plain text files. Changing the design needs basic HTML and CSS.