TYPO3 v15 dev-main snapshot ()
This commit is contained in:
@@ -0,0 +1,35 @@
|
||||
.. include:: /Includes.rst.txt
|
||||
|
||||
.. _content-element-bullets:
|
||||
|
||||
===========
|
||||
Bullet list
|
||||
===========
|
||||
|
||||
.. include:: /Images/AutomaticScreenshots/ContentOverview/BulletTypicalPageContent.rst.txt
|
||||
|
||||
With this content element you can provide unordered and ordered bullet lists, but also a
|
||||
definition list, in the frontend.
|
||||
|
||||
|
||||
.. include:: /Images/AutomaticScreenshots/ContentElements/BulletsBackend.rst.txt
|
||||
|
||||
The type of list can be defined with the field :guilabel:`Type of bullets`.
|
||||
|
||||
The content is added in the field :guilabel:`Bullet List`, where each new line
|
||||
is a new bullet.
|
||||
|
||||
.. code-block:: none
|
||||
|
||||
Bullet 1
|
||||
Bullet 2
|
||||
Bullet 3
|
||||
|
||||
For definition lists you use one line for a single definition which starts with the term,
|
||||
followed by the description, separated by a vertical bar "|".
|
||||
|
||||
.. code-block:: none
|
||||
|
||||
Term 1|Description 1
|
||||
Term 2|Description 2
|
||||
Term 3|Description 3
|
||||
@@ -0,0 +1,12 @@
|
||||
.. include:: /Includes.rst.txt
|
||||
|
||||
|
||||
.. _content-element-div:
|
||||
|
||||
=======
|
||||
Divider
|
||||
=======
|
||||
|
||||
.. include:: /Images/AutomaticScreenshots/ContentOverview/DividerPageContent.rst.txt
|
||||
|
||||
Nothing more than a horizontal rule.
|
||||
@@ -0,0 +1,15 @@
|
||||
.. include:: /Includes.rst.txt
|
||||
|
||||
.. _content-element-header:
|
||||
|
||||
======
|
||||
Header
|
||||
======
|
||||
|
||||
.. include:: /Images/AutomaticScreenshots/ContentOverview/HeaderTypicalPageContent.rst.txt
|
||||
|
||||
.. include:: /Images/AutomaticScreenshots/ContentElements/HeaderBackend.rst.txt
|
||||
|
||||
The content element "Header" will render a header, which can be linked. There is the
|
||||
possibility to add a subheader and a date. The fields used for this content elements are
|
||||
the same as :ref:`content-elements-general-header`, but with a field for the subheader.
|
||||
@@ -0,0 +1,14 @@
|
||||
.. include:: /Includes.rst.txt
|
||||
|
||||
.. _content-element-html:
|
||||
|
||||
====
|
||||
HTML
|
||||
====
|
||||
|
||||
.. include:: /Images/AutomaticScreenshots/ContentOverview/HTMLPageContent.rst.txt
|
||||
|
||||
.. include:: /Images/AutomaticScreenshots/ContentElements/HtmlBackend.rst.txt
|
||||
|
||||
Insert HTML directly using this content element.
|
||||
|
||||
@@ -0,0 +1,116 @@
|
||||
.. include:: /Includes.rst.txt
|
||||
|
||||
.. _content-elements:
|
||||
|
||||
====================
|
||||
The content elements
|
||||
====================
|
||||
|
||||
.. include:: /Images/AutomaticScreenshots/ContentOverview/TypicalPageContent.rst.txt
|
||||
|
||||
This chapter describes the default set of content elements provided by TYPO3's
|
||||
Core. It will show you a description and screenshots of the backend fields.
|
||||
|
||||
.. _content-elements-general:
|
||||
|
||||
General fields
|
||||
==============
|
||||
|
||||
These are fields which are used by (almost) every content element.
|
||||
|
||||
|
||||
.. _content-elements-general-header:
|
||||
|
||||
Header
|
||||
------
|
||||
|
||||
Almost every content element can contain a header, which consists of the following parts:
|
||||
|
||||
Header
|
||||
The text of the header
|
||||
|
||||
Type
|
||||
The type of heading (heading 1, heading 2, heading 3 ... or if the header is hidden).
|
||||
When not choosing an option, the default heading will be used, which can be configured
|
||||
at :ref:`constant-editor`.
|
||||
|
||||
Date
|
||||
Have the possibility to group the header with a date
|
||||
|
||||
Link
|
||||
Link wrapping the header text. This can be a TYPO3 CMS page, an external page, an email
|
||||
address or a link to a file.
|
||||
|
||||
The header fields can be found in the :guilabel:`General` tab of a content element.
|
||||
|
||||
|
||||
.. include:: /Images/AutomaticScreenshots/ContentElements/HeaderBackend.rst.txt
|
||||
|
||||
|
||||
.. _content-elements-general-show-in-section-menus:
|
||||
|
||||
Show in Section Menus
|
||||
----------------------
|
||||
|
||||
Using this option will only be visible when using menu's based on sections. This will be
|
||||
described in the chapter :ref:`content-element-menu`.
|
||||
|
||||
This field can be found in the :guilabel:`Appearance` tab.
|
||||
|
||||
.. include:: /Images/AutomaticScreenshots/ContentElements/ShowInSectionMenus.rst.txt
|
||||
|
||||
A :guilabel:`Section Menu`, which is in turn a content element itself
|
||||
produces an output including the headlines of all content elements
|
||||
with the flag :guilabel:`Show in Section Menus` set.
|
||||
|
||||
.. _content-elements-general-link-to-top:
|
||||
|
||||
Append with Link to Top of Page
|
||||
-------------------------------
|
||||
|
||||
.. include:: /Images/AutomaticScreenshots/ContentElements/AppendWithLinkToTopOfPage.rst.txt
|
||||
|
||||
When checked, this will render a link below the content element to bring the visitor the
|
||||
top of the page. This will be very convenient for your visitors when having long pages.
|
||||
|
||||
.. _content-elements-general-access:
|
||||
|
||||
Access
|
||||
------
|
||||
|
||||
.. include:: /Images/AutomaticScreenshots/ContentElements/AccessTab.rst.txt
|
||||
|
||||
These fields define if and when a visitor has access to this content element. The access
|
||||
fields all reside in the :guilabel:`Access` tab:
|
||||
|
||||
Visibility of content element
|
||||
By checking this option the content element will not be visible to any visitor.
|
||||
|
||||
Publish Date
|
||||
The date on which the content has to be published, which means making visible at a
|
||||
certain date.
|
||||
|
||||
Expiration Date
|
||||
The date on which the content will be expired, which means the content will be hidden
|
||||
on a certain date
|
||||
|
||||
Usergroup Access Rights
|
||||
Here you can select whether the content element only is available to a certain
|
||||
frontend user group, if it has to be visible only when the visitor is logged in or if
|
||||
it has to be hidden at a login.
|
||||
|
||||
.. toctree::
|
||||
:maxdepth: 5
|
||||
:titlesonly:
|
||||
:glob:
|
||||
|
||||
Header/Index
|
||||
TextMedia/Index
|
||||
Bullets/Index
|
||||
Table/Index
|
||||
Uploads/Index
|
||||
Menu/Index
|
||||
Shortcut/Index
|
||||
List/Index
|
||||
Div/Index
|
||||
Html/Index
|
||||
@@ -0,0 +1,18 @@
|
||||
.. include:: /Includes.rst.txt
|
||||
|
||||
.. _content-element-list:
|
||||
|
||||
=============
|
||||
Insert plugin
|
||||
=============
|
||||
|
||||
.. include:: /Images/AutomaticScreenshots/ContentOverview/PluginContentElements.rst.txt
|
||||
|
||||
Extensions often provide plugins to render frontend output. They are essentially the
|
||||
same as content elements. When an extension depends on a plugin, select the
|
||||
plugin in this content element. The fields might change depending on the plugin.
|
||||
|
||||
For example, the system extension *indexed_search* provides the *Indexed Search*
|
||||
plugin which does not offer any additional fields:
|
||||
|
||||
.. include:: /Images/AutomaticScreenshots/ContentElements/PluginBackend.rst.txt
|
||||
@@ -0,0 +1,96 @@
|
||||
.. include:: /Includes.rst.txt
|
||||
|
||||
.. _content-element-menu:
|
||||
|
||||
=====
|
||||
Menus
|
||||
=====
|
||||
|
||||
.. include:: /Images/AutomaticScreenshots/ContentOverview/MenuContentElements.rst.txt
|
||||
|
||||
In websites, menus are often created outside the content element scope, because they have
|
||||
to reappear within every page. These could be the main menu, a sub menu, a bread crumb or
|
||||
a language menu. However, there are situations where you would like to create a menu
|
||||
specifically on one page. The following content elements will give you some options to render
|
||||
a menu. These available content elements are:
|
||||
|
||||
Menu of selected pages
|
||||
The menu consists of links to the selected pages in the TYPO3 CMS backend.
|
||||
|
||||
Menu of subpages of selected pages
|
||||
The menu consists of links to the subpages of the selected pages in the TYPO3 CMS
|
||||
backend.
|
||||
|
||||
Menu of subpages of selected pages including abstracts
|
||||
The same as above, but showing the abstract of these pages as well, when not empty.
|
||||
|
||||
Menu of subpages of selected pages including sections
|
||||
This will render a menu of the subpages of the selected pages. Below each subpage an
|
||||
extra menu will be showing the titles of content elements which belong to that certain
|
||||
subpage, which have the option "Show in Section Menus" in the :guilabel:`Appearance` tab enabled.
|
||||
This makes it possible for the website visitor to jump to the selected content element,
|
||||
within that page, immediately.
|
||||
|
||||
Sitemap
|
||||
Render a full sitemap of the website, starting at the root page.
|
||||
|
||||
Sitemaps of selected pages
|
||||
Render one or more sitemaps at once. The starting point of each site map will be a
|
||||
single selected page.
|
||||
|
||||
Section index (page content marked for section menus)
|
||||
Menu of content elements within the selected page, which have the option "Show in
|
||||
Section Menus" in the :guilabel:`Appearance` tab enabled. This makes it possible for the website
|
||||
visitor to jump to the selected content element, within that page, immediately.
|
||||
|
||||
Recently updated pages
|
||||
Shows a list of pages which are updated in the last 7 days. Updated only means a
|
||||
change in the page properties, not the content on the page.
|
||||
|
||||
Related pages (based on keywords)
|
||||
Shows a list of the selected page and all other pages, which have one or more keywords,
|
||||
entered in the page properties, in common.
|
||||
|
||||
Pages for selected categories
|
||||
Displays a menu of all pages which have been assigned one or more of the selected
|
||||
categories.
|
||||
|
||||
Content elements for selected categories
|
||||
Displays a menu of all content elements which have been assigned one or more of the
|
||||
selected categories.
|
||||
|
||||
The availability of links in each type of menu will depend on access rights. If a website
|
||||
visitor has no access to a certain part (with a frontend login), the link will not be
|
||||
shown.
|
||||
|
||||
.. include:: /Images/AutomaticScreenshots/ContentElements/MenuBackend.rst.txt
|
||||
|
||||
In case no pages are selected, the menu will be rendered from the
|
||||
current page where the menu is put on.
|
||||
|
||||
Styling of the current page in a menu
|
||||
======================================
|
||||
|
||||
.. versionadded:: 12.0
|
||||
All menu content elements related to page navigation reflect the "current"
|
||||
state of a page now.
|
||||
|
||||
If the current page is displayed within a menu the aria attribute
|
||||
:html:`aria-current="page"` is added to the a-tag of a menu-item.
|
||||
|
||||
For styling with CSS the attribute of the link can be used:
|
||||
|
||||
.. code-block:: css
|
||||
:caption: EXT:site_package/Public/Css/menu.css
|
||||
|
||||
[aria-current="page"] {
|
||||
/* Special style for the current page link */
|
||||
}
|
||||
[aria-current="page"]:hover {
|
||||
/* Special style for the current page link when hovered */
|
||||
}
|
||||
[aria-current="page"]::before {
|
||||
/* Special virtual element for additions like chevrons, etc. */
|
||||
}
|
||||
|
||||
The default styling of contains no style for the current page.
|
||||
@@ -0,0 +1,28 @@
|
||||
.. include:: /Includes.rst.txt
|
||||
|
||||
.. _content-element-shortcut:
|
||||
|
||||
==============
|
||||
Insert Records
|
||||
==============
|
||||
|
||||
.. include:: /Images/AutomaticScreenshots/ContentOverview/InsertRecordsPageContent.rst.txt
|
||||
|
||||
Ever have content on one page that you want to reference on another page? But you don't want to have to
|
||||
maintain both and keep them both in sync? And you don't want to show the whole content from one
|
||||
page on another. Using insert records you can add one content element from a page or all
|
||||
the content elements from a page. You can also add content elements from several pages.
|
||||
|
||||
.. include:: /Images/AutomaticScreenshots/ContentElements/InsertRecordsBackend.rst.txt
|
||||
|
||||
Just select the content elements you want to display and if necessary, put them in the
|
||||
right order.
|
||||
|
||||
In the frontend the referenced content elements will show up the same as the original one
|
||||
(if the styling is not different for that page)
|
||||
|
||||
.. note::
|
||||
|
||||
This is the only content element still using a small amount of TypoScript in the rendering
|
||||
process. This is done because you can add different rendering for records from
|
||||
different tables. Take a look at :typoscript:`tt_content.shortcut.20`.
|
||||
@@ -0,0 +1,42 @@
|
||||
.. include:: /Includes.rst.txt
|
||||
|
||||
.. _content-element-table:
|
||||
|
||||
=====
|
||||
Table
|
||||
=====
|
||||
|
||||
.. include:: /Images/AutomaticScreenshots/ContentOverview/TableTypicalPageContent.rst.txt
|
||||
|
||||
The :guilabel:`Table` content element can be used to display tabular data.
|
||||
|
||||
.. hint::
|
||||
In the database the data is saved as comma separated values (CSV), a
|
||||
plain text format for storing table data (numbers and text). This format
|
||||
can be used to import data from external sources.
|
||||
|
||||
.. include:: /Images/AutomaticScreenshots/ContentElements/TableBackend.rst.txt
|
||||
|
||||
By default the :guilabel:`Field delimiter` is a vertical bar "|", the
|
||||
:guilabel:`Text enclosure` set to **none**.
|
||||
|
||||
A :guilabel:`Table caption` can be provided as a heading for the table.
|
||||
|
||||
.. include:: /Images/AutomaticScreenshots/ContentElements/TableAppearanceBackend.rst.txt
|
||||
|
||||
Also some appearance options are available for the table. These can be found in the
|
||||
:guilabel:`Appearance` tab:
|
||||
|
||||
Columns
|
||||
The maximum amount of columns. Even when more columns are defined in the
|
||||
:guilabel:`Table content` field, the table will only show the maximum amount of columns.
|
||||
|
||||
Table class
|
||||
Some predefined classes to style the table output.
|
||||
|
||||
Table header position
|
||||
The first row or the first column can be used as a table header.
|
||||
|
||||
Use table footer
|
||||
The last row will be used to group the table's footer area (which may be a summary, an
|
||||
addition of column values, or some call to action based on the preceding content).
|
||||
@@ -0,0 +1,36 @@
|
||||
.. include:: /Includes.rst.txt
|
||||
|
||||
.. _content-element-textmedia:
|
||||
|
||||
=============
|
||||
Text & Images
|
||||
=============
|
||||
|
||||
.. include:: /Images/AutomaticScreenshots/ContentOverview/TextMediaTypicalPageContent.rst.txt
|
||||
|
||||
This content element allows you to combine text and images. Additionally there
|
||||
is also a content element for :guilabel:`Text & Media` where you can use videos
|
||||
or Audio. There are also separate content elements for :guilabel:`Text`
|
||||
or :guilabel:`Images` individually. These offer no advantage over the content element
|
||||
:guilabel:`Text & Images` except that some fields are missing and the backend form
|
||||
is less cluttered.
|
||||
|
||||
The text can be entered in the rich text editor of the :guilabel:`General`
|
||||
tab.
|
||||
|
||||
.. include:: /Images/AutomaticScreenshots/ContentElements/RteBackend.rst.txt
|
||||
|
||||
The media elements can be added in the :guilabel:`Images` tab. In this tab
|
||||
there is also the option to turn the *enlarge on click* behaviour on for images.
|
||||
|
||||
.. include:: /Images/AutomaticScreenshots/ContentElements/MediaBackend.rst.txt
|
||||
|
||||
Multiple images and movies are combined as a gallery, which can be configured
|
||||
using the :guilabel:`Gallery Settings`. In some installations there are
|
||||
specific settings for width or height for each element, if a border
|
||||
should be shown around each element, the position of the gallery in relation
|
||||
to the text and the amount of columns which should be used for the gallery.
|
||||
|
||||
The maximum width of the gallery can be different when the gallery is on
|
||||
top or bottom of the text, or inside the text. This can be set using the
|
||||
:ref:`constant-editor`.
|
||||
@@ -0,0 +1,39 @@
|
||||
.. include:: /Includes.rst.txt
|
||||
|
||||
.. _content-element-uploads:
|
||||
|
||||
==========
|
||||
File links
|
||||
==========
|
||||
|
||||
.. include:: /Images/AutomaticScreenshots/ContentOverview/FileLinksPageContent.rst.txt
|
||||
|
||||
This content element gives you the opportunity to offer downloadable files to the visitors
|
||||
of your website.
|
||||
|
||||
.. include:: /Images/AutomaticScreenshots/ContentElements/UploadsBackend.rst.txt
|
||||
|
||||
You can add or select single files but also use a file collection. A file collection can
|
||||
be one of the following:
|
||||
|
||||
- A static selection of files
|
||||
- A folder within a storage, holding the files
|
||||
- A file selection by category
|
||||
|
||||
When combining both methods, single files and file collections, all files from these
|
||||
methods will be presented to the website visitor.
|
||||
|
||||
At the bottom of the tab :guilabel:`General` you will find several options how
|
||||
the files will be presented:
|
||||
|
||||
Display file/icon/thumbnail
|
||||
In this dropdown you can select if you only want to show the file name, the file name
|
||||
and a corresponding icon, based on the file extension, or the file name with a
|
||||
thumbnail, if it is possible for TYPO3 CMS to generate a thumbnail from the file.
|
||||
|
||||
Display file size information
|
||||
Will show the file size calculated from the amount of bytes and presented as a human
|
||||
readable string with the proper unit (B, KB, MB ...).
|
||||
|
||||
Display description
|
||||
Will display the description of each file, if available.
|
||||
Reference in New Issue
Block a user