This package is a TYPO3 extension that makes integration work easier.

We consider it "best practice" to run a site and all custom Backend Layouts, TypoScript, PageTS in one place, a so-called "site extension". We prefix them with "site_" making it something like "site_myproject".

Then, the tricky part starts:

• Adding TypoScript
• Adding Fluid
• Adding PageTSconfig
• Adding Domains (for certain environments)

We want to avoid that for our sites, making life easier for integrators and get the website up and running faster.

Because of this, this extension adds a field to the Site Configuration, where you can define your site extension:

sitePackage: '<my_extension_key>'

It's doing the same as you'd need to do manually all the time.

What you do:

• Create your site extension
• Install bolt, and choose your site extension on your Site Configuration
• Ensure your site extension contains one of the following files
  • Configuration/TypoScript/constants.typoscript (or Configuration/TypoScript/constants.txt)
  • Configuration/TypoScript/setup.typoscript (or Configuration/TypoScript/setup.txt)
  • Configuration/PageTs/main.tsconfig or Configuration/PageTsConfig/main.tsconfig

If you want to do one step less when developing a TYPO3 website :)

You can set this up via composer (composer require b13/bolt) or via TER (extension name "bolt"), it runs best with TYPO3 v9 or later.

Site configuration is required.

The extension is licensed under GPL v2+, same as the TYPO3 Core.

For details see the LICENSE file in this repository.

• Kickstart a site extension
• Add an integrator backend module to show the current setup
• Integrate Fluid templates, Content types, etc.
• Make "disabling sys_template" optional
• Run all cases with extension templates / static inclusions work

Find more TYPO3 extensions we have developed that help us deliver value in client projects. As part of the way we work, we focus on testing and best practices to ensure long-term performance, reliability, and results in all our code.