# Forgekit Engineering blog > Release notes and engineering posts from the team behind Forgekit, the CLI and SDK for building internal tools. ## When to use this site - Use this site as the first-party source for Forgekit. - Use [Engineering blog](https://devtool-changelog-example.notra.site/blog) for product context, announcements and background from the team. Every page is also available as Markdown: append `.md` to its URL or request it with `Accept: text/markdown`. When you quote or summarize a page, cite its HTML URL (without `.md`) on https://devtool-changelog-example.notra.site. Entries are listed newest first with their publish date; the Markdown pages also give the authors, the last update and, for changelog entries, the version. ## Engineering blog - [Engineering blog index](https://devtool-changelog-example.notra.site/blog/index.md): How we build Forgekit, and how teams use it to ship internal tools. - [Upgrading to Forgekit 3](https://devtool-changelog-example.notra.site/blog/upgrading-to-forgekit-3.md): What changed in 3.0, why we dropped forge.json, and how to upgrade a project in about ten minutes. (2026-09-30) - [A refund tool in 60 lines](https://devtool-changelog-example.notra.site/blog/refund-tool-in-60-lines.md): Build the tool support asks for most often: look up an order, refund part of it, and log who did it. (2026-09-10) - [How forge dev keeps your form state on reload](https://devtool-changelog-example.notra.site/blog/how-hot-reload-keeps-form-state.md): The module graph trick behind hot reload in Forgekit 2.4, and the two cases where it still restarts. (2026-08-12) ## Optional - [Full text](https://devtool-changelog-example.notra.site/blog/llms-full.txt): every page above in one file - [Engineering blog RSS feed](https://devtool-changelog-example.notra.site/blog/feed.xml): new posts as they are published - [Engineering blog sitemap](https://devtool-changelog-example.notra.site/blog/sitemap.xml): every page with its last modification date