What Link Should a Developer Put on a CV When Their Projects Live on Different Sites?

A developer with projects spread across GitHub, app stores, and product sites should put one stable portfolio URL on the CV, then use that page to label and route each project to its strongest public proof.

A row of unrelated URLs makes the reviewer decide what each link means before they can assess your work. A single index gives that context in advance and survives changes to individual products. It does not replace GitHub or a store listing; it makes those sources easier to navigate from a CV.

Where should the portfolio link appear on the CV?

Place the portfolio URL beside your email and professional profiles at the top, then reference it again only when a project entry genuinely needs more detail.

Use readable anchor text such as “Project portfolio” in a PDF and print the full, short URL where the CV may be printed. The destination should open without an account, explain who you are immediately, and keep the same address as you add new work.

Do not distribute different portfolio links through every job bullet. The recruiter needs one dependable route into your work and direct proof links inside that route.

Top contact block: one short, stable portfolio URL.
Project section: names and outcomes, not repeated raw links.
Portfolio page: direct routes to code, demos, stores, or products.

How can IndieShow create the CV link without a custom website?

IndieShow creates the CV link by assigning your claimed handle to a project page that you edit from a dashboard rather than from code.

Add your name, bio, location if useful, social profiles, and project entries with logos, tags, descriptions, URLs, optional metrics, and clear status sections. The live preview lets you check the composition before publishing the public page.

Because the page lives at indie-show.com/yourname, your CV link stays fixed when a repository moves or an app gets a new listing. You update the destination in the editor instead of exporting another CV for every small URL change.

Claim your IndieShow pageStart by claiming a handle; after that, the dashboard shows the $15 one-year pass and $30 lifetime option See the editor and publishing options.

Which projects should a developer include for one specific application?

Include projects that prove the role’s core work first, then retain other credible projects lower down to show range without diluting the application.

For a backend role, lead with deployed services, APIs, data work, or operational tooling. For mobile, lead with store links and the product decisions behind the app. A tiny relevant project can be more useful than a larger unrelated one if it demonstrates the requested skill clearly.

Use ordering as the customisation layer. The stable link does not prevent tailoring: move the best evidence up before sending the CV, while the rest of your track record remains available below.

How do you describe a project without copying the CV?

Describe what the project does, your contribution, and the proof destination in one or two compact sentences rather than repeating job-history bullets.

The CV answers when and where you worked; the portfolio answers what someone can inspect. Prefer “Scheduling tool for small clinics; built the booking flow and API” to an unscoped list of frameworks. If you add a metric, make it specific and defensible.

Mark unfinished and retired work visibly. A prototype can demonstrate a skill, but it should never be presented as a live production product if the destination no longer works.

Use these broader guides to decide the page structure: show multiple side projects on one page · build an indie hacker portfolio

How does IndieShow keep the CV portfolio current after you apply?

IndieShow keeps the same public handle while you edit project order, status, copy, links, logos, and profile details from the dashboard.

That matters because a recruiter may open the CV days after you send it. Fix broken destinations immediately, move a newly shipped project into the right section, and archive old experiments instead of allowing the page to contradict your application.

Use IndieShow as the maintained index and the original repositories, demos, and stores as evidence. One stable CV link then reflects the work you have now, not only the work you had when you exported the PDF.