Blog | Modules Unraveled

079 The Clean Markup Module with René Haché and M Parker - Modules Unraveled Podcast

Photo of René Haché and M Parker


  • What is the Clean Markup Module?

    • Allows a site administrator to configure the markup spit out by blocks and panels.
    • Submit feature requests and patches for other modules!
  • What does the module actually do?

    • Blocks:
      • On the block configuration page, there's a vertical tab with options for customizing the markup. e.g.:
        • Disable or set the HTML5 element to use as the block wrapper,
        • Enable or disable an inner div,
        • Add classes to the outer block element,
        • Add custom attributes (i.e. role="navigation")
        • Set the HTML5 element to wrap the title,
        • Toggle whether the block title is displayed visually,
        • Disable or set the HTML5 element to wrap the content.
    • Panels
      • Provides a pane style with similar markup options as the blocks.
      • Provides a region style with similar markup options as the blocks and panes.
        • Also lets you enable or disable separator divs between panes in the region.
      • Provides four clean panel layouts.
        • One Column Clean: one region and single wrapper.
        • One Column Reset: one region with no wrapper.
        • Six pack: six regions.
        • Myriad: five rows with four regions each that will output the absolute minimum markup. For example, a row with only one region will not output the row wrapper.
  • Where does it fit in with other modules?

    • Complements Display Suite
      • DS lets you customize node, user layouts.
    • Complements Fences.
      • Served as an inspiration to our module.
      • Really early on, our module was going to be a patch to Fences.
      • Fences deals exclusively with fields though.
    • Complements Mothership
      • Great HTML reset theme
      • Problem is that if you want to customize HTML element for a particular block, say, you have to write it's own theme files — on a site with lots of blocks, that gets unwieldy.
    • Semantic panels
      • Actually didn't know of this project originally.
      • Disclaimer: Have not used or worked with it.
      • Pretty similar to the panels part of our module.
      • Quick glance over the settings form suggests it provides fewer points of customization.
      • Have filed an issue to collaborate with them.
  • What's the future of the module?

    • Plan to support views.
      • Semantic views - it lets you customize the field and row wrappers, but doesn't support customizing view-header, view-content, view-footer regions and the view wrapper itself.

Use Cases

  • Is this best utilized during the initial development phase?
  • How easy is it to retrofit it into an existing site?

NodeSquirrel (Unofficial Sponsor)

I mentioned NodeSquirrel in this episode, and that I would share a coupon code for them. So, here it is, exclusively for listeners of the Modules Unraveled Podcast:
Use "StartToGrow" it's a 12-month free upgrade from the Start plan to the Grow plan. So, using it means that the Grow plan will cost $5/month for the first year instead of $10. (10 GB storage on up to 5 sites)

078 Drupal Fund Us with Jozef Toth - Modules Unraveled Podcast

Photo of Jozef Toth


  • What is Drupalfund and what’s the idea behind it?

    • is a crowdfunding platform for projects related to Drupal. Think of it as a Kickstarter for Drupal.

    • The problem which Drupalfund is trying to solve is that as we all know - Drupal development is backed by volunteers (individuals and companies) that donate their money or time to contribute to Drupal. However, most of the development (even core development) happens against the developer's personal free time or his paid hours. Because of this many issues, fixes and changes are pushed back and fixed when the developer can steal away some of his time. To be a little more specific I looked at top 25 most installed modules and their issue queues and got some interesting numbers:

    • These most installed or most popular modules have in average over 400 issues. It takes in average 279 days to fix & release the module. I know that the critical or security issues get fixed much faster but it still is a long time.

    • We started to look for a solution to this problem and so we've asked ourselves a question: What everything could be achieved, if we would provide an easy way how how the Drupal community could contribute financially to the Drupal development? Our community is huge. There are nearly 1M registered users on If only 1% of us would donate 1% of our salary each month, we would be able to rise over $5M/year And that is enough to hire over 65 developers to work on Drupal development full time.

    • With these numbers in your mind - think about how Drupal 8 development, porting modules to Drupal 8 could be accelerated. Think about that missing part of Drupal Commerce or Open Atrium, new features to Or think about the plans you could have to write a book on Drupal development, or release a training materials. Think about new products and services that could be born out of this. How much could we all as individuals and companies benefit if we together supported the development and not only depend on volunteering time.

    • So we built Drupalfund as our answer to this problem.

  • How does Drupalfund work

    • It works as all of the standard crowdfunding websites work:
      1. Submit a project idea
      2. set some rewards
      3. generate buzz around it
      4. get some valuable feedback from the community
      5. raise funds
      6. and deliver your project.
  • What kind of projects can it be used to raise money for?

    • Drupalfund can be used to support both coding and non-coding projects
      • Coding projects can be submitted to support existing and new modules, Drupal core initives, infrastructure, or installation profiles or products.
      • A good example of non-coding projects can be a book or curriculum, documentation, art & marketing projects or organising a sprint.
  • What plans do you have for Drupalfund

    • We would love to integrate or connect Drupalfund with
      • share user accounts
      • provide badges for activity that could be displayed on account page
      • create an easy way how to turn an project issue into Drupalfund project
      • provide widgets to embed on the module page
      • We would love to become the official platform for Drupal fundraising
  • Who is behind Drupalfund

    • Our team consists of two groups:
      • Mogdesign developed and is operating & managing the platform itself
      • we have a team of community advisors. These are very valuable and respected members of our Drupal community and we discuss very closely the future of Drupalfund with them. At this time they are Robert Douglass, Jeffrey McGuire (or Jam) and Kristof Van Tomme.
  • Why should anyone use Drupalfund?

    • I have 3 core answers to this
      • We believe that crowdfunding can be a new way to achieve greatness in Drupal development? Drupal has started in
      • Sustanability - as Drupal itself and our community grows and matures, we need to find different ways how we can multiply the amount of people that actively contributing to it. There are many people who would love to contribute to Drupal, but they are not coders, they would love, but simply don't know how they could help. Drupalfund aims to lower this barrier and provide an easy way for this to happen.
      • Giving back - we all got so much by using Drupal on our sites or selling it to our clients and I personally believe that it is time to give back from what we have gained. It does not matter if you are a large company or an individual, Drupalfund wants to help anyone to give back to Drupal.
  • Why not just use Kickstarter?

  • What should we do if we want to start?

    • If you have an interesting idea go and submit a project. Or if you know about anyone who would benefit from using Drupalfund, point him our way. Go to, get in touch with us, we would love to help you setting up the project.
    • First 3 submitted projects will get a $100 credit each:)

    • Also if you come to Drupalcon Prague, we will have a BoF session on Wednesday @1pm in the Club B · Windows Azure room where we will be to discuss Drupalfund, answer any questions or help with setting up projects. Looking forward to meet you.

077 Bugherd Bug Tracker with Alan Downie, Matt Milosavljevic and Dave Hall - Modules Unraveled Podcast

Photo of Matt Milosavljevic


  • What is Bugherd?
    • bugherd is a bug tracker for web designers and developers. it embeds in the website you’re building and allows technical and nontechnical people to collaborate on the website as it’s being built. With a few clicks it allows clients or stakeholders to submit feedback or bug reports. It automatically collects a heap of data about the page, the content and even data about the users system, browser etc making it easier to replicate and resolve issues
  • Why do Drupal folks need to know about BugHerd?
    • freelancers and agencies spend time and money building websites for customers and until now have had to rely on screenshots and meetings to get input from their clients. By giving the clients the ability to give feedback directly on the site, it smooths the entire build process.
  • There’s a Bugherd module for Drupal. What was/is your involvement with that?
    • Dave Hall, a drupal contributor, was using BugHerd on a project with a client and created the drupal module to help him work with clients more effectively
  • What does the “admin” interface look like?

Drupal Module

  • the module provides basic integration at the moment, but in the future it will be able to automatically capture a heap of metadata about the user logging the issue, their id, email address or any other meta data you might like to collect.

076 Omega 4.x with Sebastian Siemssen and Matt Smith - Modules Unraveled Podcast

Photo of Matt Smith

Omega 4.x

  • Omega 3 vs. Omega 4
    • No Layout Builder UI
    • No predefined breakpoints
    • No dependency on Omega Tools or need for Delta.
  • Sass, Compass & SMACSS
  • How does this work with Panels?
  • Will this be the route going forward for D8?
  • BEM class naming Syntax
  • Core CSS Cleanup
    • Easier to override
    • Split up stylesheets
  • Omega Layouts
  • Development tools (Guard / Grunt, LiveReload, etc.)
  • Manage assets (exclude CSS/JS, move JS to footer)
  • Manage browser compatibility (Chrome Frame, conditional classes, etc.)
  • Split up preprocess, process and theme functions
  • Drush Integration
    • drush help --filter="omega"
  • Ohm

Use Cases

  • What prompted the major overhaul?
    • This reminds me of the conversation going on around D8 right now.
    • How long can people keep using 3.x?
  • What does this mean for site-builders?
  • What does it mean for themers?
  • How does Omega 4.x compare to other base themes like AdaptiveTheme and Aurora?
  • When should we expect a stable release?

Questions from Twitter

  • Dirk Bazuin (@dbazuin): #MUP076 will there be templates made with
  • Kendall Totten (@KendallTotten): Is there a timeline for when we can expect all the Panels integration to be wrapped up in Omega 4.x? It sounds fantastic :) #MUP076

075 BadCamp with Jen Lampton and Meghan Sweet - Modules Unraveled Podcast

Photo of Jen Lampton and Meghan Sweet


  • What is badcamp?
    • 4 days of training, summits, sprints, sessions, BoFs, Jobs, Networking and more!
  • When is it?
    • October 24 - 27 / Berkeley, California
  • What makes Badcamp special?
    • The peeps (community is awesome)
    • Trainings (are free)
    • Summits (make a large event feel cozy)
    • Networking
    • Free!
  • What to expect
    • Fun!
  • Locations this year
    • What’s new
      • New Party locations (The Marsh / International House)
      • new Summit Locations (City Club / Anna Head Alumnae hall)
    • What’s old
      • Registration in the same place
      • Sessions in the same place
      • Sponsor Fair in the same place
      • Free cappuccino, vegan doughnuts, etc, in the same place
  • Summits
  • Trainings
    • What’s the deal with trainings?
      • beg -> advanced
      • free!
      • All-day Thurs and Friday
  • Sprints
    • Extended Sprints (if you want them?)
    • Core developer sprint (Sunday, Sunday SUNDAY)
  • Parties
    • Trivia Night / Game night
    • Rooftop Bubble Bar!
  • How to get involved:
    • Register
    • Submit a session (Until sept 1)
    • Speak at a summit
    • Sponsor
    • Volunteer

073 Prague Site Building Track - Modules Unraveled Podcast

Track (Ivo)

  • What is the theme of the track?
    Difficult question, since we are actually trying to cover a really broad spectrum of topics for all
    kinds of audiences. We are still in the process of deciding on the final schedule, but there will be
    sessions on distributions (bojan -- commerce without borders), site building changes coming
    with D8 (kristof), hopefully we'll have a great case study session and so on. We do try to align
    these sessions with DrupalCon's “One to Many”-theme
  • What’s the spread of D7 vs. D8 session proposals that have come in?
    Traditionally, Site Building relies heavily on contrib, which is a bit behind the curve when it
    comes to D8 adoption, so most of the session proposals are still focused on Drupal 7. We do
    have a featured session focussing on D8


  • Bojan what’s the name of your session, and what will you be talking about?
    Commerce without borders
    I'm going to be talking about building an ecommerce solution for the global market, and all the
    problems that go with it.
    You need to deal with different languages, currencies, payment gateways, taxes and tax rates.
    You also need to think about invoices, discounts, business rules, country laws and many other
    It's funny how all this represents the hardest use case you can have, but also one of the most
    common ones,
    at least if you're in Europe.
    I will be detailing some of the solutions we’ve recently developed to make these kinds of
    problems easier to handler, and how it all fits together on top of Kickstart..
  • Kristof what is the name of your session, and what will you be talking about?
    Drupal 8 for site builders.
    So site-building is a really broad topic of course. What I’m not going to do is build a site together,
    because that’s just boring. I’m going to talk about all the major contrib modules that have moved
    into core, but also subtle small modules. And also big new features that make site building life
    much easier. The conclusion of the session will hopefully be that Ivo should not look out for
    Drupal 8 site building a lot, because Drupal 8 is going to solve everything, or at least a lot.

072 Prague Coding and Development Track - Modules Unraveled Podcast


  • What is the theme of the track?

I tried to make the theme consistent with the overall DrupalCon Prague theme of “One to many”.
Leveraging new paradigms in Drupal 8: improving your projects and workflows
Drupal as an application platform
Integrating Drupal’s API with other systems and libraries

So we really want to present Drupal as a unifying platform, that can consolidate many technologies.

Part of that is what Alex is going to talk about in his featured session - removing some of the Drupalisms that we have all gotten used to in favour of incorporating best-of-breed open source components from outside the community. I think Symfony’s components are the most obvious example there, but there are a lot of other components too (like Guzzle, Doctrine).

Another element is the general move to OO, PSR-0, and the adoption of modern design patterns which bring us up to date with other major PHP projects. The plumbing is there now to integrate with other frameworks - and we’re doing that.

I’ve kind of been talking about low level code integrations, But theres also a lot that can and has been achieved with Drupal as it is today, by incorporating integrations with outside systems via web services, or supplying services to other systems. So I would like some of our presentations to cover how Drupal integrates, and maybe in ways you hopefully haven’t thought of.


  • What is the name of your session, and what is it going to be about?

071 DrupalCon Prague DevOps Track - Modules Unraveled Podcast


  • Jochen, what is DevOps? and what is your vision for the track at DrupalCon Prague?
    • The DevOps track covers all aspects of bringing Drupal websites into operation -- and making sure that they meet the demand of the business. This only works when development and operations work hand in hand -- hence, DevOps. In DevOps, the core characteristics can be summed up as “CAMS”: Culture, Automating, Measuring, Sharing. Culture means that people and process go first. In Automation, we use tools to get our processes working end-to-end. If we want to improve, we need to measure. And with the sharing of our insight and experience, we’re back to culture again. DrupalCon is a great place to talk about DevOps, and especially DrupalCon Prague with its “One to many” topic. Most of us start our infrastructure with one server and scale from there. IT teams as well grow from a single developer to a group of people. I’m very excited to have some great speakers on my track!


  • Jon, What’s the title of your session, and what is it going to be about?
    I’m going to be talking about my experiences bringing “start-up-like” DevOps thinking around deploying Linux servers and Drupal to a large, established organisation. It’ll be a bit of a war story in places, because it certainly wasn’t plain sailing.