[TYPO3-typo3org] Consolidate - don't divide?

[Daniel Bruessler]

Hey,

> (..) making sure TYPO3 is the
> best thing for the job. For that it would take a good, clear analysis of
> what the site needs, what TYPO3's strengths and shortcomings are, and
> exactly what it would take to get there.

Yeah! That's exactly my point, too. And I'm _shure_ we find an optimal
solution - even if there were requests for 200 pages-per-minute and
_more dynamic features_.
(I've put your sentence above into the TYPO3.org-improvement-wikipage)

> Those are the questions I'd ask, not "should we use TYPO3 or not?", but
> "how do we make TYPO3 the best/only choice for powering our CMS-based
> web presence?"

Yes! The way is "how" to get there.

Instead of paying xx000 bucks for an alien-CMS Web-Site what is scalable
up to xxx pages-per-second we should spend that or less money to let
TYPO3 jump over the hill!

nice weekend -- cheers!
Daniel Brüßler