Changelog settings

https://docs.evohub.io/mcp

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

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

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

{
  "servers": {
    "evohub-docs": {
      "type": "http",
      "url": "https://docs.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.

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.

#Preview before connecting a domain

You can see the changelog exactly as readers will, before it has a domain or without one. Open the changelog in the console and, at the top of its entries, choose Preview. The changelog opens in a new tab, drawn by the same renderer as the live site, with a thin banner on top: Preview — only your team can see this. Connect a domain to publish.

• Only signed-in members of your organization who can read the changelog can open a preview. The link from the button works once and only for two minutes; after that, choose Preview again.
• A preview lasts 15 minutes from the moment you ask for it. Links inside it stay within the preview.
• Previews are never indexed or cached, are not counted in analytics, and are not billed.
• Nothing can be written from a preview: the subscribe form, reactions and feedback are hidden, so no subscriber is added and no email is sent. It shows the published entries, published changelog or not.

#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 Who can read the published changelog, pick Password.
3. In the password card that appears, enter 8 to 128 characters and choose Set password, then choose Save changes. Until a password is set, the console says Set a password first.

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. After 10 wrong passwords, a reader has to wait up to 15 minutes before trying again.

On a private changelog:

• Its feeds and llms.txt open only for readers signed in with the password, so feed readers and AI tools cannot read them; the widget and the MCP server 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.

#Header links

In Settings, Links, add up to five links (a label of up to 40 characters and an https:// address) that the public changelog shows in its header — in a menu on phones — and its footer; if your organization has a published docs site, Add a link to your docs adds it in one click, and a docs site's Navigation offers Add a link to your changelog the same way.

#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 changes. 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 under Keep the counts for how long to keep them: 30, 90 or 180 days, 1 year or 2 years. Older daily counts are deleted automatically.

The counts themselves are in EvoTrail, on the Changelog tab, with every other product's. Pick the changelog there to see, for a date range, its views and visitors, What's new widget opens and clicks, reactions, feedback, feed reads, AI readers, its entries, the emails sent per day and subscriber growth. Tables can be downloaded as CSV. An old link to the changelog's Analytics screen opens that tab.

AI reads count each entry once per AI reader a day — a crawler fetching the same entry, the list or llms-full.txt fifty times in a day is one read — while AI requests count every fetch. A reader is the crawler's name when it gives one, otherwise the kind of request; every MCP tool call is a read. Days from before AI reads were counted show their requests as reads.

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, Let AI crawlers read the changelog, and deleting. See Changelog overview.
• Brand — logo, Show the site name next to the logo, brand colour and theme.
• Review — required approvals. See Writing entries.
• Widget and Notifications, and the Subscribers page — see Reaching readers.
• GitHub — connect a repository and import GitHub releases. See Managing the changelog from GitHub and Writing entries.

#Related

• Changelog overview
• Reaching readers
• Connect a custom domain to a docs site