.. include:: /Includes.rst.txt

.. _typoscript:

==========
TypoScript
==========

At the section :ref:`include-site-set` you have already added the TypoScript by
depending on the site set.

The TypoScript of the site set includes files located
in the directory :file:`EXT:fluid_styled_content/Configuration/TypoScript/`.

.. figure:: /Images/ExternalScreenshots/TypoScriptFileStructure.png
   :alt: Structure of the TypoScript files

   Structure of the TypoScript files

In this folder there are two files:

*   :file:`constants.typoscript` - This file is only used when for compatibility
    reasons the TypoScript is included via import or `TypoScript` module in the
    outdated fashion.
*   :file:`setup.typoscript` - This file will first include some other files
    which are located in the :file:`Setup/` folder in the same directory. More
    about these files later.

In the folder :file:`ContentElement/` there are files which are included by the file
:file:`setup.typoscript` as mentioned above. These files contain the rendering definitions of all
content elements that are provided by the TYPO3 Core. These are:

-   :file:`Bullets.typoscript` - Configuration for content element "Bullet List"

-   :file:`Div.typoscript` - Configuration for content element "Divider"

-   :file:`Header.typoscript` - Configuration for content element "Header Only"

-   :file:`Html.typoscript` - Configuration for content element "Plain HTML"

-   :file:`Image.typoscript` - Configuration for content element "Image"

-   :file:`List.typoscript` - Configuration for content element "General Plugin"

-   :file:`MenuAbstract.typoscript` - Configuration for content element "Menu of subpages of selected pages including abstracts"

-   :file:`MenuCategorizedContent.typoscript` - Configuration for content element "Content elements for selected categories"

-   :file:`MenuCategorizedPages.typoscript` - Configuration for content element "Pages for selected categories"

-   :file:`MenuPages.typoscript` - Configuration for content element "Menu of selected pages"

-   :file:`MenuRecentlyUpdated.typoscript` - Configuration for content element "Recently updated pages"

-   :file:`MenuRelatedPages.typoscript` - Configuration for content element "Related pages (based on keywords)"

-   :file:`MenuSection.typoscript` - Configuration for content element "Section index (page content marked for section menus)"

-   :file:`MenuSectionPages.typoscript` - Configuration for content element "Menu of subpages of selected pages including sections"

-   :file:`MenuSitemap.typoscript` - Configuration for content element "Sitemap"

-   :file:`MenuSitemapPages.typoscript` - Configuration for content element "Sitemaps of selected pages"

-   :file:`MenuSubpages.typoscript` - Configuration for content element "Menu of subpages of selected pages"

-   :file:`Shortcut.typoscript` - Configuration for content element "Insert records"

-   :file:`Table.typoscript` - Configuration for content element "Table"

-   :file:`Text.typoscript` - Configuration for content element "Regular Text Element"

-   :file:`Textmedia.typoscript` - Configuration for content element "Text and Media"

-   :file:`Textpic.typoscript` - Configuration for content element "Text and Images"

-   :file:`Uploads.typoscript` - Configuration for content element "File Links"

Since we move away from TypoScript as much as possible, these rendering
definitions only declare the following:

-   Can :ref:`FLUIDTEMPLATE <t3tsref:cobj-fluidtemplate>` be used immediately or
    do we need data processing first?

    A processor is sometimes used to do some data manipulation before all the data is sent
    to the Fluid template.

-   Assigning the Fluid template file for each type of content element separately.

In the folder :file:`Helper/` there are files which are included by the file
:file:`setup.typoscript` as mentioned above. These are:

-   :file:`ContentElement.typoscript` - Default configuration for content
    elements using :ref:`FLUIDTEMPLATE <t3tsref:cobj-fluidtemplate>`

-   :file:`ParseFunc.typoscript` - Creates persistent ParseFunc setup for non-HTML content