squidfunk / squidfunk/mkdocs-material
⚠️ End of life extended to May 5, 2027
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 27.5k
- Forks
- 4.1k
- Avg merge
- 2h 39m
- Merged PRs (30d)
- 1
Description
[!WARNING]
Material for MkDocs is in its final maintenance period. We have extended critical bug fixes and security updates through May 5, 2027, six months beyond the previously announced date. New feature development remains focused on Zensical.
There is no need to migrate immediately. The extension gives teams more time to evaluate Zensical, test their existing projects, and plan a controlled production transition.
Looking ahead
Zensical is our next-generation, open source static site generator, built from first principles by the team behind Material for MkDocs. It aims to remain compatible with your existing Material projects while bringing static site generation, theming, customization, and authoring into one coherent stack.
Zensical Studio is an authoring environment built on that foundation. It works with existing MkDocs projects, so you can write and preview your documentation there before migrating your site.

For the full context behind this transition, why we built Zensical and what it means for Material users, read our announcement:
→ Read the full announcement on our blog
Transitioning to Zensical
Zensical already supports a substantial part of the Material for MkDocs experience. These resources can help you assess when it is right for your project:
- How Zensical is compatible with Material for MkDocs
- How to build Material for MkDocs projects with Zensical today
- Supported Material for MkDocs features
- Native support for plugins from the MkDocs ecosystem
- What MkDocs 2.0 means for documentation projects
We are continuing to make the transition easier over time.
Stay in touch
- Star or watch the Zensical GitHub repository
- Subscribe to the Zensical newsletter
- Follow Zensical on X, Bluesky, or Fosstodon
[!NOTE]
Need help planning ahead?
If documentation is business-critical to your organization, get in touch to discuss Zensical, a longer transition, or support options.
Changes to the issue tracker
We will continue to welcome contributions and reports, while prioritizing work that keeps existing Material for MkDocs sites dependable during the maintenance period:
- Bug reports: Please continue to report reproducible bugs using our bug reporting guidelines. We will prioritize security issues and defects that materially affect existing sites. Minor issues may not receive a fix.
- Feature requests: New feature development belongs in Zensical. You are welcome to share requests, and we may use them to inform Zensical’s direction.
- Documentation issues: Documentation corrections and improvements remain very welcome.
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.
Research direction
The issue contains an end-of-life announcement but names no repository file, test, or entry point to update. First clarify which documentation or project content this should change and define the expected published location and acceptance criteria; completion cannot be verified from the current issue alone.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100