Skip to content

Commit 84fa93e

Browse files
authored
Add dark mode 😎 (#357)
* Add dark mode 😎 Signed-off-by: Mauro Morales <[email protected]> * Fix homepage downloads text Signed-off-by: Mauro Morales <[email protected]> --------- Signed-off-by: Mauro Morales <[email protected]>
1 parent 6b728f4 commit 84fa93e

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

46 files changed

+80
-104
lines changed

assets/js/kairos.js

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -97,13 +97,11 @@ function replaceContent(distroInfo) {
9797
// Insert the new alert div above the highlight element
9898
highlightElement.parentNode.insertBefore(alertDiv, highlightElement);
9999

100-
console.log(onlyDistros[0])
101100
const availableDistro = getSelectValueFromText(onlyDistros[0].replace(/\+/g, ' '));
102-
console.log(availableDistro)
103101
newDistroInfo = availableDistro.split(';');
104102
}
105103

106-
const preTags = highlightElement.querySelectorAll('pre');
104+
const preTags = highlightElement.querySelectorAll('code');
107105
const aTags = highlightElement.querySelectorAll('a');
108106

109107
const elements = [...preTags, ...aTags];
@@ -119,8 +117,6 @@ function replaceContent(distroInfo) {
119117
metaDistroElements.forEach(e => {
120118
e.innerHTML = decodeHTML(replaceVariables(e.dataset.originalContent, newDistroInfo));
121119
});
122-
123-
Prism.highlightAll();
124120
}
125121

126122
document.addEventListener('DOMContentLoaded', () => {
@@ -133,7 +129,7 @@ document.addEventListener('DOMContentLoaded', () => {
133129
});
134130

135131
highlightElements.forEach(highlightElement => {
136-
const preElements = highlightElement.querySelectorAll('pre');
132+
const preElements = highlightElement.querySelectorAll('code');
137133
const aElements = highlightElement.querySelectorAll('a');
138134
const elements = [...preElements, ...aElements];
139135
elements.forEach((e, i) => {

assets/scss/_styles_project.scss

Lines changed: 2 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -700,6 +700,7 @@ footer {
700700
height: 100%;
701701
box-shadow: none;
702702
font-family: 'NOTO SANS';
703+
color: black;
703704
}
704705

705706
.download-cards > div > div:first-child {
@@ -1480,23 +1481,10 @@ footer {
14801481
}
14811482
}
14821483

1484+
@import 'td/code-dark';
14831485
// load variables_project
14841486
@import "variables_project";
14851487

1486-
.alert-primary {
1487-
background-color: #edf1ff;
1488-
border-color: #4c7bd7;
1489-
1490-
.alert-heading {
1491-
color: #4c7bd7;
1492-
}
1493-
}
1494-
.alert-info {
1495-
.alert-heading {
1496-
color: #71b7b1;
1497-
}
1498-
}
1499-
15001488
// center the distro select vertically
15011489
.distro-select-wrapper {
15021490
display: flex;

assets/scss/_variables_project.scss

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,4 +42,4 @@ a:hover {
4242

4343
#basics-blade a {
4444
color: #EE5007;
45-
}
45+
}

content/en/docs/Advanced/after-install.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ To install [system-upgrade-controller](https://github.com/rancher/system-upgrade
3939
kubectl apply -f https://github.com/rancher/system-upgrade-controller/releases/download/{{< system-upgrade-controller-version >}}/system-upgrade-controller.yaml
4040
```
4141

42-
{{% alert title="Note" %}}
42+
{{% alert title="Note" color="success" %}}
4343

4444
Several roll-out strategies can be used with `system-upgrade-controller` which are not illustrated here in this example. For instance, it can be specified in the number of hosts which are running the upgrades, filtering by labels, and more. [Refer to the project documentation](https://github.com/rancher/system-upgrade-controller) on how to create efficient strategies to roll plans on the nodes. In the example above, the plans are applied to every host of the cluster, one-by-one in sequence.
4545

content/en/docs/Advanced/build.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ linkTitle: "Build"
44
weight: 5
55
---
66

7-
{{% alert title="Note" %}}
7+
{{% alert title="Warning" color="warning" %}}
88

99
This page is a work in progress!
1010
The feature is experimental and API is likely going to be subject to changes, don't rely on it yet!

content/en/docs/Advanced/bundles.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -83,7 +83,7 @@ metallb:
8383
address_pool: 192.168.1.10-192.168.1.20
8484
```
8585

86-
{{% alert title="Warning" %}}
86+
{{% alert title="Warning" color="warning" %}}
8787
For both types of bundle installation (after installation, on first boot),
8888
the installation only happens once. Changing the bundle's configuration block
8989
after Kairos installation is complete, will not have any effect.

content/en/docs/Advanced/livelayering.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -68,7 +68,7 @@ For example, a bundle can be defined as a naked container image containing only
6868
Consider the following Dockerfile to create an extension which adds `/usr/bin/ipfs` to the system:
6969

7070

71-
{{% alert title="Note" %}}
71+
{{% alert title="Note" color="success" %}}
7272
Note that systemd extensions require an extension-release file, which can be used to validate different aspects of the system being run.
7373

7474
If you don't want to limit to a single OS, you can use the special key `_any` but keep in mind that this is only available in systemd versions 252+.

content/en/docs/Advanced/sys-extensions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ Then you can use the `systemd-repart` tool to create the sysext image:
5757
$ systemd-repart -S -s SOURCE_DIR NAME.sysext.raw --private-key=PRIVATE_KEY --certificate=CERTIFICATE
5858
```
5959

60-
{{% alert title="Warning" %}}
60+
{{% alert title="Warning" color="warning" %}}
6161
Note that the extensions MUST have a `/usr/lib/extension-release.d/extension-release.NAME` file in which the NAME needs to match the sysext NAME (extension is ignored). This is an enforcement by systemd to ensure the sysext is correctly identified and some sanity checks are done with the info in that file.
6262
{{% /alert %}}
6363

content/en/docs/Architecture/network.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ To address these challenges, Kairos provides an easy and robust solution for dep
1414

1515
In this document, we will examine the advantages of using Kairos to deploy Kubernetes clusters at the edge, and how p2p technology facilitates self-coordination for a zero-touch configuration experience. We will also explore how Kairos' highly adaptable and container-based approach, combined with an immutable OS and meta-distribution, makes it an excellent choice for edge deployments.
1616

17-
{{% alert title="Note" %}}
17+
{{% alert title="Note" color="success" %}}
1818
You can also watch our [Kairos and libp2p video]({{< relref "../media/#how-kairos-uses-libp2p" >}} "Media") in the [Media Section]({{< relref "../media" >}} "Media")
1919
{{% /alert %}}
2020

content/en/docs/Development/nvidia.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ description: This page contains a reference on how to run Kairos on Nvidia Jetso
1010
Despite the Flavor you may have selected to look into the docs. The Nvidia AGX Orin only works with Ubuntu 20.04
1111
{{% /alert %}}
1212

13-
{{% alert title="Note" %}}
13+
{{% alert title="Note" color="success" %}}
1414
Please note that the following page contains only development reference. At the time of writing, we have tried porting Kairos to Jetson Nano eMMC without success. This is due to the old kernel supported (4.9), not properly working with `EFISTUB` and `U-boot` (you can see the [issue here](https://github.com/kairos-io/kairos/issues/45)). However, the steps outlined _should_ be a good reference to port Kairos to those architecture _when_ a new kernel version is available. We have tested, and have successfully booted a Jetson Nano with the 5.15 kernel, however, due to the lack of driver support, eMMC partitions are not properly recognized.
1515
{{% /alert %}}
1616

0 commit comments

Comments
 (0)