Here are some interesting Joomla blog posts I found during week 13.
I found the post by Brian Teeman about templates for Joomla 1.6 particularly interesting. The sample templates for Joomla 1.5 are quite outdated, and they could be better laid out as to help new users of Joomla understand the CMS better.
Enjoy the read!
Written By Brian Teeman
There has been some discussion and comment on the development list recently about the design of sample templates for the upcoming Joomla 1.6 release.
Have you considered what they should look like, their functionality and most importantly their purpose?
Written by Angie Radtke
The Community is still waiting for the new release of Joomla 1.6.
Users are anxious to have Acl and the new category system. But some other things will be changed too. The backend has some changes, new modules have been added, and the HTML – Output changed.
I care about the output, the implementation of standards and the beez -template.
Alltogetherasawhole: If you're a developer and haven't contributed to an Open Source project, why not?
Written by Ewout Wierda
Jen Kramer tweeted this:
If you're a developer and haven't contributed to an Open Source project, why not? RTs appreciated. http://twtpoll.com/7bcf9g
I find the results of that poll very interesting, also for Joomla although I do not know how the outcome would be if the poll was specifically made for Joomla. Some of the reasons given are opportunities, while others remove some fears.
Every installable extension for Joomla comes with a manifest file (usually the name as the extension, and is an xml file). It contains basic information about the extension, such as who wrote it, the version, what kind of program it is, where to install, and what to install. There tag requirements are relaxed, but I want to propose that we start to reform our ways and make them a bit more standard, or simplified.
Written by Anthony Olsen
Over the last fortnight we have been furiously recreating our Zen Grid Joomla template framework, adding some great new features as well as completely re-engineering the template backend. Ive attached some screenshots of the template administrator and will post some more about the new features in the next day or so, but for today I wanted to highlight the changes to the admin UI.
While this article focuses on Joomla, this is also valid for all sorts of web applications - from Drupal to nearly all cache classes on phpclasses.org - they all use the same, inherently faulty approach.
Caching is used in all sorts of software and hardware to speed up access to data that has been previously retrieved or generated - such data is stored and subsequent requests for the same data are quickly served from stored copy.