# adom-component-page

Create a wiki component page the right way.

## The three rules

1. **Slug is `<manufacturer>-<mpn>`.** `ams-ams1117`, `umw-ams1117`, `microchip-lan7800`. A bare MPN cannot express the case where one part number has two manufacturers, two datasheets and two sets of limits.
2. **One page per datasheet.** The datasheet draws the family boundary. A datasheet covering six voltages and three packages is one page covering all of them, never six pages. Two manufacturers with two datasheets for the same MPN are two pages.
3. **`readme.html` is the page.** Hand-built, on the Adom theme tokens, following a fixed ten-section shape. `README.md` is shadowed by it.

## What is in here

| Path | What |
|---|---|
| `SKILL.md` | The procedure: boundary decision, slug and title, dedup, CAD, the section shape, placeholders, publishing, deprecating, libraries |
| `templates/readme.html` | The section skeleton with the Adom studio-dark tokens |
| `templates/page.json` | Manifest skeleton with the component block |
| `scripts/inject_layers.py` | Fills the fab, silk and courtyard groups that `adom-footprint` 1.0.20 leaves empty, so component outlines are visible |
| `scripts/build_switcher.py` | Wraps N footprint embeds into one package switcher |
| `reference/worked-example.md` | The AMS1117 build end to end, every command in order, including the two places it went wrong first |

## Anything missing gets a placeholder, not silence

If a file or a fact is not available, the page says so and invites a pull request. A missing row reads as "this part has no Altium library". A placeholder reads as "nobody has contributed one yet", which is true and actionable.

## Reference pages

[adom/ams-ams1117](https://wiki.adom.inc/adom/ams-ams1117) and [adom/microchip-lan7800](https://wiki.adom.inc/adom/lan7800) are the standard. Open one before you build.

See `SKILL.md` for the full procedure.