The goal of Nuxtent is to make using Nuxt for content heavy sites as easy as using Jekyll, Hugo, or any other static site generator.

It does in two main ways:

1. By compiling all the data from markdown or yaml files based on configured rules.
2. By providing helpers for dynamically accessing this data inside Nuxt pages.

But, we didn't just want to make Nuxtent as good as a static site generator–we wanted to make it better.

So, along with that, Nuxtent also supports:

3. The usage of content files in both static sites and dynamic applications.
4. The usage of Vue components inside markdown files.
5. Automatic content navigation, between pages via path and within pages via anchors.

There you go: five reasons to give Nuxtent a try, and maybe even star and share it. 😏

Nuxtent's main focus was to integrate into Nuxt (otherwise, you're just building another Jekyll-like tool, with the same amount of mental overhead).

As a result, the API simple yet flexible. All you have to do is 1) configure the content and 2) fetch the files with the $content helper inside the asyncData method that is available in Nuxt pages.

Here's a basic example:

// nuxtent.config.js
module.exports = {
  content: {
    page: '/_post'
    permalink: ':year/:slug'
  }
}

// pages/_posts.vue
export default {
  asyncData: async ({ app, route }) => ({
    posts: app.$content('posts').get(route.path)
  })
}

If you're starting a new site, you can use the nuxtent-starter template.

$ vue init nuxt-community/nuxtent-template my-site
$ cd my-site
# install dependencies
$ npm install # Or yarn install

npm install nuxtent --save

Then, under nuxt.config.js install the module:

modules: [
   'nuxtent'
 ]

Documentation available at: https://nuxtent.now.sh/ (built with Nuxtent).

Have a site using Nuxtent? Fork the repo and add it to the list below!

• alidcastano.com source

• ency.now.sh source

MIT