Skip to main content

Front Matter

Last updated on by cernus76

Front Matter plays a crucial role in reference architectures. It defines key aspects such as SEO details, along with essential technical information like the slug (URL), sidebar position, and the date of the last update.

Example​

Here is an example of what a page front matter looks like:

---
id: id-ra0001
slug: /ref-arch/a06a959120
sidebar_position: 1
title: SAP Event-Driven Architecture Technology
description: Please add a description (max 300 characters)
keywords:
  - sap
sidebar_label: SAP Event-Driven Architecture Technology
image: img/logo.svg
tags:
  - ref-arch
hide_table_of_contents: false
hide_title: false
toc_min_heading_level: 2
toc_max_heading_level: 4
draft: false
unlisted: false
contributors:
  - cernus76
  - jmsrpp
last_update:
  author: cernus76
  date: 2026-04-21
---

---​

The front matter starts and ends with ---.

id​

  • Each page receives an id.

This id is structured as the following:

  • id - < assigned RAXXXX of the page > for the landing page.

Let's take the following example: id: id-ra0001. This id indicates this is the landing page of the reference architecture 0001.

Example:

id: id-ra0001
Do Not Modify

This information is auto-assigned during the technical validation.

slug​

  • Each page receives a slug which is the document's URL.

This slug is structured as the following:

  • /ref-arch/ is followed by a short UUID XXXXXXXXXX
  • /ref-arch/XXXXXXXXXX is reserved for the landing page of the reference architecture.

Example:

slug: /ref-arch/a06a959120

This id indicates this is the landing page of the reference architecture.

Do Not Modify

This information is auto-assigned during the technical validation.

  • sidebar_position is used to position the reference architecture on the sidebar.

Example:

sidebar_position: 1
Do Not Modify

This information is auto-assigned during the technical validation.

title​

  • title defines the page name, the one which will be displayed in the browser tab.
  • title is used for the SEO (used as page title when indexed by the search engines) or when the page is shared on social medias.
  • Additionally, title can also be displayed on your reference architecture page if it does not have any single # headings in it.
  • It should be clear and concise.

Example:

title: SAP Event-Driven Architecture Technology
Best practice

Your title should not be longer than 60 characters.

description​

  • description is used for the SEO (used as page description when indexed by the search engines) or when the page is shared on social medias.

Example:

description: Event-driven Architecture(EDA) is a software design pattern for building and integrating systems which focuses on flow of events and resulting reaction triggered by these events.
Best practice

We recommend to make sure the important part of your description is within the first 110 characters.

keywords​

  • keywords is used for specific keywords to find the page. All pages should have sap as default.

Example:

keywords:
  - sap
  - analytics
  - sac
  • sidebar_label is the displayed entry on the sidebar.
  • It can be identical to the title or different. It is up to you.
  • It should be clear and concise.

Example:

sidebar_label: SAP Event-Driven Architecture Technology
Best practice

Your title should not be longer than 50 characters.

image​

  • image is the image which will be displayed when sharing the page.
  • The default image is the SAP logo image: img/logo.svg

Example:

image: img/logo.svg
Best practice

The optimal size should be 1200 x 630.

tags​

  • tags are displayed at the bottom of the page.
  • The tags are defined in a yaml file named tags.yml.
  • It is possible to enrich the file and add new tags.

Example:

tags:
  - ref-arch
  - aws
  - azure

Example of a tag declaration in the tags.yml file:

ref-arch:
  label: "Reference Architectures"
  description: "Reference Architectures offer standardized, reusable templates for software architecture, providing best practices, guidelines, and blueprints to streamline design, development, and deployment."

hide_table_of_contents​

  • hide_table_of_contents allows you to reclaim the space allocated to the Table Of Content (TOC) on the right hand side of the page.
  • In some cases it makes sense to hide the TOC as there is no really use of it.
  • Default value is set to false.

Example:

hide_table_of_contents: false

hide_title​

  • hide_title allows you to not display the title of the page on the page.
  • In some cases it makes sense to hide the Title if there is no need for it.
  • Default value is set to false.

Example:

hide_title: false

toc_min_heading_level​

  • toc_min_heading_level allows you to define the minimum level for the TOC.
  • Default value is set to 2.

Example:

toc_min_heading_level: 2

toc_max_heading_level​

  • toc_max_heading_level allows you to define the maximum level for the TOC.
  • Default value is set to 4.

Example:

toc_min_heading_level: 4

draft​

  • draft defines the status of your page. If it is in draft mode, it means the page is not ready yet.
  • The default value is true
  • If you set this to true, the page will not be part of the build and will not be deployed.
  • If you set this to false, the page will be part of the build and will be deployed.

Example:

draft: false
Best practice

Keep the value to true until you are done and ready to submit the page for review.

unlisted​

  • unlisted defines if your page is visible in the Architecture Center. If it is unlisted, it means the page is deployed and accessible but it not visible.
  • The default value is false
  • If you set this to true, the page will be part of the build, will be deployed, but will not be visible in the sidebar. You need to access it directly via the defined slug.
  • If you set this to false, the page will be part of the build, will be deployed, and will be visible in the sidebar.

Example:

unlisted: false
Best practice

Set the value to true when you want to share the page to a limited number of people for validation.

contributors​

  • contributors defines the main contributors of the page.
  • Enter the GitHub username(s).
  • The contributors are displayed at the bottom of the page.

Example:

contributors:
  - cernus76
  - jmsrpp
  - navyakhurana
Best practice

Check the generated admonition to make sure there are no typos in the GitHub usernames.

last_update​

  • last_update defines the last update of the page (author + date).
  • The contributors are displayed at the bottom of the page.
  • The date should be YYYY-MM-DD.

Example:

last_update:
  author: jmsrpp
  date: 2025-01-01
Best practice

Enter only one author.