Design for job queue and settings page.

Implements design tickets #606 and #600.
`id` is required there for label to be anchored to something. (Then you can click on the label and checkbox will switch as well.) This is why I left IDs in, but made more unique with form class as prefix.

Meteor needs in current rendering engine IDs to be able to keep form elements preserved. Otherwise it would happen that it rerenders the form element and content is gone. With IDs it know how to handle them. Not sure why is that needed for checkbox though (I understand for other input boxes).