Why Snoopy?
I wanted to learn Go by building something I could come back to. A site generator gives me a reason to work with files, templates, and HTTP, and something useful to show for it when those pieces fit together.
I’d also like to use it for my own site. That gives me a fairly practical test for the project: how much work does it take to write a page and put it online?
Where the files go
| You write | Snoopy makes |
|---|---|
content/index.md |
output/index.html |
content/notes/hello.md |
output/notes/hello.html |
assets/site.css |
output/assets/site.css |
The layout lives in templates/default.html, and the site settings are in
snoopy.json. After a build, the files in output/ can go to a static host.
Still figuring it out
This is an early version. The preview server works, but it doesn’t watch for edits yet. There’s no front matter or plugin system either. I’d like to get a feel for using what’s here before deciding how those should fit.
I’ve kept the build notes with the example site so there’s some context for the choices in the code.