Closed fharper closed 3 years ago
@bidoubiwa Yes, exactly! Versioning is not super helpful right now, but it is a must-have for the documentation after we hit v1.0.
Before we seriously consider switching to Docusaurus or a similar tool, I'd like to test out the Vuepress versioning plugin I found. I'm still not sure if it will work for our use-case.
Repo: https://github.com/appcelerator/docs-devkit/tree/develop/packages/vuepress/vuepress-plugin-versioning Docs: https://titanium-docs-devkit.netlify.app/guide/versioning.html
I looked at it in the past. It has not a lot of star, doesn't look to be maintained a lot but it seems it has evolved in the previous month. Except from this option I did not find any other plugin. We still should try at least to make it work.
If it does not work
The other solution would be to create an in-house option but this should require some thought. It is not clear how we can manage that the most efficiently possible.
Does Docusaurus provide an easy solution for that?
@tpayet @qdequele @eskombro Could you give your opinion on the matter, or do you have any idea on how to handle this issue?
Does Docusaurus provide an easy solution for that?
@bidoubiwa Yep, it is one of their main features. https://docusaurus.io/docs/en/versioning
My proposition is: we will certainly change the documentation render engine with the new version on which the designer and the front end developer will work. We will certainly use Docusaurus. So, during the beta of the v1, we will also have the ability to test the beta of the new documentation. We could use a different subdomain like beta-docs.meilisearch.com. Like Docusaurus already have a versioning feature, after this change, we will be able to use it.
We concluded that Appcelerator's versioning plugin for VuePress does not have enough active maintainers or support for us to use it comfortably with our docs. Instead, we will go forward with Docusaurus.
What do you mean by that? Do you want to keep a documentation version for every MeiliSearch release? Like quentin described in this issue : https://github.com/meilisearch/documentation/issues/197 ?