We are currently using Docusaurus for our documentation. Mkdocs is a cleaner solution. You should pull the https://github.com/lamden/docs repo into your local IDE and compare the master branch with the dev-mkdocs branch to see the work that has been started.
The documentation should be reformated to look more appealing and follow a standard presentation of the APIs.
You do not need to rewrite any of the information, just reformat the Markdown and separate each project into its own mkdoc project.
Developers must reach out to @stuartf on Telegram before starting the project.
We are currently using Docusaurus for our documentation. Mkdocs is a cleaner solution. You should pull the https://github.com/lamden/docs repo into your local IDE and compare the
master
branch with thedev-mkdocs
branch to see the work that has been started.The documentation should be reformated to look more appealing and follow a standard presentation of the APIs.
You do not need to rewrite any of the information, just reformat the Markdown and separate each project into its own mkdoc project.
Developers must reach out to @stuartf on Telegram before starting the project.