Relatively minor style changes.

Author: kgodey

assets/static/style.css

@@ -1,8 +1,10 @@
 body {
-    font-family: 'Source Sans Pro', sans-serif;
+  font-family: 'Source Sans Pro', sans-serif;
+  color: #333333;
 }
-strong {
-  font-weight: 900;
+h2 {
+  font-weight: 600;
+  padding-bottom: 0.5rem;
 }
 .page-content {
   position: relative;
@@ -41,6 +43,8 @@ strong {
   border-color: #EE5B32;
   border-width: 10px;
   padding-left: 0px;
+  font-weight: 600;
+  color: #333333;
 }
 .project-idea-header {
   background-color: #fff;
@@ -60,7 +64,6 @@ strong {
 }
 .nav-item, .dropdown-item {
     font-size: 1.2em;
-    font-weight: 900;
 }
 .dropdown:hover .dropdown-menu {
     display: block;

content/community/code-of-conduct/contents.lr

@@ -1,5 +1,7 @@
 _model: page
 ---
+_template: page-with-toc.html
+---
 title: CC Open Source Code of Conduct
 ---
 body:

content/contents.lr

@@ -10,34 +10,24 @@ body:
 
 You can contribute to CC's software in a few different ways.
 
-----
-
-#### Finding bugs and suggesting features
+### Finding bugs and suggesting features
 
 Using our software (such as [the new version of CC Search](http://ccsearch.creativecommons.org/)) and letting us know how it's working for you is very helpful. General suggestions, bug reports, a request to build a new feature –  any form of feedback is excellent, no matter how small.
 
 You can send us feedback in a few different ways. If you have a GitHub account, [creating a GitHub issue](https://help.github.com/articles/creating-an-issue/) is easiest for us because that's where we track our work. If you know which GitHub repository (see [a full list here](/projects)) corresponds to the software about which you'd like to give us feedback, then please create an issue attached to that repository. If you're not sure what that means or you don't know the correct repository, please create an issue [on the creativecommons.org repository](https://github.com/creativecommons/creativecommons.org/issues). You can also send us feedback in the `#cc-usability` channel [on the CC Slack community](https://creativecommons.org/2016/10/18/slack-announcement/) or via email at `software@creativecommons.org`.
 
-----
-
-#### Contributing code
+### Contributing code
 
 Please see [Contributing Code](/contributing-code).
 
-----
-
-#### Integrating CC license metadata into your app
+### Integrating CC license metadata into your app
 
 Please see [the "Integrate" page on the CC wiki](https://wiki.creativecommons.org/wiki/Integrate).
 
-----
-
-#### Helping translate our content
+### Helping translate our content
 
 Please see [the "Translate" page on the CC wiki](https://wiki.creativecommons.org/wiki/Translate).
 
-----
-
-#### Contributing design
+### Contributing design
 
 If you'd like to improve the design of one of our tools or products, please propose your change in [one of our community forums](/community) and collaborate with a CC staff member if requested to before making any changes.

content/contributing-code/contents.lr

@@ -12,13 +12,10 @@ Here's a list of [all our current projects](/projects). We do all of our develop
 
 We are working on making sure all of our projects are documented, licensed, and have self-contained contribution guidelines. Until we finish that work, follow the checklist below before writing any code.
 
-----
-
 **Make sure that the project is ready for contribution**
 
 If the repository has no license file, code of conduct, or is missing basic documentation, please create a GitHub issue attached to that repository to set those up. We will prioritize adding these files to repositories towards which people show active interest in contributing.
 
-
 **Make sure your change will be accepted**
 
 * If you want to work on an open GitHub issue tagged "help wanted" or "good first issue", comment on it to indicate that you're working on it (so that no one else does) and submit a pull request when you're ready. No other steps are needed.
@@ -29,16 +26,12 @@ If the repository has no license file, code of conduct, or is missing basic docu
 
 When in doubt, ask a question on [one of our community forums](/community).
 
-----
-
 ## New projects
 
 We are also open to working on or hosting projects that are related to the Creative Commons licenses or general mission. Our [Google Summer of Code project ideas](/gsoc-2019/project-ideas) list is a good place to find ideas we'd like implemented. If you're interested in working on one of them, please propose it in one of our [community forums](/community) (you don't need to be a student, anyone is welcome to work on those ideas) and work out implementation details with CC staff members before you write any code. If you want to suggest a new project idea, follow the same process.
 
 In general, we'd like any new projects to use Python, WordPress/PHP, and/or JavaScript (our framework of choice is Vue.js) so that our team can help review and maintain the project.
 
-----
-
 ## General best practices
 
 No matter what kind of project you're working on, these are good guidelines to follow

templates/layout.html

@@ -3,7 +3,7 @@
 <meta name="viewport" content="width=device-width, initial-scale=1" />
 <link rel="shortcut icon" type="image/x-icon" href="{{ '/static/favicon.ico'|url }}">
 <link href="https://stackpath.bootstrapcdn.com/bootstrap/4.2.1/css/bootstrap.min.css" rel="stylesheet" integrity="sha384-GJzZqFGwb1QTTN6wy59ffF1BuGJpLSa9DkKMp0DgiMDm4iYMj70gZWKYbI706tWS" crossorigin="anonymous">
-<link href="https://fonts.googleapis.com/css?family=Source+Sans+Pro" rel="stylesheet">
+<link href="https://fonts.googleapis.com/css?family=Source+Sans+Pro:400,700" rel="stylesheet"> 
 <link rel="stylesheet" href="{{ '/static/style.css'|url }}">
 <script src="https://code.jquery.com/jquery-3.3.1.min.js" integrity="sha256-FgpCb/KJQlLNfOu91ta32o/NMZxltwRo8QtmkMRdAu8=" crossorigin="anonymous"></script>
 <script src="https://cdnjs.cloudflare.com/ajax/libs/popper.js/1.14.6/umd/popper.min.js" integrity="sha384-wHAiFfRlMFy6i5SRaxvfOCifBUQy1xHdJ/yoi7FRNXMRBu5WHdZYu1hA6ZOblgut" crossorigin="anonymous"></script>
@@ -75,7 +75,7 @@
       <div class="col-9 content-wrap">
         <div class="page py-3">
           <a name="top"></a>
-          <h1 class="page-title pb-3 mb-4"><strong>{% block header %}{{ this.title }}{% endblock %}</strong></h1>
+          <h1 class="page-title pb-3 mb-4">{% block header %}{{ this.title }}{% endblock %}</h1>
           {% block body %}{% endblock %}
           <a id="back-to-top" href="#top" class="btn btn-dark btn-sm" role="button">Back to top</a>
         </div>