greenwood VS lwc

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!

Actually I was wondering if lwc oss is still a thing. The website lwc.dev looks like it hasn't been updated since the release in 2019. Are many people using it or was it a nice try by Salesforce but can we consider it dead? I know of course it can't compete with react, vue or angular, but has it built a nice user base around it to keep it interesting?

Web component browser APIs aren't that many, and not that hard to grasp (if you don't know about them, have a look at Google's Learn HTML section and MDN's Web Components guide); but creating a web component actually requires taking care of many small things. This is where web component libraries come in very handy, freeing us of having to think about some of those things by taking care of them for us. Most of the things I'll mention here are handled one way of another by other libraries (GitHub's Catalyst, Haunted, Hybrids, Salesforce's LWC, Slim.JS, Ionic's Stencil) but I'll focus on Google's Lit and Microsoft's FAST here as they probably are the most used web component libraries out there (ok, I lied, Lit definitely is, FAST not that much, far behind Lit and Stencil; but Lit and FAST have many things in common, starting with the fact that they are just native web components, contrary to Stencil that compiles to a web component). Both Lit and FAST leverage TypeScript decorators to simplify the code even further so I'll use that in examples, even though they can also be used in pure JS (decorators are coming to JS soon BTW). I'll also leave the most apparent yet most complex aspect for the end.

Now in Alba’s role, she and her team use Lightning Web Components (LWC) to create custom user interfaces, a framework based on Web Components standards. With LWC, Alba creates components using modern, standard JavaScript. This means the skills that she learned previously are transferable to other JavaScript-based technologies. She pointed out that on top of this transferability, LWC is open source, and developers can use it outside of the Salesforce platform. Components can be used in Lightning App Builder and published on the AppExchange for other customers to use them.

Lightning Web Components (LWC) from Salesforce are based on standard Web Components built using HTML and JavaScript. They are lightweight, easy to build, and perform well in modern browsers. When building LWCs, you’ll become familiar with the concept of composition: piecing together simple building-block components within the body of a more complex component.

Indeed. Ever built anything in LWR+LWC opensource? It's opensource where you don't get to open its source. Most of the documentation is a mess between outdated Aura components and their new lwc.dev site which has like 2% of the material you actually need.

If you want to use LWC outside of Salesforce to build a website, check out LWC OSS

Salesforce developed Lightning Web Components (LWC) as a fast, enterprise-grade wrapper around vanilla web components. LWC is built on the same HTML, CSS, and JavaScript that powers the web, so any analyzer for those languages can be applied here.