-
Notifications
You must be signed in to change notification settings - Fork 22.5k
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
API Reference method page template - add description #36185
API Reference method page template - add description #36185
Conversation
Preview URLs (comment last updated: 2024-10-06 20:50:08) |
...en-us/mdn/writing_guidelines/page_structures/page_types/api_method_subpage_template/index.md
Outdated
Show resolved
Hide resolved
|
||
_Detailed description of how the method behaves_ | ||
_Section omitted if an introductory paraphgraph (or two) at the top of the page are sufficient._ | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
_Tips and quirks about the method._ | |
I always wonder if quirks, notes, warnings, and tips should be in the intro section or the description section.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Description, I'd say.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, but I don't think we need to mention this specifically - the would clearly be part of an extended description.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
...en-us/mdn/writing_guidelines/page_structures/page_types/api_method_subpage_template/index.md
Show resolved
Hide resolved
…api_method_subpage_template/index.md Co-authored-by: Onkar Khadangale <87750369+OnkarRuikar@users.noreply.github.com>
Thanks for the reviews gents. I'm merging the fix, and ignoring the extra suggestions in order to keep things simple |
This adds a "Description" heading to the API ref page template for methods.
FWIW I think we should not be too concerned about this - if you can create an adequate description in 3 or 4 paragraphs up the top of the page then that is better for users than having to navigate down to another section for detail. On the other hand, if it is a much bigger section, it makes sense to push it below the fold so people can jump to the detail earlier.
However if this exists it should be in this position.