Structuring Pollen libraries

[basus]

As I've been using Pollen to build my website, I've been gradually building up a small library tag functions. They're mostly for the standard HTML5 tags, but also for the Bootstrap framework. I was wondering if there's a good way to structure these so that I can (1) re-use them across projects and maybe (2) release them to other Pollen users who might find them helpful. Currently they are a couple of submodules in my top-level pollen.rkt file.

[otherjoel]

The most polished way would be to create a package and include Scribble documentation and make it available on the package server.

But if you simply make a GitHub repo with a good README and your code is well-commented, you could start by just creating one or more .rkt files that people can copy into their own projects.

[mbutterick]

Or maybe just release the source code for the whole project? Bootstrap is popular and I’m sure fellow Bootstrap lovers would enjoy seeing how it can be automated via Pollen.