summaryrefslogtreecommitdiff
path: root/site/get
diff options
context:
space:
mode:
Diffstat (limited to 'site/get')
-rw-r--r--site/get/contributor-subscriptions.md69
-rw-r--r--site/get/index.md104
-rw-r--r--site/get/nightly-builds.md76
3 files changed, 178 insertions, 71 deletions
diff --git a/site/get/contributor-subscriptions.md b/site/get/contributor-subscriptions.md
index 64e05b5..d949bbd 100644
--- a/site/get/contributor-subscriptions.md
+++ b/site/get/contributor-subscriptions.md
@@ -1,38 +1,73 @@
-# Free LTS subscriptions for contributors
+<div class='contributor-subs-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>
-We are happy to share our work on maintaining LTS releases with everyone who works together with us.
-That's why we introduced free subscriptions for contributors.
+ <div class='banner-div'>
-## Our eligibility guidelines are as follows
+ # Free LTS subscriptions for contributors
-- **Programmers**
+ We are happy to share our work on maintaining LTS releases with everyone who works together with us.
+ That's why we introduced free subscriptions for contributors.
+
+ </div>
+
+ </div>
+ </section>
+
+ <section class='content-section'>
+ <div class='content-div'>
+ <div class='guidelines'>
+
+ ## Our eligibility guidelines are as follows
+
+ - **Programmers**
Three merged, non-trivial<fn id="non-trivial">Non-trivial is relative of course. A single typo fix is trivial, while extensive proofreading of help strings and error messages definitely counts. Contact us if not sure.</fn> pull requests to the source code within the last year.
-- **Documentation writers**
+ - **Documentation writers**
Six merged, non-trivial pull requests to the documentation within the last year.
-- **Testers**
+ - **Testers**
Six non-trivial bug reports within the last year.
-- **Evangelists**
+ - **Evangelists**
A provable<fn id="evangelists">Many people tell us that they promote VyOS among friends and collegues. It may be true, but the problem is that anyone can say that. If you want to get a subscription as an evangelist, please supply links to posts or recorded talks.</fn> track record of posting about VyOS (whether on your own site or on social media) or speaking about it at live events (offline or online). Answering on the forums also counts.
-<div id="application-form">
+ </div>
+ </div>
+ </section>
+
+
+ <section class='form'>
+ <div class='containerCustom'>
+ <div id="application-form" class='application-form'>
<script charset="utf-8" type="text/javascript" src="//js.hsforms.net/forms/v2.js"></script>
<script>
- hbspt.forms.create({
- region: "na1",
- portalId: "4129050",
- formId: "3c2d93a2-e9a9-49b8-b493-38369aa9cca5"
-});
+ hbspt.forms.create({
+ region: "na1",
+ portalId: "4129050",
+ formId: "3c2d93a2-e9a9-49b8-b493-38369aa9cca5"
+ });
</script>
-</div>
+ </div>
+
+ <hr>
+
+ <div id="footnotes"></div>
-<hr>
-<div id="footnotes"> </div>
+ </div>
+
+ </section>
+
+</div>
diff --git a/site/get/index.md b/site/get/index.md
index 10dcc58..b150005 100644
--- a/site/get/index.md
+++ b/site/get/index.md
@@ -1,48 +1,85 @@
-# Get VyOS
+<div class='get-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 has three release "channels": nightly builds, monthly snapshots, and LTS releases.
+ <div class='banner-div'>
-## Nightly builds
+ # Get VyOS
-Nightly builds are automatically produced at least once a day and include all the latest
-code (bug fixes and features) from maintainers and community contributors.
+ VyOS has three release "channels": nightly builds, monthly snapshots, and LTS releases.
-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.
+ </div>
-Nightly builds are for you if you...
+ </div>
+ </section>
-* want to help us test latest VyOS code
-* want to check whether a bug is fixed in the latest code
-* made a patch and want to test it before making a pull request
+ <section class='content-section'>
+ <div class='content-div'>
+ <div class='nightly-builds'>
-Go to the [nightly builds page](/get/nightly-builds).
+ ## Nightly builds
-## LTS release
+ Nightly builds are automatically produced at least once a day and include all the latest
+ code (bug fixes and features) from maintainers and community contributors.
-Prebuilt LTS release images are available to people and companies who help us move the project
-forward.
+ 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.
-There are many ways to get access:
+ Nightly builds are for you if you...
-* Purchase a [software access subscription](https://vyos.io/subscriptions/software/).
-* Get free access with a [support subscription](https://vyos.io/subscriptions/support/).
-* Apply for a free subscription as a [contributor](/get/contributor-subscriptions).
-* Apply for a free subscription as an
- [educational instutution](https://vyos.io/community/for-educational-institutions/),
- [non-profit](https://vyos.io/community/for-non-commercial-organizations/), or an
- [emergency service](http://vyos.io/community/for-first-responders/).
+ - want to help us test latest VyOS code
+ - want to check whether a bug is fixed in the latest code
+ - made a patch and want to test it before making a pull request
-You can also build an LTS image from the source.
+ Go to the [nightly builds page](/get/nightly-builds).
-## Legacy LTS releases
+ </div>
-As a courtesy, we offer images of legacy LTS releases. To access all available legacy LTS releases, kindly complete the form below. Upon submission, you will receive an email containing links to download the images.
+ <div class='lts'>
-<div id="application-form">
+ ## LTS release
+
+ Prebuilt LTS release images are available to people and companies who help us move the project
+ forward.
+
+ There are many ways to get access:
+
+ - Purchase a [software access subscription](https://vyos.io/subscriptions/software/).
+ - Get free access with a [support subscription](https://vyos.io/subscriptions/support/).
+ - Apply for a free subscription as a [contributor](/get/contributor-subscriptions).
+ - Apply for a free subscription as an
+ [educational instutution](https://vyos.io/community/for-educational-institutions/),
+ [non-profit](https://vyos.io/community/for-non-commercial-organizations/), or an
+ [emergency service](http://vyos.io/community/for-first-responders/).
+
+ Or you can build an LTS image from source.
+
+ </div>
+
+ <div class='legacy-lts'>
+
+ ## Legacy LTS releases
+
+ As a courtesy, we offer images of legacy LTS releases. To access all available legacy LTS releases, kindly complete the form below. Upon submission, you will receive an email containing links to download the images.
+
+ </div>
+
+ </div>
+
+ </section>
+
+ <section class='form'>
+ <div class='containerCustom'>
+ <div id="application-form" class='application-form'>
<script charset="utf-8" type="text/javascript" src="//js.hsforms.net/forms/embed/v2.js"></script>
<script>
@@ -53,4 +90,9 @@ As a courtesy, we offer images of legacy LTS releases. To access all available l
});
</script>
-</div> \ No newline at end of file
+ </div>
+ </div>
+
+ </section>
+
+</div>
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>