Skip to main content

General settings

The General settings tab (under Settings in the sidebar) holds the site-wide configuration that affects every published page: title, description, language, base URL, home mode, performance mode.

These are all stored in settings/site in Firestore as a single document. The admin's useCmsData() hook subscribes to it and exposes the live values everywhere.

Site identity​

Site title​

The display name of your site. Used by:

  • The default theme's text wordmark in the header (when no logo)
  • The OG title fallback for posts that don't have a per-post SEO title set
  • The RSS feed title (flexweg-rss plugin)
  • The menu branding (sent to themes via menu.json.branding.siteTitle)
  • The admin's browser tab title when viewing the site

Free text — Unicode allowed, no length limit (themes truncate if needed).

Site description​

A short tagline / description of your site. Used by:

  • The OG description fallback for posts that don't have a per-post SEO description
  • The RSS feed description (flexweg-rss)
  • Some theme templates (e.g. corporate's hero block) that surface a tagline

Recommended length: 100-200 characters. Themes truncate longer text.

Site language​

A BCP-47 language tag (e.g. en, fr, fr-CA, pt-BR, de-AT). Injected as <html lang="…"> on every published page.

This is separate from the admin UI language — that's per-user, in the topbar locale switcher. The site language is one per site.

Pick the language your content is in. Visitors' browsers + screen readers + translation tools use this attribute to interpret your pages correctly. SEO crawlers also respect it.

If you're unsure, the prefix-match conventions are:

  • en — generic English
  • en-US — American English
  • en-GB — British English
  • fr — generic French
  • fr-CA — Canadian French (different vocabulary, accents)
  • de — German
  • de-AT — Austrian German

For monolingual sites, just en, fr, de, etc. is fine — no need to be region-specific.

Effects of changing the site language​

Most themes don't visually change based on the site language — they just emit <html lang> correctly. But:

  • The flexweg-sitemaps plugin's XSL stylesheets render labels in the matching language (English / French baked in for now; full localisation requires re-uploading the XSL via the plugin's settings page).
  • Some themes have language-specific date / number formatting (via Intl.DateTimeFormat(siteLanguage)).
  • Plugins that emit text (e.g. RSS feed item titles) honour the site language.

After changing the site language, click Save at the bottom. To propagate:

  • Sitemap XSL stylesheets: Settings → Sitemaps → Upload stylesheets
  • Theme date formatting: Themes → Regenerate site → All HTML pages (re-renders posts with the new locale's date format)

Public site URL​

The base URL of your public site, e.g. https://mysite.flexweg.com or https://www.example.com. No trailing slash.

Used by:

  • Sitemaps — every URL in the sitemap is <baseUrl>/<path> (sitemaps need absolute URLs)
  • RSS feeds — same
  • Open Graph tags — og:url is built from baseUrl + post.path
  • OG images — converted to absolute URLs
  • robots.txt — Sitemap: lines are absolute

If you change your domain (e.g. moving from mysite.flexweg.com to www.mysite.com):

  1. Update the Public site URL here
  2. Run Themes → Regenerate site → Everything to re-render every page with the new absolute URLs in OG tags
  3. Re-emit sitemaps + RSS via the plugin's regen targets

Home mode​

Two options:

Latest posts (default)​

The home page (/index.html) shows a paginated grid of recent posts. The publisher renders the active theme's HomeTemplate with the latest posts list (count configurable in Settings → Performance → Posts per page).

Best for blogs and content-heavy sites.

Static page​

The home page renders a specific Page's content (chosen via the Home page dropdown that appears when this mode is selected).

Use this for vitrine / landing-page sites where the home is a custom layout (hero + services + testimonials + CTA), built with theme blocks.

The selected Page must exist in your Pages list. If you delete it after setting home mode, the home falls back to a "404 — page not found" notice — pick a different page or revert to Latest posts.

The corporate theme is typically configured for static-page mode with a Page composed of corporate blocks. The default and magazine themes default to latest-posts.

After changing the home mode, run Themes → Regenerate site → Home page only to re-render /index.html.

Performance mode​

Two options:

Standard (default)​

The admin opens a single live subscription on the entire posts collection when you sign in. List pages, search, dashboard counts and pickers all run from the in-memory snapshot. No Firestore composite indexes needed — the query has no where and no orderBy so Firestore's automatic single-field index covers it.

Recommended ceiling: ~5,000 posts. The initial fetch starts to feel slow above that.

Server-side paginated (opt-in)​

The admin fetches one page at a time via cursor-paginated Firestore queries. Faster for very large sites — only the current page's documents are loaded, regardless of total post count.

But: requires two composite indexes to be created in your Firebase project. The admin's FirestoreSetupGate detects missing indexes the moment you flip the toggle and walks you through creating them with one-click links to the Firebase Console.

Use this only if you have >5,000 posts and the Standard mode is noticeably slow.

→ See [Firebase indexes] for the setup details.

Posts per page​

Controls how many posts appear on:

  • The Home page (Latest posts mode)
  • Each Category archive
  • Each Author archive

Range: 1–50. Default 10.

Note that this is the list-display count, not the storage. All posts are stored in Firestore regardless. Listings use this count for pagination.

Saving​

Click Save at the bottom of the form. The settings document in Firestore updates immediately. Every page in the admin re-reads via the live subscription.

Some changes propagate to the public site only after a regen:

  • Site title / description → re-render any page that surfaces them
  • Site language → re-render every page (<html lang> changes)
  • Public site URL → re-render every page (OG tags, canonical URLs change)
  • Home mode → re-render the home page
  • Posts per page → re-render the home + category archives

The admin doesn't auto-regenerate on settings changes — you decide when to regenerate. Use Themes → Regenerate site with the appropriate scope.

Continue​