879001 - UX: Docs Templates Tracking Bug

Status: RESOLVED INVALID

(developer.mozilla.org Graveyard :: General, defect, P2)

Description

[Holly Habstritt Gaal [:Habber]]

What problems would this solve?
===============================
Update current template structure and styles. 


Who would use this?
===================
MDN docs readers and editors.

What would users see?
=====================
Readers would see a more consistent style and organized content across MDN.

Editors would see a better interface and flow for adding and managing MDN content. (ie: adding and reviewing pages, history, etc)

What would users do? What would happen as a result?
===================================================
Readers would clearly distinguish page types from one another and find our content organized and readable (and as a result, trustworthy as well). 

Editors will find contributing to MDN easy to use and come back to contribute. They will also be more likely to contribute to a tool that they know users enjoy.

Is there anything else we should know?
======================================
We should provide consistent ways and styles for adding content like code samples, images, videos across MDN docs. If users are creating their own style and method of doing so with code, our templates no longer look like templates and appear very inconsistent. By creating a consistent look and feel and supporting the needs of the editors and the content they want to add to the docs, MDN will be a more readable and organized resource.

Comment 1

[Holly Habstritt Gaal [:Habber]]

List of page types to redesign, in order of priority:
1. Template master (includes elements that can appear across all page types such as breadcrumbs, toc, quick links, tags, titles, etc)
2. Article Page
3. Main API page
4. Reference Page
5. Index Page (TOC page)
6. Landing Page