Clear evidence.
Protected work.
A practical standard for showing what was built, keeping claims reviewable, and protecting private source, credentials, and client-specific details.
Make the work easy to inspect.
A portfolio should give a reviewer a clear route from a claim to its evidence. These checks keep that route useful without exposing material that belongs in a private repository.
- 01Commit hygiene
Keep changes grouped and commit messages descriptive.
- 02Clean repository
Exclude generated output, caches, dependency folders, and local environment files.
- 03Scoped case studies
Describe responsibilities and decisions without inflating unverified outcomes.
- 04Credential review
Search for secrets, tokens, local paths, and unpublished data before publishing.
Show the proof.
Keep the source safe.
Public pages can demonstrate scope and thinking even when the implementation is confidential.
Public and reviewable
- Public repositories and live websites.
- Case-study summaries with decisions and context.
- README links, screenshots, architecture notes, and review trails.
Protected
- Private source, credentials, tokens, and
.envfiles. - Unpublished datasets and client-specific internals.
- Local machine paths and raw archives that do not aid review.
Before anything goes live.
A short, repeatable pass keeps the published site clear and dependable.
git status --shortcontains only intentional files.- Credentials, placeholders, and unfinished notes have been checked.
- Private projects remain summaries, with no source copied into the site.
- Site, repository, case-study, and document links resolve.
- The built site opens on desktop and mobile with no broken assets or layout overflow.