Configuration
Site settings
The settings come with the site set and are edited in
Site Management > Settings or in
config/.
| Name | Type | Default |
|---|---|---|
| string | '12' | |
| string | 'wrapper' | |
| string | 'http://127.0.0.1' | |
| int | 0 | |
| string | '' |
-
- Type
- string
- Default
- '12'
Comma-separated page types (doktypes) listed in the section "Articles" of
llms., newest first.txt 12is the news page type of EXT:just_news. Page type1(standard) is always included.
-
- Type
- string
- Default
- 'wrapper'
idof the HTML element whose content becomes the generated Markdown of a page. Everything outside of it (header, footer, menus, modals) is ignored. If the element is missing, the first<main>element is used, and without<main>the<body>.Inside the element, anything with the attribute
data-is left out as well, for example a share bar:sillmstxt- ignore <div class="share" data-sillmstxt-ignore>…</div>Copied!
-
- Type
- string
- Default
- 'http://127.0.0.1'
How the web server reaches itself to build
llms-. The requests are sent to this address with thefull. txt Hostheader andX-of the site base. See llms-full.txt is incomplete.Forwarded- Proto
-
- Type
- int
- Default
- 0
Page with the detail plugin of EXT:news.
0switches the news support off. Only used when EXT:news is installed, see EXT:news (tx_news).
-
- Type
- string
- Default
- ''
Comma-separated page uids that contain news records. Empty: all news within the page tree of the site (hidden storage folders included).
llms.txt intro per language
Each site language has the field llms.txt intro (Markdown). It
is shown below the website title in the llms. of that language,
for example a one-line summary and a few key facts.
Where to find it: Site Management > Sites > edit the site > tab Languages > expand a language > tab LLM.
The value is stored in the site configuration:
languages:
-
title: English
languageId: 1
base: /en/
sillmstxtIntro: |-
Example is a tool for …
Note
The site configuration is a file. If it is kept in version control and deployed, change the intro there – an edit in the backend of a server is overwritten by the next deployment.