feat: new forms

src/content/docs/about/contact.md

@@ -263,7 +263,14 @@ We encourage you to use the **#technical-support** Discord forum channel for sup
 
 ### 5.4. Privacy Concerns
 
-- Email: privacy@nhcarrigan.com
+:::tip[Preferred Method]{icon=message}
+We encourage you to use our **Privacy Request Form** for privacy-related requests: https://forms.nhcarrigan.com/o/docs/forms/qEJgBWGDfyHv6x51VU9aVX/4
+
+This form helps ensure we collect all necessary information to process your request efficiently and in compliance with applicable data protection laws.
+:::
+
+- **Privacy Request Form** (Preferred): https://forms.nhcarrigan.com/o/docs/forms/qEJgBWGDfyHv6x51VU9aVX/4
+- Email: privacy@nhcarrigan.com (for general privacy questions or if you prefer email)
 - Use for:
   - Questions about our privacy policy
   - Requests for data access or deletion
@@ -272,7 +279,14 @@ We encourage you to use the **#technical-support** Discord forum channel for sup
 
 ### 5.5. Security Matters
 
-- Email: security@nhcarrigan.com
+:::tip[Preferred Method]{icon=message}
+We encourage you to use our **Security Vulnerability Report Form** for reporting security vulnerabilities: https://forms.nhcarrigan.com/o/docs/forms/wgdbBkS4tjCGoVZTqtmMNx/4
+
+This form helps ensure we collect all necessary information to investigate and address security issues efficiently and securely.
+:::
+
+- **Security Vulnerability Report Form** (Preferred): https://forms.nhcarrigan.com/o/docs/forms/wgdbBkS4tjCGoVZTqtmMNx/4
+- Email: security@nhcarrigan.com (for general security questions or if you prefer email)
 - Use for:
   - Reporting security vulnerabilities
   - Questions about our security practices

src/content/docs/community/coc.md

@@ -217,10 +217,10 @@ Community Members are required to:
 
 #### 5.1.1. Available Reporting Methods
 Community Members can report Code of Conduct violations through the following channels:
+- **Incident Report Form** (Preferred): Submit reports through our official Incident Report Form: https://forms.nhcarrigan.com/o/docs/forms/t7CYeYS4uyUuLiKFatoEvs/4
 - **Discord Reporting**: Type `@Moderator` in any channel to alert Community Leaders
 - **Direct Communication**: Contact any Community Leader through private messages
 - **Email Contact**: Submit reports to contact@nhcarrigan.com
-- **Anonymous Reporting**: Use designated anonymous reporting forms where available
 
 #### 5.1.2. Information to Include in Reports
 Effective reports should include:

src/content/docs/legal/aup.md

@@ -670,6 +670,8 @@ For questions about this AUP:
 
 To report policy violations:
 
+**Incident Report Form** (Preferred): Submit reports through our official Incident Report Form: https://forms.nhcarrigan.com/o/docs/forms/t7CYeYS4uyUuLiKFatoEvs/4
+
 **Email:** abuse@nhcarrigan.com
 
 **Subject Line:** Policy Violation Report - [Service/Platform]

src/content/docs/legal/community-support-policy.md

@@ -62,7 +62,7 @@ This policy applies to all forms of support exchange within our community platfo
 - Assistance with community projects and initiatives
 - Collaborative problem-solving on shared challenges
 - Skill sharing and mentorship opportunities
-- Accessibility assistance and accommodation support
+- Accessibility assistance and accommodation support (request accommodations via our [Accessibility Accommodation Request Form](https://forms.nhcarrigan.com/o/docs/forms/2FXY87PB6aaMHspcnXYCZX/4))
 - Platform-specific guidance and orientation
 
 #### 2.1.2. Specialised Support Areas
@@ -316,7 +316,7 @@ We are working very hard to get them in place as soon as possible. If you would
 **Designated Support Channels:**
 - **#support**: General questions and peer support requests
 - **#support-ticket**: Technical assistance and troubleshooting
-- **#accessibility**: Accessibility-related assistance and resources
+- **#accessibility**: Accessibility-related assistance and resources (for accommodation requests, use our [Accessibility Accommodation Request Form](https://forms.nhcarrigan.com/o/docs/forms/2FXY87PB6aaMHspcnXYCZX/4))
 - **Identity-specific channels**: Support spaces for specific communities and identities
 
 **Direct Message Guidelines:**

src/content/docs/legal/privacy.md

@@ -192,13 +192,15 @@ Regardless of your location, you have the following rights regarding your person
 
 To exercise any of these rights:
 
-**(a)** Submit requests to **privacy@nhcarrigan.com** from the email address associated with your account;
+**(a)** Submit requests through our **Privacy Request Form** (Preferred): https://forms.nhcarrigan.com/o/docs/forms/qEJgBWGDfyHv6x51VU9aVX/4
 
-**(b)** Provide sufficient information to verify your identity;
+**(b)** Alternatively, submit requests to **privacy@nhcarrigan.com** from the email address associated with your account;
 
-**(c)** Specify clearly which right you wish to exercise;
+**(c)** Provide sufficient information to verify your identity;
 
-**(d)** Include any relevant details or documentation to support your request.
+**(d)** Specify clearly which right you wish to exercise;
+
+**(e)** Include any relevant details or documentation to support your request.
 
 ### 5.3. Response Timeframes
 

src/content/docs/legal/security.md

@@ -48,6 +48,8 @@ This Policy is designed to operate within the framework of applicable laws and r
 
 If you discover a security vulnerability within any of our systems or applications, please report it exclusively through our designated secure reporting channel:
 
+**Security Vulnerability Report Form** (Preferred): https://forms.nhcarrigan.com/o/docs/forms/wgdbBkS4tjCGoVZTqtmMNx/4
+
 **Primary Contact:** security@nhcarrigan.com
 
 **Subject Line Format:** [SECURITY] Brief description of vulnerability
@@ -470,6 +472,8 @@ If vulnerability research reveals potential regulatory compliance issues or lega
 
 For all security-related matters, including vulnerability reports, questions about this Policy, and general security inquiries:
 
+**Security Vulnerability Report Form** (Preferred for vulnerability reports): https://forms.nhcarrigan.com/o/docs/forms/wgdbBkS4tjCGoVZTqtmMNx/4
+
 **Email:** security@nhcarrigan.com
 
 **Response Time:** We aim to respond to all security inquiries within 7-10 business days

src/content/docs/legal/subprocessors.md

@@ -352,7 +352,7 @@ Regarding data processed by subprocessors, users may:
 
 To exercise rights regarding subprocessor data processing:
 
-**(a)** **Primary Contact:** Contact us at privacy@nhcarrigan.com for coordination;
+**(a)** **Primary Contact:** Submit requests through our **Privacy Request Form** (Preferred): https://forms.nhcarrigan.com/o/docs/forms/qEJgBWGDfyHv6x51VU9aVX/4 or contact us at privacy@nhcarrigan.com for coordination;
 
 **(b)** **Direct Contact:** Contact subprocessors directly using their provided channels;
 

staff-announcement.md

@@ -0,0 +1,42 @@
+# Staff Announcement
+
+Hey team! 👋 Just wanted to share a few quick updates:
+
+## 📋 Policy Disclaimers Added
+
+We've added disclaimers to policies that are still being implemented. You'll see these as tip callouts in various policy documents (like SLA, Privacy, Content Moderation, and others) indicating that certain sections are still a work in progress. This helps set clear expectations while we continue building out the necessary infrastructure.
+
+## 🏷️ New Points and Time Labels
+
+We've introduced new labeling systems to help with capacity planning and workload management:
+
+**Points Labels** (complexity/effort):
+- `points: 1` - Very simple tasks
+- `points: 2` - Simple tasks
+- `points: 3` - Moderate complexity
+- `points: 5` - Complex issues
+- `points: 8` - Very complex
+- `points: 13` - Extremely complex/epic-level
+
+**Time Labels** (expected duration):
+- `time: <1 day` - Quick fixes
+- `time: 1 day` - One day of work
+- `time: 2-3 days` - Multi-day tasks
+- `time: 4-5 days` - About a week
+- `time: 1-2 weeks` - Major features
+- `time: >2 weeks` - Epic-level work
+
+Check out the full details in our [Labels documentation](https://docs.nhcarrigan.com/dev/labels)!
+
+## 📊 New Project Board for Available Tickets
+
+We now have a dedicated **Staff Tickets** project board where you can find all properly triaged tickets that are ready to be worked on! 
+
+🔗 **Project Board**: https://git.nhcarrigan.com/nhcarrigan/-/projects/2
+
+All tickets with the `status: ready for dev` label are automatically available on this board, making it much easier to find work that's ready to go.
+
+---
+
+Questions? Feel free to reach out! 💬
+