Spectralis devlog #5
—Hello again proggers—
This one’s website side, not app side. Less “watches chat and reacts,” more “stop lying to people who land on the page.” Changelogs, copy, and a pile of QoL that all needed doing at once, so they got done at once.
Cat or dog? GET /changelog
print(f”I try to make stu{2f} which {actually_updates} {2day}”)
Okay let’s get into it~
—Yap—
The website had drifted into “hardcoded strings and vibes” territory. Changelog was static, copy was doing the thing where every sentence has an exclamation point and says nothing, and a bunch of small friction points had just been sitting there unfixed because none of them were dramatic enough on their own to stop and deal with.
death by a thousand papercuts, website edition
—The Great Suffering—
1 — Changelogs Moved To The Backend
Changelog used to live as static content baked into the site itself, which meant every release meant a redeploy just to update a text block. Now it’s served from the backend, so shipping a new version updates the changelog without touching the frontend at all. Site and release process finally agree with each other.
2 — Marketing Fluff: Removed
Went through the copy and cut the stuff that existed to sound exciting instead of to say something. Fewer exclamation points, fewer vague superlatives, more actual sentences about what the thing does. Turns out “it’s fast” means more than “blazingly fast, lightning quick, revolutionary” stacked in one line.
RIP to several adjectives, you will not be missed
3 — A Bunch Of Small QoL Fixes
The kind of stuff that’s individually boring but collectively the difference between a site that feels maintained and one that doesn’t — broken anchor links, inconsistent spacing that had been “fine for now” for way too long, a couple of buttons that didn’t actually do what their label said, loading states that just weren’t there before. Nothing here gets its own numbered section because none of it deserves one, but all of it needed fixing.
4 — Site and Backend Actually Talk Now
With changelogs pulled from the backend, the website stopped being a static artifact that occasionally gets redeployed and started being an actual client of the backend it’s supposed to represent. Small architectural shift, disproportionate amount of relief.
—FAQ (no one asked these but they are here)—
Q: What is a “progger”?
A: A human programmer. You. The one who wrote “blazingly fast” unironically at some point.
Q: Why was the changelog static in the first place?
A: Because it was easy at the time and “at the time” was a while ago.
Q: Is the marketing copy gone entirely now?
A: No, just the fluff. The site still has to say what Spectralis does, it just doesn’t need six adjectives to do it.
Q: Does this affect the Discord bot or the app?
A: No, this one’s website-only. App and bot are untouched this round.
Q: What counts as a “small QoL fix” that didn’t get its own section?
A: The stuff that’s annoying to list individually but adds up to “the site feels better now.” You’ll notice it without being told what it was.
—This is the end*—
*end for now, copywriting urges permitting
CYA!!!