Frequently Asked Questions
Find answers to common questions about services and process.
General
PHPWolf is my public home for building and documenting software systems. It's where I share projects, tools, notes, and the thinking behind them.
Both, in a way.
PHPWolf is a personal brand and working identity, but also anchors a small ecosystem of tools and projects that may grow into more formal offerings over time.
Primarily:
- Software platforms and tools (like DenCMS)
- Infrastructure and workflow experiments
- Writing about architecture, maintenance, and systems thinking
- Occasional game design projects
Some projects are public, some are experimental, and some stay private until they're ready.
DenCMS is a multi-site content management foundation I'm building for real-world use: multiple brands, shared infrastructure, and sane workflows.
PHPWolf itself runs on DenCMS.
Not yet. DenCMS is something I'm actively shaping and protecting at the moment. It's not public yet, but I'm happy to talk if you're curious or think it might be a good fit.
Partially, but not really. At least not in a traditional sense.
PHPWolf shows work in progress, decisions made, lessons learned.
It's closer to showcase + field notes than a brochure or portfolio.
Yes, selectively.
I'm a full-stack developer, but most of my work centers around:
- PHP (specializing in Laravel, but I'm comfortable with all things PHP)
- Vue / Inertia / Livewire
- Relational databases
- Linux infrastructure and deployment pipelines
That said, tools matter less than principles. I'm stack-flexible when the problem demands it.
Because that's where most systems struggle.
Building and deploying features is easy. Keeping systems healthy over time is harder and more valuable. My work is shaped by that reality.
It's a shorthand for how I approach work.
Build with care and restraint. Then take responsibility for what you deploy. Maintenance isn't an afterthought. It's part of the job.
Irregularly, by design.
Updates happen when something meaningful changes: a release, a decision, a new direction. I'm not always optimizing for frequency, but I try to make regular updates when something meaningful happens.
No.
Some things are stable. Some are experiments. Some are halfway between idea and implementation. Some are in various test phases. I try to be clear about which is which.
Use the contact form or send a short email with context:
- What are you building?
- If stuck, what are you stuck on?
- Any constraints (timeline, budget, stack)
Clear questions tend to get clear answers.
Still have questions?
Reach out for more information