We recently launched another Drupal-powered website, and one minor requirement was a custom node-type that included a date field.

We needed to output a simple date... say, something like:

<code>&lt;div class="date"&gt;Saturday, August 18, 2007&lt;/div&gt;</code>

Turns out Drupal likes dates a bit fatter:

<code>&lt;div class="field field-type-datestamp field-field-date"&gt;
  &lt;div class="field-items"&gt;
    &lt;div class="field-item"&gt;
      &lt;span class="date-display-single"&gt; Saturday, August 18, 2007 &lt;/span&gt;
    &lt;/div&gt;
  &lt;/div&gt;
&lt;/div&gt;
</code>

Which led to yet another conversation between myself and Ken regarding Drupal, some of the disconnects between that CMS and our process, and their solutions.

Needless to say, there remains no one-size-fits-all solution. The features offered by Drupal, its vocal and active community, and its highly modular architecture make it an incredibly effective product for a wide range of implementations. On the other hand there are significant sacrifices -- for one, ridiculous HTML-bloat. Or, when it's worth it, there is the time lost trimming that same bloat.