# VS Code extension README and CHANGELOG finish the detail page

> Treat the README and changelog as sales and trust assets, because the details view shows them where the install decision happens.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/vs-code-extension-readme-and-changelog-finish-the-detail-page/
- Source: [code.visualstudio.com](https://code.visualstudio.com/api/working-with-extensions/publishing-extension)
- GrowthDex source hub: [Visual Studio Code Docs: Publishing Extensions](/sources/visual-studio-code-docs-publishing-extensions-code-visualstudio-com/)
- Last checked: 2026-06-06T12:40:00Z
- Rarity: rare
- Budget: low
- Channels: Marketplaces, Brand, Trust
- Stages: developer tools, detail page, release proof, docs quality


## Why this can grow

The extension detail page is already the product page. Users open it to decide whether the install is worth the risk, and VS Code shows the README plus the changelog right there. That means the page should teach the workflow, show the setup honestly, and make recent shipping cadence visible. The publishing docs add one more useful constraint: image URLs in the README and changelog must resolve over HTTPS. That forces the assets to be durable enough for the Marketplace instead of breaking the page with local or mixed-content junk.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where vs code extension readme and changelog finish the detail page can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Marketplaces and Brand channel.
3. Use the evidence from code.visualstudio.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

VS Code's publishing guide says the Marketplace page uses the root README.md and recommends adding CHANGELOG.md, while the extensions guide says the detail page shows the README and changelog. The publishing tool also requires README and CHANGELOG image URLs to resolve to HTTPS.

## Adjacent tactics in the same lane

- [VS Code extension verified publisher and pre-release track](/growth-ideas/vs-code-extension-verified-publisher-and-pre-release-track/) - same source, 1 shared channel, 1 shared stage
- [Teams Store icon parity with 32px name legibility](/growth-ideas/teams-store-icon-parity-with-32px-name-legibility/) - 3 shared channels
- [GitHub Marketplace feature card preview before brand refresh](/growth-ideas/github-marketplace-feature-card-preview-before-brand-refresh/) - 2 shared channels, 1 shared stage
- [GitHub Marketplace cancellation cleanup within 30 days](/growth-ideas/github-marketplace-cancellation-cleanup-within-30-days/) - 2 shared channels, 1 shared stage

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The VS Code extension page should finish the trust check](/blog/the-vs-code-extension-page-should-finish-the-trust-check/) - marketplaces, SEO, brand trust

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.