Your first week, by role
When a lead accepts your “I can help” request, you receive the project’s start link: the team’s group or the project repository. Begin with one small task you can finish in your first week.
Before you start
Section titled “Before you start”- Read the project’s brief on hasanat.dev, then its full spec when the team shares it.
- Introduce yourself in the team’s group in two lines: your role and the time you have.
- Agree on your first task and a check-in date with the lead.
- Record the task in the project’s GitHub issues if the team tracks its work there.
Starter tasks by role
Section titled “Starter tasks by role”These are suggested first tasks for each role. Effort is an estimate: small, medium, or large. Choose with the lead what fits your time.
Development
Section titled “Development”- Set up repository and development environment (small): document local setup and verify the production build.
- Build the first core user flow (large): implement the smallest end-to-end flow that delivers real user value.
- Deploy a testable version (medium): deploy a preview URL and document how to verify it.
Start from Build from the starter and the starter prompt.
Design
Section titled “Design”- Map the primary user journey (small): map screens and decisions from entry to successful outcome.
- Review mobile and bidirectional UX (medium): review Arabic RTL and English layouts on mobile.
See the design system and Arabic and RTL.
Content
Section titled “Content”- Collect and review trusted sources (medium): document content sources and verify their accuracy.
- Write Arabic and English product copy (medium): prepare clear core copy in both languages.
Never generate or paraphrase Quran or hadith text: copy it verbatim from a verified source. See the resource bank.
Translation
Section titled “Translation”- Review translation and text direction (medium): review meaning, terminology, and interface direction in both languages.
Research
Section titled “Research”- Validate the user need (medium): talk to five potential users and summarize their hardest problems.
Testing
Section titled “Testing”- Create a focused test plan (small): cover the core flow, mobile, accessibility, and error states.
- Test with three real users (medium): record what worked, what confused users, and what should change.
See run a pilot with real users (in Arabic).
Community
Section titled “Community”- Recruit community testers (medium): identify the audience and invite a small group to test the first version.
Marketing
Section titled “Marketing”- Prepare the launch message (small): write a clear announcement explaining the problem, benefit, and how to try it.
Operations
Section titled “Operations”- Organize the first-week plan (small): define owners, the first three outcomes, and check-in dates.
- Define one concrete contribution (small): turn the offer to help into one clear, completable task.
At the end of the week
Section titled “At the end of the week”Tell the team in two lines what you finished, what blocked you if anything, and your next step.