Testsite 12
| noframe | |||||||||||||||||||||||||||||||
| Bryggeri | Testsite | ||||||||||||||||||||||||||||||
| Defunct | Testsite 7 Breweri | ||||||||||||||||||||||||||||||
| Start | Testsite 7 Breweri | ||||||||||||||||||||||||||||||
| Homepage | {{#invoke:URL|url|1=ahlaforsbryggerier.se|2=}} | ||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||
| wikibeeria.com | |||||||||||||||||||||||||||||||
Designing
Editors generally compose infoboxes from four types of visual elements: A title, images, sections, and fields. Since these terms are not standard, we illustrate them here:
The selection and arrangement of fields is an important design decision for which gives some general advice. The part of a field that varies from article to article becomes a parameter for the newly prototyped infobox and must be consistently expressed in two distinct places:
- In the infobox implementation itself, to indicate where the article-specific text is to be displayed
- In the infobox documentation, to indicate which article-specific information editors are to provide when using the infobox
Additionally, the editor should decide whether a field (and hence its corresponding parameter) is required or optional. The difference between the two is that a required field is always displayed; an optional field is not displayed where articles referencing the infobox omit the parameter. If the field is required, the infobox designer should consider whether a default value for the field is useful.
