Auditing repositories for DPG compliance and adaptability

[saurabhlevin]

From James' comment on slack:
Have you performed a more detailed audit of those two repositories in terms of reuse/adaptation to new contexts? For example:

• I see files like risk_score_combined_till_Aug_2024.csv that are specific to CDL’s deployments in the current states.
• views.py has code specific to Assam.
• The GeoTypes class in models.py is specific to India. Instead, admins should be able to control the available choices (e.g. make this into a Model rather than a TextChoices).
• The import_data.py management command is specific to Assam. It should perhaps be moved out of this repo e.g. as a separate Django app that depends on this repo’s Django app.
• When I last reviewed IDS-DRR-Frontend, I noticed deployment-specific hardcoding in these files (non-exhaustive):
  • app/[locale]/
  • layout.tsx
  • about-us/components/
  • collaboratingPartner.tsx
  • supportedBy.tsx
  • teams.tsx
  • analytics/components/default-output-window.tsx
  • components/
  • about.tsx
  • footer.tsx
  • Video.tsx
  • components/mobile-nav.tsx
  • config/
  • consts.ts
  • site.ts