Yesterday I pushed out Respons-O-Matic, a very simplistic tool to preview RWD layouts, without much thought to how others might use it. Unsurprisingly, a few folks had some really great feedback on their own workflows, and how to make Respons-O-Matic play nicer.
Check out the updated demo if you want to see it in action, or head to the repository on Github for the code.
Here’s what’s new or different:
This weekend I was testing out some new layouts I’ve been working on, and I built myself a little tool to preview Responsive (RWD) layouts more easily.
I thought it might be of use to some other folks as well.
It looks like this:
And you can check out a demo or go snag the repository on Github and have at it.
Further Reading As I write in the FAQ section of the repo, Respons-O-Matic is not meant to be a substitute for real, on-device testing, or anything else for that matter.
Wowzers, have the days simply flown by in April! It has been a little while since my last post, and this one is going to be a brief one to be sure, but I wanted to catch up to what’s been going on this month.
Reboot! First up, May 1st Reboot is right around the corner. Just three days left to crank! If you’re launching, relaunching or just breathing new life into something on the web, you should check it out and follow #May1Reboot to see what our colleagues and community are up to.
(Update: Forgot to include ScrollMagic. Big oops!)
Before I continue, I wanted to set forth what this post is about. It is not a teardown of jQuery or a preachy case for using such-and-such a JavaScript framework.
Rather, it is an acknowledgement of two things:
If your target is modern browsers (really anything post IE8) and you are building something of modest size, then any library or framework, jQuery or otherwise, may be overkill.
It’s midnight, and for the past hour I’ve been trying to figure out why I was unable to echo the correct id values for rows of data in my blade templates. I thought I was going crazy. Here’s the relevant template snippet, and its output:
feed/index.blade.php <ul> @foreach ($feeds as $feed) <li><a href="/feed/{{ $feed->id }}">{{ $feed->title }}</a></li> @endforeach </ul> Output <ul> <li><a href="/feed/0">BBC News - Business</a></li> </ul> There is obviously a value in the object sent to the template, which meant the id attribute was present at least.