Meta:FormWizard/pt

• Deutsch
• English
• português
• čeština
• 中文
• 한국어

FormWizard is a gadget that provides a structured, step-by-step workflow for creating a new wiki-page and populating it with content.

The Form Wizard is translatable and highly configurable, and can be used to create new pages or update existing ones. Enter information into form fields to define and set template parameters, create and populate new sections, or add hidden HTML comments. You can see it on action at Subsídios:IdeaLab/Ideias .

The Form Wizard simplifies the process of creating new pages within a portal that conform with a pre-specified template, such as Grant proposals, IdeaLab ideas, and Learning Patterns. Clicking a button on an existing wiki page invokes the Wizard, a series of dialog boxes in which the user enters content that will appear on the resulting page.

The Form Wizard provides many standard webform elements, such as single- and multi-line text boxes, dropdown menus, radio button lists, and image previews. It provides validation for certain element types.

The location of the resulting page, the page sections and infobox parameters, and all the fields in the form are configurable. The form is created dynamically from a config file, eg Project:FormWizard/Config/IdeaLab . The Form Wizard interface text can be translated using the Translation extension, and logged-in users will see instructions in the language they have specified in their account preferences (if a translation exists in that language).

This tool was developed as part of IdeaLab April August 2014 sprint

The FormWizard is currently enabled on MetaWiki, English Wikipedia, Wikidata, and TestWiki

To install the FormWizard on a Wikimedia wiki, perform the following steps.

Setting up a new Wizard on a monolingual wiki (like English Wikipedia) involves two steps:

Most Wikimedia projects will want to use the monolingual version of the FormWizard.

The multilingual version of the FormWizard works with the Translate extension. Any string value in the configuration file can be wrapped in translation tags, and the file can be marked for translation, allowing the wizard to display instructional text in a user's interface language (if a translation exists).

See an example of a translated config file. One major difference in calling a multilingual version is that it will expect an English version of the config file using an /en suffix for the page title (e.g.Meta:FormWizard/Config/IdeaLab/en, not Meta:FormWizard/Config/IdeaLab), so be sure to create this translation page either manually or using the translate extension. Importantly, updating the configuration page for a multilingual file requires marking the page for translation after editing the file. Without marking the page for translation, the associated pages will not be updated, and no changes to the interface or operation will be occur.

The primary purpose of the Form Wizard is for creating new wiki pages with a common format. Information that users enter into form fields (which you specify in the configuration file) will be published on the created page. You can also specify other content to be outputted on the created page by default (the user doesn't have to enter anything), such as section headings, <!-- inline comments --> and infobox parameters and values.

Below is an example of the 'config' sub dictionary for the first step of the IdeaLab wizard workflow.

You can use the FormWizard to expand a page as well. The expand feature allows you to:

To use the FormWizard to expand a page:

The FormWizard can be used with any infobox template, as long as the template is in the top section of the page. However it is designed for use with Probox (the grants infobox). It also plays well with the AddMe gadget.

Some notes available at this etherpad

The configuration for each grant type is maintained in a separate file, eg IdeaLab would be formsGadgetConfig/IdeaLab. Each config file has broadly two kinds of sub dictionaries. One called 'config' and the others called 'step-n'. Where n is the nth step in the form. At any given point of time only one step is visible. The user can navigate forward or backward. This is configurable too.

Below is an example of the 'config' sub dictionary

'config':{
"post-edit":"Thank you for creating your idea! Visit the toolkit page (linked at the bottom of the infobox) for some next steps to turn your idea into action.",
"infobox":"Probox",
"page-home":"Grants:IdeaLab/Build",
"dialog-title":"Let's create your idea!",
"toolkit-name":"Toolkit",
"toolkit-template":"subst:Grants:IdeaLab/Build/Idea_toolkit",
},

You can define as many steps as needed. Eg

"step-1":{
.....
},
"step-2":{
.....
},
"step-3":{
.....
}

The steps further contain elements as shown below.

"projectNameTextbox":{
"type":"smallTextBox",
"placeholder":"What should we call your idea?",
"title":"Idea title",
"characterLength":100,
"mandatory":true,
"error-messageLength":"Max length reached",
"error-notFilled":"Mandatory field",
"add-to":"infobox",
"infobox-param":"project",
"validate":"doesNotExists",
"page-title":true,
},

The elements supported in the forms gadget are listed below.

For elements where there are multiple values like dropdowns, checkbox list and the special stepperlist the values are defined in the as given in the example below. The hidden values are values that will not be shown to the user but will get added to the page (infobox).

Textual description can be added, as many as need by adding like in the example below.

"introText":{
"type":"text",
"string":"Don't worry about getting all your answers perfect in this form, you can edit the page later!",
},