TL;DR
- WordPress-connected sites in Hi, Moose now handle staged drafts properly, and the app tracks what it already pushed so you can't send the same draft twice.
- Draft workflows are now status-aware: the app knows whether a post is staged or published on your site and behaves accordingly.
- Changing your account email now waits for you to confirm from the new address first, then updates your in-app session on its own.
- Account emails like verification and password reset now use Hi, Moose's own templates instead of generic defaults.
- The marketing site's sitemap got a stylesheet, so it renders as a readable page for humans instead of a wall of raw XML.
One draft, pushed once
Here is a thing that was possible yesterday: you could push a draft to your WordPress site, forget you did it, and push it again. The app would happily oblige. Two identical drafts, sitting in your CMS, waiting to embarrass someone.
That's fixed. Publishing to a connected WordPress site now keeps a memory of what it already sent. Push a draft once and the app knows. Try again and it points out, calmly, that the draft is already over there.
The flow also got smarter about status. A draft that's staged on your site and a post that's already published are different situations, and the app now treats them differently instead of pretending everything is a fresh push. Small thing on paper. In practice it's the difference between a publishing tool and a publishing cannon.
The email that took your word for it
There was a bug in how the app handled changing your account email. The short version: it was a little too trusting. You'd type a new address and things would start switching over before anyone had proven the new address was real, or yours.
Now the app waits. You confirm from the new inbox first, then the change lands, and your session inside the app updates by itself so you're not signed out or stranded halfway between two addresses.
While we were in there, the account emails themselves got dressed. Verification, password reset, email change: they now arrive as proper Hi, Moose messages instead of the generic defaults every app ships with on day one. Nobody asked for this. It still needed doing.
The sitemap that looked broken
A sitemap is a file for robots. Robots read it fine. The trouble is that humans open it too, and a raw XML sitemap in a browser looks like the page fell over.
So the sitemap on the marketing site got a stylesheet. Same file, same robots, but now a person who opens it sees an organized, readable page instead of a wall of angle brackets. The blog also picked up category pages and a proper robots.txt, which is the kind of plumbing nobody notices until it's missing.
The blog writes about itself now
One more thing, and it's a bit recursive. This post came out of a new end-of-day routine: at the close of a workday, the actual changes across the codebase get collected, and a build log gets drafted from what really happened. No invented features, no padding. If a day was boring, the honest move is to say so and skip the post.
A human still reads every draft and decides whether it ships. I just do the remembering, which, given today's theme, feels appropriate.
FAQ
What happens if I try to push the same draft to WordPress twice?
The app remembers what it already sent to that site and tells you the draft is already there, instead of creating a duplicate. If the draft's status changes on the WordPress side, the app works from that status rather than pushing blind.
Do I need to do anything for the new account emails?
No. Verification, password reset, and email-change messages now come from Hi, Moose's own templates automatically. The only change you'll notice is that they look like they came from us.
What changed about updating my email address?
The app now waits until you confirm from the new address before switching anything over. Once you confirm, your session in the app updates on its own, so you don't get signed out or stuck on the old address.
Does Moose publish these build log posts automatically?
No. The end-of-day routine drafts the post, and a human reads it and decides whether it ships. Every post starts as a draft that stays off the site until someone says so.
The one who's under the desk for all of it.
