[WIP] Add essential community health files and templates

[Copilot]

Plan: Add Essential Community Health Files and GitHub Templates

• Create CODE_OF_CONDUCT.md with Contributor Covenant
• Create SECURITY.md with vulnerability reporting process
• Create .gitignore for web projects
• Create CHANGELOG.md following "Keep a Changelog" format
• Create .github/ISSUE_TEMPLATE/bug_report.md
• Create .github/ISSUE_TEMPLATE/feature_request.md
• Create .github/PULL_REQUEST_TEMPLATE.md
• Create .github/FUNDING.yml
• Verify all files are properly formatted and follow best practices

Original prompt

Objective

Add essential community health files and GitHub templates to improve project governance, contribution guidelines, and repository standards.

Files to Add

1. CODE_OF_CONDUCT.md

• Add a comprehensive Code of Conduct file
• Include community standards and behavioral guidelines
• Define expected behavior and consequences for violations
• Use the Contributor Covenant standard or similar

2. SECURITY.md

• Create a security policy file
• Include vulnerability reporting process
• Specify supported versions
• Provide contact information for security issues
• Add disclosure timeline expectations

3. .gitignore

• Create a proper .gitignore file for web projects
• Include patterns for:
  • Node.js dependencies (node_modules/)
  • IDE files (.vscode/, .idea/, .sublime-)
  • OS files (.DS_Store, Thumbs.db)
  • Build files (dist/, build/)
  • Environment files (.env, .env.local)
  • Log files (*.log)
  • Package manager files (npm-debug.log*, yarn-debug.log*)

4. CHANGELOG.md

• Add a CHANGELOG.md file for version history tracking
• Follow "Keep a Changelog" format
• Include sections for: Added, Changed, Deprecated, Removed, Fixed, Security
• Start with [Unreleased] section

5. .github/ISSUE_TEMPLATE/bug_report.md

• Create bug report template in .github/ISSUE_TEMPLATE/
• Include sections for:
  • Bug description
  • Steps to reproduce
  • Expected behavior
  • Actual behavior
  • Screenshots (if applicable)
  • Environment details (browser, OS, etc.)

6. .github/ISSUE_TEMPLATE/feature_request.md

• Create feature request template in .github/ISSUE_TEMPLATE/
• Include sections for:
  • Feature description
  • Problem it solves
  • Proposed solution
  • Alternatives considered
  • Additional context

7. .github/PULL_REQUEST_TEMPLATE.md

• Create pull request template
• Include sections for:
  • Description of changes
  • Type of change (bug fix, feature, breaking change, etc.)
  • Related issues
  • Checklist (testing, documentation, etc.)

8. .github/FUNDING.yml

• Add funding configuration file
• Include support/sponsorship information
• Add relevant platform usernames (GitHub Sponsors, Patreon, etc.)

Requirements

• All files should follow industry best practices
• Templates should be clear and easy to use
• Content should be relevant to a web development project
• Files should be properly formatted (Markdown)
• Maintain consistency in tone and style across all files

This pull request was created from Copilot chat.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.