/
How to Convert ARNR HTML Templates to Confluence Storage Format

How to Convert ARNR HTML Templates to Confluence Storage Format

Background

Atlassian has deprecated the legacy Confluence editor and is moving all content creation to the new editor experience.

Historically, ARNR (Automated Release Notes & Reports for Jira) allowed users to create Confluence templates using HTML within the ARNR Template Builder. These templates were then published to Confluence pages using the legacy editor.

To align with Atlassian's changes, ARNR now supports publishing pages directly using the Confluence New Editor, enabling users to leverage native Confluence macros and enhanced customization options.

The ARNR team is currently working on a native migration solution that will automatically convert legacy HTML-based Confluence templates into the Confluence storage format used by the new editor.

Until that solution is available, you can use the following DIY approach to convert your templates using Google Gemini Gems.

Important: No Jira data is shared with Gemini during this process. Only the template structure/source code is used for conversion. Variables and macros remain in template as it is and no project data is exposed.

Step 1: Create a Gemini Gem

  1. Open ‎Google Gemini

  2. From the left navigation menu, click Gems.

  3. Click New Gem.

image-20260618-195425.png

  1. Enter a suitable name and description for your Gem.

  2. In the Instructions section, paste the following prompt exactly as shown:

We have an app called Automated Release Notes & Reports for Jira (ARNR). This app has a template builder where users can create reusable templates for release notes and reports. The template builder stores the template body in HTML. The template contains a static text, variables, stat macro, JQL section macro and some other macros that contains logic to fetch specific information from Jira. For confluence, Atlassian announced deprecation of legacy editor and hence in the new method users create confluence templates right within confluence using ARNR's variables and macros. The data is stored in confluence's proprietary storage format. Many of the old users who had created confluence template in the legacy way (in HTML) now move to newer way of creating templates right within confluence. They want to find a way to auto-convert the source code of their legacy confluence templates (in HTML) to the confluence compatible storage format. Whenever you are provided with .txt file of HTML source code of legacy template you should follow the Readme and reference material in the knowledge and using that convert the HTML source code to corresponding confluence compatible source code (storage format) and provide output
image-20260618-195658.png

  1. Upload all the provided Knowledge Files below to the Gem.

  1. Click Save.

image-20260618-200504.png

Your Gem is now ready to perform template conversions.

Step 2: Get the HTML Source Code from ARNR

  1. Open the ARNR template that you want to convert.

  2. Click the Source Code button in the template editor toolbar.

image-20260618-200848.png

  1. Copy the complete HTML source code.

image-20260618-202154.png

  1. Paste the content into a text editor such as Notepad.

  2. Save the file with a .txt extension.

Example:

ReleaseNotesTemplate.txt

Step 3: Convert the Template

  1. Open your newly created Gemini Gem.

  2. Upload the .txt file containing the template source code.

image-20260618-202342.png

  1. Submit the file for processing.

  2. Gemini will generate the equivalent Confluence Storage Format compatible with the Confluence New Editor.

  3. Copy the generated output.

image-20260618-202448.png

Step 4: Create a New Confluence Template

You can now create a Confluence New Editor template using the generated storage format.

Since Confluence does not allow direct editing of a page's storage format, you can temporarily use our public Confluence instance to create and validate your template.

  1. Open the following Confluence instance:

    https://arnr-html-converter.atlassian.net/wiki/

  2. Create your own space in the instance.

  3. Create a new Confluence page and publish a blank page with only a title.

  4. Once the page is published, open the page and navigate to:

    ••• → Apps → Edit Storage Format

image-20260618-204426.png

  1. A blank storage format editor will open.

  2. Paste the storage format generated by the Gemini Gem into the editor and click Save.

image-20260618-204519.png

  1. Refresh the page to view the rendered content.

Your Confluence New Editor template is now ready to use.

Step 5: Move the Template to Your Own Confluence Instance

Once you have verified that the page renders correctly:

  1. Copy the page to your own Confluence instance.

  2. Validate the output in your environment.

  3. Delete the pages and spaces created in the public conversion instance.

Note: The public Confluence instance is intended only for template conversion and validation. Do not add confidential information or actual Jira data to pages created in this instance.

Ready to use your converted template? Check out our guide on integrating the Confluence New Editor with your instance.

  1. Checklist to publish release notes (in new Confluence editor) using ARNR Helper app

  2. Creating Confluence Template (New Editor)

  3. ARNR Specific macros (Confluence helper app macros)

Notes

  • This process converts only the template structure and ARNR macros.

  • No Jira issue, project, or report data is sent to Gemini.

  • Some complex custom HTML layouts may require minor manual adjustments after conversion.

  • ARNR migration tool is currently under development and will simplify this process in the future.

In case of any queries, please feel free to reach out to us via our Service desk.

 

 

 

copy the whole source code and save it in notepad as a .txt file

 

On this page

On this page