Confluence developer-oriented wikis

Redacted screenshots of the Confluence wiki spaces for which I was responsible at EIS Group. The wikis hosted documentation for B2B insurance technology (over 50,000 pages).

1 / 8 ×
Architecture topic
2 / 8 ×
Example wiki space home page
3 / 8 ×
Example wiki space home page
4 / 8 ×
Documentation hub
5 / 8 ×
Functional documentation
6 / 8 ×
Developer recipe registry
7 / 8 ×
Technical reference section
8 / 8 ×
Technology stack topic

Single-source projects

These files (a redacted PDF and screenshots of two HTML Help files) are from one of the many single-source projects that I have set up. They were created from the same source in MadCap Flare.

Click the first thumbnail to open the PDF inside an iframe on this page. Click the second and third thumbnails to see screenshots of HTML Help files created from the same source as the PDF.

1 / 8 ×
chm 1
2 / 8 ×
chm 2

API Documentation

As well as completing the full "Documenting APIs" hands-on course by Tom Johnson, at EIS Group, I managed a comprehensive audit of the API documentation for a B2B insurance product suite (Policy, Billing, Claims). The audit resulted in consistent terminology and clearer descriptions for over 100 Swagger/JSON schemas. Rather than editing swagger files in isolation, I used an Excel-based approach to facilitate cross-file edits:

  1. API Style Guide: Created a style guide for API descriptions to ensure consistency.
  2. Schema Extraction: Imported swagger.JSON schemas to Excel.
  3. Editorial Review: Reviewed and edited endpoint descriptions as needed.
  4. Developer Feedback: Provided "Clean-JSON" exports to the engineering team for direct integration into the build pipeline.
workflow for API review/edit process

Enterprise Documentation

This section shows...

User and configuration guides

These files show a few of the many user and configuration guides that I have created. These ones were created using MadCap Flare.

Click a thumbnail to open the redacted PDF inside an iframe on this page.

1 / 3 ×
configuration guide PDF
2 / 3 ×
product user guide PDF
3 / 3 ×
product user guide PDF
Release Notes

These files show a glimpse of my involvement in the creation of release notes:

  • The first file is a Release Notes PDF created using MadCap Flare
  • The other files are screenshots of release note pages from a Confluence/Scroll portal

Click the first thumbnail to open the redacted PDF inside an iframe on this page. Click any other thumbnail to display the screenshot.

1 / 6 ×
Release Notes PDF
2 / 6 ×
Confluence release notes topic
3 / 6 ×
Confluence release notes topic
4 / 6 ×
Confluence release notes topic
5 / 6 ×
Confluence release notes topic
6 / 6 ×
Confluence release notes topic
Product updates & reference guides

These files show a glimpse of my involvement in the creation of product updates and technical reference guides:
      • The first file is a product update PDF created using MadCap Flare.
      • The second file is a reference guide PDF created using MadCap Flare
      • The third file is a screenshot of a technical reference section in Confluence

Click the first and second thumbnails to open the redacted PDFs inside an iframe on this page. Click the third thumbnail to display the screenshot.

1 / 2 ×
Technical Reference PDF
2 / 2 ×
Technical reference in Confluence
Cheat sheets

This file shows a "Quick Guide" cheat sheet for ICU Nurses. It was created using MadCap Flare. (I used the same source to generate cheat sheets for other audiences, such as Surgeons and Anesthetists.)

Click the thumbnail to open the redacted PDF inside an iframe on this page.

Integration of product and training documentation

These PDFs were created using FrameMaker and PowerPoint. They are user guides and training material created from the same source. We referred to this as "Training-in-a-Box".

Click a thumbnail to open the redacted PDF inside an iframe on this page.

Portals built with Confluence K15t Scroll addon

This section shows redacted portal prototypes that I created at EIS Group using the K15t Scroll addin for Confluence. Topics are authored in Confluence, but rendered as traditional web portals. Conditions are used to create multiple portal versions from a single source (spread across multiple wiki spaces). Customers are provided access to a specific high-level portal and from there can access multiple sub-portals.

Architecture diagrams

These diagrams (redacted) were used to design the system. They were created using LucidChart to show the sub-portals needed by each client portal. For brevity, only two of the six client portals are shown here. Orange and green sections indicate the key product suites. Rectangles inside these sections are sub-portals for the constituent products. Each sub-portal is created from its own Confluence wiki space using the K15t Scroll addin. Versioning is available for each wiki space. Content from each sub-portal is shown conditionally depending on the package.

1 / 2 ×
Clients on package 1
2 / 2 ×
Clients on package 2
High-level portals

Redacted screenshots of two high-level portals. Each customer group has access to a specific high-level portal from which they can access multiple sub-portals.

1 / 2 ×
Portal 1
2 / 2 ×
Portal 2
Low-level portals

Redacted screenshots of a few low-level portals (sub-portals). Each sub-portal has an associated Confluence wiki space.

1 / 3 ×
Glossary sub-portal
2 / 3 ×
Release notes sub-portal
3 / 3 ×
Sub-portal for one product in a package

Android development

The files at the bottom of this section are screenshots of an Android app that I created in Spring 2026 as part of a personal project. The app is available here in the Google Play Store:

https://play.google.com/store/apps/details?id=com.adrianmorse.mnemonixrussian

You can also use this QR code to install it on your phone:

Although the app does not fall within the scope of technical writing experience I am including it in my portfolio to give an indication of my technical abilities and my aptitude for learning. Before creating the app I took the Google Developer "Android Basics with Compose" course focussing on Android Studio, Kotlin and Compose.

About the app

The app is called Mnemonix — Russian and is a language-learning flashcard app focussed purely on Russian vocabulary. It is loaded with the 1000 most-frequent Russian words. Unlike other flashcard apps for language learning in Google Play Store, Mnemonix — Russian allows the user to enter their own mnemonic notes to help remember words. This is particularly useful for learners of Russian whose native language does not use the Cyrillic alphabet, such as native English speakers. (Context: I began learning Russian in 2021 because it was the native language of most employees in my company.)

The screenshots show the following:

  • App logo
  • Splash screen
  • Onboarding screen shown on first use
  • Main screen showing word list
  • Flashcard screen - Russian word
  • Flashcard screen - English translation
  • Flashcard screen - Viewing/editing a mnemonic note
  • Hidden words screen
  • Settings screen

It took me 10 days to create the app, plus two days handling the Play Store submission and incorporating tester feedback.

While waiting for testing to complete I also set up a partial web demo version by migrating the app to a kotlin multiplatform setup. (Because the web version is only for demos, any user-entered notes are not retained on closing or refreshing the page.)

https://docu-mental.github.io/MnemonixRussianDemo/

Companion Java app

As a companion project, I built a Java console-based flashcard app using IntelliJ IDEA, which can be found on GitHub:

https://github.com/Docu-Mental/Russian-Flashcards-Java-Project

1 / 9 ×
logo
2 / 9 ×
splash screen
3 / 9 ×
main screen
4 / 9 ×
main screen
5 / 9 ×
flashcard - Russian
6 / 9 ×
flashcard - translation
7 / 9 ×
flashcard - mnemonic
8 / 9 ×
hidden words screen
9 / 9 ×
settings screen

Team Management

I have the following experience of managing teams:

  • I managed the Liquid Crystal Group of Manchester University Physics Dept for a year while the professor was on sabbatical. Besides overseeing several postdocs and PhD students I was also responsible for funding applications during this period.
  • I was the team lead for the Documentation Group in Picis (Barcelona) for five years (guiding a team of three).
  • I was the Documentation Group Manager at Picis for 10 years. During this team I managed employees in Chicago, Boston and Barcelona.
  • At EIS, I was in a management role for nearly five years. I managed employees in San Francisco, Texas, UK, Lithuania and (before sanctions) Belarus.

Internal process documentation

These files are PDFs that I created for internal audiences. (The third PDF relates to Virtual PC; I was the first to use virtual machines in the company and after I demonstrated them to the IT team they were rolled out to the developer and SQ departments.)

Click a thumbnail to open the redacted PDF inside an iframe on this page.

Localization

These documents highlight my involvement in localization projects.

  • A PDF of a presentation that I gave at a national tech writing conference in the UK regarding the automatic localization of screenshots.
    (The process that I devised saved the company (Picis) tens of thousands of dollars.)
  • My PhD. thesis in Spanish, which I personally translated.
  • Two PDFs showing a translation project that I worked on (Spanish to English).  (Note that I was asked to maintain the source formattting.)

Besides these examples, I also managed the whole localization process while working at Picis. I coordinated closely with the development team and contracted an agency to localize our UI strings and documentation/help source into 10 languages.

Click a thumbnail to open the PDF inside an iframe on this page.

My PhD. and associated publications

These files show my PhD thesis and other documentation that I wrote while working in the field of liquid crystal displays.

  • A proposal document for seting up a new university research unit in Alicante, Spain.
    (I was subsequently offered a lectureship.)
  • My PhD thesis (created with Microsoft Word)
  • An article I wrote for the Daily Telegraph 'Week in Science'.
  • An article I wrote for the New Scientist 'Science for All' week.
  • Peer-reviewed articles I wrote for scientific journals.

Click a thumbnail to open the PDF inside an iframe on this page.

My publications related to technical writing

These files highlight my involvement in the technical writing community:

  • Two articles that I wrote for "Communicator" – the magazine of the Institute of Scientific and Technical Communicators (UK).
  • Three talks that I have given at international tech writing conferences.

Click a thumbnail to open the PDF inside an iframe on this page.

Docs-as-Code | AI | Automation

Docs-as-code

I have set up the following Docs-as-code projects:

  • A documentation portal for the OpenL Tablets open-source project. I created the underlying GitHub repo, converted existing documentation to Markdown (using Writage), configured MkDocs as the static site generator publishing to Read-the-Docs, and established a Jira/Git process for contributions. (I spent two years on this project while at EIS Group.)

    Click thumbnail to open the portal

    Click thumbnail to open the GitHub repo

  • This portfolio, hosted in CloudFlare and sourced from a private GitHub repo.
AI for Release Notes Automation

As a personal learning project, I created an LLM-based release notes generator.
A Python script extracts Jira ticket data and converts it into structured Markdown release notes using the Claude API.

Click thumbnail to open the GitHub repo

Headless CMS (Storyblok)

As a personal learning project, I built a small headless CMS application using Storyblok and Next.js.

The project took me through a complete content workflow, from modelling structured content in Storyblok to retrieving it through the Content Delivery API and presenting it in a Next.js frontend.

While I designed the Storyblok content model and CMS configuration myself, I used AI as a development assistant for much of the Next.js implementation.

The application includes:

  • structured content models
  • relationships between routes and launch points
  • pages generated dynamically from Storyblok content
  • deployment to Vercel with continuous deployment from GitHub

The live demonstration and complete source code are available below.

https://storyblok-kayak-guide.vercel.app/

1 / 1 ×
Camunda 8 project

As a personal learning project, I built a simple documentation review and publishing workflow project with Camunda 8. You can find the project in GitHub.

The workflow allows an author to:

  1. Submit a Markdown document.
  2. Automatically validate the document against a list of prohibited terms.
  3. Transition the document to human review.
  4. Publish an approved document and record its published URL.
  5. Receive automated email notifications when correction or rejection is required.

The project combines Camunda Cloud/SaaS components with a small Python worker running on the local development machine.

While I designed the BPMN model, workflow and forms myself, I used AI to help with creating the python script.

The global workflow consists of three processing routes, as shown in the following videos.

Note that the videos do not have an audio track.


Flow 1 - prohibited terminology


Flow 2 - document passes terminology check, but fails review


Flow 3 - document passes terminology check, then passes review

About This Website

I created this website in November 2025 as follows:

  1. Set up a skeleton GitHub repo and configured it to create a corresponding "pages" website in CloudFlare
  2. Used Gemini to hunt for a HTML template for the main page based on high-level requirements. Obtained the 'Dimension' template from HTML5 Up.
  3. Used Google Chrome Developer Tools AI assistant to fix specific sizing issues in the main page template.
  4. Checked W3Schools. for ideas on creating image galleries. Combined code from the Tab Gallery, Scrollable Image Gallery and the Slideshow Gallery to make a scrollable tab gallery with image numbering, captions, and previous/next buttons.
  5. Added iframes for the sections that have PDFs.
  6. Used Gemini and ChatGPT to fix gallery and iframe issues and make improvements.

With the help of AI it took me four days to collate samples and create this site. Without AI it would likely have taken four weeks.

Note that this website has not been optimized for mobile devices.