Template:Infobox software/doc

Usage
The following is the base code required to generate an infobox. One can copy and paste the base code into an article and insert relevant information in front of the "=" signs. Removing HTML comments ("&lt;!--", "--&gt;" and anything between these two) is optional. To avoid accidental misuse, this base code does not have a handful of parameters that must be handled with absolute care and are not normally needed, such as.



Example


Conditional formatting parameters
The following shows the effect of three parameters which change the formatting of certain infobox fields: collapsible, discontinued, ver layout.



Parameters
All parameters are optional.


 * name
 * Name of the infobox. Can affect the title of the infobox but its primary use is to help retrieve release data from outside the article. In such cases, if you want to edit the title at the top of the infobox, use the title parameter instead.
 * Attention: Please do not include a wikilink, hyperlink or image in this parameter. This parameter should be composed of pure text.


 * bodystyle
 * CSS styling for the infobox as a whole


 * title
 * Name of the software product as displayed above the infobox. When not specified, contents of name parameter will be displayed instead.
 * Important note: Please do not include an image in this field. WikiDevi accessibility requirements mandates that this field should contain text that can be read by screen readers.


 * logo
 * Code for a small image to be displayed as software product's logo or computer icon. You may specify a full image syntax (see Help:Contents/Images and media) or just a file name, with or without namespace prefix. In other words, the following examples are all acceptable:
 * The GIMP icon - gnome.svg
 * File:The GIMP icon - gnome.svg
 * Image:The GIMP icon - gnome.svg
 * The GIMP icon - gnome.svg
 * [[Image:The GIMP icon - gnome.svg|64px]]


 * logo size
 * Size of the logo. Defaults to 64px.


 * logo caption
 * Caption of the logo that appears below it. Should not be used to provide trivial captions, such as "This is the logo of X", which is automatically assumed. Reserved for special cases when a description beyond telling the obvious is needed, or for inserting ffdc or deletable image-caption.


 * logo alt
 * Alternative text of the logo; very important.


 * screenshot
 * Code for an image to be displayed as software product's screenshot. You may specify a full image syntax (see Help:Contents/Images and media) or just a file name, with or without namespace prefix. In other words, the following examples are all acceptable:
 * GIMP_screenshot.png
 * File:GIMP_screenshot.png
 * Image:GIMP_screenshot.png
 * GIMP_screenshot.png
 * [[Image:GIMP_screenshot.png|300px]]


 * caption
 * A caption for screenshot that appears below it. Please include this parameter only when there is an image to display.


 * screenshot size
 * Size of the screenshot. Defaults to 300px.


 * screenshot alt
 * Alternative text of the screenshot; very important. Defaults to image caption.


 * collapsible
 * Whether this screenshot is by default hidden and is only shown when user clicks on a minuscule "Expand" button. Can be set to "yes". Especially useful in case of long vertical screenshot


 * author
 * Name of the original author(s) or publisher(s) of the software product. It can be either an individual or an organization/business. Most of the times, it only needs to be specified when developer field is populated.


 * developer
 * Name of the current developer of the software product. It can be either an individual or an organization/business.


 * released
 * The date in which version 1.0 (or closely-matching release) of the software product in question reaches its release to manufacturing (RTM) stage. In case the article is about a specific major release of a software product (for instance Internet Explorer 8 or Microsoft Office 2007), this field should contain the date in which that specific major release reached RTM stage. In case the software product is still in development and has not reached its RTM stage, please ignore this field; do not use this field to specify the release date of the first preview/test release of the software product; there is already another parameter for that use.
 * The content of this field should look like the following:
 * In case the article uses DMY as date format, use this code instead:
 * If you are unsure which date format to use, please consult WP:MOSDATES.
 * If you are unsure which date format to use, please consult WP:MOSDATES.
 * If you are unsure which date format to use, please consult WP:MOSDATES.


 * discontinued
 * Whether this product is no longer being developed, thus changing the phrase "Latest release" in the infobox to "Last release". For technical reasons, anything for this parameter has the same effect, be it "yes", "no" or anything else. To nullify the effect of this parameter, you need to omit it.


 * latest release version
 * The version number of the latest release of the software product. Please observe the following examples:
 * Example #1: If the article is about a product called Example Software whose latest version is 1.5, specify:
 * v1.5
 * Example #2: If the article is about a product called Example Software whose latest release is called Example Software 2008 and whose latest version number is 12.2, specify:
 * 2008 (v12.2)
 * Example #3: If the article is about Famous Example Software 2010, which is a significant release of a product called Famous Example Software and whose latest version number is 14.0.0.25, just specify:
 * v14.0.0.25
 * Example #4: If the article is about Famous Example Software 2010 for which no update is released since its initial release-to-manufacturing (RTM), please omit this parameter unless there is an evidence that it is necessary for the reader to know this number. One reason would be the presence of preview releases of the software product which can only be distinguished from the RTM by their version number.
 * depends on this parameter.


 * latest release date
 * The release date of the latest released version. If no update is released for the software since its initial release, please omit this field; filling in the  field would be enough. The content of this field should look like the following:
 * In case the article uses DMY as date format, use this code instead:
 * If you are unsure which date format to use, please consult WP:MOSDATES.
 * This parameter only works when a  is present.
 * If you are unsure which date format to use, please consult WP:MOSDATES.
 * This parameter only works when a  is present.


 * latest preview version
 * The version number of the latest preview version or development branch. Should only be specified when development of a new version of the software product in question (newer than one specified in ) is in progress. Please consult descriptions for   provided above for best practices of specifying this parameter.


 * latest preview date
 * Specifies the release date of the latest preview version or development branch. Should only be specified when development of a new version of the software product in question (newer than one specified in ) is in progress. Please consult descriptions for   provided above for best practices of specifying this parameter.


 * status
 * The development status of the computer program, such as: Planned, Active, Unmaintained, Discontinued, Stalled or Abandonware


 * programming language
 * The programming language of that subject of the article. If the program language of the software product has a corresponding article in WikiDevi, please link to it. Here is an example:
 * Code:
 * Result: C++ and C#
 * When specifying the name of the programming language please make sure that you cite your source. Unreferenced assertions in WikiDevi may be challenged or removed. If you do not have a source, do not include this parameter.


 * operating system
 * The operating system on which the given software product works. Please be as accurate as possible but also be mindful of the length and avoid specifying vague phrases such as Cross-platform, Multi-platform, all or none. If the project is a web app or if only an OS-agnostic source code is released, ignore. Please consider these examples:
 * If the software product works on all incarnations of Unix, Linux and derived operating systems, please specify:
 * If the software works unconditionally on ALL incarnations of Microsoft Windows, please specify:
 * or
 * If the software product works only on Windows XP and all subsequent releases of Microsoft Windows, please specify:
 * If the software product works only on Windows XP and all subsequent releases of consumers versions of Microsoft Windows, please specify:
 * (At the time of this writing, February 2013, Windows 8 was the latest consumers release of Microsoft Windows.)
 * If the software product is released for various families of different operating systems, (such as specific versions of BSD, Linux, Mac OS and Microsoft Windows) so that listing them in the infobox gives it undue length, please leave the details to article body and specify:
 * (At the time of this writing, February 2013, Windows 8 was the latest consumers release of Microsoft Windows.)
 * If the software product is released for various families of different operating systems, (such as specific versions of BSD, Linux, Mac OS and Microsoft Windows) so that listing them in the infobox gives it undue length, please leave the details to article body and specify:


 * platform
 * The computing platform on which the product runs. You might like to include the following information:
 * Processor architecture: Some software products run on a certain processor architecture such as IA-32 (also known as x86 an i386), x86-64 (also known as x64, AMD64 and EM64T), Itanium, ARM and MIPS. Please avoid common mistakes highlighted in.
 * Software frameworks: Some software products run on Java platform, .NET Framework, Adobe Flash, Adobe AIR, Microsoft Silverlight or XUL without regard to the processor architecture. If so, you may ignore processor architecture and instead specify the framework.
 * Please avoid specifying vague phrases such as "cross-platform" unless the following conditions meet:
 * The software product has been released for numerous different platforms, so much so that including all of them causes the infobox size to grow unduly large.
 * The article body lists the platforms under which the product runs.
 * If the above do not meet, then specifying such a vague phrase is the same as not specifying it.


 * size
 * Size of the installer package. Only applies to software products that are available via download. For products distributed physically in boxes or other packages, ignore this parameter. Do not forget to include your unit of measurements (i.e. Kilobytes, megabytes or gigabytes).
 * Note: Use a non-breaking space ("&#x26;nbsp&#x3B;") to prevent numbers and units of measurements from separating when "word wrapping" occurs. You can also use Nowrap template to produce the same effect.
 * Observe the following examples:


 * width = "50%" |
 *  760&#x26;nbsp&#x3B;KB  ? 760 KB
 *  32&#x26;nbsp&#x3B;MB  ? 32 MB
 * width = "50%" |
 *  842 KB  ? 842 KB
 *  48.5 MB  ? 48.5 MB
 * }
 * For more information, visit WP:UNITS
 * For more information, visit WP:UNITS


 * language
 * Lists the natural languages in which the software product user interface can interact with user. Please do not supply "Multilingual" or such vague phrases which do not add to the knowledge of the reader. Also please do not wikilink the name of languages: Readers are most likely unwilling to read about those languages. For a comprehensive list of items that should not be generally linked to, see . A large list of languages can disrupt the natural flow of the article. When the list of languages grows large, consider one of the following measures:
 * Use language count parameter in conjunction with this parameter. This will allow the list of languages to be hidden and revealed with the click of a mouse. This method is not printer-friendly: A collapsed list does not appear on print and an expanded list may disrupt the natural flow of the article.
 * Add a link to a section of the article which lists languages. Please keep the link printer-friendly. For example, instead of " Click here to see the list of languages ", consider " 35 languages; see § Localization ". This solution is useful when the inclusion of a list of languages is important or when the localization of the subject of the article is discussed.
 * Ignore this parameter and use language count and language footnote instead. This approach is useful when the article is short and inclusion of the list of languages is unwanted or contested.


 * language count
 * Number of natural languages in which the software product user interface can interact with user. Please supply a number only. Don't use this parameter if the list of languages includes less than five entries. (Please see: )
 * If both language and language count parameters are present, the value of language will be collapsed under "List of languages" title.


 * language footnote
 * Use this parameter to supply citation on available translations, especially when language is not specified. Use of this parameter is not mandatory, as long as appropriate citation information is attached to the text. For instance, citation information may be attached to text itself in the article body or language, especially when there are more than one source for it information given. (E.g. when one source includes full translations and another includes partial translations; or when one source specifies the translations of one given version and another discusses what is added to that version after an update.) As a general rule, avoid citing automatically generated reports, statements about development versions or other sources of time-sensitive information.


 * genre
 * Type of program. Should be wikilinked to an article such as Geographic information system. For more information, consult List of software categories. Please do not use this field to briefly describe the role and function of the subject of the article. For example, instead of "SVG creator, editor and converter", consider using "Vector graphics editor". Instead of "PDF creator, editor, converter and viewer", consider using "Desktop publishing software". Instead of "DWG creator/editor", consider using "Computer-aided design".


 * license
 * Type of the software license under which the consumer is allowed to use the product. You may specify it in two forms:
 * You may specify a type of well-known license. For example:
 * Proprietary commercial software : Software products which are licensed for use for a price. (As in this example, please be sure to link to, which is an article about this type of software, and not to  , which is a disambiguation page.)
 * Trialware/Shareware: Same as proprietary commercial, but the user may try the product for limited time. Most software today are published under this license type.
 * Freemium: Software products that are provided in both freeware and commercial versions, with the free version being usable without the need for any compulsory payment, but lacking certain features (not to be confused with shareware)
 * Freeware: Software products which are licensed for use (and sometimes redistribution) but free of charge.
 * GNU General Public License, GNU Lesser General Public License and BSD License: three forms of free and open-source software.
 * Please avoid specifying phrases that makes no sense to the unfamiliar reader such as "Microsoft EULA", "Adobe End-User License Agreement" or "Symantec Terms of License", etc. (Always bear in mind that you are writing the article for those who do not know about the subject and come to the article to gain knowledge. You are not writing WikiDevi articles for your fellow contributors or editors who already know.)


 * licence
 * Same as license. Pick either license (American English) or licence (Commonwealth English), not both - select the one which matches the content of the article the template is used in.


 * alexa
 * The website's current Alexa ranking (find on Alexa.com; make sure to cite Alexa's page for this info.)


 * Put Increase OR Steady  OR Decrease  BEFORE the ranking number to indicate the change of ranking compared with the previous month.
 * Mention the date of putting the ranking number AFTER the ranking number. Put the date in parenthesis, for example: (July 2012). If you update the ranking number, update the date as well.
 * At User talk:Riley Huntley/AlexaBot.js you can request that a bot will monthly update the rank.
 * website
 * The web site URL of the software package. This URL must be readable in print. Therefore, you should use URL template like this: "http://www.example.com". Avoid using printer-hostile forms like " ". In absence of this parameter, infobox attempts to acquire the website link from Wikidata. This parameter overrides the Wikidata link. (It is useful when a second infobox for something different is defined on a page.) In addition, the special value "hide" suppresses this field, even in presence of a Wikidata link. This is useful for articles with several infoboxes, to avoid repeating one Wikidata link.


 * repo
 * The online source code repository, if available. For example, the sourceforge or github project page. As with the  parameter, this should use the URL template. In the absence of this parameter, infobox attempts to acquire the repository link from Wikidata. This parameter overrides the Wikidata link.


 * standard
 * Technical standard of the subject of the article adheres.


 * AsOf
 * A pseudo-parameter populated by bots and users tending to maintenance categories. The intricacies of this parameter are not included here. If you don't know what it does, please do not touch.

Moving release data outside the article
The subject's latest release version, latest release date, latest preview version and latest preview date can be moved outside the article. Users visiting the article may click the version number or "[±]" link in the infobox to edit that external source. This mode is very useful for articles about software products whose vendors keep releasing updates or newer versions. With this mode is enabled, users can quickly and effectively edit the release data without editing the article proper (and cluttering its edit history with inconsequential edits).

Note, however, that if latest release version or latest preview version parameters are explicitly specified, the infobox does not look for external sources. (This can be useful if, for example, the preview version is frequently updated, but the release version is not.)

To make the infobox retrieve release data from outside the article:
 * 1) Create an external source that supplies data for latest stable release. To do so: 1. Copy and paste the following URL into your browser's address bar, replacing INFOBOX_NAME with the value supplied in name parameter of the infobox:

2. In the page that opens, fill in the required information.

3. Save the page.
 * 1) Create an external source that supplies data for latest preview release. To do so: 1. Copy and paste the following URL into your browser's address bar, replacing INFOBOX_NAME with the value suppplied in name parameter of the infobox:

2. In the page that opens, fill in the required information.

3. Save the page.
 * 1) In the main article, delete latest release version, latest release date, latest preview version or latest preview date parameters from the corresponding infobox.
 * 2) Save the article.
 * 3) Refresh the article.

Microformat
<!--

TemplateData
{	"description": "An infobox for computer software", "params": { "title": { "label": "Title", "type": "string", "required": false, "description": "Name of the computer program. Displayed at the top of the infobox. If not specified the 'Name' parameter or the PAGENAME are used. It should be plain text. Do not include a wikilink, hyperlink or image in this parameter." },		"name": { "label": "Name", "type": "string", "required": true, "description": "Name of the infobox. This is used internally in combination with Template:Latest stable software release/'name' and is also displayed at the top of the infobox if the Title parameter is absent. It must be pure text. Do not include any wikimarkup in this parameter.", "default": "PAGENAME" },		"logo": { "label": "Logo", "type": "wiki-page-name", "required": false, "description": "Filename for the image e.g. 'File:The GIMP icon - gnome.svg' " },		"logo size": { "label": "Logo size", "type": "string", "required": false, "description": "Size of the logo.", "default": "64px", "aliases": [ "logo_size" ]		},		"logo alt": { "label": "Logo alternative text", "type": "string", "required": false, "description": "Alternative text for the logo (used by the blind and when web browsers cannot or do not load the image)", "aliases": [ "logo_alt" ]		},		"logo caption": { "label": "Logo caption", "type": "string", "required": false, "description": "Caption for the logo. Must only be used to provide anything far more important than 'This is the logo of X'. e.g. used for inserting or ." },		"screenshot": { "label": "Screenshot", "type": "wiki-page-name", "required": false, "description": "File name for a screenshot of the image, e.g. 'File:GIMP_screenshot.png'" },		"screenshot size": { "label": "Screenshot size", "type": "string", "required": false, "description": "Size of screenshot", "default": "300px", "aliases": [ "screenshot_size" ]		},		"screenshot alt": { "label": "Screenshot alternative text", "type": "string", "required": false, "description": "Alternative text for the screenshot (used by the blind and when web browsers cannot or do not load the image)", "aliases": [ "screenshot_alt" ]		},		"caption": { "label": "Caption", "type": "string", "required": false, "description": "Caption for the screenshot" },		"collapsible": { "label": "Collapsible?", "type": "string", "required": false, "description": "Whether this screenshot is hidden by default, set to 'yes' to place the screenshot in a collapsible section" },		"author": { "label": "Original author", "type": "string", "required": false, "description": "Name of the original author or publisher of the software product. It can be either an individual or an organization/business. Most of the times, it only needs to be specified when developer field is populated." },		"developer": { "label": "Developer", "type": "string", "required": false, "description": "Name of the current developer of the software product. It can be either an individual or an organization/business." },		"released": { "label": "Initial release date", "type": "string", "required": false, "description": "The date in which version 1.0 (or closely-matching release) of the software product in question reaches its release to manufacturing (RTM) stage. In case the article is about a specific major release of a software product (for instance Internet Explorer 8 or Microsoft Office 2007), this field should contain the date in which that specific major release reached RTM stage. In case the software product is still in development and has not reached its RTM stage, please ignore this field; do not use this field to specify the release date of the first preview/test release of the software product; there is already another parameter for that use. The content of this field should look like the following: In case the article uses DMY as date format, use this code instead:  If you are unsure which date format to use, please consult WP:MOSDATES." },		"discontinued": { "label": "Is discontinued?", "type": "string", "required": false, "description": "Whether this product is no longer being developed, thus changing the phrase 'Latest release' in the infobox to 'Final release'. For technical reasons, anything for this parameter has the same effect, be it 'yes', 'no' or anything else. To nullify the effect of this parameter, you need to omit it." },		"ver layout": { "label": "Version info layout", "description": "Defines how version number information appear in the infobox. Can be set to \"simple\" (default) or \"stacked\". \"Simple\" allocates an ordinary row to \"latest release version\" and another to \"latest preview version\". But \"stacked\" gives the full width of the row the info and adds a header, so that several version numbers can appear and use the infobox space more efficiently.", "autovalue": "simple", "type": "string" },		"latest release version": { "label": "Latest release version", "type": "string", "required": false, "description": "The version number of the latest release of the software product. E.g. 'v1.5', '2008 (v12.2)', ", "aliases": [ "latest_release_version" ]		},		"latest release date": { "label": "Latest release date", "type": "string", "required": false, "description": "The release date of the latest released version. If no update is released for the software since its initial release, please omit this field; filling in the released field would be enough. The content of this field should look like the following: ", "aliases": [ "latest_release_date" ]		},		"latest preview version": { "label": "Latest preview version", "type": "string", "required": false, "description": "The version number of the latest preview version or development branch. Should only be specified when development of a new version of the software product in question (newer than one specified in latest release version) is in progress. Please consult descriptions for latest release version provided above for best practices of specifying this parameter.", "aliases": [ "latest_preview_version" ]		},		"latest preview date": { "label": "Latest preview date", "type": "string", "required": false, "description": "Specifies the release date of the latest preview version or development branch. Should only be specified when development of a new version of the software product in question (newer than one specified in latest release version) is in progress. Please consult descriptions for latest release date provided above for best practices of specifying this parameter.", "aliases": [ "latest_preview_date" ]		},		"status": { "label": "Status", "type": "string", "required": false, "description": "The development status of the computer program, such as: 'Planned', 'Active', 'Unmaintained', 'Discontinued', 'Stalled' or 'Abandonware'" },		"programming language": { "label": "Programming language", "type": "string", "required": false, "description": "The programming language in which the subject of the infobox is created. If the program language of the software product has a corresponding article in WikiDevi, please link to it. E.g. 'C++ and C#'. Be advised that WikiDevi policies such as WikiDevi:Verifiability and WikiDevi:No original research also apply here.", "aliases": [ "programming_language" ]		},		"operating system": { "label": "Operating system", "type": "string", "required": false, "description": "The operating system on which the given software product works. E.g. 'Microsoft Windows' or 'Windows', 'Windows XP and later'. If the software is an operating system–independent web application, ignore this parameter. Please be as accurate as possible in specifying this parameter (but also be mindful of the length) and avoid specifying vague phrases such as 'Cross-platform' (or its redirect, Multi-platform) or 'Unix-like' (implies that the subject runs on most desktops, server and mobile devices).", "aliases": [ "operating_system" ]		},		"platform": { "label": "Platform", "type": "string", "required": false, "description": "The computing platform on which the product runs. Can be specific processors like 'IA-32' (i386), 'x86-64' 'Itanium', 'ARM' or 'MIPS'." },		"size": { "label": "Size", "type": "string", "required": false, "description": "Size of the installer package. Only applies to software products that are available via download. E.g. '48 MB'." },		"language": { "label": "Language", "type": "string", "required": false, "description": "Lists the natural languages in which the software product user interface can interact with user. Please do not supply 'Multilingual' or such vague phrases." },		"language count": { "label": "Language count", "type": "number", "required": false, "description": "Number of natural languages in which the software product user interface can interact with user." },		"language footnote": { "label": "Language footnote", "type": "string", "required": false, "description": "Use this parameter to supply citation on available translations." },		"genre": { "label": "Genre", "type": "wiki-page-name", "required": false, "description": "Type of program. Should be wikilinked to an article such as 'Geographic information system'. For more information, consult List of software categories." },		"license": { "label": "License", "type": "string", "required": false, "description": "Type of the software license under which the consumer is allowed to use the product. E.g. 'Proprietary commercial software', 'Freeware', 'Free software', 'GNU General Public License', 'BSDLicense'." },		"licence": { "label": "Licence", "type": "string", "required": false, "description": "Alternative to license for articles using Commonwealth English." },		"alexa": { "label": "Alexa ranking", "type": "string", "required": false, "description": "The website's current Alexa ranking. See main documentation page for details on automatic update." },		"website": { "label": "Website", "type": "string", "required": false, "description": "The web site URL of the software package. This URL must be readable in print. Therefore, you should use 'URL' template like this: 'http://www.example.com'. Avoid using printer-hostile forms like 'Example website'. In absence of this parameter, infobox attempts to acquire the website link form Wikidata. This parameter overrides the Wikidata link. (It is useful when a second infobox for something different is defined on a page.) In addition, the special value 'hide' suppresses this field, even in presence of a Wikidata link. This is useful for articles with several infoboxes, to avoid repeating one Wikidata link." },		"repo": { "label": "Source code repository", "type": "string", "required": false, "description": "The online source code repository, if available. For example, the sourceforge or github project page. As with the website parameter, this should use the undefined template. In the absence of this parameter, infobox attempts to acquire the repository link from Wikidata. This parameter overrides the Wikidata link." },		"standard": { "label": "Standard(s)", "type": "string", "required": false, "description": "Technical standard of the software." },		"AsOf": { "label": "Infobox timestamp (AsOf)", "type": "string", "required": false, "description": "Infobox timestamp in the form of month name, space character, year (four digits). Used by maintenance procedures and bots." },		"bodystyle": { "label": "Body style (CSS)", "type": "string", "required": false, "description": "CSS styling for the infobox as a whole" }	},	"format": "block", "paramOrder": [ "title", "name", "logo", "logo size", "logo alt", "logo caption", "screenshot", "screenshot size", "screenshot alt", "caption", "collapsible", "author", "developer", "released", "discontinued", "ver layout", "latest release version", "latest release date", "latest preview version", "latest preview date", "repo", "status", "programming language", "operating system", "platform", "size", "language", "language count", "language footnote", "genre", "license", "licence", "alexa", "website", "standard", "AsOf", "bodystyle" ] } -->