cutty.dev devlog #8 — pre-launch finale
T-2 to launch (June 3). This isn't a devlog about new features — it's the final review before liftoff. I'm wrapping up three things: login, content in 25 languages, and monitoring. Basically, readiness.
Login — four paths at the start
- Google, LinkedIn, X — verified, publicly working. Plus classic email + PIN, independent of any provider — no one is left without the ability to create an account.
- Facebook is paused for now. Meta requires business verification with documents that, as a solo creator, I simply don't have. Instead of leaving a button that leads to a Meta error, I turned it off cleanly — it shows "coming soon." It will return once I sort out the paperwork.
- Every production redirect checked character by character — no "localhost" tangled in the config.
25 languages — also in link previews
- Social-share images (og:image) native for all 25 languages. When someone shares cutty.dev on social media, the preview is in their language. Previously, 13 of them were just copies of the English version — now each has its own render, including Hebrew (right-to-left), Thai, Japanese, and Devanagari. Checked by eye, character by character.
- The blog translates itself. I write a post in Polish, and the site generates 25 versions locally — without sending text to an API in the US or China — and shows each reader their language.
- "Login methods" lists in the content updated for current providers.
Monitoring that actually alerts
The least pleasant discovery of the day: the health check had been failing silently for a week. Meaning, on launch day, if something stopped working, no one would know. Fixed, test alert arrived. Now the site pings itself every five minutes and screams if something is wrong.
Status as of now
Zero broken services, login covered, content in 25 languages, monitoring alive. Launch June 3, 2026. Only minor details on my side and one test I need to click myself — but the core is ready.