You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
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
The text was updated successfully, but these errors were encountered: