docs: Add optional Firefox Add-on links to homepage showcase#2208
docs: Add optional Firefox Add-on links to homepage showcase#2208shadoath wants to merge 3 commits intowxt-dev:mainfrom
Conversation
Allow extension entries to include a firefoxSlug alongside the Chrome ID, rendering a "Firefox" badge that links to addons.mozilla.org. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
✅ Deploy Preview for creative-fairy-df92c4 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
I support the idea, since I also publish on Firefox Addons, but having Firefox URL optional while Chrome Extension URL required is still biased toward Chrome Extensions. What if you only publish the extension(s) on Firefox? You can't showcase it, then. Due to smaller user base of Firefox, it actually serves as a great real testing ground with real users before finally deploying it to Chrome. So some people, including me, may publish it there first. |
|
I'll make that update. Also going to scrap the extensions that are already there and add the firefox slug if I can find it. |
|
Only used "K" and not "m" to give the number some weight, when it was 2,000k, it seemed more impressive than 2m. Also, this change helped the stats sit on a single line, making the display cleaner. |
2 participants
Overview
Updates the Using WXT homepage section (
docs/.vitepress/components/UsingWxtSection.vue) so extension cards can list Chrome Web Store and/or Firefox Add-ons, with clearer stats and layout.chromeId,firefoxSlug, or both (ExtensionEntry).useFirefoxAddonDetails). Fetches are per-slug so a bad or missing slug does not drop all Firefox data.Kwith en-US comma grouping, e.g.2,000K users,31.8K users) and star ratings, with Chrome / Firefox labels on every card (including single-store listings).Related composables:
useListExtensionDetails.ts(no-op when there are no Chrome IDs),useFirefoxAddonDetails.ts(resilient batch fetch).Screenshot