Planet Drupal

Subscribe to Planet Drupal feed
Drupal.org - aggregated feeds in category Planet Drupal
Updated: 26 min 32 sec ago

AGLOBALWAY: Responsive tools

Thu, 01/05/2014 - 19:14
Responsive design is hot, real hot. This isn’t new to anyone either, but when developing sometimes you need a little but of help or some assistance from a few modules, libraries or some browser extensions.  Some of the tools I come across quite often seem to be after thoughts, like I need something that I never expected. Say clients putting embed YouTube videos in the ckEditor and they want it responsive. I fixed that with FitVids (https://drupal.org/project/fitvids), which is a very handy, and lightweight jQuery module/library that supports all major video providers.    Always facing challenges making IE8+ websites, and also responsive for everyone else not behind a enterprise firewall or in the dark ages. Media queries help make website scale from 320px iPhone 4 all the way up to 27” 1080p monitor but in IE 8 and down media queries take over and now the website is a huge mobile phone.  No matter what screen size Respond.js (https://github.com/scottjehl/Respond )  to the rescue. Created by Scott Jehl and the Filament Group. Respond.js is a polyfill for min/max-width CSS3 Media Queries that brings your responsive website back in time to work in IE 6 + 8 and also shrinks to your iPhone 4. The trick to get this working in Drupal is to Go to /admin/config/development/performance. Enable Aggregate and compress CSS files. Respond.js only works on <link> tags; it will not work on @import stylesheets. Drupal 7 uses @import when CSS aggregation is disabled, but uses <link> when CSS aggregation is enabled. Duh!! Give it a try then go to your aunt’s house and fire up her 1999 Dell running XP.    The most used responsive tool would have to be responsive frameworks. There are a lot out there but not all work well with Drupal. Bootstrap (https://drupal.org/project/bootstrap ) is great and we’ve used it and tested it and become pretty comfortable with how it works and how we make it work for us. Plus they have a great support community!  Basic (https://drupal.org/project/basic ) is a SASS based grid system using bourbon neat (http://neat.bourbon.io/ ) which is great to use with all the mixins, functions and variables packed up in there.  As the Basic project page says “Basic is perfect if you want a simple, smart, and flexible theme starter.” Which it exactly is.     Responsive Images Community Group (http://responsiveimages.org/ )  ”We’re a group of developers working towards a client-side solution for delivering alternate image data based on device capabilities to prevent wasted bandwidth and optimize display for both screen and print.” Here are some smart guys/girls who are making the Internet a much better place.  They’re pushing picture element and the srcset to the W3C. Here’s more info about the picture element http://picture.responsiveimages.org/ and the srcset http://www.w3.org/html/wg/drafts/srcset/w3c-srcset/ . Before you know it our responsive websites will have responsive images and no more heavy jQuery plugins just good old-fashioned HTML5 and CSS3.    Tags: responsivedrupal planet
Categories: Elsewhere

Blink Reaction: Scaling your team: a practical guide to the value of values

Thu, 01/05/2014 - 18:25

With a culture of awesome people that enjoy their work, they can inspire each other to foster and share our values - to become a part of the fabric of how we communicate. So our advice to you as you grow your team - don’t ignore values - don’t create them in a vacuum - build them around your people; nurture them, and let the rest take care of itself.

Categories: Elsewhere

OhTheHugeManatee: Coder vs. Themer Ultimate Grudge Match Smackdown Fight to the Death

Thu, 01/05/2014 - 17:15

I’m really excited about a new session that I’ve been doing with my friend and colleague, Adam Juran aka scaragucc: the Coder vs Themer Ultimate Grudge Match Smackdown Fight to the Death! The basic premise: we both start with the same wireframe of a front page to build. But I’m only allowed to use the module layer, and Adam is only allowed to use the theme layer. It’s a really fun and entertaining way to play with the blurry lines between “coder” and “themer”. We get the audience pretty pumped up, which is impressive for a session that’s basically about watching other people code!

If you didn’t catch it at Drupal Dev Days in Szeged, or at Drupalcamp Frankfurt, you’re probably going to have to wait for Drupalcon Amsterdam to take part! But I do have a video of the session at Frankfurt, just to whet your appetite. :)

You can consider this a challenge: if any other themers out there want to challenge me to a coder vs themer style battle, I’ll be keynoting at Drupalcamp Helsinki in a few weeks. I’ll meet you there!

Categories: Elsewhere

Bluespark Labs: A Beautiful Friendship: How Bluespark and TripAdvisor put relationship best practices to work, and how you can, too.

Thu, 01/05/2014 - 11:08

If you’re a consulting company, as Bluespark is--our international team specializes in building beautiful web sites using the Drupal CMS, with an emphasis on powerful user experience and design--you know that excellent work is necessary but not sufficient to achieve a great (or even a good) relationship with your client.

Ultimately, no matter how hard you work, it’s the relationship that will decide whether the project is a success -- or, more to the point, whether your client believes it was a success.

You’re probably already an expert at listening not just to what clients say, but what they don’t say. You’re an accomplished reader of subtext. You work to build trust because if your client isn’t comfortable, you know it’s going to be a lot harder to sell them on your ideas.

You also know that a great relationship doesn’t happen just by chance, and it’s not just because “they don’t question our bills and they pay on time” (though of course that’s something any service company wants).

No, a great relationship is the result of specific acts. And as you might imagine, it’s a two-way street. When it happens, it’s worth looking at what you and your client have done to make it happen.

So we have some ideas for you, whether you’re the client or the vendor.

FOR VENDORS

Become an extension of your client’s team.

People like to talk about this, but it doesn’t happen much. Why? Because vendors have strong ideas about what’s best for their clients. They have experience not only in their client’s industry but most likely in others as well, and they’re more up to date on the best technologies to achieve client goals. They know more (they assume) and so they’re prone to pressing the point on their ideas rather than finding a way to meet clients where they are.

When TripAdvisor, the world’s largest travel site, approached Bluespark looking to improve their existing Wordpress solution for communications with business owners, we felt sure that a Drupal-based solution would best achieve their aims. This was after all a marketing platform with heavy content management requirements reaching a global audience (and they wanted to increase the number of languages supported from 7 to 20).

We weren’t just thinking Drupal because that’s our core platform; we truly believed from the start that it was the best way to go. Nevertheless, we engaged in a comprehensive evaluation with TripAdvisor, providing any information they asked for, and we were willing to talk about Drupal’s limitations in the context of their goals, not just its advantages.

After this process, we jointly agreed that moving to Drupal would provide us with a more flexible framework to meet current and future needs. This wasn’t just performing listening exercises to stroke the client. This was serious work, and in the process we got to know their team, their various concerns, and the way they liked to communicate.

Once we got started on defining the actual project, we were already a tight knit team. We’d earned their trust by being honest. We continued to offer them all the resources they needed.

Be flexible on who does what.

TripAdvisor’s technical team handles implementations concerning the existing TripAdvisor stack, and they also handled the visual design. We brought to the table our UX expertise and the actual Drupal development. We constantly looked for ways to fit what we were doing to their needs.

Be responsive.

This may seem to be a given, but it’s not. One of the most common questions we field when talking with prospective clients, especially ones that have been burned by bad vendor relationships in the past, is, “How fast is your response time?”

Bluespark is an international, distributed team. This presented some challenge in terms of coordinating the regular progress meetings (at least weekly, sometimes more), but it also gave us an advantage--quite simply, we covered more of the clock. Team members in Europe had a head start on the US business day, which came in handy where updates were concerned.

Make your process transparent.

During the project lifecycle, some clients want more of a hands-on role than others. TripAdvisor, with its talented technical and design teams, had the wherewithal and the desire to be deeply involved in everything we worked on together.

So every step of the way, we figured out together how to do the work. We made no assumptions. We  didn’t try to impose our process on them, but we were always willing to talk about how we work and what to expect.

With a project of this scale, even when every player on the team is extremely skilled, coordination and communication is what will ultimately determine success.

FOR CLIENTS

Demand the same level of organization from your own team that you expect from your vendor.

Let’s face it, TripAdvisor didn’t get to be the world’s largest travel site by hiring slackers. Their team is at the top of their game. They communicate expectations really well. They are always focused on keeping things on track. They are always, always prepared for meetings. There’s no drama and no one who has to be coddled.

In short, they demand the best--not just from us, but from themselves.

Know who the product owner is.

Do you know what can do the worst to a relationship--and a project? Lack of clarity with respect to who the ultimate decision maker is. Who gets to break the tie? Who bears final responsibility?

TripAdvisor always knows who this person is. After the TripAdvisor designers sign off on the visuals, we have someone who is clearly in charge to take the project from there. They are empowered to make decisions, or they are able to quickly come back to us with an answer.

Opt for a smaller core team.

TripAdvisor is a big company, and the work we’re doing with them reaches a global audience. But the total number of their people with whom we interact on a regular basis is three.

Aside from the designers, there are six or seven others with particular knowledge or expertise that will cycle in and out depending on current project needs.

On our end, it’s the same number--our Chief Technology Officer, Technical Director, and a Senior Developer. Other members of our team are brought in to handle specific pieces of work as needed.

So with two international companies (TripAdvisor being a bit bigger than we are, perhaps!) there is a core group of six people making the decisions and performing the work that reaches millions of people globally.

Conclusion

All this may come off as a love letter of sorts, and we’re OK with that. We love our work, and we love working with TripAdvisor, as well as all our other great clients (expect more love letters in the future).

Our hope is that you can put these ideas to work in your own client or vendor relationships.

Great relationships reinforce what’s best in you and support you in stretching your best even further. TripAdvisor has done that for us, and we like to think we’ve done the same for them.

Tags: Drupal PlanetBest PracticesProject Management
Categories: Elsewhere

Achieve Internet Blog: A Drupal Developers Guide to Responsive Web Design

Thu, 01/05/2014 - 05:36
The Achieve Internet Standard for RWD
Categories: Elsewhere

Pages