customizing GitHub pages

Author: JamesMessinger

_config.yml

@@ -1,3 +1 @@
 theme: jekyll-theme-architect
-markdown:    kramdown
-highlighter: pygments

assets/css/style.scss

@@ -0,0 +1,29 @@
+---
+---
+
+@import "{{ site.theme }}";
+
+
+// Override the theme's two-column layout with a one-column layout
+section#main-content {
+  float: none;
+  width: auto;
+}
+
+aside#sidebar {
+  display: block;
+  float: none;
+  clear: both;
+  width: 100%;
+  background: none;
+  border-top: solid 1px #2f74c2;
+  min-height: 0;
+  margin-top: 10em;
+  padding: 2em;
+}
+
+
+// Make the code samples look better
+.highlight {
+  background-color: white;
+}

docs/exports/Resource.md

@@ -52,6 +52,7 @@ The resource's data.  This can be any value that is serializable as JSON, such a
 
 Properties
 -----------------------
+
 | Property Name       | Data Type               | Description
 |:--------------------|:------------------------|:-------------
 | `collection`        | string       | The resource's collection path.  This property can be an empty string, if the resource is at the root of your API.<br><br> The collection path should always begin with a forward slash and should _not_ end with one.  The `Resource` constructor automatically handles this normalization.  For example, "pets/" becomes "/pets".

docs/middleware/mock.md

@@ -95,6 +95,7 @@ But what if your API has a path _without_ a `GET` operation?  Or what if your `G
 This is where the [CRUD](https://en.wikipedia.org/wiki/Create,_read,_update_and_delete) happens.  Each HTTP method corresponds to a CRUD action, though the action varies depending on whether this is a resource operation or a collection operation.
 
 ##### Resources
+
 | HTTP Method | CRUD action
 |:------------|:-------------
 | `GET`       | Returns the resource.  If no data exists, then an [HTTP 404 (Not Found)](http://httpstatusdogs.com/404-not-found) error is sent.
@@ -106,6 +107,7 @@ This is where the [CRUD](https://en.wikipedia.org/wiki/Create,_read,_update_and_
 | `OPTIONS`   | `OPTIONS` is usually reserved for CORS preflight requests.  If you're _not_ using the [CORS middleware](CORS.md), then `OPTIONS` is treated the same as `GET`
 
 ##### Collections
+
 | HTTP Method | CRUD action
 |:------------|:-------------
 | `GET`       | Returns all resources in the collection.  If your API has `query` parameters, they can be used to filter the results (e.g. _/pets?age=4&type=dog_)