Autonex
In productionThe internal tool behind the Alcaldía de Cali's press releases. Publishing one on cali.gov.co used to take 20–30 minutes of manual work in the CMS. With Autonex it takes 1–2 minutes of review.
- less hands-on time per press release
- 10–20×
- median time from email to live
- 6.4 min
- press releases published in 6 weeks
- 303
- median time to build a full draft
- 25 s
Autonex times are measured from its logs. The manual time is an estimate.
- Does the busywork. Reads the Word doc, crops the cover, builds the photo gallery and fills in every field of the CMS.
- Starts before anyone asks. Press releases that arrive by email are drafted automatically, and a push notification on desktop or phone says when they're ready.
- No silent failures. Catches duplicates and anything the CMS would quietly break, and checks every step by reading the CMS back.
- People stay in control. It can't publish on its own: a person always makes the final click.
How I built it
Solo and end to end, from product design to the server it runs on: a Vue 3 + shadcn-vue interface, a Bun and Express API that drives the CMS over plain HTTP (with Playwright as a fallback), 930 automated tests, and a Cloudflare setup that keeps it private.