Actions
Feature #103036
openEpic #103035: Handle EXT syntax more flexible
Customize TYPO3 without a site extension
Status:
New
Priority:
Should have
Assignee:
-
Category:
System/Bootstrap/Configuration
Target version:
Start date:
2024-02-04
Due date:
% Done:
0%
Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:
Description
I think it would be beneficial if we start reducing complexity for people creating new websites, e.g. with the bootstrap package, when they only want to add a CSS class or something the like in a template. Same goes for the Content Blocks, to override a content block HTML template, or a news plugin.
For this reason, we should consider having a template Base Path on a per-site basis, which is automatically added in the frontend for Fluid paths:
An example:
Folder Structure ./src/ (your PHP files, ViewHelpers etc) ./config/ ./resources/ ./resources/sites/my_site/Layouts/ ./resources/sites/my_site/Partials/ ./resources/sites/my_site/Pages/Default.html ./resources/sites/my_site/Pages/Default.html ./resources/sites/my_site/Content/TextMedia.html ./resources/sites/my_site/Plugins/News/News/List.html ./resources/sites/my_site/Plugins/News/{controller}/{action}.html ./resources/sites/my_site/Plugins/News/Partials/Whatever.html ./resources/sites/my_site/Public/JavaScript ./resources/sites/my_site/Public/StyleSheets ./resources/sites/my_site/Public/Icons ./resources/sites/my_site/Public/Fonts ./config/sites/my_site/settings.yaml ./config/sites/my_site/config.yaml ./config/sites/my_site/setup.typoscript ./config/sites/my_site/page.tsconfig
Some questions arise:
- Should we use ./config/TCA/Overrides/ once we do not need ext_tables.sql anymore?
- How to handle "label" overrides?
- How can we publish assets from resources to "public/_assets"?
Updated by Benni Mack about 2 months ago
- Target version changed from 13.3 to Candidate for Major Version
Actions