The article head holds the above-the-fold content, such as the headline, byline, introduction, and an optional basic aside.
The article head content is not version-controlled, but any changes made to it are immediately visible. That means that if changes to these need to be made as a result of a new version of the article body, release the new version, then immediately update the head content.
Article headers scale with the width of the page, so their elements stay in the same spatial relationship to each other and won't suddenly wrap around at narrow widths.
If requiring a complete version of an article for saving in a records management system, save as a single self-contained file which many browsers offer, or print to a PDF file, though the latter may disable live links or other functionality .
Descriptions of the navigation bar items.
|a||Owner path||Article owner hierarchy as jumps to their listing in the Access section of the Work list page|
|b||Phase details||Various details of the current phase. Only shown if the article is being edited|
The article body navigation bar provide jumps to the pages for it and its hierarchy of owners.
|1||Subsite||Owning subsite identifier as a jump to its entry in the Access section in the Work list page, with its category list expanded|
|2||Category||Owning category identifier as a jump to its entry in the Access section in the Work list page, with its article list expanded|
|3||Article||Article identifier as a jump to its entry in the Access section in the Work list page. New for a new article|
The article body navigation bar holds the details of the current phase.
|1||Phase||Current editing phase as a jump to the article's entry in the In-progress section of the Work list page. Followed by the locale, user ID and due duration if applicable|
|2||Locale||Locale being processed by the current phase. Only shown if an editing or review phase|
|3||User ID||User identifier of the person assigned the current phase. If not an editing or review phase, Manager is shown|
|4||Due||Duration in which the task is expected to be completed. Only shown if an editing or review phase|
This section describes the basic information for managing an article.
|1||Subtype||Subtype of article. One of Article, Navigation, Procedure or Test. Not displayed for subsite-specific articles|
|2||Headline||Headline for the article as a link to the latest release. Cannot be changed to one that already exists. Analogous to a newspaper headline as a short catchphrase to get attention|
|3||Navigation||Short version of the Headline to be used in navigation links|
|4||Byline||Analogous to a newspaper byline that qualifies or extends the Headline, so that the latter can be kept short. Appears in the article header below the Headline|
|5||Introduction||Plain text introduction of what the article is about. Also used to provide text about the article on various pages|
|6||Author||Full name of the writer of the current article. Used instead of the site and subsite Authors|
|7||Signature||Whether the article is listed at the top of an alphabetically-sorted Category page. Checking disables Signature for any other article in the category. Only shown if not template, in default category or subsite article|
|8||Dates||Date the article was created and last updated as a release|
|9||Subsite||Provides the numbers of categories and articles in the article's subsite. Not shown for writers|
|10||Category||Provides the numbers of articles in the article's category, as well as a means to change that category. Not shown for writers|
|11||Versions||Buttons for viewing and updating versions. History jumps to the Phases checkbox for the master locale on the History page if there are phases, else to the Article ID in its owner path. Update does the same and creates an Update phase, but only appears if the latest version is a release. Latest jumps to the Article body page, for the phase's locale if assigned|
|12||Show||Specifying how visible pages are in terms of discoverability. Listed means the article is listed on various public pages. Unlisted do not appear on those pages, but can be accessed if its URL is known. Hidden cannot be publicly accessed. Subsite-specific articles are never listed, but the articles can be accessed if their URL is known, though there are settings to show their links in the Site navigation bar and Site links. Not shown for writers|
|13||Locales||Which non-master locales an article can be publicly rendered in. Not shown for writers|
|14||Delete||Available to delete an article, but only if it is hidden and is not linked to. Only shown for master manager|
The identifier used by links and URLs is derived from the master locale Headline by converting it all to lowercase, converting each sequence of non-alphabetic characters to a single -, then prefixing it with the letter for the article type and -.
Because Android phones usually show text about 8% larger than almost anywhere else, if not having access to an Android phone to check that Headline and Byline don't make the text in them wrap around, allow at least 5-10% clearance either end of the text when designing on other devices.
Navigation is mainly for ensuring that navigation text is short so that many items can appear in navigation bars. That means that it may not be required for all locales, but only for those that may need to be shorter. Therefore, unlike other values that fall-through the locale hierarchy to the master, Navigation is only used if defined for the current locale, otherwise the headline is used. A ? will appear if the headline is perhaps too long, but Navigation may be safely ignored at the expense of possibly cluttered navigation bars.
For a card, the article's Navigation and Introduction are used as its heading and explanatory text. If there is no navigation text, the Headline is used. Consider how the text for these article attributes would look in a card when composing their text. In particular, avoid long words that may cause large gaps between them when rendered with justification, though they may alright to use as the first word.
By default, new articles are only enabled for the master locale. Once all the text for a locale for the article has been completed, the locale can be enabled under Locales. Up until then, the locale is bypassed in locale fall-through. If the locale was specified for rendering of the page, a highlighted message is displayed under the page header indicating that it is not available and which locale the page is being displayed with. All links on the page still use the original locale to maximise locale continuity while traversing the site.
Enabling a locale for an article does not check if any text has actually been translated in it as some fall-through may be wanted, such as when having two different English locales where spellings differ, but some paragraphs may have no such differences, so the non-master versions do not need to have their own text. While editing, rich-text element blocks will have an 🗗 to indicate that it has no inline elements, while fields for sections, and asides and glossary headings will be empty.
The home page cannot be deleted directly. When its subsite is deleted, the home page will be converted to a normal navigation page (h- in its ID is replaced with n-) and placed under Templates, from where it can be deleted.
A basic aside is a simple aside whose only content is an introduction, image and optionally a quote.
|1||Actions||Buttons are provided for enabling and removing the basic aside|
|2||Heading||Heading for the aside|
|3||Introduction||Plain text introduction for the image. If there is no image, this is displayed as a paragraph|
|4||Image||Details about the current image used for the aside or for displaying in a card or gallery item that links to the article, with an opportunity to select another, or remove it. Only Cards and Asides are available for selection|
|5||Quote||Optional plain text quote to be centred under the image. Insert @^ for each line break required. Use for a personal saying of the person in the image. Not shown on a page if no Image|
The selected Image can be used in a cards (if Card) or gallery (if Card or Aside) array of a Navigation article by referencing the article as part of the array, regardless of whether the aside is enabled or not. If no Heading is specified, the basic aside is not shown on the page. However, if there is an Image, the article can still be referenced from a cards or gallery array.
This section lists all the article's links.
|1||Link type||Name of the link group. This jumps to the Links page to allow modifying which links are in that group|
|2||Target||List of the group's links targets and their type, with jumps to them. For Site links, there are toggles for which existing subsite-specific pages are to be included|
|1||Cards||Articles or categories from which the heading, basic aside image and introduction are extracted for an array of card for informative navigation choices. Only for Navigation article pages|
|2||Catalog||Articles or categories from which the heading, basic aside image and introduction are extracted for Category page-like custom themed list. Only for Navigation article pages|
|3||Gallery||Articles or categories from which the basic aside images are extracted for an array of images for visual navigation choices. Only for Navigation article pages|
|4||Inline||Any links in the article body, and times used if more than once. Can only change these by editing the article on the Article body page|
|5||Related articles||Articles and categories that are part of the site|
|6||Related sites||Pages from other sites|
Only one of a cards array, catalog or gallery can be used in the one navigation page. Cards are for primary navigation, while a gallery is more a way to show some pictures for people to select from on a whim.
For external links in the list of links for Related sites, the listings will be the URL. For internal links in the other link types, the form is Article: ID. Inline links will be prefixed with the host type, like Link: or Citation:
This section lists the sources of all the links to this article.
|1||Source type||The type of owner of the link that points to the article. Either Subsite or Article|
|2||Source ID||The source identifier of the host of the link to the article. Click on it to jump to its manage page|
|3||Link type||The location of the link in its host. Click to jump to where that link is defined in the source|
This section lists all the files linked to by the article, either inline in the article, or by its basic aside.
|1||File ID | …||File identifier, extension and the number of times used|
|2||Thumbnail||Scaled down view of an image or video, and blank for any other type. Can be clicked on or tabbed to to expand it|
|3||Text | …||Text description of the file, file mime type and its purpose (usage type). The text is used for images by the screen readers used by those who cannot see|
A new article only requires a heading, an introduction, and optionally a byline.
The fields for a new article are only available after clicking on the New link on various pages, clicking on the required subtype, and either clicking on Blank or an article from the list to clone from. That list of articles is only those of the same type that have been released and not currently being edited. New articles are always Hidden.
|1||Headline||Headline for the new article. Cannot be the name of an existing article. Note that the resulting article identifier derived from the headline might also be rejected because it already exists|
|2||Byline||Analogous to a newspaper byline that qualifies or extends the Headline, so that the latter can be kept short. Appears in the article header below the Headline. Not available if cloned|
|3||Introduction||Plain text introduction to what the article is about. Also used to provide text about the article on various pages. Not available if cloned|
For cloning, while the new article must have a different headline for the master locale to ensure it has its own URL, the rest of the article is as intact as possible. Especially if using multiple locales, this keeps the maximum amount of existing content to aid in deciding what to edit for the purpose of the new article. The cloned article will have a creation date at least one second after the article it was cloned from, reflecting the starting copyright date of the content cloned. The updated date will be that of the cloned article or the new creation date, whichever is later.