2bb907d0d9
* added first draft of instructions for pull requests * added a diagram to explain process * added description of the process, moved specific instructions - split the diagram into two parts to easy comperehension and allow people to better follow the process - added descriptions of the conceptual steps, keeping them separate from specific instructions - moved the specific instructions under a common heading to make the ToC more readable * added explanations - added link to GitHub docu on forks - added note on philosophy followed - improved ToC structure * tried to finalize process description (see below) - added airline-style "pay attention to the instructions" tip - added bit about testing with Material for MkDocs documentation and examples from the examples repo - added note on being respectful in discussion and on how sometimes PRs do not get accepted for good reason - improvements for readability * moved the "philosophy" bit to the steps IMHO this is a better place to make this point as the comments are mainly about what tools are used, which is more relevant to the instructions, not the 30k ft view process * added more text to steps guidance, dos and don'ts - added more text to pretty much every section under 'steps' - added a section with dos and don'ts - left some questions for @squidfunk to ponder * addressing first set of comments * addressed further comments In particular: - removed the bits about linters and - about dealing with merge conflicts These may perhaps need attention in the future. * removing question about PR template |
||
|---|---|---|
| .devcontainer | ||
| .github | ||
| .vscode | ||
| docs | ||
| includes | ||
| material | ||
| src | ||
| tools/build | ||
| typings | ||
| .browserslistrc | ||
| .dockerignore | ||
| .editorconfig | ||
| .eslintignore | ||
| .eslintrc | ||
| .gitattributes | ||
| .gitignore | ||
| .stylelintignore | ||
| .stylelintrc | ||
| CHANGELOG | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| Dockerfile | ||
| giscus.json | ||
| LICENSE | ||
| mkdocs.yml | ||
| package-lock.json | ||
| package.json | ||
| pyproject.toml | ||
| README.md | ||
| requirements.txt | ||
| setup.py | ||
| tsconfig.json | ||
A powerful documentation framework on top of MkDocs
Write your documentation in Markdown and create a professional static site for your Open Source or commercial project in minutes – searchable, customizable, more than 60 languages, for all devices.
Check out the demo – squidfunk.github.io/mkdocs-material.
Silver sponsors
Bronze sponsors
Everything you would expect
It's just Markdown
Focus on the content of your documentation and create a professional static site in minutes. No need to know HTML, CSS or JavaScript – let Material for MkDocs do the heavy lifting for you.
Works on all devices
Serve your documentation with confidence – Material for MkDocs automatically adapts to perfectly fit the available screen estate, no matter the type or size of the viewing device. Desktop. Tablet. Mobile. All great.
Made to measure
Make it yours – change the colors, fonts, language, icons, logo, and more with a few lines of configuration. Material for MkDocs can be easily extended and provides many options to alter appearance and behavior.
Fast and lightweight
Don't let your users wait – get incredible value with a small footprint by using one of the fastest themes available with excellent performance, yielding optimal search engine rankings and happy users that return.
Built for everyone
Make accessibility a priority – users can navigate your documentation with touch devices, keyboards, and screen readers. Semantic markup ensures that your documentation works for everyone.
Open Source
Trust 20,000+ users – choose a mature and actively maintained solution built with state-of-the-art Open Source technologies. Keep ownership of your content without fear of vendor lock-in. Licensed under MIT.
Quick start
Material for MkDocs can be installed with pip:
pip install mkdocs-material
Add the following lines to mkdocs.yml:
theme:
name: material
For detailed installation instructions, configuration options, and a demo, visit squidfunk.github.io/mkdocs-material
Trusted by ...
... industry leaders
ArXiv, Atlassian, AWS, Bloomberg, CERN, CloudFlare, Datadog, Google, Hewlett Packard, ING, Intel, JetBrains, LinkedIn, Microsoft, Mozilla, Netflix, Red Hat, Salesforce, SIEMENS, Slack, Square, Zalando
... and successful Open Source projects
Arduino, Auto-GPT, AutoKeras, BFE, CentOS, Crystal, Electron, FastAPI, GoReleaser, Knative, Kubernetes, kSQL, Nokogiri, OpenFaaS, Percona, Pi-Hole, Pydantic, PyPI, Renovate, Traefik, Trivy, Vapor, ZeroNet, WebKit, WTF
License
MIT License
Copyright (c) 2016-2023 Martin Donath
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.