https://arran4.github.io/blog/tags/filesystem/Recent content in filesystem on Arrans Technical blogHugo -- gohugo.ioentechnicalblog123@arran4.com (Arran Ubels)technicalblog123@arran4.com (Arran Ubels)Arran Ubels. This work is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by-sa/4.0/">Creative Commons Attribution-ShareAlike 4.0 International License</a>.Sun, 16 Aug 2026 14:32:00 +1000https://arran4.github.io/blog/post/2026/037-walking-template-filesystems/Sun, 16 Aug 2026 14:32:00 +1000technicalblog123@arran4.com (Arran Ubels)https://arran4.github.io/blog/post/2026/037-walking-template-filesystems/A useful Go pattern appears whenever files are part of application composition rather than merely data on disk: accept an fs.FS, recursively discover files, give them stable logical names, validate them, and assemble them into a larger runtime object. For HTML templates, I will call the single-filesystem form walkfs and the multi-source form walkmultifs. The walking code itself is small. The interesting part is getting the Go design around it right: ownership, package dependencies, template names, collision handling, runtime overrides, function maps, testing, and application lifecycle.