Making your site as cache-able as possible is vital to ensure a smooth browsing experience. WordPress in it’s basic form is quite efficient, when you compare it to code-bases such as Magento. Adding functionality such as plug-ins, media, themes and widgets all have a negative effect on performance. As part of the process of making this domain as efficient as possible, a number of caching techniques have been considered and employed.
Developing bespoke components for Joomla can be quite daunting. There are a lot of resources, books, dev articles and the API documentation; these try to give you a basic understanding of how things should be laid out. A lot of these work on the premise of learning by doing. Many of the documented examples from the API point developers to look at the core components to see how it works.
Configuring an effective component router can be quite tricky, as it depends on how complex your component is. This article serves as a reference for how routing works in Joomla, why it’s important, and how you could make better use of component routing in your projects.
I have been dealing with file uploads a lot recently, and I stumbled upon a few different methods for validating files which provide both basic file-type checking and file size checking before uploading.
The web app was already making use of jQuery with the excellent jQuery validation plugin; so I wrote a couple of extended validators.
For years, web designers have been yearning for custom fonts in web design. It’s a real shame that web fonts didn’t really take off with IE4 in 1997! The web was a different place back then, web design was a pretty new thing. Bandwidth was highly constrained at the time, so one could not imagine waiting for web fonts to load. Microsoft’s container format of choice is also EOT, which is a Microsoft proprietary technology. Although everybody slates it’s proprietary and closed nature, it was sort of a good idea. EOT provides domain locking, encryption, sub-setting and compression – all good things for convincing those behemoth font foundries to allow web embedding licenses.
Now is a better time than ever to move away from the standard web-safe fonts. Mainstream browsers have caught up with IE, over a decade later. Here is a short history lesson on the many techniques that Web Designers have been using to get beautiful type into their pages.
Just by configuring your site and server in the right way, you can get much faster and responsive load times out of your CMS. With mainstream open source CMS software, you are given the ability to add bolt-on functionality. It’s common for each of these add-ons to provide their own set of CSS definitions, images and JavaScript. This makes these add-ons easy to implement for non-technical users. If you aren’t careful though, you will end up with tens or even hundreds of CSS and JavaScript files. This has a performance penalty, which can affect your rankings in the SERPs.
The 4xx class of status code is intended for cases in which the client seems to have erred. Except when responding to a HEAD request, the server should include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition. These status codes are applicable to any request method. User agents should display any included entity to the user. These are typically the most common error codes encountered while online.
I’m happy to say that after buying my domain nearly four years ago, the site is now live. It’s the first design that I am generally pleased with. Planned updates include adding support for mobile browsers, and the right sidebar needs some work, and comments lists have been left slightly neglected. There will be some QA tests of available mobile plug-ins at some stage, though I hope to avoid the “Instant iOS” styling that the popular ones provide.
The design is under technical review, so if anybody notices any rendering issues feedback would be appreciated. The theme is built from the ground up, loosely based upon the skeleton theme Bianco. There’s some CSS3 sprinkled around; differences in older browsers are intentionally not addressed. Rendering bugs in IE6 won’t be fixed, lets not go back to the mosaic browser either 
.
OMG! Ubuntu
PK Davies