Here we are again, anonymous Internet denizen. You, me, and 1GAM, starting up a third year of this delightful madness. I am powerless to resist the call of ongoing personal challenge, so here we go.
This part's pretty straightforward to explain - it's the thing you're looking at. The basic layout remains the same, but I finally learned about responsive design and reworked the whole site to adapt cleanly to various resolutions. The list of projects is finally an actual data structure, so now there are views that sort them by month, or by type, or release date. Tags are visible, games designed for jams are labeled as such, and various other little niceties have been added. Should work better for me, take less effort to maintain, and display much more cleanly on phones and tablets and whatnot. All set for 12 more projects. Woo!
Entweedle was my first experiment in Twine 2 custom story formats, and it serves precisely one purpose. Some of my previous projects have involved creating a story script in Twee 1.x, exporting it to twee source, and parsing that source in a Unity project. I could use Twine as a visual script editor, and then still have the flexibility of a full development environment. Based on the feedback I've gotten on those projects, I'm not the only one.
However, Twine 2 recently came out of alpha/beta into full release, and there's apparently no option to create a twee source file representation of a story. So that's where I started, and before long I had Entweedle. I hope my made-up word is sufficiently evocative of its purpose, but to be clear, it's a story format that converts a Twine 2 story to a twee source file. Since Twine 2 creates HTML exports, what Entweedle actually does is create a story file that has only one visible element, which contains a twee-format conversion of the story's passages. Just copy and paste that into the text editor of your choice, and that should be all you need.
This may be the very nichest of niche needs, but if by some chance you need to be able to export a Twine 2 story to twee, hopefully I've got you covered. The link to my Twine 2 projects page is below.
Illume on the other hand is a bit more complicated. With Entweedle working, I was playing around with ideas for something more complex, and eventually I landed on the idea of a proofing format to improve the reviewing options for someone editing a Twine story, particularly if that person is not the author.
I have more info over on my new Twine Projects page, but the short version is that Illume provides an interface where an editor can review each passage of a Twine story, flag them as reviewed/unreviewed individually, and make changes in-place in the passage viewer. Changes are displayed in a real-time diff format so you can always see what you've changed, and you can revert changes per-passage if needed. You can filter the passage list in various ways, and when you're done, you can export a change list that details every edit made, passage by passage, also in diff format for easy review.
The idea was that it provides a focused editing environment outside of Twine, and because the "illuminated" version of your story can be saved to a file, as can the change list created by the editor, you can easily get well-formatted and easily-reviewed edits from an editor who isn't a developer of any kind, and doesn't even have to use Twine.