contractpatch: Page layout adjustments.

Try to make sections clearer and avoid the "big monolith of text"
feeling.

www/conservancy/static/css/conservancy-bigscreen.css

@@ -10,3 +10,16 @@
     float: right;
     width: 49%;
 }
+
+#contractpatch-follow {
+    float: left;
+    width: 30em;
+    margin-right: 1.5em;
+    /* Below from .shaded, but we don't want the class on non-big screens. */
+    padding: .75em;
+    background: #F0FFB8;
+}
+
+#contractpatch-follow h2 {
+    font-size: large;
+}

www/conservancy/templates/contractpatch/index.html

@@ -15,7 +15,7 @@
 <div id="subhed">Everything is negotiable</div>
 
 <div id="contractpatch-intro" class="section">
-<h3>What is ContractPatch?</h3>
+<h2>What is ContractPatch?</h2>
 
 <p style="clear: both;">Many free and open source software developers sign employment agreements with their employers.  These agreements can affect whether and how developers contribute to FOSS—whether it’s done as part of their employment, after hours, or both.  ContractPatch is Conservancy’s initiative to give developers the words they need to make sure they can continue to do the work that’s important to them and our community.  Whether those words are negotiation tactics for the hiring process, or language to suggest for a prospective employment agreement, ContractPatch helps developers defend their own interests.</p>
 
@@ -23,7 +23,7 @@
 </div>
 
 <div id="contractpatch-follow" class="section">
-<h3>Follow ContractPatch</h3>
+<h2>Follow ContractPatch</h2>
 
 <p><a href="https://lists.sfconservancy.org/mailman/listinfo/contractpatch">Subscribe to our discussion mailing list.</a>  This is a great place to talk about issues in employment agreements, and suggest what ContractPatch might tackle next.</p>
 
@@ -31,7 +31,7 @@
 </div>
 
 <div id="contractpatch-blog" class="section">
-<h3>Blog posts</h3>
+<h2>Blog posts</h2>
 
 {% comment %}
 FIXME: