Bootstrap 3The latest release of Twitter’s Bootstrap framework (some 2 months back) has both great as well as troubling implications for web designers who are currently using Bootstrap 2 (including those who have switched over to Joomla! 3). While there is no need to switch over immediately, its new features and a new paradigm means that this will be an attractive option for many.

Not everyone will jump on the bandwagon, of course. Joomla’s core development team, for instance, has intimated that they will not be incorporating Bootstrap 3 until the next major version of Joomla (v4, in this case). This means that Bootstrap 2 will continue to be the primary framework used in Joomla’s core and its extensions until a year from now. But if you want to be on the bleeding edge, then do take these things into consideration:

Bootstrap 3 is mobile-first

A significant (and very extensive) remodeling of the framework means that Bootstrap 3 is optimised and designed in view of mobile devices that may have minimal screen size and a portrait orientation by default. Bootstrap 3, in fact, has RWD in mind all throughout (but its developers understand that not every website should be responsive, and they do allow you to turn it off), and has changed its grid system to suit. In effect, this means that they expect Web developers to design their sites on phone screen resolutions, then make sure they work well when moving to higher resolutions. If you have been designing for desktop resolutions, and then testing for mobile devices, this is a change of paradigm you will have to get used to.

Bootstrap 3 breaks sites based on earlier versions

Simply dropping the new version of Bootstrap into your existing website could cause you a world of hurt. Almost everything has been redesigned and – more importantly – renamed. While there are ways of auto-updating your website from Bootstrap 2 to 3, it is a non-trivial task, and you would be best off checking manually that everything went smoothly.

Bootstrap 2 is no longer officially supported

Unlike proprietary software which has incredible support lifecycles (Microsoft, for instance, has supported Windows XP for a staggering 12 years), FOSS does not (and cannot) sustain such a business model, and is likely to have support lifecycles measured in months. In light of this, Twitter’s decision to drop support & continued development for Bootstrap 2 is understandable. The documentation is still on their website, and obviously expertise in Bootstrap 2 is not going away soon. Official support is not critical for something rarely subject to security vulnerabilities – but it is something to keep in mind.

Older browsers are no longer supported

For most people, this is probably not an issue. But if you do have a substantial number of users still using IE7 and/or Firefox 3.x, either stick with Bootstrap 2, or ask them to upgrade. Globally, the total number of people still surfing with both browsers combined is less than 2%, which is probably why Twitter decided they could drop support.

Progress is inevitable, and by 2015, assuming Twitter hasn’t come up with Bootstrap 4 or 5, we should see widespread adoption of this very popular framework. If you are building a website based on Bootstrap 3 right now, you should take full advantage of its greater ease and versatility. Otherwise, you may want to hold off for a year or so.


We have been on a roll these past few weeks! First was our DPSlider extension, and our case management tool (which, incidentally, is why we may not have been as quick to respond to support issues as we have been), and now I would like to introduce to you our latest free extension: DPAttachments. DPAttachments is a simple but very powerful attachment extension suite, which seamlessly integrates file attachments into articles (or any other component which triggers the onContentAfterDisplay event).

DPAttachments integrates automatically with the following extensions:

  • Content Articles

  • DPCases

  • DPCalendar Events

  • And many more ....

How to use

Just drag and drop files into the article area, and the attachment will be generated automatically. If the file can be viewed in the browser, a preview mode is available, and download tracking comes out-of-the-box as standard.

There are plenty of use cases for this extension; I’m sure you will have your own, but here are a few (just to get your creative juices flowing):

  • Menus and business card attachments when food blogging

  • Flyers, brochures and coupons or vouchers when promoting a new product

  • Videos for HOWTO articles (as opposed to using YouTube to stream)

  • Screenshots for reporting support issues

  • Files as additional information for events

If you have any other ideas, send them along to us!

Behind the scenes

On a technical note, DPAttachments attaches files to Joomla items like articles and inherits it's ACL settings. This means that you can use this extension without worrying who can manage attachments on a new place. The attachments are stored locally on your website, and the Joomla site administrator can remove them if space constraint issues crop up.

If you want to integrate DPAttachments into your own component, do read the developer guide at – it only takes two lines of code, and you extension does support attachments.


DPAttachments is in its early stages and a preview release can be downloaded by our active DPCalendar subscribers from our download portal. After further testing and feedback from you, we will then make it available for free to the public. This is a big THANK YOU for your support all over the years for Digital Peak!!

We do plan to have additional features built into it, and be reassured that we will constantly (and vigorously!) be auditing our code to ensure the highest compatibility standard with the Joomla codebase, along with the new features. Please keep in mind that DPAttachments runs on Joomla 3.1 or higher only.

joomla peopleIt’s no surprise to anyone that Joomla has a commanding hold on the marketplace. It has a robust, multi-platform ecosystem of hosting companies, consultants, developers and other ancillary support resources for those who develop websites on Joomla. Since 2005, Joomla has gone forwards 3 major versions, added support for Responsive Web Design, spawned thousands of extensions and with the forthcoming native support of structured data, remains ahead of its time.

But Joomla started out as a fork of Mambo, a previously open-source (and now mostly-dead) Content Management System (CMS). A short read through of the history behind this fork can send chills down any developer’s spine. Could the same thing happen to Joomla, and if so, what happens then? The questions which arise do not have much to do with Joomla as a technical achievement, and everything to do with Joomla as a product supported by fallible human beings. So, let’s take a look at who’s behind Joomla, and whether you need to worry about its future.

In the real world, Joomla can be considered to be represented by two groups of people; its administrators, and its programmers. Joomla’s Leadership Team together is made up of both administrators and programmers, and they work closely together to ensure that the spirit of Joomla is carried out both in its daily operations, as well as in its project development.

The day-to-day administration of Joomla (and its assets) is handled by a non-profit organisation incorporated in the USA called Open Source Matters (OSM). Amongst other things, the volunteers in OSM largely handle the financial aspects (keeping Joomla well-funded and paying the bills), legal issues (sign contracts & other legal documentation, watch out for copyright/trademark infringements) and regulatory affairs (a matter of internal corporate governance). Oh, and they maintain Joomla’s various assets (such as the Internet domains). Most of the OSM Board also contribute to Joomla in other ways.

Joomla’s core programmers, on the other hand, concentrate on the software development and user experience aspects of the Joomla platform. These, too, are volunteers, and functionally separated into 2 groups; the Production Working Group (which handles code, language and documentation) and the Community Working Group (which handles the people populating the Joomla ecosystem and the communications between these various stakeholders with Joomla). Each working group has its own specialised teams specifically in charge of various key aspects of their responsibilities (e.g. Production has the Joomla Bug Squad, which identifies and fixes Joomla bugs, while Community has the Joomla User Groups Team, which supports the various Joomla User Groups).

When Joomla was initially set up, its key personnel came from Mambo, and their intention was to ensure that Joomla would not have to face the same issues that Mambo did. Hence, they spent a great deal of time crafting their mission and vision statements, as well as determine the necessary processes by which OSM remains accountable to what Joomla stands for, and true to its values.

But why only take them at their word? As the saying goes, trust… but verify. Hold them accountable for whatever they say, and make sure that they carry out their intentions in what they do. Open source does matter, and by keeping a close eye on them, you do your part in ensuring that Joomla will remain a premier open source CMS of choice for the foreseeable future to come.

dpsliderI thought I would take the opportunity to announce (and introduce you to) DPSlider, our newest free extension for the Joomla! CMS. DPSlider is a content slider module that provides you with a responsive, touch-enabled page section through which multiple (up to 10) ‘sub-pages’, or slides, of content can be displayed in a slideshow fashion. Each separate slide can be swiped/dragged left or right to display the next slide (we have enabled wraparound so the last slide will wrap to the first and vice versa), or you can click on any individual slide on the position indicator to directly display the contents on that slide.

You can use DPSlider for various purposes; as we have used it on our DPCalendar product page for explaining its (DPCalendar’s, that is) individual benefits, in a photo gallery to ‘flip’ through different pictures, or as a drop-in streamlined (yet still surprisingly powerful) replacement for SlideShare or other presentation slide deck viewers. Or think up your own use; you’re limited only by your imagination.

DPSlider is still in its early days yet, so documentation is somewhat sparse on our site, and of course, there are a number of features we plan to add over the course of its development. However, as it is now, it is 100% usable and will add some fun (and functionality) to any existing Joomla-powered website. So do keep a watch out for new cool things we might do later (e.g. more slide transition effects, higher number of slides supported, autoplay option, 3D, that sort of thing), but in the meantime, this is a lightweight alternative to the other slider extensions you may have seen.

Here is our listing in the Joomla Extensions Directory, and have a look at our documentation on our own website. See how it works on our DPCalendar web page. You can get a copy of the source code from our code repository on Github  and play around with it a bit, or even fork it and create some pull requests. I highly encourage you to try it out, and do let us know what you think about it. Who knows, the next revision might have your ideas in it!

This Joomla module is free of charge and can be downloaded withou registration and can be used without any limitation. That's a thank you to the Joomla community!

Mad props go out to, and especially their Swiper slider, which is where we, er, “swiped” and adapted some of the code (thanks, guys!).

dpcases releasedSince many years we have used a forum to interact with our customers. To handle the cases efficient, we at Digital peak decided that we need a more profesional solution. After testing out many solutions from trackers to project management tools we decided to create our own one. This was the birth of DPCases a professional case management tool where you can

  1. Assign cases to users
  2. Status per case
  3. Using tags for horizontal classification
  4. Organising in categories
  5. Due dates
  6. Commenting
  7. Attachment support

We launched it today. At the same time we made the forum readonly and closed our ticket tool. We know it is a new direction we are heading to and it wont be without trouble at the beginning, but we are sure it will be the right choice. If you encounter any issue let us know by opening a case :-). Every case should be filled with as much information as possible and comments should be done carefully. Our target is to create a powerfull knowledge base for our customers.

We hope you are happy with our new too and excited as we arel!!


We use cookies on our website. Some of them are essential for the operation of the site, while others help us to improve this site and the user experience (tracking cookies). You can decide for yourself whether you want to allow cookies or not. Please note that if you reject them, you may not be able to use all the functionalities of the site.