I've elected to pay less attention to the more Notion-y and business-y use cases for this big shaggy mound of features I'm piling up, and refocus on Storyspace-as-a-service/Twine-y ends. Although I'll inevitably end up doing the web-publishing stuff because there's no possible utility for that really.
Making big-picture statements is of course ridiculous right now, as I attempt to get a nice, Cohost-esque tags-editing experience without the benefit of React. It's enraging that there isn't already a free web component out there that works the way I want. I can either tool around on this ambiguously-licensed SAP thing that's all in fucxking TypeScript, attempt to port the Downshift library that Cohost uses from React to vanilla, or just light my free time on fire and roll my own. booooooooo
Did you know: I've never written hypertext fiction unless you count eensy little fragments of Inform 7? Nonfiction all the way.
And then I started doing it essentially server-side like everything else I've been doing. and it's going fine. insert shruggy emoji guy
It's getting to where I have the itch to come up with an abstraction for the take-a-browser-action, have-the-server-do-stuff-and-make-a-render, place-the-render process. This would probably be a mistake given that the framework I'm using has its eyes on electric, which has the much better structure of treating the whole thing as a compiler problem. I have quibbles about the exact expression of the idea but it's cool. It reminds me (and that's all it does!) of the Spritely stuff, which I'm keeping a close eye on.
