Docusaurus customizations
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- react
- Domain
- documentation, frontend
Research direction
Review the custom theme components under src/theme/ and compare them with the newer Docusaurus theme component structure. Use the DocPage, DocItem, navbar, doc metadata, and custom CSS examples named in the issue as discussion points. Done means identifying concrete, reusable customization needs and documenting which refactors or stable class names would address them.
Written by the indexing model from the issue text.
Description
Hi there, I'm the Docusaurus maintainer.
Your site has interesting customizations, and I'd like to discuss those.
In particular, noticed the custom theme components implemented by @jaredcbaum here: https://github.com/ionic-team/ionic-docs/blob/main/src/theme/
Unfortunately, this requires the ejection of a bit too much internal code.
We are trying to make such customizations simpler over time, with less code to manage on your side, and would like to discuss such opportunities with you.
Note that for the next version, we refactored a few theme components. Many large components have been split into smaller ones, so that you can more easily intersperse your own components before/after the default ones.
Please take a look and let us know if any of your use-cases now become simpler to implement, and if some further refactors could help you.
Some random bits:
-
We really want to provide a system for custom navbar item types, but your workaround seem to work fine until then (https://github.com/facebook/docusaurus/issues/7227)
-
We could refactor
DocPageto allow you to more easily add your custom doc navbar -
We could refactor
DocItemmore to allow you to more easily change the layout and plug your demo sandbox -
We could add the doc meta to a React context and provide the hook so that things like
editUrlin TOC do not require an extra prop
Those are just examples, open to anything as long as it's not too specific to your site and reusable by others.
Also open to knowing better which custom CSS rules are fragile and for which we could provide more stable class names
Note that we have a dedicated issue to report customization use-cases: https://github.com/facebook/docusaurus/discussions/5468
- Dominant language
- MDX
- Stars
- 621
- Forks
- 3.2k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 86
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ionic-team/ionic-docs
-
content
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
ionic-team/ionic-docs#4705 ·
-
content package: angular
Difficulty 2/5 Half a day Newbie friendliness 78/100
ionic-team/ionic-docs#4702 ·
-
triage
Difficulty 1/5 Under an hour Newbie friendliness 80/100
ionic-team/ionic-docs#4546 ·
-
content: broken link Opencontent
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ionic-team/ionic-docs#4381 · 2 comments ·
-
triage
Difficulty 1/5 Under an hour Newbie friendliness 72/100
ionic-team/ionic-docs#3639 ·
All issues in ionic-team/ionic-docs
Similar issues
-
Area: Excel support
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
orbeon/orbeon-forms#7893 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
docToolchain/docToolchain#1705 ·
-
kb-infra-drift
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
OCHA-DAP/ds-knowledge-base#653 · 1 comment ·
-
area/dev-productivity area/disaster-recovery area/ipcei kind/enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
namespace operations
Difficulty 1/5 Under an hour Newbie friendliness 90/100
EclipseFdn/open-vsx.org#13419 ·