I'll have to think about that. It currently uses path parameters from the julienschmidt/httprouter router implementation, which I think are pretty important. How would you expect to define and receive path parameters?
Passing the parameters from the handler to the template could be left to the user of the library.