This directory contains template files for setting up a comprehensive GitHub Wiki for your CivicTechWR project.
- Go to your GitHub repository settings
- Scroll down to "Features" section
- Check "Wikis" to enable the wiki feature
Copy the content from these template files to create corresponding pages in your GitHub wiki:
| Template File | Wiki Page Name | Purpose |
|---|---|---|
Home.md |
Home | Main wiki landing page |
Project-Overview.md |
Project-Overview | Comprehensive project description |
Team-and-Roles.md |
Team-and-Roles | Team member information |
Community-Partners.md |
Community-Partners | Stakeholder relationships |
Season-Timeline.md |
Season-Timeline | 12-week project schedule |
User-Research.md |
User-Research | Community research findings |
Technical-Architecture.md |
Technical-Architecture | System design details |
Meeting-Notes.md |
Meeting-Notes | Weekly meeting documentation |
Decision-Log.md |
Decision-Log | Important project decisions |
- Replace all placeholder content (marked with [brackets])
- Update navigation links to match your project structure
- Add project-specific sections as needed
- Update project status regularly
- Document key decisions and changes
- Keep team and partner information current
- Record meeting notes and progress updates
- ✅ Central hub for all project information
- ✅ Clear team roles and responsibilities
- ✅ Decision tracking and rationale
- ✅ Meeting notes and action items
- ✅ Transparent project progress
- ✅ Clear ways for community to get involved
- ✅ Impact measurement and reporting
- ✅ Accessible documentation for all skill levels
- ✅ Season timeline and milestone management
- ✅ Community partnership documentation
- ✅ Demo Day preparation resources
- ✅ Knowledge preservation for future contributors
- ✅ Handoff documentation for post-season
- ✅ Community impact story for funding/partnerships
- ✅ Technical documentation for maintenance
- Write for multiple audiences (technical and non-technical)
- Keep information current and accurate
- Use clear, accessible language
- Include visuals when helpful (screenshots, diagrams)
- Use consistent navigation across pages
- Link related pages together
- Create clear hierarchies and categories
- Make important information easy to find
- Weekly: Update meeting notes and progress
- Bi-weekly: Review and update team/role information
- Monthly: Update impact metrics
- Season milestones: Major updates to overview and timeline
Based on your project needs, consider adding:
API-Documentation.md- Technical integration detailsDevelopment-Setup.md- How to contribute codeTesting-Strategy.md- QA and accessibility testingDeployment-Guide.md- How system is deployed
User-Guides.md- How community members use the systemAccessibility-Guide.md- Ensuring inclusive designFAQ.md- Common questions and answersFeedback-and-Support.md- How to get help or provide input
Issue-Tracking.md- GitHub project integrationDemo-Day-Preparation.md- Presentation planningRisk-Management.md- Project risks and mitigationResource-Planning.md- Budget and resource allocation
- Link wiki pages to project issues and milestones
- Reference wiki documentation in issue templates
- Link to main CTWR documentation for guidelines
- Reference community policies and procedures
- Connect to organization-wide resources
- Share wiki links in community discussions
- Use wiki for Demo Day presentation preparation
- Reference in partner communications
- Ask in weekly community meetings
- Use community Slack/Discord for wiki questions
- Reference main CTWR documentation repository
📚 Template Information:
- Created for: CivicTechWR Project Template
- Compatible with: GitHub Wikis
- Framework: Civic tech workflow with 12-week lifecycle
- Maintenance: Update placeholders and customize for your project