Move content to Docusaurus

[shawntabrizi]

This is just a suggestion, but it may make sense to have this content migrated to Docusaurus.

@4meta5, are there advantages to using RustDoc for these recipes?

[4meta5]

Just saw this, odd that I wasn't notified earlier. I'll look into migrating to Docusaurus this weekend. I'm reorganizing a lot of the content and using the module-template to yield compileable code samples.

I guess the main advantage of using mdbook is that I'm comfortable with it.

You can also build custom backends with mdbook which might be useful in the future, although I have not yet explored this...

[shawntabrizi]

Well before you spend time on the weekend I think it would be good to come up with a final plan. For example, if you are reorganizing content to use the module-template, then it makes sense to use rustdoc right?

And have all the comments and teachings be inline to the code?

Otherwise, I saw that your project is just a bunch of MD files, which should be able to just copy and paste into docusaurus.

[4meta5]

I would rather reorganize the content to use the module-template so I'll do that with rustdoc. I think this is the right approach.

[4meta5]

todo

• get compilation on all existing recipes and organize them into separate folder
• add doc comments and render with rustdoc
• add unit tests?

[4meta5]

I think the current approach (mdbook + kitchen) makes sense. I'm closing this because mdbook works and we can provide a kitchen with compiled examples. I'll open another issue for showing the recipes on the README along with whether the builds work (via travis) AND putting links to the compiled recipe in each section.