Packt Publishing has been flexible and focused on releasing quickly specialized books on various technologies. Especially for the web, they basically cover every hot topic so, if you are in the need of a book, have a look at their website.

Packt has gained wide acceptance by being a good promoter and supporter of successful open source projects. They donate back to the community and they cultivate the ground for more people to jump in.

JMatrix component released today and soon will be available on JED. It falls under the "Article Listing" category providing a Section/Category table view of your articles. I would be glad if you could give it a spin and let me know of any bugs or additional features you may like to see. You can download it here.

I think SQL and CSS have something in common, on the first look they appear to be dead easy to learn and then, as you move on, you realize that things can get tough. This is because both CSS and SQL trying to resemble ordinary language, they remain syntactically loose. This is good and bad. You can get to the same result by following different paths, the compiler will not be extremely strict with you but, when you try to build something, you may stare at you monitor for a really long time before you start writing a single word.

Now, as long as Joomla stores all its data in a MySQL database, you definitely need a fundamental knowledge of SQL to get to the next level. SQL is useful for looking behind the scenes, for generating reports or for changing data on the fly. Not to say that it is vital if you look forward to creating your own Joomla extensions. In this article I will give you some basic SQL SELECT examples attempting to build difficulty gradually. All examples should work if run against a standard Joomla database so, go ahead and test them.

KillerT provides a flexible way to style up your article titles and footers. In short terms you can define positions in your article headers and footers and then embed in these positions various elements.

Writing a Joomla plugin is a fairly straight forward process. In particular, after reading this article at the Joomla developer community I tried creating a few quick plugin examples of type "content" just to verify their operation. The plugin templates provided in the article are very simple and the whole process is really easy to follow. The motivation behind the attempt was to create smart article headers and footers as well as to embed custom tags in my articles that would be replaced upon display.

Joomla plugins cover various areas like user authentication, content display, content editors, web services and others. For a quick introduction on the various plugin types you can also read this article.

The high level picture behind plugins is this: Joomla incorporates a global dispatcher object that triggers events. Plugins are basically listeners that attach to these events. From our point of view, we just need to declare a class that inherits from the JPlugin class and define methods that will be executed upon event triggering automatically. The good news is the implementation of the dispatcher and the whole event triggering mechanism is (thanks Joomla) hidden to us... It boils down to defining a method, synonym to the triggering event.

If you‘ve been playing with Joomla templates, either trying to build your own or customize an existing one, you’ve most likely come across the following issue: You need to conditionally load stuff on your webpage. A few examples follow to give you the basic idea:

• You may fancy loading various style sheets conditionally throughout your entire website. This is either for spicing it up or for maintaining multiple layouts. For example, you could use a different style sheet to eliminate a side column or to change the background.
• You may need to change on the fly the position of a module. A good candidate for this is the login module which does not need to occupy much space for logged in users.
• Also, think about these hefty mootools files (or any other Javascript framework), do you need them to be loaded on the front page or is it better to load them later on, where most layout components are already cached in the browser?