Creating a new guide - RedHatInsights/red-hat-ansible-automation-platform-documentation GitHub Wiki
This checklist helps you remember the files, directories, and symbolic links you need to set up when you are adding a new guide to the docset.
Create directories in the repo:
-
β Create a directory for the main book:
/titles/aap-on-azure
-
β Create a directory for the assemblies:
/assemblies/aap-on-azure
-
β Create a directory for the modules:
/modules-aap-on-azure
Create symlinks so that itβs easy to include modules and assemblies in a book. Use tab autocompletion to get the right path for your symlinks.
-
β In
/titles/aap-on-azure
, create a symlink to theassembly
directory (/assemblies/aap-on-azure
) -
β in
/titles/aap-on-azure
, create a symlink to theattributes
directory (/attributes
) -
β in
/titles/aap-on-azure
, create a symlink to theimages
directory (~/<path_to_your_repo>/downstream/images
) -
β in
/titles/aap-on-azure
, create a symlink to theaap-common
directory (~/<path_to_your_repo>/aap-common
)
The AAP on Azure doc uses new directories for assemblies and modules. Add a symbolic link in the new assemblies directory to point to the modules directory.
-
β In
/assemblies/aap-on-azure
, create a symlink to themodules
directory (/modules/aap-on-azure
)
Add content:
-
β Add new Ansible on Azure aliases to
/attributes/attributes.adoc
-
β Create
titles/aap-on-azure/master.adoc
-
β Create
titles/aap-on-azure/docinfo.xml
-
β Create an assembly and a couple of modules. You can use newdoc to generate pre-populated module and assembly files formatted with AsciiDoc. Use the
include
statement to include them in the guide.
# Navigate to `titles/aap-on-azure`.
# Create symlinks to the `/assemblies`, `/attributes, `/common`, and `/images` directories :
$ ln -s ../../assemblies/aap-on-azure ./aap-on-azure
$ ln -s ../../attributes ./attributes
$ ln -s ../../images ./images
$ ln -s ../../../aap-common ./aap-common
# Navigate to assemblies/aap-on-azure. Create a symlink to the modules directory for AAP on Azure:
$ ln -s ../../modules/aap-on-azure ./aap-on-azure
The title/aap-on-azure
directory structure after these changes:
β /titles/aap-on-azure/
$ tree -l .
.
βββ aap-on-azure -> ../../assemblies/aap-on-azure
β βββ aap-on-azure -> ../../modules/aap-on-azure
β β βββ con-about-aap-on-azure.adoc
β β βββ con-why-aap-on-azure.adoc
β βββ assembly-intro-to-aap-on-azure.adoc
βββ attributes -> ../../attributes
β βββ attributes.adoc
βββ aap-common -> ../../../aap-common
β βββ making-open-source-more-inclusive.adoc
βββ docinfo.xml
βββ master.adoc
βββ images -> ../../images
β βββ aap-on-azure-architecture.png
β βββ <# Snipped list of image files for clarity>
β βββ security-lab-environment.png
The High Availability doc uses assemblies and modules from the pre-existing assemblies/hub
and modules/automation-hub
directories.
This means that you do not need to add a symlink in the assemblies directory to point to the modules directory.
Note that the High Availability title directory (/titles/hub/high-availability/
) is at a deeper nested level than the AAP on Azure title (titles/aap-on-azure/
). The paths in the symlinks are therefore different. Use tab autocompletion to get the right path for your symlinks.
# Navigate to the `/titles/hub/high-availability/` directory.
# Create symlinks to the `/assemblies`, `/attributes` `/common`, and `/images` directories :
$ ln -s ../../../assemblies/hub ./hub
$ ln -s ../../../attributes ./attributes
$ ln -s ../../../images ./images
$ ln -s ../../../../aap-common ./aap-common