anchor.diff:  
   == Versioning
   
  -The wiki uses branches for versioning. The current branch being used for the jMonkeyEngine is *always* the master branch of the wiki. This means you use the previous branch of the jMonkeyEngine for the new versioned branch name. If the current *wiki version* is targeting 3.3 and you are creating a new version, then the new version branch would be v3.3. Branch version names should only target major/minor releases, not the patch of a version.
  +There are two files that control versioning for the wiki, each serves a different purpose.
  +
  +. `wiki-playbook.yml` - determines what branches to use for content.
  +. `antora.yml` - controls module versioning.
  +
  +The wiki uses branches for versioning. The current branch being used for the jMonkeyEngine is *always* the master branch of the wiki.  In the playbook this is known as the `*HEAD*` branch.
  +
  +The `docs` module is the main module for the wiki. Its `antora.yml` file controls the version of the wiki. The playbook uses this version to create the folders inside the `gh-pages` branch, building the content from the branches configured in the playbook.
  +
  +Branch version names should only target major/minor releases, not the patch of a version and start with "`v`".
   
   When it's time to cut a new version for the wiki, the process is as follows.
   
  -IMPORTANT: A component module is a module that has an `antora.yml` file. A named module lives inside a component module. The version in the `antora.yml` file controls the version for the component module i.e. the wiki, not the version in the `wiki-playbook.yml`.
  -
  -We do not want the Antora cache to be versioned so you need to either remove the cache from the master branch before creating the new version branch or delete it after creating the new version branch.
  -
  +. We do not want the Antora cache to be versioned so you need to either remove the cache from the master branch before creating the new version branch or delete it after creating the new version branch.
  ++
   .How to remove first
  -. From the `Commit Packages` command in the main.yml workflow, located in the `.github/workflows` directory, remove the cache part from the `add:` line.
  +.. From the `Commit Packages` command in the main.yml workflow, located in the `.github/workflows` directory, remove the cache part from the `add:` line.
   +
   ```
   # Commits these files to root if and only if there are changes.
   add: "package-lock.json package.json ./.cache/antora/*"
   ```
  -. Next, delete the `.cache` folder.
  -. Stage, commit and push your changes to the repository.
  -. Create a new branch that matches the *current version* of the wiki. If master is currently targeting 3.4 for example, that would mean the branch name would be v3.3.
  +.. Next, delete the `.cache` folder.
  +.. Stage, commit and push your changes to the repository.
  +. Create a new branch that matches the *current version* of the wiki. If the current version (HEAD) is targeting version 3.3 in the `antora.yml` for example, and you are creating a new version, you would name the new branch v3.3. Thereby preserving the current master branch content.
  +. If you didn't remove the cache during step one, delete it from the newly created branch.
   . Push the branch to the repository.
   . On the `master` branch, edit these files:
   .. Add the newly created branch to the `branches:` array in wiki-playbook.yml.
  
positive.code: 
  ...
  ----
  
  .Updated jmonkeyengine.json
  [source, .json]
  ----
  
negative.code: title: JME
  version: '3.4'
  ```
  .The docs-wiki antora.yml
  ```
  name: docs-wiki
  