Template:Generic Pattern Adjacent Service Row/doc: Difference between revisions
Jump to navigation
Jump to search
(doc stub) |
(doc added) |
||
| Line 1: | Line 1: | ||
{{Documentation subpage}} | {{Documentation subpage}} | ||
<!-- PLEASE ADD CATEGORIES AND INTERWIKIS AT THE END OF THIS PAGE. --> | <!-- PLEASE ADD CATEGORIES AND INTERWIKIS AT THE END OF THIS PAGE. --> | ||
This template creates a row in a table listing all Adjacent Services. | This template creates a single row in a table listing all Adjacent Services for a Generic Pattern. It takes the following, mandatory, named parameters: | ||
* ''service'': must be the name of a page representing the adjacent Generic Service; | |||
* ''choice'': the architect can specify if the adjacency of the Pattern Type is mandatory or optional, by using either the word "Must" or "May". If left empty, "Must" is assumed! | |||
* ''reason'': here the architect will usually insert an explanatory text, describing the rationale for adjacency. | |||
To use this template, cut and paste the following text: | |||
<pre><nowiki>{{Generic Pattern Adjacent Service Row | |||
|service= | |||
|choice= | |||
|reason= | |||
}}</nowiki></pre> | |||
<includeonly> | <includeonly> | ||
<!-- ADD CATEGORIES AND INTERWIKIS BELOW THIS LINE --> | <!-- ADD CATEGORIES AND INTERWIKIS BELOW THIS LINE --> | ||
[[Category:Query templates]] | [[Category:Query templates]] | ||
</includeonly> | </includeonly> | ||
Latest revision as of 07:55, 19 April 2013
 |
This is a documentation subpage for Template:Generic Pattern Adjacent Service Row (see that page for the template itself). It contains usage information, categories and other content that is not part of the original template page. |
This template creates a single row in a table listing all Adjacent Services for a Generic Pattern. It takes the following, mandatory, named parameters:
- service: must be the name of a page representing the adjacent Generic Service;
- choice: the architect can specify if the adjacency of the Pattern Type is mandatory or optional, by using either the word "Must" or "May". If left empty, "Must" is assumed!
- reason: here the architect will usually insert an explanatory text, describing the rationale for adjacency.
To use this template, cut and paste the following text:
{{Generic Pattern Adjacent Service Row
|service=
|choice=
|reason=
}}