Do you ned a lot of experience to know how to start browser-native tools?
I wouldn't have a clue how to start with Web Components and all the other things, to build a < 1000 user web app. I've read the Web Components docs and tutorials but there's few tutorials that are like "Here's how to a full system for XYZ; here's to
handle templating, routing, API data layer, server-side, etc."
I don't think I have the energy to move off from Sveltekit to a new thing, without having to re-learn everything and make a ton of mistakes
It's been a while since I dipped into it, but Web Components use this thing called Shadow DOM to encapsulate the CSS inside from being affected by the stuff outside. Great for compartmentalization, but unnecessary for my personal needs.
So if you're curious about the concept, check out Custom Elements. Same thing, but no Shadow DOM. I found them to work quite well for a toy project I made a couple years ago.
Shadow DOM is a nice touch and in terms of isolating CSS definitions per-component, it does something beyond what most popular front frameworks can do. That said, I know some developers don't even use the shadow DOM; you can use inline styles like some people do with React or you can use a centralized stylesheet for skinning and only write barebones CSS definitions as part of components.
I wouldn't have a clue how to start with Web Components and all the other things, to build a < 1000 user web app. I've read the Web Components docs and tutorials but there's few tutorials that are like "Here's how to a full system for XYZ; here's to handle templating, routing, API data layer, server-side, etc."
I don't think I have the energy to move off from Sveltekit to a new thing, without having to re-learn everything and make a ton of mistakes