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 miss the days of forums, when any issue about a product was discussed on its own site and nowhere else. I do believe issues are better resolved online with posts, not chats. Inappropriate use of chat software erodes mental health, at least, mine. Here's a fun articulate essay on why the author "hates Slack":https://bitquabit.com/post/i-hate-slack-and-you-should-too/ (and you should too). And Slack is proprietory. I just scrolled up and was stopped and told I need a paid plan! And Discord: why?! Trendiness happens.
"“Breaking Smart”":https://breakingsmart.com/en/season-1/ by Venkatesh Rao. This is the first collection, "Software is Eating the World", inspired by a residency at Andreessen/Horowitz.
"“The Premium Mediocre Life of Maya Millennial”":https://www.ribbonfarm.com/2017/08/17/the-premium-mediocre-life-of-maya-millennial/ by Venkatesh Rao is the best thing I've read on the internet all year. I especially love his notion of being "above or below the API line". For more mediocrity theory, see his "“Survival of the Mediocre Mediocre”":https://www.ribbonfarm.com/2018/04/24/survival-of-the-mediocre-mediocre/: "Evolution is survival, not of the most mediocre (that would lead to paradox), but _survival of the mediocre mediocre_."
"“Modelling Process Intensive Scenarios for the Smart City”":https://link.springer.com/content/pdf/10.1007%2F978-3-662-44426-9_12.pdf [PDF]. In this paper by professors at the computer science department at the University of Camerino in Italy, the authors discuss BPMN (and bpFM, which I'd never heard of before) in the context of municipal services, specifically bike-sharing. Another perspective "on bike-sharing, this time re usability, by mobile-first thought leader Luke Wroblewski.":https://www.lukew.com/ff/entry.asp?1995
Impressive mobile usability thought leader "Josh Clark shares the tools he uses":https://aneventapart.com/news/post/josh-clark-the-tools-i-use, from pen to Piwik (now Matomo).
"Inflatable, an awesome logo.":https://www.underconsideration.com/brandnew/archives/new_logo_and_identity_for_inflatable_by_collins.php
"Why does tech have so many political problems?":https://marginalrevolution.com/marginalrevolution/2018/08/tech-many-political-problems.html A list of 17 answers by Tyler Cowen. I love the phrase "Robespierrean social justice terror".
Why was he like this to her? Excerpt from "Lisa Brennan-Jobs' upcoming book about her father Steve":https://www.vanityfair.com/news/2018/08/lisa-brennan-jobs-small-fry-steve-jobs-daughter.
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