Talk:TYPO3: Difference between revisions
m Removed deprecated parameters in {{Talk header}} that are now handled automatically (Task 30) |
|||
(46 intermediate revisions by 23 users not shown) | |||
Line 1: | Line 1: | ||
{{talk header}} |
|||
⚫ | |||
{{todo}} |
|||
⚫ | |||
{{WikiProject banner shell|class=| |
|||
{{WikiProject Computing |importance= |free-software=yes |free-software-importance= |software=yes }} |
|||
}} |
|||
{{User:MiszaBot/config |
|||
|archiveheader = {{talk archive navigation}} |
|||
|maxarchivesize = 100K |
|||
|counter = 1 |
|||
|minthreadsleft = 4 |
|||
|minthreadstoarchive = 1 |
|||
|algo = old(90d) |
|||
|archive = Talk:TYPO3/Archive %(counter)d |
|||
}} |
|||
{{Broken anchors|links= |
|||
* <nowiki>[[Internet Explorer 6#Version 6|IE6]]</nowiki> |
|||
}} |
|||
⚫ | |||
⚫ | |||
==TypoScript part needs some work== |
|||
⚫ | |||
In my opinion, this part is a total mess. TypoScript is a simplified way to write a php configurtion array with some goodies (e.g. copy and delete operator). The php array is then used as rendering instruction to generate the output. |
|||
⚫ | |||
Also the part about the TS is far too long. There is much more to tell about TYPO3 - have a look at german translation ... is something like that wanted for english WP? |
|||
⚫ | |||
⚫ | |||
# [EDIT] Briefly explain the caching framework |
|||
# Briefly mention the [http://docs.typo3.org/typo3cms/InstallationGuide/InstallingTypo3QuickInstall/1-2-3/Index.html 1-2-3 installer] |
|||
# Insert section ''criticism'' (Too complex, need to learn TypoScript, cryptic etc.) |
|||
⚫ | |||
⚫ | |||
--[[User:Jesus Presley|Jesus Presley]] ([[User talk:Jesus Presley|talk]]) 16:27, 30 July 2012 (UTC) |
|||
⚫ | |||
==Spam in External Links?== |
|||
== typoscript syntax highlighting lost == |
|||
Somehow I don't think that links to "consultancies" or non-english sites in the en.wikipedia.org domain ought to exist. I think that the article ought to exist in the other language venues at WP with the appropriate links moved there. As to the consultancies, it just smacks of commercial advertisement -- a place not to be found in WP. I propose that both types be removed. --[[User:Zhen-Xjell|Paul Laudanski]] 03:08, 6 September 2005 (UTC) |
|||
: Ok it seems [[User:Hirzel]] removed the links [http://en.wikipedia.org/enwiki/w/index.php?title=Typo3&diff=prev&oldid=22872430]. --[[User:Zhen-Xjell|Paul Laudanski]] 02:04, 9 September 2005 (UTC) |
|||
:Links to consultants using the software are definitely [[wp:spam]] and should be remove without discussion. -- <span style="text-decoration: none;">[[User:Kl4m|<font color="#696969">Kl4m</font>]] <sup>[[User talk:Kl4m|T]] [[Special:Contributions/Kl4m|C]]</sup></span> 18:53, 18 October 2007 (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 [http://pygments.org/ Pygments]. Alternatively, if there is another language which has similar syntax, we can add that as a fallback. <span style="font-variant:small-caps">[[User:John Vandenberg|John Vandenberg]] <sup>'''([[User talk:John Vandenberg|chat]])'''</sup></span> 20:59, 18 July 2015 (UTC) |
|||
---- |
|||
:In the meantime, TypoScript support has been added to Pygments. It will most likely be released in Pygments 2.2 and be available for the syntax highlighting extension of MediaWiki once this extension has been updated to that new version of Pygments. I am using a self-compied Pygments wheel file myself, which already includes the new highlighter and I can confirm that the new highlighter fixes highlighting again. --[[Special:Contributions/87.123.54.224|87.123.54.224]] ([[User talk:87.123.54.224|talk]]) 22:44, 4 April 2016 (UTC) |
|||
Also, the External link called '''Comparing TYPO3 with phpWebSite''' lead to an outdated article which seems to me biased and contains also misleading information. Eg. on Page 2: "TYPO3 has a very strong content orientation. It's basically one monolithic piece of software...". Typo3 is definitely not monolithic - far from it; it's very nicely modularized. Not just the content and appearance are separated, but the Front-End, Back-End, Extensions, localizations, etc. And, if we are to compare CMS systems, the [OpenSourceCMS]http://www.opensourcecms.com/ website with user comments is way better source of information for undecided people looking for a suitable CMS. [[User:Hardzsi|Hardzsi]] ([[User talk:Hardzsi|talk]]) 13:37, 17 April 2008 (UTC) |
|||
== Splitting proposal == |
|||
⚫ | |||
{{discussion top|1=Consensus to '''split'''. A refund of the draft created by [[User:Kopfaufholz|Kopfaufholz]] has been requested. [[User:Felix QW|Felix QW]] ([[User talk:Felix QW|talk]]) 08:11, 21 June 2022 (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. |
|||
The first sentence says TYPO3 is a [[Content management system|CMS]], but TYPO3 describes itself as a "web content management framework", which I agree with. It's difficult for a non web-developer to build upon TYPO3. What do you think about it? -- <span style="text-decoration: none;">[[User:Kl4m|<font color="#696969">Kl4m</font>]] <sup>[[User talk:Kl4m|T]] [[Special:Contributions/Kl4m|C]]</sup></span> 18:57, 18 October 2007 (UTC) |
|||
⚫ | |||
---- |
|||
: Fixed proposed split link [[User:AngusWOOF|<strong><span style="color: #606060;" class="nowrap">AngusW🐶🐶F</span></strong>]] ([[User talk:AngusWOOF#top|<span style=" color: #663300;">bark</span>]] • [[Special:Contributions/AngusWOOF|<span style="color: #006600;">sniff</span>]]) 17:26, 29 March 2021 (UTC) |
|||
*'''Support''' per nom, it would be nice if the draft had better reliable sources, though. [[User:CanadianOtaku|<span style="background-color: red; color: white; font-weight: bold">CanadianOtaku</span>]] [[User talk:CanadianOtaku|<sup>Talk Page</sup>]] 00:32, 31 March 2021 (UTC) |
|||
*'''Support''' I know both projects. After six years of independent development it's time for independent pages [[User:Jesus Presley|Mateng]] ([[User talk:Jesus Presley|talk]]) 09:26, 4 October 2021 (UTC) |
|||
{{discussion bottom}} |
|||
⚫ | |||
I guess Kasper designed that primarily as a flexible framework, but it was tightly integrated with the CMS elements/functions so at the end of the day Typo3 version 4.x IS a CMS which is based on a well thought-of framework. To my knowledge, this framework is only used and utilized by Typo3 at the moment. |
|||
This tight framework-CMS integration can disapperar with the new Flow3 system, started from scratch. Flow3 is (will be) the next-gen framework, and Typo3 v5.x will be only one CMS 'application', that will be built/running on top of this framework - but other people can built other CMS or non-CMS systems on this new, independent framework logic called Flow3. [[User:Hardzsi|Hardzsi]] ([[User talk:Hardzsi|talk]]) 08:39, 17 April 2008 (UTC) |
|||
{{ping|Kopfaufholz|CanadianOtaku|Mateng}} After closing the splitting discussion, I have obtained a refund of [[Draft:Neos_(content_management)|the draft]]. |
|||
== "NPOV: 'one of the leading...'" == |
|||
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. [[User:Felix QW|Felix QW]] ([[User talk:Felix QW|talk]]) 09:28, 21 June 2022 (UTC) |
|||
First sentence of this entry is derived from TYPO3's marketing materials (via Google search) and is clearly NOT from a NPOV (plus factually quite questionable). Very close to deletable as an advertisement with this lead?? |
|||
CMS/CMF is industry jargon, with no clear distinction between the two; at the time of release, 'CMS'es were arguably very hard for a non-developer to build upon; and TYPO3 is listed as a CMS by CMSWatch, so I'm not sure there's any way to further clarify in this article.[[Special:Contributions/68.217.153.207|68.217.153.207]] ([[User talk:68.217.153.207|talk]]) |
|||
FrankyBkk: |
|||
I am new here and hope that I do not break any rule here. But I want to tell you that I think that the TYPO3 article was for me very informative. And that TYPO3 is one of the leading CMS is just the Truth. What you expect that they write instead? TYPO3 is a CMS and that was it? It have in my opinion nothing to do with marketing, specially because TYPO3 is under the GNU Licence and totaly for free. To say that TYPO3 is one of the leading CMS'es is just a information for the reader. If they would say that they are '''THE''' leading CMS then would it be in my opinion a break of rules. |
|||
I think that it is much more important to give a lot of informations to the readers of the Best Online Encyclopdia on earth as to look into every word that it is conform with the rules. Oops, I think it is not allowed to say that Wikipedia is the best one? |
|||
I think it is just not fair to delete this sentence. |
|||
[[User:FrankyBkk|FrankyBkk]] ([[User talk:FrankyBkk|talk]]) 05:57, 15 March 2009 (UTC) |
|||
⚫ | |||
⚫ | 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 |
||
⚫ | |||
⚫ | |||
⚫ | |||
⚫ |
Latest revision as of 18:02, 17 July 2024
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: 3 months |
To-do list for TYPO3:
|
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 |
To-Do: Update several sections
[edit]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:
Design: Rename to "Architecture" and merge updated information from the Funktion und Architektur part from de.WPCLA for TYPO3 version 5: Why is the CLA mentioned with a whole paragraph, although TYPO3 5 (TYPO3 Phoenix) hasn't been mentioned before? Suggestion: Label the paragraph TYPO3 v6 / Phoenix, add information about v6, why it is special and mention CLA briefly.Translate & insert the version history table.- [EDIT] Briefly explain the caching framework
- Briefly mention the 1-2-3 installer
- Insert section criticism (Too complex, need to learn TypoScript, cryptic etc.)
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)
typoscript syntax highlighting lost
[edit]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)
- In the meantime, TypoScript support has been added to Pygments. It will most likely be released in Pygments 2.2 and be available for the syntax highlighting extension of MediaWiki once this extension has been updated to that new version of Pygments. I am using a self-compied Pygments wheel file myself, which already includes the new highlighter and I can confirm that the new highlighter fixes highlighting again. --87.123.54.224 (talk) 22:44, 4 April 2016 (UTC)
Splitting proposal
[edit]- The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.
- Consensus to split. A refund of the draft created by Kopfaufholz has been requested. Felix QW (talk) 08:11, 21 June 2022 (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)
- Fixed proposed split link AngusW🐶🐶F (bark • sniff) 17:26, 29 March 2021 (UTC)
- Support per nom, it would be nice if the draft had better reliable sources, though. CanadianOtaku Talk Page 00:32, 31 March 2021 (UTC)
- Support I know both projects. After six years of independent development it's time for independent pages Mateng (talk) 09:26, 4 October 2021 (UTC)
Splitting off Neos (content management)
[edit]@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)
- Wikipedia pages with to-do lists
- Unassessed Computing articles
- Unknown-importance Computing articles
- Unassessed software articles
- Unknown-importance software articles
- Unassessed software articles of Unknown-importance
- All Software articles
- Unassessed Free and open-source software articles
- Unknown-importance Free and open-source software articles
- Unassessed Free and open-source software articles of Unknown-importance
- All Free and open-source software articles
- All Computing articles