-
-
Notifications
You must be signed in to change notification settings - Fork 8.6k
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
Theme gallery #3522
Comments
Hi, is this still a desired feature? I'm considering working on it |
Hi @vthirupathi , this is still a desired feature, but we need to factorize some code to make this happen first, and then we'll likely delegate it to MLH interns. |
Any ETA on the tailwind preset? |
no progress but we now have a "configurePostCss" hook and users are already using Tailwind with Docusaurus here: #2961 |
Theme gallery
We'd like to have multiple Docusaurus themes.
For now:
We agreed that those themes should all rather implement the same UX and work with docs, blog, pages...
This way, we can:
@docusaurus/utils-client
package (edit: this is now@docusaurus/theme-common
)Related issues to read, as we already had theme-gallery related discussions with @fanny here:
The integration test suite will be handled in a separate issue #3523
IMPORTANT: Algolia crawlers use DOM selectors to understand the hierarchy of the pages. We'll have to also make sure the default Algolia Docusaurus config works fine for all themes, so we should find a way to make the selectors "stable" across themes, in the same way they should be stable for tests. We'll probably add explicit "lvl0-lvl6" markers in each theme so that we don't break these selectors in the future.
See our current config: https://github.com/algolia/docsearch-configs/tree/master/configs/docusaurus-2.json
The text was updated successfully, but these errors were encountered: