Merge kc-pit-2026 into main

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,4 +1,4 @@
-name: "🐞 Bug report"
+name: " Bug report"
 description: "File a reproducible problem with the software."
 title: "[Bug]: <short summary>"
 labels: ["bug", "triage"]
@@ -62,11 +62,13 @@ body:
         - Windows
         - macOS
         - Linux
+        - iPad
+        - Surface Tablet
         - Other (specify below)
   - type: input
     id: platform_other
     attributes:
       label: Other environment details
   - type: markdown
     attributes:
-      value: "Thank you for helping us improve! 🙏"
+      value: "Thank you for helping us improve! "

.github/ISSUE_TEMPLATE/config.yml

@@ -1,7 +1,7 @@
 blank_issues_enabled: false
 contact_links:
-  - name: 💬 General question / discussion
-    url: https://github.com/uw-ssec/project-template/discussions
+  - name: General question / discussion
+    url: https://github.com/SSDALab/respondent-driven-sampling/discussions
     about: Please ask questions in Discussions instead of opening an issue.
 issue_templates:
   - name: Bug report

.github/ISSUE_TEMPLATE/documentation.yml

@@ -1,4 +1,4 @@
-name: "📚 Documentation gap"
+name: " Documentation gap"
 description: "Report missing or confusing docs."
 title: "[Docs]: <short summary>"
 labels: ["documentation"]

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -1,4 +1,4 @@
-name: "✨ Feature request"
+name: " Feature request"
 description: "Suggest an idea or enhancement."
 title: "[Feature]: <short summary>"
 labels: ["enhancement", "triage"]

.github/ISSUE_TEMPLATE/performance_issue.yml

@@ -1,4 +1,4 @@
-name: "🐢 Performance issue"
+name: " Performance issue"
 description: "Report slowness, excessive memory, etc."
 title: "[Perf]: <short summary>"
 labels: ["performance", "triage"]

.github/pull_request_template.md

@@ -5,35 +5,35 @@
   PRs that follow this template are easier to review and merge.
 -->
 
-## 📄 Description
+## Description
 
 <!-- What does this PR change? Why is it needed? -->
 
-## ✅ Checklist
+## Checklist
 
 -   [ ] Tests added/updated where needed
 -   [ ] Docs added/updated if applicable
 -   [ ] I have linked the issue this PR closes (if any)
 
-## 🔗 Related Issues
+## Related Issues
 
 Resolves #\<issue-number>
 
-## 💡 Type of change
+## Type of change
 
-| Type             | Checked? |
-| ---------------- | -------- |
-| 🐞 Bug fix       | [ ]      |
-| ✨ New feature   | [ ]      |
-| 📝 Documentation | [ ]      |
-| ♻️ Refactor      | [ ]      |
-| 🛠️ Build/CI      | [ ]      |
-| Other (explain)  | [ ]      |
+| Type            | Checked? |
+| --------------- | -------- |
+| Bug fix         | [ ]      |
+| New feature     | [ ]      |
+| Documentation   | [ ]      |
+| Refactor        | [ ]      |
+| Build/CI        | [ ]      |
+| Other (explain) | [ ]      |
 
-## 🧪 How to test
+## How to test
 
 <!-- Steps reviewers can run to verify functionality -->
 
-## 📝 Notes to reviewers
+## Notes to reviewers
 
 <!-- Anything specific reviewers should know before starting -->

.github/workflows/azure-webapp-deploy.yml → .github/workflows/azure-webapp-deploy-rds-app-kc-prod.yml

@@ -1,9 +1,9 @@
-name: RDS MAIN Build and Deploy Monolithic React + Node app to Azure
+name: Deploying kc-pit-2026 branch to rds-app-kc prod slot
 
 on:
   push:
     branches:
-      - main # or your deployment branch
+      - kc-pit-2026 # or your deployment branch
 
 jobs:
   build-and-deploy:
@@ -57,7 +57,7 @@ jobs:
       - name: Deploy to Azure Web App
         uses: azure/webapps-deploy@v3
         with:
-          app-name: rds-main # Replace with your Azure App Service name
+          app-name: rds-app-kc # Replace with your Azure App Service name
           slot-name: "Production"
-          publish-profile: ${{ secrets.AZURE_PUBLISH_PROFILE }}
+          publish-profile: ${{ secrets.AZURE_PUBLISH_PROFILE_rds_app_kc}}
           package: ./server

.github/workflows/azure-webapp-deploy-test.yml → .github/workflows/azure-webapp-deploy-rds-app-kc-test.yml

@@ -1,9 +1,9 @@
-name: RDS TEST Build and Deploy Monolithic React + Node app to Azure
+name: Deploying kc-pit-2026-test branch to rds-app-kc test slot
 
 on:
   push:
     branches:
-      - test # or your deployment branch
+      - kc-pit-2026-test # or your deployment branch
 
 jobs:
   build-and-deploy:
@@ -57,7 +57,7 @@ jobs:
       - name: Deploy to Azure Web App
         uses: azure/webapps-deploy@v3
         with:
-          app-name: rds-test # Replace with your Azure App Service name
-          slot-name: "Production"
-          publish-profile: ${{ secrets.AZURE_WEBAPP_PUBLISH_PROFILE_RDS_TEST_DEPLOY }}
+          app-name: rds-app-kc # Replace with your Azure App Service name
+          slot-name: "test"
+          publish-profile: ${{ secrets.AZURE_PUBLISH_PROFILE_rds_app_kc_test }}
           package: ./server

.github/workflows/docs.yml

@@ -0,0 +1,23 @@
+name: Deploy MkDocs to GitHub Pages
+
+on:
+  push:
+    branches:
+      - main
+  workflow_dispatch:
+
+permissions:
+  contents: write
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - uses: actions/setup-python@v5
+        with:
+          python-version: '3.x'
+      - run: pip install -r docs/requirements.txt
+      - run: mkdocs gh-deploy --force

.gitignore

@@ -66,4 +66,8 @@ desktop.ini
 
 # Generated seed PDFs
 scripts/seeds/
-scripts/coupons/
+scripts/coupons/
+
+# Pulumi
+infra/node_modules/
+infra/Pulumi.*.yaml

.zenodo.json

@@ -0,0 +1,16 @@
+{
+  "upload_type": "software",
+  "communities": [
+    { "identifier": "uw-ssec" }
+  ],
+  "grants": [
+    { "id": "10.13039/100000001::2142964" }
+  ],
+  "related_identifiers": [
+    {
+      "identifier": "https://ssdlab.github.io/respondent-driven-sampling/",
+      "relation": "isDocumentedBy",
+      "resource_type": "publication-softwaredocumentation"
+    }
+  ]
+}

CITATION.cff

@@ -0,0 +1,64 @@
+cff-version: 1.2.0
+title: "Respondent-Driven Sampling (RDS) Application"
+message: "If you use this software, please cite it using the metadata from this file."
+type: software
+license: BSD-3-Clause
+repository-code: "https://github.com/SSDALab/respondent-driven-sampling"
+url: "https://ssdalab.github.io/respondent-driven-sampling/"
+abstract: >
+  An open-source web application for conducting Respondent-Driven Sampling (RDS)
+  surveys of unsheltered populations. Built for the King County Regional Homelessness
+  Authority's Point-in-Time count; designed for reuse by other cities and localities.
+authors:
+  - name: "University of Washington Scientific Software Engineering Center (SSEC)"
+  - given-names: Ihsan
+    family-names: Kahveci
+  - given-names: June
+    family-names: Yang
+  - given-names: Emily
+    family-names: Porter
+  - given-names: Zack
+    family-names: Almquist
+  - given-names: Elizabeth
+    family-names: Deng
+  - given-names: KelliAnn
+    family-names: Ramirez
+  - given-names: Jasmine
+    family-names: Vuong
+  - given-names: Hannah
+    family-names: Lam
+  - given-names: Ella
+    family-names: Weinberg
+  - given-names: Arushi
+    family-names: Agarwal
+  - given-names: Devanshi
+    family-names: Desai
+  - given-names: Aryan
+    family-names: Palave
+  - given-names: Kaden
+    family-names: Kapadia
+  - given-names: Hrudhai
+    family-names: Umashankar
+  - given-names: Liya
+    family-names: Finley Hutchison
+  - given-names: Hana
+    family-names: Amos
+  - given-names: Zack
+    family-names: Crouse
+  - given-names: Kristen L
+    family-names: Gustafson
+  - given-names: Anant
+    family-names: Mittal
+  - given-names: Natalie
+    family-names: Robbins
+  - given-names: Anshul
+    family-names: Tambay
+keywords:
+  - respondent-driven sampling
+  - RDS
+  - homelessness
+  - point-in-time count
+  - survey
+  - open-source
+version: "1.0.0"
+date-released: "2026-02-20"

CONTRIBUTING.md

@@ -0,0 +1,41 @@
+# Contributing to RDS App
+
+Thank you for your interest in contributing. This document explains how to run the app, run tests, open issues, and submit pull requests.
+
+## How to run the app
+
+Follow the [Setup Instructions](README.md#setup-instructions) in the main README. You will need:
+
+- Node.js (see repo or CI for version)
+- MongoDB connection string and Twilio credentials in `server/.env`
+
+## How to run tests
+
+- **Server:** From the repo root, run `cd server && npm test`. For coverage: `cd server && npm run test:coverage`.
+- **Client:** Run lint with `cd client && npm run lint`. The client does not currently define a test script in package.json.
+- **Lint:** Run `npm run lint` in both `client/` and `server/` before pushing.
+
+## Pre-commit
+
+We use [pre-commit](https://pre-commit.com/) for consistent formatting and checks. Before pushing, run:
+
+```bash
+pre-commit run --all-files
+```
+
+CI also runs these hooks on push/PR to `main`.
+
+## How to open issues
+
+Use the [issue templates](.github/ISSUE_TEMPLATE/) when opening a new issue (bug report, feature request, documentation gap, or performance issue). Search existing issues first to avoid duplicates.
+
+## How to submit pull requests
+
+1. Open a new issue or comment on an existing one to discuss the change if it’s substantial.
+2. Create a branch from `main` (or the target branch).
+3. Make your changes and run tests and pre-commit locally.
+4. Open a pull request using the [PR template](.github/pull_request_template.md). Link any related issue in the description.
+
+## Code of Conduct
+
+This project adheres to the [Contributor Covenant Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code.