Decide section order for page types with split or unclear majorities
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- html, markdown
- Domain
- documentation
Research direction
Start by comparing the section order across the MDN pages in the html-attribute, landing-page, mathml-attribute, and learn-module-assessment types. Record the competing orders and propose a consistent editorial order for each type; done means each type has a documented decision that can be applied consistently to its pages.
Written by the indexing model from the issue text.
Description
MDN URL
https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Global_attributes/popover
What specific section or headline is this issue about?
Section order for html-attribute, landing-page, mathml-attribute, and learn-module-assessment.
What information was incorrect, unhelpful, or incomplete?
These page types don't have a clear majority order, so pages of these types can't be checked consistently. For example, on html-attribute, "Values" comes before "Description" on 2 pages and after it on 1. On landing-page, "Guides" comes before "Reference" on 7 pages and after it on 3. On mathml-attribute, 2 of 8 pages are out of order, and on learn-module-assessment, 1 of 58 is.
What did you expect to see?
An editorial decision on the order for each type, so the rest of each type can follow it.
Do you have any supporting links, references, or citations?
No response
Do you have anything more you want to share?
No response
- Dominant language
- Markdown
- Stars
- 11.1k
- Forks
- 23.3k
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 187
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from mdn/content
-
Content:WebExt needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
CSS Custom Highlight API: mention StaticRange for highlights that outlive DOM changesPossibly taken @abdul-karim-mia claimed this 4 days ago. OpenContent:WebAPI help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Content:Meta needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
can `name` of objects in `webRequest.HttpHeaders` repeat?Possibly taken @Ashish-CodeJourney claimed this 2 days ago. OpenContent:WebExt
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
mdn/content#46472 · 1 comment ·
Maintainers usually reply within 1 day
-
`filter` creating a containing block unmentionedPossibly taken @Ganeshguru5 claimed this 4 days ago. OpenContent:CSS
Difficulty 1/5 Under an hour Newbie friendliness 75/100
mdn/content#46414 · 2 comments ·
Maintainers usually reply within 1 day
Similar issues
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
molgenis/molgenis-emx2#7059 ·
Maintainers usually reply within 1 day
-
sync-en
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
needs-format
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Niko1221/Strata#6251 · 1 comment ·
Maintainers usually reply within 5 days
-
area: plugins documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
CatVinci-Studio/Textus#727 ·
Maintainers usually reply within 1 day