Notice: The WebPlatform project has been discontinued when the Stewards partnership agreement ended in September 2015. This site has been frozen, and the assets we have created will remain.


Minimal Viable Product

This table tracks the tasks we want to complete before we launch and which ones are required to create a minimal viable product (MVP). Current categories for tasks are: Content, Marketing, and Infrastructure.

CategoryTopicOwnerStatusTarget Time (weeks)NoteRequired
InfraWiki SetupRyanDoneRequires MediaWiki componentyes
MarketingSkinMarketing taskforce.See Designyes
ContentContent MigratedContent taskforce.See Content Migration. Requires MediaWiki component (some)yes
ContentContent ArchitectureContent taskforce.See Content Architecture.yes
ContentOriginal_ContentContent taskforce.See Original Content
ContentMobilize the MDN community to free up the content(Janet) MozillaGet permissions from authors to migrate content from CC-BY-SA to CC-BY. Move down to content taskforce.
InfraTwitter account @webplatformDougDoneyes
MarketingTwitter policyMarketing taskforce.Will be done by marketing teamyes
InfraIRC channel #webplatformDougDoneNeeds to be documented where it is.yes
InfraWeb client (IRC)DougDone (no skin)Requires MediaWiki component. Needs to be documented where it is
InfraLogging bot (IRC)DougRequires MediaWiki component
ContentCommunity OrganizationContent taskforce.See Community Organization. See Art of Communityyes
ContentFlagsContent taskforceSee Page Structure Requires MediaWiki componentyes
InfraCommentsDougRequires MediaWiki componentyes
ContentClear URL structureContent taskforcelargely doneSee below.yes
???Easy page creationAlexSee Page Structure
InfraInternationalizationDoug (with support of Ryan, on behalf of W3C I18n team)We need to have a mechanism, at least a plan for it, in the beginning. Requires MediaWiki componentyes
InfraLanguage switchingRyanRequires MediaWiki componentyes
InfraSandbox (live viewer)Lea
InfraForums (Q2A)Doug*Requires SSO, Skin. Will this hold up the launch? Needs discussion first.yes
Content?Teaching materialsChrisMoodle? Later
InfraFederated Login featureDoug*Requires MediaWiki component
InfraRequired email address for accountsDougDoneDoesn’t work as well as necessary.yes
InfraSingle sign in (SSO)(Doug*)Case by case basis. This captures that the blog and wiki need to have their login integrated.yes
InfraBlog(Doug)Requires SSO, Skin. Requires MediaWiki componentyes
InfraEmail feedback account set upDougOthers: Twitter, blog, IRC, forums, comments in topicsyes
ContentHow to use this siteLea & Dougyes
ContentHow to help (includes migrating MDN)Janet. (In content taskforce)yes
ContentPrivacy policyWendyyes
InfraMetrics and trackingEliot (and Doug)(Google analytics? Adobe? Piwik?) Create Wiki page with policy about collecting and sharing metrics.yes
Metrics policyWendyyes
InfraAccessibilityChrisThis needs to be broken down into separate things. Like ensuring the site is accessible, and content on accessibilityyes
InfraIssue tracker (bugs)EliotDoneIn W3C bugzilla. See
ContentTask-oriented TutorialsContent taskforce.Small tutorials about how to, say, center content on the web platform. CDNDoug*, Ryan Lane to do actual work.yes
InfraSystem backup of siteDoug*, Ryan Lane to do actual work.yes
InfraDeployment script for siteDoug*, Ryan Lane to do actual work.yes
ContentCopyrightWendyNeed to approve the terms by which people can use the content on WPD. Start with the text on the W3C Wiki.yes
???Figure out list of “early preview” peopleAlexIdeally include people who will actually do work. Maybe give some of the people with invites a small number of invites? Have a gatekeeper of the actual signups.yes
???Finalize license of web platform logoWendy (with Alex to help)
MarketingOrganize pre-launch hackathonAlex (Coordinate with Eliot)Likely on west coastyes
MarketingOrganize post-announcement community engagement (and hackathon?)Peter (?)yes


These are broken out from the top-level table.

Content Migration

TOPIC Subtopic Owner Status Note
Figure out locations for all articles Chris Blocked on finalizing the URL structure. First step is to break up the list of articles to set up. Then assign people to take responsibility for each section.
Migrate test article from MSDN Doug\*, work will be done by Yaron
Migrate existing articles Doug\*, work will be done by Yaron
Figure out concrete MDN licensing flow New pages Janet
Merging content in Janet
SA License Janet A manual attirbution block at bottom?
### Content Architecture
Final URL structure/ content organizationChris
Create stub articles to fill out entire hierarchyChris
Language dropdownDoug*, work done by Yaron
Semantic mediawiki queries on listing/API summary pages to pull in all relevant attributesAlex*, work done by Yaron
Placement of stewards’
Indicating standards track APIsAlexJust figuring out how to use tags/flags

Original Content

Comprehensive list of content neededChrisBased on Chris’ [earlier draft of the same]. Ideally a roadmap of all the content we’ll want to fill out over the years.
Home pageLea
Section header pagesChrisPages like docs/css landing page, but also sub-pages like docs/css/properties. Some of these can be somewhat auto-generated (list of sub-pages, maybe like include tutorials). Will need some templates for it.
Marketing pagesWai (marketing taskforce)
Create content for steward pagesUp to each steward

Page Structure

TOPIC Subtopic Owner Status Note
Inspect MSDN/MDN content and make sure it's compatible, and how we want this site's content to end up Make page mock-ups Doug ( with help from Lea) Blocks on finalizing the list of all page types (next row). See the list of page types in the 6 rows below.
Ensure we have all page types listed on [WPD:Architecture](/WPD:Architecture) Lea, with help from Doug Make sure to review the whole content architecture. Make sure to include all page types, including ones that don't have templates.
Make templates Alex
Make import script Yaron
Figure out how to map existing content into the templates or page structure Yaron Chris figuring out where articles fit, Alex figuring out how the content fits in, and Yaron implementing
Flags Making sure we have all of the flags we need. Alex
Finalize flags. Alex
Implement flags that can take a string value as well (e.g. merge candidate) Alex
Multiple articles to display end state Simple CSS Property N/A
Complex CSS Property (CSS transforms) N/A
Guide article (Canvas) N/A
Large object: Document (lots of methods) N/A
JS object or data type: Date N/A
Regular Expressions N/A
Figure out compatibility table design How it looks CJ
How it gets populated Alex
How we maintain it Alex Just in the best practices / style guide. In the long run may want to have it automated.
Templates/Properties/Categories Alex Created based on our content organization
Create page forms for all page types. Alex Page forms should transclude short summaries about best practices for each section, with pop-up links to more detail.
"New page" experience New page experience defined Alex
New page experience defined for i18n Doug
New page experience implemented Alex
### Community Organization
Tighten up pillars docAlex
Strengthen the overall guide (practical counterpart to pillars)Alex, b/c he knows what this one means.
Beef up “Getting Started” guideDoug / Lea
Create style guide for code examplesEliotIn progress
Finalize the Manual of Style (including sub pages)Alex
Figure out about badges and community recognitionPeter Lubbers


Handled by the marketing taskforce

TOPIC Subtopic Owner Status Note
Design Attribution block final styling CJ [Open]([Closed](
Links CJ Styling different for intra-page links, intra-wiki links, external links, and links to non-existing pages
Note callouts CJ [Example](
Language dropdown in header CJ [Open]([Closed]( Shows current language; allows user to select new language; also allows authenticated user to create new translation
Search Box alignment CJ Done Size and position should align with other visual elements
[CSS Prefix](/Template:CSS_Prefix) callouts need to be styled CJ [Example](
Design style guide CJ [File:Web-Platform-Style-Guide-web-1.pdf](/File:Web-Platform-Style-Guide-web-1.pdf) Provides guidlines for creating sub-properties like blog, IRC, etc.
Compatibility table styling CJ [Example]( For an example, see [css/properties/font-size](/css/properties/font-size)
Stewards Page Design CJ [Example]( Extensible to work for each steward, unique page for each
Landing Page Design CJ [Examples](/WPD:Design/Landing)
Static Page Design CJ [Blog Example](

Q/A Example

Styling for language tags in examples CJ [Example]( See [css/properties/font-size](/css/properties/font-size) for an example.
Community Badges
Skin External attribution blocks use something equivalent to details/summary elements Doug\*
Make sure bolding looks right on Chrome Doug\*
Section editing Doug\*
Username dropdown Doug\* Needs down-arrow; item highlight; item should be whole area, not just text
[Editorial](/Template:Editorial) callouts should only show for logged-in users (via CSS) Doug\* This should probably be as simple as having a `.editors-only { display:none}` rule in the CSS file, so we can create new templates that are hidden from readers easily.
Edit / watch button colors Doug\* Edit button should be strongest
Syntax highlighting of examples with prism.js Lea Will need to modify [Template:Single\_Example](/Template:Single_Example)
Style the standardization flag. Doug [Template:Standardization\_Status](/Template:Standardization_Status)