Vanilla 1.1.9 is a product of Lussumo. More Information: Documentation, Community Support.
The CSS Gallery List
1 to 22 of 22
The built-in functionality, combined with dozens of freely available add-on modules, will enable features such as: Content Management Systems...
<div id="sidebar-left" class="sidebar"> <div id="block-user-1" class="clear-block block block-user">
there are no less than eight server calls for separate style sheets on your own Drupal-powered website
It becomes time consuming and frustrating to sift through multiple style sheets to be able to target a single CSS property in the kind of mess that Drupal barfs onto the screen.
I know this reads like an absolute rant against Drupal, and it's not meant to be. I just want to make it absolutely clear that it is not a plug & play, easy to use system for your next web project.
I can't speak about version 6 as I have no experience with it. Do you deny that currently, the default markup that Drupal creates is bloated, redundant and not semantic? And, talk about inefficiency... Not including inline styles (inline styles?!) there are no less than eight server calls for separate style sheets on your own Drupal-powered website.
Not just the markup from the default Drupal installation, but the markup of all of the modules that we were using. We even hired not one, not two, but four separate Drupal consultants to help get things in order... to no avail. In the end, we went about one million dollars over budget, and the project never turned out; I'm not exaggerating - $1,000,000.
I'd LOVE to see some of your sample Drupal work to see how well you are controlling the markup and UI.
Drupal's code is bloated and redundant. Anyone considering its use should understand that there is a steep learning curve. It's not a great blogging system. If someone wants a blog they should use blogging software. Using Drupal for a blog is like killing a fly with a sledgehammer.
I'm not bragging. I want people to know why I feel the way I do about Drupal, and understand that open source does not necessarily mean free or cheap.
I still don't get it. You claim there was $1,000,000 spent on the project you were involved with, yet you still aren't aware that you can remove all the default CSS by changing 1 line of code and how to control the output markup. I find that truly astonishing and would argue that the source of the problems the team experienced had nothing to do with Drupal. Similarly, I would hazard it had nothing to do with open source.
As a tip, whenever a project goes pear shaped, it's a good idea to have some sort of postmortem to identify where and what went wrong. I mean, seriously. After spending, as you claim, $1,000,000million dollars, did it not cross anyone's mind to learn from the mistakes?
As an aside, that's partly what makes makes your flippant and inaccurate comments about Drupal so irritating and in the context of this forum (A skills share forum), very unhelpful and very misleading.
What's even more irritating is that the whole concept of open source and community development is that problems that people experience feed back into the community and the project improves as a result.
Does that (1 line of code trick) strip out all of the crufty CSS and markup from modules as well?
Just the CSS. Changing 1 line of code removes all the default CSS from the output but I have outlined below how to go deeper.
That means you're starting from the equivalent of a blank canvas from a CSS point of view and working with the default markup. Most prefer to go to level 2 and control the markup as well.
Option 1: Onscreen, by using the CSS/Designers helper module called CONTEMPLATE.MODULE, which makes it easy to rearrange fields, output different fields for teasers and body, remove the field title headers, output fields wrapped for use with tabs.module (part of JSTools), or anything you need. The nice thing about this module is that it allows you to customise RSS feeds for all content types, e.g, you might prefer to have different content/fields included in the RSS feed for gigs as opposed to news RSS feeds etc.
Option 2: Using a text editor like notepad, to edit template files, such as page.tpl.php, node.tpl.php, block.tpl.php, blog.tpl.php, forum.tpl.php, node-audio.tpl.php, comment.tpl.php and so on. Those tpl.php files look pretty much like a html file. Here's a representation of the default page.tpl.php template file on screen and a list of variables available to the template. It should be fairly intuitive from there how to remove/modify/add markup.
Level 1 and Level 2 will remove all the styles and allow you to control the markup Drupal spits out. However, there are situations where you may want to override how certain module content is output, to a very granular, field level, such as menu's, (un)ordered lists, bullets, messages, a login form or an audio player, for example. That's where a special template.php file comes in, where you can override completely how it's output. This level of "theming" in Drupal is more advanced and someone who knows php is useful to have around to help construct the theme overrides, if examples don't already exist in the Drupal handbook.
It's plausible that Drupal could just spit out the content, without any markup and styles, but, most designers don't want to learn a programming language, they just want to control how the output looks, which is why the architecture behind the Drupal theme (layout) framework is structured in such a way that a CSS/HTML designer can get to level 3, without having to learn a programming language or getting their hands dirty/pulling their hair out over code.
It does require a time investment getting to grips with the basics and the Drupal philosophy, but, that's a small price to pay for the functionality and scalability that you get in return.
I hope that is useful for others.
Drupal is a very robust, feature-rich platform, upon which experienced developers can create powerful websites.
It does require a time investment getting to grips with the basics and the Drupal philosophy