This repository contains the documentation for the Amplify Open Banking solution. It follows the docs-as-code approach currently used by Axway for publishing product documentation.

This overview outlines the main points of note in that context with some "Getting Stared" style sections for making developers as productive as possible.

Note the expectation is that a user of this repository is very familiar with using git, GitHub and the process of source controlling configuration items. The docs-as-code approach is an extension of those practices.

It's pretty simple. Ensure you have the following installed:

• Hugo.
• git.
• Node.js/NPM.

Then clone the repository and run build.sh to start a local server:

git clone https://github.com/Axway/open-banking-docs
cd open-banking-docs
./build.sh

The development server is by default hosted at http://localhost:1313.

All content is created in the content/en/docs directory as shown below.

content
| -- en
|    | -- docs
|    |    | -- deployment
|    |    | -- overview
|    |    |    | -- integration
|    |    |    | -- technical
|    |    | -- reference
|    |    |    | -- brazil

To explain the directories:

The process for adding new content to an existing directory is simple:

• Add a file to the relevant directory. For example, to add a new integration subpage create a file called example.md in content/en/docs/overview/integration
• Add Front Matter to the page as described below and add content in Markdown format below the Front Matter.
• To add an that cannot be referenced remotely copy the image to the static/Images.
• To add a sequence diagram follow the guidelines in the PlantUML section.

To create new content in a new directory:

• Create the new directory in the correct place in the directory structure.
• Create a new Markdown file called _index.md in the new directory. This creates the overview page that links all subpages within the new directory.
• Add Front Matter to _index.md and some content that introduces the section.
• Follow the guide above for creating a new page in an existing directory.

All sequence diagrams are written using PlantUML syntax. This is a text-based language that is transformed to a display format by the PlantUML Java Library.

While there are solutions that support the real-time rendering of native PlantUML content this does not appear to be supported by our current docs-as-code stack. The PlantUML must therefore be converted to SVG and stored as an image as follows:

• Convert the source PlantUML file using a converter of your choice or the conversion script in this repository. Note to use this you must have plantuml.jar installed locally.
• Copy the SVG file to static/Images.

This section is for guidance only

Front Matter is the metadata that informs Hugo/docsy about the characteristics of the page being loaded. It is a series of key/value pairs that can be expressed in a number of formats - in the case of Axway Open Docs, in YAML.

An example of Front Matter is shown below (note this is not exhaustive and there are many more keys available in both Hugo and the docsy theme):

---
title: "Deployment"
linkTitle: "Deployment"
weight: 4
description: Deploying the Amplify Open Banking solution
---

The keys in this example are defined as follows:

• title: Sets the page title.
• linkTitle: Sets the name of any links to the page rendered in the sidebar or by a parent page.
• weight: Sets the ordering of the page in the sidebar - a lower number displays the page in the navigation list first while a higher number displays the page in the navigation list last. To avoid renumbering existing pages when a new page is added, it is suggested to spread the numbers used for the weight out by increments of 5 or more.
• description: Description of the page, which is rendered on the page under the title.

Its worth noting that both title and description provide a useful introduction to a given page, so should be used rather than Markdown content containing the same thing. This looks neater and stops repetitive content being served.

To date this project implements GitHub Flow, which is a simple and easy-to-use method doing documentation updates.

The outline process is as follows:

• The relevant subject matter expert creates a new branch and starts work on their changes.
• When they are happy they commit and push to the branch.
• They then create a Pull Request. The technical writer then reviews and suggest changes, etc.
• When approved the changes are merged to master.
• The final step is a merge to production, which does not necessarily need to be performed at each merge to master on GitHub. This happens through a manual push to Zoomin, the production provider for https://docs.axway.com.

Production is handled by the technical writer assigned to the project.