A bit mindblowing: put the browser itself in the cloud: Mighty [Hacker News discussion].
Since major overhauls to a web site are relatively infrequent and set the stage for years to come, they are rare and vital opportunities to step back to basics. What should the site be? What should it express? Who is it for and what should it do for them?
MindBody is a web-based management system widely used by yoga studios. Using MindBody’s SOAP-based API, eeMindBody provides an easy way for a studio’s ExpressionEngine web site to access its MindBody data.
MacStories does an AirTag review roundup.
Craig Mod reveals the consolations of we the web-literate as he tinkers with his servers. Plus the man walks and writes rather well and is probably tall to boot.
OK I haven’t actually read this yet but really honestly intend to. Via Robin Rendle on CSS Tricks via Jim Nielsen’s Blog, A Complete Guide To Accessible Front-End Components by Vitaly Friedman in Smashing Magazine.
Andy Bell outlines new CSS functionality in Smashing Magazine.
Dated but still interesting: The Guardian looks at the rather disappointing design of Japanese newspaper websites.
The Basecamp fellows have released a new web development paradigm, Hotwire. I don’t quite get it, but with their pedigree and skill as the makers of Ruby on Rails, this could be big.
Dave Rupert does a nice job (April 2018) listing the pitfalls of card UIs. I’m beginning to think though that for Rupert, a long list of drawbacks is throat-clearing for “I’m going ahead with this.”
Metatags.io, a very nice tool to test your metatags. Bravo, makers.
Launch is probably just the first of many phases.
nce everything’s built and running silky smooth at a web site or system built to your specifications on a robust platform, you can start cashing in on the benefits of such a setup by having us add new functionality and features.
In fact, in the spirit of software’s “release early, release often” mantra, we generally divide projects into phases from the get go, building out each part to completion before starting on the next. That way, ongoing support and development is simply a continuation of the initial working style.
The entire process, with dependencies