---
title: "TypoScript"
manual: "Universal Messenger"
version: "main"
permalink: "https://docs.typo3.org/permalink/universal_messenger:configuration-typoscript@main"
source: "Configuration/TypoScript.rst"
rendered: "2026-10-07T12:03:11+00:00"
---

# TypoScript {#configuration-typoscript}

The extension's default TypoScript (the newsletter preview page type, the
plugin and the content element configuration) is loaded automatically, see
[Site configuration](https://docs.typo3.org/permalink/universal_messenger:installation-site-configuration@main). Two further static templates
render the actual newsletter markup and are **required** for newsletters
to work, they are not loaded automatically.

## Fluid content elements {#configuration-typoscript-fluid-content-elements}

Provides the Fluid rendering used for the newsletter view and the
newsletter container template. Without it, the backend preview and the
dispatch to Universal Messenger have no template to render.

On classic (`sys_template` based) sites, go to the **Web >
Template** module, select **Edit TypoScript Record**, then
**Edit the whole TypoScript record**. On the **Advanced
Options** tab, add `Universal Messenger: Fluid Content Elements` to the
list of included static templates.

On Site Set based sites, the same TypoScript is already imported by the
`netresearch/universal-messenger` Set, no extra step is needed.

-   **inlineCssFiles**

    -   *type:* TypoScript array
    -   *Default:* `EXT:universal_messenger/Resources/Public/Css/ZurbFoundation.css`
    -   *Path:* plugin.tx_universalmessenger.settings.inlineCssFiles

    Additional CSS files that are inlined as `style` attributes into the
    respective HTML elements when a newsletter is rendered, in addition to
    the [Foundation for Emails 2](https://get.foundation/emails.html) base CSS the extension already
    includes by default.

    **Add a project-specific CSS file**

    ```typoscript
    plugin.tx_universalmessenger {
        settings {
            inlineCssFiles {
                10 = EXT:universal_messenger/Resources/Public/Css/ZurbFoundation.css
                20 = EXT:your_sitepackage/Resources/Private/Css/Newsletter.css
            }
        }
    }

    module.tx_universalmessenger < plugin.tx_universalmessenger
    ```

    The backend module preview uses `module.tx_universalmessenger`, keep
    it in sync with the frontend plugin setup as shown above.

    > [!NOTE]
    > Some HTML elements used by the bundled Fluid partials are not
    > reset by the shipped `ZurbFoundation.css`, nor by browser
    > default stylesheets. For example, the `Textpic`/`Media`
    > partials render images inside `<figure>`, and browsers apply a
    > default margin to it (Chrome: `margin: 1em 40px`) that
    > Foundation for Emails never resets, since its own image
    > component is class-based (`.thumbnail`) rather than built on
    > `<figure>`. This shrinks the image's content box and can make
    > a `width: 100%` image rule look "too narrow" compared to the
    > surrounding text column. If you hit this, add your own reset
    > (for example `figure { margin: 0; }`) to your own
    > `inlineCssFiles` entry, other elements may need the same
    > treatment depending on your design.

## Example newsletter template {#configuration-typoscript-example-newsletter}

Provides an example newsletter backend layout and page template as a
starting point for a project-specific newsletter design.

On classic sites, include the static template \``Universal Messenger:
Example Newsletter Template`\` the same way as above. On Site Set based
sites it is imported together with the Fluid content elements template.

Open the page where the layout should apply, switch to the page
properties **Resources** tab, and add \``Universal Messenger:
Backend Layout`` to the :guilabel:`Page TSconfig` selection. The layout is
then selectable on the page's :guilabel:`Layout\` tab.