Apps

MadCap IXIA CCMS with Markup AI Chrome Extension

Integration Guide

Check, score, and fix your DITA content without leaving MadCap IXIA CCMS. The Markup AI Chrome extension reads the topic you’re editing, flags the issues it finds, and applies the fixes you accept straight back into the editor.

Checks run against the brand standards your organization has configured in the Markup AI console — the same standards enforced everywhere else you write.


What you need

  • Access to your organization’s MadCap IXIA CCMS instance.
  • Google Chrome.
  • A Markup AI account. Don’t have one yet? Create your organization at the Markup AI console.
  • Permission to install Chrome extensions. If your browser is managed by your organization, an admin may need to deploy it first.

Which agents are supported

  • Style Agent

What Markup AI does for you in MadCap IXIA CCMS

  • Check & score: Analyze the DITA topic you’re editing and get a Content Risk level plus a Style Agent score for that topic.
  • Issues highlighted in the editor: Flagged text is color-coded by severity right in your topic, so you see every finding in context.
  • Apply a fix in place: Accept a suggested rewrite and the extension writes it straight back into the topic — saved the same way as any edit you make by hand.
  • Comment for a reviewer: Attach a comment carrying the finding to the flagged text so someone else can follow up on it.
  • Results that persist: Issues, scores, and highlights are saved per topic, so you can close and reopen the panel without losing your place.

Installing the extension

There are two ways to get the extension: install it yourself from the Chrome Web Store, or have an admin deploy it across your organization.

Option 1: Install it yourself

1

Open the Chrome Web Store listing

Open the Markup AI extension on the Chrome Web Store.

2

Add the extension

Select Add to Chrome, then Add extension in the confirmation dialog.

3

Pin it to the toolbar

Select the puzzle-piece (Extensions) icon in the toolbar and pin Markup AI so the icon stays visible.

Option 2: Deploy to your organization (admins)

If you manage Chrome through the Google Admin console, you can force-install the extension for your users:

1

Open Apps & extensions

Go to Devices → Chrome → Apps & extensions → Users & browsers.

2

Select the organizational unit

Select the organizational unit to deploy to.

3

Add the extension by ID

Select + (Add) → Add Chrome app or extension by ID and enter the extension ID:

abfamcopbgmiehgnnjchnkaikmejpgag
4

Set the installation policy

Set the installation policy to Force install (or Force install + pin to toolbar), then Save.

Deployed settings can take some time to reach managed browsers. For full details, see Google’s guide to installing apps and extensions.


Grant access to your IXIA CCMS instance

MadCap IXIA CCMS runs at a domain that’s specific to your organization — hosted instances live under ixiasoft.com, and on-premise instances use your own company domain. Because the extension can’t know your instance’s address in advance, it asks for permission the first time you open the side panel there.

A DITA topic open in the MadCap IXIA CCMS editor with the Markup AI panel alongside it, prompting for permission to access the site with a Grant Access button.
Select Grant Access to let the extension connect to your CCMS instance.

Launching Markup AI in a document

  1. Open a DITA topic for editing in MadCap IXIA CCMS.
  2. Open the side panel by selecting the Markup AI icon from the toolbar or your pinned extensions.
  3. Select Log In and sign in with your account credentials, through Google or Microsoft authentication, or your organization’s single sign-on. Your sign‑in persists for future sessions.
  4. Pick your team’s Style Guide from the dropdown, then select Check. Issues are scored and highlighted right in your topic, and you can act on them in place.

Reviewing and resolving issues

Each issue shows the agent that found it, a severity badge, the flagged text, and an explanation — and the text is highlighted in your topic, color-coded by severity. Select an issue’s text to jump straight to the matching content in the editor.

Working through an issue card

For each issue you can:

  • Apply Change — replace the flagged text with the suggested fix, written straight into the topic.
  • Add Comment — attach a comment with the finding to the flagged text so a reviewer can follow up.
  • Mark as Resolved — available when an issue has no one-click fix; use it to clear an issue once you’ve handled it yourself.
  • Dismiss — set an issue aside without changing your topic.
The Markup AI panel listing issues by category next to a DITA topic, with one Spelling and Grammar issue open in the editor showing its explanation, suggestion, and an Apply Change button.
Issues grouped by category in the panel, with the selected issue opened in the topic.

Results are saved per topic, so you can close and reopen the panel without losing your place.

Your brand standards are all managed in the Markup AI console; the extension checks against whatever your organization has configured.


FAQ

  • Why is the extension asking for permission to my CCMS site? Your IXIA CCMS instance runs on a domain specific to your organization, which the extension can’t know ahead of time. Granting access the first time lets it connect the side panel to your editor. It’s a one-time grant per instance.
  • Will the extension change my topic without asking? No. It only edits your topic when you choose Apply Change. Because edits are written directly into the editor, they’re saved the same way as any change you make by hand.
  • Can I check a DITA map? You can run a check on a map, but it only covers the text in the map file itself. The extension doesn’t resolve the map, so the content of the topics it references isn’t included — that’s why maps are listed as not supported yet. To check that content today, open each topic and run a check there.
  • Do I need to update the extension? No. When a new version is released, Chrome updates the extension automatically — you’ll always be on the latest version.
  • The panel shows “Unable to connect to page” — what should I do? Reload the topic and the extension will reconnect.

Known limitations

  • Checks run against a single DITA topic at a time — DITA maps aren’t supported yet.
  • Content pulled in by reference (for example, conref’d content from another topic) is not covered by a check.
  • Checks cover text content; images and other non-text elements aren’t analyzed.