Roadmap for v3

[cesasol]

This is a list of goals to meet before releasing a stable 3 version:

• Improve the documentation and at least a spanish translation
• Windows compatible (Help needed)
• Be zeroconf and extendible through it's own api and exposing the markdown parser
• Allow default attributes to be set on the frontmatter ej. title
• Real async modules (this affects ssr more than a static build)
• Fully integrate with the new features nuxt2.0 and node 12
• Debugable configuration
• Better error reporting
• Document the code in order to simplify contributions and future development
• Improve the template with optional addons as examples
• Support multiple file types (json, yaml, markdown, html)
• Integrate the api configuration with nuxt itself while keeping it configurable
• Expose $content helper and it's constant like api endpoint through all of vue
• Keep the main features from nuxtdown:
  • Breadcrubms
  • Automatic table of content (TOC)
  • Isolated and global configurations
  • Allow for nested content and index files
• Improve on SSR memory usage

The following are the features that would be nice to have but are left for a future release 3.x

• Vuex integration
• Use sqlite for the content

All of the previous features are open to discussion and may be expanded to fit more use cases.

_{This question is available on Nuxt community (#c141)}

[renestalder]

@cesasol Just want to check in. Is there a plan of action for continuous development? Or do you recommend alternatives to nuxtent?

I really love how this module works and I would even help you to develop it further. I currently use a fork of this project, but all the forks state that the "maybe" get merged some day. You especially did quite some changes on the development branch, so I wondering, when these get released and the "don't use in production" line removed.

[joostdecock]

Guys, I should perhaps clarify my (lack of) involvement in this project. As you may or may not know, I'm using nuxtdown in production on freesewing.org, and that's how I got involved in the first place.

However, I've been working on a new frontend built on React/Gastby, and as soon as it's ready I will no longer have a stake in Nuxtent.

That being said, I think this is a very useful module, and you guys are doing great work 🥇

[TheAlexLichter]

@joostdecock I'd love to hear the reasons why you switched over ☺️

[joostdecock]

@joostdecock I'd love to hear the reasons why you switched over ☺️

We currently deploy about 2700 pages, and the vast majority of those are just embellished markdown.

We have a ton of documentation, we have blog posts, showcases from the community, 5 different languages, and other things that are more website than app.

For our needs, Gatbsy and the ecosystem around it felt like a better match.

[renestalder]

Maybe a bit off-topic here but keep Gridsome on the radar if you look for something similar like Gatsby for Vue.js.

That's also my next alternative after Nuxtent (maybe will desperately fork @joostdecock's Nuxtdown branch and try to fix some things but if this doesn't work, probably make the switch).

[TheAlexLichter]

@renestalder We really want to improve the "static" part of nuxt, especially when it comes to easier integrations.

I'm pretty sure that Nuxtent and the full-static mode are two points to start with but not the end of the improvements.

[TheAlexLichter]

@joostdecock Interesting! Thanks for the insights ☺️

[renestalder]

@manniL Thanks for the info. I somehow just would wish that the patches that are applied on one of the development branches now (especially for Nuxt 2.3 compatibility) would go into a patch release. I see that some refactoring is going on but I wonder if that is required for releasing some patches at this moment. It doesn't make much sense for me to now dig into the code to apply the patches for myself in my projects and at the same time, I don't want to hook in the development branch into my projects as there is a clear warning that nobody should use that in production.

[cesasol]

@renestalder I use it in production for many sites. It's just that I haven't had the time to keep documenting all that is going on, there is some progress to document and refactor all the code to make possible what @joostdecock does but with Nuxt and async components.

But with my team we are looking to keep maintaining this as well as possible but is not really our highest priority.

[cesasol]

@manniL I'm looking to keep track of this and add some ideas from my experience with nuxt.