“Every practice we use as part of our work puts forces on us, and generally those forces can push us toward or away from more successful ways of doing things.” –Ron Jeffries
I tried forestry.io and investigated netlify. Interesting, but the experience is far from frictionless. They still force a good deal of developer-level complexity on you. Short story: neither seems to be the magic bullet I was hoping for.
Minor nit: I save frequently while editing, which creates a stream of work-in-progress commits when using those tools. Annoying.
I’m intrigued by services like forestry.io and netlify that put a browser-based editor in front of a static site generator like hugo. Seems like that’s what is needed to make static sites a compelling alternative to the traditional CMS.
I keep thinking of John Gordon’s “How to build a safe and sane social network” this weekend. “Essentially it’s the public radio model.” Intriguing.
Unlike the raw indieweb – interesting ideas, but a science project – Gordon’s is a model that could actually be workable. It’s a federation of nodes, where each node is used by multiple people. The tech people (let’s call them “tinkerers”) can run the nodes, while the non-tinkerers can participate either for free or for for a small donation.
The critical part is that it allows for easy use by non-tinkerers, aka “normal people.”
Indieweb’s weakest spots are exactly where the big silos add most value: effortless social connection, simple UX, and hiding the complex infrastructure.
One strong aspect of our React/Redux-based architecture has been the separation of concerns. When some code turns ugly, the damage is often contained in one small area.
Trying out the Hugo static site generator. So far I’m loving it. Wicked fast, easier to work with than everything else I’ve used.
I’ve found Amazon Echo “skills” SDK far too complex for simple IoT / smart home devices, and the resulting UX is awkward and poor. Built-in echo support for wemo switches is better – and can be emulated for arduino devices. +1
The Amazon Echo = game changer for my Arduino projects: a voice interface for wifi-enabled ESP8266 devices. Fits the command-based devices best.
I’ve been using a small board called the Oak from digistump for deploying arduino home-automation devices around the house. The Oak is a great board with good wifi, but the Particle firmware has always been trouble: difficult to set up, random flaky behavior, etc.
At heart the Oak is an ESP8266 chip, and these days there’s a lot of independent support for ESP8266. So when I found some notes in the Oak forum about removing the Particle firmware and using the ESP8266 core directly, I jumped at the chance to try it out.