not a big deal, but one of those things to account for eventually.

If not serving the (semi-)static content (css etc and the media
items) through a dedicated webserver but using paste#static the
caching is bad.

It could easily be argued, that on a real deployment, these tings
should be served by a dedicated webserver. But still, the paste
based setups should give reasonable caching.

There are two items to consider:


1. mediagoblin/mgoblin\_static/ (CSS, ...)

Only layout/etc developers will change this and those will likely
use "reload" on their browsers anyway. Everybody else will only
change this when updating their install. So even thinking about
people updating and wanting a fresh look soon, at least an hour
would be good. I'd rather suggest a day.


2. media content (public\_store)

media items aren't **modified** currently. They get written once
and stay there as written. Creating a new media entry, creates a
new object id, etc. I'd say a week is good.

The size of checkboxes vary between browsers and operating systems.
In Ubuntu I can cover it almost entirely with my mouse pointer, and
on other systems they're not much larger -- Also, try it with
pointer accelleration & touchpad!

It would help greatly if the checkbox had a label that was
associated correctly with ....

Resource:
`http://www.10sharpdesign.com/accessibility/forms/3b-ii-labels-checkboxes.html <http://www.10sharpdesign.com/accessibility/forms/3b-ii-labels-checkboxes.html>`_