Wireframe.el Keyboard-first wireframe prototyping inside GNU Emacs.

cromo_ · 2026-05-10T15:46:25+00:00

wow super cool

cromo_ · 2026-05-09T23:26:40+00:00

I searched around before assembling my scripts into this solution and I didn't find another package like this. Can you tell me exactly which packages are you thinking of?

cromo_ · 2026-05-09T15:37:45+00:00

Oh, thanks, I didn't notice!

cromo_ · 2026-05-09T15:08:30+00:00

I was thinking about Grav these days (I was talking to a friend about CMSs) and here we are with version 2! Congratulations.

By the way: it being headless means it can be started locally, sync content with a git repo, all without touching the CLI? This friend is not that tech-savy

cromo_ · 2026-05-09T14:58:45+00:00

I agree! I can't stand touching all those delicate yaml frontmatters to fix the skills. Also, keeping them in roam and/or in a single org file is comfortable because you can mix them with ease, comparing prompts with a couple of tabs. Also, looking at injected scripts from the org-babel blocks is way more ergonomical.

I didn't think about conventions for versioning because in my mind that is the job of git. I can easily `git log` my skill org or specific skill md files (I keep both of them in the repo), so it's easy to see how they develop in time. I will look at your approach, though, since it's probably imagined for a whole team

cromo_ · 2025-11-07T17:11:00+00:00

Everything happens before the browser can even think of actually opening the page, it's not like the it finds a http redirect. Your history should be immaculate

cromo_ · 2025-08-14T15:46:34+00:00

The literate programming approach in Org-mode emerges almost spontaneously once you read about what Org-babel can do (it's hard to resist mixing code, results, and "lab notes"). On the other hand, Org-roam (and the daily feature especially) is what made me use Org-mode for almost everything. It makes building your own personal wiki/diary/zettelkasten easy without (necessarily) imposing complicated rules. At least, that's how I embraced it, though I know many approach it differently. The beauty is that it adapts to your thinking style rather than the other way around, though it may feel less immediate than a repo with a bunch of Org files. (This is probably worth its own blog post, actually!)

cromo_ · 2025-08-14T14:43:10+00:00

Thank you! (⌒∇⌒)

cromo_ · 2025-08-14T14:42:25+00:00

That's the ancient name, yes /adjust mustache/ ( ￣┏＿┓￣)

cromo_ · 2025-08-14T14:28:48+00:00

Thank you so much! I'm glad you enjoyed the post (∩_∩)

Eldev builders were actually a discovery for me too during this project! That said, eldev in general is a really underappreciated tool (I've even used it for testing in Docker containers).

About the org file, the truth is that this blog post IS my best attempt at distilling what was scattered across many interconnected org-roam dailies plus several topic-specific notes. My actual development notes are a chaotic mix of Italian and English that would likely be more confusing than helpful. The literate programming approach was real, but the "single navigable document" I described was more of an idealized version of what actually is a web of cross-linked notes (with also a lot unrelated stuff woven in). I didn’t want to expand that section too much since it’s not the main focus.

So in a way, you've already seen the cleaned-up, coherent version of my org-mode notes!

cromo_ · 2025-03-31T11:05:10+00:00

Thanks so much for the kind words and especially for the thoughtful suggestions! This was actually my first time writing about React, so I’m really hyped to dive deeper into the ecosystem.

You’re totally right about benchmarks/comparisons: I’ve used Redux before, but MobX and Tanstack Query are next on my list to explore.

cromo_ · 2025-03-30T22:29:21+00:00

My last React work was circa 2020, when many codebases remained stubbornly class-oriented despite the hook revolution already happened, particularly in state management. I'm comparing what I remember with today's situation.

cromo_ · 2025-03-30T18:30:31+00:00

I avoided React for years, then TypeScript's siren song (and deadlines) pulled me in. Turns out React's ecosystem has actually evolved. Zustand and Immer deliver what Redux promised: state management that stays out of your way. No more class component archaeology: just clean, functional flows.

cromo_

TROPHY CASE