# Hammer for Mac - the 2025 rebirth

**URL:** <https://community.beach.io/t/hammer-for-mac-the-2025-rebirth/46>\
**Category:** Hammer\
**Tags:** hammer, swift, swiftui, product\
**Created:** [January 6, 2025, 12:17pm UTC](https://community.beach.io/t/hammer-for-mac-the-2025-rebirth/46 "2025-01-06T12:17:49Z")\
**Posts on this page:** 1\
**Showing post:** 45

<div class="post-metadata">

**Author:** ![steve](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.beach.io/steve/32/43_2.png) [@steve](https://community.beach.io/u/steve)\
**Post date:** [November 20, 2025, 9:47pm UTC](https://community.beach.io/t/hammer-for-mac-the-2025-rebirth/46/45 "2025-11-20T21:47:11Z")

</div>

Great to hear.

I think I understand the question and use-case but am probably making some assumptions about how your wife would work with the content.

As a starting point, have you seen my draft concept for content management and generation in Hammer?

> [@Concept: Hammer CMS](https://community.beach.io/t/concept-hammer-cms/86):
>
> I’ve been exploring a concept to bring content generation directly into Hammer for Mac. I’d love to open this up for discussion and collective shaping with the community. Some background: It was a long time ago that we started to explore what has become common place - the combination of headless CMS with build time compilation and static site generation and deployment to the edge via a global CDN. Our version of this many moons ago combined third party headless CMS services of the time - [C…](https://contentful.com)

I think it would answer the separation of content from templating and markup, what do you think?

I’m not clear how you would want the content \> compilation \> deployment workflow to be. I would imagine when the site is designed and built you wouldn’t want to be responsible yourself for the hammer build and export? But it also sounds like your wife wouldn’t be running Hammer to trigger compilation after making content updates in GitHub editor?

for this, it seems like having GitHub sync with Hammer cloud compilation triggered before deployment would work. That way your wife could simply edit the content and commit the change or make a PR and post on merge, GitHub will fire webhook and trigger deploy.

Will you host on Forge? If so, we can do this.

---

_[View the full topic](https://community.beach.io/t/hammer-for-mac-the-2025-rebirth/46)._