Dictionary of cloud stuff. (Work in progress…)
See also: Cloud Native (Bookmarks).
My bookmarks. Mess of. Publishing them to spur myself to… put in order (before everything we know becomes obsolete!).
(Last updated 2020-10-19.)
WordPress is dead (and doesn’t know it yet). Gutenberg is… wrong on so many levels. But, I can’t develop an alternative for this devlog, yet. So, for now, hacking to the rescue!
For a specific usecase (slideshow) where I need(?) to tweak HTML markup, the WP editor’s “raw” HTML editing turned out unusable — mutilates the HTML too much. I’m already comfortable editing HTML in Geany, locally, but copy-pasting to keep a local file and WP in sync would be a significant hindrance. Here’s how I coded (and open sourced) this hack…
[Lecture slides. Work in progress…]
What the WWW was/is/will be all about, software engineering principles pertinent to web development (web=app=mobile), current failures and implications for startups, and maybe attempted forecasts?
A serial CTO’s perspective on what makes the world (of PWA startups particularly) tick.
The long and winding road of (low-level) migrating content from a Drupal website to WP. Workplan: MySQL and SFTP → SQL → CSV → scripting → import plugin → theme hacking…
Teacup (HTML templating in CoffeeScript) is a fantastic DSL (domain specific language). Less “specific” than Jade, but it’s a programming language, so the potential for extending is exciting! I’ve been writing “helpers” to abstract HTML details, make my templates a higher level DSL.
But, although Teacup has nice facilities for extendibility, it’s restricted by its rendering architecture: a single pass, depth first recursion, immediately rendering CS→HTML. This limitation obviously prevents post-processing of nested contents by wrappers higher up the call stack, given, of course, we don’t want to manipulate/parse rendered HTML — that would smell wrong, and require a complex and slow full parser… which really misses the point.
Two use cases I’m sorely missing: patching any nested content to, eg, provide defaults, and freely composing helpers, eg:
# Allow wrapping immediate calls: mockup initially_hidden screen '#home' # But also support wrapping callbacks: mockup ->initially_hidden ->screen '#home'
(First form calls inner, then wrapper; second form — reversed order.)
Thus, Teacup must be hacked!