The animated line-drawing illustrations at Ralph Ammer blog definitely make me want to read every post!
Since major overhauls to a web site are relatively infrequent and set the stage 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.
Poolside.FM, the lovely Mac throwback to 1997.
Ash Kyd built his web site to look and act like Windows 95 — cool!
technovelgy.com, where science meets fiction, and a glorious taste of the old web.
An anonymous employee beneficiary of Twitter’s IPO: “I think a lot of [people in Silicon Valley] care about basic income for everyone, because we’ve lived with it ourselves.”
More people will die from Covid-19 because we cannot study drugs more quickly, writes Matthew Herper in STAT.
Yes. Anonymized data from all patients should be accessible to all. The social media giants have demonstrated that it can be done — data entered from all over the world into a single system that produces meaningful output. Indeed, the web is the perfect medium for it. Rather than setting up trials to evaluate the efficacy of a treatment, researchers could instead be checking the global treatment knowledgebase.
Using their web-connected devices, registered medical practitioners would log each step of a patient’s treatment as it happens; in medicine a new understanding would take hold that the practice is to both treat the individual at hand and publish that treatment because every facet of every case history can contribute to a myriad of studies.
A standards body could set the data model that is a medical case. Presumably the model would emanate out to include such information as the identity of the treating hospital, so that, eg, the geographical locale can be factored in by researchers.
One problematic aspect of a case is the patient’s anonymized identity, required for factoring in pre-existing conditions. A new price of our medical care would be its worldwide publicization, and the understanding that motivated organizations could connect even anonymized medical data with other aspects of a person’s life, such as a cessation of credit card use during hospitalization. Yet given what we now see is the catastrophic fallout of a pandemic, we will surely come to accept this cost, just like say driving licenses. Moreover, perhaps this could justify to Americans why healthcare should be free: one is contributing one’s medical biography to the knowledgebase.
Such instant availability of global treatment data would be useful not only to researchers but also — and possibly primarily — to doctors devising treatments in the moment.
In Reading Newsletters with Feedbin and Reeder Federico Viticci rebels against the new too-cool-for-school notion of reading what should be on web browsers as newsletters in email clients.
“More news, less junk. Faster.” Brent Simmons has just released the free and open source RSS reader NetNewsWire app for iOS. This may well be a visible dent in the universe.
In an interview with Kelly Gulmont on MacObserver, he says in an interview that one of the things he’s most proud of is that search is really fast (in a 20-minute podcast, this, remarkably, is the only bit of substance; I won’t be listening again).
There’s a review up at MacStories, “NetNewsWire for iOS and iPadOS Review: The Perfect Complement to the App’s macOS Counterpart” while Cult of Mac has “NetNewsWire is reborn on iOS”. Also 9to5Mac.
DesignBoom’s sauna page. This is just great work about great work about great living.
In CSS-only fluid modular type scales, Trys Mudford lays out the code for letting type grow appropriately (and uses the Golden Ratio for the steps). Very nice!
And I love the applied musical modular scale, which I’d not seen before, one of those great things that in retrospect seem obvious.
I’ve been fumbling towards all this without stopping to actually systematize it as they’ve done. And they did it here in Brighton, at Clearleft. Kudos.
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