Kubair Shirazee, CEO ikonami technologies Ltd has finally succeeded to present a "Drupal Community in Pakistan - A silent majority" in a session in coming Drupalcon Munich 2012.

For more details please click here

• Web Experience Management

Monday 0% (0 votes) Tuesday 0% (0 votes) Wednesday 0% (0 votes) Total votes: 0

• Drupal 8 Initiatives

Greetings, y'all.

Been grappling with this issue. I want taxonomy description, which I have painstakingly added to each term, to appear on mouseover of the taxonomy term -- or alternatively, mouseover of an added post-term icon (such as "i" symbol).

I am quite surprised that this is not default behavior. It appears to be for "allowed values", but not when those values are pulled from taxonomy.

USE CASE:
Dev site (a wiki-type site) has many content types and many fields. Most of the fields are taxonomy term fields. Both the node form and the display node are inadequate, with respect to listed tags (tax terms), without taxonomy description for clarification. All are presented as radio/checkboxes.

Creating a bunch of custom template files seems kludgy, especially since that is something will like continue to increase over time. Hoping for an automated solution.

Have tried the Tipsy module, which provides the vocabulary description upon moveover of individual terms, when using the forms override option. And, have played around with that modules custom selector options. No luck.

A bit stumped at a good, efficient, scalable UI solution. I feel as though I am overlooking something obvious -- thinking too complex.

Ideas?

• Central Florida

Start:  2012-05-03 19:00 - 21:00 UTC Online meeting (eg. IRC meeting) Organizers:  JohnAlbin

Please join us for our next IRC meeting to discuss issues related to the Drupal 8 mobile initiative. The meeting will be held in #drupal-mobile on IRC at 19:00 UTC on Thursday, May 3. Using IRC is easy; Drupal.org provides a guide to using IRC.

Thursday, May 3:
San Francisco — 12pm
New York — 3pm
London — 8pm
Taipei — 3am (Friday)
Convert to your timezone

Agenda

As a reminder, the scope of the D8 Mobile Initiative includes:
- Mobile-friendly Drupal admin
- Responsive design issues
- Front-end performance
- Converting existing D8 themes to be responsive

The agenda will be driven by the questions and suggestions given by attendees.

Please post your proposed discussion topics in the comments.

• Drupal 8 Initiatives

Sign ups for the beta launch of Weblance is almost full. Beta users are limited to registered Drupal users. Beta users get free premium membership for life! Sign up now and don't miss the launch! We are currently hosting our blog on the http://weblance.com domain to allow for beta signups. Once we go love live we no longer offer free memberships. Sign up now on our blog before its too late!

• Drupal Jobs

Start:  2012-04-17 (All day) - 2012-04-18 (All day) UTC Related event (ie. not Drupal specific) Organizers:  weblance eric@druzzle.com

Sign ups for the beta launch of Weblance is almost full. Beta users are limited to registered Drupal users. Beta users get free premium membership for life! Sign up now and don't miss the launch! We are currently hosting our blog on the http://weblance.com domain to allow for beta signups. Once we go love live we no longer offer free memberships. Sign up now on our blog before its too late!

• Drupal Jobs

As part of the Drupal.org code sprint in Portland; Chris Ruppel, Joel Moore and myself have been discussing a new Bluecheese. A lean, tight, and admin friendly theme that lays out a framework for the future. One that would allow us to develop a mobile friendly, responsive design.

What we want An admin friendly UI

The current bluecheese theme is utilises the common 960.gs CSS framework. The layout is defined by inserting “grid-x” CSS classes into the html using template files and preprocess functions. It’s a maintainability nightmare and it’s a high level barrier to making changes. This constructs a technical barrier and spreads the customisation among many files. What we want is a way to handle this layout through a GUI.

A true responsive layout system

The major problem with adding non-semantic CSS classes in the markup hits when we attempt to make this solution responsive. How can the class “grid-8” be reinterpreted to fit into a grid system with fewer columns? We need a way to switch out different grid systems based on the size of the screen. These breakpoints should be based on the content and the design, not current devices. This is different for every project; the content and design is unique. Tools like gridpak.com or gridsetapp.com are emerging that allow us to define these responsive grid systems.

Changing the visual source order based on breakpoints

We need to respect content hierarchy. Simply un-floating everything and making them full width is the path to a shoddy mobile design. Important information appears in the sidebars of Drupal.org. We need to respect this and maintain the visibility of this content. One example would be to move some of the sidebar content above the main content while letting the rest fall below. Another example is moving the navigation from above the content to below. Try out an example by Jordan Moore (Webkit only)

Current thinking is that the CSS Flexbox specification or CSS Regions spec could be the path to this in the far future. Right now, support is a little light.

Fine control over asset loading

“Mobile friendly” sites that don’t consider page weight are missing the point. We need control over when and how we load assets based on feature detection. There is no generic use case we can apply to every site.

So... do we use a base theme?

There has been some heated discussion previously on whether we should use a base theme to provide us with this framework and if we do; which base theme gives us our required solution?

What has become obvious this week is that there is currently no existing framework that fulfills all of these design goals.

Omega

• Admin friendly UI — Yep
• True responsive layout system — Nope
• Breakpoint based visual source order — Nope
• Fine control over asset loading — Nope

AdaptiveTheme

• Admin friendly UI — Yep
• True responsive layout system — Yep
• Breakpoint based visual source order — Nope
• Fine control over asset loading — Nope

Zen

• Admin friendly UI — Yep
• True responsive layout system — Yep, with some SASS based control over the grid systems. It also touts Gridset App support?
• Breakpoint based visual source order — Partially yes, with Zen Grids, but see the comment below for fuller explanation
• Fine control over asset loading — Interesting SASS based control actually.

Arctica

• Admin friendly UI — Yep
• True responsive layout system — Yep, but device based?
• Breakpoint based visual source order — Nope
• Fine control over asset loading — A bit?

Please jump in and correct me with any of these tests, I haven’t used all these base themes recently so I might of missed some deeper features.

• Mobile User Experience & Design

As jacine with angelic patience has explained her concerns over the last few weeks and suffered through my blundering over trying to solve them, I arrived fairly prepared for the theme sprint and we have agreed on a lot more than we disagreed. Actually we didn't need to debate over anything at all! :)

1. On the caller side, we are going to go with something like

   $list1 = new Template('list', array('items' => array('listitem1', 'listitem2')));

   Of course, this can be made recursive:

   $list2 = new Template('list', array('items' => array('listitem1', $list1)));

   The Template class will have a __toString() method and that's how the recursive printing will work: automatically. This data structure will contain no caller-added HTML (ie do not add HTML to your modules) but it might contain user input HTML (for eg from the database). The templating engine needs to be responsible for making it secure.

2. Speaking of security, on the templating end, we have agreed on that the templating provides a default escaping which is adequate for HTML text and passable for HTML attributes (although you probably want to strip tags instead of escaping tags for attributes). Text which should be run over check_markup will be carried in another class which has a __toString method which does the filtering automatically upon printing. So templates will never be required to specify escaping in order to handle security. In some cases, templates will want to print a variable that contains HTML in an attribute value or <title> tag, and therefore strip tags from it, and they'll have an easy way to do so, but not doing so will simply result in some markup appearing where it shouldn't, not in a security vulnerability. Currently we do escaping in preprocess and we do it poorly as we try to have one variable which fits. This is somewhat impossible as you might want to print the same thing inside a <h1> check_markup'd, inside a <title> strip_tag'd.
3. Mostly because of security, we do not want templates to contain raw PHP. Basically the moment JohnAlbin stood up in Denver and said "We hand themers a loaded gun and tell them to hammer in a nail with it. Oh, and be careful" phptemplate was finally dead. Finally because the security team was thinking for many year on how to make PHPtemplate secure...
4. Now, among the non-PHP solutions we really like Twig. It's extensible, security-focused, fast and it's what Symfony uses and we seem to want to woo Symfony developers.
5. Coding commenced at http://drupal.org/sandbox/chx/1541306

• Theme development

I need to be able to modify (if possible) The Corporate Clean Theme. Specifically, the menu behavior for showing the menu flyout. the first-level (and I am guessing, subsequent levels) only opens-up when a page in that menu has the focus. I would like the menu to fly-open when I hover over another menu group. But again, this does not happen until I click on the first-level (main menu) item. Then I can hover over that main menu item to open it.

Does anyone know of a setting or a place in the code where I can get the menu to open just by hovering?

• Theme development

Start:  2012-04-12 19:00 - 21:00 UTC Online meeting (eg. IRC meeting) Organizers:  JohnAlbin

Please join us for our next IRC meeting to discuss issues related to the Drupal 8 mobile initiative. The meeting will be held in #drupal-mobile on IRC at 19:00 UTC on Thursday, April 12. Using IRC is easy; Drupal.org provides a guide to using IRC.

Thursday, April 12:
San Francisco — 12pm
New York — 3pm
London — 8pm
Taipei — 3am (Friday)
Convert to your timezone

Agenda

As a reminder, the scope of the D8 Mobile Initiative includes:
- Mobile-friendly Drupal admin
- Responsive design issues
- Front-end performance
- Converting existing D8 themes to be responsive

• No office hours this weekend unless someone volunteers to help run it
• The UX Team update at http://drupal.org/node/1513926 is awesome!
• The D8 Mobile Initiative sandbox and building issue-specific demo sites at http://getpantheon.com
• Need Bartik conversion plan
• Drupal Camp sprint planning!
• admin UX update

Please post your proposed discussion topics in the comments.

Open questions: What Drupal camps are you attending this summer? Do you want JohnAlbin to attend a virtual Mobile Initiative sprint (via IRC, Skype, etc.) at your camp?

• Drupal 8 Initiatives

Start:  2012-04-12 19:00 - 21:00 UTC Online meeting (eg. IRC meeting) Organizers:  JohnAlbin

Please join us for our next IRC meeting to discuss issues related to the Drupal 8 mobile initiative. The meeting will be held in #drupal-mobile on IRC at 19:00 UTC on Thursday, April 12. Using IRC is easy; Drupal.org provides a guide to using IRC.

Thursday, April 12:
San Francisco — 12pm
New York — 3pm
London — 8pm
Taipei — 3am (Friday)
Convert to your timezone

Agenda

As a reminder, the scope of the D8 Mobile Initiative includes:
- Mobile-friendly Drupal admin
- Responsive design issues
- Front-end performance
- Converting existing D8 themes to be responsive

• No office hours this weekend unless someone volunteers to help run it
• The UX Team update at http://drupal.org/node/1513926 is awesome!
• The D8 Mobile Initiative sandbox and building issue-specific demo sites at http://getpantheon.com
• Need Bartik conversion plan
• Drupal Camp sprint planning!
• admin UX update

Please post your proposed discussion topics in the comments.

Open questions: What Drupal camps are you attending this summer? Do you want JohnAlbin to attend a virtual Mobile Initiative sprint (via IRC, Skype, etc.) at your camp?

• Drupal 8 Initiatives

Pixelclever is looking for a dependable and competent backend Drupal developer for a part time position which would lead to full time once competence is established.

Necessary skill set:
Git, Php, Drupal Api, Jquery / Ajax, Views, and if you have some theming skills then that's icing on the cake.

Location:
This is a telecommute position, but you must be located in the Americas or Western Europe (translation: we do not hire from India). This position is for individuals only, no agencies.

Those wishing to apply should go to http://pixelclever.com/drupal-jobs and fill out the form completely. Please do not attempt to skip this step and contact us by other methods. Doing so will indicate that you don't read or follow instructions. The ability to follow instructions is absolutely crucial, so please don't disqualify yourself in the very beginning by trying to call us on the phone or skype.

• Drupal Jobs

I accept convert PSD,HTML to Drupal Theme

• Theme development

Start:  2012-03-29 19:00 - 21:00 UTC Online meeting (eg. IRC meeting) Organizers:  JohnAlbin

Please join us for our next IRC meeting to discuss issues related to the Drupal 8 mobile initiative. The meeting will be held in #drupal-mobile on IRC at 19:00 UTC on Thursday, March 29. Using IRC is easy; Drupal.org provides a guide to using IRC.

Thursday, March 29:
San Francisco — 12pm
New York — 3pm
London — 8pm
Taipei — 3am (Friday)
Convert to your timezone

Agenda

As a reminder, the scope of the D8 Mobile Initiative includes:
- Mobile-friendly Drupal admin
- Responsive design issues
- Front-end performance
- Converting existing D8 themes to be responsive

• progress made during Drupalcon sprint
• lessons learned so far
• next steps
• admin UX update

Please post your proposed discussion topics in the comments.

• Drupal 8 Initiatives

Some people believe that wrapper markup should be controlled via UI so that those configuring the site can choose the proper element to wrap blocks of content in, down to fields. This question is about Drupal core itself. Contrib has been and will continue to be able to solve this problem. See Display Suite, Views, Fences, etc.

I ask this because there has been a lot of discussion about improving the theme layer, and somehow this issue always comes up, and Drupalcon Denver as no exception. I can recall 3 separate sessions where it was asked if this was going into Drupal core, and in JohnAlbin's responsive techniques session he deferred it to me and the HTML5 Initiative and said he wouldn't be against it.

I think this would be better in contrib, personally, and I also think it’s out of the scope of the HTML5 Initiative, because it would have far reaching consequences, some good, some bad. I think it’s within the scope of the HTML5 Initiative to provide better default templates and that’s what we’ve been concentrating on (which BTW is no small task). Aside from the obvious bloat this would add to core, these are the reasons why I think it would be a bad idea in Drupal core:

• It wont work seamlessly with templates. The UI cannot always know if a template override is in place, which means if you decide to handle something via template, you end up with a broken UI. In some cases we’d also have to worry about others making markup changes where they weren’t wanted.
• It turns the job of a Drupal themer into that of a Site Builder who writes CSS. There are a lot of big changes coming to Drupal 8, including layouts like Panels and possibly a move to abandon PHP Template for something else like using Twig or Tokens in templates. If we go the route of allowing markup to be selected in the UI, we would have to use variables to print tags in templates, which make them more complicated to approach and lessen the HTML in them period, which is not a good thing.
• It has implications for contributed themes. Drupal already has a bad name for lack of nice looking themes, and this could make it worse. If all of this is editable via the UI, a theme has no real foundation to style CSS against. Classes will get you halfway there, but sometimes you need more specificity, and that means using the tag in the selector, except you wont really be able to rely on that.
• It expects the Site Builder to know HTML. They won’t have to actually code it, no, but they’ll need to understand the semantics of their content and the meaning of the tags. This also complicates the UI rather than simplifying it, which is problematic IMO.

But, what do you think?

• Drupal 8 Initiatives

We are looking for well rounded freelance Drupal developers who are willing to dedicate a 35-40 hours a week. This position is only available to individuals operating out of the the Americas (U.S. Canada and Latin America) and Europe. Agencies need not apply, individuals from countries outside the regions mentioned above need not apply.

Required Skill Sets:
The Drupal API (you need to be comfortable writing modules using forms api, theme api etc...)
PHP proficiency
Jquery and Ajax
Ubercart API
Ability to work from PSD files or PNG files and to slice those files accurately.
Standards compliant CSS and html
English spoken and written (Exceptions to this will only be made for French or Spanish speakers, but you will still need to be capable of reading and writing in English from time to time).
Ability to make accurate estimates and meet deadlines that you agree to. This element is crucial and will be tested early on.
Good communication practices (be available for honest updates on a daily basis through skype and email).
Familiarity with git.

Required information (to be included in your email):
Your skill sets and strength in each area rated between 1 and 10 (with 10 being complete mastery). Be honest.
Your skype name
Your preferred base theme (you should be comfortable with 960gs type themes such as Omega and Fusion)
Your current location
Your native language and Nationality
Your drupal.org user id
Links to 3 sites you have themed and or proof of modules you have contributed to the public
Your website
Your estimate for how long it would take you to theme this one page and how much you would charge (no inner pages, presume all views and content types are in place) http://www.templatemonster.com/demo/36285.html This is just an example to be used to judge your ability to assess time accurately. You will not be asked to theme this page.

Send responses to: patrick.pixelclever at gmail.com
Do NOT post to contact form or through any other email.

• Drupal Jobs

Let me start by stating that I came into drupal thinking template overrides and adding/removing divs, classes and regions within the template files was the most important thing to know in order to theme in drupal. I have since learned that most of the work can be done through configuring within the administrative interface as well as by utilizing the default div's and classes in your CSS.

Overriding a template should only be done when you need major, site-wide structural changes to a page's, node's, or block's template file such as adding or removing regions because the changes will apply to ALL use-cases of those files. Smaller, less structural - but still site wide - changes can be applied through theme functions and lastly, fine-tuned and case specific changes can be applied through theme hook suggestions. But that's just the tip of the iceberg for all the theming strategies available to you.

These kinds of distinctions are exactly what I am trying to clarify in this overview comparing the many, many different theming strategies used by Drupal themers and which are alluded to in the book “The Definitive Guide to Drupal 7,” by Melancon et al (which the page #’s reference) and to a lesser extent, “Beginning Drupal 7″ by Todd Tomlinson. I am told that as an open source system there are no hard and fast rules for using one theming strategy over another in any given circumstance so my goal is to organize everything as best as possible into an easy to understand context in order to compare and develop well-informed personal preferences and maybe even codify some best practices. That is, I am more interested in the when and why rather than the how.

I’m still learning Drupal and began compiling this information as a study guide rather than as a knowledgeable expert in the field, so if anyone out there can offer any suggestions or elaborate on the information here, particularly in the list of most common/practical examples offered for each technique, feel free to improve this wiki.

Modifying Contents, Structure, and Placement of Elements

The Basic page content type provides you with a text field for entering the title of the content item, and a body text area. The body field is flexible and can contain whatever the author feels like writing about.

• Write an entire book in the body field, including HTML markup (headings, tables, CSS, and so on).
• Insert pictures.
• Write a single sentence.

An article is identical to a basic page with the single exception that an article has an image upload feature and an additional field where the author can enter what are called tags. Tags are simply words that help classify, organize, and search for related content on your site.

Custom Content Types and Fields are good when you want to:

• Require that certain information is entered before the author submits the content item for publishing; for example the start date and time for an event, the address of the venue where the event is being held, and a link to the event on a Google map.
• Have the ability to perform calculations based on the information that is captured in a content item.
• Have the ability to sort content items by specific “fields.”
• Have the ability to “filter” or restrict which content items are displayed on a page based on a value in a field.
• Enforce the structure of how a piece of content is rendered on a page; for example, you may want to display information about a book and want the title to be followed by the author, followed by the ISBN, followed by the price, followed by the description of the book.

A block is a generic term that is applied to any self-contained piece of content, menu, or code. Standard blocks that come with Drupal include the login block, the search block, the “who’s online” block, the “who’s new” block, the latest blog postings block, and more. There are also blocks that come with contributed modules, such as blocks that share the latest weather report, your recent Twitter posts, or your current Facebook status. As a site administrator, you can construct your own custom blocks

Views provides an easy-to-use tool for selecting and displaying lists of content on your website. It is essentially a smart query builder that can build the proper query, execute it, and display the results. Examples of how you might use Views include:

• Displaying the most recent news articles posted to your website, sorted in descending order by the date of posting.
• Displaying a list of company locations as a table that is sortable by clicking on the titles for the location name, city, state, and country.
• Displaying a list of blog postings that is filterable by subject.
• Creating an RSS feed that lists the most recent content posted on your website.
• Displaying just about any kind of list that you can think of, created from the content that is stored on your website, as a list, table, or RSS feed.

Panels are useful when you want to divide a region into multiple “mini-regions” called panel panes. *

Alter Hooks (p 323), ex: dynamically add HTML for new small bit of content into a region, moving content from one region to another based on certain circumstances, and changing the contents of tabs based on certain circumstances. **

render(), hide(), and show() (p 327), selectively renders bits of content, such as fields, inside theme functions, templates and pre/process functions. Ex: render() is essentially an implementation of a render array **, hiding part or all of a render element to allow them to be placed outside of a div, hiding content based on certain circumstances, show() reverts a previously applied hide(), render() can be used multiple times. ***

*Views can be used with panel panes to define what content should be rendered, how many items should be included in the list, and how those items should be rendered. Using Taxonomy, content authors select the appropriate taxonomy term that is associated with each panel pane, and the content automatically appears in the right spot on the right page.

** Render Arrays are structered arrays that contain nested data and other information that drupal uses to render HTML (p 321) they are similar to theme hooks in that they use template and theme functions but they are modified using alter hooks (323).

***It’s best to do these operations in preprocess or process functions in order to keep your templates clean and more manageable (329).

STYLING

Define Stylesheets via the .info file (p 343), to be loaded for all pages.

drupal_add_css() to conditionally load stylesheets (p 344), ex: to dynamically print as an “inline” block of css code within the tag, stylesheets for single pages, specifying the weight of a file to control the order that it loads, conditional stylesheets that target specific browsers, loading external stylesheets, excluding a CSS file from the aggregation and compression process. *

hook_css_alter() to remove or override CSS files provided by modules and core (p 345).

*Enabling aggregation and compression for CSS files (admin/config/development/performance) on all live sites is highly recommended, as it will speed up page loads quite a bit (341).

Adding, Removing and Modifying Variables

Preprocess Functions (p 314) are normally used to add or tweak variables* available inside template files, for example to provide the $subject variable in block.tpl.php. Ex: dynamically adding CSS classes to variables (such as regions) as opposed to overriding a template, hiding links in certain situations, modifying the portion of content that is to be viewed in certain situations, and to create a custom variable to input a link for a type of user (318). **

Process Functions (p 314) ex: adding, removing, hiding, and modifying variables in certain circumstances “later in the processing cycle.” **

*use devel module’s dpm() function to determine all the available variables to work within each theme hook p.311

** These functions are run prior to the template being displayed, thereby allowing you to manipulate the variables for use in the templates themselves.

Modifying HTML Markup

Theme Hook Suggestions p.305 – progressively traverse drupal’s template/theme function/block specificity to target a specific template/theme function/block for one-off specific changes.

Theme Functions* p.301 – small, but site-wide, changes to form elements, fields, menu items, and adding/modifying content to blocks (p301) See: http://api.drupal.org/api/group/themeable/7

Template Overrides** p.293 – major site-wide changes to structure of a page, nodes, blocks, or to add/remove regions*** (291)

*These are theme specific, meaning if the site employs more than one theme it will not apply.

** The block.tpl.php file, for example, is used when a block is being rendered. Template files can be overridden by copying them into your own theme. It is also possible to make specific overrides with naming conventions, such as block–user.tpl.php.

*** Regions play a large part in defining the high-level structure of HTML markup. Typical regions include the header, footer, sidebars, and content, most of a site’s content is output inside these regions.

Note: This was originally a post on my blog: www.projectdesignportfolio.com

• Students of Drupal

We are needing a drupal theme expert, specifically with experience in cross-browser optimization. We have an immediate need to fix a website which has some serious problems in Internet Explorer.

We have been using a customized theme which has some poor coding. We would need it cleaned up and optimized in all major browsers, but specifically IE. Other minor enhancements may also be needed. We maintain and build many other sites, and so further work will be needed.

As we evaluate your performance, we would have you work on this project. After which, we would consider additional work, either full time or on a contract basis depending on your situation.

Please contact us for further details.

Email: jobs@flipjab.com

• Drupal Jobs

We are needing a drupal theme expert, specifically with experience in cross-browser optimization. We have an immediate need to fix a website which has some serious problems in Internet Explorer.

We have been using a customized theme which has some poor coding. We would need it cleaned up and optimized in all major browsers, but specifically IE. Other minor enhancements may also be needed. We maintain and build many other sites, and so further work will be needed.

As we evaluate your performance, we would have you work on this project. After which, we would consider additional work, either full time or on a contract basis depending on your situation.

Please contact us for further details.

Email: jobs@flipjab.com

• Drupal Jobs

There are a lot of Sessions and BOFs about Responsive Web Design happening during Drupalcon Denver 2012, here is some overview:

Sessions

Introduction into RWD Tuesday 10:45am-11:45am Beginner
http://denver2012.drupal.org/program/sessions/responsive-web-design-past...

More Intermediate Overview of RWD Tuesday 2:15pm-3:15pm Intermediate
http://denver2012.drupal.org/program/sessions/rethinking-responsive-buil...

Case Study of RWD Site Tuesday 5:00pm-6:00pm Intermediate
http://denver2012.drupal.org/program/sessions/big-websites-small-screens...

Design for RWD Wednesday 10:45am-11:45am Beginner
http://denver2012.drupal.org/program/sessions/ux-design-every-screen

RWD with Omgega Theme Thursday 10:45am-11:45am Intermediate
http://denver2012.drupal.org/program/sessions/creating-responsive-and-mo...

Projectmanagement with RWD Thursday 1:00pm-2:00pm Beginner
http://denver2012.drupal.org/program/sessions/responsive-project-process

BOFs

Workflow, Project Management, Estimating with RWD Tuesday 11:45am-1:00pm
http://denver2012.drupal.org/bof/responsive-design-workflow-project-mana...

RWD with Sass+Compass Thursday 1:00pm-2:00pm
http://denver2012.drupal.org/bof/responsive-theming-using-sasscompass

Creative Concept Design Discussion (What software do you use to manage all those device layouts?) Thursday 2:15pm-3:15pm
http://denver2012.drupal.org/bof/responsive-design-creative-concept-desi...

RWD Developers Experience Sharing Wednesday 3:45pm-4:45pm
http://denver2012.drupal.org/bof/responsive-web-design-experience-sharing

• Mobile