.github

Org-wide community health files and profile for PyDevices:

• profile/README.md — the org profile page shown on github.com/PyDevices.
• CONTRIBUTING.md — shared contributing guide, used as the default for repos without their own.
• docs/repo-layout.md — shared directory and root-file convention (src / lib / tests / tools / requirements-dev.txt, …), plus the preferred MICROPYPATH / PYTHONPATH search paths.
• data/repos_db.json — the single source of truth for the repository map. scripts/generate_sites.py renders it into every landing page, into profile/README.md, and into pydevices/docs/ecosystem.md. Run it by hand from a full workspace checkout (python3 dotgithub/scripts/generate_sites.py) after editing the database; it validates the database first and is idempotent.
• .github/ISSUE_TEMPLATE/ — default bug report / feature request templates, used as the fallback for repos without their own.
• docs/github-presence.md — map of Discussions, Issues, Pages sites, licensing, and other org setup.
• docs/platform-roadmap.md — cloud-agent workstreams for platform expansion, including the 2026-07-15 org triage decisions (pursue / docs-only / out; parallel pursue tracks, why-comment rule, out-of-scope list).
• docs/publishing-automation.md — the org-wide release runbook for palettes, pdwidgets, pygraphics, pydevices, and lvgl-python: shared workflows, secrets, discovery rules, and the centralized MIP queue.
• docs/workflows.md — inventory of every GitHub Actions workflow in the org: which are shared, which are per-repo, and which deliberately differ.
• docs/building-docs.md — how the three library ReadTheDocs sites (palettes, pdwidgets, pygraphics) are built and published.
• docs/docstrings.md — Google-style docstring conventions for the generated API reference pages.
• docs/doc-style.md — the fixed set of landmark emoji used on doc section headings across PyDevices, and when (not) to use them.

Board / Detect inventory docs live in pydevices/docs (Pages).

Website: https://pydevices.github.io/

This repo is the org-level glue for community health files, issue templates, and shared docs. It does not publish a product Pages site of its own; the product repos publish their own Pages content, while this repo provides the shared org profile and documentation references.