🧑‍🔬 Advanced Issue

Welcome! This is an Advanced Issue touching core website architecture.

It is designed for expert contributors who have demonstrated deep architectural understanding and a proven track record of high-quality contributions.

🐞 Problem Description

Currently when a contributor creates an issue no one is notified and the issue remains open.

This creates a problem as the team needs to determine if the issue is valid and label it properly.
With out proper labeling our current bots to do not count the work. This interferes with issue counts for contributors. Ultimately, the bot does not recognize the issue or add it to the count with proper triage.

🛠️ Implementation Notes

We propose to implement work flow files that will moderate issues by reserving/locking them until the issue has been approved by a team member.

Workflows must be tested and corresponding PR's must include some form of successful testing to ensure code works as intended.

🧠 Advanced Contributors — Prerequisites & Expectations

🏁 Concrete Prerequisites

• Advanced Web Development: Proficient with React, Next.js, and TypeScript.
• Expertise: Deep architectural understanding of the website's component structure, routing, and build pipeline.
• Proven History: Successfully completed ≥ 10 intermediate issues in this repo.
• Consistency: ≥ 3–4 months of active, human-led contributions to this project.

⚠️ AI Usage Policy

• Using AI to generate code for Advanced issues is strictly discouraged
• AI may be used to help explain file relationships, but cannot be the main source of research.
• Submitting AI-generated or unvalidated code is grounds for immediate closure

⏱️ Timeline & Workflow

• Typical time: ~1 month / ~50 hours.
• 🔴 Completing an advanced issue in 1–3 days is a red flag and will likely be rejected.
• Suggested: Post your proposed architectural approach as a comment and wait for explicit maintainer approval before writing any code.

🔬 Technical Domains

• Advanced React / Next.js (Server Components, App Router, dynamic routing, middleware)
• Component Architecture (design systems, reusable patterns, composition)
• Performance & Optimization (Core Web Vitals, image optimization, code splitting, caching)
• Accessibility (WCAG compliance, screen reader support, keyboard navigation)
• Build & Deployment (Next.js config, CI/CD, hosting/deployment integration)
• Testing (unit, integration, E2E, accessibility testing, visual regression)

🛡️ Quality & Review Standards

Advanced PRs must be "safe, maintainable, architecturally sound, and production-ready."

1. Architectural Fit: The solution must fit naturally into the existing website architecture.
2. Security & Correctness: Evaluate all logic for injection risks, XSS vulnerabilities, or state corruption issues.
3. Maintainability: Code must be short and clear enough for any other maintainer to debug without your assistance.
4. Backward Compatibility: Existing pages, routes, and components must not break. If a breaking change is required, it must be explicitly managed.
5. Comprehensive Testing: Must include unit and integration tests covering all new logic paths, edge cases, and failure modes. AI-generated tests based on AI-generated code are grounds for immediate rejection.

✅ PR Quality Checklist

Before opening your PR, the contributor must confirm:

• I have spent the majority of my time researching the problem and solution space extensively, including reviewing relevant code, documentation, and external resources.
• I understand the system-wide impact of these changes on affected modules and performance.
• The design fits with the current website's architectural approaches.
• I have tested my changes extensively across browsers and screen sizes.
• Every line of code is personally understood and explainable.

📚 Resources & Support

References:

• Next.js Documentation
• React Documentation
• Tailwind CSS Documentation
• Vitest Documentation
• Writing Blog Posts

🆘 Stuck?

• Community Calls
• Discord