Bearded

Zoobean Is Hiring a Lead Developer

Tue, 14 May 2013 15:01:36 -0400

Zoobean is looking for a full-stack web developer!

Zoobean (zoobean.com) is a Ruby on Rails web application for children’s books built by Bearded (bearded.com).

Zoobean makes it easy to find remarkable children’s educational products, starting with books, that have been recommended and curated by parents. Books on Zoobean are catalogued by recommended age, relevant topics, characters’ backgrounds, and other tags that matter to families. The company offers a subscription service, direct sales of featured books, and affiliate sales of books in its catalog.

Zoobean has already secured $500,000 in seed investment, led by Kapor Capital (Mitch Kapor is the founder Lotus Development Corporation, designed Lotus 1-2-3, and is the founding chair of the Mozilla Foundation.)

Our ideal candidate has a strong working knowledge of:

Ruby
Source control software (preferably Git)
Relational databases (we use Postgres, but any will do)
MVC architecture
Object-oriented programming
JavaScript
CSS and CSS precompilers

Though you may not have worked with everything we’re using on Zoobean, experience with the following technologies and techniques is preferred:

Rails
SASS
Compass
Breakpoint
jQuery
Heroku
Responsive web design techniques

If chosen, Zoobean’s new developer will spend 3-5 weeks working on-site at Bearded in Pittsburgh. Bearded’s developers will work closely with you to help you acclimate to the application, it’s technologies, and approach. Once you know your way around, you’ll become Zoobean’s lead developer, communicating and collaborating with Bearded when helpful.

The salary for this position is competitive, and the opportunities for honing your skills and employing new web technologies are great.

Not only that, but you get to help grow this start-up with a heart and give families remarkable resources that empower their children to imagine and achieve anything!

Interested applicants can send the following to felix@zoobean.com :

Online résumé
GitHub profile with examples of relevant work
Stack Overflow profile

Thanks for your interest, we’ll see you on the internets!

Bearded & Zoobean

Zoobean Is Live!

Tue, 14 May 2013 12:59:00 -0400

by Matt Griffin

OMG, y’all, Zoobean is live!

We’ve been working on this project for some time here at Bearded, and man are we psyched to finally show it off. Zoobean is a unique new site for children’s books. It has a special filter system that lets you find the right books for children based on things like age, topics (like bullying or holidays), or character background (like gender or ethnicity). All the books are hand-selected by parents, as well as reviewed and rated by users.

Zoobean also selects special books each month that users can subscribe to receive monthly in the mail, or buy as one-off purchases.

There are a ton of neat features on this site – so much that I can’t get into them all here – and of course, the whole thing is responsive. You should probably just go check it out.

Not only are they helping parents and friends find books that kids can relate to, but Zoobean also contributes a portion of its proceeds to a selected youth literacy charity each month. So there’s plenty to feel good about with these guys.

I can’t thank all the members of the Bearded team enough for their hard work on this site. I can’t imagine a more creative and talented bunch of folks than the ones who worked on this project. My hat goes off to Brett Bender, Matt Braun, Patrick Fulton, and Mark Frey.

Our clients and the owners of Zoobean, Felix and Jordan, were tireless in their support of and commitment to the project. They’ve been integral parts of the team, and I deeply appreciate that they brought this super fun project to our door.

But enough about us. Go check out some kids books!

From the Trenches: Breakpoint - easy media queries in Sass & Compass

Mon, 06 May 2013 15:08:25 -0400

by Patrick Fulton

tl;dr: We now use nesting and a Compass extension to manage our media queries.

Several months ago, we started experimenting with an excellent Compass extension called Breakpoint. Breakpoint lets you create variables for your most commonly used media queries, and then it handles all of the heavy lifting for you.

Previously, we had been managing our media queries in Compass by splitting them out into partials: one for the base / mobile-first styles, one for “small” screens, one for “medium” screens, and so on. Then, in our main compiled file, we’d “@import” those files inside of their respective media queries. You can see an example of this approach here.

Doing this isn’t wrong, and it’s not even a bad idea, but for projects that had entered their “support” phase, going back and managing the styles across those media query partials isn’t exactly my idea of fun. Not only do you lose context, but this approach is also prone to unnecessary code duplication and specificity issues.

Enter Sass 3.2, which lets you do all kinds of awesome things with media queries, including letting you nest them and use variables in them. Awesome, indeed.

Back to Breakpoint

Nesting media queries in Compass is already a huge win, but Breakpoint gives you a more managable workflow by letting you set up the variables that you’ll use for your media queries. It can also turn your pixel values into ems, if that’s how you like to roll (and you do, right?).

Breakpoint also provides an easy way to generate CSS for browsers that don’t support media queries with its No Query Fallbacks feature.

That’s a .wrap

If you’re a Compass user, and you’re developing responsive sites, you definitely need to try Breakpoint. If the benefits aren’t immediately apparent to you, they will be when you go back to that project six or eight months down the road.

If you like, you can also check out the Breakpoint presentation that I recently gave at the SassyPgh meetup.

— Special thanks to our pal Ben Callahan at Sparkbox for planting the idea in our heads that you can split IE-specific styles out into their own files. This ultimately led us to discovering Breakpoint.

Meet the Neighbors: Bearded | The Beauty Shoppe

Tue, 30 Apr 2013 15:25:42 -0400

Meet the Neighbors: Bearded | The Beauty Shoppe:

You can watch a nifty little video of Matt Griffin talking about Bearded’s approach to responsive web design process and working with clients on a website we built (whoa, meta!). It’s short, and Matt’s hair will never look that immaculate again – check it out!

RWD Summit

Mon, 15 Apr 2013 10:01:10 -0400

by Matt Griffin

I’m going to to be speaking about responsive web design and client process at RWD Summit this week. RWD Summit is an online web conference, so you can do experience the whole thing right from your desk!

The conference chock full of great speakers like Dave Olsen, Trent Walton, Dan Mall, Sara Wachter Boettcher, Tim Brown, Ben Callahan, Jen Simmons, Dave Rupert, and more!

You can still sign up, and if you use the code 20MATT, you’ll get 20% off on your tickets.

See you on the internets,

–MG

Lou Ferrigno Gives His Body 110%, Should You?

Mon, 18 Mar 2013 11:00:00 -0400

by Matt Griffin

The other day, Patrick and I were discussing approaches to setting the base font size of our websites. When we use relative measurements like ems, you see, that relative measure has to come from somewhere. Historically we’d do that by setting the font-size of the element. There have been several approaches over the years, and perhaps most recently the Filament Group made a compelling argument to set it at 100%. The points they make are great, and it’s an approach we’ve been using on our sites for a while.

But here’s the rub: 100% (using default browser settings, that translates to 16px) is not a good default font size a lot of the time. Paragraphs are often too big at that size, which mean they need to be set to a lower size, like 0.875em (14px). Once the paragraphs are that size, you generally want other elements to line up, so then you have to set your unordered and ordered lists. And the headings need to fall in line at related sizes, too.

So, OK, not so bad. Your type is all worked out, right? Well sure, until someone uses a table or a definition list. Then we have a problem again. And this is exactly the situation that bit us just after launching the new site for the Pittsburgh Glass Center. It was an edge case kind of thing, and I doubt anyone besides myself noticed before I fixed it, but – it’s the kind of thing that makes feel like our approach is too brittle. It requires too much attention; it’s not an extensible solution.

What I really wanted to do was to start with body { font-size: 87.5%; }, then add some media queries to scale the font size up and down, as necessary, for all elements. Why media queries? Well, something the web world knows from graphic design is the idea of a readable measure. Basically, as line length increases, font size should also increase to limit the number of characters per line and aid in readability. (Trent Walton describes the responsive web approach quite well on his blog.)

This approach left us with something like this:

body { font-size: 87.5%; @media (min-width: 55em) { font-size: 100%; } @media (min-width: 70em) { font-size: 110%; } }

This has the effect of scaling the base font of everything from 87.5%, to 100%, to 110%. But starting the base body size at less than 100% felt a little weird to me, for all the reasons in the Filament Group post.

Now this was about the point where I decided (as I often do with issues like this) to bounce the idea off Ben Callahan. Ben was pretty much in the same boat as us. He’d been following similar practices, and also saw the brittleness as an issue. But he had a different perspective on font sizing to contribute. Ben took an issue with our assumption that font size and container width have a linear relationship; that as the container width goes up, so must font size. His feeling was that 100% was actually a great place to start on small screens, simply because touch targets need to be larger, and you’re often holding the little screens further from your face. Small browser widths, he argued, often mean small devices, which users interact with differently than, say, a low width browser window on a desktop computer. Small type on a small screen may have a short line length, sure – but it’s just too darn tiny to read.

Not only did all of that make sense, but Ben’s approach also got us back to a default font-size of 100% – which feels a lot less heavy-handed and hacky.

After factoring in Ben’s idea, we ended up with the following:

body { font-size: 100%; // This actually happens in the reset stylesheet. @media (min-width: 40em) and (max-width: 55em) { font-size: 87.5%; } // In between these two media queries we go back to 100%. @media (min-width: 70em) { font-size: 110%; } }

This final approach has the effect of scaling the base font of everything from 100%, to 87.5%, back to 100%, and finally to 110%.

We’re feeling like this covers all the main bases for us, and it’s the approach we’re including in our front-end starter kit. Until, of course, we think of something even better.

Follow-Up

Trent Walton brought up some good points on Twitter, where he wondered if we should be making our type smaller at all. His point being that right now we tend to associate touch screen interactions with smaller screen sizes, but that this is not a very future friendly mindset, considering where things are going.

Perhaps we’re seeing my own aesthetic preference for slightly smaller type get the better of my desire for extensible multi-device UX, here, eh? Definitely something to keep in mind as we test our designs on devices. Regardless, it’s probably best to assume that any size at all may very well end up on a touch screen, with all the UI needs that entails.

Pittsburgh Glass Center

Tue, 26 Feb 2013 09:22:00 -0500

by Matt Griffin

We just launched the new Pittsburgh Glass Center website, and boy are we excited! We began the planning and research for the project back in June, and now all those ideas and months tapping away at our keyboards have coalesced into a live, functioning piece of the multi-device web. It never ceases to amaze me.

The new Glass Center site has loads of great functionality (which you can read more about on the Bearded site), and everything is built responsively, with a fluid layout. It was designed “in the browser” using CSS and HTML comps – and to us the resulting designs and approach really show the benefits of that process.

This site happened only because of the heroic efforts of all involved. This project also saw our client contacts, Sam and Paige, really become part of the team – something we love to see happen on a project. They’ve been smart, studious, thoughtful, and empathetic – truly ideal clients.

On the Bearded side, this would not have been possible without the labors of Brett Bender, Matt Braun, Mark Frey, Lauren Fries, Patrick Fulton, and Michael Hellein. I’m immensely proud of this project, and have the intelligence, patience, and skill of all these good folks to thank for it. Sam from PGC summed it up pretty well on Twitter this weekend. And don’t I know it.

–MG

Bearded Work at Indiana University

Tue, 19 Feb 2013 16:47:11 -0500

Recently we were fortunate enough to have a bunch of Bearded work on display at the Grunwald Gallery at Indiana University in Bloomington, Indiana.

On display were our responsive websites for the Children’s Museum of Pittsburgh, American Association for Homecare, and Bearded – as well as letterpress posters for Wood Type Revival.

Check out some of the lovely images, below.

WTR Cosmopolitan Is Here!

Sat, 02 Feb 2013 12:36:55 -0500

woodtyperevival:

Our latest WTR font, Cosmopolitan, is here! Go get it now at the Wood Type Revival store!

Not only that, but Cosmopolitan is also available on Typekit for all your web font needs!

Cosmopolitan is a script face that knows how to hold its own. Big and bold, but not afraid of a flourish, it’s the typographic equivalent of getting old gramps to whittle you a doily with his penknife. And it’s everything you hoped it would be.

Cosmopolitan slides designed by Regina Casaleggio.

Matt Griffin at Artifact Conference

Fri, 25 Jan 2013 15:45:27 -0500

Matt Griffin at Artifact Conference:

Bearded’s Matt Griffin will be speaking at Artifact Conference in May!

ARTIFACT is a two-day, single-track conference for DESIGNERS adapting to the challenge of designing for a MULTI-DEVICE world.

Slide Rules

Fri, 25 Jan 2013 11:30:34 -0500

by Matt Griffin

I hereby declare this week The Week of The Slider! After seeing Erik Runyon’s very helpful (if not surprising) post about slider interaction statistics and Brad Frost’s fervently thoughtful post about the feature we love to hate, I’ve decided to dredge up my almost-finished-never-published post about same said feature. However, rather than discussing user interaction and statistics, I’m going to throw my thoughts about the Slider Information Design Conundrum into the ring.

First, I will come clean. We’ve implemented our share of homepage sliders here at Bearded. It’s a common homepage convention. And there are times when this strikes me as a reasonable thing to do. For instance, a product with multiple key features of equal weight. Like the iPhone. But lately – at least for me – it’s started to feel like we’re getting a little habitual with our sliders.

In some ways, it’s an easy fix to a complicated problem. On the client side, it can be hard to negotiate a perfect hierarchy for a website’s information. And the more complicated and diverse a site’s content is (most sites don’t have the laser focus of a single product) the harder the task becomes.

Then there are internal opinions and politics. Different departments or individuals will likely think their content is more important, and may push to get it promoted on the site. Personal relationships may factor in – no one wants to let down their co-workers, after all. And let’s face it, it’s easier to just promote four things to a slideshow and largely defer potentially difficult decision-making. Why is that so bad? I didn’t think it was, until I began to feel an itch in the information design part of my brain; a feeling that often signals the arrival of a problem.

As an example, let’s consider a desktop slider layout like the diagram below:

The upper area is a slider that’s packed with three content chunks: 1a, 1b, and 1c. Below the slider are two other pieces of content (marked 2 and 3). The relative importance of these items is assigned by:

Placement: The slider is above and more prominent, while the two featured items are below and less prominent
Size: The slider is full width and more prominent, while the four featured items are partial width and less prominent.

Because we’re talking about the slider as a whole unit, this is pretty clear cut. But now let’s consider the temporal aspect of the individual slider items. Only one is ever on the screen at a time – at which point it has hierarchical dominance on the page. Meanwhile the rest of the slider items are hidden completely, and thus have zero prominence on the page. The items take turns being visible every few seconds, and their place in the information hierarchy shifts accordingly. So what our design is saying about slider content is:

When a slider item is active, it’s more important than everything else on the page.
When a slider item is inactive, it’s completely unimportant.

The problem is that I can’t think of a content scenario when this should be the case. The importance of these items is either all or none, depending on when someone looks at the screen, when they decide to scroll, etc. As an information designer, I find this unsettling.

I’m not sure that this means the homepage slider approach is simply bad. But when making design decisions like this, we should consider how it affects the information hierarchy of the page, and ask ourselves (and our clients) if it is appropriate to the content at hand.

It’s also important to check that we’re not making design decisions that enable our clients to defer making hard content hierarchy choices. If it’s a “let’s get more stuff above the fold” issue, then maybe consider that “below the fold” (wherever that fold may be*) is better than not present entirely.

Hiding content like this adds a fair amount of chance into our information hierarchy. Will users see the first slide? Probably. Will they see the second one? Maybe. The third? Who knows?

Is it possible that all the items in a slider are equally important and need to share the same space (albeit not at the same time)? Yes it is. But is it likely?

*After all, websites are not newspapers. Where the fold is for any given user is dependent on screen size, browser viewport size, display resolution, device, and of course the user’s act of scrolling. It’s hard to ask for “above the fold” when we don’t even know where the fold is.

Wood Type Revival: WTR Borders and Ornaments Released!

Thu, 24 Jan 2013 10:58:35 -0500

Wood Type Revival: WTR Borders and Ornaments Released!:

woodtyperevival:

Go check out the latest Wood Type Revival release: Borders and Ornaments! Loads of fun decorative elements drawn from original wood type from the WTR collection. Just like all WTR fonts, it’s only $15. And if you were one of our wonderful Kickstarter bakers and still have credits – it’s a…

Bearded Work at the Grunwald Gallery, Bloomington, IN

Thu, 10 Jan 2013 19:18:52 -0500

Bearded Work at the Grunwald Gallery, Bloomington, IN:

Indiana University is showing work representing all the departments in the School of Art, and Graphic Design is being represented by BFA alum and Bearded founder Matt Griffin.

On display will be letterpress and web work involving the talents of past and current Beardeds: Brett Bender, Matt Braun, Dominic Dagradi, Mark Frey, Patrick Fulton, Matt Griffin, and Michael Hellein.

If you’re in the Bloomington area, please stop in and take a look!

Matt Griffin Interviewed for Responsive Design Weekly

Mon, 07 Jan 2013 12:56:25 -0500

Matt Griffin Interviewed for Responsive Design Weekly:

Since December, Responsive Design Weekly has been interviewing people at the forefront of the RWD movement and publishing their answers to the same four questions. This week Bearded’s own Matt Griffin shares the stage with Ben Callahan.

Work for $ Design for ♥

Fri, 07 Dec 2012 08:47:36 -0500

Work for $ Design for ♥:

by Matt Griffin

A nice excerpt from David Airey’s new book Work For Money, Design For Love on AIGA’s website talks about how and why Matt Braun and I created Wood Type Revival.

Living in Interesting Times

Fri, 30 Nov 2012 16:28:55 -0500

by Matt Griffin

2012 is almost over, but in Beard Years, we’ve already hit our big annual milestone. On 11.11.12, Bearded turned four years old. A not insignificant moment, for what began as two guys in their homes with an iMac and a pink laptop.

For Bearded, 2012 has been clearly marked by change. Over the course of the last year, we switched our primary development platform from Drupal to Ruby on Rails, and we completely re-worked our design process to better reflect the new responsive web. I think there might be a few screws in my desk that we haven’t replaced yet, though.

Our new front-end dev, Patrick Fulton, has been here nearly eight months now. Not unrelated, his new ginger beard is really coming along. Beard or no, he’s fitting in quite nicely.

Not satisfied with all the ruckus, though – we’ll be enacting another big shift today. Longtime developer Michael Hellein, who has been working remotely from Vermont for the last 2 years, will be leaving Bearded for new adventures up north. His spot will be taken by Mark Frey, who has been working on Bearded projects as a contractor since the Pittsburgh Children’s Museum website. Mark’s mighty beard puts mine to shame, frankly. Come to think of it, our company will now be roughly three times as hirsute as it was last year. Infer from that what you will.

This year I somehow managed to become twice published in my favorite web design publication, A List Apart, as well as my runner-up favorite .net Magazine. In the last few months, we’ve started working with some truly great Pittsburgh institutions, including the Pittsburgh Children’s Museum, the Pittsburgh Glass Center, the Andy Warhol Museum, and the Carnegie Museum of Art – not to mention the warm and fuzzy feelings created by our recent collaborations with The Mario Lemieux Foundation. The prospect of working for clients like this is, to be honest, one of the biggest reasons I took the leap to start Bearded in the first place. Feels good, man.

On top of all that we launched by far the largest website we’ve ever built. AIChE’s new site and it’s four subsites represent tens of thousands of nodes of content – I can’t even begin to recount how many useful lessons we’ve learned from just the first phase of that project.

After all the growth and exhilarating change of 2012, we’re all looking forward to settling into our new configuration, and blazing ahead with renewed vigor and focus. We may be four years in, but it feels like we’re just getting started.

Ready? Engage.

Web Developers, Inquire Within

Mon, 12 Nov 2012 14:27:00 -0500

Note: This position has been filled. Thanks to all who applied!

In a rare alignment of the Internet Planets, Bearded is hiring a web developer! Here’s what interested parties need to know:

We are a small, collaborative group of designers and developers who are working to build the device-agnostic web of the future. We ♥ the Internets like crazy, and are constantly looking to better our process and products with today’s bleeding edge ideas.

We’re committed to the responsive web, and are working with our peers to find the right way forward in these exciting and unstable times. Not to toot our own horn, but Ethan Marcotte (author of Responsive Web Design) said after we launched the new Pittsburgh Children’s Museum website: “I would like Bearded to stop making the rest of us look so bad.”

Our ideas can be seen in the finest publications of the web like A List Apart and Dot Net Magazine. And if you’re still hungry for more, just dive on into the blog.

The work environment is relaxed, flexible, and supportive. If you’re nerdy about the Interblags, it’s also super fun. We’re very generous with vacation and health care.

You will have a great deal of autonomy. If you like blazing your own trail and getting credit for your work, you will love it here.

No one will hold you back from the future. You will level up like crazy, and help the rest of us do the same.

Our clients are awesome, and will leave you with warm fuzzy feelings when you go home at the end of the day. Just check out our client list, chock full of non-profits, and you’ll get the idea.

You

You are neither a ninja, nor a rockstar. You are totally into the web, and love building this stuff. You take pride in the craft of software. You love solving problems and working with an awesome team. You strike a realistic balance between “perfect” and “good enough.” You’re curious and have a tremendous appetite for learning. You put the good of the team and your work ahead of personal ego. You can both accept and give constructive criticism. Sometimes you dig playing video games, and you think the memes are hilarious.

You probably think of yourself professionally as a full stack developer, leaning towards the back end; or a back end developer leaning towards full stack.

Strong working knowledge of:

• Ruby

• Source Control software (preferably Git)

• Relational Databases (We use postgres, but any will do)

• MVC Architecture

• Object-oriented programming

We will prefer candidates with:

• A background in Computer Science or a similar field

• Rails Experience

• Javascript Experience

• Experience with TDD / BDD / Automated tests

Some stuff that is definitely helpful, but not essential to have experience with (in descending order):

• CSS/SCSS/Compass

• Systems administration (Linux / MacOS)

• NoSQL Database systems

• Native iOS or Android development

• Node.js

• Drupal

• Wordpress

• PHP

Action

Still here? Awesome!

Go to this contact page and send us:

• A few words about why you want to work at Bearded

• A link to your online resume

• A link to your Github page

• Your salary requirements (we just want to get this out of the way early on – a range is fine)

• One thing about yourself that no one else applying to this job will say

Thanks for reading. See you on the Webosphere!

Bearded's Matt Griffin Interviewed On the Non-Breaking Space Show.

Thu, 25 Oct 2012 14:49:36 -0400

Bearded's Matt Griffin Interviewed On the Non-Breaking Space Show.

Responsive Comping on A List Apart

Tue, 16 Oct 2012 10:13:00 -0400

by Matt Griffin

My new article, Responsive Comping: Obtaining Signoff with Mockups, is now live on A List Apart. In it I take a detailed look at Bearded’s browser/code-based approach to designing responsive websites – something that’s been very much on our minds for the last 6 months. I hope it’s helpful to you.

I am once again grateful to Jeffrey Zeldman and the entire ALA staff for their support and encouragement. They helped me progressively nudge a reasonable blog post into a fine and useful article. Particular thanks goes to my editors Rose Weisburd and Sara Wachter-Boettcher. If you find my words logical and easy to follow, it’s surely due to their efforts.

My RWD friends Ben Callahan and Brad Frost also provided a second and third set of eyes early on in the process, as did my pals here at Bearded.

Thank you all for your help and insight. Now, back to work for me!

–MG

The Thing About Those Media Types

Mon, 15 Oct 2012 15:53:00 -0400

by Matt Griffin and Ben Callahan

After my last blog post about vertical media queries, I received an intriguing tweet from Sparkbox’s Ben Callahan. He asked:

“Curious, why do you use ‘only screen and…’ by default?”

When someone like Ben asks you a question like that, you may quickly realize that you do not have a great answer prepared.

A few weeks later and we were digging into the implications of media types on Skype. Here’s the deal:

At Bearded we’ve been specifying “only screen” in our media queries. At Sparkbox they’ve been specifying no media type, which results in all media types getting their media query-based styles.

We both agreed that we wanted all screen-ish devices to get our responsive styles. What makes the situation a little less clear is that most media types that we’d want to get our media queries, but are not actually screen (handheld, projection, tv), often identify themselves as screen because … well, because nobody ever uses those other media types.

But the idea with responsive design is that we don’t know what’s coming down the road, and we want our flexible designs to handle those unknowns as best they can. Which means in general, we want all media types to get our responsive styles.

That in mind, the Sparkbox approach seems more appropriate. Everybody getting the responsive layout is definitely better than “only screen.”

There are, however, some media types that we probably don’t want to get all of our extra styles. Print being the most obvious. Taking a whitelist approach of “screen, projection, handheld, tv” is not very future-friendly, as it would disallow future media types. So then we wondered: could we take a blacklist approach? Is there a “not” function?

Turns out there is. At first glance, this seemed pretty exciting. At first glance, this seemed pretty exciting. We both thought something like:

not print and (min-width: 60em)

… could be pretty useful – if the “not” only applied to “print.” Ben took the time to put together some tests to see how it worked, and unfortunately the results were a bit discouraging. It seems like the “not” keyword ends up applying to everything, media type and media query – which is less than helpful..

So now we’re back to the beginning. Is the best approach really just to not specify a media type (or specify “all”), and let everything get the responsive layout? Does this impact accessibility for types like braille, tty, or speech? We have no idea. And that, internet friends is where you come in. If you have any thoughts, please let us know on Twitter: @elefontpress & @bencallahan.

Update: Ben has written a follow-up with some great stuff on the Sparkbox Blog!