Update theme

blog/2018-06-21-making-a-wifi-enabled-smart-air-humidifier/index.md

@@ -116,4 +116,6 @@ binary_sensor:
     pin:
       number: D5
       mode: INPUT
-```
+```
+
+<BlogDiscussions/>

blog/2019-02-15-smart-doorbell-with-xiaomi-aqara-button-and-google-home/index.md

@@ -49,4 +49,6 @@ Now we need to create a handler of the Aqara button in `automations.yaml`:
   - data:
       message: "Someone near your front door"
     service: notify.push
-```
+```
+
+<BlogDiscussions/>

blog/2019-02-21-home-assistant-presence-detection-with-google-wifi/index.md

@@ -134,4 +134,6 @@ Now we can rely on that group’s state to check if there is nobody home. I’ve
     service: notify.push
 ```
 
-That is all for now. Thanks for reading.
+That is all for now. Thanks for reading.
+
+<BlogDiscussions/>

blog/2020-11-10-using-variables-as-configuration-for-home-assistant-automation/index.md

@@ -208,4 +208,6 @@ Also, this automation should be able to run in parallel to make it possible to h
 ```yaml
   mode: parallel
   max: 10
-```
+```
+
+<BlogDiscussions/>

blog/2020-12-29-bed-presence-detection-with-aqara-window-and-door-sensor-and-a-cheap-car-part/index.md

@@ -40,4 +40,6 @@ binary_sensor:
         friendly_name: "Bed occupancy"
         device_class: occupancy
         value_template: "{{is_state('binary_sensor.bed_occupancy_door_side', 'off') or is_state('binary_sensor.bed_occupancy_window_side', 'off')}}"
-```
+```
+
+<BlogDiscussions/>

blog/2021-01-06-send-and-receive-sms-in-home-assistant-with-gsm-modem/index.md

@@ -42,4 +42,6 @@ action:
 
 ![Parsing action](parse_action.png)
 
-Here we are checking for the `engine is off` text in incoming SMS to perform some action. For example, to set the value of some `input_boolean`.
+Here we are checking for the `engine is off` text in incoming SMS to perform some action. For example, to set the value of some `input_boolean`.
+
+<BlogDiscussions/>

blog/2021-01-13-adding-wifi-power-control-to-an-integrated-amplifier/index.md

@@ -105,3 +105,5 @@ switch:
 ```
 
 That’s it for today. Thanks for reading.
+
+<BlogDiscussions/>

blog/2021-01-13-building-wifi-ir-remote-control-for-any-tv-with-esp8266-wemos-d1-mini-and-esphome/index.md

@@ -237,4 +237,6 @@ Before placing our power supply inside the TV we need to make sure it is isolate
 
 So the overall picture is looking like this:
 
-![](overview.png)
+![](overview.png)
+
+<BlogDiscussions/>

blog/2021-01-15-ir-code-reader-with-esp8266-wemos-d1-mini-and-esphome/index.md

@@ -85,4 +85,6 @@ Compile, flash, open logs and start firing into our device with your IR remote.
 [17:34:51][D][remote.samsung:055]: Received Samsung: data=0xE0E020DF
 ```
 
-You can now use this data with the ESPHome [Remote Transmitter](https://esphome.io/components/remote_transmitter.html) component to build, for example, something like [this](/2021-01-13-building-wifi-ir-remote-control-for-any-tv-with-esp8266-wemos-d1-mini-and-esphome/index.md).
+You can now use this data with the ESPHome [Remote Transmitter](https://esphome.io/components/remote_transmitter.html) component to build, for example, something like [this](/2021-01-13-building-wifi-ir-remote-control-for-any-tv-with-esp8266-wemos-d1-mini-and-esphome/index.md).
+
+<BlogDiscussions/>

blog/2021-01-15-using-stepper-motor-to-control-amplifier-volume-knob/index.md

@@ -120,4 +120,6 @@ Decreasing the volume action is the same, but with negative `target`:
 service: esphome.amplifier_set_volume
 data:
   target: -50
-```
+```
+
+<BlogDiscussions/>

blog/2023-10-31-hosting-ghost-blog-on-synology-nas/index.md

@@ -119,4 +119,6 @@ You'll get an email notification on the address added here when there will be ti
 
 After certificate generation, we should open Settings on the same Certificates tab, find our domain service, and choose the newly generated certificate for it.
 
-That's it!
+That's it!
+
+<BlogDiscussions/>

blog/2023-12-19-monitor-usb-ups-connected-to-synology-nas-in-home-assistant/index.md

@@ -43,4 +43,6 @@ In your Home Assistant go to _Settings -> Devices & services_ and click the _"Ad
 
 In the configuration window that appeared you need to set your NAS's local IP address as a _Host_ and leave the _Port_ number unchanged.
 
-Hit _Submit_ and you are done.
+Hit _Submit_ and you are done.
+
+<BlogDiscussions/>

blog/2023-12-19-restart-or-shutdown-your-proxmox-node-from-home-assistant-automation/index.md

@@ -54,4 +54,6 @@ The authorization header should have the next format: `PVEAPIToken=<proxmox user
 
 You can use `shutdown` or `reboot` as a `command`.
 
-After restarting Home Assistant you will have a new service available. In our example, it would be `rest_command.spacedock_one_shutdown`. Calling it will do the trick.
+After restarting Home Assistant you will have a new service available. In our example, it would be `rest_command.spacedock_one_shutdown`. Calling it will do the trick.
+
+<BlogDiscussions/>

blog/2025-02-15-wireguard-tunnel-from-ubuntu-vps-to-homelab-through-unifi-vpn-server/index.md

@@ -105,4 +105,6 @@ And up it back with a system service, also enabling it:
 sudo systemctl start wg-quick@wg0 && sudo systemctl enable wg-quick@wg0
 ```
 
-Further interface control should be performed through `systemctl` as well like `systemctrl stop`, `systemctl restart` or `systemctl status`.
+Further interface control should be performed through `systemctl` as well like `systemctrl stop`, `systemctl restart` or `systemctl status`.
+
+<BlogDiscussions/>

blog/2025-05-21-make-one-proxmox-node-to-wol-another/index.md

@@ -98,4 +98,6 @@ Cron job line to add:
 
 ```
 @reboot sleep 30s && /usr/sbin/etherwake -i vmbr0 <mac_address>
-```
+```
+
+<BlogDiscussions/>

blog/2025-10-07-proxmox-ve-on-hetzner-dedicated-server/index.md

@@ -70,7 +70,7 @@ iface vmbr1 inet static
 
 Let's see what's going on in here.
 
-For the containers that don't require a public IP, I choose `vbmr1` bridge, set some IP from the local IP range (192.168.50.x), and use the local IP as a gateway:
+For the containers that don't require a public IP, I choose `vbmr1` bridge, set some IP from the local IP range (192.168.50.x), and use host local IP as a gateway:
 
 ![LXC local network](vmbr1.png)
 
@@ -182,4 +182,6 @@ After installing it and configuring it to use [Backblaze S3 storage](https://pbs
 ## Conclusion
 Have no idea why everyone wants to write a conclusion for each post nowadays. It looks like a forced conclusion to a school physics problem in most cases: "Solving this problem of moving trains, we found out that trains can move".
 
-Have a nice tinkering.
+Have a nice tinkering.
+
+<BlogDiscussions/>

docusaurus.config.js

@@ -102,7 +102,7 @@ const config = {
         ],
       },
       footer: {
-        style: 'dark',
+        style: 'light',
         links: [
           {
             title: 'This site sections:',

package.json

@@ -1,6 +1,6 @@
 {
   "name": "yevi-org",
-  "version": "0.2.2",
+  "version": "0.4.0",
   "private": true,
   "scripts": {
     "docusaurus": "docusaurus",

src/components/BlogDiscussions/index.js

@@ -0,0 +1,16 @@
+import styles from './styles.module.css';
+
+export default function BlogDiscussions() {
+  const Svg = require('@site/static/icons/matrix.svg').default;
+
+  return (
+    <section className={styles.blogDiscussions}>
+
+      <a className={styles.blogDiscussions_container} href="https://matrix.to/#/%23yevi-org-pub:vi.place" target='_blank'>
+        <Svg fill="currentColor" className={styles.icon} role="img" />
+        <span className={styles.linkText}>Join discussion at Matrix</span>
+      </a>
+
+    </section>
+  );
+}

src/components/BlogDiscussions/styles.module.css

@@ -0,0 +1,27 @@
+.blogDiscussions {
+  display: flex;
+  flex-direction: row;
+  justify-content: center;
+  padding: 1rem 0;
+}
+
+.blogDiscussions_container {
+  display: flex;
+  flex-direction: row;
+  flex-wrap: wrap;
+  justify-content: center;
+  align-items: center;
+}
+
+.linkText {
+  width: 12rem;
+}
+
+.icon {
+  width: 3rem;
+  height: 3rem;
+}
+
+.icon path {
+  fill: var(--ifm-link-color) !important;
+}

src/components/HomepageFeatures/styles.module.css

@@ -9,15 +9,31 @@
   padding-bottom: 1rem;
 }
 
+@media (max-width: 996px) {
+  .featureBlock {
+    --ifm-col-width: 50%;
+  }
+}
+
+@media (max-width: 500px) {
+  .featureBlock {
+    --ifm-col-width: 100%;
+  }
+}
+
 .featureSvg {
-  height: 100px;
-  width: 100px;
+  height: 60px;
+  width: 60px;
 }
 
 .featureSvg path {
   fill: var(--ifm-link-color) !important;
 }
 
+.featureBlock:hover .featureSvg path {
+  opacity: 0.7;
+}
+
 .featureLink {
   display: contents;
   color: unset;
@@ -31,4 +47,8 @@
 .featureLink:visited {
   text-decoration: none;
   color: unset;
+}
+
+.featureLink p {
+  color: var(--ifm-color-secondary-contrast-foreground);
 }

src/css/custom.css

@@ -16,7 +16,13 @@
   --ifm-code-font-size: 95%;
   --docusaurus-highlighted-code-line-bg: rgba(0, 0, 0, 0.1);
   --ifm-footer-link-hover-color: #b07ab0;
-  --ifm-link-color: var(--ifm-color-primary-lightest)
+  --ifm-link-color: var(--ifm-color-primary-lightest);
+  --ifm-global-shadow-lw: 0 1px 2px 0 #541d5428;
+}
+
+.hero--primary {
+  --ifm-hero-background-color: transparent;
+  --ifm-hero-text-color: var(--ifm-font-color-base);
 }
 
 /* For readability concerns, you should choose a lighter palette in dark mode. */
@@ -32,14 +38,6 @@
   --ifm-link-color: var(--ifm-color-primary-darker);
 }
 
-@media (max-width: 996px) {
-  .col {
-    --ifm-col-width: 50%;
-  }
-}
-
-@media (max-width: 500px) {
-  .col {
-    --ifm-col-width: 100%;
-  }
+.hero {
+  border-bottom: 2px solid var(--ifm-color-primary-opaque-2);
 }

src/theme/MDXComponents.js

@@ -0,0 +1,13 @@
+import React from 'react';
+// Import the original mapper
+import MDXComponents from '@theme-original/MDXComponents';
+//Import custom component
+import BlogDiscussions from '@site/src/components/BlogDiscussions';
+
+export default {
+    // Re-use the default mapping
+    ...MDXComponents,
+    // Map the "<BlogDiscussions>" tag to our BlogDiscussions component
+    // `BlogDiscussions` will receive all props that were passed to `<BlogDiscussions>` in MDX
+    BlogDiscussions,
+};