Closed Bug 1120964 Opened 9 years ago Closed 6 years ago

Split display property into subpages

Categories

(Developer Documentation Graveyard :: CSS, enhancement)

Product:
Developer Documentation Graveyard
Component:
CSS
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: teoli, Assigned: me, Mentored)

References

(
URL
)

Details

With the years, the possible values of display: have seen a dramatic increase. This lead to a page that is barely usable.

In order to have better information, better examples, and easier to read compat tables, we need to have one page per display type.

Subpages should be named display: xyz and the slug be /en-US/docs/Web/CSS/display/xyz.

The structure should be the classical property structure, slightly adapted as the syntax is a tiny subset of the display syntax.

If anybody is interested, I can mentor him or her. It is a significant task though, and you shouldn't be afraid of writing basic examples around tables, flexbox, and ruby.
Whiteboard: [Mentor=:teoli]
Mentor: jypenator
Whiteboard: [Mentor=:teoli]
Severity: normal → enhancement
OS: Mac OS X → Unspecified
Hardware: x86 → Unspecified
Summary: Split display property in sub pages → Split display property into subpages
This has been done by Rachel Andrew as part of https://github.com/mdn/sprints/issues/456 (specifically https://github.com/mdn/sprints/issues/456#issuecomment-421581354)
Assignee: nobody → me
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
See Also: → https://github.com/mdn/sprints/issues/456
Yep, kudos to Rachel for the work!

Hopefully, browser implementors jump on this soon and allow to specify the multi-keyword values!

Sebastian
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.