Right now we run make assets serve but there's no need to run make assets if none of the mtimes on the assets are updated.

The assets target should specify all of the files it depends on, then it can check the mtimes on those to figure out whether it needs to recompile.

Same for go install, we can skip it if none of the files changed.

I've built several projects using the rudiments implemented here, and I am wondering what you would like to see.

For example, I could add boilerplate to handle sessions, signup, log in and log out, writing to a datastore interface.

Hey Kevin,

I suspect there's a good chance this project could be simplified, while still doing everything it's doing now, and more (like applying HTTP gzip compression of embedded static resources efficiently), by using vfsgen. Instead of go-bindata as it currently does.

Have you already considered vfsgen? Are you interested in exploring this direction?

I've created a similar but simpler project for getting started with GopherJS at https://github.com/gopherjs/gopherpen, which might be worth looking at as an example.

Let me know what you think, either way. Thanks for consideration!

If you have more than one template, you probably want them to share a header and a footer. Unfortunately that's not trivial to set up.

It would be nice to have an example showing how to do this.

No reason we can't help people do this:

The landing page of https://www.deconstructconf.com is now a single HTTP request. All images, CSS, and fonts are inlined. Zero repaints. I'm seeing 220 ms from reload keystroke to final load DOM event. It's 300 kb gzipped. Greetings, things should be simple and fast.

https://twitter.com/garybernhardt/status/956624509599019008

In my projects I prefer use nginx reverse proxy for https protocol.

What would be advantages of realizing https inside boilerplate?