The Snippets were available a number of years and have been helpful. But for quite some time, they were no longer being used much and no new Snippets were being added.
The main problem currently is that the manual was never versionized, so there is no way to see for which TYPO3 version the snippet applies. This makes it especially difficult for newcomers, while experts may still find the information they need and have no problem figuring out whether it applies to their TYPO3 version.
However, the Matomo results also show, that there is very little traffic to these pages.
Decreased activity may also be a reflection that people are now using other platforms, for example Stack Overflow or their own blogs to introduce tips, small snippets and examples and information on how to do things.
As advertised on the start page, the snippets were never meant to be maintained by the Documentation Team, which meant everyone was free to add their own snippets, there was no quality control or entry exam to complete. While this made it very open and inviting, it had the inherent problem, that there never was an official review. Since we now have other platforms where you can vote and comment (e.g. Stack Overflow) or have an author who stands behind the content and has an incentive to keep it up to date or people just know it is something with an expiration date and never meant to be kept updated (e.g. blogs) - these may be better suited for this type of content.
On the other hand, it is not easy to take down or deprecate content, people may find it disruptive and we hate to throw away content that was created by the community and that served its purpose many years.
This is now the plan:
"Snippets" were removed from main menu on https://docs.typo3.org
the rendered pages are still available but contain a prominent banner, informing about the fact that this manual is not being maintained
the repository is archived on GitHub
At some time in the future, we may also remove the rendered snippets and redirect to the https://docs.typo3.org start page. The archived repository on GitHub is still available.
Nothing was thrown away - it will just be less prominent in the future.
How you can help:
Give us feedback on this decision or the structure of the documentation in general, either as issues or via Slack
Help to increase the knowledgebase of useful examples for TYPO3 by contributing to Stack Overflow, your blog or the existing documentation. Help to keep existing documentation on docs.typo3.org updated.
When you find information in the Snippets that you think is important and helpful to others, see if you can migrate it to a repository which has been versionized to Stack Overflow or some other appropriate medium. (Get in touch with the original authors to ask permission first!)
Don't hesitate to contact us on Slack in the channel #typo3-documentation.
Fluid start page¶
A Fluid start page was created in "TYPO3 Explained". This reflects the importance of Fluid in TYPO3 and the multiple ways it is now used in TYPO3. A t3coreapi:fluid-introduction subpage was added as well.
The Fluid page serves as an overview of various ways to use Fluid in TYPO3 as Fluid is now no longer used only in developing Extensions with Extbase & Fluid as was the case when it was initially introduced.
As next steps the documentation could be further restructured, moving for example general Fluid information that is not specific to Extbase / Fluid from the Extbase Fluid Book to "TYPO3 Explained".
We made several changes to the TypoScript reference and documentation for the topic TypoScript in general.
Renamed to "TypoScript Templating Reference"
Menu was restructured
Consolidated older versions (finalized migration, ...)
Added introduction, links to other information and quick links to start page
In more detail:
Menu before and after restructuring
It was pointed out that the "TypoScript Reference" menu was confusing in parts: some functions (such as calc and objectSplit) were found under "Objects and Properties", top-level objects were hidden in a rubric "setup" etc. This resulted in things not being found where they were expected. We managed to simplify the menu and sort the topics accordingly.
The use of objects and object types was used inconsistently, some types were referred to as "objects" and vice versa. Especially, the term "cObject" was used inconsistently, sometimes to refer to the type, sometimes as synonym for "content objects". We corrected the use of these terms in some places and added a glossary.
We renamed "TypoScript Reference" to "TypoScript Templating Reference" because the term TypoScript has 2 meanings and in this reference we mean TypoScript templating and not (primarily) TypoScript syntax (which is handled in t3coreapi:typoscript-syntax-start in "TYPO3 Explained". See decisions.typo3.org for discussion about this topic.
The chapter "Introduction" contained no introduction into the topic - this is a common problem in the documentation: There is a chapter "Introduction" where you expect to find information about the topic or what the manual is about and often this only contains very little information about the manual, credits, how to give feedback etc. For this reason we renamed the current Introduction to "About this manual", moved it to the end of the menu and added a real Introduction.
We linked to other manuals where topics are handled in depth (TypoScript in 45 minutes and "TypoScript syntax" in "TYPO3 Explained"), both on the start page and in the "Introduction"
We added the chapter "Using and setting TypoScript" to the older versions <= 8.7. Previously it only existed for versions 9.5 and master (10). (This is due to the fact that the migration of some manuals - like "TypoScript Syntax and in depth study" was done for version 9.5 and had not been performed for previous versions. This is now being done, step by step.)
We added "TypoScript Syntax" to older versions <= 8.7 in "TYPO3 Explained".
Added quick links to start page
The topic of using objects and objects types was addressed but could still be improved.
Additionally, a number of pages could be improved. For example, the page FLUIDTEMPLATE could use a better introduction.
If you would like to help with this, please look at the open issues.