0.2.15

• Fixed component naming for imports error.

Announcing Nuxtent

Changed name and package from @nuxtjs/content to nuxtent.

New features:

• Use vue components inside markdown files with @[pathToComp](compProps) syntax.
• Nuxtent now uses serverMiddleware to load content data so that it is not all bundled together.
• Added nuxtent-body component to faciliate rendering of content.
• Can use the content in dynamic site, using app.$content helper or static site using ctx.payload.

Major changes:

• Config file name changed from nuxt.content.js to nuxtent.config.js.
• Content configurations go under content property, which now either access an object for route level configurations or an array if configuring multiple content types under nested directories. Both options are not allowed due to endpoint conflicts.

Use markdown content with Nuxt.js

Key benefits

• Automatically parse all content files
• Full control over the content's routes URL structure
• Easily request the data via helper methods injected into app instance

** Based on the constraints mentioned in #4, Nuxt content does not yet compile markdown files to Vue components.