🤩 Created a new component for secret values to use in displaying API key
also used the same for secret automation emails that I already had
🚀 Testing all API routes before publishing
🐞 Fix an issue with status pages that happen when an incident resolved date is *before* start date
👌☝️ Read Zero to One
💅 Designing landing page & onboarding
💅 Fix UI issues
🧑🚀 finish incidents part of api
🔥 created fallback dynamic status pages
previously you had to wait for one minute for first static build, now you’ll get served a dynamic status page until the page is built for the first time (completely smooth & hidden from new customers)
🤙 call with a potential future acquirer lol
🔥 Finished the REST API for create, read, update and delete of incidents and incident updates
🚀 Working on REST API
💅 Designing new approach for landing page
💅 Fix get updates menu FOUC
🤓 Now incident titles will be colored like the incident impact
Degraded performance incidents will have yellow titles and major outage incidents in red
🤓 Add impact field for incidents
🚀 start replying to customers who had the issues that I fixed
🚀 start pushing all recent status page improvements to production
🙋🏻♂️ submit to a lot of weird directories & sites
🧐 improving how people are notified about new maintenances
📖 Read 50% of Zero to One
✨ Now uptime bars in status pages will show different colors depending on severity of the issues
previously i used to show only green (no issues that day) or orange (issues occured)
😎 Better current incident and maintenance looks
not shipped yet to status pages as i'm bundling multiple updates because i deploy to every page (1300+) separately
🔥 push typescript backend to prod
this includes a couple of bug fixes because i'm an idiot and i do different tasks on the same branch