chore: release prep for v1.4.0

CHANGELOG.md

@@ -0,0 +1,74 @@
+<!-- =====================================================================
+CHANGELOG.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.
+====================================================================== -->
+
+<!-- markdownlint-disable MD024 -->
+
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+This project follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
+Version numbers use a **SemVer-inspired** `MAJOR.MINOR.PATCH` format, with
+version increments reflecting both user-visible and operational impact.
+
+---
+
+## [Unreleased]
+
+---
+
+## [1.4.0] – 2026-01-01
+
+### Added
+
+- Added `vercel.json` to define Vercel build configuration and security headers.
+- Added Vercel as a supported deployment target for this site.
+- Added `VERSIONING.md` to document the project’s versioning strategy.
+- Added `runtime.txt` to specify the project's Python runtime version.
+
+### Changed
+
+- Updated `dev` script in `package.json` to enable hot reloading of content
+  (`--livereload`).
+- Corrected formatting of `contributing.md` with Prettier.
+- Updated home page (`src/index.md`) to better reflect the company’s current
+  mission, focus, and messaging.
+- Migrated static site deployment from Netlify to Vercel.
+- Converted Netlify build configuration (`netlify.toml`) to Vercel-equivalent
+  settings.
+- Updated MkDocs build invocation to use `python -m mkdocs` for improved
+  compatibility in CI environments.
+- Explicitly configured the build output directory as `build/`.
+- Preserved existing Content Security Policy (CSP), reporting endpoints, and
+  security headers under Vercel.
+- Bumped project version to `v1.4.0`.
+- Updated frontend tooling dependencies:
+  - `@eslint/js` `^9.39.1` → `^9.39.2`
+  - `autoprefixer` `^10.4.22` → `^10.4.23`
+  - `browserslist` `^4.28.0` → `^4.28.1`
+  - `eslint` `^9.39.1` → `^9.39.2`
+  - `globals` `^16.5.0` → `^17.0.0`
+  - `markdownlint` `^0.39.0` → `^0.40.0`
+  - `markdownlint-cli2` `^0.19.0` → `^0.20.0`
+  - `prettier` `3.6.2` → `3.7.4`
+  - `stylelint` `^16.25.0` → `^16.26.1`
+  - `stylelint-order` `^7.0.0` → `^7.0.1`
+
+### Removed
+
+- Removed `netlify.toml`, as Netlify is no longer the active deployment
+  platform.
+- Removed reliance on Netlify-specific header configuration in favor of Vercel
+  headers.
+
+---
+
+<!-- Link references -->
+
+[Unreleased]: https://github.com/netwk-pro/docs/compare/v1.4.0...HEAD
+[1.4.0]: https://github.com/netwk-pro/docs/releases/tag/v1.4.0

VERSIONING.md

@@ -0,0 +1,47 @@
+# Versioning Policy
+
+This project uses a **SemVer-inspired versioning scheme** based on the
+`MAJOR.MINOR.PATCH` format.
+
+Version numbers are intended to communicate the **impact of a change** rather
+than strict compliance with the Semantic Versioning specification. In addition
+to user-facing changes, version increments may reflect infrastructure, hosting,
+or operational changes relevant to maintainers.
+
+## Version Number Meaning
+
+### MAJOR (`X.0.0`)
+
+Incremented when changes introduce **user-visible incompatibilities**, such as:
+
+- URL or navigation structure changes
+- Removal or renaming of major sections
+- Changes that break existing links or bookmarks
+- Changes to access, availability, or licensing
+
+### MINOR (`1.X.0`)
+
+Incremented for **backward-compatible but significant changes**, including:
+
+- Hosting platform migrations (e.g. Netlify → Vercel)
+- Build or deployment pipeline changes
+- Security header or CSP delivery changes
+- Changes that may affect maintainers or operators, but not readers
+- New features or content additions that do not break existing usage
+
+### PATCH (`1.1.X`)
+
+Incremented for **backward-compatible, low-impact changes**, such as:
+
+- Content edits or corrections
+- Dependency updates
+- Tooling updates that do not alter build behavior
+- Internal refactoring or cleanup
+
+## Notes
+
+- Infrastructure or platform changes may be considered “breaking” from a
+  maintainer perspective, but do not automatically imply a MAJOR version bump.
+- Version numbers are intended to communicate **impact**, not just change.
+- Detailed migration or operational notes are documented in the changelog when
+  relevant.