1) When I started this, I thought could this be an HTMX-PHP framework. If you see the examples directory, I added a few HTMX examples early days. Maybe I can niche down on this...
2) If I'm honest, I don't know yet. I first started building the router, then I was told through some feedback that there's been a lot of research (rightly so) into this area and I would be better off implementing the FastRouter that's in Slim, so I switched to that...
As mentioned above, if I could make this framework fit with HTMX more, I could have a PHP framework that talks HTMX with less of the wiring up. I still need to figure this out.
3) I've avoided building an official site/docs for it, but I might have to. I had hoped the examples were a good source, but as more features were added, creating official docs site might have to be my next task.
PHP isn't yet part of my default stack, but I am trying to thanks to what I've been learning building Dumbo.
1) Target Audience: Since Dumbo isn't aiming to compete with Laravel or Slim, who do you see as the ideal user for this framework? Hobbyists, small-scale production apps, or perhaps developers exploring modern PHP paradigms?
2) Distinguishing Features: You mentioned drawing inspiration from Hono.dev—how does Dumbo bring Hono's strengths into the PHP world? Are there specific design patterns or DX (developer experience) improvements that set it apart from existing lightweight frameworks like Slim?
3) Learning Resource Vision: As you see Dumbo also as a learning tool, do you plan to include guided examples or documentation for PHP developers looking to understand the modern ecosystem better?
PHP is definitely in an interesting place right now; excited to see what Dumbo evolves into!