This is a special interest group dedicated to improving and expanding the Drupal theme system including theme functions and templates, CSS, markup, and how contrib modules add in their functions, CSS, and markup.
for example, we'll take stock of the location and number of CSS files and discuss if the architecture can be improved through emerging frameworks like Object Oriented CSS.
We will consider the questions "What do themers need from Core in terms of CSS? Module developers? SEO specialists?" and "What's new in CSS? What does Drupal support? What's the roadmap for CSS support?"
Themable function guidelines and documentation
We have a great theme system, but we don't always make full and proper use of it from the developer side and the themer side is underdocumented. I propose we improve this situation by writing guidelines:
- When to use themable functions; building on How to write themable modules.
- What PHP is allowed in a themable function and what is not. Somewhere between
print $fooanddb_query()there is a hard line to be drawn. - Notes on accessibility
- What HTML is best, including
designing a new themeing system, for railfrog, reason behind brickslate.
I am currently involved in a new CMS on Rails, called Rail Frog. This CMS aims to become a so called "engine" for Ruby on Rails, meaning, that you use it as a start for your project.
This post is here, to introduce the conceptual engine, called brickslate, and to explain the reasoning behind it, by explaining the architecture of rail frog and its theme engines.
For Railfrog, we needed a theme system that is clean, well integrated, flexible and all that. Im developing this, a pdf is found on my site, and the project pages are in the Railfrog Wiki.
Read more