Fortunately, most systems aim for online playability (including save/restore) these days, since it’s the easiest way for less-enfranchised players (i.e. people coming across your game who don’t already have a Z-machine/TADS/etc interpreter set up to their liking) to jump in and play.
Twine, unfortunately, is not really designed for parser games. It’s straightforward to get started with, but out of the box it’s meant for choice-based games, and you have to do a lot of work to implement a command parser and an elaborate world model.
I’m a big fan of Inform 7, but its natural-language syntax isn’t for everyone. Its main goal is to optimize code readability, though, so that may be helpful if your eyesight causes problems. (The idea is that it’s easier to accurately take in “increase the score by 5” than “score += 5” when you’re skimming a long block of code.)
If you’re fond of database apps, you might also look into Dialog, which is a relation-based system inspired by Prolog. It’s relatively new to the scene (big emphasis on the “relatively”!) but I’ve found it quite straightforward to pick up compared to TADS, which is weighed down by the relics of its long history.
Or you might try Adventuron, which is explicitly designed to be easy to pick up (for use in the classroom and such). It’s also very database-like (the main part of the coding is putting in your data and the relationships between it) but the syntax is more C-like than Dialog’s.
I don’t think anyone codes to TADS Web UI these days. You don’t need to in order to make TADS games playable online. Parchment can play TADS 3 games in the browser, for example.
TADS 3 with WebUI is unnecessarily convoluted, and requires too much to get running in any capacity, and Parchment just completely skips all of that.
At of the time writing this, Parchment does lack some markup functionality (like clickable text, mono-width fonts, and centering), but I have heard that they’re currently working on getting this working for TADS 3 games.
Therefore, you could probably just make the game normally for QTads (or your preferred interpreter), and rest assured that Parchment will catch up to you later. Once the missing markup stuff is handled, it’ll just work for your game, as-is.
TADS 3 also has functionality for rewriting clickable text when it’s running in something that doesn’t support it.
What about Inform 6? It’s Object Oriented and has ample support for publishing online, where you can “spice it up” with any and all HTML related technologies.
You may check my own published works (either on itch.io or my web page) to see a fair and simple example of what’s possible.
I am going to pimp QuestJS, because I wrote it! Read about it here:
It is all in JavaScript, but if you are used to TADS, you will be fine with this. There is plenty of documentation, and your game is basically a web page, so easy to put on the web. Players can save and load games, and there are all sorts of options for the UI.
I wrote a game that was in IFComp a couple of years ago, if you want to see how it plays.
You could also consider PunyInform, which to me is even simpler than using normal Inform 6. PunyInform generates z-code files but it is possible to get them running online, though I never tried it.
The basic build of Parchment works with playing my TADS 3 compiled games online (these have a T3 extension). I haven’t yet figured out if there is a way to get the games to look as cosmetically nice as they look on my local interpreter – line spacing seems a bit funky and html center tags seem to be ignored so far. But that’s not a deal breaker for me. Thank you – I plan to code with TADS 3 since it will save me from having to learn a new system.
This is being worked on, too. At some point in the future, any games you’ve uploaded will look like they do on your local interpreter. Even if it was a deal breaker, it wouldn’t be one forever.
As a general rule when I make games with TADS: I try to make the game work well on QTADS, Parchment, a screen reader, and on a basic terminal. All the fancier output formatting is just a bonus to me, and I try not to lean into it too much.
EDIT: More importantly: Welcome aboard! It’s always fun to have another TADS 3 dev!