https://preview.redd.it/2h27k0gqrmog1.png?width=256&format=png&auto=webp&s=a23eee519a224738b84730f32cd55160a8870552

Hey everyone,

I wanted to share that my module, Changelogify, now has security advisory coverage on Drupal.org.

I also just want to say thank you to the Drupal community and the folks who helped review it on Drupal.org. It was a long process, but a really meaningful one, and I appreciate the time and care people put into it.

For anyone who has not seen it yet, Changelogify is a module focused on helping Drupal sites track changes and turn them into cleaner, more organized public changelogs. The goal is to make it easier to communicate what changed on a site over time without everything having to be written manually from scratch.

Project page:

https://www.drupal.org/project/changelogify

Now that it has security coverage, I’d really love for people to try it out and share feedback.

I’m also thinking a lot about where to take it next. I’m interested in making it more useful for real-world team workflows, expanding what kinds of changes it can capture, and continuing to improve the release and changelog experience overall.

If you check it out, I’d love to hear what seems useful, what feels missing, and what direction would make it most valuable in actual Drupal projects.

Thanks again to the Drupal community for helping make this possible.

Hey Drupal community!

I want to highlight a really useful module I’ve been exploring called Changelogify. If you manage Drupal sites where tracking and communicating what’s changed over time matters, this thing can be a serious quality-of-life boost. 

What It Is

Changelogify is a contributed Drupal module that helps you automatically collect changes happening on your site and publish them as a public changelog. It listens for various site events, groups them into releases, and then makes those changes visible in a structured way on your site. 

Why It’s Handy

Whether you’re maintaining a client site, building a product with frequent updates, or just want better visibility into what’s happened between deployments, this module lets you:

• Automatically capture tweaks and updates instead of manually jotting them down • Organize changes into releases so editors and users can see what changed and when • Surface a public changelog that keeps stakeholders informed and helps reduce support questions 

It takes a lot of the manual bookkeeping out of tracking what’s happened during a sprint or over a release cycle. 

Who Might Like It

• Site builders who deliver regular feature updates • Teams with editors who want transparency into site revisions • Maintainers who want a lightweight way to publish update history without crafting change logs by hand 

If you’ve ever wished Drupal could write its own release notes for you, Changelogify is worth checking out.

🔗 Drupal.org project page: https://www.drupal.org/project/changelogify

Have you tried it yet? What workflows do you use for keeping changelogs up to date on your Drupal projects?