# Work in Progress: CMS Replacement for Foundry 3 Alloy

**URL:** <https://forums.realmacsoftware.com/t/work-in-progress-cms-replacement-for-foundry-3-alloy/46684>\
**Category:** Elements API\
**Created:** [March 11, 2025, 6:49pm UTC](https://forums.realmacsoftware.com/t/work-in-progress-cms-replacement-for-foundry-3-alloy/46684 "2025-03-11T18:49:28Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![logrunner](https://avatars.discourse-cdn.com/v4/letter/l/59ef9b/32.png) [@logrunner](https://forums.realmacsoftware.com/u/logrunner)\
**Post date:** [May 14, 2025, 3:30pm UTC](https://forums.realmacsoftware.com/t/work-in-progress-cms-replacement-for-foundry-3-alloy/46684/16 "2025-05-14T15:30:40Z")

</div>

I have just viewed this latest of the series of updates from @ben - [Dev Diary 81: Big CMS Update: New Components & Full Twig Templating!](https://forums.realmacsoftware.com/t/dev-diary-81-big-cms-update-new-components-full-twig-templating/47559)

The [Elements](https://elementsapp.io/) CMS is looking really good!

I have therefore decided to not release my Alloy Blog replacement as the [Elements](https://elementsapp.io/) CMS that @ben is developing is so much better and more flexible than what I have managed to create. I am really impressed with the use of Twig and the flexibility of the system.

I would have released mine (to help out) but given that the [Elements](https://elementsapp.io/) CMS will be arriving within a few weeks, it doesn’t now make sense to publish mine. 🙂

I am really impressed with what @ben has created. It makes much more sense to have a fully embedded CMS within [Elements](https://elementsapp.io/) and I am looking forward to getting to grips with it and modifying / replacing what I have already done. 😀

---

_[View the full topic](https://forums.realmacsoftware.com/t/work-in-progress-cms-replacement-for-foundry-3-alloy/46684)._