Feature #71697
closed
Multi-Channel-Publishing
0%
Description
TYPO3 is repeatedly referred to as a Enterprice CMS. A real feature of this kind is definitely multi-channel publishing! To shine at the customers with TYPO3, ist should provide these Features too.
Updated by Mathias Schreiber over 8 years ago
- Description updated (diff)
Hi Carsten,
I don't quite get this remark.
TYPO3 is able to supply any channel for the last 15 years.
It doesn't matter if you feed Twitter, Facebook, InDesign Server, some Mobile App, the Print-Factory, a ticketing machine or a TV on a cruiseship.
Can you go into a bit more detail, what exactly you are missing in this regards?
Updated by Georg Ringer over 8 years ago
- Status changed from New to Needs Feedback
Updated by Riccardo De Contardi over 8 years ago
I'll write here some of my toughts about this topic
I think that "multichannel" means that the CMS must be able to "tailor" its output, for example the
templates or even the content to different devices or scenarios
e.g. the screen of my computer is a "channel"; my smartphone is another "channel";
search engines are another "channel"; an RSS reader is another "channel"; even the printer is another "channel". (I think that NEOS has a similar concept called "dimensions")
TYPO3 is already able to "tailor" the output using the typoscript conditions
and today, with fluid and fluid_styled_content the possibilities have increased: it is possible to set a different TemplateRootPaths, etc using conditions.
But there are at least a couple of drawbacks
- there is not (as far as I know, correct me if I am wrong) a reliable way to detect mobile devices (WURFL extension has been abandoned as far as I can see)
- the conditions are not very easy to manage.
How about this idea (just a draft):
it could be nice to assign a whole typoscript template to a "channel"; I imagine something like this:
- introduce a new type of record, called "rendering device"
- the "default" rendering device is the "screen", that means "everything" if there are no one else (it is auto-created like the default file storage under fileadmin )
- the typoscript template must be associated to the rendering device
- of course you can add other rendering devices
- "rendering devices" can be determined in at least three ways:
1) querystring (e.g. adding "&print=1")
2) internal TYPO3 functions (add WURLF to TYPO3 core?)
3) custom php logic provided by a developer
Updated by Carsten Tornow over 8 years ago
Well, that sounds very interesting! OK, but HOW do we do that? Out of the box?
@ Riccardo: A working smartphone recognition is possible to implement: with an user function, a PHP class (i.e. http://mobiledetect.net) and a condition... But multi channel are not about only smartphones and tablets.
What's with Facebook & Co? There is an extrension like cc_facebook_publisher. But only for tt_news!
Carsten
Updated by Riccardo De Contardi over 8 years ago
If everyone agrees, I would change the tracker of this issue to "story" or "epic" because this topic is huge, and this issue could be the "container" of all related subtasks that will come in the future about this topic.
I would also suggest to open a discussion on Slack (I don't know if on a dedicated channel or on the cms channel)
Updated by Riccardo De Contardi about 8 years ago
- Status changed from Needs Feedback to New
Updated by Riccardo De Contardi about 8 years ago
- Priority changed from Must have to Could have
Updated by Riccardo De Contardi over 7 years ago
- Category set to Frontend
I see that there has been no activity on this: just for the records, this extension looks very near to the topic discussed here https://typo3.org/extensions/repository/view/contexts
Not compatible with 7.x or higher, so far.
Updated by Riccardo De Contardi over 7 years ago
Ext:context is compatible with version 7.x and 8.x now https://typo3.org/extensions/repository/view/contexts.
Could it be sufficient to consider this issue closed?
Updated by Riccardo De Contardi about 7 years ago
- Target version changed from 8 LTS to 9.0
Updated by Benni Mack over 6 years ago
- Target version changed from 9.0 to Candidate for Major Version
Updated by Riccardo De Contardi over 6 years ago
- Status changed from New to Closed
- Target version deleted (
Candidate for Major Version)
Hello Carsten - I hope it is ok for you if I close this issue for now, as such a topic requires concepts, blueprints, planning and people who actively work on it. At the moment it seems this does not happen.
After the concepts are discussed, then fresh issues (Tasks, Features) must be created if it comes to a core integration. In the meanwhile, as I wrote on one of my comments, you could try the extension https://typo3.org/extensions/repository/view/contexts
Feel free to open a discussion or a new issue on that if you feel that is important for you, writing more details about your ideas.
Thank you and best regards.