What's New in TYPO3 v13.0? (Feature Release Series #1)
Community
Update
TYPO3 Losing People To WordPress: Case Study
According to researched statistics, Do you know WordPress is the most competitor of TYPO3 CMS? In this micro TYPO3 blog, I’d like to share data, statistics, why/how people are migrating from TYPO3 to WordPress, and some of my personal opinions to solve it.
According to researched statistics, Do you know WordPress is the most competitor of TYPO3 CMS? In this micro TYPO3 blog, I’d like to share data, statistics, why/how people are migrating from TYPO3 to WordPress, and some of my personal opinions to solve it.
In my history of TYPO3, I was always eager to know... After all, what’s an alternative to TYPO3 for people? If some people do not get along with TYPO3 then what’s an option they choose? My doubt was WordPress because it’s already #1 CMS in all over the world. And that’s correct, according to research data by t3versions.com.
My dear TYPO3 reader, IMHO “TYPO3 is suitable for every site”. TYPO3 has all the potential to create small to medium to large scale websites. Did you know how TYPO3 is more powerful than WordPress? Read our one of the most popular blogs TYPO3 vs WordPress Controversy (Revealed with Infographics).
This blog contains data & statistics from T3Versions.com, I want to dedicate this blog to Torben (who maintains t3versions.com) and a team who are working hard to research & publish TYPO3 statistics to the community. Indeed, it will help to make the right decisions of TYPO3 future.
IMHO, WordPress is definitely not a poor platform, don't get me wrong, it is somewhere equally potential to hold a tight comparison with TYPO3. But being associated with TYPO3 since 12 years, I firmly believe that TYPO3 deserves more of active audience, users, support and contributing community.
Losing 10K+ TYPO3 Sites Quarterly (From 260K+ Sites)
Last year, 10K+ TYPO3 sites migrated to another CMS or Framework in all four quarters. Of course my friend, Good thing is, we are also getting more new TYPO3 sites too ;)
Sep 2019
From the underlying graph it is depicted to which platforms sites from TYPO3 CMS are migrated to. Around 39% sites TYPO3 sites have been migrated to other CMS platforms in just the month of September 2019.
Apr 2020
Approximately 6266 TYPO3 sites have been migrated to other CMS platforms in just the month of April, 2020.
Oct 2020
15981+ known TYPO3 sites have been migrated till the month of October 2020. Turning in ratio here is less than turning out ratio.
Dec 2020
Till month 2020, it is being clear that most of the TYPO3 websites have been migrated to Wordpress platform. Being stated that TYPO3 is all rounder CMS, but then too why is there a decrease in use of TYPO3?
Which version sites stop using TYPO3?
According to the underlying graphical data from t3versions.com, it is a sign of relief that we have stable versions and people are continuing using TYPO3 post version 7.0 but we can see that we had a lot of audience who tried TYPO3 for their business in earlier period, yet they stopped using TYPO3 for however reasons.
Decrement in TYPO3 Market Share
It is a bit disheartening to see there is constant decrement in market share of TYPO3.
TYPO3 is (only) Enterprise CMS, Really?
That's an interesting myth since the 20 years history of TYPOP3.
Little case study, Many TYPO3 people developed a wrong statement about TYPO3 with a mantra “TYPO3 is (only) for Enterprise CMS”. Now here is the tricky point, many enterprise websites (because it’s developed with TYPO3 CMS) are migrating to WordPress (the CMS known for small scale and blogging purposes).
If the CMS known for development of small-scale websites can serve as the choice for higher-level enterprise websites, then why TYPO3 can not do small-scale websites? Obviously TYPO3 can but there’s something fishy about what’s wrong with small scale website development with TYPO3, Isn’t it?
Is WordPress Competitor of TYPO3?
Yes!! Well, you’ve still doubt? I think the above proof of data and statistics says the same. I remember, TYPO3 people often ignore the comparison between TYPO3 (apple) and WordPress (pears). We should accept, to grow more we should face competition. Take a look at one of the debates about TYPO3 vs WordPress.
What’s Solutions to Stop Migration TYPO3 to WordPress?
Being associated with TYPO3 for more than a decade, I personally believe TYPO3 is worth being used and felt for by people to understand richness. TYPO3 needs more awareness and engagement. Here are some of my opinions that can be helpful to stop TYPO3 migration to WordPress. If only it could be helpful for the change, I’d be more than happy.
TYPO3 Branding & Marketing
- Globalized use of english language
- More tutorials and clear documentations
- More atomization and less complexity to use (Need more ventures like TYPO3 SaaS)
- Reduced complexity in CMS as it is bit difficult for beginners to learn
- Globalized awareness
- Needs more marketing
TYPO3 Site Owner Experience
- Most of the cases TYPO3 calls for requirement of technical knowledge
- Needs better backend usability for editors
- Customizations should be made within CMS
- Moving towards adoption of TYPO3 templates over custom development
- Need more of TYPO3 extensions associated with real problem solving cause
TYPO3 Ecosystem & Marketplace
- Newer versions with modern customer requirements
- More Collaboration with modern technologies
- Supporting emerging innovations and ventures associated with TYPO3
- Encouragement of Sharing, caring and earning concept for flourishment
TYPO3 Education & Awareness
- More local branding
- TYPO3 Knowledge sharing camps
- More of easy TYPO3 books and resources
- TYPO3 Videos
- TYPO3 learning resources for free
- Helping and supporting newbies to get along with TYPO3
TYPO3 CMS is for everyone.
~ Benni Mack
Wrapping-up!
As compared to other popular CMS, the experience of setting up a TYPO3 site as a novice is quite complex and frustrating.
The first major roadblock encountered is documentation, which is sprawling, conflicting, and language barriered. To compete with other CMS, we need to have clear, concise, and consolidated documentation that explicitly indicates the recommended/supported/official way to do things. I trust TYPO3 is ultimately feature rich, flexible and allows us to do things in infinite ways. It's not unique in that way. We can still make things better in multiple ways.
Somewhere TYPO3 lacks the "out-of-the-box" features and marketing for getting quickly spun up on a web server, and it lacks a bit of the simplicity and speed of Wordpress.
I know that TYPO3 holds all the potential for ambitious sites and also one that is a joy to use, even for novices. Phew, this was something I’d like to bring to your notice. What do you think? Do you agree or disagree with the above points? I’d love to know your comments!
Post a Comment
Join over 4300+ TYPO3 Subscribers
Namecheap exists to help EVERYONE get, make, and achieve more online with less cost, hassle, and headaches. We offer everything you need to get online and thrive, from domains to hosting to security to specialist services and products — all with value built in.
Great prices, world-beating customer support, and extra resources come as standard. ==>> https://zeep.ly/rxViL
I'm working as a full-stack developer (Certified Developer and Integrator) mainly working in TYPO3 for the last 8 years. Almost every day I use TYPO3 and I love the technology that much.
I think people like you could market the TYPO3 and its capability as an enterprise-level CMS to the unknown sectors worldwide. I think it can be done from India also. If you could market with real case studies in marketing it would be great!.
One problem I see with the market is most of the clients think like TYPO3 is expensive and difficult to manage. Because the migration/updating versions cost the customer a lot comparing the other CMS. So I hope at least in the future releases of TYPO3, the core team should also think about backward compatibility and migration easiness.
- Lovers are DEVs who like the structured and dev oriented way of TYPO3 and are willing to learn the complex structure (it took me ~2 years as self student to realize what a static template is about) and their clients, because they find a well organized backend and enjoy the pros of TYPO3 (extensibility, security, easy updates and even upgrades)
- Haters are devs without TYPO3 experience (that grab the job, even if their client demands TYPO3 as platform) and their clients. These devs harm TYPO3 most. I could write books about "TYPO3 specialized" agencies that first drilled a hole through all TYPO3 APIs down to PHP, where they now how to do things. Their clients suffer from all down sides of such installations: Not usable (because the backend if often setup poorly), not maintainable, not upgradable.
- There are just those two groups and it takes years to convince a discontent client to use TYPO3 again
- I fully agree with your point that it is still quite complex for a newcomer to properly set up a TYPO3 installation
- The second large impediment I have noticed is TypoScript. Yes, I know why it’s there, but it still takes a long time to fully understand the concepts of all aspects (userTS, pageTS, constants, setup, template module, inheritance, conditions, static templates, stdWrap etc.)
But of course I keep fighting for TYPO3 as long as it makes sense to me to use it. :)