Find examples, then choose your own criteria
Developer Portfolios can help you find personal websites to study. Its alphabetical order cannot tell you which example fits a backend engineer applying for a job or a consultant explaining specialist work. Begin with the audience your own site needs to serve.
The README describes the collection as inspiration. Entries pair names with links, sometimes followed by a role or specialty. Use those labels to find candidates, then inspect what each destination explains. A role label is a starting point for browsing, not a review of the person's work.
What happened when we ran it
Our October 3, 2026 sandbox run at commit 39bb80c completed installation in 6 seconds, recording 35 dependencies and 37 MB on disk. The build succeeded in 1 second. Pytest completed in 2 seconds with 39 passed and 0 failed of 39. Pip-audit reported 0 known vulnerabilities.
The checkout contained 25 files, approximately 1,986 source lines and 0.6 MB. The scan found a tests directory and 2 CI workflow files, with no Dockerfile. The recorded configuration was 3 CPUs, 8 GB RAM and image ghcr.io/astral-sh/uv:python3.12-bookworm. That image name does not verify the executing Python or operating-system version.
The supplied results report successful commands, but do not expose their implementation or individual test coverage. We therefore cannot say which destinations the checks contacted or what they verified. No portfolio-by-portfolio browser evaluation accompanies this run, and the results do not establish that the hosted directory application works.
Browse before installing
You can read the Markdown directory in a browser. Local installation is unnecessary if your task is finding examples for your own portfolio.
Try a specific comparison: can a visitor identify the developer's contribution to a project without opening its source? For each shortlisted site, record where that explanation appears and whether the homepage makes it easy to find. Then compare that with a project description you have written yourself. These are suggested browsing steps; we did not execute this exercise or assess its results.
Before copying assets or code, check the destination's own permissions and license. Inclusion in a directory does not establish permission to reuse another person's writing, images or implementation.
Follow the contribution checklist with care
The contribution guide asks contributors to open their portfolio link, check that it loads without an error or parking redirect, add the entry in strict first-name order and leave feed.json unchanged because it is generated automatically.
The guide says a scheduled workflow checks links every Saturday and flags broken or parked destinations for removal. This is the documented policy. The supplied packet does not include the workflow implementation or a report proving that schedule completed, so it cannot establish current availability across the directory. Open a destination yourself before recommending it.
The longer Git guide needs caution. It refers to master in its maintenance steps, then says to create a branch off develop and elsewhere warns about staging. Those inconsistent references weaken its value as a command-by-command tutorial. Use the submission checklist to understand the required change and confirm the current target branch in GitHub before submitting. No contribution commands were executed for this review.
For repeatable research, record the checkout commit and retrieval date. Our measurements belong to 39bb80c; the supplied README and contribution extracts are not pinned to that commit. Release availability is unverified, so this review makes no claim that the repository has no releases.
Choose an alternative for a different next step
Portfolio Ideas includes screenshot and technology columns. Choose it when those details will help narrow your browsing. We did not verify the listed technologies against the destination implementations.
Awesome Portfolio Websites is a website project whose README presents experience, project and research pages. Choose it when you want a codebase to evaluate for adaptation. We did not test its installation or deployment.
How the ratings work
The editorial rubric uses 1 for substantial documented obstacles, 2 for a partial path with unresolved obstacles, 3 for a usable documented path with material limits, 4 for a straightforward path supported by documentation or the supplied run, and 5 for broad independent verification within the rated scope. These are editorial judgments, not benchmark scores. Missing evidence receives N/A.
Setup ease earns 4 because browser access needs no local installation and the supplied installation and build succeeded. Documentation earns 3 because the checklist is concrete but the longer guide mixes branch references. Community support and directory-wide maturity remain unassessed.
Before choosing a layout, write one project explanation in your own words. Use the directory to find a presentation that makes that explanation easy for your intended reader to reach.

