Though not ideal, the Developer Handbook is now in Markdown until we can come up with a workaround, like a wrapper for Hugo to support Asciidoctor. Ultimately, we should consider migrating to Jekyll, which wouldn't be very difficult, and supports Asciidoctor with far less issues and has a bigger community.
There are some CSS issues with the static files that already existed before, and I'm working on a fix for that. Still need to make some minor changes and add callouts we are missing from Asciidoc. Here are some screenshots of how it looks when the CSS is rendered correctly:
However, as mentioned, there are some CSS issues and also mobile-compatibility issues that should be addressed in a future PR. We should also work on SEO-related enhancements and a sticky TOC, time-permitting.
Though not ideal, the Developer Handbook is now in Markdown until we can come up with a workaround, like a wrapper for Hugo to support Asciidoctor. Ultimately, we should consider migrating to Jekyll, which wouldn't be very difficult, and supports Asciidoctor with far less issues and has a bigger community.
There are some CSS issues with the static files that already existed before, and I'm working on a fix for that. Still need to make some minor changes and add callouts we are missing from Asciidoc. Here are some screenshots of how it looks when the CSS is rendered correctly:
However, as mentioned, there are some CSS issues and also mobile-compatibility issues that should be addressed in a future PR. We should also work on SEO-related enhancements and a sticky TOC, time-permitting.