# Changelog Docs: Follow-Up After Four Months > Source: > Published: 2026-10-07 11:12:57+00:00 In a [previous post](https://dev.to/alexiskypridemos/changelog-vs-narrative-documentation-a-real-world-test-1kck), I tested a changelog-driven approach to documentation using a real open source project, the [Trongate PHP framework](https://trongate.io). The open questions then were: Answering those questions: It seems like the framework maintainers have hit on an automated workflow that works for them. Their AI assistant, [Grady](https://github.com/grady-trongate), has updated the changelog with each of the 17 releases since I published the previous article on June 9th, 2026, without apparent human intervention. The only exceptions were a couple of releases in early to mid July, for which I [updated the changelog manually](https://github.com/trongate/trongate-framework/pull/246). A writer's gripe: while clearly timely and hopefully effortless for the maintainers, the AI is wordy. Whereas I pictured the changelog as a series of bullet *points* of about a line or so, the AI defaults to bullet *paragraphs*. I realized "Will users find it useful?" was an ambitious question, and I have no good way to measure to that. I'm open to suggestions. I searched for "changelog" on [Trongate's forums](https://trongate.io/forums/search_results/Sd29L6y2DsykQ5bY), but none of the results were a user reaction. The latest framework release was on [September 27, 2026](https://github.com/trongate/trongate-framework/pull/275), but the docs repo has not been updated since [August 25, 2026](https://github.com/trongate/trongate-docs/commit/99716a16c75e1ad614cd56bc39bc8865bf9578a3). A one-month documentation lag for an open source project is, I would argue, hardly mission critical. However, I think this goes toward proving my point: long, narrative documentation does not lend itself to being updated at the typical rate of change of most software projects. This wasn't a question four months ago, but after 17 releases, I wondered if the [README I wrote in April](https://github.com/trongate/trongate-framework/commit/22baa63c3234148302b5af3c8377bd8b556a0d94), and which hasn't been updated since, still works. It does. I tested it again today, October 7, 2026, and the instructions still work, which, in my humble opinion, proves one of my other points: you want to keep the documentation primitive and deliberately **not all-inclusive** so that it remains reasonably accurate and future-proof, enduring multiple future releases with **zero maintenance**. For example, navigating to the local Trongate installation's index page is a different experience today than it was in June. However, the instructions don't reference that page. Instead, they say to go to `http://localhost/trongate/demo`. A cheap writer's trick, but it works.