Incremental change is an important aspect of working on the website.
Without it, whatever ideas I have for it will forever remain useless, buried beneath dozens upon dozens of boulderous tasks. One task, in itself, is feasible; together, all at once, they may seem unbearable. Working on something this difficult is neither pleasant nor desirable.
This is why I was okay with launching something that, though complete and usable, was far from the finish line. I have lots of things to add to it, big and small. Without being able to do so incrementally, step after step, I may never be able to.
There's a distinguishable pleasure in making a big thing work, but there's also its own pleasure it making small, often unnoticable things to work. Adding small animations here and there, inconsequential to the user at large, makes the whole experience slightly more flavorful. It's what UX designers call "sparking joy": giving the user little details to enjoy while they work with the main thing, like flowers along the road you walk to work every day. None of the flowers on its own adds anything noticable to your experience, but together, all of them, provide the background you need for a fuller, more satisfying experience. It leaves a lasting feeling even if in the end you left unsatisfying with the problem you came to solve.
Things compound. It's important to recognize that. Small things, good and bad, in large masses add a lot more volume, synergetically. In Web design, in keeping your home clean, in talking to people. Unnoticable, often untracable, lasting effect that guides you without you ever noticing.
Too much of anything is bad. Finding the balance is important. The first release candidate of this website had arrows on every list-like item: in the navigation menu, on the front page, on every list of every category... Far too many arrows. I added a little code complexity – a separate style declaration for navigation-bar lists – to create a lot more visual space on the page. Now, not everything screams for your attention: only the parts that, I would argue, need it. A little more work for me, a lot more pleasure for the visitor – or, a lot less noise, depending on how you look at it.
There's still a lot of work to do for this virtual place. Some of it would require JS enabled in-browser – something that I know not everybody wants to have, what with oh so many malicious agents tracking and fingerprinting and injecting and profiling the user without their consent or notice. Most users have JS on by default, which means most users will get the features I want to present them with – like "back to last", which takes the visitor to the last page they've been reading, to the exact position they left the page on. Some portion of users – those with JS off – won't even notice the features are not there. It's called "progressive enhancement": let those who can use it use it, and fall quietly back to having none for those who can't.
There's a lot of small things, too. The favicon is still missing, for one thing. Or, today I added styles for inline arrows, which are distinct-enough from their block counterparts that you have to have a separate declaration for them. I'm not planning on using them any time soon, but they may well be of us, and it would be nice have it figured out and ready for use when I need them.