API Improvements

[s-ludwig]

Makes the entity module API @safe to make it better suited for web app embedding and adds more fine-grained access to Ddoc section contents.

[WebFreak001]

rest LGTM

[WebFreak001]

unused or undocumented public API

Should this rather return a helper struct that you can foreach on to be more idiomatic? (e.g. opApply)

[WebFreak001]

unused or undocumented public API

[s-ludwig]

@WebFreak001: I was focused on making the additional information available consistently with the existing code, but you are right that the current API is not very good. My suggestion for getRawSectionContent would be to instead make Section public and replace getRawSectionContent with a simple sections() getter property and plan for eventually replacing the renderSection* methods with Section.render().

I'm not sure about the opApply/helper struct route for renderParameters, maybe this can eventually also be replaced with a simple parameters() getter property that returns a new parameter struct type, which then also has a render() method. Since there are interactions with the other section related functions to consider, though, I'd really like to postpone a deviation from the existing API structure until there is a clear picture of how a better API would look overall.