Skip to content

Conversation

@SunDevil311
Copy link
Member

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

Documentation

  • Updated directory structure and static/pgp section of README.md.

Changed

  • Bumped project version to v1.22.1.
  • Updated the text and layout of AboutContent.svelte.
  • Added a link to the privacy email address in PrivacyContent.svelte and PrivacyDashboard.svelte for easier access.
  • Updated the text of ServicesContent.svelte.

Fixed

  • Corrected TermsUseContent.svelte to reflect hosting by Vercel, not Netlify.
  • Corrected license identifier syntax on the following pages:
    • AboutContent.svelte
    • FossContent.svelte
    • LicenseContent.svelte
    • PrivacyContent.svelte
    • PrivacyDashboard.svelte
    • ServicesContent.svelte
    • TermsConditionsContent.svelte
    • TermsUseContent.svelte

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!

@vercel
Copy link

vercel bot commented Oct 21, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
web Ready Ready Preview Comment Oct 21, 2025 10:56am

💡 Enable Vercel Agent with $100 free credit for automated AI reviews

Copy link
Member Author

@SunDevil311 SunDevil311 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All changes look good. Merging pending completion of tests.

@github-actions
Copy link

⚠️ Lighthouse Budget Issues Detected

  • First Contentful Paint (score: 0.99)
  • Largest Contentful Paint (score: 0.86)
  • Max Potential First Input Delay (score: 0.9)
  • Time to Interactive (score: 0.94)
  • Largest Contentful Paint element (score: 0)
  • Links rely on color to be distinguishable. (score: 0)
  • Serve static assets with an efficient cache policy (score: 0.5)
  • Reduce unused CSS (score: 0)
  • Reduce unused JavaScript (score: 0.5)
  • Avoid serving legacy JavaScript to modern browsers (score: 0.5)
  • Use efficient cache lifetimes (score: 0.5)
  • Network dependency tree (score: 0)
  • Render blocking requests (score: 0.5)

View the full report in the workflow artifacts or in .lighthouseci/report.html.

Copy link
Member Author

@SunDevil311 SunDevil311 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes look good. Waiting on tests.

@github-actions
Copy link

⚠️ Lighthouse Budget Issues Detected

  • First Contentful Paint (score: 0.93)
  • Largest Contentful Paint (score: 0.5)
  • Speed Index (score: 0.96)
  • Max Potential First Input Delay (score: 0.99)
  • Time to Interactive (score: 0.87)
  • Largest Contentful Paint element (score: 0)
  • Links rely on color to be distinguishable. (score: 0)
  • Serve static assets with an efficient cache policy (score: 0.5)
  • Reduce unused CSS (score: 0)
  • Reduce unused JavaScript (score: 0)
  • Avoid serving legacy JavaScript to modern browsers (score: 0)
  • Use efficient cache lifetimes (score: 0)
  • Optimize DOM size (score: 0)
  • Duplicated JavaScript (score: 0.5)
  • Legacy JavaScript (score: 0)
  • Network dependency tree (score: 0)
  • Render blocking requests (score: 0.5)

View the full report in the workflow artifacts or in .lighthouseci/report.html.

@SunDevil311 SunDevil311 merged commit 657ddb0 into master Oct 21, 2025
10 checks passed
@SunDevil311 SunDevil311 deleted the feature/revise-pages branch October 21, 2025 11:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants