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.
I like it, I like it: "theorizing":https://blog.hichroma.com/the-crucial-tool-for-modern-frontend-engineers-fb849b06187a on "UI components":https://blog.hichroma.com/hidden-in-plain-site-the-levels-of-component-reuse-ee9b0d7b1bd2 by Dominic Nguyen.
"34 most popular GitHub JS repositories in March '19":https://dev.to/iriskatastic/34-most-popular-github-js-repositories-in-march19-4hkb by Iren Korkishko
Putting the ack! in acquihire: "Our Incredible Journey":https://ourincrediblejourney.tumblr.com/.
Jonathan Hoefler explores something that typeface designers have long known but that researchers have only now corroborated: "horizontal lines appear thicker than vertical ones":https://www.typography.com/blog/turning-type-sideways.
Important to consider: despite choice fatigue, "users do benefit from some symbolic choices":https://medium.com/s/story/the-ux-uncanny-valley-cf30df9fb45a, this piece argues.
"itshello.co":https://itshello.co/ — clientless, open-source video chat in the browser.
Now that's a web site: "New York City tree map":https://tree-map.nycgovparks..org/#treeinfo-2135461 -- every last one, including street view, species, diameter. [via Kottke]
Wow, a "360° Taliesin West walkthrough":https://my.matterport.com/show/?m=iWvNCvUJxvg&utm_source=4.
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