glue.xml

<?xml version="1.0" encoding="UTF-8"?>
<!-- This file originates from the project https://github.com/openSUSE/doc-kit -->
<!-- This file can be edited downstream. -->
<!DOCTYPE topic
[
  <!ENTITY % entities SYSTEM "../common/generic-entities.ent">
    %entities;
]>
<!-- refers to legacy doc: <add github link to legacy doc piece, if applicable> -->
<!-- point back to this document with a similar comment added to your legacy doc piece -->
<!-- refer to README.md for naming conventions -->
<!-- metadata is dealt with on the assembly level -->
<topic xml:id="glue-example"
 role="glue" xml:lang="en"
 xmlns="http://docbook.org/ns/docbook" version="5.2"
 xmlns:its="http://www.w3.org/2005/11/its"
 xmlns:xi="http://www.w3.org/2001/XInclude"
 xmlns:xlink="http://www.w3.org/1999/xlink"
 xmlns:trans="http://docbook.org/ns/transclusion">
  <info>
    <title>Performing Task XYZ</title><!-- can be changed via merge in the
    assembly -->
    <!-- add author's email address -->
    <meta name="maintainer" content="" its:translate="no"/>
    <!-- add an abstract/para here, if you need one -->
    <!-- can be changed via merge in the assembly -->
  </info>
  <!-- This is an example of how a glue topic would look like. If your task contains a large number of independent subtasks, make sure to include the glue topic to provide a means of navigation and to tie them together -->
  <para>
    The following sections describe how to perform task XYZ. They are arranged
    in the sequence of a common workflow, but you can also perform most of them
    independently, if the prerequisites are in place.
  </para>
  <!-- As long as there is no linking framework in place, use web links here -->
  <itemizedlist>
    <listitem>
      <para>
        A
      </para>
    </listitem>
    <listitem>
      <para>
        list of links
      </para>
    </listitem>
    <listitem>
      <para>
        to possible subtasks
      </para>
    </listitem>
  </itemizedlist>
</topic>