@networkpro/blog 1.1.3 → 1.1.4

package/mkdocs.yml

@@ -15,14 +15,14 @@ theme:
   favicon: /favicon.svg
   palette:
     # Palette toggle for automatic mode
-    - media: "(prefers-color-scheme)"
+    - media: '(prefers-color-scheme)'
       primary: amber
       accent: yellow
       toggle:
         icon: material/brightness-auto
         name: Switch to light mode
     # Palette toggle for dark mode
-    - media: "(prefers-color-scheme: dark)"
+    - media: '(prefers-color-scheme: dark)'
       scheme: slate
       primary: amber
       accent: yellow
@@ -30,7 +30,7 @@ theme:
         icon: material/brightness-4
         name: Switch to system preference
     # Palette toggle for light mode
-    - media: "(prefers-color-scheme: light)"
+    - media: '(prefers-color-scheme: light)'
       scheme: default
       primary: amber
       accent: yellow
@@ -85,8 +85,8 @@ extra:
       link: https://netwk.pro/contact
 
 copyright: >
-  Copyright © 2025 Network Pro Strategies (Network Pro™) –
-  <a href="#__consent">Change cookie settings</a>
+  Copyright &copy; 2025 Network Pro Strategies (Network Pro&trade;) – <a
+  href="#__consent">Change cookie settings</a>
 
 plugins:
   - search
@@ -103,7 +103,7 @@ plugins:
   - tags:
       tags_file: tags.md
   - rss:
-      match_path: "posts/.*"
+      match_path: 'posts/.*'
       date_from_meta:
         as_creation: date.created
         as_update: date.updated
@@ -117,4 +117,4 @@ nav:
   - Website: https://netwk.pro
   - Contributing:
       - Code of Conduct: CODE_OF_CONDUCT.md
-      - Contribute to Network Pro™: contributing.md
+      - Contribute to Network Pro™: CONTRIBUTING.md

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@networkpro/blog",
-  "version": "1.1.3",
+  "version": "1.1.4",
   "description": "The official blog of Network Pro Strategies (Network Pro™).",
   "keywords": [
     "advisory",
@@ -18,7 +18,7 @@
   ],
   "homepage": "https://blog.netwk.pro",
   "bugs": {
-    "url": "https://github.com/netwk-pro/netwk-pro.github.io/issues"
+    "url": "https://github.com/netwk-pro/netwk-pro.github.io/issues/new/choose"
   },
   "repository": {
     "type": "git",

package/ref/README.md

@@ -29,10 +29,11 @@ You will also need to install the [mkdocs-rss-plugin].
 This the repository is a [template repository], so you can create as many forks
 of it as you like and your repository will contain only a single commit to start
 with, instead of the whole history of the template. Also, you can create a
-private repository from this template (while forks inherit the visibility settings
-from the original).
+private repository from this template (while forks inherit the visibility
+settings from the original).
 
-[template repository]: https://docs.github.com/en/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template
+[template repository]:
+  https://docs.github.com/en/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template
 
 Simply hit the `Use this template` button. You can set the specifics of your new
 repository from there.

package/src/CODE_OF_CONDUCT.md

@@ -1,13 +1,15 @@
 ---
 date:
   created: 2025-03-21
-  updated: 2025-05-30
+  updated: 2025-06-07
 title: Code of Conduct
-summary: The Contributor Covenant Code of Conduct for Network Pro's public repositories.
+summary:
+  The Contributor Covenant Code of Conduct for Network Pro's public
+  repositories.
 authors:
   - team
 tags:
-  - network-pro
+  - networkpro
   - contributing
   - code-of-conduct
 ---
@@ -20,7 +22,7 @@ tags:
 # Contributor Covenant Code of Conduct
 
 **Network Pro Strategies**  
-**Effective Date:** 3/21/2025
+**Effective Date:** June 7, 2025
 
  
 
@@ -49,8 +51,6 @@ identity and orientation.
 We pledge to act and interact in ways that contribute to an open, welcoming,
 diverse, inclusive, and healthy community.
 
-<sub>[Back to top](#top)</sub>
-
 <a name="standards"></a>
 
 ## Our Standards
@@ -83,17 +83,19 @@ Examples of unacceptable behavior include:
 
 ## Responsibilities
 
-Company and community leaders are responsible for clarifying and enforcing our standards of
-acceptable behavior and will take appropriate and fair corrective action in
-response to any behavior that they deem inappropriate, threatening, offensive,
-or harmful.
+Company and community leaders are responsible for clarifying and enforcing our
+standards of acceptable behavior and will take appropriate and fair corrective
+action in response to any behavior that they deem inappropriate, threatening,
+offensive, or harmful.
 
-Company and community leaders have the right and responsibility to remove, edit, or reject
-comments, commits, code, wiki edits, issues, and other contributions that are
-not aligned to this Code of Conduct, and will communicate reasons for moderation
-decisions when appropriate.
+Company and community leaders have the right and responsibility to remove, edit,
+or reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, and will communicate reasons for
+moderation decisions when appropriate.
 
-Network Pro Strategies reserves the right, at its sole discretion, to remove, edit, or reject any contributions that are contrary to or detrimental to its business interests.
+Network Pro Strategies reserves the right, at its sole discretion, to remove,
+edit, or reject any contributions that are contrary to or detrimental to its
+business interests.
 
 <sub>[Back to top](#top)</sub>
 
@@ -102,10 +104,10 @@ Network Pro Strategies reserves the right, at its sole discretion, to remove, ed
 ## Scope
 
 This Code of Conduct applies within all community spaces, and also applies when
-an individual is officially representing the company or community in public spaces.
-Examples of representing our company or community include using an official email address,
-posting via an official social media account, or acting as an appointed
-representative at an online or offline event.
+an individual is officially representing the company or community in public
+spaces. Examples of representing our company or community include using an
+official email address, posting via an official social media account, or acting
+as an appointed representative at an online or offline event.
 
 <sub>[Back to top](#top)</sub>
 
@@ -113,11 +115,19 @@ representative at an online or offline event.
 
 ## Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the abuse team at [abuse@neteng.pro](mailto:abuse@neteng.pro). All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the abuse team at
+[abuse@neteng.pro](mailto:abuse@neteng.pro). All complaints will be reviewed and
+investigated and will result in a response that is deemed necessary and
+appropriate to the circumstances.
 
-The abuse team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+The abuse team is obligated to maintain confidentiality with regard to the
+reporter of an incident. Further details of specific enforcement policies may be
+posted separately.
 
-Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project’s leadership.
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project’s leadership.
 
 <sub>[Back to top](#top)</sub>
 
@@ -129,9 +139,8 @@ This Code of Conduct is adapted from the [Contributor Covenant][homepage],
 version 2.1, available at
 [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
 
-The **Enforcement** section is adapted from the
-[Contributor Covenant][homepage],
-version 1.4, available at
+The **Enforcement** section is adapted from the [Contributor
+Covenant][homepage], version 1.4, available at
 [https://www.contributor-covenant.org/version/1/4/code-of-conduct/][v1.4].
 
 For answers to common questions about this code of conduct, see the FAQ at
@@ -148,22 +157,15 @@ For answers to common questions about this code of conduct, see the FAQ at
 
 ---
 
-<span style="font-size: 12px; font-weight: bold; text-align: center;">
-
-[Home](https://netwk.pro) &nbsp; | &nbsp; [Terms of Use](https://netwk.pro/terms-of-use)  
-[Privacy Policy](https://netwk.pro/privacy) &nbsp; | &nbsp; [Legal](https://netwk.pro/license)
-
-</span>
-
-&nbsp;
-
 <span style="font-size: 12px; text-align: center;">
 
-Copyright &copy; 2025  
-**[Network Pro Strategies](https://netwk.pro/)** (Network Pro&trade;)
-
-Network Pro&trade;, the shield logo, and the "Locking Down Networks&trade;" slogan are [trademarks](https://netwk.pro/license#trademark) of Network Pro Strategies.
+Network Pro&trade;, the shield logo, and the "Locking Down Networks...&trade;"
+slogan are [trademarks](https://netwk.pro/license#trademark) of Network Pro
+Strategies.
 
-Licensed under **[CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)** and the **[GNU GPL](https://spdx.org/licenses/GPL-3.0-or-later.html)**, as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
+Licensed under **[CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)** and
+the **[GNU GPL](https://spdx.org/licenses/GPL-3.0-or-later.html)**, as published
+by the Free Software Foundation, either version 3 of the License, or (at your
+option) any later version.
 
 </span>

package/src/contributing.md

@@ -1,13 +1,14 @@
 ---
 date:
   created: 2023-12-31
-  updated: 2025-05-30
+  updated: 2025-06-07
 title: Contributing to Network Pro™
-summary: Instructions for getting involved and contributing to Network Pro Strategies.
+summary:
+  Instructions for getting involved and contributing to Network Pro Strategies.
 authors:
   - team
 tags:
-  - network-pro
+  - networkpro
   - contributing
 ---
 
@@ -16,220 +17,193 @@ tags:
 <sup>[SPDX-License-Identifier](https://spdx.dev/learn/handling-license-info):
 `CC-BY-4.0 OR GPL-3.0-or-later`</sup>
 
-# Contributing to Network Pro™
+# 🤝 Contributing to Network Pro Strategies
 
-♥ [Network Pro Strategies](https://netwk.pro/) and want to get involved?
-Thanks! We're actively looking for folks interested in helping out and there
-are plenty of ways you can help!
+**Network Pro Strategies**  
+**Effective Date:** June 7, 2025
 
-Please take a moment to review this document in order to make the contribution
-process easy and effective for everyone involved.
+&nbsp;
 
-Following these guidelines helps to communicate that you respect the time of
-the developers managing and developing this open source project. In return,
-they should reciprocate that respect in addressing your issue or assessing
-patches and features.
+Thanks for your interest in improving **Network Pro Strategies** (Network
+Pro™)! We're always looking for collaborators and contributors of all skill
+levels. This guide will help you get started quickly and effectively.
 
-## Using the issue tracker
+Following these guidelines helps us all work together efficiently and
+respectfully. 🙌
 
-The [issue tracker](https://github.com/netwk-pro/netwk-pro.github.io/issues) is
-the preferred channel for [bug reports](#bugs), [features requests](#features)
-and [submitting pull requests](#pull-requests), but please respect the following
-restrictions:
+---
 
-- Please **do not** use the issue tracker for personal support requests (use
-  [Stack Overflow Teams](https://stack.neteng.pro/), [Discussions](https://discuss.neteng.pro), or [Discord](https://discord.neteng.pro/)).
+## 🐛 Using the Issue Tracker
 
-- Please **do not** derail or troll issues. Keep the discussion on topic and
-  respect the opinions of others.
+Use the [issue tracker](https://github.com/netwk-pro/netwk-pro.github.io/issues)
+for:
 
-<sub>[Back to top](#top)</sub>
+- Reporting [bugs](#bug-reports)
+- Submitting [feature requests](#feature-requests)
+- Proposing [pull requests](#pull-requests)
 
-<a name="bugs"></a>
+🚫 Please do **not** use issues for general support — instead, head to:
 
-## Bug reports
+- [Stack Overflow Teams](https://stack.neteng.pro/)
+- [GitHub Discussions](https://discuss.neteng.pro)
+- [Discord](https://discord.neteng.pro)
 
-A bug is a _demonstrable problem_ that is caused by the code in the repository.
-Good bug reports are extremely helpful - thank you!
+---
 
-Guidelines for bug reports:
+<a name="bug-reports"></a>
 
-1. **Use the GitHub issue search** &mdash; check if the issue has already been
-   reported.
+## 🐞 Bug Reports
 
-2. **Check if the issue has been fixed** &mdash; try to reproduce it using the
-   latest `master` or development branch in the repository.
+A bug is a clear, reproducible issue in the code. High-quality reports help us
+fix problems faster.
 
-3. **Isolate the problem** &mdash; ideally create a [reduced test
-   case](https://css-tricks.com/reduced-test-cases/) and a live example.
+### ✅ A good bug report includes
 
-A good bug report shouldn't leave others needing to chase you down for more
-information. Please try to be as detailed as possible in your report. What is
-your environment? What steps will reproduce the issue? What browser(s) and OS
-experience the problem? What would you expect to be the outcome? All these
-details will help people to fix any potential bugs.
+- A **descriptive title**
+- Steps to reproduce
+- Your environment (OS, browser, version)
+- Expected vs actual behavior
+- Links to a minimal reproducible case (if possible)
 
-Example:
+_Example_:
 
-> Short and descriptive example bug report title
->
-> A summary of the issue and the browser/OS environment in which it occurs. If
-> suitable, include the steps required to reproduce the bug.
->
-> 1. This is the first step
-> 2. This is the second step
-> 3. Further steps, etc.
->
-> `<url>` - a link to the reduced test case
+<!-- markdownlint-disable MD042 -->
+
+> **Title**: Checkbox toggle fails on Safari 17  
+> Steps:
 >
-> Any other information you want to share that is relevant to the issue being
-> reported. This might include the lines of code that you have identified as
-> causing the bug, and potential solutions (and your opinions on their
-> merits).
+> 1. Visit page X
+> 2. Click toggle
+> 3. Observe that...  
+>    Expected: ...  
+>    Actual: ...  
+>    [Live example](#)
+
+<!-- markdownlint-enable MD042 -->
 
 <sub>[Back to top](#top)</sub>
 
-<a name="features"></a>
+---
 
-## Feature requests
+<a name="feature-requests"></a>
 
-Feature requests are welcome. But take a moment to find out whether your idea
-fits with the scope and aims of the project. It's up to _you_ to make a strong
-case to convince the project's developers of the merits of this feature. Please
-provide as much detail and context as possible.
+## ✨ Feature Requests
 
-<sub>[Back to top](#top)</sub>
+Feature requests are welcome — just make sure it aligns with the project’s
+goals.
 
-<a name="pull-requests"></a>
-
-## Pull requests
+Before posting:
 
-Good pull requests - patches, improvements, new features - are a fantastic
-help. They should remain focused in scope and avoid containing unrelated
-commits.
+- Search for similar requests
+- Clearly describe the problem it solves
+- Explain the use case and who benefits
 
-**Please ask first** before embarking on any significant pull request (e.g.
-implementing features, refactoring code, porting to a different language),
-otherwise you risk spending a lot of time working on something that the
-project's developers might not want to merge into the project.
+Strong proposals help us prioritize.
 
-Please adhere to the coding conventions used throughout a project (indentation,
-accurate comments, etc.) and any other requirements (such as test coverage).
+<sub>[Back to top](#top)</sub>
 
-Adhering to the following process is the best way to get your work
-included in the project:
+---
 
-<code><strong>1.</strong></code> [Fork](https://help.github.com/articles/fork-a-repo/) the project, clone your fork, and configure the remotes:
+<a name="pull-requests"></a>
 
-```bash
-# Clone your fork of the repo into the current directory
-git clone https://github.com/<your-username>/netwk-pro.github.io.git
+## 🔁 Pull Requests
 
-# Navigate to the newly cloned directory
-cd netwk-pro.github.io
+Well-scoped, well-documented pull requests are the lifeblood of open-source.
 
-# Assign the original repo to a remote called "upstream"
-git remote add upstream https://github.com/netwk-pro/netwk-pro.github.io.git
-```
+### ⚠️ Ask First
 
-<code><strong>2.</strong></code> If you cloned a while ago, get the latest changes from upstream:
+Before large PRs (new features, refactors, dependency upgrades), please check
+with maintainers first.
 
-```bash
-git checkout master
-git pull upstream master
-```
+### 📋 Steps
 
-<code><strong>3.</strong></code> Create a new topic branch (off the master project development branch) to
-contain your feature, change, or fix:
+`1.` **Fork the repo & set remotes**:
 
 ```bash
-git checkout -b <topic-branch-name>
+git clone https://github.com/<your-username>/netwk-pro.github.io.git cd
+netwk-pro.github.io git remote add upstream
+https://github.com/netwk-pro/netwk-pro.github.io.git
 ```
 
-<code><strong>4.</strong></code> Install locked dependencies:
+`2.` **Stay Updated**
 
 ```bash
-npm ci
+git checkout main
+git pull upstream main
 ```
 
-Ensure that your `node` and `npm` versions are compatible with the `engines`
-specification in `package.json`.
-
-<code><strong>5.</strong></code> Lint your code locally. As reflected in the `devDependencies`, the following
-linting and formatting tools &mdash; or equivalent &mdash; should be used:
-
-- [Prettier](https://prettier.io/)
-- [ESLint](https://eslint.org/)
-- [markdownlint](https://github.com/DavidAnson/markdownlint) and
-  [markdownlint2](https://github.com/DavidAnson/markdownlint-cli2)
-- [Stylelint](https://stylelint.io/)
-
-<code><strong>6.</strong></code> Commit your changes in logical chunks. Please adhere to these [git commit
-message guidelines](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)
-or your code is unlikely be merged into the main project. Use Git's
-[interactive rebase](https://help.github.com/articles/about-git-rebase/)
-feature to tidy up your commits before making them public.
-
-<code><strong>7.</strong></code> Locally merge (or rebase) the upstream development branch into your topic branch:
+`3.` **Create a topic branch:**
 
 ```bash
-git pull [--rebase] upstream master
+git checkout -b my-feature
 ```
 
-<code><strong>8.</strong></code> Update any applicable test cases and run tests:
+`4.` **Install & test locally:**
 
 ```bash
+npm ci
+npm run lint
 npm run test
 ```
 
-Tests must cover changes and pass to be accepted.
+`5.` **Make your changes**
 
-<code><strong>9.</strong></code> Run build and commit changes to build:
+(and commit them in logical chunks with good commit messages).
+
+`6.` **Build:**
 
 ```bash
 npm run build
 git add build/
-git commit
+git commit -m "Build: update assets"
 ```
 
-   <!-- markdownlint-disable MD029 -->
-
-<code><strong>10.</strong></code> Push your topic branch up to your fork:
+`7.` **Push and open a PR:**
 
 ```bash
-git push origin <topic-branch-name>
+git push origin my-feature
 ```
 
-<code><strong>11.</strong></code> [Open a Pull Request](https://help.github.com/articles/using-pull-requests/)
-with a clear title and description.
+Open your PR with a clear title, description, and reference the related issue
+(if any).
 
-<!-- markdownlint-enable MD029 -->
+<sub>[Back to top](#top)</sub>
 
-&nbsp;
+---
 
-**IMPORTANT**: By submitting a patch, you agree to allow the project
-owners to license your work under the terms of [CC BY 4.0](https://netwk.pro/license#cc-by) and the [GNU GPL](https://netwk.pro/license#gnu-gpl).
+## ✅ Coding & Style Notes
 
-<sub>[Back to top](#top)</sub>
+- Use the defined code style (Prettier, ESLint, Stylelint, markdownlint)
+- Avoid unrelated changes in the same PR
+- Keep PRs focused and test-covered when appropriate
 
----
+&nbsp;
 
-<span style="font-size: 12px; font-weight: bold; text-align: center;">
+## 🔐 Legal Notice
 
-[Home](https://netwk.pro) &nbsp; | &nbsp; [Terms of Use](https://netwk.pro/terms-of-use)  
-[Privacy Policy](https://netwk.pro/privacy) &nbsp; | &nbsp; [Legal](https://netwk.pro/license)
+By submitting a pull request, you agree to license your contributions under:
 
-</span>
+- [CC BY 4.0](https://netwk.pro/license#cc-by)
+- [GNU GPL 3.0 or later](https://netwk.pro/license#gnu-gpl)
+
+<sub>[Back to top](#top)</sub>
 
 &nbsp;
 
-<span style="font-size: 12px; text-align: center;">
+_Thanks again for your contribution and for being part of the Network Pro
+community!_
 
-Copyright &copy; 2025  
-**[Network Pro Strategies](https://netwk.pro/)** (Network Pro&trade;)
+---
+
+<span style="font-size: 12px; text-align: center;">
 
-Network Pro&trade;, the shield logo, and the "Locking Down Networks&trade;" slogan are [trademarks](https://netwk.pro/license#trademark) of Network Pro Strategies.
+Network Pro&trade;, the shield logo, and the "Locking Down Networks...&trade;"
+slogan are [trademarks](https://netwk.pro/license#trademark) of Network Pro
+Strategies.
 
-Licensed under **[CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)** and the **[GNU GPL](https://spdx.org/licenses/GPL-3.0-or-later.html)**, as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
+Licensed under **[CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)** and
+the **[GNU GPL](https://spdx.org/licenses/GPL-3.0-or-later.html)**, as published
+by the Free Software Foundation, either version 3 of the License, or (at your
+option) any later version.
 
 </span>

package/src/index.md

@@ -8,7 +8,7 @@ authors:
   - team
 tags:
   - index
-  - network-pro
+  - networkpro
   - blog
 ---
 

package/src/posts/2025-05-29-heliboard.md

@@ -2,7 +2,9 @@
 date:
   created: 2025-05-29
 title: FOSS Spotlight - HeliBoard
-summary: Say hello to HeliBoard – your privacy-first, open-source keyboard built just for Android!
+summary:
+  Say hello to HeliBoard – your privacy-first, open-source keyboard built just
+  for Android!
 authors:
   - team
 categories:
@@ -21,7 +23,9 @@ tags:
 
 ## Say hello to HeliBoard – your privacy-first, open-source keyboard built just for Android! 🚀
 
-This sleek and lightweight keyboard doesn’t just look good—it respects your data, <em>always</em>. No network permissions, no shady tracking, no unnecessary bloat. HeliBoard is here for those who type with purpose AND privacy in mind. 🛡️
+This sleek and lightweight keyboard doesn’t just look good—it respects your
+data, <em>always</em>. No network permissions, no shady tracking, no unnecessary
+bloat. HeliBoard is here for those who type with purpose AND privacy in mind. 🛡️
 
 ### 💡 Key Features
 
@@ -33,17 +37,23 @@ This sleek and lightweight keyboard doesn’t just look good—it respects your
 
 <!-- more -->
 
-Whether you're switching from Gboard or just want something more minimal and ethical, **HeliBoard** brings you that true FOSS flavor while keeping your taps smooth and secure.
+Whether you're switching from Gboard or just want something more minimal and
+ethical, **HeliBoard** brings you that true FOSS flavor while keeping your taps
+smooth and secure.
 
 📥 HeliBoard can be downloaded from the following links:  
 GitHub: [github.com/Helium314/HeliBoard](https://github.com/Helium314/HeliBoard)  
-F-Droid: [f-droid.org/packages/helium314.keyboard/](https://f-droid.org/packages/helium314.keyboard/)
+F-Droid:
+[f-droid.org/packages/helium314.keyboard/](https://f-droid.org/packages/helium314.keyboard/)
 
-🛠️ Open-source. Lightweight. Transparent. HeliBoard isn’t just a keyboard—it's a philosophy.
+🛠️ Open-source. Lightweight. Transparent. HeliBoard isn’t just a keyboard—it's a
+philosophy.
 
-**Weekly FOSS gems like this remind us: we have powerful alternatives, built by passionate devs, made for people who care. _Let's support that_.**
+**Weekly FOSS gems like this remind us: we have powerful alternatives, built by
+passionate devs, made for people who care. _Let's support that_.**
 
-Got a favorite FOSS project? Let us know at [social@neteng.pro](mailto:social@neteng.pro), and we might feature it next!
+Got a favorite FOSS project? Let us know at
+[social@neteng.pro](mailto:social@neteng.pro), and we might feature it next!
 
 &nbsp;