The Future of Template Editing?

From MWStake
Revision as of 09:39, 12 May 2015 by Chris Koerner (talk | contribs) (Created page with "{{Blog Post |title=The Future of Template Editing? |tags=VisualEdtior, Templates, Editing, Forms, |author=Chris Koerner }} I had a chance to play with the latest version of [h...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

by Chris Koerner on 12 May 2015 10:39 (EDT)

Tag.png Tags: Editing, Forms, Templates, VisualEdtior

I had a chance to play with the latest version of VisualEditor and was really impressed at how far template editing has become. For those of you who may not be familiar with VisualEditor, it uses an extension called TemplateData to define the fields and their options for editable templates. This way VisualEditor presents and easy to use interface - not too dissimilar to Semantic Forms.

The TemplateData tag is basic JSON and the documentation on the extension page is fairly comprehensive. You can define default text, types, required fields, and other common form-driven input options.

Here's a demo where I edit a Wikipedia page with VisualEditor and then modify fields inside of the inbox using TemplateData.

<html> <iframe width="420" height="315" src="https://www.youtube-nocookie.com/embed/JbVN5BapFEw?rel=0" frameborder="0" allowfullscreen></iframe> </html>

What do you think? Could a future version of Semantic Forms work within VisualEditor? Do you use TemplateData on your own wiki? Drop me a note on the Talk page.

Retrieved from "https://mwstake.org/w/index.php?title=Blog_Post:6&oldid=342"