IRIS
Dashboard / eon.com — Setup map

eon.com — Setup map

The whole setup of this client on one page, in plain words.

Follow the arrows: content is written in a content system, prepared by a series of transformers, and delivered to websites and apps. The content blueprints at the bottom describe what each kind of content block contains.

eon.com gets its content from 1 source, prepares it in 4 steps and has no delivery channel registered. Its content follows 1 blueprint.

What the status labels mean
  • On — working, or tested successfully
  • Not tested yet — on, but its connection was never checked
  • Failed — the last connection test did not succeed
  • Switched off — set up, but not in use
  • Not used here — only applies to another kind of source

  1. Sources

    Content comes in here.

    Content systems

    Where editors write the content.

    • Contentstack

      Pulls content from Contentstack for every page that no other source is set up for.

      • Connection: eon-com (Nova)
      On · last test OKMain sourceManage

  2. Transformers

    Content is prepared here, step by step from top to bottom.

    Step 1Built-in steps

    Run on every page, in this order.

    • Standard component types

      When a page component is a customised copy of a standard component, treats it as the standard one so the website can display it. Only affects content from AEM.

      Always on

    • Layout containers

      Turns AEM's layout areas — the boxes that hold a page's building blocks — into simple containers the website understands.

      Always on

    • Navigation menu

      Builds the website's navigation menu — main links, logos, top-bar links and drop-down panels — from AEM's navigation component.

      Not used here — no AEM source

    • Public page addresses

      Rewrites internal page addresses inside the content (links, images, navigation) into the public web addresses visitors see, using this client's address rules.

      Always on

    • Schematic transformers

      Sends each block to the add-on services its building block asks for — for example a tone-of-voice rewrite — before the page is delivered.

      Always on

    • Field name spelling

      Renames the field names in AEM content into the spelling the website expects. Runs last, after every other step.

      Not used here — no AEM source

    Step 2Plugins

    Add-on services run by other teams.

    No plugins are connected — content goes out exactly as the built-in steps prepared it.

    Step 3Combined pages

    Only for the page addresses listed.

    No combined pages are set up — every page comes straight from one source.

  3. Delivery channels

    Finished pages go out here.

    Web addresses

    The host names visitors type; each belongs to one environment.

    No web address is registered yet — visitors cannot reach this client by its own host name.

    Websites and apps

    Where visitors see the result.

    No delivery channel is registered yet — pages can still be fetched directly.

Content blueprints (Schematics)

Each blueprint defines what one kind of content block contains. Sources, steps and websites all follow them.

Page addresses: 0 address rules and 0 redirects are set up. See routing