LimeSoda Blog

Typo3 with integrated blog

The situation: a client wants a website with pages in the navigation structure that contain blog posts. These pages should support the same functionality as what WordPress offers:

Solution number 1: Typo3 + WordPress

The power of both systems could be connected to each other to fit the needs of the client. The client will have access to both the Typo3 and the WordPress backend. Normal page content can be added/edited through Typo3, while blog posts will be organized by using the WordPress backend.

The pros and cons of this solution are:



Solution number 2: Just Typo3

There are some extensions available for Typo3 that will add blog functionality to the system. The main to extensions are Timtab and T3blog. Timtab is unfortunately very outdated; the latest update is from 2006. T3blog is more up to date. According to the the manual of T3blog, it supports posts, categories, tags and blogrolls.



Solution number 3: Just WordPress

The third solution is that instead of Typo3, WordPress will be used as CMS. WordPress will take over all the work, so every kind of content can be edited/added from 1 backend.




WordPress has a very large fan base, and a very large database of plugins. Features like pagination, social bookmarks or related posts are available through downloadable plugins. These plugins work very well, and need little customization. Then there is of course the advantage of adding little blocks with cool functionality as a widget in the sidebar. There are thousands of these widgets available.

Typo3 on the other hand is a dedicated CMS with some very powerful features. The menu system is one of them. Even at large websites with a lot of pages, Typo3 manages to keep the backend clear. WordPress lacks in this region.

WordPress can be customized so that it will behave as a CMS but compared to Typo3, WordPress is bad coded and it can be pretty difficult to extend the website in the future according the needs of the client.

So, using Typo3 as a main CMS with WordPress to manage the blog pages seems the best solution. WordPress will have to be installed on a subdomain, and it will be visible in the URL. This has not a negative influence on SEO or on the usability of the website.

Noch keine Bewertungen.