Settings

The Settings page is at Admin → Settings. It covers site-wide configuration that applies to every page.

General settings

Site name

The name of your website. Used in:

The admin panel header
Outgoing emails (forgot password, 2FA codes)
The <title> tag if your template uses it

Site URL

The canonical URL of your site, e.g. https://example.com. No trailing slash. Used in sitemap.xml and outgoing emails.

robots.txt

RuntCMS serves a dynamic robots.txt. Edit it via Pages & Assets → robots.txt → Edit.

The default content allows all crawlers:

User-agent: *
Allow: /

Sitemap: https://yourdomain.com/sitemap.xml

To block all crawlers (useful on staging sites):

User-agent: *
Disallow: /

sitemap.xml

RuntCMS generates a sitemap.xml automatically from all published pages. It's available at /sitemap.xml and updates whenever you add or change pages.

To include additional URLs — such as marketing pages or docs that aren't managed by the CMS — go to Pages & Assets → sitemap.xml → Edit and add one URL path per line.

Email configuration

RuntCMS sends emails for:

Password reset requests
Two-factor authentication codes (email OTP fallback)

Configure SMTP in the Settings page:

Field	Description
SMTP host	Your email provider's SMTP server address
SMTP port	Usually 587 (STARTTLS) or 465 (SSL)
SMTP username	Usually your email address
SMTP password	Your email account or app password
From name	The sender name shown in emails, e.g. "My Website"
From email	The sender address
Encryption	STARTTLS or SSL/TLS

Recommended: Use Brevo (formerly Sendinblue) — free tier includes 300 emails/day, which is plenty for a small site. It gives you reliable delivery and is easy to set up with RuntCMS.

After saving your SMTP settings, use the Send test email button to verify everything is working. The test email goes to your admin account email address.

No SMTP configured? Password reset and email OTP will not work. Configure SMTP before sharing editor credentials if those features are needed.

Development mode

Development Mode controls whether RuntCMS records revision history for files edited in the admin panel (CSS assets, JS assets, HTML pages, and Global Partials).

Mode	Behaviour
Local (default)	No file revisions are recorded. The History button in the editor opens an info modal explaining that you should use Git or a version control tool for local development.
Server	Every admin save records a revision. Up to 10 revisions per file are kept. Use this when you (or a developer) will be editing files directly on a live server without a separate version control workflow.

When to use Server mode: If you deploy via FTP and make CSS/JS tweaks directly in the admin panel, Server mode gives you a safety net. If you deploy via Git and always edit files locally, leave it on Local.