Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docgen: general improvements to Markdown format #14290

Closed
oandregal opened this issue Mar 6, 2019 · 1 comment
Closed

docgen: general improvements to Markdown format #14290

oandregal opened this issue Mar 6, 2019 · 1 comment
Labels
[Tool] Docgen /packages/docgen

Comments

@oandregal
Copy link
Member

oandregal commented Mar 6, 2019

This is to add requests to improve formatting that we should apply in batch to all packages, once the PRs at #14227 are landed.

TODO

@oandregal oandregal changed the title Improve docgen formatting docgen: general improvements to Markdown format Mar 6, 2019
@oandregal oandregal added the [Tool] Docgen /packages/docgen label Mar 6, 2019
@aduth
Copy link
Member

aduth commented Mar 6, 2019

Couple other thoughts:

  • The generated function output looks very run together, and it's hard to identify where one function's documentation ends and the other begins. Additional formatting like using code for titles could help this by serving as a sort of visual mark. Line separators (---) may be another option, though perhaps too severe a division.
  • Would it make sense to include a leading table of contents for the functions? Just a list of links. I could see a counter-point being that it might be more on the rendered context to make sense of the semantic structure of the markdown document and build its own table of contents if applicable (i.e. the WordPress Developer Handbook page or GitHub itself generating a table of contents)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Tool] Docgen /packages/docgen
Projects
None yet
Development

No branches or pull requests

2 participants