Another blogger blogging about Drupal websites.

Recent notes from the Drupalwoo archive.

• Mar 10, 2014
  Webforms in Drupal: passing information through the URL

  Capturing context about a visitor — where they came from, what they clicked — and feeding it into a webform through the URL.

• Feb 2014
  Using icons, buttons and other components in Drupal's Bootstrap theme

  Working through the Bootstrap component library inside a Drupal sub-theme, from glyphs to buttons to nav bars.

• Jan 22, 2014
  Filter your content using the Quicksand jQuery plugin

  Adding animated filtering to a Drupal-built gallery with the Quicksand jQuery plugin — no heavy module required.

• Dec 4, 2013
  Using Omega as a Drupal base theme

  Why Omega-4.x is a sensible starting point for a custom sub-theme, and how the layout grid fits together.

• Nov 13, 2013
  Contributing a patch back to Drupal: a small walkthrough

  From cloning the issue queue to posting a clean diff — what the first contribution actually feels like.

About Boriana →

Working on a Drupal site often means treating the back office as a product in its own right, where editors log in every day and judge the experience by how quickly they can publish, correct, or rearrange content. A well-tuned administration interface reduces the number of clicks between intention and result, turning routine tasks like creating a node, editing a view, or moderating pending comments into a calm rhythm rather than a chore. Theming, field configuration, and permission roles all shape that daily feel, and small touches — collapsible fieldsets, sensible tab order, predictable save buttons — accumulate into an interface that respects the editor's time and attention.</p>

Modules remain the most expressive surface of Drupal, and choosing among contrib options is as much about editorial workflow as about raw feature lists. A typical content team might rely on one module for richer text formatting, another for conditional field display, and a third for managing image styles or responsive display settings. Each addition introduces configuration screens, access considerations, and a maintenance footprint, so the goal is a lean set of well-understood tools rather than a crowded list of partially used capabilities. Field collections, entity references, and view modes can often replace a custom module, keeping the stack closer to core and easier to upgrade.</p>

Building blocks and views sit at the heart of most Drupal page compositions, turning structured content into readable layouts without requiring a developer for every rearrangement. A well-named block, scoped to the right region and visibility conditions, lets editors surface a contact form on the contact page, a subscribe call-to-action on blog listings, or a sidebar of recent posts only where it makes sense. Views, configured through the interface rather than code, give non-technical users a sense of authorship over the site, since they control which content appears, in what order, with what teaser length, and whether pagination, filters, or exposed sorts are available to readers.</p>

Front-end polish in a Drupal theme often lives in the small decisions: whether a read-more link matches the typography of the surrounding paragraph, how a form field communicates its required state, or how a long title is trimmed without breaking layout. JavaScript and jQuery tricks — toggling a section, collapsing a sidebar on small screens, swapping a class on scroll — are usually the difference between a theme that feels static and one that feels responsive to the visitor. CSS provides the visual language, but it is the careful attention to spacing, font choices, and hover states that makes navigation feel deliberate and content feel legible across devices and screen sizes.</p>

A Drupal project matures through iterative editor feedback, and the most useful improvements often come from watching real users rather than from feature roadmaps. A form field that confuses people becomes a help-text revision; a content type that is rarely used suggests a missing default value or a confusing label. Practices like limiting maxlength on long text fields, disabling comments where they add noise, and highlighting pending moderation items in the admin dashboard all reflect an attitude of care toward the people who keep the site alive. Over time, those small refinements define the character of the site more than any single module or visual flourish.</p>

Comments on the blog tend to go further than the contact form — and the discussion usually belongs to the next reader as much as to the author.

— A note on technical questions

Drupal, written down while building.

Drupalwoo collects practical development tips from real client and side-project work — themes, modules, admin workflows, and the jQuery plugins that fill in the gaps. The aim is a notebook a colleague could follow, not a tutorial series.

Posts cover Drupal administration across the Appearance, Structure, Content, People, and Modules sections, alongside accessibility, analytics, and SEO considerations that come up on most builds.

For general inquiries, the contact page is the right place. Technical questions are best left in the comments on the relevant post.

• Drupal
• Bootstrap
• Omega
• Webforms
• jQuery
• SEO
• Accessibility

Snapshots.