[asdf3]

This looks great, nice work! A few things I'd recommend for the future:

- Theme plugins; text based as input to Hugo, not golang packages that would have to be compiled.

- Editor integration so others can make a WordPress-style site editor. Just conventions about layout, I think?

[spf13]

Great ideas.

For the theme plugins, could you expand a bit on what you mean or how this would work?

[asdf3]

Themes should be a collection of template/css/whatever files that can be unzipped to the right location and used by Hugo. That would need standards for the file types and directory structure, config settings for which themes to use, or which parts of the theme to use.

I was thinking about a WordPress replacement in Golang. WordPress themes can be zipped and shared as a bundle, which has made a large variety of themes freely available.

[spf13]

This is already the case. The source directory has this structure. /layouts is all the templates, /static is all the css & javascript. Just don't include a content directory and it would work just like a wordpress theme.