Open RTLS Website

First iteration Hugo one-pager for open-rtls.com.

Stack

• Hugo
• Tailwind CSS v4 (@tailwindcss/typography)
• Vite for frontend asset build
• Cloudflare Pages static hosting

Development

npm ci
npm run dev

Production build

npm ci
npm run build

Build output directory is public/.

Cloudflare Pages

Use these settings:

• Build command: npm ci && npm run build
• Build output directory: public

wrangler.toml is included as a Pages-ready scaffold for future iteration needs.

GitHub Publishing Flow

Publishing is handled by GitHub Actions:

• Pull requests to main run validation (.github/workflows/pr-validate.yml)
• Pushes/merges to main auto-deploy to Cloudflare Pages (.github/workflows/deploy-cloudflare.yml)

1. Create API token permissions in Cloudflare

• Account -> Cloudflare Pages -> Edit
• Zone -> DNS -> Edit
• Zone -> Zone -> Read
• Zone Resources: include open-rtls.com

2. Set GitHub Actions secrets

Create repository secrets in GitHub:

• CLOUDFLARE_API_TOKEN
• CLOUDFLARE_ACCOUNT_ID

You can load these from cloudflare.env using GitHub CLI:

while IFS='=' read -r key value; do
  [[ -z "$key" || "$key" =~ ^# ]] && continue
  gh secret set "$key" --body "$value"
done < cloudflare.env

3. One-time domain setup in Cloudflare Pages

• Add custom domains to the Pages project:
  • open-rtls.com
  • www.open-rtls.com
• In DNS, point both hostnames to open-rtls-website.pages.dev as CNAME records.
• Keep DNS records as DNS only until domain status is active.
• Add redirect rule:
  • Source: https://www.open-rtls.com/*
  • Target: https://open-rtls.com/$1
  • Status: 301

After that, merging to main publishes automatically.

Optional: direct local deploy

If you need to deploy from a local machine instead of GitHub Actions:

1. Create API token permissions in Cloudflare:

• Account -> Cloudflare Pages -> Edit
• Zone -> DNS -> Edit
• Zone -> Zone -> Read
• Zone Resources: include open-rtls.com

2. Create local credentials file:

cp cloudflare.env.example cloudflare.env

Fill in CLOUDFLARE_API_TOKEN in cloudflare.env.

3. One-time domain setup in Cloudflare Pages:

• Add custom domains to the Pages project:
  • open-rtls.com
  • www.open-rtls.com
• In DNS, point both hostnames to open-rtls-website.pages.dev as CNAME records.
• Keep DNS records as DNS only until domain status is active.
• Add redirect rule:
  • Source: https://www.open-rtls.com/*
  • Target: https://open-rtls.com/$1
  • Status: 301

4. Deploy (repeatable):

npm run deploy:cloudflare

This command builds the site, ensures the Pages project exists, and deploys to production.

Scope

This first iteration focuses on a usable initial website version. Deployment automation is configured through GitHub Actions.