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

API Reference method page template - add description #36185

Merged
merged 2 commits into from
Oct 6, 2024

Conversation

hamishwillee
Copy link
Collaborator

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.

@hamishwillee hamishwillee requested a review from a team as a code owner October 4, 2024 04:10
@hamishwillee hamishwillee requested review from chrisdavidmills and removed request for a team October 4, 2024 04:10
@github-actions github-actions bot added Content:Meta Content in the meta docs size/s [PR only] 6-50 LoC changed labels Oct 4, 2024
Copy link
Contributor

github-actions bot commented Oct 4, 2024

Preview URLs

(comment last updated: 2024-10-06 20:50:08)


_Detailed description of how the method behaves_
_Section omitted if an introductory paraphgraph (or two) at the top of the page are sufficient._

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
_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.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Description, I'd say.

Copy link
Collaborator Author

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.

Copy link
Contributor

@chrisdavidmills chrisdavidmills left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

…api_method_subpage_template/index.md

Co-authored-by: Onkar Khadangale <87750369+OnkarRuikar@users.noreply.github.com>
@hamishwillee
Copy link
Collaborator Author

Thanks for the reviews gents. I'm merging the fix, and ignoring the extra suggestions in order to keep things simple

@hamishwillee hamishwillee merged commit c56a907 into mdn:main Oct 6, 2024
8 checks passed
@hamishwillee hamishwillee deleted the page_structure_method_desk branch October 6, 2024 20:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Content:Meta Content in the meta docs size/s [PR only] 6-50 LoC changed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants