Should we migrate our Jekyll site to Docusaurs?

[stijnmoreels]

The Tech Radar, Arcus, Academy all use Docusaurus, as was proposed by the Frontend team for easy versioning and minimal frontend files that helps non-frontend developers to solely focus on writing markdown.

Should we therefor migrate our currently Jekyll site to a Docusaurus one?

[stijnmoreels]

@THMKAE, would this be a big chunk of work, or would this migration be fairly easy? All documentation is too in Markdown and hosted on Netlify. Only the search - on a private repo - I'm not sure of. Algolia might not be free, in that case?

CC @GoutsmitSam

[THMKAE]

The migration would not be the biggest part I guess, it's still going to take a couple hours / days to get it to work, depending on edge cases in the MD files that may not be supported by docusaurus or behave differently.

Comparing the minimal frontend files that are required, I don't think Jekyll is that much of a difference, if I look at this repo, it maybe even has less (or I might not be aware, only did a quick glance).

But it is probably the versioning you are after, in that case I would say, yes, it is a good idea to do a migration. Don't know if Jekyll has any or if you kept some of the old versions?

The search will not work on a private repo/site, so you'll have to use other search plugins which are not as powerful but can still get you somewhere. For example: https://github.com/cmfcmf/docusaurus-search-local

[stijnmoreels]

Ok, I'm already looking at the unsupported files so that we can get that out of the way before a possible migration - are improvements nonetheless.

Thx! Also for the plugin, we can have a look. Yes, my most concern is indeed versioning, as we currently delete older versions, while still providing support for them.