I decided to transcribe these notes because on Friday, James Forrester asked me, “What do you expect to get out of the strategy retreat next week?”
My answer was…long. I won’t bore you with the details. Continue reading
I feel somewhat responsible for putting James Forrester on the hot seat concerning this article as I was the one who asked him to take out time from his busy schedule to explain some of the challenges faced by the team concerning the project and manage expectations somewhat concerning the release.
I hope it is clear from the post that the VisualEditor project has to overcome many “firsts” to become a reality. Some of the ones mentioned include:
- The criteria to support 290 languages is beyond the scope of support of existing software.
- The VisualEditor UI needs to be programmable in such a manner that “free form” HTML editing cannot be permitted unless those edits can be synced with an internal, client-side “data model.”
- The VisualEditor needs to leave room for extensibility in all fronts to adapt to the extensible nature of current WikiText capabilities like transclusions and templates.
- A two-way representation needs to be created out of wikitext to HTML back to wikitext. This cannot be emphasized enough since before the [parsoid project], it was actually unclear if this was even possible.
- In both the parser and in all points of the VisualEditor, edits must be made in a manner that only manipulates the areas intended by the editor so was to not introduce “dirty diffs”.
- All of this must be done in a forward thinking transactional manner to allow things like real-time collaboration, micro-edits, and the ability to walk through actions.
[parsoid project]: http://www.mediawiki.org/wiki/Parsoid “Parsoid—MediaWiki” Continue reading
You tell that other boy, not to touch the woodwork…