chore: release prep for v1.4.0

[SunDevil311]

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Description

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.

Checklist

• I have read and followed the guidelines in the CONTRIBUTING document.
• I've checked for existing Pull Requests for the same update/change.
• My code follows the project’s coding style.
• My code has been linted locally before submission.
• All new and existing tests pass.

 

• I have updated the documentation accordingly.
• I have added tests to cover my changes, if applicable. (Optional, especially for new contributors)

Pull requests are part of a collaborative process — we welcome contributions and review each one carefully. For all but the smallest changes, you can expect maintainers to request improvements or clarifications.

Please check back after opening your PR and be responsive to feedback so we can get your contribution merged quickly.

Thanks for helping improve Network Pro Strategies!

[SunDevil311]

All changes look good. Merging.