Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: enable tab sync #1205

Closed
TomCools opened this issue Nov 13, 2024 · 2 comments · Fixed by #1217
Closed

docs: enable tab sync #1205

TomCools opened this issue Nov 13, 2024 · 2 comments · Fixed by #1217
Labels
enhancement New feature or request process/needs triage Requires initial assessment of validity, priority etc.

Comments

@TomCools
Copy link
Contributor

In the quickstarts, we often support multiple languages. At this time, someone using the non-default language must manually click the tab of the preferred language (ex. Kotlin or Python)

Setting :tabs-sync-option: will sync these tabs. After selecting Python on 1 tab, it will also select Python on all other tabs. See https://github.com/asciidoctor/asciidoctor-tabs for more details.

This increases the usability of our docs at a relatively low cost. We do need to align the naming of all our tabs, and create tabs even when Java/Kotlin have exactly the same content.

@TomCools TomCools added enhancement New feature or request process/needs triage Requires initial assessment of validity, priority etc. labels Nov 13, 2024
@ge0ffrey
Copy link
Contributor

Yes! This is a serious paper cut.

@TomCools
Copy link
Contributor Author

Already did this on a separate branch. @ge0ffrey. Will finish it up today. 😊

TomCools added a commit to TomCools/timefold-solver that referenced this issue Nov 20, 2024
triceo pushed a commit that referenced this issue Nov 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request process/needs triage Requires initial assessment of validity, priority etc.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants