removed labels from building blocks files (#69)

Co-authored-by: rafapaezbas <rafa@holepunch.com>

building-blocks/autobase.md

@@ -1,7 +1,5 @@
 # Autobase
 
-<mark style="background-color:blue;">**experimental**</mark>
-
 Autobase is used to automatically rebase multiple causally-linked Hypercores into a single, linearized Hypercore. The output of an Autobase is 'just a Hypercore', which means it can be used to transform higher-level data structures (like Hyperbee) into multiwriter data structures with minimal additional work.
 
 > Although Autobase is still under development, it finds application in many active projects. Keet rooms, for example, are powered by Autobase! This is a testament to the potential of Autobase, and we are excited to see what else it can achieve.

building-blocks/hyperbee.md

@@ -1,7 +1,5 @@
 # Hyperbee
 
-<mark style="background-color:green;">**stable**</mark>
-
 Hyperbee is an append only B-tree based on [`Hypercore`](hypercore.md). It provides a key/value-store API, with methods for inserting and getting key-value pairs, atomic batch insertions, and creating sorted iterators. It uses a single Hypercore for storage, using a technique called embedded indexing. It provides features like cache warmup extension, efficient diffing, version control, sorted iteration, and sparse downloading.
 
 > As with the Hypercore, a Hyperbee can only have a **single writer on a single machine**; the creator of the Hyperdrive is the only person who can modify it as they're the only one with the private key. That said, the writer can replicate to **many readers**, in a manner similar to BitTorrent.

building-blocks/hypercore.md

@@ -1,7 +1,5 @@
 # Hypercore
 
-<mark style="background-color:green;">**stable**</mark>
-
 Hypercore is a secure, distributed append-only log built for sharing large datasets and streams of real-time data. It comes with a secure transport protocol, making it easy to build fast and scalable peer-to-peer applications.
 
 Notable features include:

building-blocks/hyperdht.md

@@ -1,7 +1,5 @@
 # HyperDHT
 
-<mark style="background-color:green;">**stable**</mark>
-
 The DHT powering Hyperswarm and built on top of [dht-rpc](https://github.com/mafintosh/dht-rpc). The HyperDHT uses a series of holepunching techniques to ensure connectivity works on most networks and is mainly used to facilitate finding and connecting to peers using end-to-end encrypted Noise streams.
 
 In the HyperDHT, peers are identified by a public key, not by an IP address. A public key can be connected regardless of where the peers are located, even if they move between different networks.

building-blocks/hyperdrive.md

@@ -1,7 +1,5 @@
 # Hyperdrive
 
-<mark style="background-color:green;">**stable**</mark>
-
 Hyperdrive is a secure, real-time distributed file system designed for easy P2P file sharing. We use it extensively inside Holepunch; apps like Keet are distributed to users as Hyperdrives, as is the Holepunch platform itself.
 
 Notable features include:

building-blocks/hyperswarm.md

@@ -1,7 +1,5 @@
 # Hyperswarm
 
-<mark style="background-color:green;">**stable**</mark>
-
 Hyperswarm helps to find and connect to peers announcing a common 'topic' that can be anything. Using Hyperswarm, discover and connect peers with a shared interest over a distributed network. For example, we often use Hypercore's discovery key as the swarm topic for discovering peers to replicate with.
 
 Hyperswarm offers a simple interface to abstract away the complexities of underlying modules such as [HyperDHT](hyperdht.md) and [SecretStream](../helpers/secretstream.md). These modules can also be used independently for specialized tasks.

lib/docs-viewer.js

@@ -86,6 +86,10 @@ customElements.define('docs-viewer', class extends HTMLElement {
         #stability-indexing + p + p + table td:nth-child(2) {
           text-align: left
         }
+
+        .pear-api-label {
+          font-size: 15px;
+        }
       </style>
       <div id="panel" class="${lightMode ? 'light' : ''}"><slot></slot></div>
     </div>

reference/api.md

@@ -1,4 +1,4 @@
-# Application Programming Interface (API) <mark style="background-color: #8484ff;">**experimental**</mark>
+# Application Programming Interface (API) <mark class="pear-api-label" style="background-color: #8484ff;">**experimental**</mark>
 
 The Pear API enables applications to interact with Pear platform features.
 

reference/cli.md

@@ -1,4 +1,4 @@
-# Command Line Interface (CLI) <mark style="background-color: #8484ff;">**experimental**</mark>
+# Command Line Interface (CLI) <mark class="pear-api-label" style="background-color: #8484ff;">**experimental**</mark>
 
 The Command Line Interface is the primary interface for Pear Development.