legacy-modules VS content

Checkout the nuxt toast module. Makes it super easy to report errors in a ux pleasing way. https://github.com/nuxt-community/community-modules/tree/master/packages/toast

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

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

Anyone able to help me out with this? the Docus theme is nice but mostly trying to use the Nuxt Content functionality to render a static site.

NuxtJS has a Content module that provides CMS functionality. It's file-based, so I write an article in markdown, commit it to source control, and it is published to the site.