EvoHub Docs Sign in
EnglishEN

Changelog

Changelog settings

Use with AI
View as MarkdownThis page as plain text, for pasting into an AI tool Open in ClaudeAsk Claude questions about this page Open in ChatGPTAsk ChatGPT questions about this page
Connect to Cursor / VS Code / ClaudeSearch and read these docs from your AI tool (MCP server)

MCP server URL

https://docs-dev.evohub.io/mcp

Claude Code

claude mcp add --transport http evohub-docs-docs https://docs-dev.evohub.io/mcp

Claude (claude.ai and Claude Desktop): Settings → Connectors → Add custom connector, and paste the URL above.

Claude Desktop — claude_desktop_config.json

{
  "mcpServers": {
    "evohub-docs-docs": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://docs-dev.evohub.io/mcp"
      ]
    }
  }
}

Cursor — ~/.cursor/mcp.json

{
  "mcpServers": {
    "evohub-docs-docs": {
      "url": "https://docs-dev.evohub.io/mcp"
    }
  }
}

VS Code — .vscode/mcp.json

{
  "servers": {
    "evohub-docs-docs": {
      "type": "http",
      "url": "https://docs-dev.evohub.io/mcp"
    }
  }
}

This page covers the changelog settings that decide where and how it is read: its custom domain, password access, language, and analytics. Settings are under Settings in an open changelog. Anyone who can read the changelog can look at them; changing them needs permission to manage changelogs (changelog:site:write).

Custom domain

A changelog has exactly one public address: a subdomain you own, such as changelog.example.com. EvoHub does not give changelogs an address of its own, so until a domain is active, the changelog is visible only in the console. The subscribe form, email links, the widget and webhook links all use this domain.

Enter the hostname

Open Settings, Domain. Under Your domain, type the hostname and choose Connect domain. Use a subdomain with at least three labels; apex domains (example.com) are not supported.

Add the DNS records

The console shows two CNAME records to add at your DNS provider:

Type Name Value
CNAME _acme-challenge.changelog.example.com The value shown in the console
CNAME changelog.example.com cname.evohub-dns.com

Add the _acme-challenge record first and wait for it to validate, then add the routing CNAME, so the domain never goes live without a certificate. If your DNS is proxied through Cloudflare, set SSL to Full (not Flexible).

Wait for validation

Choose Re-check to refresh. When the status shows Verified · SSL active, the changelog is live at https://changelog.example.com.

The statuses are Not connected, Pending DNS, Validating, Verified · SSL active and Action needed. For Action needed, check that both records are still in your DNS exactly as shown and Re-check; if it stays red, remove the domain and connect it again. Keep both records for as long as you use the domain.

A hostname can serve only one changelog, docs site or status page. Remove domain disconnects it; the changelog keeps its entries.

Password access

A changelog is public by default. To share it with a limited group — partners, an early-access group — make it private:

  1. Open Settings, Access.
  2. Under Changelog password, enter 8 to 128 characters and choose Set password.
  3. Under Who can read the published changelog, pick Password and choose Save access settings.

Readers then enter the shared password once per session. Session length sets how long they stay signed in: 1 hour, 8 hours, 24 hours, 3 days, 7 days or 30 days. Sign everyone out ends every session now; changing the password or the visibility does the same. Repeated wrong passwords are slowed down.

On a private changelog:

  • Its feeds, llms.txt and the widget are off.
  • Uploaded images stay reachable by their address.
  • Subscribing and reactions still work for readers who are signed in.

Password access is the only private mode for changelogs. EvoHub does not currently offer sign-in with EvoHub accounts or your own sign-in (JWT) for changelogs; docs sites have both. See Private docs.

Language

In Settings, General, Language sets the language of the changelog's own words — buttons, headings, dates, the widget and the subscribe pages. Your entries are shown as you wrote them. Available languages:

English, Deutsch, Français, Español, Italiano, Português, Nederlands, Polski, Türkçe, Русский, 日本語, 한국어, 中文 and العربية (shown right to left).

Under Customise text, replace single texts of the public changelog in that language — for example the label of the subscribe button. Pick a text from the suggestions, write your version, and choose Save custom text. Keep placeholders in curly braces as they are.

EvoHub does not translate entries; write them in the language your readers use.

Analytics

Turn on Count how the changelog is read in Settings, Analytics, and choose how long to keep the counts: 30, 90 or 180 days, 1 year or 2 years. Older daily counts are deleted automatically.

Open Analytics in the changelog's menu to see, for a date range:

  • totals for Views, Visitors, Widget opens, Widget clicks, Reactions, Feedback, Feed reads, AI requests and Confirmed subscribers;
  • views, visitors and widget opens per day;
  • Top entries, Referrers, Countries, Devices, Feeds, AI readers and AI agents.

Each report can be exported as CSV.

How readers are counted: no cookies, no stored IP address, and a hash that changes daily, so visitors are counted per day. Readers who send Do Not Track or Global Privacy Control are not counted.

Other settings

  • General — name, address, description, Website, Default theme, Let AI crawlers read the changelog, publishing and deleting. See Changelog overview.
  • Brand — logo and brand colour.
  • Review — required approvals. See Writing entries.
  • Widget, Subscribers and Integrations — see Reaching readers.

Last updated