Cleaning up project docs, folder structure, and adding service landing page.

Author: matthewhudson

README.md

@@ -1,11 +1,97 @@
-# WebPipe Block Demos
+# WebPipe Examples
 
-In this repo we're demonstrating simple but complete example blocks. Using
-`now.sh`, Node, and the node-webpipe server module.
+> Welcome to the world's finest private collection of meticulously handcrafted
+> WebPipes.
 
-## Examples
+> This project is a single web service (available at
+> [webpip.es](https://webpip.es)) built on top of the
+> [ZEIT Now](https://github.com/zeit/now-examples) cloud platform.
 
-Try running a few client requests locally.
+\*Note: As of 6/8/2019, only NodeJS examples exist the moment. However,we should
+be able to include any Now-supported runtime.
+
+## Public Convenience API
+
+As a convenience, each example is publically available at via
+[webpip.es](https://webpip.es). You can check `now.json` for each example's HTTP
+pathname, but basically, the folder each lives in is also the HTTP pathname.
+Accordingly, you can find the `./api/parse-url` example is available via
+`https://webpip.es/parse-url`:
+
+```bash
+curl -v -X OPTIONS https://webpip.es/parse-url
+```
+
+<details>
+  <summary>Response body is the input & output block definitions.</summary>
+
+```json
+{
+  "name": "Parse URL",
+  "description": "Parse URL using WHATWG URL Standard.",
+  "inputs": [
+    {
+      "name": "url",
+      "type": "string",
+      "description": "A url to parse."
+    }
+  ],
+  "outputs": [
+    {
+      "name": "parts",
+      "type": "objects",
+      "description": "Returns the parsed URL parts."
+    }
+  ]
+}
+```
+
+</details>
+
+> _Nice things are nice._ Please be mindful and keep your _use_ & _usage_
+> responsible. It's intended to serve primarily as a hands-on demonstration for
+> newcomers.
+
+## Full Example
+
+Try running a few client requests locally. Just run `node index.js` inside the
+example folder, or `now dev` if you prefer.
+
+It may be a bit easier starting with the very minimal `calculate-square-root`
+WebPipe. That said, the examples aren't structured in any particular order or
+and don't have any sort of difficulty levels, so feel free to explore in
+whatever way feels most comfortable.
+
+```bash
+curl -v -X OPTIONS \
+  https://webpip.es/inspect-hostname-dns
+```
+
+<details>
+  <summary>Response body is the input & output block definitions.</summary>
+
+```json
+{
+  "name": "DNS Lookup",
+  "description": "Determine whether or not a hostname exists.",
+  "inputs": [
+    {
+      "name": "hostname",
+      "type": "string",
+      "description": "A hostname to lookup."
+    }
+  ],
+  "outputs": [
+    {
+      "name": "ok",
+      "type": "bool",
+      "description": "Returns true of false if lookup succeeds."
+    }
+  ]
+}
+```
+
+</details>
 
 ### DNS Lookup Block
 
@@ -15,7 +101,7 @@ to do is provide. a hostname then the block does its work to find us answer.
 
 ## Example Usage
 
-```sh
+```bash
 curl -v -X OPTIONS \
   https://webpip.es/inspect-hostname-dns
 ```
@@ -46,7 +132,7 @@ curl -v -X OPTIONS \
 
 </details>
 
-```sh
+```bash
 curl -i -X POST \
   -H "Content-Type: application/json" \
   -d '{"inputs":[{"domain":"google.com"}]}' \