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.
Now that I’ve joined eyeem.com, I was attracted to this article on Instagram and art history. “Today, we look at Instagram feeds with the same level of scrutiny as the Renaissance merchants who converted their Madonnas into ducats.” He argues persuasively and enjoyably that we are being just like Amsterdam burghers.
From the top: Chapter 1, Part 1 of The Internet History Podcast.
Joel Spolsky announces the public beta of HyperDev, “a developer playground for building full-stack web-apps fast.”
Likely the canonical review of Mr Robot, Season #1. By Matt Zoller Seitz.
As announced at WWDC 2016, Macworld summarizes the new things in iOS 10. Among them are voicemail transcription, a new Home app for HomeKit-enabled devices, and a redesigned Control Center.
Lately I’ve noticed an irritating profusion of paid-in-kind reviews on Amazon—see Is Amazon Doing Anything To Fight Latest Wave Of Fake, Paid-For Reviews? in The Consumerist. I think that allowing this is a huge mistake on Amazon’s part—the first I can remember seeing them make. It essentially makes their incredibly valuable review functionality—even other retailers include it in their web sites—valueless. Worse, it’s irritating and draining, because you have to scan to the end of a review to find out if it’s been subsidized by the vendor. See “How to Snag a Deal by Writing an Amazon Review” in USA Today. The current antidote? fakespot.com.
Nicely presented on Vimeo, Jen Simmons of The Web Ahead podcast gives a 1-hour talk on web design at a 2016 An Event Apart conference entitled Modern Layouts: Getting Out of Our Ruts. Lots of nice slides of magazine layouts, where she suggests web designers should be returning for inspiration.
Centralized or distributed computing? It’s a pendulum.
Hoefler & Co provides a wad of typography tips for mobile.
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