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.
Goodbye, grids, I at least hardly knew ye. Ethan Marcotte, coiner of the very term responsive design, argues that a web design today should “algorithmically generate a responsive layout that best reflects the importance of the information within it.”. Yes! Another choice quote: “The breakpoints we introduce to our responsive designs aren’t tied to the shape of a device’s screen. Instead, our media queries defend the integrity of the content we’re designing.”
Maciej Cegłowski is surely a genius. His article, the text version of a talk, is about website bloat, a topic important to whoever cares about the web (and increasingly as it becomes dominated by big sites I realize it’s easy to stop caring). He explains why it matters. And is funny. He makes a living with software but is also a painter. [Via Daring Fireball]
Interesting, easy-to-understand breakdown of colors used in iOS app icons in 2015. Reds are most popular, then blues. By Hwee-Boon Yar. [via MacStories]
A professor of medieval history laments the contemporary propensity to be surveilled just as Europeans were by the Church. [Via aldaily.com]
Hard to say which part of this is more valuable: John Gruber interviewing the right venerable Craig Federighi on Apple’s Swift programming language or the very lengthy and insightful follow-up with John Siracusa. Daring Fireball’s The Talk Show #139.
Like the author burrowed into my mind and shone a light on the murk, these thoughts about CSS are three years old now but still valuable for anyone doing front-end web development.
Great fun piece with side-by-side illustrations of architectural and web design epochs.
I found this quite exciting: Mike Maas of Cisco expounds on how the Internet of Things will be integrated into the factory floor. (1:11:34)
The squat, the perch — a reminder that we are not designed to defacate in seating position.
As well as smarts, what really makes a successful implementation likely is experience.
rmed with a plan for the back-end, the rubber hits the road with the installation and configuration of the system chosen for the project.
Each system of course has its own way of doing things, and developing a plan on paper into an actual working system is always a bit of an act of translation. The likelihood of a successful realization of a plan within a particular system is increased mostly by one thing: experience with that system (smarts notwithstanding).
Engaging.net’s experience is with ExpressionEngine — as users of its predecessor, pMachine, we’ve been using EE from the moment it was released.
With EE, the system itself needs to be installed, as well as the software it rests on (see the ExpressionEngine Requirements page). Then we can install and configure the add-ons and build out the channels, fields, categories, statuses and member groups.
The entire process, with dependencies