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.
Some unconventional wisdom from David C Baker that I'd like to revisit every once in a while: "“Why Monthly Recurring Revenue (MRR) Arrangements May Not Be Ideal”":https://www.davidcbaker.com/why-monthly-recurring-revenue-arrangements-may-not-be-ideal. He concludes: "If I’ve confused you with all this, just concentrate on this one point: retainers and MRR relationships scream hourly work, and you shouldn’t be doing hourly work." But at least for me at Engaging, the opposite is true: I've always billed hourly anyway, and some MRR arrangements I've made more recently have freed us from thinking in terms of hours (even though I'm still habitually keeping a log of hours worked).
"State of CSS 2019":https://2019.stateofcss.com/.
"Naval's How to Get Rich: Every Episode":https://nav.al/how-to-get-rich. His bifurcation between wealth and status is particularly bracing.
The Beta for Strapi v3 is out, with such major internal changes that it might well have been Strapi 4. Strapi is the Node-based self-hosted content management system / API generator that I use (though not yet for this site). The "migration":https://strapi.io/documentation/3.0.0-beta.x/migration-guide/migration-guide-alpha.26-to-beta.html is quite involved, but for the first time I can remember, a migration like this went off without a hitch and worked first time! I'm very pleased with my choice of Strapi, even wearing the t-shirt. Bravo the Parisians!
Interesting /r/webdev thread: "Does real web dev exist? Like the stuff they write all those articles about?":https://www.reddit.com/r/webdev/comments/bu7lii/does_real_web_dev_exist_like_the_stuff_they_write/ The consensus seems to be that the further along the spectrum from web site to web app, the more testing and whatnot becomes worthwhile.
Nice frank piece by Monica Lent, a software engineer in Berlin, about "mistakenly believing one is a senior developer":https://monicalent.com/blog/2019/06/03/absolute-truths-unlearned-as-junior-developer/.
Well this is handy: an article on "all James Bond's watches":https://www.watchtime.com/featured/watches-james-bond/.
We must be facing this: David Gelertner on "giving up Darwin":https://www.claremont.org/crb/article/giving-up-darwin/. Like Smith's invisible hand and even Newton's laws of physics, these glorious, newly-algorithmic cosmologies — the precursors to our wonder-world of bitty digitalism — aren't the full explanation.
First episode of "Views on Vue":https://overcast.fm/+Meco779Jw that I've found worthwhile, on things people _don't_ like about Vue, including a discussion on language and translation.
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