Hello. I, too, am so, so very old. Oh, lordy. :(

Different needs require different solutions. I like to think of it like this: If you need to hammer in a nail so you can hang a picture of your mom, you can get away with using a rock to bang it in for free, or you could go buy a really cheap hammer at the hardware store.

However, if you're a professional carpenter – making chairs for a living – a rock won't do. In fact, you might not be in the market for a hammering tool at all, since a custom chair-making robot would be what you'd actually need.

Likewise, if you have a garage band that need a place to announce your next gig, then a template site (or even a Facebook page) might be all you need. But if you're a business, who need to convert your pageviews into sales in order to pay your employees – you're going to need a custom solution.

And just as we need both cheap hammers and CAD milling robots, we need simple cookie cutter solutions for websites, and bespoke design that take individual business needs into consideration.

And I for one think the one with the robots is more fun.

I really like Lea Verou's WCAG contrast checker-thinggy as a sanity check for colour contrast.

Looks really good! Love the daring but fitting use of motion.

From a code point of view, there's a lot of divs going on there… I'd definitely try to cut some of the container divs, and switch some of them to more semantic container tags, like header, footer and main.

Also not sure if I'd still bother providing px-fallbacks for REM-units anymore. And you don't seem to use neither Playfair or Montserrat anywhere, so no need to keep those references either?

The contact icons have an empty class attr., which we could probably do without.

I'm also not sure the third person in the body copy works for me here – the design has so much personality, and feels so personal, and the third-person kinda takes me out of it.

All pretty insignificant – over all I really like it! You've created a great little world in just the single-pager, and I'd love to explore it further in the coming pages.

I would keep going with the mystical wood, game-like theme.

Just be careful not to overdo ye olde english – especially in long-form case studies. Do tell the studies as stories, and if you find a way to naturally frame them in the world you've created that would be awesome – but the character you create for yourself on the site shouldn't be too far from the one I'd meet if I came to an in-person business meeting with you.

(In my opinion "Hail fellow" treads close to overstepping that fine line, which in turn makes "forged" seem strained, even though the rest of the bio reads well. And I love "send a raven".)

Again, really great world building and design - can't wait to see it evolve!

Works for me!

Oh, well. ¯_(ツ)_/¯

We've adapted the GV design sprints a bit, basically aligning the design sprints with the two-week development sprints (I'm the sr. designer at a software development company), and we run sprints continuously.

That extra week is spent adding in a fair bit more traditional research, and usually creating prototypes using more-or-less production ready code. Which takes a bit more time up front, but saves us a lot of time if our tests are successful. (Really novel ideas where we have little to no existing code to build on is still done in Sketch and InVision, though.)

Works really well for us. It means all new features and interaction patterns get run through a design sanity check, while keeping design an integral part of the product development cycle.

I liked the way Hubbub and BBC solved it in the Rest Test.

I use the Withings Aura, which is a beautiful device, that also uses light to wake you, as well as an assortment of less-jarring-than-an-alarm sounds (think wood chimes, birds chirping, etc.) to wake you up. It also has a sensor that goes under the mattress, that keeps track of how much (and how deep) sleep you're getting, and attempts to wake you up when you sleep the lightest.

It has had some software issues, though - thinking I'm asleep when I'm not, and not registering touches sometimes. Overall satisfied with it, though.

Seemingly not, according to the browser support-section of their GitHub-readme. My guess is that service worker support is the biggest bottleneck here. :/