openeditorcode.devFIELD MANUAL / 0.2.41Español
coverage.md DOCUMENTATION

21 — Under the hood

Coverage and sources

An auditable matrix of capabilities, references and version. How to maintain this documentation as OEC evolves.

v0.2.41Source review ·
On this page

Review method

Documentation reviews OEC 0.2.41 and plugin 0.3.4 at independent snapshots: SVG, content filtering, Markdown, document safety, adaptive panels and palette. Each publication status and its evidence are recorded separately; tarball checks do not imply public by-name installation.

The standalone catalog retains 28 configurable IDs and 36 logical palette entries. Plugin options, shortcuts and metadata are audited separately. Public source and evidence links are enabled only after publication is confirmed.

Update with each version

  1. Pin the new version and commit in product.ts after reviewing the diff from the previous version.
  2. Compare useKeyboardShortcuts, the useWorkbench palette, CLI, defaults/schema, document types, Git and distribution scripts.
  3. Update records, sections and the default snapshot in both languages. Every new capability must have a chapter and source.
  4. Review findings: if fixed, update their description with evidence. Do not mix pending plans with available capabilities.
  5. Run the website build and verify:docs: validate identity, internal links, translation structure, catalog, configuration and generated sitemap.

What coverage means

This matrix shows where each reviewed area is explained. It does not claim 100% test coverage, absence of defects or certified compatibility with every terminal. Inherited behavior is identified and static findings retain their status.

Coverage matrix

Every row has equivalent Spanish and English documentation. Plugin sources are pinned to its published commit, independently of the standalone snapshot.

Chapter sources

Links pinned to the reviewed commit; they do not follow main.

Static documentation · ES / ENView coverage ↗