Difference between revisions of "Best Practices for Forms and Templates"

From edegan.com
Jump to navigation Jump to search
Line 9: Line 9:
  
 
You can assign the type of a property and restrict a property's value by creating a page for that property.  
 
You can assign the type of a property and restrict a property's value by creating a page for that property.  
 +
<nowiki>
 
  This is a property of type [[Has type::Text]].
 
  This is a property of type [[Has type::Text]].
 
   
 
   
Line 15: Line 16:
 
  * [[Allows value::In development]]
 
  * [[Allows value::In development]]
 
  * [[Allows value::Draft]]
 
  * [[Allows value::Draft]]
 +
</nowiki>
  
 
Also, the following create a link to a property page and show its information:
 
Also, the following create a link to a property page and show its information:

Revision as of 19:38, 27 February 2017

Links

Conventions

You can assign the type of a property and restrict a property's value by creating a page for that property.

 This is a property of type [[Has type::Text]].
 
 The allowed values for this property are:
 * [[Allows value::Idea]]
 * [[Allows value::In development]]
 * [[Allows value::Draft]]
 

Also, the following create a link to a property page and show its information:

 [[Property:Has_paper_status]]
 {{Property:Has_paper_status}}
 


Notes

Check that you did the following:

  • Put the category in the template itself
  • Make sure that there is a default form associated with the template
 {{#default_form:McNair Projects}}
 [[category:McNair Projects]]
 

Use simple assignment whenever possible:

| label6       = Start Date
| data6        =  

If you have to use an array ref, here's the syntax:

| label5      = Owner
| data5       =