# A featured-on section for the badges you earned

> Show the launch badges and mentions you earned in one tidy, fast section, from one data file.

Canonical: https://abacklaunch.com/prompts/featured-on-section
Last updated: 2026-10-26

Version 1.0.

Badges from launch sites and press mentions are social proof for the production site, but pasted embed codes pile up into a slow, messy footer. Put the badges and mentions I have really earned into one tidy, fast section, kept in a data file, using each site's own badge code where its terms require it.

Site: not given. Find the production URL in the project config, or ask me.

## Ground rules

1. Read before you write. Explore the parts of the codebase this job touches and tell me what is already in place.
2. Plan, then stop. Give me a numbered plan: what you will change, in which files, and why. Wait for my approval before editing anything.
3. Fix things at their source (the shared layout, the config, the generator), not with one-off patches page by page.
4. Keep the project's conventions: its framework APIs, file layout, naming and code style. Add no new dependency without asking.
5. Where something is already done well, say so and leave it alone.

## You will not

- Edit `.env` files, secrets or API keys, or print their values.
- Deploy, push, merge or publish anything.
- Delete data, or run migrations or scripts against a production database.
- Add tracking, third-party scripts or links to any site I did not ask for.
- Change copy, design or behaviour that this job does not need.
- Add badges or mentions I have not confirmed.
- Alter a badge code whose site requires it unchanged.

## Your stack

- Framework: Work out the framework, router and build output from the project files (package.json, lockfiles, framework config) before planning, and say which you found.
- Host: Work out where the site is hosted from the config files (vercel.json, netlify.toml, wrangler config, Dockerfile, fly.toml) and say which you found.

## Steps

### 1. Collect what was earned

Ask me for each badge or mention: the site, what it was for (launched, top 3 of the week, featured article), the date, the link, and the badge embed code if the site provides one. Only include what I confirm.

### 2. Store it as data

Keep entries in one data file: name, kind, date, link, image or embed code. Where a site's badge must be its own code (some check for it to keep a listing's link), keep that code as given; otherwise use a local image.

### 3. Build the section

A compact row or grid in the footer or the about page, with consistent heights, images with width, height and alt text, lazy loading below the fold, and links that open the listing or article. Third-party badge scripts must not block rendering.

### 4. Keep it honest

Show each badge for what it is ("Launched on", not "Winner", unless it won), and keep the date. Remove badges whose listing no longer exists.

## Done means

- [ ] Every badge and mention shown is one I confirmed.
- [ ] Entries live in one data file.
- [ ] Images have dimensions and alt text, and no badge script blocks rendering.
- [ ] Each badge says what it was for, honestly.

## Report back

When you finish, give me:

- what you changed, file by file;
- anything you skipped, and why;
- anything I must do by hand (DNS records, dashboards, accounts, deploys);
- how to check each change on the live site.

## Related

- [A press kit page writers can use in two minutes](https://abacklaunch.com/prompts/press-kit-page)
- [A testimonial wall from real reviews](https://abacklaunch.com/prompts/testimonial-wall)
- [A changelog page with dated entries and a feed](https://abacklaunch.com/prompts/changelog-page)