[TYPO3-english] Major background issues

[Xavier Perseguers]

Dear Marina,

> When I came across TYPO3 in my research for a usable alternative to
> WordPress, I really thought I had found what I was looking for: as a
> "Webmaster", with a lot of experience with hand-coded static Websites,
> the descriptions at <http://typo3.org/about/typo3-the-cms/> promised all
> I needed. And I loved the ethics behind the product, as well as Kasper's
> story and the general "community feel" that come through from the Website.

Good and that's how TYPO3 is, regardless of what you may read here with
very strong words from only a few of our community members.

> Now, a few weeks later, after spending many hours trying to get TYPO3
> installed (please don't ask or insinuate - I have read the docs, tried
> all the scripts, tried to find all the answers online!), I discover it's
> been all for nothing. Apparently, if I wanted TYPO3 to work for me, I'd
> have to hire a specialist developer.

Well, that's not how it is supposed to be. Of course you will need a
developer if you want to do something that is not supported either
out-of-the-box by TYPO3 itself or by an existing extension but if you
want to create a website using a HTML/CSS/JS template, you definitely do
NOT need a developer! However you will have to learn how to do it with
TYPO3 as it is not Wordpress or another CMS and as such it might bit a
bit different.

> There's nothing wrong with the idea of paying someone else to install
> TYPO3 for me. It's just that that was not clear from the start!

Again, this is certainly not a requirement!

> So could I put forward a suggestion, or a request if you like: could
> those who have access to the Website make it clearer that TYPO3 requires
> specialist support for installation and general setup. And for this
> reason, it requires substantial money investments by "ordinary
> Webmasters" (like me) and anybody who is not a fully trained application
> programmer.

No! Because this is not the case.

> This will enormously help those who, like me, land on TYPO3's Website
> thinking it is fundamentally as accessible and "usable" as WordPress is.

TYPO3 is a CMS, not a blogging platform. I know WordPress does more and
more regarding "arbitrary websites" but currently working on a service
layer between a fully custom intern managing solution and a
WooCommerce-based e-shop I can assure you that this is not the case, and
WordPress is not from my POV best-suited for arbitrary websites.

The same is true for TYPO3, even with existing "solutions", I don't
consider this CMS to be best-suited for blogging, for instance.

> Once more, I must say I am disappointed at how so-called "free software"
> ends up being a lot more expensive than "commercial" applications - both
> because of the time invested into getting nowhere, and of the ultimate
> consequence, which is the requirement of hiring a specialist for
> (possibly never ending) installation and support services. This, of
> course, not to mention the time wasted by core developers in listening
> to the moans and groans of the ignorant (would be) user base...

Did I miss some previous messages of yours? It's highly probable,
unfortunately I don't have time to go through each and every post in the
various mailing lists. You seem to have fought quite some time now and
be at a point where you think TYPO3 is simply not for you and that it
did not keep its promise. But did you ask for help, for hints how to
start or for examples? Or did you only try to get it up and running by
yourself, possibly not using the best how-to's?

Our community is willing to help people and make them happy with TYPO3
so you should ask without worrying, you'll always find people taking
time to help you and guide your first steps with TYPO3.

Kind regards

-- 
Xavier Perseguers
Release Manager TYPO3 4.6

TYPO3 .... inspiring people to share!
Get involved: http://typo3.org