frameDock bloghttps://www.framedock.app/blog/Tutorials, build workflows and product updates from frameDock.en What a SHA-256 file manifest proves, and what it doesn'thttps://www.framedock.app/blog/file-manifest/https://www.framedock.app/blog/file-manifest/Thu, 15 Oct 2026 00:00:00 GMTBuild workflowsEvery frameDock build is archived with a manifest of file sizes and hashes. Here is what that tells a tester, and the three things it cannot tell them. Read a failed build from the first actionable errorhttps://www.framedock.app/blog/first-actionable-error/https://www.framedock.app/blog/first-actionable-error/Thu, 15 Oct 2026 00:00:00 GMTTroubleshootingEngine logs bury the cause under the consequences. How to use frameDock's raw log and setup checks to find what actually failed, fix it and retry safely. Your first verified build, step by stephttps://www.framedock.app/blog/first-verified-build/https://www.framedock.app/blog/first-verified-build/Thu, 15 Oct 2026 00:00:00 GMTTutorialsFrom a game project folder to an artifact you have checked and played. The shortest path through frameDock setup, with what each step should show. Completed, inspected, prepared, live: four states of a buildhttps://www.framedock.app/blog/four-build-states/https://www.framedock.app/blog/four-build-states/Thu, 15 Oct 2026 00:00:00 GMTRelease preparationA green build is not a shipped game. Why frameDock records a completed build, an inspected artifact, a prepared destination and a live release separately. frameDock 2026.1.1 for Windows and Linuxhttps://www.framedock.app/blog/public-test-build-2026-1-1/https://www.framedock.app/blog/public-test-build-2026-1-1/Thu, 15 Oct 2026 00:00:00 GMTProduct updatesframeDock 2026.1.1 installers for Windows 11 x64 and Ubuntu 24.04 LTS x64, and what changed in this release.