Since such overhauls are relatively infrequent and set the stage for a web site 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.
Clickbait undoubtedly, and for a tiny niche, but Jason Bloomberg suggests in The End of Business Process in the Digital Era that business processes will be replaced by digital journeys. Seems to me though that this is merely a name change to handle some increased complexity, since a process remains a process?
A photo essay by Dan Frommer on attending Apple’s iPhone X event — its first at the Steve Jobs Theater.
There’s some powerful new stuff in iOS 11, as summarized at The Verge. Document scanning in Notes (though no OCR, need an app for that). Markup on screenshots. Screen recording. A file system. Configurable Control Panel. I do so love Apple.
I appreciate this nicely laid out summary of wisdom reminders for the working life by Studio Lovelock, This Much We Know.
Another dizzyingly ironic yet comic and worthy essay by a late 20-something “writer based in Brooklyn” (I shouldn’t disparage, to be such was my highest ambition), this is Daniel Kolitz’s What I Learned at Personal Branding School.
What an internet treasure. Standard Ebooks is — according to their web site — “a volunteer driven, not-for-profit project that produces lovingly formatted, open source, and free public domain ebooks.” These are some beautiful, consistently-designed ebooks. The epub version works a charm in iBooks.
Wired on Apple Park.
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