improve services

_config.yml

@@ -39,55 +39,60 @@ collections:
     id: services
     position: 6
     output: true
+  layer2:
+    title: Layer 2
+    id: layer2
+    position: 7
+    output: true
   nodeop:
     title: Node Operation
     id: nodeop
-    position: 7
+    position: 8
     output: true
   resources:
     title: Resources
     id: resources
-    position: 8
+    position: 9
     output: true
   glossary:
     title: Glossary
     id: glossary
-    position: 9
+    position: 10
     output: true
   tutorials-recipes:
     title: Recipes
     id: tutorials-recipes
-    position: 10
+    position: 11
     output: true
   tutorials-javascript:
     title: Javascript Tutorials
     id: tutorials-javascript
-    position: 11
+    position: 12
     output: true
   tutorials-python:
     title: Python Tutorials
     id: tutorials-python
-    position: 12
+    position: 13
     output: true
   apidefinitions:
     title: API Definitions
     id: apidefinitions
-    position: 13
+    position: 14
     output: true
   testnet:
     title: Testnet
     id: testnet
-    position: 14
+    position: 15
     output: true
   tutorials-ruby:
     title: Ruby Tutorials
     id: tutorials-ruby
-    position: 15
+    position: 16
     output: true
   tutorials-php:
     title: Ruby Tutorials
     id: tutorials-php
-    position: 16
+    position: 17
     output: true
 
 plugins:

_data/nav.yml

@@ -29,24 +29,29 @@ toc:
     url: "/services/"
     position: 4
     exclude: true
+  - title: "Layer 2s"
+    collection: "layer2"
+    url: "/layer2/"
+    position: 5
+    exclude: true
   - title: "Appbase API"
     collection: apidefinitions
     url: "/apidefinitions/"
     exclude: true
-    position: 5
+    position: 6
   - title: "Node Operation"
     collection: "nodeop"
     url: "/nodeop/"
-    position: 6
+    position: 7
     exclude: true
     top_level_section: true
   - title: "Resources"
     collection: "resources"
     url: "/resources/"
     exclude: true
-    position: 7
+    position: 8
   - title: "Glossary"
     collection: "glossary"
     url: "/glossary/"
-    position: 8
+    position: 9
     exclude: true

_layer2/_defaults.md

+---
+title:
+position:
+type:
+description:
+---

_layer2/engine.md

+---
+title: Hive Engine
+position: 1
+type:
+description:
+---
+
+About hive engine

_quickstart/choose_library.md

@@ -8,7 +8,7 @@ exclude: true
 Accessing and interacting with Hive data is easy from various options depending on your infrastructure and objectives.
 
 Building a web3 app is a breeze with the [JavaScript, check related tutorials]({{ '/tutorials/#tutorials-javascript' | relative_url }}). 
-There is also a [Python tutorials]({{ '/tutorials/#tutorials-python' | relative_url }}) available, [hive.blog]({{ '/services/#services-hive-blog' | relative_url }}), as well as many [opensource projects]({{ '/resources/#resources-overview' | relative_url }}) 
+There is also a [Python tutorials]({{ '/tutorials/#tutorials-python' | relative_url }}) available, as well as many [opensource projects]({{ '/resources/#resources-overview' | relative_url }}) 
 which could be beneficial for your Hive project.
 
 ---

_services/dhf.md

 ---
 title: DHF
-position: 5
+position: 7
 canonical_url: dhf.html
 ---
 

_services/hive.blog.md

 ---
-title: hive.blog
+title: Condenser
 position: 1
 canonical_url: hive.blog.html
 ---
 
-#### Hive.blog endpoints
+#### Condenser endpoints
 
-Hive.blog offers a few endpoints for getting common data. User profile and post JSON data is very convenient and simple by appending .json
-to your request. 
+Condenser is codename to [opensource frontend](https://gitlab.syncad.com/hive/condenser) hosted on [Hive.blog](https://hive.blog). It offers a few endpoints for getting common data. 
+User profile and post JSON data is very convenient and simple by appending .json to your request. 
 
 Getting a particular user profile JSON:
 

_services/hivesigner.md

 ---
 title: Hivesigner
-position: 2
+position: 5
 canonical_url: hivesigner.html
 ---
 

_services/imageHoster.md

 ---
 title: ImageHoster
-position: 4
+position: 3
 canonical_url: imageHoster.html
 ---
 # Definition
 
 Imagehoster is a Hive-powered image hosting and proxying service. Any image uploaded to, or proxied through, your Imagehoster has a copy stored within it. This means that the image continues to be available even if 3rd party sites go down or change their URLs. For as long as your instance of imagehoster is running the image will be available, anytime you need it.
 
-The purpose of this tool is to provide a way to host and proxy images used by [condenser](https://gitlab.syncad.com/hive/condenser#condenser) to help maintain the privacy of the authors and general users accessing the images.
+The purpose of this tool is to provide a way to host and proxy images used by Hive applications to help maintain the privacy of the authors and general users accessing the images.
 
 Using ImageHoster will help limit access to IP addresses of the general user.  It will also strip [image metadata](https://en.wikipedia.org/wiki/Exif) related to the author's geographical location.  It also helps to verify that the original author uploaded the image they intended.
 
-The ability to upload images on hive.blog was originally added in January, 2017.  Please note that this tool **does not** store any image data on the blockchain.
+Please note that this tool **does not** store any image data on the blockchain.
 
-Detaied information on Imagehoster can be found in its [repository](https://gitlab.syncad.com/hive/imagehoster/-/blob/master/README.md#imagehoster)
+Detailed information on Imagehoster can be found in its [repository](https://gitlab.syncad.com/hive/imagehoster/-/blob/master/README.md#imagehoster)
+
+Currently there are 2 independent instances of imagehoster run by community, [https://images.hive.blog](https://images.hive.blog) and [https://images.ecency.com](https://images.ecency.com).
 
 ## The API
 

_services/jussi.md

 ---
 title: Jussi
-position: 3
+position: 6
 description: A reverse proxy that forwards json-rpc requests.
 canonical_url: jussi.html
 ---

_services/videoHoster.md

+---
+title: VideoHoster
+position: 4
+canonical_url: videoHoster.html
+---
+# Definition
+
+Video hosting is a [SPK network](https://spk.network) powered video hosting and encoding service. Service built on top of IPFS and Hive to power video content generation.
+
+Currently, [3speak.tv](https://3speak.tv) and [ecency.com](https://ecency.com) utilizes this service to upload and manage videos in decentralized way.
+
+
+## The API
+
+1. [Session management](https://swimlanes.io/u/DNhPCxqYn)
+
+2. [Video & Thumbnail upload](https://swimlanes.io/u/aqmqixwiR)
+
+3. [Update information for NEWLY uploaded video](https://swimlanes.io/u/I2QLEEXWG)
+
+4. [Show videos based on Status to user](https://swimlanes.io/u/_NTeLb2Kx)
+
+5. [Update video information for existing video](https://swimlanes.io/u/TJZogAOri)
+
+6. [Update just the thumbnail of the video](https://swimlanes.io/u/90tpBBsTq)
+
+7. [Mark video as published](https://swimlanes.io/u/7xPWxOvpH)
+
+Above steps cover all APIs needed by client to integrate 3Speak/SPK network. For reference integration, [opensource Ecency](https://github.com/ecency) 
+codebase could also be utilized by app developers. 

layer2.html

+---
+title: Layer 2
+section: Layer2
+layout: default
+permalink: /layer2/
+---
+
+{% assign sorted_collections = site.collections | where:'id', "layer2" %}
+{% for collection in sorted_collections %}
+	{% assign sorted_docs = collection.docs | sort: "position" %}
+	{% for doc in sorted_docs %}
+		<section id="{{doc.id | slugify}}" class="row {{ doc.id | slugify }}">
+			<h3>
+				<a id="{{ doc.id | slugify }}">
+					{{ doc.title }}
+					{% if doc.type %}
+						<span class="endpoint {{ doc.type }}"></span>
+					{% endif %}
+				</a>
+			</h3>
+			{% if doc.description %}
+				<p class="description">{{doc.description}}</p>
+			{% endif %}
+
+			{{ doc.content | replace: "<dl>", "<h6>Parameters</h6><dl>" }}
+		</section>
+	{% endfor %}
+{% endfor %}