fix(jiva): broken link on to an image on v1.0.0 (#780)

Signed-off-by: isamrish <[email protected]>
openebs-archive · Apr 24, 2020 · c1969cd · c1969cd
1 parent 5a65d71
commit c1969cd
Show file tree

Hide file tree

Showing 5 changed files with 47 additions and 47 deletions.
diff --git a/docs/assets/Longhorn-blog-latest.png → docs/assets/Longhorn_blog.png b/docs/assets/Longhorn-blog-latest.png → docs/assets/Longhorn_blog.png
diff --git a/docs/jiva.md b/docs/jiva.md
@@ -22,7 +22,7 @@ The following content is directly taken from Rancher's LongHorn [announcement do
 
 ------
 
-Jiva replicas are built using Linux sparse files, which support thin provisioning. Jiva does not maintain additional metadata to indicate which blocks are used. The block size is 4K. When you take a snapshot, you create a differencing disk. As the number of snapshots grows, the differencing disk chain could get quite long. To improve read performance, Jiva, therefore, maintains a read index that records which differencing disk holds valid data for each 4K block. In the following figure, the volume has eight blocks. The read index has eight entries and is filled up lazily as read operation takes place. A write operation resets the read index, causing it to point to the live data. ![Longhorn read index](/docs/assets/Longhorn-blog-latest.png)
+Jiva replicas are built using Linux sparse files, which support thin provisioning. Jiva does not maintain additional metadata to indicate which blocks are used. The block size is 4K. When you take a snapshot, you create a differencing disk. As the number of snapshots grows, the differencing disk chain could get quite long. To improve read performance, Jiva, therefore, maintains a read index that records which differencing disk holds valid data for each 4K block. In the following figure, the volume has eight blocks. The read index has eight entries and is filled up lazily as read operation takes place. A write operation resets the read index, causing it to point to the live data. ![Longhorn read index](/docs/assets/Longhorn_blog.png)
 
 
 

diff --git a/website/siteConfig.js b/website/siteConfig.js
@@ -51,10 +51,7 @@ const siteConfig = {
     'https://buttons.github.io/buttons.js',
     'https://cdnjs.cloudflare.com/ajax/libs/clipboard.js/2.0.0/clipboard.min.js',
     '/js/code-blocks-buttons.js',
-  ],
-  separateCss: [
-    'static/css/code-blocks',
-  ],
+  ]
 };
 
 module.exports = siteConfig;
diff --git a/website/static/css/code-blocks/code-blocks-buttons.css b/website/static/css/code-blocks/code-blocks-buttons.css
diff --git a/website/static/css/custom.css b/website/static/css/custom.css
@@ -65,7 +65,7 @@ body{
 
 /* Body */
 body {
-    color : ##262B3E;
+    color : #262B3E;
     background: #fff;
 }
 h1, h2, h3, h4 {
@@ -402,3 +402,47 @@ redoc .operation-type {
   background-color: #FEF0EB;
   border-radius: 15px;
 }
+
+
+/* CSS of "Copy" code block button on the docs */
+pre {
+    position: relative;
+  }
+
+  pre .btnIcon {
+    position: absolute;
+    top: 4px;
+    z-index: 2;
+    cursor: pointer;
+    border: 1px solid transparent;
+    color: #383030;
+    background-color: #f5f4f7;
+    height: 30px;
+    transition: all .25s ease-out;
+  }
+
+  pre .btnIcon:hover {
+    text-decoration: none;
+    background-color: #fff;
+  }
+
+  .btnIcon__body {
+    align-items: center;
+    display: flex;
+  }
+
+  .btnIcon svg {
+    fill: currentColor;
+    margin-right: .4em;
+  }
+
+  .btnIcon__label {
+    font-size: 11px;
+  }
+
+  .btnClipboard {
+    right: 1px;
+    border-radius: 4px;
+    padding: 0 8px;
+  }
+
Original file line number	Diff line number	Diff line change
Expand Up		@@ -22,7 +22,7 @@ The following content is directly taken from Rancher's LongHorn [announcement do

		------

		Jiva replicas are built using Linux sparse files, which support thin provisioning. Jiva does not maintain additional metadata to indicate which blocks are used. The block size is 4K. When you take a snapshot, you create a differencing disk. As the number of snapshots grows, the differencing disk chain could get quite long. To improve read performance, Jiva, therefore, maintains a read index that records which differencing disk holds valid data for each 4K block. In the following figure, the volume has eight blocks. The read index has eight entries and is filled up lazily as read operation takes place. A write operation resets the read index, causing it to point to the live data. ![Longhorn read index](/docs/assets/Longhorn-blog-latest.png)
		Jiva replicas are built using Linux sparse files, which support thin provisioning. Jiva does not maintain additional metadata to indicate which blocks are used. The block size is 4K. When you take a snapshot, you create a differencing disk. As the number of snapshots grows, the differencing disk chain could get quite long. To improve read performance, Jiva, therefore, maintains a read index that records which differencing disk holds valid data for each 4K block. In the following figure, the volume has eight blocks. The read index has eight entries and is filled up lazily as read operation takes place. A write operation resets the read index, causing it to point to the live data. ![Longhorn read index](/docs/assets/Longhorn_blog.png)



Expand Down