Altabel Group's Blog

Archive for June 2013

All of these mobile devices were supposed to make our jobs easier. On a flight? Edit your presentation from your tablet at 10,000 feet. Working from home? Review a time-sensitive document on your smartphone. This was the popular narrative on-the-go workers told themselves, and it was a good story – but it was a fictitious one.

Editing a Word document on an Android phone was not easy, nor was editing an Excel spreadsheet on an iPad. The Microsoft Office that workers know today is still stuck in its original design meant for a desktop computer. And when mobile users tried to download workaround applications, they often found so-called solutions that failed to live up to their promises. That, finally, is changing.

The market is now producing tools that offer a true fix to the mobile workflow challenge, with functionality to address every pain point that has throbbed in recent years. We have entered an era of all-in-one mobile productivity, although the difficulties of the recent past have left mobile enterprises skeptical of a brighter present and future.

That skepticism is understandable. Because Microsoft doesn’t offer an Office version for iPads, Android phones or any of the other popular mobile devices or operating systems that today’s workforce uses to stay connected, those workers had to build their own connectivity to their offices, coworkers and clients. For example, if a mobile worker wanted to revise a Word document on an iPad, he might have a complex recipe in place to make a few simple edits, and now IT solutions have arisen to fill each gap:

Step one: gain access. To even open the file, the mobile worker had to email the attachment to himself or open an account with a cloud storage service like Box.

Step two: view the file. Next, he might have downloaded an operating system-agnostic productivity app like Open Office to open the file on his mobile device and see whatever text, tables or graphics it contained.

Step three: edit or annotate. This can be the most difficult step, since some viewing apps don’t offer editing capabilities. At this stage, an additional annotation app comes into play for writing notes or changing the Word file.

Step four: save and share. To share an edited, annotated file from his mobile device, the user might have opted for Box or Dropbox. Enterprises should use more stringent criteria to leverage combined file access, viewing, editing and sharing on one interface for mobile enterprise workers. There are several mobile-friendly apps that aim to replicate the editing control you have from your desktop, while also building the cloud’s accessibility into their DNA.

Step five: secure. While it’s important that mobile workers can access files from anywhere, risk-averse enterprise users also have to ensure that unauthorised parties can’t access those files. Dropbox and Box have begun building security controls to accommodate enterprise security needs, such as permissions in Dropbox for Teams; however, these controls pale in comparison to security applied directly to a file, rather than the cloud compartment it lives in, for the inevitable point when that file is shared offline, outside the cloud.

IT department concerns with compatibility are no longer limited to “dumb” phones that are solely used for calls or simple text emails. The next generation of enterprise IT problems involve ensuring file compatibility and security across operating systems. Some organisations will even limit employees’ bring-your-own-device (BYOD) practices to one OS (like an iPhone) altogether just to avoid the issues that stem from this type of segmentation. The result has been frustration among on-the-go employees, suppressed productivity, and company fear regarding mobile access.

This trend will only continue to grow. By 2017, according to several forecasts by Gartner and Forrester, tablet sales will outnumber desktop sales. In addition, we’re likely to see mobile phone shipments (mostly smartphones) grow to more than 2 billion in 2017, according to Gartner.

To keep pace with the growing employee demand for mobile access and collaboration solutions, businesses must rely on technologies that keep information safe and increase mobile productivity, which is a combination rarely seen in today’s market. This means scrapping piecemeal solutions that only address one aspect of the mobile-user experience and implementing an all-in-one solution that facilitates secure access, editing and collaboration, and control over a file’s complete lifecycle in order to track recipients and revoke access at anytime if needed.

The future belongs to computing on the move. That future is now for enterprises and employees that select secure, native Microsoft Office functionality and collaboration tools for their mobile devices.

To conduct everyday business, mobile users have been forced to download multiple apps to help them access, edit and annotate Microsoft Office files. They have settled for insecure cloud file services for sharing. The time for settling is over. Enterprise IT needs to deliver instant access to any file from anywhere, and companies can now achieve this. Mobile devices were supposed to make our jobs easier. With the recent evolution in mobile collaboration tools, they do.


Kristina Kozlova

Marketing Manager



Altabel Group

Professional Software Development


Responsive web design isn’t the future, it’s the present

In our humble opinion it’s late to debate whether responsive web design is the future because it’s already the present of everybody’s business represented online. Consumer/client behavior has been changing. According to statistics and analysts’ predictions, for instance, for the first time since 2001, PC sales are projected to be lower than they were in 2012; smartphone sales will double PC sales in 2014; tablet sales are expected to exceed 100 million this year and may top notebooks next year. So the shift to mobile is happening at an extraordinary speed, and tablets and smartphones are becoming extremely popular for business and pleasure matters. This means people view your content on thousands of oddly shaped and different sized screens. What’s more, according to Google research, mobile users “expect their mobile experience to be as good as their desktop experience” – this expectation poses a thorny challenge for both, business stakeholders and web designers and developers.

So this is no longer about “How do I make my website available to a smartphone or tablet?” – it’s “How do I make my business available in smartphone and tablet context?”. For some business it’s not important – it’s literally critical, for example: according to the Pew Research Center, 60% of tablet users prefer reading news on the mobile web than via an app; the same percentage is quite common for e-commerce sites according to Google Analytics and that’s why RWD has been listed in E-commerce marketing checklist for 2013. If you wish to identify the percentage of your audience that use mobile devices use the Google Analytics Mobile Overview report feature: if mobile users are more than 5% of your total audience you should consider catering for them too.

In general, there are three main approaches to providing information and interaction to mobile/tablet device users : responsive (and adaptive) web design, mobilized websites, and mobile apps. It’s important to understand that these are different marketing channels and their value proposition is very different. A mobile web site may do something very different from a mobile app – simply said, “if your goal is just to display and show content beautifully create a responsive or mobilized website; if your goal is to show productivity tools, build an app”. Which option is the best for your business will depend on your use case, your users’ habits and your budget.

Responsive web design vs mobile web development: advantages and challenges

To talk about advantages of responsive web design, let’s start from its definition. RWD is a front-end development approach aimed at crafting device agnostic sites. It uses “media queries” to figure out what resolution of device it’s being served on. Flexible images and fluid grids then size correctly to fit the screen. So responsive design provides easy reading and navigation with a minimum of resizing, panning, and scrolling, and eliminates the need for separate sites for different devices. Adaptive web design is either a subset of responsive design, or a related approach. “Responsive design will show more stuff or less, optimized for a mobile layout, but is likely to still provide access to the full desktop-view’s content. Adaptive design, by contrast, might show very different content, and also present a different UI, reflecting touchscreen’s tap/swipe/scroll versus desktop’s keyboard/mouse interaction.” In either case, responsive (and adaptive) web design will be based on the same code as a desktop site, and will locate on the same URL.

– In the definition above a couple of advantages of RWD are pointed out. Indeed, it improves user web browsing experience since a website adapts to the browser or device compatibility automatically and makes the content look good. For customers it shows that your business is receptive to changing technology and understanding of consumers’ needs.

– From business perspective, “one website – multiple devices” concept means that it’s easy to manage and focus on developing good content for your website. The same applies to analytics and strategy development and deployment since there is only one set of analytics to examine and a single strategy to develop and deploy. From maintenance standpoint, the technique is great too as one update affects all of your platforms.

– Additionally, responsive websites are easier for consumers to find than traditional or mobile web sites because they come up higher in search engines’ rankings. “In fact, Google recommends responsive web design because having a single URL for desktop and mobile sites makes it easier for Google to discover content and for Google’s algorithms to assign indexing properties to content.”

– One more advantage from the future perspective, as Resnick predicts, is: “As the internet transforms further into a platform of services and user interfaces that tie those services together, leveraging RWD technology in the future will allow companies to integrate a plethora of back-end services, such as Facebook, Twitter,, and Amazon Web Services, and then present the integrated data back out the front-end iad layer on a responsive design so the application looks great on all devices without custom coding needed for each device or screen size. No longer are expensive back-end solutions needed to integrate legacy systems with business partners.”

Actually responsive web design is quite immature so it faces many challenges too.

– Even though we might view a responsive website on a smaller screen and it displays less visible content or smaller-sized images, this does not mean that the site will load faster. The thing is that from one side responsive websites are not much smaller in download size when viewed on smaller devices or screen resolutions compared to when being viewed on a desktop browser jacked into a broadband internet service provider, on the other hand mobile internet speeds still lag much behind broadband internet ones. Thus responsive web sites need advanced optimization, such as serving smaller images and conditionally loading scripts, and much more. An alternative may be found in dedicated mobile web development solutions since they specifically address mobile devices.

– The related issue concerns complexity. Responsive web designs are inherently complex because they are trying to support many viewing experiences without necessarily optimizing the experience for one particular device (or genre of devices). Mobile browsers will have to deal with a big HTML file, and the site would need to carefully avoid running specific scripts, loading certain CSS and download large images. Perfect implementation is possible, still avoiding over-resourcing requires scripts or code and therefore additional complexity. Typical “m dot” site wins in this case and is simple. It usually has a small amount of HTML, limited scripts, CSS, and images (if at all) as it is built specifically for its intended small-screen, touchscreen mobile devices viewing experience.

– As for UI and UX, responsive websites have limitations here. Not only in screen size, they are also limited for utilizing or recognizing key mobile features such as user location, connectivity, device limitations, software potential, and user needs. Mobilized sites and mobile apps will provide broader opportunities and advantages here.

Information architecture can be an issue. It needs to be carefully considered and should be hierarchically structured before the design implementation.

Advertising is an issue. Ads will have to shift with the sites, something that will wreak havoc with advertisers who want guaranteed placements on sites.

So, which approach will or do you use to present your business online?

HTML5’s momentum and Best tools for responsive web design

Responsive web design is not a specific technology but a whole design approach. However, responsive design is enabled primarily by CSS3 and JavaScript, which fall under the banner of HTML5. HTML5 is really maturing in terms of its functionality and, more importantly, its speed. So now HTML5 is the backbone of the new and interactive features of responsive web design.

To achieve a smooth flow from a large screen to a small one it takes a lot of patience and perseverance. To reach a seamless result there are a number of tools that help you with it. Below you will find a list of best responsive design tools broadly recommended in the web as well as by Altabel’s dev team:

1. Gridset
A tool that helps you design, prototype and build any type of grid layout required – columnar grids, asymmetrical, fixed, fluid or responsive grids. It even lets you create a library of your own grids, with a variety of presets available. It will allow you to build responsive prototypes (without all the calculations) very quickly and easily, providing all the measurements and tools to integrate with your existing markup.
Alternatives: Frameless, Tiny Fluid Grid, Gridpak, SimpleGrid, Responsify,, Golden Grid System and Photoshop Grid for Responsive Design.

2. Bootstrap
An intuitive and powerful front-end framework from Twitter to start a responsive website fast and easy. It addresses the most popular user interface components and interactions, uses a 12-column responsive grid system with simple and flexible HTML, CSS, and Javascript and features dozens of components, styles and JavaScript plug-ins, with basic global display, typography and link styles all set. It also gives the option of customizing components of your website for instance by using the Customizer .
Alternatives: Skeleton, Foundation, Base, InuitCSS, LESS Framework, Gridless, 320 and Upand Gumby.

3. Wirefy
Clients wish to see how wireframes will adapt to different device sizes. Static wireframes aren’t particularly useful to show a client how responsive your design is, or what functionality is being suggested. But rapid prototyping by building flexible wireframes may. Wirefy is a collection of functional responsive HTML snippets and templates that scale as the browser is resized (working across multiple devices). It builds on tools such as the Frameless grid system and Bootstrap, and uses CSS media queries that adapt to different device resolutions. Wirefy focuses on key elements such as typography, tables, images, slideshow, forms, tab panel, paginator, menu, etc., focusing on the users.
Alternatives: Froont, Interactive Style Tiles, Responsive Sketch Sheets, Responsive Wireframe Template, Interface Sketch Templates, Responsive Device Diagrams, Wirify.

4. FlevNav
Navigation strategy is a really critical component of any responsive website design. FlexNav is a jQuery plugin that takes a device-agnostic approach to complex site navigation. It is a mobile-first concept using media queries and JavaScript to create a menu with drop downs. It features multiple nested sub-menus, with support for em units and tap targets to reveal sub-menus for touchscreens.
Alternatives: TinyNav.js, Navigation Patterns for Responsive Design, MeanMenu, Responsive Solutions for Menu Navigation, jPanelMenu.

5. Adaptive Images
Previously, making your website images responsive was tricky and usually meant using a “hack-around”. Now several tools may simplify this task. Using a one htaccess file, one php file and a single line of JavaScript, Adaptive Images detects screen size of browsing devices, cashes and delivers device appropriate re-scaled versions of your web page’s embedded HTML images without any mark-up changes. Also it is entirely non-destructive, and works on existing websites and markups — without the need to edit anything. Adaptive Images works on the premise that you are already using the highest-resolution images on your site, and also offers a ton of customization options.
Alternatives:, jQuery Picture, ResponsiveImg, Retina.js and Retina Images.

6. FitText
As content scales according to a user’s viewport, the text will naturally wrap as the container is narrowed; and this often causes widows, orphans or your headlines to look rather ugly, and can even break the entire layout. FitText is a jQuery plugin specifically for headlines and big text. It auto-updates the font size according to the width of the element wrapping it, so you can achieve scalable headlines and a non-broken layout that can be caused by font-sizing issues. FitText works perfectly with Lettering.js or any CSS3 property thrown at it. There are options to fine-tune the text, including the ability to set min-max sizes and the level of scaling. Still FitText is only for headlines, and shouldn’t be used with paragraph text.
Alternatives: BigText, Lettering.js, Kerning.js, Kern.js, Type Butter and Slabtext.

7. Responsive Slides
This lightweight plugin allows you to create a responsive slider using elements inside a container. The images have to be the same size and jQuery 1.6 and up should be used. You can keep captions and other non-HTML elements inside the slides, while also using CSS3 transitions with JavaScript fallback. It works in all major desktop and mobile browsers, can support multiple slide shows, have settings for transition and timeout durations, automatic and manual fade, and have options for customization.
Alternatives: Flex Slider, Slides.js, PhotoSwipe, Supersized, Camera, RefineSlide, BlueberrySequence.js and Galleria.

8. Responsive Tables
Data tables in responsive design can be troublesome: you want it to not break responsive layouts, not hide content, let you see entire rows and columns, not be too small to read easily or zoomed in too far requiring scrolling. Here ZURB comes out – a simple JavaScript/CSS combination containing two key files: responsive-tables.js and responsive-tables.css. It works by taking the first column, which is often the unique key for a table, and “pinning” it to the left of the table, allowing you to scroll the other columns under it.
Alternatives: Responsive Data Tables, Stackable.js, Footable, Responsive Tables, Responsive Tables, Responsive SEO Friendly Data Tables.

9. Responsive Design Testing
Building a responsive website means constantly testing how it displays across mobile and tablet devices. You could resize the browser yourself, or use a browser extension or tools within your IDE; but there is an extremely simple tool that allows you to see how a page displays on different screen sizes, in a single view. With Matt Kersley’s RWD testing tool you just have to enter your website’s URL into the address bar to test a specific page in different widths and device sizes. Also you can share the results of the test with others by adding any URL to the end of the testing page address. One major benefit of this tool is that it can be self-hosted (available on GitHub) by downloading and installing it on your own site. You can then navigate through the frames that your website appears in, testing the entire site effortlessly.
Alternatives: Screen Queries, Screenfly, Responsivepx, Responsinator, Responsive, and Resize My Browser.

10. Respond.js
The problem with media queries in responsive web design is that they are a part of CSS3 specifications so they do not work with older browser versions such as IE8 and lower. Respond.js comes to the rescue for browsers that don’t support media queries directly, translating any media queries it finds into equivalent JavaScript.The script itself is incredibly small and lightweight. It works unobtrusively, and doesn’t rely on any other scripts or frameworks to run.
Alternatives: Modernizer, Adapt, Categorizr, CSS3 Media Queries and Enquire.js.

The tools above are ultra useful for any RWD project from the planning and designing phase right through to testing, and what’re your favorites?

Welcome to share your view points.

Helen Boyarchuk

Helen Boyarchuk
Skype ID: helen_boyarchuk
Business Development Manager (LI page)
Altabel Group – Professional Software Development

Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

Today comparing software on a market is a difficult task. Each product comes from a market / technology niche with great specific features developed by passionate people and open source lovers. There is no doubt the most appropriate CMS will depend on what one is trying to use it for, but let us try to have sort of a general comparison and see what definitely should be on our Java CMS shortlist.

There are so many Open Source Java CMS but let me focus on some of them which are considered quite popular now and they are Hippo, Magnolia and Jahia.


Hippo contains an optimal combination of enterprise architecture capabilities, fast development possibilities and values of open integration. It enables you to gain the power to be open for integration with any technology that you require to manage, optimize and create high-impact customer experiences.

This CMS is really about managing content for multi-channel publication: web, mobile, social, print, etc. Separation of content from presentation is the cornerstone of the product.

Speaking of analytics systems like Webtrends, Omniture and Google Analytics Hippo CMS makes it possible for you easily embed tracking codes into content to feed analytics systems. You can also observe your content effectiveness, as Hippo exposes data collected by analytics systems in the CMS.

In terms of ecommerce, Hippo has been integrated with many custom eCommerce solutions. Take ATG, Konakart, Magento and IBM WebSphere Commerce as example. Due to the open interfaces of all Hippo components, it works whatever eCommerce system you chose.

Hippo format neutral way of managing content makes it a great source for publishing into portals. So, if your extranet or intranet runs in a portal environment, then it is not necessary to rebuild it with Hippo if you want to increase it with centrally managed content. Hippo plays nicely with all major portals and has been integrated with portals like Liferay, JBoss, SAP and Websphere Portal.

Hippo Pros:
• flexible content structure & faceted navigation
• integration with some external applications
• portal alike functionalities/ integrations
• a lot of sub-sites with sharing content capabilities


Magnolia powers the websites of government as well as leading Fortune 500 enterprises in more than 100 countries on all continents of the world. It is a leading CMS favored for its ease of use and license. The page editing interface enables authors to lay out content exactly as it would appear to the Web site visitor.

Magnolia is similar to Hippo in lots of ways, except that it’s very much focused on managing smaller, “single” websites. Magnolia CMS is not a framework to build web applications, however can be used to manage data. You can for instance manage products and use them as content for web pages.

Authors no longer need to switch between different navigation mechanisms to make a small change, but they can instantly edit any page in their browser.

Magnolia’s inline-editing feature ensures that editors see content paragraphs in their right context at all times, reducing the switching between working modes.

Magnolia has been designed for heavy-load enterprise websites, having a low memory footprint, a smart cache, built-in clustering capabilities, a distributed deployment architecture that decouples authoring from publishing and the possibility to build load-balanced public servers to provide more throughput and availability.

Magnolia Pros:
• good for smaller sites (content related); although, Magnolia can be used on quite big sites as well
• need in page editing/inline editing (this is possible within Hippo CMS but Magnolia is bit easier to setup)
• you only have page(content) based site/navigation. Hippo solution is much more flexible in this regard.


Jahia delivers web content integration software by combining enterprise web content management with document and portal management features. Jahia is content centric depending on the type of project you envision, this is a major difference. The granularity of Jahia’s content model offers a deeper control on each content item. This provides greater benefit when it comes to repurposing, reusing content or controlling precisely how your content should behave (roles, workflow, layout, display options, etc.). Of course, these advantages need to be balanced with the specific objectives or your project. For a basic website scenario, this granularity is perhaps not necessary and Magnolia may be an easier choice. For intranet or portal scenarios, complex websites or content based applications, the Jahia model and its widely recognized flexibility may be more appropriate.

Jahia works great with structured content. For instance, Jahia offers options beyond the unique paragraph concept – more suited to create unstructured objects that must be displayed in a page, it offers a variety of additional objects with multiple properties you can manipulate, sort, validate, repurpose, etc. You can obviously decide to only use a simple, unstructured approach in Jahia but the ability to really declare, control and manipulate a wide range of additional object types is very powerful in more complex scenarios. Also important is that all Jahia editing UIs are auto-generated based on simple content definitions: not having to create your own input masks is a huge time saver and cuts development time.

Jahia embeds several frameworks that are very important if you plan to manipulate your content through API and code, and if you want your Jahia instance to interact with other apps / systems, some of the most important ones are) Jboss Drools, Apache Camel, jBPM.

Caching mechanisms in Jahia is based on long experience fine tuning performance for large and high traffic websites: there is a sophisticated and efficient caching solution that deals with both automatic invalidation and expiration. This allows avoiding dependencies and flushing management problems, which is key to complex, large and/or interactive sites scenarios.

Jahia Pros:
• deep control on each content item due to granularity of Jahia’s content model
• good for working with structured content
• good for large and high traffic websites

The CMSs under review have their differences but also have something in common. It might be interesting to note that all three products actually use the same storage technology: Apache Jackrabbit, which is the reference implementation of the Java Content Repository API. This ensures some guarantee as to the possibility to migrate in/out the content relatively easily.

You are welcome to make Java CMS shortlist of your choice longer with other products as well as to share your comments and comparative analysis details on the given ones. It would be really great to learn more on this subject as well as get to know your experience.

Thank you!

Aliona Kavalevich

Aliona Kavalevich
Skype ID: aliona_kavalevich
Business Development Manager (LI page)
Altabel Group – Professional Software Development

The stumbling block for many companies and the reason why organizations fall behind in the planning and pre-planning stages of big data, appears to be confusion on how best to make big data work for the company and pay off competitively.

With all the talk about rapid deployment and breakneck business change, there can be a tendency to assume that businesses are up and running with new technologies as soon as these technologies emerge from proof of concept and enter a mature and commercialized state. However, the realities of where companies are don’t always reflect this.

Take virtualization. It has been on the scene for over a decade-yet recent research by 451 Research shows that only 51 percent of servers in enterprise data centers around the world are virtualized. Other recent survey data collected by DataCore shows that 80 percent of companies are not using cloud storage, although cloud concepts have also been with us for a number of years.

This situation is no different for big data, as reflected in a Big Data Work Study conducted by IBM’s Institute of Business Value. The study revealed that while 33 percent of large enterprises and 28 percent of mid-sized businesses have big data pilot projects under way, 49 percent of large enterprises and 48 percent of mid-sized businesses are still in big data planning stages, and another 18 percent of large enterprises and 38 percent of mid-sized businesses haven’t yet started big data initiatives.

The good news is that the study also showed that of those organizations actively using big data analytics in their businesses, 63 percent said that the use of information and analytics, including big data, is creating a competitive advantage for their organization–up from 37 percent just two years earlier.

The stumbling block for many and the reason why organizations fall behind in the planning and pre-planning stages of big data, appears to be confusion on how best to make big data work for the company and pay off competitively.

Big data projects need to demonstrate value quickly and be tightly linked to bottom line concerns of the business if big data is to cement itself as a long-term business strategy.

In far too many cases when people plan to build out a complete system and architecture before using a single insight or building even one predictive model to accelerate revenue growth. Everyone anticipates the day when Big Data can become a factory spitting out models that finally divulge all manner of secrets, insights, and profits.

So how do you jump start your big data efforts?

Find big data champions in the end business and business cases that are tightly constructed and offer opportunities where analytics can be quickly put to use.

When Yarra Trams of Melbourne Australia wanted to reduce the amount of repair time in the field for train tracks, it placed Internet sensors over physical track and polled signals from these devices into an analytics program that could assess which areas of track had the most wear, and likely would be in need of repair soon. The program reduced mean time to repair (MTTR) for service crews because it was able to preempt problems from occurring in the first place. Worn track could now be repaired or replaced before it ever became a problem-resulting in better service (and higher satisfaction) for consumers.

Define big data use cases that can either build revenue or contribute to the bottom line.

Santam, the largest short-term insurance provider in South Africa, used big data and advanced analytics to collect data about incoming claims, automatically assessing each one against different factors to help identify patterns of fraud to save millions in fraudulent insurance payments.

Focus on customers

There already is a body of mature big data applications that surround the online customer experience. Companies (especially if they are in retail) can take advantage of this if they team with a strong systems integrator or a big data products purveyor with experience in this area.

Walmart and Amazon analyze customer buying and Web browsing patterns for help in predicting sales volumes, managing inventory and determining pricing.


Kristina Kozlova

Marketing Manager



Altabel Group

Professional Software Development


There are many good open-source CMSs for web development. TYPO 3 is one of them. Although it is considered to be a really powerful CMS, but does it mean it serves well? Will it be appropriate for your website? Why use it and not some other CMS? To answer all these questions let’s try to understand if it is the right choice for you and why it is so.

TYPO3 is a powerful open-source, enterprise-class CMS Platform based on PHP, designed specifically with the needs of both enterprise and corporate clients in mind. Many CMSs are intended for specific types of websites. For example Magento is great for e-commerce web sites when WordPress is ideal for blogs. As for TYPO3, virtually it fits any website type: home pages, blogs, newspapers, blogs, e-commerce, educational, etc.


• The first and probably most powerful advantage of TYPO3 is that it is a universal system. There exist over 2000 extensions to TYPO 3. When you install these extensions, you add corresponding functionality to TYPO3 at the same time keeping the power of the TYPO3 core and functionality added by any other extension. It means you can have for example a blog, a shop, support section and many more all at once. This is true universal solution. And it is all manageable using TYPO3 Backend. If you need something new, you just install an extension and you get the functionality. You don’t need to install WordPress or Magento on top to add some kind of shopping to your blog. You do not have to login to blog and shop separately like in case of WordPress and Magento. With TYPO3 you login once and you have access to everything you need. You can even refer from your blog to your products. If you rearrange pages, TYPO3 will automatically ensure that links still work.

• Another advantage of TYPO3 is a very flexible user system. Many systems allow only one administrator user. But with TYPO3 it’s possible to have as many administrator users as you want. You have access control over everything that is really important. Users can also be assigned to groups-“Editors” or “Reviewers”-so you may assign user rights to the whole group. Every user can be assigned to as many groups as you wish, which makes TYPO3 incredibly flexible.

• In TYPO3 you have real pages. Not just a flat list of pages where you have to invent titles and later search for a long flat list. With TYPO3 you have a real page tree where you can group pages as necessary, reuse parts of the page tree from other parts through shortcuts or mount points.

• TYPO3 comes with lots of types of content that you can create. These types are optimized for the best presentation of the content. For example, you can create a text, or text with image. Image can be opened in a separate window when it is clicked making a very easy enlarge-on-click feature. And editors do not have to bother about it much: they just turn on a check box that enables this feature. It is that simple! Tables, forms, multimedia – all is available with lots of tuning possibilities. It is an incredible degree of control over web site look.


• First of all, TYPO3 is large. So it needs a good hosting. If you run a company you can afford it, so it is not a great disadvantage. TYPO3 can run on a shared hosting too, though it is not the best hosting case for it. So need for a good hosting is a price to pay for a good system.

• Another often heard disadvantage is that TYPO3 is difficult to learn. But it depends. TYPO3 can be used by three types of people: editors, administrators and programmers. Learning becomes harder with each next group. It is easy for editors to learn TYPO3. Not as easy as WordPress (because WordPress is a very simple blogging-only tool) but still easy. If you are administrator, you need to manage TYPO3, write TypoScript, install modules, etc. This requires learning. It may take from several weeks to 2-3 months depending on your learning ways and enthusiasm. But the result is always rewarding. If you are a programmer, it is the longest learning curve. Knowing how to program in PHP does not mean that you can write a good TYPO3 module. But if you compare it to other systems, it is not different. Every system will require learning, so this is not truly a disadvantage. So, yes, it will take time to use TYPO3. But it is worth the result.

• Sometimes people say that being open source is a disadvantage. Open source is often driven by a group of enthusiasts and there is no support. Fortunately, there are lots of very professional companies, who can provide TYPO3 support for you. So, if you can’t do something “in house”, you always can get help and learn how to make it.

So, advantages are obvious and huge, when disadvantages are minor and temporary until you learn.

TYPO3 CMS is used by over 300,000 web sites, ranging from corporations and universities to small businesses and non-profit organizations. Some of the users of TYPO3 include: Volkswagon; New York Times; Lufthansa; Ford; Samsung; Stanford University; General Electric. Will you be the next to use it? 🙂 Do you agree that this CMS is really worth learning and using it? As always, eager to hear your comments!

Yuliya Tolkach

Yuliya Tolkach
Skype ID: yuliya_tolkach
Business Development Manager (LI page)
Altabel Group – Professional Software Development

%d bloggers like this: