Reusable attributes

Fedora Documentation Team Version 0.0.1 Last review: 2020-08-26

This page explains how to use reusable metadata, or attributes, across multiple AsciiDoc documents in Fedora Documentation.

Why reusable attributes?

Sometimes you may want to use the same data across many AsciiDoc documents. Some examples are below:

For these and more use cases, attributes allow you to define some metadata in a single place, and reuse it in multiple places.


There are two requirements for your Fedora Documentation project to use attributes.

  1. Create an attributes file

  2. Import attributes in your AsciiDoc file

Create attributes file

First, initialize an attributes.adoc file for any module. The example below shows a globally reusable attributes file in the ROOT module:

└── ROOT
    ├── nav.adoc
    ├── pages
    │   └── index.adoc
    └── partials
        └── attributes.adoc

This is an example attributes.adoc from the Fedora DEI Team:

// This is a data store of information about the Fedora DEI team.

// Team name:
:team_name: Fedora Diversity, Equity, & Inclusion (DEI) Team

// Team summary:
:team_summary: The {team_name} encourages, supports, and enables DEI in the Fedora community. We work with the community to create an environment where everyone feels empowered to be a part of and contribute to the Fedora Project.

// Team page URL:

// Team activity status.
// Choose from: Active, Inactive
:team_status: Active

// Preferred asynchronous communication channel

// Preferred synchronous communication channel

// Issue tracker

// Meetings

// Imported from our old attributes file.
:YEAR: 2023

Import attributes

Next, import the attributes file into your AsciiDoc document. Placing this macro on the top line will do the rest:


Use attributes in documentation

After creating an attributes file AND import attributes, reference the attributes in AsciiDoc documents with the following syntax:


See this example from the Fedora DEI Team:

*Full consensus* is required to approve new processes, make changes to
existing team policies, and tickets requiring{FISCALYEAR}/d-i.html[D&I budget].