/hackforgaza-team-17

Hackathon - Hack for Gaza

Primary LanguageTypeScript

Hack for Gaza 🇵🇸

Hackathon - Emergency Hack for Gaza organised by Deen Developers

hackforgaza-team-17

Selected Problem Statement

Education & Awareness

We are building an app to humanise the dehumanised victims of genocide in Palestine.

Solution Objective

Is to inform as many discerning people on the fence about genocidal oppression that is being concealed from them, and to encourage them to an active stance against oppression (particularly with the pertinent Palestine issue).

Solution Overview

A platform for visitors “easily see” the evidence-based timeline of genocidal incidents, and the identity of their victims.

User Persona

  1. Up to 90% which could be on the fence.
  2. Want to be good, ethical people. Want to do good by society.
  3. Either too lazy or too busy to get facts or figures for themselves, or pick up a history book.

Features and Functionality

  1. Humanise i. Memorialise their identity and their memories

    • name
    • photographs, videos
    • age, gender

  2. Journal of Oppression

  3. Victims 1. Killed 2. Maimed 3. Injured 4. Detained

  4. Facilities/Infrastructure 1. Destroyed 2. Damaged

  5. Capture the Countless Modes of Oppression 1. Explosions 2. Assaults + Torture 3. Detentions 4. Occupations 5. Verbal Aggression

  6. Credibility of the Above

  7. Archiving evidence (for availability)

  8. Categorising evidence (i.e. primary, secondary)

  9. Providing reliable stats

User Flow

  1. Stay up to date with feed of incidents.
  2. Can see Individual stats of incident.
  3. See aggregate (major status, “headline forming”) stats. 1. killed 2. maimed 3. injured 4. detention 5. dispossessed.
  4. Explore all of the disparate pieces of information that document the genocide using the dashboard:
  5. See incidents on a (timeline-synced) map. 1. See time and place of incident (visuospatial). 2. See victims of the incidents. 3. See damage done to facilities and infrastructure by the incidents. 4. See evidence documenting the incidents.
  6. See aggregate (major status, “headline forming”) stats. 1. Click on them to view details.
  7. All of above user flows should lead to share (CTA).

Timeline and Milestones (remember to utilise the kanban board!)

  1. Milestone 1: Define data format and infrastructure to store the data.
  2. Milestone 2: Agree on API/contracts.
  3. Milestone: Frontend
  4. Milestone 3: Design
  5. Milestone 4: Userflow – Data Entry
  6. Milestone 5: Userflow – Incidents Feed
  7. Milestone 6: Userflow – Dashboard
  8. Milestone 7: Userflow – Details for Incidents, Victims, Infrastructure, Testimonies

Resources Needed

  1. Hosting: Vercel/Firebase Hosting
  2. Storage: Firebase Storage
  3. Database: DBMS + VM?

Team Responsibilities

  1. Saidur - PM (Design & GTM)
  2. Tej - Backend Engineer (Design & node.js)
  3. Abu - Backend Engineer (node.js, DevOps)
  4. Yasir - Full-stack (Design & React)

Challenges and Risks

References and Supporting Documents

  1. Not applicable