5 items
Comment on rendered markdown previews in GitHub PRs. Because GitHub won't let you write in the margins. Comment on rendered markdown previews in GitHub PRs. The thing GitHub forgot. GitHub lets you leave inline comments on code in PRs. Line by line, with full context. It's great. GitHub also lets you preview rendered markdown in PRs. Tables, headings, mermaid diagrams, the works. GitHub does not let you do both at the same time. If you want to review a TRD, an RFC, an architecture doc, a changelog — anything where the rendered output is the thing that matters — you have to bounce between the rendered preview (no comments) and the raw markdown diff (no rendering, hard to read). Or you give up and load the doc into Google Docs.
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.