@networkpro/blog 1.0.12 → 1.1.2

package/CODE_OF_CONDUCT.md

@@ -0,0 +1,173 @@
+<!-- =========================================================================
+CODE_OF_CONDUCT.md
+
+Copyright © 2025 Network Pro Strategies (Network Pro™)
+SPDX-License-Identifier: CC-BY-4.0 OR GPL-3.0-or-later
+This file is part of Network Pro.
+========================================================================== -->
+
+<a name="top"></a>
+
+[SPDX-License-Identifier](https://spdx.dev/learn/handling-license-info):
+`CC-BY-4.0 OR GPL-3.0-or-later`
+
+# Contributor Covenant Code of Conduct
+
+**Network Pro Strategies**  
+**Effective Date:** 3/21/2025
+
+&nbsp;
+
+## Contents
+
+- [Our Pledge](#pledge)
+- [Our Standards](#standards)
+- [Responsibilities](#response)
+- [Scope](#scope)
+- [Enforcement](#enforce)
+- [Attribution](#attribute)
+
+---
+
+<section id="pledge">
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+</section>
+
+<section id="standards">
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+<sub>[Back to top](#top)</sub>
+
+</section>
+
+<section id="response">
+
+## 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 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.
+
+<sub>[Back to top](#top)</sub>
+
+</section>
+
+<section id="scope">
+
+## 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.
+
+<sub>[Back to top](#top)</sub>
+
+</section>
+
+<section id="enforce">
+
+## 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.
+
+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.
+
+<sub>[Back to top](#top)</sub>
+
+</section>
+
+<section id="attribute">
+
+## Attribution
+
+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
+[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
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[v1.4]: https://www.contributor-covenant.org/version/1/4/code-of-conduct/
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations
+
+<sub>[Back to top](#top)</sub>
+
+</section>
+
+---
+
+<div 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)
+
+</div>
+
+&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.
+
+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/README.md

@@ -1,7 +1,7 @@
 <!-- =========================================================================
 README.md
 
-Copyright © 2025 Network Pro Strategies (Network Pro)
+Copyright © 2025 Network Pro Strategies (Network Pro™)
 SPDX-License-Identifier: CC-BY-4.0 OR GPL-3.0-or-later
 This file is part of Network Pro.
 ========================================================================== -->

package/cspell.json

@@ -5,16 +5,25 @@
     "acode",
     "bleepingcomputer",
     "bnav",
+    "changefreq",
+    "Donath",
     "fontawesome",
     "FOSS",
     "Gboard",
     "Heli",
     "heliboard",
+    "homescreen",
+    "lastmod",
     "mkdocs",
+    "msauth",
     "NETPRO",
     "npmjs",
+    "pozil",
+    "robotstxt",
     "stylesheet",
-    "vcard"
+    "urlset",
+    "vcard",
+    "Voss"
   ],
   "ignorePaths": [
     ".gitignore",

package/eslint.config.mjs

@@ -1,6 +1,7 @@
 /* ==========================================================================
 eslint.config.mjs
 
+Copyright © 2025 Network Pro Strategies (Network Pro™)
 SPDX-License-Identifier: CC-BY-4.0 OR GPL-3.0-or-later
 This file is part of Network Pro.
 ========================================================================== */

package/mkdocs.yml

@@ -2,13 +2,15 @@ site_name: Network Pro™ Blog
 site_url: https://blog.netwk.pro
 repo_url: https://github.com/netwk-pro/netwk-pro.github.io
 repo_name: GitHub
-docs_dir: docs_raw
+docs_dir: src
 site_dir: build/
 
 theme:
-  name: material
   language: en
-  font: false
+  name: material
+  font:
+    text: null
+    code: null
   logo: /icon-512x512.png
   favicon: /favicon.svg
   palette:
@@ -106,8 +108,13 @@ plugins:
         as_creation: date.created
         as_update: date.updated
 
+extra_css:
+  - stylesheets/extra.css
+
 nav:
   - Home: index.md
   - Tags: tags.md
   - Website: https://netwk.pro
-  - Contributing: contributing.md
+  - Contributing:
+      - Code of Conduct: CODE_OF_CONDUCT.md
+      - Contribute to Network Pro™: contributing.md

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@networkpro/blog",
-  "version": "1.0.12",
+  "version": "1.1.2",
   "description": "The official blog of Network Pro Strategies (Network Pro™).",
   "keywords": [
     "advisory",
@@ -31,24 +31,27 @@
     "url": "https://bio.neteng.pro"
   },
   "type": "module",
-  "styles": "docs_raw/styles/global.css",
   "scripts": {
-    "clean": "rm -rf build/* node_modules package-lock.json && npm install",
+    "dev": "mkdocs serve",
+    "start": "npm run dev",
+    "build": "mkdocs build",
+    "delete": "rm -rf build node_modules package-lock.json",
+    "clean": "npm run delete && npm cache clean --force && npm install",
     "format": "prettier --check .",
     "format:fix": "prettier --write .",
-    "lint": "eslint --ext .mjs,.js,.json,.jsonc --config eslint.config.mjs .",
-    "lint:fix": "eslint --ext .mjs,.js,.json,.jsonc --config eslint.config.mjs . --fix",
+    "lint": "eslint . --ext .mjs,.js,.json,.jsonc",
+    "lint:fix": "eslint . --ext .mjs,.js,.json,.jsonc --fix",
     "lint:md": "npx markdownlint-cli2 \"**/*.{md,markdown}\" \"#node_modules/**\" \"#build/**\"",
-    "lint:css": "npx stylelint \"docs_raw/styles/*.css\" --ignore-path .stylelintignore",
+    "lint:css": "npx stylelint \"**/*.css\" --ignore-path .stylelintignore",
     "lint:all": "npm run lint && npm run lint:md && npm run lint:css && npm run format",
     "upgrade": "npx npm-check-updates -u"
   },
   "devDependencies": {
-    "@eslint/js": "^9.27.0",
+    "@eslint/js": "^9.28.0",
     "@eslint/json": "^0.12.0",
     "autoprefixer": "^10.4.21",
     "browserslist": "^4.25.0",
-    "eslint": "^9.27.0",
+    "eslint": "^9.28.0",
     "eslint-config-prettier": "^10.1.5",
     "globals": "^16.2.0",
     "markdownlint": "^0.38.0",

package/postcss.config.mjs

@@ -1,3 +1,11 @@
+/* ==========================================================================
+postcss.config.mjs
+
+Copyright © 2025 Network Pro Strategies (Network Pro™)
+SPDX-License-Identifier: CC-BY-4.0 OR GPL-3.0-or-later
+This file is part of Network Pro.
+========================================================================== */
+
 export default {
   plugins: {
     autoprefixer: {}, // Enables autoprefixer and uses Browserslist configuration

package/{docs_raw/contributing.md → src/CODE_OF_CONDUCT.md}

@@ -1,27 +1,30 @@
 ---
 date:
-  created: 2023-12-31
-  updated: 2025-05-10
+  created: 2025-03-21
+  updated: 2025-05-30
 title: Code of Conduct
-summary: The Contributor Covenant Code of Conduct for our repositories.
+summary: The Contributor Covenant Code of Conduct for Network Pro's public repositories.
 authors:
   - team
 tags:
   - network-pro
   - contributing
+  - code-of-conduct
 ---
 
-<sup>[SPDX-License-Identifier](https://spdx.dev/learn/handling-license-info/):
-`CC-BY-4.0 OR GPL-3.0-or-later`</sup>
-
 <a name="top"></a>
 
+<sup>[SPDX-License-Identifier](https://spdx.dev/learn/handling-license-info):
+`CC-BY-4.0 OR GPL-3.0-or-later`</sup>
+
 # Contributor Covenant Code of Conduct
 
 **Network Pro Strategies**  
-**Effective Date:** May 10, 2025
+**Effective Date:** 3/21/2025
+
+&nbsp;
 
-## Table of Contents
+## Contents
 
 - [Our Pledge](#pledge)
 - [Our Standards](#standards)
@@ -147,8 +150,8 @@ 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.html)  
-[Privacy Policy](https://netwk.pro/privacy.html) &nbsp; | &nbsp; [Legal](https://netwk.pro/legal.html)
+[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>
 
@@ -159,7 +162,7 @@ For answers to common questions about this code of conduct, see the FAQ at
 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/legal#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.
 

package/src/contributing.md

@@ -0,0 +1,235 @@
+---
+date:
+  created: 2023-12-31
+  updated: 2025-05-30
+title: Contributing to Network Pro™
+summary: Instructions for getting involved and contributing to Network Pro Strategies.
+authors:
+  - team
+tags:
+  - network-pro
+  - contributing
+---
+
+<a name="top"></a>
+
+<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™
+
+♥ [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!
+
+Please take a moment to review this document in order to make the contribution
+process easy and effective for everyone involved.
+
+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.
+
+## Using the issue tracker
+
+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/)).
+
+- Please **do not** derail or troll issues. Keep the discussion on topic and
+  respect the opinions of others.
+
+<sub>[Back to top](#top)</sub>
+
+<a name="bugs"></a>
+
+## Bug reports
+
+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:
+
+1. **Use the GitHub issue search** &mdash; check if the issue has already been
+   reported.
+
+2. **Check if the issue has been fixed** &mdash; try to reproduce it using the
+   latest `master` or development branch in the repository.
+
+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 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.
+
+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
+>
+> 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).
+
+<sub>[Back to top](#top)</sub>
+
+<a name="features"></a>
+
+## Feature requests
+
+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.
+
+<sub>[Back to top](#top)</sub>
+
+<a name="pull-requests"></a>
+
+## Pull requests
+
+Good pull requests - patches, improvements, new features - are a fantastic
+help. They should remain focused in scope and avoid containing unrelated
+commits.
+
+**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.
+
+Please adhere to the coding conventions used throughout a project (indentation,
+accurate comments, etc.) and any other requirements (such as test coverage).
+
+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:
+
+```bash
+# Clone your fork of the repo into the current directory
+git clone https://github.com/<your-username>/netwk-pro.github.io.git
+
+# Navigate to the newly cloned directory
+cd netwk-pro.github.io
+
+# Assign the original repo to a remote called "upstream"
+git remote add upstream https://github.com/netwk-pro/netwk-pro.github.io.git
+```
+
+<code><strong>2.</strong></code> If you cloned a while ago, get the latest changes from upstream:
+
+```bash
+git checkout master
+git pull upstream master
+```
+
+<code><strong>3.</strong></code> Create a new topic branch (off the master project development branch) to
+contain your feature, change, or fix:
+
+```bash
+git checkout -b <topic-branch-name>
+```
+
+<code><strong>4.</strong></code> Install locked dependencies:
+
+```bash
+npm ci
+```
+
+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:
+
+```bash
+git pull [--rebase] upstream master
+```
+
+<code><strong>8.</strong></code> Update any applicable test cases and run tests:
+
+```bash
+npm run test
+```
+
+Tests must cover changes and pass to be accepted.
+
+<code><strong>9.</strong></code> Run build and commit changes to build:
+
+```bash
+npm run build
+git add build/
+git commit
+```
+
+   <!-- markdownlint-disable MD029 -->
+
+<code><strong>10.</strong></code> Push your topic branch up to your fork:
+
+```bash
+git push origin <topic-branch-name>
+```
+
+<code><strong>11.</strong></code> [Open a Pull Request](https://help.github.com/articles/using-pull-requests/)
+with a clear title and description.
+
+<!-- markdownlint-enable MD029 -->
+
+&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).
+
+<sub>[Back to top](#top)</sub>
+
+---
+
+<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.
+
+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/{docs_raw → src}/manifest.json

@@ -1,6 +1,6 @@
 {
-  "name": "Network Pro Strategies",
-  "short_name": "Network Pro",
+  "name": "Network Pro Blog",
+  "short_name": "Blog",
   "description": "Access our cybersecurity and privacy blog anytime, anywhere. Fully optimized for speed, security, and mobile use, it's your gateway to expert insights, project highlights, and seamless connection—all in one place.",
   "start_url": "/?utm_source=homescreen",
   "display": "standalone",

package/{docs_raw/posts/heliboard.md → src/posts/2025-05-29-heliboard.md}

@@ -39,12 +39,17 @@ Whether you're switching from Gboard or just want something more minimal and eth
 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/)
 
-🛠️ Open-source. Lightweight. Transparent. HeliBoard isn’t just a keyboard
+🛠️ 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_.**
 
-Got a favorite FOSS project? Let us know at [social@neteng.pro](mailto:social@neteng.pro).
+Got a favorite FOSS project? Let us know at [social@neteng.pro](mailto:social@neteng.pro), and we might feature it next!
 
  
 
-![HeliBoard](../img/heliboard-promo.png)
+<figure class="poster-figure">
+  <img src="/img/heliboard-promo.png" alt="FOSS Spotlight: HeliBoard">
+  <figcaption>FOSS Spotlight: HeliBoard – featured visual</figcaption>
+</figure>
+
+<!-- ![HeliBoard](../img/heliboard-promo.png) -->

package/{docs_raw/posts/msauth.md → src/posts/2025-05-29-msauth.md}

@@ -46,6 +46,9 @@ Check the link below for full details:
 
  
 
-![Microsoft Authenticator](../img/msauth-promo.png)
+<figure class="poster-figure">
+  <img src="/img/msauth-promo.png" alt="Microsoft Authenticator Users: Major Change Incoming">
+  <figcaption>Microsoft Authenticator Changes Incoming – featured visual</figcaption>
+</figure>
 
 <!-- cspell:ignore ente -->

package/src/robots.txt

@@ -0,0 +1,20 @@
+# robots.txt
+#
+# Copyright © 2025 Network Pro Strategies (Network Pro™)
+# SPDX-License-Identifier: CC-BY-4.0 OR GPL-3.0-or-later
+# This file is part of Network Pro
+#
+# www.robotstxt.org
+
+User-agent: *
+
+# Disallow dev and CI/CD artifacts
+Disallow: /tests/
+Disallow: /reports/
+Disallow: /build/
+
+# Allow everything else
+Allow: /
+
+# Inform bots where to find the sitemap
+Sitemap: https://blog.netwk.pro/sitemap.xml