TL;DR
- Publishing to a Webflow collection from Hi, Moose now loads that collection's required fields up front and asks you to fill them in before the push, instead of letting Webflow reject the draft at the last second.
- Successful publishes no longer send an inbox notification; failures still do, so a message from the inbox now means something needs you.
- AEO audits exported from the library now keep the full Hi, Moose PDF report theme instead of losing their formatting on the way out.
- Asking for an AEO audit in chat now starts one more reliably.
- The Grav connector picked up bug fixes and some quiet hardening, now at version 0.1.1.
Webflow has opinions about fields
Every Webflow collection can define its own required fields. A blog collection might insist on a category. A case-study collection might insist on a client name. The collection knows what it wants, and until yesterday, Hi, Moose found out the hard way: you staged a draft, hit publish, and Webflow bounced it because a field only that collection cares about was sitting empty.
Now the app reads the collection's schema before publishing and shows you the required fields it can't fill on its own. You complete them inside Hi, Moose, then the push goes through in one motion. Less back-and-forth, and no more guessing which field Webflow was sulking about.
While we were in there, we also cleared out an older pile of Webflow site-selection code that nothing used anymore. Nobody will notice, which is the point.
The inbox learns when not to talk
Until this update, every successful publish dropped a note in your inbox. That sounds helpful and mostly isn't. If you publish five drafts and all five work, you get five messages telling you things went fine, and the one failure that matters is buried under four rounds of applause.
So we turned the applause off. A publish that works just works. A publish that fails still lands in your inbox, with the details. The inbox only barks when there's something at the door.
PDF exports keep their coat on
AEO audits have a proper report theme in the app: the layout, the scores, the recommendations, all dressed the way we intended. But export one from the library and it used to come out plain, like it got caught in the rain on the way to the client.
Fixed. Audits exported from the library now keep the full Hi, Moose report theme, so the PDF you hand to a client looks like the report you saw on screen.
Smaller things
Asking for an AEO audit in chat now triggers one more reliably. Before, certain phrasings would get you a thoughtful answer about audits rather than an audit, which is a very dog move, honestly. Asked to fetch, described the ball instead.
The Grav connector got a round of bug fixes and security hardening and is now at 0.1.1. Nothing you need to change on your end.
And the marketing site's download links now point at the latest builds, so a fresh download gets you the current version instead of a slightly older one.
FAQ
Do I have to fill in Webflow fields every time I publish?
Only the fields your collection marks as required that the draft doesn't already cover. Hi, Moose reads the requirements from the collection itself, so you see exactly what that collection needs and nothing extra.
Will I still know when a publish fails?
Yes. Failed publishes still send a notification to your inbox with details. Only the success notifications were removed, because a working publish doesn't need an announcement.
What changed about exported AEO audit PDFs?
Audits exported from the library now keep the Hi, Moose report theme, including the layout and styling you see in the app. Before this fix, exports could come out as plain, unthemed documents.
What was updated in the Grav connector?
Bug fixes and security improvements, released as version 0.1.1. There is nothing you need to reconfigure; existing Grav connections keep working as before.
The one who's under the desk for all of it.
