Front-end Portfolio Examples

The underlying structure is the same for every role — one clear claim, two or three verifiable projects, a GitHub profile that supports them, and a CV that links to both. What changes for front-end work is the emphasis, and which projects are worth featuring.

Worked examples

Projects that work for front-end roles

Five briefs from the library that produce the kind of evidence front-end reviewers look for:

• Module Deadline Tracker — Coursework deadlines live across four different university systems, an email thread and a lecturer's slide. Students miss submissions they knew about a fortnight earlier. (1–2 weekends)
• Recipe Cost Calculator — Students cooking on a budget have no idea what a meal actually costs per portion, so food shopping is guesswork and money disappears. (1–2 weekends)
• Markdown Notes App — Note apps are either too heavy or lock your notes in a proprietary format you cannot grep. (1–2 weekends)
• Multi-City Weather Dashboard — Checking the weather for several places — home, university, where family lives — means opening the same site three times. (1 weekend)
• Spaced-Repetition Flashcards — Revising by re-reading notes is close to useless, and the good spaced-repetition tools have a steep learning curve for one module's worth of revision. (2 weekends)

Full specifications for these and the rest are on the front-end projects page.

Other tracks

• Back-end portfolio examples
• Full-stack portfolio examples
• Mobile portfolio examples
• Game development portfolio examples