ABOUT
Philip Rehberger
Full-stack developer in Colorado. Fifteen years of shipping production web work across WordPress, Laravel, React, and Next.js. The business side runs through scopeforged.com; this hub is the WordPress-specific portfolio.
What this hub is for
Most WordPress portfolios are screenshots. This one is a working platform. Every demo on the hub is a real WordPress install at a real subdomain, running the same chassis theme, sharing the same block plugin, and managed through the same provisioning scripts. The case studies link out to the live sites so the work can be poked at — back-end, front-end, Lighthouse scores, source code on GitHub.
The goal is to settle the question that comes up on most WordPress conversations: “can WordPress actually do this?” Yes — and here’s a working example, the code that built it, and the operational scripts that keep it running.
How I work
- Fixed-scope proposals when the work is well-defined. Small enough that “done” is unambiguous.
- Discovery-then-build for larger projects. A short, paid discovery surfaces scope; the build that follows is fixed-price against that scope.
- Clear updates on a cadence the client picks (daily Slack, weekly written, ad-hoc — your call).
- Source-controlled deliverables. Every project ships as a real repository on the client’s GitHub org, deployable from a script, not a tarball.
Outside the WordPress lane
This hub focuses on WordPress. The personal side of my work — songs, books, family games, and a few open-source packages — lives on philiprehberger.com. They’re separate sites by design: clients shouldn’t have to scroll past my albums to find a case study, and listeners shouldn’t have to read a stack diagram to find a song.
Get in touch
Project inquiries go through scopeforged.com. For everything else — questions about the platform itself, the code that builds it, or to flag a bug on a demo — email me@philiprehberger.com.