community readiness

.github/ISSUE_TEMPLATE/accessibility_issue.md

@@ -0,0 +1,39 @@
+---
+name: Accessibility issue
+about: Report an accessibility barrier in the app, docs, or demo
+title: "Accessibility: "
+labels: "accessibility, needs accessibility review"
+assignees: ""
+---
+
+## Summary
+
+What accessibility barrier did you encounter?
+
+## Location
+
+- URL or route:
+- File or document:
+- Browser/device:
+
+## Impact
+
+Who is affected and how?
+
+## Assistive Technology
+
+If relevant, include screen reader, keyboard-only, browser zoom, voice control, or other tools used.
+
+## Steps to Reproduce
+
+1.
+2.
+3.
+
+## Suggested Fix
+
+If you have a suggestion, add it here.
+
+## Screenshots
+
+Add screenshots if useful. Do not include personal, student, school, or sensitive data.

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,50 @@
+---
+name: Bug report
+about: Report something that is broken or behaving unexpectedly
+title: "Bug: "
+labels: "type: bug, needs triage"
+assignees: ""
+---
+
+## Summary
+
+What is broken?
+
+## Steps to Reproduce
+
+1.
+2.
+3.
+
+## Expected Behavior
+
+What did you expect to happen?
+
+## Actual Behavior
+
+What happened instead?
+
+## Area
+
+- [ ] Public landing page
+- [ ] Demo login
+- [ ] Student experience
+- [ ] Teacher experience
+- [ ] Admin/content experience
+- [ ] Backend/API
+- [ ] Documentation
+- [ ] Other
+
+## Environment
+
+- Browser:
+- Device:
+- URL or route:
+
+## Screenshots or Logs
+
+Add screenshots or logs if useful. Do not include personal, student, school, or sensitive data.
+
+## Notes
+
+Anything else maintainers should know?

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Security report
+    url: https://github.com/mrwrite/echoed/blob/main/SECURITY.md
+    about: Please report vulnerabilities through the security policy.
+  - name: Public demo guide
+    url: https://github.com/mrwrite/echoed/blob/main/docs/public-demo.md
+    about: Review demo roles, shared credentials, limitations, and feedback paths.

.github/ISSUE_TEMPLATE/educator_curriculum_feedback.md

@@ -0,0 +1,41 @@
+---
+name: Educator or curriculum feedback
+about: Share bounded feedback on lesson flow, classroom fit, curriculum, or facilitation
+title: "Educator feedback: "
+labels: "educator feedback, curriculum, needs triage"
+assignees: ""
+---
+
+## Your Context
+
+Role or perspective:
+
+Grade band or learner context:
+
+## What You Reviewed
+
+- [ ] Landing page
+- [ ] Public demo guide
+- [ ] Student demo flow
+- [ ] Teacher demo flow
+- [ ] Admin/content flow
+- [ ] Specific lesson or activity:
+- [ ] Other:
+
+## Feedback
+
+What felt useful?
+
+What felt unclear, inaccurate, inaccessible, or culturally off?
+
+What would make this more useful for educators or learners?
+
+## Suggested Change
+
+If you have a concrete suggestion, add it here.
+
+## Recognition
+
+- [ ] I am comfortable being publicly credited if this feedback leads to a visible change.
+- [ ] Please do not publicly credit me.
+- [ ] Ask me first.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,41 @@
+---
+name: Feature request
+about: Suggest a feature or improvement
+title: "Feature: "
+labels: "type: feature, needs triage"
+assignees: ""
+---
+
+## Summary
+
+What should EchoEd add or improve?
+
+## Problem
+
+What problem would this solve?
+
+## Audience
+
+- [ ] Student
+- [ ] Educator
+- [ ] Parent/family
+- [ ] School or organization admin
+- [ ] Contributor/developer
+- [ ] Community organizer
+
+## Proposed Direction
+
+Describe the smallest useful version of this feature.
+
+## Alternatives
+
+What could work instead?
+
+## Acceptance Criteria
+
+- [ ]
+- [ ]
+
+## Notes
+
+Include links, examples, or context if useful.

.github/ISSUE_TEMPLATE/good_first_issue_proposal.md

@@ -0,0 +1,38 @@
+---
+name: Good first issue proposal
+about: Propose a small, beginner-friendly task
+title: "Good first issue: "
+labels: "good first issue, needs triage"
+assignees: ""
+---
+
+## Task
+
+What small task should a new contributor be able to complete?
+
+## Area
+
+- [ ] Documentation
+- [ ] Frontend
+- [ ] Backend
+- [ ] Testing
+- [ ] Accessibility
+- [ ] Demo
+- [ ] Curriculum tooling
+
+## Suggested Files or Routes
+
+List likely files, folders, or routes.
+
+## Acceptance Criteria
+
+- [ ]
+- [ ]
+
+## Validation
+
+How should a contributor know the task is complete?
+
+## Notes for First-Time Contributors
+
+Add any context that would help someone new.

.github/ISSUE_TEMPLATE/historical_accuracy_source_concern.md

@@ -0,0 +1,40 @@
+---
+name: Historical accuracy or source concern
+about: Report a historical, source, cultural framing, or curriculum accuracy concern
+title: "Historical review: "
+labels: "historical accuracy, curriculum, needs historical review"
+assignees: ""
+---
+
+## Concern
+
+What appears inaccurate, weakly sourced, overgeneralized, or culturally concerning?
+
+## Location
+
+Where did you see it?
+
+- URL or route:
+- Lesson, activity, or document:
+- Screenshot or quoted excerpt if useful:
+
+## Why It Matters
+
+Explain the historical, cultural, learner, or classroom impact.
+
+## Suggested Sources or Framing
+
+If you have suggested sources, terminology, or framing, add them here. This is helpful but not required.
+
+## Urgency
+
+- [ ] Blocks public sharing
+- [ ] Needs review before classroom use
+- [ ] Improvement or clarification
+- [ ] Question for maintainers
+
+## Recognition
+
+- [ ] I am comfortable being publicly credited if this feedback leads to a visible change.
+- [ ] Please do not publicly credit me.
+- [ ] Ask me first.

.github/pull_request_template.md

@@ -0,0 +1,47 @@
+# Summary
+
+What changed?
+
+# Motivation
+
+Why is this change needed?
+
+# Type of Change
+
+- [ ] Documentation
+- [ ] Frontend
+- [ ] Backend
+- [ ] Tests
+- [ ] Accessibility
+- [ ] Demo
+- [ ] Curriculum/community review
+- [ ] Other
+
+# Test Plan
+
+List the checks you ran.
+
+- [ ] Backend tests
+- [ ] Frontend build
+- [ ] Frontend unit tests
+- [ ] Demo smoke test
+- [ ] Manual review
+- [ ] Not run. Explain below.
+
+If you could not run a check, explain why:
+
+# Screenshots
+
+Add screenshots for visible UI changes.
+
+# Accessibility Check
+
+Describe any accessibility impact, including keyboard, contrast, labels, readable text, and mobile layout where relevant.
+
+# Community or Curriculum Impact
+
+Does this affect educator review, historical accuracy, source quality, learner experience, community language, or contribution flow?
+
+# Notes
+
+Anything maintainers should know?