Chris Ferdinandi Portfolio
Independent web developer and educator focused on vanilla JavaScript and progressive enhancement, maintaining the open-source Kelp UI toolkit and a long-running article archive as an alternative to framework-heavy web development.
What makes it work
A breakdown of the choices that make this portfolio stand out.
A stated, contrarian technical position
Deliberately teaching framework-free JavaScript in an ecosystem dominated by React and similar tools gives the site a clear point of view — visitors know exactly what kind of developer they're looking at within seconds.
An open-source toolkit that backs the philosophy with code
Kelp UI exists as a real, usable library built on the "no framework needed" premise, turning a stated opinion into something visitors can actually inspect and use.
A "Now" page tracking current focus
Publicly noting shifts in focus over time (including writing less than before) is an honest touch that most curated portfolios avoid — it reads as a real person's site rather than a marketing page.
What Web Developers can take from this
Specific, actionable tips to apply to your own portfolio — no generic advice.
Having a clear, stated technical point of view (not just a list of skills) makes a portfolio memorable and easy to categorize at a glance.
Back up any strong technical opinion with an actual open-source project built on that premise — code is more convincing than the opinion alone.
Being honest about changes in your output or focus over time (rather than pretending consistent activity) reads as more trustworthy than a static, evergreen-looking site.
More Web Developer portfolios
Ready to build your portfolio?
Follow the Web Developer roadmap — skills, projects, and timeline to get hired.