There is still a real gap between "making some HTML" and actually getting something published on the web, especially for non-technical users. A simple path on top of GitHub Pages makes a lot of sense.
Curious how you are thinking about the next step after publish. Do you want weejur to stay intentionally minimal, or do you see it growing toward simple editing / updating workflows too?
CSP always feels like one of those things that sounds straightforward in theory, but gets annoying fast once you are trying to make a real app work without punching accidental holes in the policy.
Curious how you approached the feedback loop: does the extension mainly help generate directives, or does it also help explain which current policy rule is actually causing a given breakage?
For many business apps, vanilla JS with strong server-side structure is still a very solid choice. If I need heavier server-side logic, I am very happy with MVC in .NET Core and keeping the front end as close to the platform as possible.
I think a lot of teams reach for framework complexity earlier than they really need to.
I used Grammarly because English is not my native language, but the post itself was written by me.
It's funny that we're getting to a point where people might need to intentionally write with grammar mistakes just to prove they're human.
Sometimes I wish we were still in 2016.