Changelog tabs: separate changelogs for Free, Pro and more
Changelog tabs split one changelog into several, each with its own releases. A typical use is one tab for your free plugin and one for the Pro version, but you can use them for any split: editions, platforms, apps or plans.
When to use tabs
Use tabs when one product ships in more than one edition and each edition has its own version numbers and release notes.
| Situation | What to use |
|---|---|
| One product, one release history | A single changelog, no tabs |
| One product in several editions, such as Free and Pro | Changelog tabs |
| Completely separate products, each with its own docs | One knowledge base per product |
Without tabs, every release sits in one list and readers have to work out which ones apply to them. With tabs, readers pick their edition and see only its releases.
How tabs work
- Tabs belong to one knowledge base. Each knowledge base has its own changelog and its own tabs.
- Readers see tabs once you have two or more. With one tab, or none, the page stays a single changelog.
- Every release belongs to exactly one tab.
- The first tab is the one readers land on.
- You can add as many tabs as you need, up to 20.
Add your tabs
Open the changelog settings
Go to PinkDocs → Settings → Changelog and scroll to Releases. Above the list of releases you'll see a bar with All and a dashed + button.
Add the first tab
Click +. A tab named Free appears, ready for you to type a new name. Press Enter to keep the name.
Add the second tab
Click + again. The second tab is named Pro by default. Later tabs start as Tab 3, Tab 4 and so on.
Save
Save your settings. The tabs now appear on your changelog page.
Put each release in a tab
Once you have two or more tabs, every release shows a small menu next to its version and date. Choose the tab the release belongs to.
- Releases you already had start in the first tab. Move the ones that belong elsewhere.
- A new release joins the tab you are viewing. Click Pro, then New release, and the release is created in Pro.
- If All is selected, a new release goes to the first tab.
The number beside each tab name is how many releases it holds. Click a tab to show only its releases, or All to see everything.
Rename, reorder and delete tabs
Rename
Double-click a tab name, type the new name and press Enter. Press Escape to cancel. Names can be up to 30 characters.
?tab=pro to ?tab=premium. Update any links you have shared to the old address.Reorder
Drag a tab onto another tab to move it to that position. Releases stay with their tab. With the keyboard, focus a tab and press Alt + Left or Alt + Right.
The order matters: the first tab is the default one on your changelog page.
Delete
Click the tab to select it, then click the × on it. PinkDocs asks you to confirm and tells you how many releases the tab holds.
Nothing is final until you save. If you delete a tab by mistake, reload the page without saving and it comes back with its releases.
If only one tab is left and you remove it, its releases are kept. You are back to a single changelog.
What readers see
On your changelog page, the tabs appear under the title and subtitle. Each tab shows its name and number of releases.
- The first tab opens at the normal changelog address, such as
yoursite.com/docs/changelog/. - Every other tab has its own address, such as
yoursite.com/docs/changelog/?tab=pro. Link straight to it from your website, emails or plugin. - The filters and version list in the sidebar apply to the tab being viewed.
- On small screens, tabs wrap onto a second line when there are many.
If two tabs have the same name, the second gets an address ending in -2, such as ?tab=pro-2. Give tabs different names to avoid this.
Tabs in the Changelog block
The Changelog block shows your latest releases on the docs homepage. With tabs turned on, each release in the block carries a small label with its tab name, so readers can tell a Free release from a Pro release at a glance.
Tabs and AI tools (MCP)
If you have connected PinkDocs to Claude or another AI tool, the assistant can read and write to any tab.
- When it reads the changelog, it sees the list of tabs and which tab each release belongs to. It can also ask for one tab only.
- When it adds a release, it can name the tab. Without a tab name, the release goes to the first tab.
Example prompts:
- "Show me the last five releases in the Pro changelog."
- "Add version 2.1.0 to the Free changelog with these changes."
If you name a tab that doesn't exist, the assistant gets the list of valid tab names back instead of adding the release to the wrong place.
Example: Free and Pro
Create the tabs
Add two tabs and name them Free and Pro.
Sort your existing releases
All releases start in Free. Open each Pro release and switch its menu to Pro.
Check the counts
The numbers on the tabs should match what you expect, for example Free 12 and Pro 7.
Save and link
Save, then link Pro customers to yoursite.com/docs/changelog/?tab=pro.
Common questions
As many as you need, up to 20. Two to four is easiest for readers to scan.
No. Each release belongs to one tab. If a change applies to both editions, add a release to each tab.
Yes. Move every release into one tab, delete the other tabs, then remove the last tab. Its releases are kept as one changelog.
Readers only see tabs when there are two or more, and only after you save. Check that the changelog itself is published as well.
They are deleted with the tab, after you confirm. Move them to another tab first if you want to keep them.
Yes. Tabs are set per knowledge base, so two knowledge bases can use different tabs or none at all.
