Improved TOC header navigation for headers nested in tabs #3010
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Preview of modified files: no change to preview. |
reithor
approved these changes
Jan 15, 2026
Contributor
reithor
left a comment
reithor
left a comment
There was a problem hiding this comment.
lgtm - tested on chrome and opera.
One thing though:
May be it's semantically not 100% correct to use tabs for LTS updates in https://doc.ibexa.co/en/5.0/update_and_migration/from_4.6/update_from_4.6/#lts-updates
Tabs are fine when having a group of very similar things (like MySql|Postgres Headless|Experience|Commerce). Probably it is better to avoid Tabs for LTS Updates ?
Contributor
Author
|
The idea I had is that it's easier to quickly check the tab for each LTS update you use - having it without tabs would mean that you read through every LTS update section even when not using it. But it's something we can discuss within the team |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Target: 4.6, 5.0
Issue reported on Slack.
Disclaimer: code is heavily AI-generated, but I've reviewed and tested it dilligently - hope I didn't miss anything.
One test scenario:
go to https://ez-systems-developer-documentation--3010.com.readthedocs.build/en/3010/update_and_migration/from_4.6/update_from_4.6/ and click on the headers (in the right TOC) in the "LTS updates" section - the tab should be activated automatically.