The /content directory is where all the site's (English) Markdown content lives!

See the markup reference guide for more information about supported Markdown features.

See the contributing docs for general information about working with the docs.

• Frontmatter
  • versions
  • redirect_from
  • title
  • shortTitle
  • intro
  • permissions
  • product
  • layout
  • mapTopic
  • featuredLinks
  • showMiniToc
  • miniTocMaxHeadingLevel
  • allowTitleToDifferFromFilename
  • defaultPlatform
  • learningTracks
  • includeGuides
  • type
  • topics
  • Escaping single quotes
• Autogenerated mini TOCs
• Versioning
  • Free-pro-team vs. GitHub.com versioning
• Filenames
• Whitespace control
• Links and image paths
  • Preventing transformations
• Creating new sublanding pages

YAML Frontmatter is an authoring convention popularized by Jekyll that provides a way to add metadata to pages. It is a block of key-value content that lives at the top of every Markdown file.

The following frontmatter values have special meanings and requirements for this site. There's also a schema that's used by the test suite to validate every page's frontmatter. See lib/frontmatter.js.

• Purpose: Indicates the versions to which a page applies. See Versioning for more info.
• Type: Object. Allowable keys map to product names and can be found in the versions object in lib/frontmatter.js.
• This frontmatter value is currently required for all pages.
• The * is used to denote all releases for the version.

Example that applies to GitHub.com and recent versions of GitHub Enterprise Server:

title: About your personal dashboard
versions:
  free-pro-team: '*'
  enterprise-server: '>=2.20'

Example that applies to all supported versions of GitHub Enterprise Server: (but not GitHub.com):

title: Downloading your license
versions:
  enterprise-server: '*'

You can also version a page for a range of releases. This would version the page for GitHub Enterprise Server 2.22 and 3.0 only:

versions:
  free-pro-team: '*'
  enterprise-server: '>=2.22 <3.1'

• Purpose: List URLs that should redirect to this page.
• Type: Array
• Optional

Example:

title: Getting started with GitHub Desktop
redirect_from:
  - /articles/first-launch/
  - /articles/error-github-enterprise-version-is-too-old/
  - /articles/getting-started-with-github-for-windows/

See contributing/redirects for more info.

• Purpose: Set a human-friendly title for use in the rendered page's <title> tag and an h1 element at the top of the page.
• Type: String
• Optional. If omitted, the page <title> will still be set, albeit with a generic value like GitHub.com or GitHub Enterprise.

• Purpose: An abbreviated variant of the page title for use in breadcrumbs.
• Type: String
• Optional. If omitted, title will be used.

Example:

title: Contributing to projects with GitHub Desktop
shortTitle: Contributing to projects

• Purpose: Sets the intro for the page. This string will render after the title.
• Type: String
• Optional.

• Purpose: Sets the permission statement for the article. This string will render after the intro.
• Type: String
• Optional.

• Purpose: Sets the product callout for the article. This string will render after the intro and permissions statement.
• Type: String
• Optional.

• Purpose: Wrap the page in a custom HTML layout.
• Type: String that matches the name of the layout file, without an extension. For a layout named layouts/article.html, the value would be article.
• Optional. If omitted, layouts/default.html is used.

• Purpose: Indicates whether a page is a map topic. See Map Topic Pages for more info.
• Type: Boolean. Default is false.
• Optional.

• Purpose: Renders the linked articles' titles and intros on product landing pages and the homepage.
• Type: Object.
• Optional.

Example:

featuredLinks:
  gettingStarted:
    - /path/to/page
  guides:
    - /guides/example

• Purpose: Indicates whether an article should show a mini TOC above the rest of the content. See Autogenerated mini TOCs for more info.
• Type: Boolean. Default is true on articles, and false on map topics and index.md pages.
• Optional.

• Purpose: Indicates the maximum heading level to include in an article's mini TOC. See Autogenerated mini TOCs for more info.
• Type: Number. Default is 3. Minimum is 2. Maximum is 4.
• Optional.

• Purpose: Indicates whether a page is allowed to have a title that differs from its filename. For example, content/rest/reference/orgs.md has a title of Organizations instead of Orgs. Pages with this frontmatter set to true will not be flagged in tests or updated by script/reconcile-ids-with-filenames.js.
• Type: Boolean. Default is false.
• Optional.

• Purpose: Render a list of changelog items with timestamps on product pages (ex: layouts/product-landing.html)
• Type: Array, items are objects { href: string, title: string, date: 'YYYY-MM-DD' }
• Optional.

• Purpose: Override the initial platform selection for a page. If this frontmatter is omitted, then the platform-specific content matching the reader's operating system is shown by default. This behavior can be changed for individual pages, for which a manual selection is more reasonable. For example, most GitHub Actions runners use Linux and their operating system is independent of the reader's operating system.
• Type: String, one of: mac, windows, linux.
• Optional.

Example:

defaultPlatform: linux

• Purpose: Render a list of learning tracks on a product's sub-landing page.
• type: String. This should reference learning tracks' names defined in data/learning-tracks/*.yml.
• Optional

*Note: the first learning track is by-default the featured track.

• Purpose: Render a list of articles, filterable by type and topics. Only applicable when used with layout: product-sublanding.
• Type: Array
• Optional.

Example:

includeGuides:
  - /actions/guides/about-continuous-integration
  - /actions/guides/setting-up-continuous-integration-using-workflow-templates
  - /actions/guides/building-and-testing-nodejs
  - /actions/guides/building-and-testing-powershell

• Purpose: Indicate the type of article.
• Type: String, one of the overview, quick_start, tutorial, how_to, reference.
• Optional.

• Purpose: Indicate the topics covered by the article.
• Type: String
• Optional.

If you see two single quotes in a row ('') in YML frontmatter where you might expect to see one ('), this is the YML-preferred way to escape a single quote. From the YAML spec:

In single quoted leaves, a single quote character needs to be escaped. This is done by repeating the character.

As an alternative, you can change the single quotes surrounding the frontmatter field to double quotes and leave interior single quotes unescaped.

Every article on the help site displays an autogenerated "In this article" section (aka mini TOC) at the top of the page that includes links to all H2s and H3s in the article by default.

• To make the mini TOC include additional (or fewer) heading levels, you can add miniTocMaxHeadingLevel frontmatter to specify the maximum heading level. For example: miniTocMaxHeadingLevel: 4
• To disable the mini TOC for a specific article, you can add this frontmatter: showMiniToc: false

Mini TOCs do not appear on product landing pages, category landing pages, or map topic pages.

Make sure not to add hardcoded "In this article" sections in the Markdown source or else the page will display duplicate mini TOCs.

A content file can have two types of versioning:

• versions frontmatter (required)
  • Determines in which the versions the page is available. See contributing/permalinks for more info.
• Liquid statements in content (optional)
  • Conditionally render content depending on the current version being viewed. See contributing/liquid-helpers for more info. Note Liquid conditionals can also appear in data and include files.

As of early 2021, the free-pro-team@latest version is only supported in content files (in both frontmatter and Liquid versioning) and throughout the docs site backend. It is not user facing. A helper function called lib/remove-fpt-from-path.js removes the version from URLs. Users now select GitHub.com in the Article Versions dropdown instead of Free, Pro, Team.

The convenience function allows us to continue supporting a consistent versioning structure under-the-hood while not displaying plan information to users that may be potentially confusing.

When adding a new article, make sure the filename is a kebab-cased version of the title you use in the article's title frontmatter. This can get tricky when a title has punctuation (such as "GitHub's Billing Plans"). A test will flag any discrepancies between title and filename. To override this requirement for a given article, you can add allowTitleToDifferFromFilename frontmatter.

When using Liquid conditionals in lists or tables, you can use whitespace control characters to prevent the addition of newlines that would break the list or table rendering.

Just add a hyphen on either the left, right, or both sides to indicate that there should be no newline on that side. For example, this statement removes a newline on the left side:

{%- if currentVersion == 'free-pro-team@latest' %}

These characters are especially important in index pages comprised of list items.

Local links must start with a product ID (like /actions or /admin), and image paths must start with /assets. The links to Markdown pages undergo some transformations on the server side to match the current page's language and version. The handling for these transformations lives in lib/render-content/plugins/rewrite-local-links.

For example, if you include the following link in a content file:

/github/writing-on-github/creating-a-saved-reply

When viewed on GitHub.com docs, the link gets rendered with the language code:

/en/github/writing-on-github/creating-a-saved-reply

and when viewed on GitHub Enterprise Server docs, the version is included as well:

/en/enterprise-server@2.20/github/writing-on-github/creating-a-saved-reply

There are transformations for image paths in GitHub Enterprise Server (versions 2.20-3.0) only. Once those versions are deprecation, there will no longer be any transformations for image paths. For more information, see /assets/images/enterprise/legacy-format/README.md.

Sometimes you want to link to a Dotcom-only article in Enterprise content and you don't want the link to be Enterprise-ified. To prevent the transformation, write the link using HTML and add a class of dotcom-only. For example:

<a href="/github/site-policy/github-terms-of-service" class="dotcom-only">GitHub's Terms of Service</a>

Sometimes the canonical home of content moves outside the docs site. None of the links included in lib/redirects/external-sites.json get rewritten. See contributing/redirects.md for more info about this type of redirect.

To create a sublanding page (e.g. Actions' Guide page), create or modify an existing markdown file with these specific frontmatter values:

1. Use the sublanding page template by referencing it layout: product-sublanding
2. (optional) Include the learning tracks in learningTracks
3. (optional) Define which articles to include with includeGuides.

If using learning tracks, they need to be defined in data/learning-tracks/*.yml. If using includeGuides, make sure each of the articles in this list has topics and type in its frontmatter.