webrune-tim / webrune-tim/The-Autonomy-Protocol
Add an FAQ section to the homepage
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Problem & Context
The Educator Portal homepage currently lacks a clear, accessible FAQ section. Prospective teachers, administrators, and mentors need quick, straightforward answers to understand the purpose of The Autonomy Protocol (TAP), how it operates in practice, and how to get involved or support the project.
Scope of Work
1. Content & Copy Architecture
Draft candid, authoritative answers for key educator questions, categorized by topic:
Protocol Overview & Philosophy
- What is The Autonomy Protocol (TAP)?
- Core definition: An open-source framework and curriculum designed to teach practical self-governance, personal accountability, and executive functioning skills.
- Why TAP? (The Philosophical Anchor)
- The problem with compliance-based education vs. the value of individual agency, mutual honesty, and real-world consequences.
- How does TAP work in a classroom or cohort?
- Practical mechanics: How mentors facilitate student-owned contracts, daily/weekly inventory check-ins, and habit tracking without coercive monitoring.
Logistics & Engagement
- How can educators or curriculum writers contribute?
- Ways to contribute lesson materials, refine rubrics, or test modules in live cohorts.
- How can I contact the TAP team?
- Direct communication channels for questions, feedback, or institutional pilots.
- How can I support or donate to the project?
- Contribution pathways for open-source sponsorship, material donations, or platform hosting support.
2. UI / Component Requirements
- Accessible accordion or expandable list pattern (
<details>/<summary>or ARIA-compliant disclosure widgets). - High scannability with clean typography and distinct expand/collapse states.
- Direct deep-linking support (anchor IDs for individual questions) so specific answers can be shared via URL.
- Responsive design verified across mobile and desktop viewports.
Acceptance Criteria
- FAQ copy written, edited for clarity, and free of vague educational buzzwords.
- Accessible, keyboard-navigable FAQ component built and integrated into the educator landing page.
- Anchor tags added to each question for direct linking.
- Contact and donation links route to verified endpoints/forms.
- Component renders cleanly on both desktop and mobile viewports.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the educator landing page and inspect the existing homepage structure and components before choosing the FAQ insertion point. Build the specified accessible expandable FAQ with deep links, verified contact and donation destinations, and responsive desktop/mobile presentation; done means every acceptance criterion is met.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- content, frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100