Deletion candidates #255
Comments
The information is already available on the runTests.sh page (including the "direct commands"). The additional page makes it necessary to maintain information in several pages and is unnecessary. Related: TYPO3-Documentation#253 Related: TYPO3-Documentation#249 Related: TYPO3-Documentation#255
|
Last updated: June 3, 2022 Least accessed pagespage views (14 or less page views) due to Matomo. Least accessed first.
top access pagesMost accessed first May 2022 Some of the page with very many views, might be strays which are lost and not looking for info for TYPO3 contribution. (may need a note, as done for DDEV page).
...
|
|
Will add section "pain in the neck to maintain" pages. and page "Aliases": https://docs.typo3.org/m/typo3/guide-contributionworkflow/main/en-us/Appendix/Aliases.html to list of pages to be deleted. Also, PR coming up ... (after lunch) I noticed, the docs rendering has changed and you need to use the new container, see https://docs.typo3.org/m/typo3/docs-how-to-document/main/en-us/RenderingDocs/Quickstart.html#render-documenation-with-docker Any page which still contains the "old" rendering Docker container is a good candidate for deletion because if it has not been noticed yet, people are either not using the page or not contributing. Also, the content was added by myself, so I am not stepping on anyone's toes (except my own) by removing it. The Aliases page actually has some views (see Matomo results above) and I find it helpful to just copy-paste the entire thing. Perhaps alternatively, we can change the setup page to have one code block which you can copy-paste in one scoop (but that should be handled separately). |
Additionally, some minor changes in "Adding documenation" to reduce text (mostly unnecessary bloat). The aliases page repeated some of the commands in "Setup", "Git cheat sheet" and for documentation rendering. Removing content where it is duplicate helps maintainence and keeps existing content more up to date. Related: TYPO3-Documentation#255
Additionally, some minor changes in "Adding documenation" to
reduce text (mostly unnecessary bloat). Also, the rendering
documenation commands were removed so that it is documented
only in one place ("Writing documentation").
The aliases page repeated some of the commands in "Setup", "Git cheat
sheet" and for documentation rendering.
Removing content where it is duplicate helps maintainence and keeps
existing content more up to date.
Related: TYPO3-Documentation#255
Additionally, some minor changes in "Adding documenation" to
reduce text (mostly unnecessary bloat). Also, the rendering
documenation commands were removed so that it is documented
only in one place ("Writing documentation").
The aliases page repeated some of the commands in "Setup", "Git cheat
sheet" and for documentation rendering.
Removing content where it is duplicate helps maintainence and keeps
existing content more up to date.
Related: #255
These are empty pages where the content has already been removed 2 years ago. Related: TYPO3-Documentation#255
These are empty pages where the content has already been removed 2 years ago. Related: #255
This page was initially introduced to provide some information and conventions for people editing this guide. However, the page is only valualbe, if visible and commonly used. Unless a general convention is established if and how to provide information about editing a specific guide, the page is of little value and should be removed. Related: TYPO3-Documentation#255
These are deletion candidates (!). Deletion has not been decided (yet).
Reasons for deletions
What to keep
Criteria
List of possible deletion candidates
empty pages
obsolete pages / duplicate content
rarely used pages
"pain in the neck to maintain" pages
this is sometimes the case because content is duplicated in several places and must be maintained in several places (e.g. in Git cheat sheet, setup and "Aliases")
general non-TYPO3 specific information
runTests.shscript, it is not necessary to install Composer locallyGit GUIs
Tool installation
misc
The text was updated successfully, but these errors were encountered: