Hammer for Mac - Preview 0.16.1

Products Hammer
, ,
1

:hammer: Hammer for Mac — Preview: 0.16.1

Welcome to the discussion thread for this Hammer for Mac Preview Build.

Use this space to share feedback, report issues, and discuss your experience with other testers and the team.

:magnifying_glass_tilted_left: Build Information

Version: 0.16.1

Build: 1

Release Date: 15th Dec 2025

Platform: macOS 15.0

Distribution: Private Invite Only

:sparkles: Highlights

This release introduces the Page Readiness Audit System — a comprehensive validation tool that ensures your content pages are ready for search engines and AI systems. Combined with the content publishing features from 0.16.0, Hammer now provides a complete content management and quality assurance workflow.

Page Readiness Audit System

Comprehensive page validation: The new audit system validates rendered HTML for SEO and AI compatibility, checking search hygiene, page identity, AI readability, and more. Access the audit via the audit button (checkmark seal icon) on any content entry in the Content tab.

Automatic fix suggestions: Many common issues can be fixed automatically directly from the audit view. The auto-fix system applies corrections to your source files, which you can then verify with a rebuild. This dramatically speeds up the process of getting pages ready for publication.

AI readability checks: New validation checks ensure your content is properly structured for AI systems to understand and cite. This is increasingly important as AI-powered search and assistants become more prevalent.

Page identity validation: The audit validates essential identity markers including title tags, meta descriptions, heading hierarchy, and other elements that help search engines and AI systems understand what your page is about.

Content Publishing & Management (from 0.16.0)

Publishing workflow: Content entries can now be published immediately, saved as drafts, or scheduled for future publication. Scheduled content automatically publishes when the date arrives — perfect for time-sensitive releases.

Content management UI: The new Content tab provides a centralized view for managing all your content entries. Features include status badges, date pickers for scheduling, filtering by collection and status, search, and sorting. All changes are saved directly to your content files.

AI context features: Site descriptions and collection style guides provide AI assistants (like Cursor) with natural language context about your site and content structure. Style guides help AI understand how to author content for each collection.

See Changelog - Hammer for Mac for complete list of updates in this pre-release.

:speech_balloon: Feedback & Discussion

We’d love your input on:

  • Your overall experience with this build

  • How the page readiness audit works with your content

  • Any crashes, UI issues, or unexpected behaviors

  • Feature suggestions or workflow feedback

  • How the auto-fix system handles your specific issues

  • Your experience with content publishing and scheduling workflows

:light_bulb: Tip: When reporting an issue, include:

  • Steps to reproduce

  • Expected vs. actual result

  • macOS version

  • Logs, screencasts or screenshots if possible

:package: Installation / Update Notes

  • Don’t use Dropbox sync’d folder for your Site location due to system event chaos.

  • The page readiness audit requires a successful build to analyze rendered HTML. Make sure your site builds without errors before running audits.

  • Auto-fix features modify your source files. We recommend committing your work to version control before using auto-fix, or reviewing changes after fixes are applied.

:wrench: Resources

:blue_book: Full Changelog: Changelog - Hammer for Mac

:open_book: Content Mode Documentation: Hammer for Mac Documentation

Thank you for testing!

Your feedback directly helps shape the next version of Hammer for Mac.

2

FYI, the Hammer reload seems to fail in Safari. The console says “Invalid regular expression, nothing to repeat”. Gemini tells me the ? character should be escaped. I can’t see how to change this code, so I’m posting here…

1 Like
3

I created the reload tag very early on, and then mostly used live server plugin for vs code so havent tested it so thoroughly in the wild, I’ll make a note to look into it but wouldn’t surprise me if there’s a bug there…

4

Here’s an interesting one. I had a variable in variables.html called “year”. I then added “firstYear”. Hammer then was unable to find either. After experimenting I find that if I rename the “year” to “currentYear” they both work properly again.

5

Noted, will tweak the variable name parsing logic

6

Now have my simple blog working - comes back to my comment before that it would be good to be able to control the looping in some way. Right now the order of the posts appears to be “random”. Being able to sort by a field, perhaps a date, or any random field (so I could specify an integer for ordering manually (with gaps!)). And also to be able to limit the number returned, so I could say “order by date, top 10 only”.

Apart from that, looking good. (Will be starting on a project with two collections next - way more complex site). Thanks!

1 Like
7

Another thought as I dig deeper - it would be nice to have a markdown summary so I know what can be done. And more important, it would be good to be able to tag a paragraph with a css class name somehow, so that I can highlight a block or something from the markdown. Not sure if html is allowed, but a css tag would be sufficient I think?

1 Like
8

I had further thoughts as I went to sleep last night. Sorry!

I don’t know if it already supports it, but I need to put images in the markdown texts. Ideally with formatting so I can have the image to the left as well as inline. But the ideal solution I realised was to have includes with parameters. This way I can have an include any place in the markdown that could pass in the image name or other to control the output. I figure it would be like:

## <!-- @include includes/iconimage.html params{ image="myicon.png" } --> My Title

For fancier layouts, I could have an include that started a div, and another at the end that closed the div. Obviously the actual parameter passing could be however makes sense for your needs.

Or simple HTML could be passed through - I don’t know if that is possible, but I do like the idea of using includes in the HTML even still as it allows for great flexibility.

1 Like
9

I love it, you’re having the same pre-sleep routine I have enjoyed this year. So thrilled to see you really diving in. I’d love to grab some time with you personally if that would be ok to see how you’re getting on, see how you’re using Hammer.

Meanwhile certainly taking on board these posts and will digest and see what makes sense to go into upcoming releases. Keep it coming!!!

10

I’ve already implemented sort helpers in loop tags, will be in the next release.

Works like this:

<!-- @loop post in collections.post sort="date:desc" -->
<!-- @loop post in collections.post sort="date:desc,category:asc" -->

Tried to keep it like a familiar html attribute syntax.

11

You should be able to mix and match html in the markdown, give it a try.