As engineers, we learn from the very beginning that bundling too many things together is bad. Be it writing a huge function or a class file, having thousands of lines. The same holds true for non-technical aspects such as project documentation, project tickets, etc.
I have been writing my projects' documentation as code for some time now and have recently discovered Mkdocs and its framework Mkdocs Materials.
It allows you to quickly and effortlessly generate your documentation as a website.
The large number of themes and plugins can help you add tons of functionality to your site, and the results look very professional.
* Disclaimer: When talking about DDD in this context, I mainly mean the use of an expressive and rich model.
During my career as a web-developer, I have noticed a repeating antipattern related to front-end code. For some reason most of the best practices that we usually use on the backend code are rarely applied in the front. This looks especially true for DDD and TDD principles.