How to Plan and Build an AX Plugin Within a Third Party Environment (CMS, PIM, etc.)

AX Semantics relies on data to automate content. The common integration for data import is to connect a data storage application like a shop or PIM system to AX Semantics. Also quite common for content delivery is to extract the content to a CMS System. Both ways are fully automatable and can be covered by one plugin to provide an overall roundtrip for data management and content publishing.

The Roundtrip From Data to Content on the AX NLG Cloud

The standard case on how to implement AX Semantics via our API encompasses import from your data into our system, generation of content and export of the generated content back into your system: API Guideopen in new window

A few Tips in Regard to Handling Your Data

Now that the 3 necessary steps on the platform are clear from a technical standpoint, let’s see how to best shape the data sources environment on the AX NLG Cloud. In the data sources you have access to data containers, called “collections”.

How to structure your collectionsopen in new window

Starting to Implement the Roundtrip

Get your AX Semantics account by creating one here:

The trial period is three days. If you need more time to develop your plugin, please contact us via in-app chat to get your developer license.

On the platform, you can find your request token and links to the API documentation by going on your profile settings and selecting the menu entry “API Accessopen in new window”.

Next, it is mandatory to get a grasp on how the AX NLG Cloud works.

Go to the point “Learning” in your profile and go through the “AX Semantics Seminaropen in new window”.

Now that you have access to the API and an understanding on how the plugin might be designed, you are set for implementing the AX API Integration into your plugin.

Designing the Data Import

First of all, start with a full sync from your storage application to the AX Semantics platform. For that, create a Collection in your Project and import every dataset into that collection. When the data is imported for the first time, you can start to implement more (optional) advanced features for the data import:

  • That includes filtered exports from your PIM for different data subsets.
  • That includes importing different data subsets into different collections on the AX NLG Cloud.
  • That includes a highly flexible data model that can be altered regularly in composition and structure.

Please check back with your content manager whether one or more of these cases is necessary for the user of your customer.

Crafting a Data Model

The next step after the data import is the matching/processing of the data in the ruleset on the AX NLG Cloud. This should be done by yourself and by one of your colleagues from your content team. Here is a small guide on how the data model crafting should be pursued.

How to Craft Your Data Modelopen in new window

Implementing the Content Generation

The initial content generation is quite easy to implement. If you are using Collections or the direct API, every method comes equipped with an option to automatically trigger the generation of content when a dataset is imported for the first time. This also can be expanded to generate content whenever a dataset is changed. It is highly advisable to first concentrate on automatic content generation for your plugin. At a later stage it might be feasible to implement a content preview which would be implemented using our “direct APIopen in new window” for generation in real time.

Publishing the Generated Content

In a best case scenario, the generated content is then ready for publishing right after the content generation. In that case you can simply extract the generated content from webhook messages or the API response (direct API) and sort it into your system.

[Optional] Reviewing the Generated Content

This is an optional feature that implements a QA loop inside your plugin. Please check with your editorial colleagues whether this is necessary. These are (optional!) cases to keep in mind for the QA process of the automated content:

  • If the initial content is not meeting expectations, the returned content needs to be

    • A. Altered by hand or,
    • B. Regenerated.

    Please check with a colleague from content management if and how this feature should be build into your plugin. Regeneration of a single piece of content can be achieved with this API Callopen in new window.

  • The generated content needs to be stored for the editorial review, which is achieved by implementing draft and published collections. Depending whether your customers like the resulting content, there are four options to cover:

    • Discarding the piece of content (In case your ruleset is not producing adequate results yet).
    • Regenerating the piece of content (In case you wish to see a different composition for the generated content).
    • Saving the generated content to your system (In case you would like to revisit that certain result, or save manual changes).
    • Publishing the content to the intended platform (In case the review was completely successful).
  • The ruleset is always producing consistent results, in accordance to the defined rules. Mass operations are necessary:

    • Mass-Regenerationopen in new window (In case you want to apply, current changes to the ruleset to the respective batch of data)
    • Mass-Publishing (The final action when the content is matching your current requirements)

If these things are present in your plugin, the customer is highly autonomous during editorial review and publishing of the generated content.

Next Steps

That is an overview of the technical information and considerations that should greatly help you with building your new application with AX Semantics. If you need a second opinion or are stuck somewhere or have a finished puzzle piece that needs review, feel free to reach out and book a call with us.