New Python v2 resolve page (#597)

* Updating Data Sources pages

* first drafts of entity import

* more work on entities

* continued work

* continued work

* allow sample API key

* more work

* more work on entities

* more work

* more changes

* more changes

* split out custom entities into a separate file

* start work on Python v2 docs

* start of new Python docs

* create all pages for directory and more work on landing page

* more work

* add skeleton files

* rename old Python docs

* fix mistaken files

* fix files again

* fix more files

* remove template from PR

* changed examples to directly print responses

* move pagination out of main page and into node page

* wording change suggested by Jorge

* fixed response formatting object wording, per Jorge

* new node page

* start work on resolve

* more work

* More changes

* Finish the resolve page and reword REST resolve page

* Remove template from push

* Incorporate feedback from Christie

* fix missing s on method name

Author: kmoscoe

api/python/v2/node.md

@@ -19,6 +19,9 @@ More specifically, this API can perform the following tasks:
 - Get the values of a property for individual or multiple nodes. 
 - Get all connected nodes that are linked with individual or multiple nodes.
 
+* TOC
+{:toc}
+
 ## Request methods
 
 The following are the methods available for this endpoint. 
@@ -60,18 +63,20 @@ All request methods return a `NodeResponse` object. It looks like this:
 
 | Name      | Type   | Description                                                                  |
 | --------- | ------ | ---------------------------------------------------------------------------- |
-| data      | object | Data of the property label and value information, keyed by the queried nodes. |
+| data      | object | Data of the property label and value information, keyed by the queried nodes.  |
 | nextToken | string | A token used to query the [next page of data](#pagination), if `all_pages` is set to `False` in the query. |
 {: .doc-table}
 
 ### Response property methods
 
-In addition to the [formatting methods](index.md#response-formatting) available for all reponses classes, you can call the following methods on the `NodeResponse` object:
+You can call the following methods on the `NodeResponse` object:
 
 | Method | Description | 
 |--------|-------------|
-| nextToken | Extract the `nextToken` value from the response. See [Pagination](#pagination) below for more details |
-{: .doc-table}
+| to_dict | Converts the dataclass to a Python dictionary. See [Response formatting](index.md#response-formatting) for details. |
+| to_json | Serializes the dataclass to a JSON string (using `json.dumps()`). See [Response formatting](index.md#response-formatting) for details. |
+| nextToken | Extracts the `nextToken` value from the response. See [Pagination](#pagination) below for more details |
+{: .doc-table }
 
 ## fetch
 
@@ -95,6 +100,7 @@ fetch(node_dcids, expression, all_pages, next_token)
 
 ### Examples
 
+{: .no_toc}
 {: #fetch_ex1}
 #### Example 1: Get all incoming property labels for a given node
 
@@ -128,6 +134,7 @@ Response:
 ```
 {: .example-box-content .scroll}
 
+{: .no_toc}
 {: #fetch_ex2 }
 #### Example 2: Get one (outgoing) property value for a given node
 
@@ -164,6 +171,7 @@ Response:
 ```
 {: .example-box-content .scroll}
 
+{: .no_toc}
 #### Example 3: Get a list of all statistical variables
 
 This example gets the list of all statistical variables in the knowledge graph, by fetching all nodes that are types of the class `StatisticalVariable` and using the `<-typeOf` symbol to express the incoming relationships. Also, because of the size of the response, it enables [pagination](#pagination) to split up the response data into multiple calls.
@@ -254,6 +262,7 @@ fetch_property_labels(node_dcids, out, all_pages, next_token)
 
 ### Examples
 
+{: .no_toc}
 #### Example 1: Get all incoming property labels for a given node
 
 Get all incoming arc property labels, i.e. the property labels that are used in attached nodes, of the node with DCID `geoId/06` (California) by setting the `out` parameter to `False`. This is identical to [example 1](#fetch_ex1) of the `fetch` method.
@@ -311,6 +320,7 @@ fetch_property_values(node_dcids, properties, constraints, out, all_pages, next_
 
 ### Examples
 
+{: .no_toc}
 #### Example 1: Get one (outgoing) property value for a given node
 
 This example gets the `name` property for a given node with DCID `dc/03lw9rhpendw5`. This is identical to [example 2](#fetch_ex2) of the `fetch` method.
@@ -346,6 +356,7 @@ Response:
 ```
 {: .example-box-content .scroll}
 
+{: .no_toc}
 #### Example 2: Get multiple (outgoing) property values for multiple nodes
 
 This example gets the `name`, `latitude`, and `longitude` values for nodes `geoId/06085` and `geoId/06087`.
@@ -443,6 +454,7 @@ Response:
 ```
 {: .example-box-content .scroll}
 
+{: .no_toc}
 #### Example 3: Get DCIDs of nodes of a specific type, with an incoming relation to a node
 
 In this example, we use a [filter expression](/api/rest/v2/#filters) to specify "all contained places in
@@ -509,8 +521,6 @@ Response:
 ```
 {: .example-box-content .scroll}
 
-
-
 ## fetch_all_classes
 
 Fetches all nodes that are entity types, that is, have `Class` as their type.
@@ -530,7 +540,10 @@ fetch_all_classes(all_pages, next_token)
 
 {: .doc-table }
 
-### Example 1: Fetch all classes, with pagination
+### Examples
+
+{: .no_toc}
+#### Example 1: Fetch all classes, with pagination
 
 This example sets `all_pages` to get a [paginated response](#pagination) with a `next_token` value.