Creating a New Site

To create a new site, follow these steps:

Client defines these:

• Site name
• Logo, favicon
• Theme primitives (base colors, typography choices, border radius)
• Content structure (which collections it has - events, catalog, programs, guides)
• domain name
• list of languages and the default language
• define which footer to use

Developer Setup Steps

1. Decap Turbo

1. Log in to Decap Turbo dashboard
2. Add new site with project name: cmt-{brand}
3. Get the Turbo Site ID from dashboard
4. Add the ID to config/{brand}/hugo.toml’s [params.cms] block, alongside the hide* feature flags for this brand (hideEcommerce/hideCatalog/hideEvents/hideGuides):

   [params.cms]
   turboSiteId = "your-turbo-site-id-here"
   hideEcommerce = false
   hideCatalog = false
   hideEvents = false
   hideGuides = false
   

   This is read directly by layouts/admin/list.cmsConfig.yml when it renders /admin/config.yml — there’s no separate CMS config file to create. The CMS’s locale list is derived automatically from this same hugo.toml’s [languages.*] block, so it doesn’t need to be set here too.

2. Configuration Files

Add brand to deployment:

• .github/workflows/deploy.yml - Add to BRANDS env var. Add new brands on the CMT Cloudflare account without cmt- prefix on the Pages project name (e.g. fit-retreat, gud-plesi) — add the brand to the case statements in the “Select Cloudflare account and project name” step, and to the matching case in bin/build.sh’s set_site_url(). Brands still named cmt-{brand} haven’t been migrated to the CMT account yet
• README.md - Add URLs and commands
• bin/site-config.mjs - Add the brand name to BRAND_NAMES (this is what validates SITE= for bin/dev.js/bin/build.sh and what bin/prompt-site.mjs’s menu lists)

Hugo config:

• config/{brand}/hugo.toml - Site config with params (including [params.cms], see above), a [languages.*] block, social links, module mounts
• config/{brand}/menus.json - Navigation structure (main, cta, relatedbrands)

Form submission recipients:

• Create functions/form-recipients/{brand}.json:

  {
    "default": ["recipient@example.com"],
    "forms": []
  }
  

• Register it in functions/form-recipients.js (import + add to FORM_RECIPIENTS_BY_BRAND). Form names on this brand must start with {brand}- so they’re matched correctly.

3. Brand Styling

File: assets/{brand}/styles/_brand-theme.scss

Define CSS variables for:

• Brand colors (primary, secondary with 100/120 variants)
• Accented colors (text, surfaces, borders)
• Font families (display, heading, title, body, label, supporting, button)
• Font weights for each family

4. Content & Data Files

Content:

• content/{brand}/_index.{lang}.md - Homepage for each language

Data files in data/{brand}/:

• footer.json - Footer links, social media, contact info
• faqTabs.json - Add a default tab entry (e.g. {"key": "default", "label": "Splošno"}) so the help center page has a tab for FAQ groups to fall back to — without it, groups/FAQs won’t render on the help center page

5. Static Assets

Directory: static/{brand}/

• favicon.png - Site favicon

6. Cloudflare Deployment

1. Create Pages project: {brand} (sites that are named cmt-{brand} haven’t been migrated to the CMT Cloudflare account yet — see step 2 above)
2. Connect to GitHub repository
3. Add required environment variables:
   • HUGO_VERSION (e.g., 0.154.5)
   • NODE_VERSION (e.g., 20)
   • BREVO_API_KEY and BREVO_SENDER_EMAIL - needed for forms to send email
   • …
4. Disable automatic deployments - we use GitHub Actions for builds instead

7. Booking API CORS

If the brand has ecommerce products, add its domain to the CORS allowlist on cmt-booking in Azure:

• Develop domain → cmt-booking-develop
• Stage and production domain → cmt-booking

Timeline

The deadline for creating a new site is 5 working days since the client provides all necessary inputs defined above. The client must inform the contractor 2 weeks in advance about the intention to create a new site.