This section collects precise, version-bounded Web Device contracts. It is for lookup, not a replacement for task-oriented guides. A page that records a limitation or an unresolved public contract is intentionally not a promise of a hidden API.
Read by question
- Directory and file conventions for file locations and compatibility inputs.
- AUP layout boundary for what a Web layout can accept.
- Source-binding reference for declared data-source boundaries.
- Site configuration reference and routes and locales reference for the currently verified configuration and URL surface.
- Content access reference for
access,preview, path rules, and the serve-time gate. - Bookmark and note (save capability) for
blocklet.yamlsave:, HTML attributes, and/.actions/bookmark//.actions/annotate. - Component resolution and theme and token reference for provider/resolver boundaries.
- Unit pages (one capability per page):
- Layout components — default theme + site
.web/components - Surfaces
- Markdown directives & structures
- Layout components — default theme + site
- Version compatibility before carrying an example to another ARC release.