restyled all pages

1 files changed, 53 insertions, 23 deletions

diff --git a/site/get/nightly-builds.md b/site/get/nightly-builds.md
index 6bbbe08..06311c3 100644
--- a/site/get/nightly-builds.md
+++ b/site/get/nightly-builds.md
@@ -1,33 +1,63 @@
-# VyOS nightly builds
+<div class='nightly-builds-page'>
+  <section class='banner'>
+    <div class='containerCustom'>
+      <div class='left-shape'>
+        <img src='/img/global/shape-left.svg' />
+      </div>
+      <div class='right-shape'>
+        <img src='/img/global/shape-right.svg' />
+      </div>
 
-VyOS nightly builds are automatically produced from the `current` branch and the development branch for the LTS release,
-at least once a day.
-They include all the latest code from maintainers and community contributors.
+  <div class='banner-div'>
 
-Nightly builds are not hand-tested before upload. A basic set of automated
-[smoke tests](https://github.com/vyos/vyos-1x/tree/current/smoketest/scripts/cli) is executed
-for each build ensuring that basic functionality is working. In addition we load arbitrary
-[configurations](https://github.com/vyos/vyos-1x/tree/current/smoketest/configs) to ensure
-there are no errors during config migration and system bootup.
+  # VyOS nightly builds
 
-## Verifying image signatures
+  </div>
 
-We use [minisign](https://jedisct1.github.io/minisign/) for release signing. To learn about its advantages
-over GPG, read [signify: Securing OpenBSD From Us To You](https://www.openbsd.org/papers/bsdcan-signify.html).
+  </div>
+  </section>
 
-One obvious advantage is that you don't need to import the key anywhere, you can pass it as a command line argument.
-Once you download an image and its `.minisig` file, you can verify its integrity with this command:
+  <section class='content-section'>
+    <div class='content-div'>
+      <div class='image-signatures'>
+  
+  VyOS nightly builds are automatically produced from the `current` branch and the development branch for the LTS release,
+  at least once a day.
+  They include all the latest code from maintainers and community contributors.
 
-```
-minisign -Vm <ISO file> -P RWTclGe42GmvIX/xnNiXdigNll7NSfpYGl1rj+sEERcLgoEsse5EwAgA
-```
+  Nightly builds are not hand-tested before upload. A basic set of automated
+  [smoke tests](https://github.com/vyos/vyos-1x/tree/current/smoketest/scripts/cli) is executed
+  for each build ensuring that basic functionality is working. In addition we load arbitrary
+  [configurations](https://github.com/vyos/vyos-1x/tree/current/smoketest/configs) to ensure
+  there are no errors during config migration and system bootup.
 
-If in doubt, you can get the public key from the [nightly builds repository](https://github.com/vyos/vyos-rolling-nightly-builds/blob/main/minisign.pub).
-If you are _really_ in doubt (i.e., you have a reason to suspect that the repository and/or this website were compromised),
-you should report that to the maintainers.
+  ## Verifying image signatures
 
-Currently, we create nightly builds with GitHub Actions and store them in releases of the [vyos/vyos-rolling-nightly-builds](https://github.com/vyos/vyos-rolling-nightly-builds/releases)
-repository. Here is an auto-generated list of available builds.
+  We use [minisign](https://jedisct1.github.io/minisign/) for release signing. To learn about its advantages
+  over GPG, read [signify: Securing OpenBSD From Us To You](https://www.openbsd.org/papers/bsdcan-signify.html).
 
-## Available builds
+  One obvious advantage is that you don't need to import the key anywhere, you can pass it as a command line argument.
+  Once you download an image and its `.minisig` file, you can verify its integrity with this command:
 
+  ```
+  minisign -Vm <ISO file> -P RWTclGe42GmvIX/xnNiXdigNll7NSfpYGl1rj+sEERcLgoEsse5EwAgA
+  ```
+
+  If in doubt, you can get the public key from the [nightly builds repository](https://github.com/vyos/vyos-rolling-nightly-builds/blob/main/minisign.pub).
+  If you are _really_ in doubt (i.e., you have a reason to suspect that the repository and/or this website were compromised),
+  you should report that to the maintainers.
+
+  Currently, we create nightly builds with GitHub Actions and store them in releases of the [vyos/vyos-rolling-nightly-builds](https://github.com/vyos/vyos-rolling-nightly-builds/releases)
+  repository. Here is an auto-generated list of available builds.
+
+  </div>
+
+  <div class='available-builds' id='available-builds'>
+
+  ## Available builds
+
+  </div>
+
+  </section>
+
+</div>