Talk:TYPO3: Difference between revisions
Trialpears (talk | contribs) m Add Talk header to link currently inaccesible archives. (via WP:JWB) |
→Splitting proposal: Support |
||
Line 58: | Line 58: | ||
: 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) |
: 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''' 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) |
Revision as of 09:26, 4 October 2021
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 |
Computing: Software / Free and open-source software Unassessed | ||||||||||||||||
|
To-do list for TYPO3:
|
This article was nominated for deletion. Please review the prior discussions if you are considering re-nomination:
|
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 |
"NPOV: 'one of the leading...'"
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.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.
FrankyBkk (talk) 05:57, 15 March 2009 (UTC)
To-Do: Update several sections
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
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
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)
- 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
- Wikipedia pages with to-do lists