This is the
talk page for discussing improvements to the
TYPO3 article. This is not a forum for general discussion of the article's subject. |
Article policies
|
Find sources: Google ( books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
Archives:
1Auto-archiving period: 90 days
![]() |
|
![]() | This article was nominated for
deletion. Please review the prior discussions if you are considering re-nomination:
|
![]() | This article has not yet been rated on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||
|
![]() | This article links to one or more target anchors that no longer exist.
Please help fix the broken anchors. You can remove this template after fixing the problems. |
Reporting errors |
I just discovered how big the differences between this and the german version are. I already updated the TypoScript section, but I think that several other parts need maintenance. The de.WP version is very thorough, while the english one misses a lot of valuable facts. So...my suggestions:
Any ideas or objections? -- Jesus Presley ( talk) 16:27, 30 July 2012 (UTC)
Update: I added a lot of information. If someone could please check if the recently added sections are still complying with WP standards? As I use TYPO3 myself, some details might appear NPOV. -- Jesus Presley ( talk) 21:08, 31 July 2012 (UTC)
Since the switch from Geshi to Pygments for syntax highlighting ( phab:T85794), support for 'typoscript' was unfortunately dropped, as can be seen with the plain text formatting on this page. If you want specialised 'typoscript' syntax highlight support again, it will need to be added to Pygments. Alternatively, if there is another language which has similar syntax, we can add that as a fallback. John Vandenberg ( chat) 20:59, 18 July 2015 (UTC)
I propose that sections Neos be split into a separate page called Neos (content management). As the Neos section itself says: "In May 2015 the TYPO3 Association and the Neos team decided to go separate ways, with TYPO3 CMS remaining the only CMS product endorsed by the Association and the Neos team publishing Neos as a stand-alone CMS without any connection to the TYPO3 world." see https://typo3.org/news/article/typo3-project-focuses-on-typo3-cms-neos-to-start-its-own-community/
Neos is a separate project for 6 years now with regular releases and an annual conference and meetups which justifies an own article. Content for the splitted page is prepared as Draft:Neos_(content_management) but it was suggested to start the article as a split. The Neos contents cannot be added here first as it makes no sense to add the version history of Neos to a TYPO3 article.
Kopfaufholz ( talk) 16:13, 26 March 2021 (UTC)
@ Kopfaufholz, CanadianOtaku, and Mateng: After closing the splitting discussion, I have obtained a refund of the draft. However, I am also concerned about the lack of reliable sources or reviews, although in fairness the current section on Neos on this page is in no way better. Felix QW ( talk) 09:28, 21 June 2022 (UTC)
This is the
talk page for discussing improvements to the
TYPO3 article. This is not a forum for general discussion of the article's subject. |
Article policies
|
Find sources: Google ( books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
Archives:
1Auto-archiving period: 90 days
![]() |
|
![]() | This article was nominated for
deletion. Please review the prior discussions if you are considering re-nomination:
|
![]() | This article has not yet been rated on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||
|
![]() | This article links to one or more target anchors that no longer exist.
Please help fix the broken anchors. You can remove this template after fixing the problems. |
Reporting errors |
I just discovered how big the differences between this and the german version are. I already updated the TypoScript section, but I think that several other parts need maintenance. The de.WP version is very thorough, while the english one misses a lot of valuable facts. So...my suggestions:
Any ideas or objections? -- Jesus Presley ( talk) 16:27, 30 July 2012 (UTC)
Update: I added a lot of information. If someone could please check if the recently added sections are still complying with WP standards? As I use TYPO3 myself, some details might appear NPOV. -- Jesus Presley ( talk) 21:08, 31 July 2012 (UTC)
Since the switch from Geshi to Pygments for syntax highlighting ( phab:T85794), support for 'typoscript' was unfortunately dropped, as can be seen with the plain text formatting on this page. If you want specialised 'typoscript' syntax highlight support again, it will need to be added to Pygments. Alternatively, if there is another language which has similar syntax, we can add that as a fallback. John Vandenberg ( chat) 20:59, 18 July 2015 (UTC)
I propose that sections Neos be split into a separate page called Neos (content management). As the Neos section itself says: "In May 2015 the TYPO3 Association and the Neos team decided to go separate ways, with TYPO3 CMS remaining the only CMS product endorsed by the Association and the Neos team publishing Neos as a stand-alone CMS without any connection to the TYPO3 world." see https://typo3.org/news/article/typo3-project-focuses-on-typo3-cms-neos-to-start-its-own-community/
Neos is a separate project for 6 years now with regular releases and an annual conference and meetups which justifies an own article. Content for the splitted page is prepared as Draft:Neos_(content_management) but it was suggested to start the article as a split. The Neos contents cannot be added here first as it makes no sense to add the version history of Neos to a TYPO3 article.
Kopfaufholz ( talk) 16:13, 26 March 2021 (UTC)
@ Kopfaufholz, CanadianOtaku, and Mateng: After closing the splitting discussion, I have obtained a refund of the draft. However, I am also concerned about the lack of reliable sources or reviews, although in fairness the current section on Neos on this page is in no way better. Felix QW ( talk) 09:28, 21 June 2022 (UTC)