Styleguide is a TYPO3 extension. It provides a backend module that hooks into the 'Help' menu of the top toolbar of the TYPO3 Backend. It can also create a page tree to show examples.
This extension in maintained in the official TYPO3 github organization.
Styleguide is developed "core-near": When TYPO3 core adds or deprecates features covered by this extension, core developers strive to keep it updated, reflecting these changes.
Styleguide is a reference to show a lot of TYPO3 backend features, often relevant for own extensions:
- A set of snippets showing how to use default backend functionality like tables, buttons, boxes or notifications.
- A huge set of 'TCA' examples, showing "all" features of the backend editing forms.
-
The extension is interesting for backend extension developers as a reference to see how casual stuff like buttons and other HTML related things are solved or used in the backend, and to copy+paste solutions. Additionally, the TCA examples is a near-complete show-case of FormEngine (editing records in the backend). Developers will see new things they did not know yet. Guaranteed!
-
The extension can be interesting for technical project managers to get an idea of what the backend editing is capable of out-of-the-box and which parts can be sold to customers without adding expensive implementation burdens to developers.
-
Styleguide is a "require-dev" dependency of the TYPO3 CMS core mono repository. It is used by core developers to test and verify changes to JavaScript, HTML and PHP code do not break layout or functionality of backend modules. The extension is also used in core backend acceptance tests to verify FormEngine details do not break when developing core patches.
-
Styleguide is used within the official core documentation to provide examples, screenshots and possible usages of core functionality. Especially the TCA reference heavily relies on it.
-
Styleguide comes with a simple set up of unit, functional and acceptance tests that are executed by github action workflow "tests.yml" - or locally if desired. This setup is documented as a working test set up example within the official TYPO3 explained testing section and can be used as a copy+paste boilerplate in own extensions.
Styleguide comes as a TYPO3 extension for the TYPO3 backend. It appears as backend module within the "Help" section of the top toolbar. After initial installation, it is advisable to let styleguide create an example page tree with records by clicking the "TCA / records -> Create styleguide page tree with data", and waiting for a couple of seconds for the system to crunch the data.
With composer based TYPO3 installations, styleguide is easily added to the project.
TYPO3 v12 based project:
composer require --dev typo3/cms-styleguide:^12
TYPO3 v11 based project:
composer require --dev typo3/cms-styleguide:^11
bin/typo3 extension:activate styleguide
For non-composer projects, the extension is available in TER as extension key styleguide and can
be installed using the extension manager.
With styleguide, it is possible to automatically create sample pages and content for 2 purposes:
- "styleguide TCA demo" to showcase various TCA features
- "styleguide frontend demo" to create pages which can be used for Frontend testing
These pages can be created either in the backend or on the command line:
# show help
bin/typo3 styleguide:generate -h
# create pages
bin/typo3 styleguide:generate -c
Alternatively, the pages can be created in the TYPO3 backend:
- Access the styleguide module by clicking on the question mark in the top bar: ? | Styleguide | TCA / Records / Frontend
- Click the available buttons
Styleguide comes with a module which is available by clicking on the question mark in the top bar: ? | Styleguide.
You can also peruse through the TCA demo by selecting the pages in the page tree. Use the list module to get access to the records.
The TYPO3 TCA reference documentation often uses examples from the styleguide.
Styleguide comes with a simple demo set of unit, functional and acceptance tests. It relies
on the runTests.sh script which is a simplified version of a similar script from the TYPO3 core.
Find detailed usage examples by executing Build/Scripts/runTests.sh -h and have a look at
.github/workflows/tests.yml to see how this is used in CI.
Example usage:
Build/Scripts/runTests.sh -s composerUpdate
Build/Scripts/runTests.sh -s unit
packagist.org is enabled via the casual github hook. TER releases are created by the "publish.yml" github workflow when tagging versions using tailor. The commit message of the commit a tag points to is used as TER upload comment.
Example:
composer req --dev typo3/tailor
.Build/bin/tailor set-version 12.0.0
composer rem --dev typo3/tailor
git commit -am "[RELEASE] 12.0.0 Core v12 compatibility"
git tag 12.0.0
git push
git push --tags
This project is released under GPLv2 license. See LICENSE.txt for details.
- The "tree" icon is from Yusuke Kamiyamane
- Placeholder texts are from Bacon Ipsum