Code Nomad – Developer Portfolio
My personal website and publishing platform, built independently to present my experience, document projects as case studies, and publish technical articles. Public and NDA-covered projects share one case-study format, and the content is maintained as Markdown files and structured data. The site is available in English and Polish.
Overview
The site has to serve three purposes: present my professional experience, document projects that are either public or covered by NDA, and keep publishing technical articles low effort. It has to work in English and Polish, stay readable on small screens, and remain fast and accessible. Performance and accessibility are goals I build toward; this case study does not quote audit scores.
My Role
I designed and built the site on my own, alongside a full-time Tech Lead role. I made the decisions on frontend architecture, content structure, interface, and release tooling, and I maintain both the code and the content.
Technologies Used
Key decisions
Public and NDA-covered projects. I needed to show work whose code and client details I cannot share. Each project carries an NDA flag that switches it to a layout without source or demo links and with a confidentiality notice, and the copy describes my role and decisions instead of client specifics. The trade-off is that NDA case studies stay at the level of context and decisions, with no code to inspect.
Content and localization. I wanted to publish without a CMS. Articles are Markdown files in the repository, with an optional Polish version next to each English file, and interface text and project content live in per-language message files. The trade-offs are that there is no editing interface and that Polish content has to be written and kept in sync by hand. A post without a Polish file is shown in English with a notice.
Animation and accessibility. I wanted motion to support reading rather than compete with it. Animation is limited to entrances and scroll reveals, and the animation code checks the reduced-motion preference before running. The trade-off is extra client-side JavaScript on the animated pages.
Release notes. I wanted a public changelog without maintaining one manually. A script generates the release notes file from Conventional Commits before every dev run and build, and a Husky hook with Commitlint enforces the commit format. The trade-off is that the notes are only as good as the commit messages; commits that ignore the convention are not captured.
Outcomes
Delivered. A live site in English and Polish with a projects listing, case studies, a blog, and a public release notes page generated at build time. Publishing a new article means adding a Markdown file.
Limitations. I have not collected data on traffic, inquiries, or conversions, so I make no claims about audience results. Adding or changing a project case study is a code and message-file change, not a content-editor task.
Highlights
- Articles published as Markdown files, with optional Polish versions
- Release notes generated from commit history, so the changelog needs no manual upkeep
- Animations that respect the reduced-motion preference