Update on MkDocs Fork and Ecosystem Continuity #12
DevTwilight
started this conversation in
Show and tell
Replies: 2 comments 9 replies
-
|
Alright, thanks for the reminder. I’ve been keeping an eye on the discussions in our community and have read all of them, just haven’t had time to reply yet. ^_^ MaterialX already prepared for this in advance. The update released a few days ago has restricted the dependent version of mkdocs to < 2 to ensure stability first. Then, going forward, I’ll wait for updates from the mkdocs community. I fully support whatever direction they take, whether it’s a fork or a rename! |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
we should use GitHub action for deployment of material docs |
Beta Was this translation helpful? Give feedback.
8 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Update on MkDocs Fork and Ecosystem Continuity
Hi @jaywhj,
Just to keep you updated on the MkDocs ecosystem: the original MkDocs project is moving forward with “Version 2,” but this has left the community in a situation where a fork and rename are being planned to continue supporting the existing ecosystem.
The fork aims to maintain compatibility with existing plugins and themes, and strategies like meta-importers are being explored to allow current extensions to work without major modifications. This should help reduce fragmentation and keep the ecosystem functional while Version 2 evolves.
More context and discussion about the fork can be found here: MkDocs Community Discussion
Thought this might be useful context for MaterialX and other projects that rely on MkDocs.
Beta Was this translation helpful? Give feedback.
All reactions