greenwood VS content

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!

Nuxt is an appealing framework to work with, partly because of its robust module ecosystem. Popular UI libraries, headless CMS tools, and databases can be easily integrated with a single line of code. Among other third-party modules, Nuxt Image, Nuxt Content, and Nuxt UI are some of the official modules developed by the Nuxt team.

For reference also in the space of 'website from markdown':

* https://content.nuxt.com/ - JS, SSG and SSR

If you want to continue using markdown, nuxt 3 has a module, Nuxt Content - https://nuxt.com/modules/content https://content.nuxtjs.org/

Nuxt Content is what you’re looking for.

Then I recalled about Content. It's a file-based Headless CMS which use files of extension .md, .yml, .csv and .json a data layer for the application. And its MDC syntax is cherry on top. So I came with a plan to use .json files to handle project data. Basically, I'll just create a projects section using Content, put my projects in .json files, use the Querying functionality of Content to fetch them and populate the Components as needed.

I would argue that using something like Nuxt/Content[0]is even simpler. I create a new markdown file in my website’s local repo, write the content and commit if it’s ready for publishing. No need for the FTP step and version control is build in.

This setup is also completely free since the content lives on GitHub and my static site on render.com (but any static site hosting will work).

And since it’s Nuxt based, it automatically also supports more advanced features such as tagging, advanced queries and filtering.

Can only recommend it!

0. https://content.nuxtjs.org