User:WikiMaster/WYSIWYG

Wiki Editing 2.0: Visual Editors, Wikis & You

• PDF: Editing 2.0: MediaWiki's upcoming visual editor and the future of templates - (Brion Vibber's wikimania2011 presentation.)

So pretty! Wikipedia articles can include rich formatting, beyond simple links and images to complex templates to generate tables, pronunciation guides, and all sorts of details.

So icky! But when you push that “edit” button, you often come face to face with a giant blob of markup that’s very hard to read. Here we can’t even see the first paragraph of the article until we scroll past several pages of infobox setup.

Dave's Note: Moved references to Extension:InlineEditor and What You See Is For The Win (WYSIFTW) / What You See Is What The Fuck (WYSIWTF) up here to the top of this list because these look like two of the most immediately available options that we might be able to successfully adapt to PortlandWiki until realistic / workable alternatives come along.

MediaWiki Extension:InlineEditor

Dave's Note: This might be the easier-to-use editor we go with, even though it's still in development stage, because:

1. It's testing well (so far).
2. The code looks clean and well-written.
3. The project is extensively researched.

• Extension:InlineEditor

InlineEditor is an editing interface that allows users to edit and preview elements in the page by clicking them.

Extension:InlineEditor Demo

Extension:InlineEditor/Proposal

Extension:InlineEditor/Prototypes

The different prototypes for the Sentence-level editing project are to illustrate the concept, and can be used as a starting point for an actual implementation. All the prototypes are briefly described on this page.

• PDF: SentenceLevelEditing_Usability_RuG.pdf - Usability script Sentence-Level Editing
• PDF: In-line Editing: a New Approach to Editing Wikis (Thesis)
• PDF: IN-LINE EDITING: A NEW APPROACH TO EDITING WIKIS (Presentation)

Category:Sentence-level editing (Wikimedia Commons)

• InlineEditor: Documentation ; SVN ; Code documentation ; Demo
• InlineEditor mailing list discussion
• Browse source code: Index of /trunk/extensions/InlineEditor

InlineEditor Demo On Telecafe

• Telecafe InlineEditor Demo

Requires Login

(Unfortunately, due to sporadic monitoring, Telecafe only allows folks with "email confirmed" accounts edit the InlineEditor Demo on Telecafe's wiki.)

WYSIWTF (aka WYSIFTW)

Dave's Note: It looks like Kotra (perhaps tentatively) favors Magnus Manske's WYSIFTW approach over Jan Paul Posma's InlineEditor extension. Reason? Simpler interface.

• WYSIFTW

WYSIFTW (formerly WYSIWTF) is a JavaScript-based tool originally written by Magnus Manske. Its primary purpose is to make it easier to edit Wikipedia articles, especially for people unfamiliar with the intricacies of MediaWiki syntax.

WYSIWTF (aka WYSIFTW) - The js code.

WYSIFTW: Documentation ; SVN ; Code documentation ; Demo

• WYSIFTW status
• WYSIWTF working demo

Additional WYSIWYG Research

• WYSIWYG editor

For the more technically inclined, wiki markup is a simple way of formatting a wiki page. However, many would-be users of MediaWiki are put off by what looks to them—rightly—to be code of any sort. These users are adjusted to publishing and editing in a more visually straightforward WYSIWYG (What You See Is What You Get) environment.

• “Wikipedia’s WYSIWYG Dilemma” (Wired)

From Article: (Wikipedia's) editing platform is intentionally designed to be complex so as to lower participation and thus make it easier to manage, and that if they open up the floodgates, "the site will probably come to a grinding halt."

• WYSIWYM

WYSIWYM is an acronym for What You See Is What You Mean, and refers to a paradigm for document editing. It is an alternative to the better-known WYSIWYG (what you see is what you get) paradigm, which displays the document on screen as it will be printed.

Wikipedia WYSIWYG

• Wikipedia WYSIWYG
  • Wikipedia WYSIWYG - wiki

Wikipedia WYSIWYG is a collaboration between GRNET and MediaWiki developers. The goal is to provide a better editing interface for Wikipedia. This will be done by evaluating existing approaches and improving them. Read more about the usability testing. The first step is to do usability testing with some of the existing approaches: InlineEditor, WYSIFTW, RTE and others (see below for details).

WYSIWYG Extensions

• Category:WYSIWYG extensions

FCKeditor (Official)

• Extension:FCKeditor (Official)

WYSIWYG

• Extension:WYSIWYG

The WYSIWYG extension enables a more intuitive editing of pages on a MediaWiki-based site. When this extension is installed, the tab 'Edit' in the command bar on top of every page leads directly in the wysiwyg editing mode. The WYSIWYG extension uses a special version of the CKeditor that outputs wiki text rather than the usual HTML that caused problems for MediaWiki integrations in the past.

RTE (Rich Text Editor (Wikia)

• Wikia's Community Test Wiki (RTE Demo)

Help:Rich text editor

This extension is enabled by default on Wikia.

svn.wikia-code.com/wikia/trunk/extensions/wikia/RTE

Other Editing Tools

wikEd

• User:Cacycle/wikEd

wikEd is a full-featured Wikipedia-integrated advanced text editor for regular to advanced wiki users. wikEd features syntax highlighting with code check and reference and template folding, on-page Show preview and Show changes, and advanced search and replace functions. Please check the wikEd help page for details. wikEd works under all web browsers except Internet Explorer and Opera.

• • User:Cacycle/wikEd help
  • User:Cacycle/WYSIWYG

This Essay in a Nutshell: Pure WYSIWYG is evil. Really. But we can learn a thing or two from it.

Semantic Forms

• Extension:Semantic Forms

Semantic Forms allows you to have forms for adding, editing and querying data on your wiki, without any programming. Forms can be created and edited not just by administrators, but by users themselves.

Wikimedia Foundation Planning

Wiki Text / Wiki Markup

• Wikitext.next

MediaWiki's markup syntax has grown organically since 2002, itself based on earlier wiki syntaxes going back to 1995. None of it's very consistent, and there are a lot of edge cases which tend to surprise folks.

1. Raw markup can look really ugly and intimidating to editors
2. Tables, templates, tags, etc have many unexpected boundary conditions, which makes some uses of these constructs hard to deal with even for experts
3. Lack of structure or standardization means that changes to the parser code can unexpectedly change those cases
4. Combination of edge cases makes round-tripping to HTML and back very hard, which has made it difficult to get rich text editing fully integrated

• WMF Projects

List of currently active projects being managed by the Wikimedia Foundation.

• Future

Wikimedia Engineering's key future-facing priority for 2011–2012 is creating a rich text editing environment, backed by a revamped, normalized, more consistent wikitext parser. The Wikimedia Foundation's 2011-2012 annual plan aims to "Develop Visual Editor. First opt-in user-facing production usage by December 2011, and first small wiki default deployment by June 2012."

• Future/Parser plan

Draft started here: http://etherpad.wikimedia.org/mwhack11Sat-ParserDraft

• wikimedia:2011-2012 Annual Plan Questions and Answers#What are the main increases in spending for 2011-12?

“Included in the spending increases for 2011-12 are: 1) Additional spending on technology that will include funding for the development of the Visual Editor, new editor engagement features, internationalization improvements…”

PortlandWiki WYSIWYG Discussions

• PortlandWiki Search Results: WYSIWYG