[TYPO3-core] (New) TYPO3 CMS Vision
michael.stucki at typo3.org
Tue Aug 26 15:09:09 CEST 2014
Hi Oliver, hi all!
The discussion is getting more specific about features, still I am not
sure if we agree about the vision yet.
I am reluctant to phrase a vision for TYPO3 CMS because I think that our
main goal should be to carry the legacy of it.
This is not half as exciting as other visions seem to be, but that's
also not my main point. I want to provide a great product for the users
who are working with TYPO3 right now. We should always focus on their
TYPO3 is legacy, not bleeding edge. If we focus on the bleeding edge
(changing workflows, frameworks, etc.) then we will mainly disappoint
the existing users. I repeat myself when I say that Neos is the bleeding
edge, not CMS.
Yet there are many features which TYPO3 lacks. For example, I really
like the suggestions that Felix brought up. If this was the roadmap for
the next three versions of TYPO3 CMS, then it would absolutely kick ass!
My wish is that we can agree on the direction and accept one or the
other inconsistency and detour that exists in TYPO3 CMS. Instead, the
focus should be put on features which serve the operators, integrators,
editors who are working with TYPO3 today and for the next few years...
Am 15.08.2014 um 11:04 schrieb Oliver Hader:
> Hi everybody,
> currently there are different topics flying around in the TYPO3 universe
> that need some care but also some more time to think about and to
> elaborate on. I don't think there is the requirement to rush things and
> to just do things because others might expect those things. If a process
> is unclear or fuzzy, we have the freedom to take the time that is
> required to turn it into something fruitful.
> There is a promise we gave with TYPO3 CMS 6.2 LTS in March 2014 which
> will last at least until March 2017. And besides that, continuing is
> also quite obvious, but processed, working modes and the vision need
> some adoption and revitalization.
> This thread is open for the topic "vison for TYPO3 CMS" and is a base
> for further discussions, ideas and feedback on the next larger and
> long-term steps with TYPO3 CMS. Please hand in your feedback in an open
> but also constructive way. Try to be specific if phrases tend to be
> unclear (e.g. "TYPO3 needs to be cooler" - what exactly?).
> Ok, let's start now! Thanks in advance for your input!
> All the best
More information about the TYPO3-team-core