Improving ddoc

[via Digitalmars-d]

On Thursday, 1 January 2015 at 00:44:33 UTC, Adam D. Ruppe wrote:
> I'd actually prefer to focus more on ddoc's unique strengths - 
> that it understands the compiler's scoping rules.

If I understand this correctly, it seems very compelling to me. 
Would it be an option to

1. Work on ddoc (as it is now) to be even closer to the compiler 
(e.g. scoping rules)
2. Add a carefully selected markdown on top of proper ddoc (e.g. 
use ddoc instead of html as fallback)
3. Provide ddoc macro definitions to generate all kinds of output

This would help in several ways

1. The fully functional ddoc system that can do books remains 
available. There is use for it.
2. The code documentation could be much more lightweight (but 
still have the full ddoc macros available if needed)
3. Generating to pandoc or the like. There are converters out 
there.

If any of this is of any value, I am happy to help to make it 
happen.