Project:VisualEditor testing/Roadmap


 * This is not set in stone, just an outline of our current thinking for the time being.

Our current VisualEditor/Parsoid development priorities (as of 2012-08-21) for the December release are:

Things above this line are "drop-dead" criteria for release in December 2012.
 * 1) Round-tripping (i.e., what you edit is what gets saved, and what you read is what you see when you click 'edit')
 * 2) Alienation (i.e., if we don't yet support editing of a node type, it instead displays as a block that you can move and remove but not alter, and adjusts the wikitext appropriately on save)
 * 3) Productionisation (i.e., it doesn't fall over at scale)
 * 1) Getting what we have working perfectly &mdash; (paragraphs, headings, pre-formatted paragraphs, OLs, ULs; italics, bold, links)
 * Lingering issues with inline nodes and whitespace preservation
 * 1) API-ing the VE/Parsoid stack (so they can be extended by new developers without them having to learn the whole code base)
 * 2) Adding support for new node types:
 * 3) Images (inclusion inline and as thumbnails)
 * 4) DLs
 * 5) Categories