tree: 451063b655c5b1eedb5b8b98ea88ad56c112702e [path history] [tgz]
  1. api_docs/
  2. developers/
  3. website/
  4. .markdownlint.yml
  5. README.md
docs/README.md

IREE Documentation

Documentation exclusively for project developers lives in developers/, while the source pages and assets for IREE's user-focused website live in website/.

Developer documentation should use GitHub-flavored markdown (see this guide), while the website uses MkDocs, with the Material for MkDocs theme.

A high bar should be set for pages published to the website:

  • Page structure should be consistent across sections
  • Content should be kept up to date regularly
  • Instructions should be portable across environments (e.g. don't overspecialize on a specific Linux distribution or a particular version of Visual Studio on Windows)

When in doubt, the guide at https://developers.google.com/style offers good instructions.

Developer documentation can compromise on each of these points. Pages may also be promoted to website/ after some refinement.