A micro-volunteering platform connecting nonprofits with skilled volunteers. Complete quick 5 to 30-minute missions, help verified charities, and earn skill badges.

Nonprofits and community organizations often need quick help with specific tasks (translating a document, designing a flyer, reviewing data, or writing copy), but recruiting full-time volunteers is slow and difficult. MicroMatch breaks volunteering down into bite-sized missions that busy people can complete in under 30 minutes.

Volunteers pick tasks that match their skills, submit their work, and earn verified digital badges for their portfolio. Nonprofits get tasks completed quickly by motivated contributors without endless administrative overhead.

• Bite-sized task feed: Filter by time (≤15 / ≤20 / ≤30 min), cause hashtags, or shortest duration first.
• Volunteer portal: Claim tasks, submit proof of work via file or link, track review status, and collect skill badges.
• Nonprofit dashboard: Post tasks with deadlines and volunteer caps, review submissions, and manage organization badge awards.
• Charity verification: Simple trust verification where nonprofits submit their tax or charity ID, verified against public registries with a verified badge displayed on their tasks.
• Custom badge awards: Organizations define custom award badges (label, color, icon, criteria) automatically awarded upon task approval.
• Worldwide localization: Paraglide provides type-safe, reviewed UI catalogs and locale-prefixed routes; self-hosted LibreTranslate handles user-created task content on the server.
• Email updates: Automated email notifications keep volunteers and organizations informed of approvals and submissions.

These are real recordings of the application in action, captured by the automated test suite and rendered as previews:

Run bun run demoto regenerate: it reseeds, records fresh MP4s, and converts them to GIFs. The reseed is not optional. Demo tasks auto-archive after 30 days of no activity, and the closed-loop recording needs its claim and badge state reset or the badge never appears. See CONTRIBUTING.md for the one-time setup,e2e/demo/for the specs, andplaywright.demo.config.ts for the recording configuration.

The core loop, end-to-end:

sequenceDiagram
  autonumber
  actor V as Volunteer
  actor N as NGO
  participant App as MicroMatch
  participant DB as Appwrite
  participant Mail as Plunk

  N->>App: Post task
  App->>DB: tasks.create (isVerified ← NGO's verification status)

  V->>App: Browse feed, claim task
  App->>DB: claims.create (status=pending)

  V->>App: Submit proof (URL or file)
  App->>DB: claims.update (proofUrl, notes)

  N->>App: Approve claim
  App->>DB: claims.update (status=approved)
  App->>DB: badges.create (matching BadgeDefinitions for org)
  App-->>V: Dashboard updates, badge appears in vault

  Note over N,Mail: Verification flow (parallel)
  N->>App: Submit verification (tax ID + doc)
  App->>DB: ngoVerifications.create (status=pending)
  Note over App: Admin reviews queue with ProPublica enrichment
  App->>DB: status=approved, back-fill tasks.isVerified
  App->>Mail: Send "you're verified" email
  Mail-->>N: 📧

Quick path:

git clone https://github.com/Builder106/micro-match.git
cd MicroMatch
bun install
cp .env.example .env

# Fill in Appwrite + Plunk + ProPublica + LibreTranslate values

bun run dev

The app runs at http://localhost:5173. Full setup (Appwrite resources, environment variables, project layout, conventions) lives in CONTRIBUTING.md.

bun run dev             # dev server with HMR
bun run build           # production build (uses adapter-vercel)
bun run check           # svelte-check + tsc
bun run test            # vitest (459 tests across server / API / components)
bun run test:e2e        # Playwright (run `bunx playwright install chromium` once)
bun run seed            # (re)seed the demo NGO + tasks — run before any demo recording
bun run verify:libretranslate # live health and API-key smoke check
bun run demo            # seed, record the demo suite, convert to GIFs
bun run render-media    # regenerate the README banners + social preview from /static/*.html

Three layers of coverage:

• Server modules (vitest, node) — pure-ish helpers and DB CRUD: tagColors, propublica, email, verifications, badgeDefs, badgeCriteria, badgeAwarder. Mock fetch + Appwrite at the module boundary.
• API endpoints (vitest, node) — /api/verifications, /api/verifications/[userId]/approve, /api/verifications/[userId]/reject, /api/profile/role, /api/badges/manage. Auth gates, validation, multi-step side effects.
• Components (vitest, jsdom) — BadgeChip, EmptyState, ProgressBar, VerificationCard (all four state branches via mocked fetch).
• End-to-end (Playwright, chromium) — public-facing flows: landing, feed, login/signup multi-step, forgot-password, protected route redirect.

bun run test:coveragewrites an HTML report tocoverage/.

The demo suite in e2e/demo/ is deliberately not part of this. It shares Playwright but exists to record the GIFs above, so it's slow by design (slowMo, dwell beats), needs seeded fixtures, and never runs in CI.

Stored in Appwrite TablesDB (see docs/appwrite-schema.md for full schema details):

Plus three Appwrite Teams (volunteers, ngos, admins) for role + moderation gating. Storage uses separate avatars and verifications buckets with file-level permissions. To automatically provision the database tables, attributes, and storage buckets:

bun scripts/setup-appwrite.ts

• CONTRIBUTING.md — local setup, project layout, conventions, PR process
• docs/index.md — platform docs index
• docs/volunteer.md — volunteer guide
• docs/ngo.md — NGO guide
• docs/api.md — full API specification (public & authenticated endpoints)
• docs/appwrite-schema.md — database schema and Appwrite resources specification
• docs/faq.md — FAQ

MIT — see LICENSE.