This documentation is for you if you're contributing to the Mojo standard library. For example, if you're adding or changing stdlib APIs, fixing bugs, or working through the codebase for the first time, start here.
-
development.md—Mojo standard library development: Set up your environment, fork and branch, install the nightly Mojo compiler (for example, with Pixi), and run tests. Start here if you're new to contributing.
-
style-guide.md—Coding standards and style guide: Conventions for stdlib code: file layout,
mojo format, naming, value lifecycle, API docstrings, and how to validate docstrings. -
docstring-style-guide.md—Mojo docstring style guide: How to write API docs (docstrings) in Mojo: Markdown usage, code font, Parameters and Constraints sections, and alignment with the Google Python docstring style.
-
faq.md—Frequently asked questions: Contributor-focused FAQ for the standard library (platform support, bug reporting,
AnyTypevs__TypeOfAllTypes, MLIR dialects, compiler-runtime). -
governance-structure.md—Mojo standard library governance structure: Who leads the stdlib, how reviews and proposals work, and how the structure may evolve.
/mojo/docs: Source docs for docs.modular.com/mojo./max/docs: Docs for developers working in the MAX framework./max/docs/design-docs: Engineering docs that describe how core Modular technologies work.- docs.modular.com: All other developer docs.