greenwood VS lit

I have a project in called Greenwood that can probably help here if you're interested to check it out. Made to easily start with HTML (or markdown) and focused on web standards to make learning and development easy and familiar. Works great with Web Components and can even pre-render them! https://github.com/ProjectEvergreen/greenwood

Either is pretty easy to get started with and keep you nicely aligned with web standards if that's of interesting to you. I have a project that could help you work with either of those option you are so inclined, with the getting started guide of the website giving a brief overview of how to get started with native web components. https://www.greenwoodjs.io/

My project Greenwood might be able to help here, depending on what your current setup looks like. Inspired by the old HTML Includes spec, I created a plugin for replicating this sort of edge side include behavior.

I do, and that's a big part of why I started working on Greenwood. I wanted to always just be able to start from an index.html file, but also have some nice minimal glue like a dev server, file based routing, markdown, and leveraging Web Components for templating and SSR.

That's a big part of why I started working on Greenwood. I wanted to always just be able to start from an index.html file, but also have some nice minimal glue like dev server, file based routing, markdown, and even leveraging Web Components for templating and SSR. Loving learning even more about the web and so for that reason I like to think of it less as a framework, and instead as your full-stack workbench for the web! https://github.com/ProjectEvergreen/greenwood

I created my project Greenwood as a way to support web standards based development (e.g. not a meta framework) that can be as easy to start with as an index.html, or a markdown file, and can do most architectures; SPA / CSR, MPA, SSR. I like to think of it as your full-stack workbench for the web.https://github.com/ProjectEvergreen/greenwoodStill a WIP and continuing to improve our design and feature set, so feel to give it a try, and any and all feedback welcome! Check out our blog if your curious about what we've been up to in 2022, and there will be a post soon about our plans for 2023

Not sure if this would be of interest to you, but my project Greenwood let’s you start with just HTML / markdown and standard web dev to build out the rest, with a focus on supporting Web Components, even for SSR. https://www.greenwoodjs.io

I like to think of my project Greenwood not so much of a framework, for similar sentiments as what you describe, and have come to refer to it as a "workbench for the web"; emphasizing web standards based development (e.g. so not a meta framework) and has great support for Web Components. (full stack web components, ftw!) https://github.com/ProjectEvergreen/greenwood

My project Greenwood might be able to help. It supports web standards based development (e.g. not a meta framework) and has great support for Web Components. As easy to start as an index.html file or a markdown file, and can do most architectures; SPA / CSR, MPA, SSR. I like to think of it as your workbench for the web. https://github.com/ProjectEvergreen/greenwood Still a WIP and continuing to improve our design and feature set, so feel to give it a try, and any and all feedback welcome!

That is the reason why I experiment with the TiniJS framework for a while. It is a collection of tools for developing web/desktop/mobile apps using the native Web Component technology, based on the Lit library. Thank you the Lit team for creating a great tool assists us working with standard Web Component easier.

https://github.com/lit/lit/tree/main/packages/labs/virtualiz...

actually, looking at it (https://lit.dev/), i do exactly that.

I also define a `render()` and extend my own parent, which does a `replaceChildren()` with the render. And, strangely, I also call the processor `html`

I'll still stick with mine however, my 'framework' is half-page of code. I dislike dependencies greatly. I'd need to be saving thousand+ lines at least.

Here, I don't want a build system to make a website; that's mad. So I don't want lit. I want the 5 lines it takes to invoke a dom parser, and the 5 lines it takes do define a webcomp parent.

I rather like https://lit.dev/ for web components so far.

For the reactivity stuff, you might want to read https://frontendmasters.com/blog/vanilla-javascript-reactivi... - it shows a bunch of no-library-required patterns that, while in a number of cases I'd much rather use a library myself, all seems at least -basically- reasonable to me and will probably be far more comprehensible to you than whatever I'd reach for, and frameworks are always much more pleasant to approach after you've already done a bunch of stuff by banging rocks together first.

I work on Lit, which I would hesitate to call a framework, but gives a framework-like DX for building web components, while trying to keep opinions to a minimum and lock-in as low as possible.

It's got reactivity, declarative templates, great performance, SSR, TypeScript support, native CSS encapsulation, context, tasks, and more.

It's used to build Material Design, settings and devtools UIs for Chrome, some UI for Firefox, Reddit, Photoshop Web...

https://lit.dev if you're interested.

I am more a fan of the augmented style because it doesn't entrap you in dev lock-in to platforms.

The problem with frameworks, especially web frameworks, is they reimplement many items that are standard now (shadowdom, components, storage, templating, base libraries, class/async, network/realtime etc).

If you like the component style of other frameworks but want to use Web Components, Google Lit is quite nice.

Google Lit is like a combination of HTML Web Components and React/Vue style components. The great part is it is build on Web Components underneath.

[1] https://lit.dev/

From the comments I see here, it seems like people expect the Webcomponents API to be a complete replacement for a JS framework. The thing is, our frameworks should start making use of modern web APIs, so the frameworks will have to do less themselves, so can be smaller. Lit [0] for example is doing this. Using Lit is very similar to using React. Some things work different, and you have to get used to some web component specific things, but once you get it, I think it's way more pleasant to work with than React. It feels more natural, native, less framework-specific.

For state management, I created LitState [1], a tiny library (really only 258 lines), which integrates nicely with Lit, and which makes state management between multiple components very easy. It's much easier than the Redux/flux workflows found in React.

So my experience with this is that it's much nicer to work with, and that the libraries are way smaller.

[0] https://lit.dev/