Why you should use css/theming frameworks
follow up: http://drupal.org/sandbox/frankbaele/1545148
Doing Drupal front-end without going mad is easy. Let's be honest, every design and project is focused on the FrontPage and forgets that most of the theming work that is done isn't for the FrontPage at all. Drupal contains far more html/pages then you ever can imagine and the usage of RTE by the user doesn't make this easier. Forms, button, tables, grid layouts, ie fixes, ... are all necessities for a website but are easily overlooked and feel like a burden to implement.
But do we need to rewrite these forgotten parts on every project? Do we need the call from a customer too tell use their tables look bad on the website. nope. You can use frameworks as an insurance and ground layer, so that you can focus on the creative part of the theme development.
In this session I want to show, what frameworks and techniques you can use too make your life easier as a drupal front-ender.
Topics:
- What the F**K is a theming framework
- Why can frameworks make our life easier
- What are the pitfals when using frameworks
- How does frameworks translate too drupal and theming.
- Q&A