What it was
A short Markdown guide to Chrome power-user features — keyboard shortcuts, DevTools tricks, Omnibox capabilities, gestures. Not nanodegree work; written in 2025 as a “what I’d tell a new dev” braindump that I imagined growing into a community-edited guide.
It didn’t grow into anything; the content is fine but the format (a single README) doesn’t invite contribution.
What it taught me
Documentation-only repos rarely catch contributions unless they’re plugged into an editing pipeline (a GitBook, a deployed site, a linked-from-elsewhere reference). A loose README in an otherwise-unknown account is the documentation equivalent of a tweet — write-only.
If I cared about the content, the right move would have been a
too.foo/apps/chrome page (the Astro tile pattern) with proper
discoverability + a “suggest an edit” link to the source MDX.
Lesson noted; not executed.