Create issue: Set Up Quality Testing Pipeline

Author: benkutil

issues/Set-Up-Quality-Testing-Pipeline.md

@@ -0,0 +1,29 @@
+### Detailed Plan
+
+1. **Title of the Issue**: Set Up Quality Testing Pipeline
+   - This issue focuses on integrating robust quality testing systems, including pre-commit hooks, local testing scripts, and CI pipelines, to ensure the codebase adheres to high-quality standards.
+
+2. **Description**:
+   - Set up pre-commit hooks to automatically check code quality before commits. This will include tools like `husky` and `lint-staged` to lint and fix CSS, JavaScript, and Nunjucks templates.
+   - Create local testing scripts for CSS (`stylelint`), JavaScript (`eslint`), Nunjucks (`eslint-plugin-nunjucks`), and HTML validation using `htmlproofer`.
+   - Configure accessibility testing through `pa11y`.
+   - Set up a CI workflow with GitHub Actions to automate the following:
+     - Prettier, Stylelint, and ESLint linting for all files.
+     - Building the site using Eleventy.
+     - HTML validation (`htmlproofer`) and accessibility checks (`pa11y`).
+     - Adding Visual Regression Testing tools (optional).
+
+3. **Acceptance Criteria**:
+   - All necessary tools (Prettier, Stylelint, ESLint, etc.) must be installed and functional.
+   - The repository must include local testing scripts accessible via npm run commands.
+   - CI workflows should successfully execute linting, testing, and build processes.
+   - CI workflows must pass without errors on every code push or pull request.
+
+4. **Checklist**:
+   - [ ] Add pre-commit hooks with husky and lint-staged.
+   - [ ] Configure local testing scripts for linting and validation.
+   - [ ] Set up GitHub Actions workflows for CI testing.
+   - [ ] Ensure Visual Regression Testing is optional but supported.
+
+---
+This issue ensures the repository improves developer experience and code quality, making it easier to maintain and evolve.