This module implements , , , ,  and . Please see those templates' pages for documentation on how to use those templates. (Instructions for the convert function of this module are in the  documentation.)  The aforementioned templates rely on data stored in subpages for this module. For example,  generates  using মডিউল:পার্শ্ববর্তী স্টেশন/এমটিআর.  It is possible to create and edit data by following existing examples, but having some knowledge of Lua helps prevent mistakes. If you have programmed or used Lua before, you may like to skip the next subsection.   শর্তাবলী    Lua has data types. The ones relevant here are boolean, string, number, and table.  A boolean is either true or false.  A string is text, stored as a list of characters. While Lua has several ways of indicating strings within code, in the Lua examples here, strings are indicated by enclosing text in double quotes (e.g. "This is a string").  A number is a numerical value, like 0.5 or 42.  A table is a structure that can contain other objects, including other tables.  An empty table looks like {} in the code.  Tables have keys and values, which are typically of the structure ["key"] = value; each key–value pair is separated by a comma. All keys used here are strings or numbers.  {"text", "more text"} is equivalent to {[1] = "text", [2] = "more text"}.  A variable can be defined using local variable_name = "value".  Whitespace is any tab, line break or other space. Whitespace doesn't matter in Lua, but all examples here except for those inline with text are neatly indented for readability, with separate table keys on separate lines.  A return statement (e.g. return variable_name) causes a function to exit and reports the value of variable_name. The "function" here is the code in the main module calling the subpage, and the variable_name should be the data table.   Basic structure  Two modules are demonstrated below:  Blank   Example   The example module is মডিউল:পার্শ্ববর্তী স্টেশন/Kaohsiung Rapid Transit.  The two required table entries are "station format" and "lines". The former is a table with data to form links to station articles, and the latter is a table containing a table for each line.  "system title" is the text in the middle cell of the table header row.  "station format" defines the default name format for station articles and exceptions. The first variable ("%1 metro station") is the default. Exceptions are listed as key–value pairs (e.g. "Zuoying"–"Zuoying HSR station"), where the key is the input name. The module displays the input name and links to the article with the formatted name, replacing "%1" with the input. Alternatively, the full wikilink and be entered. This can be used to have the display be different from the input.  "lines" is where the lines are listed. The names here are used internally and not displayed, so choose a concise one.  "line title" is the text displayed in the middle of each row indicating the line; "left terminus" is the default station name for the left side terminus, and "right terminus" is the default station name for the right side terminus.  Each "color" entry is the colour of the line.  Below is মডিউল:পার্শ্ববর্তী স্টেশন/Taiwan High Speed Rail:   x (defined in the first line) is a string used for formatting the station name. The variable x is used inside the "station format" table for the three articles where the title ends in "station" instead of "HSR station". This practice is optional but helpful when many articles fit a second pattern.  The module recognises a virtual line named ["_default"]. The title and colour of this line is used for all lines unless overridden. Parameters are used in the absence of a specified line= in transclusion.   Hierarchy and list of parameters   The first layer of the table is data for the entire system, as well as output options.  Under the system table is the list of lines.  The third layer is data for a given line.  Each line can have 'types'. This can be either types of services or branches of the line.  The fifth layer is data for a given type.  If not specified, all keys and values are strings.   Main layer (1)  +ParameterTypeUsed in Description["lang"]StringValues are "en-US" and "en-GB". If not set, "en-GB" is assumed.["system title"]StringText in the middle cell of the header.["system icon"]StringImage used in the middle cell of the  header and by .["system icon format"]StringIcon type, used by . If specified and not "image", the value is passed to the function that implements .["system color"]StringRGB hex triplet (three or six characters, like "BE2D2C" or "039"). Can be called by using only one parameter in .["header stop noun"]StringThe noun after 'preceding' and 'following' in the left and right header cells. Default value is "station".["name format"]StringCSS for the header of  and anything else using the style function with . Values can be strings or nested tables, with the first level being for the line (whatever's in  of ). The second level is currently unused. The first entry in a nested table with no key (i.e. with key 1) is the default.["header background color"]StringRGB hex triplet for  subheaders and anything else using the style function with . By default, it is a light gray. Values can be strings or nested tables, like those for "name format".["header text color"]StringRGB hex triplet for  subheaders and anything else using the style function with . By default, it is calculated based on the header background color. Values can be strings or nested tables, like those for ["name format"].["station format"]Table or stringTable containing station format strings. The first entry without a specified key (i.e. with the key being the number 1) is the default, and all other entries must have keys corresponding to the input. Format strings without wikilink brackets are converted to links, with the input (usually the station name) used as the displayed text. Tables can be nested within this table to indicate options based on the line and line type passed to this template.  %1, %2 and %3 can be used in all strings regardless of the level of nesting to be replaced respectively by the station input, the line input (after alias replacement) and the type input (after alias replacement).["lines"]TableData table containing line tables.["aliases"]TableTable containing aliases (as table keys) for lines (as values). All keys are lowercase, as the input is treated as case-insensitive by being lower-cased.   Station format table (2)  +ParameterTypeUsed in Description[1]StringDefault format.["non-default station name"]String or tableFormat for a non-default station, or line-specific format table.   Line-specific format table (3)  +ParameterTypeUsed in Description[1]StringDefault format.["line name"]String or tableFormat for a non-default station, or type-specific format table.   Type-specific format table (4)  +ParameterTypeUsed in Description[1]StringDefault format.["type name"]StringFormat for a non-default station.   Line table (3)  A virtual line named ["_default"] can be added to set default values for all lines. Currently, this is available for two parameters. ParameterTypeUsed in Description["title"]StringThe text displayed in the middle cell, typically a link to the line's article. If not specified, then the data in ["_default"] is used (%1 in the default value is replaced by the input after alias replacement).["short name"]StringAbbreviated line name used by .["icon"]StringImage used by .["icon format"]StringIcon type used by . If specified and not "image", the value is passed to the function that implements .["color"]StringRGB hex triplet. Lines fall back to the ["_default"] colour (if any) or the system's colour if they themselves do not have one; types fall back to the line's colour (if any), to the ["_default"] colour (if any) or to the system's colour. This colour is used in the second and fourth columns of , and by  and  as the emphasised colour. By default, if a type and its line both have a colour, then the line's colour will be treated as the background colour (see next section) for the line name in the middle cell. This can be turned off by setting the type's background colour to "" or "transparent".["background color"] StringRGB hex triplet (three or six characters). This colour is optional and is only displayed behind the line name in the middle cell. The module adds transparency so that all text displayed over the background is legible.["border color"]StringRGB hex triplet used by .["text color"]StringRGB hex triplet used by .["left terminus"]StringThe station which is usually the left terminus of the line. If there are multiple stations by default, the value should be a table containing numbered values (e.g. ["left terminus"] = {"Chesham", "Amersham"}). The key ["via"] in that table can be used to append 'via' and the value's station link.["right terminus"]StringThe station which is usually the right terminus of the line; behaves like ["left terminus"].["note-mid"]StringDefault small text below line and type names. Overridden by  in transclusion.["circular"]BooleanIf the value is true then the termini will display without 'toward'/'towards'.["oneway-left"] BooleanIf the value is true then 'One-way operation' will display instead of the left terminus. ["oneway-right"]BooleanRight counterpart of oneway-left.["types"]TableTable containing the line type tables.   Type table (5)  ParameterTypeUsed in Description["title"]StringThe name of the line type. In , this is displayed as normal-sized text below the line name in the middle cell; in , for some options this is displayed after the line name, separated from it by a spaced en dash (this is also used for the nonstop text). To avoid displaying a type name, set this to "".["short name"]StringAbbreviated line name used by .["icon"]StringImage used by .["icon format"]StringIcon type used by . If specified and not "image", the value is passed to the function that implements .["color"]StringRGB hex triplet. Lines fall back to the ["_default"] colour (if any) or the system's colour if they themselves do not have one; types fall back to the line's colour (if any), to the ["_default"] colour (if any) or to the system's colour. This colour is used in the second and fourth columns of , and by  and  as the emphasised colour. By default, if a type and its line both have a colour, then the line's colour will be treated as the background colour (see next section) for the line name in the middle cell. This can be turned off by setting the type's background colour to "" or "transparent".["background color"] StringRGB hex triplet (three or six characters). This colour is optional and is only displayed behind the line name in the middle cell. The module adds transparency so that all text displayed over the background is legible.["border color"]StringRGB hex triplet used by .["text color"]StringRGB hex triplet used by .["left terminus"]StringThe station which is usually the left terminus of the line. Overrides line terminus. If there are multiple stations by default, the value should be a table containing numbered values (e.g. ["left terminus"] = {"Chesham", "Amersham"}). The key ["via"] in that table can be used to append 'via' and the value's station link.["right terminus"]StringThe station which is usually the right terminus of the line; behaves like ["left terminus"].["note-mid"]StringDefault small text below line and type names. Overridden by  in transclusion.   For developers  Suggestions are welcomed on the talk page.  To-do list   Convert more systems from , ,  and   Make an example module which contains all of the module's features, to avoid excessive examples in the documentation (maybe based on )  Allow direct replacement of ?  Function for calling a line terminus (for station layouts?)  Before translation: figure out how to handle grammatical gender and inflection in various languages with the i18n table (e.g. these phrases)  Allow inline sources to be added  Figure out Wikidata integration (require sources on Wikidata end)  Add a short list of changes from , for the convenience of the many editors who have used it in the last 11 years  changes in function (new structure, data inside module, circular and branch functionality changed, replacement of manual cell merging…)  parameter name changes (-left and -right, mostly – search  for , maybe with the TemplateData generator, to make a list)