Files
micropython/docs
Damien George 0e1d857f80 README: Define and describe the port Tier levels.
MicroPython has quite a few ports now (20 of them), but not all are in the
same stage of development.  This commit attempts to define port Tier levels
and assign a Tier to each of the existing ports.

The main aim here is to set expectations for the level of support and
development each port gets.  And also lower the bar of entry for new ports
so they can enter at a low Tier and gradually rise up to Tier 1.

See prior art here:
- https://peps.python.org/pep-0011/
- https://doc.rust-lang.org/rustc/target-tier-policy.html
- https://docs.zephyrproject.org/latest/project/release_process.html#hardware-support-tiers

Signed-off-by: Damien George <damien@micropython.org>
Signed-off-by: Angus Gratton <angus@redyak.com.au>
2025-10-23 11:23:17 +11:00
..
2025-09-16 10:39:46 +10:00

MicroPython Documentation

The MicroPython documentation can be found at: http://docs.micropython.org/en/latest/

The documentation you see there is generated from the files in the docs tree: https://github.com/micropython/micropython/tree/master/docs

Building the documentation locally

If you're making changes to the documentation, you may want to build the documentation locally so that you can preview your changes.

Install Sphinx and sphinx_rtd_theme, preferably in a virtualenv:

 pip install sphinx
 pip install sphinx_rtd_theme

In micropython/docs, build the docs:

make html

You'll find the index page at micropython/docs/build/html/index.html.

Documentation autobuild

For a more convenient development experience, you can use sphinx-autobuild to automatically rebuild and serve the documentation when you make changes:

pip install sphinx-autobuild

Then run from the micropython/docs directory:

sphinx-autobuild . build/html

This will start a local web server (typically at http://127.0.0.1:8000) and automatically rebuild the documentation whenever you save changes to the source files.

Having readthedocs.org build the documentation

If you would like to have docs for forks/branches hosted on GitHub, GitLab or BitBucket an alternative to building the docs locally is to sign up for a free https://readthedocs.org account. The rough steps to follow are:

  1. sign-up for an account, unless you already have one
  2. in your account settings: add GitHub as a connected service (assuming you have forked this repo on github)
  3. in your account projects: import your forked/cloned micropython repository into readthedocs
  4. in the project's versions: add the branches you are developing on or for which you'd like readthedocs to auto-generate docs whenever you push a change

PDF manual generation

This can be achieved with:

make latexpdf

but requires a rather complete install of LaTeX with various extensions. On Debian/Ubuntu, try (1GB+ download):

apt install texlive-latex-recommended texlive-latex-extra texlive-xetex texlive-fonts-extra cm-super xindy