Skip to content

docs: record where the plugin page's content comes from - #148

Merged
viztor merged 1 commit into
mainfrom
docs/plugin-page-map
Nov 2, 2026
Merged

viztor merged 1 commit into
mainfrom
docs/plugin-page-map

Conversation

@viztor

@viztor viztor commented Nov 2, 2026

Copy link
Copy Markdown
Owner

The plugin page renders meta.detail from locale/<language>.json, falling back to the whole README — which is why this package's page carried 461 lines of engineering notes until #146.

A maintainer needs that fact in the repo map, not only in the test that enforces it, because the next person to wonder why the page looks like that will read the map first.

One entry, pointing at docs/detail.md, the hero image's shipping requirement, and test/plugin-detail.test.ts.

The page renders `meta.detail` from `locale/<language>.json`, falling back to
the whole README — which is why this package's page carried 461 lines of
engineering notes until the previous commit. A maintainer needs that fact in the
map, not only in the test that enforces it, because the next person to wonder
why the page looks like that will read the map.
@viztor
viztor merged commit 5903131 into main Nov 2, 2026
3 checks passed
@viztor
viztor deleted the docs/plugin-page-map branch November 2, 2026 15:16
@viztor viztor mentioned this pull request Nov 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant