[6-Month Roadmap](https://github.com/EqualifyEverything/equalify/issues/577)
[Hung Scan Postmortem](
https://docs.google.com/document/d/1nSx8ZcpJF-7f45tmRJZL9vz0b8sC43rnByCf5dLDfH8/edit?tab=t.0)
[Dev Report - Period ending March 6th](https://equalify.uic.edu/reports/2026-03)
[Dev Report - Period ending March 31st](https://equalify.uic.edu/reports/2026-04)
# New/Discussion
- [ ] Still waiting on RED plugin deployment
- [ ] Weird issue:
- Scanner->results webhook can be:
- OK
- Error
- but also Error ... Error ... OK
- Means Count on errors is tricky/unclear to user: if I scan 50 pages, I could get 40 (or 80!) errors but still have 50 successful scans
- Options
- OK overrides/drops errors from table: drops data but simplest/does what it says UX. Is first try error data important?
- No retry: simplest to understand but uh kinda counter to the goal, which is scanning
- Retain but only show "final" errors in UX: most complete but not sure easiest way to implement
- [ ] Investigate strange PDF metrics. The `scanStarted` metric is reporting _very_ high numbers of PDF scans, and PDF-heavy audits are showing some very high blocker count numbers. We should look into this!
# Outstanding
@azdak To Dos:
- [x] (Michael 3/5) https://github.com/EqualifyEverything/equalify/issues/589
- [x] (Michael 3/5) #590 Double-check email delivery fix is working
- [x] (@azdak proposed 3/17) Add URL count to chart tooltip and scans table
- [x] Fix Wordpress plugin - [Review here](https://gist.github.com/azdak/6517b32c200f3e4be4b7ffb95a212ede)
- [x] [Service Request SOP](https://docs.google.com/document/d/1o_onHA5kJoxX2c2PgIuoUP6UkkZv6FJ6e8Ga6-Sz2K8/edit?usp=sharing)
- [x] Review User Documentation from Amanda
- [x] Technical Notes (made in doc)
- [x] Complete Survey
- [x] [Requested changes from RED team](https://github.com/EqualifyEverything/equalify/issues/602) for new WP plugin
- [x] [Inconsistent Link Target bug](https://github.com/EqualifyEverything/equalify/issues/601)
- [x] [Pagination bug](https://github.com/EqualifyEverything/equalify/issues/603)
@heythisischris To Dos:
- [ ] (proposed 1/22) Fix URL for prod Hasura
- [ ] Coordinate meeting w/ Helen & Michael on documentation workflow AND ask about how Equalify communications are handled, what team is responsible, and how we can properly coordinate updates / FAQ / etc.
- [x] Have a conversation with Blake & Dean to separate out PDF costs from Equalify costs in AWS account, also get a sense of what our cost ceiling is, limits, their recommendations, etc.
- [x] Work on DB Schema version control and Hasura metadata version control
- [ ] Include in CI/CD
- [x] Building Chrome extension prototype
- [x] Equalify Tech Spec sheet (@heythisischris 3/16)
- [x] (roadmap, 3/19) crawl module
- [x] add Crawl button to build audit
- [x] set up lambda for crawling
- [x] sitemapper? crawlee? (We decided on Sitemapper!)
- [x] set up API endpoint
- [x] accepts options (depth, etc) (No longer doing depth, out of scope)
- [x] on return, table of toggleable URLs in Build Audit
- [x] Improved report generation script, references previous reports.
- [x] Talk to Amanda to discuss whether she wants to be involved in monthly reports (either included, or review, or release).
- [ ] [Duplicate Blocker ID](https://github.com/EqualifyEverything/equalify/issues/600)
- [ ] Get clean AWS account provisioned (talk to Dean)
# Future Sprints
(pending development priority decision, and in no particular order)
### FOSS Sprint aka Infrastructure Week (1-2 weeks)
- [ ] **Determine IaC/Provisioning Framework (Terraform, OpenTofu, whatever)**: there are a variety of options for Infrastructure as Code (IaC) and we need to look at the tradeoffs for each and settle on one
- [ ] **Create BUILD SCRIPTS ๐**: Write IaC scripts to provision all the infrastructure-ie lambdas, DB, and relationships between them- needed to run an Equalify instance
- [ ] **Determine deployment strategy**: Figure out how to handle deployment, ie how code (and code updates) are pushed to the provisioned infrastructure
- [ ] **Provisioning & Deployment Documentation**: Technical documentation for deployment
- [ ] **User Documentation**: Developer-focused Readme to introduce how to use the app from a high level.
### Design & Maintenance Sprint (1-2 weeks)
- [ ] Get alignment on overall visual direction and palette
- [ ] Branding: Defining how branding is handled on the system.
- [ ] Design System: Atomic system or Storybook for component uniformity
- [ ] Darkmode ๐
- [ ] Mobile breakpoints
- [ ] Style and Code Cleanup: Finish componentizing, minimize global styles, and code cleanup
- [ ] Discussion/Fit into roadmap (@azdak 3/16): Roll-up reporting, eg being able to get a summary view of several audits at once
- [ ] Discussion/Fit into roadmap (@azdak 3/16): user<->audit groups and/or more fine-grained control over what each user sees on the audit listing page
### Onboard Features Sprint (1-2 weeks)
- [ ] **Site onboarding features**
- [ ] Lambda for site crawling
- [ ] Integrate onboarding features into Build Audit
- [x] Allow external, linked CSVs as basis for Audit URLs (with regular or just-in-time on-scan re-scrapes), allowing WordPress plugin integration
- [ ] CSV User import
# Backlog/Blocked
- [ ] (Liaisons Meeting 3/26) Add UIC Logo
- For now, add UIC logo inside of current static asset (Equalify logo)
- In future, consider adding admin-customizable logo image (or we could let open source deployments dictate via environment variable or image).
- [ ] Help text first pass
- [ ] ID icon areas
- [ ] Refactor HelperTooltip component
- [ ] Write help text
- [ ] Integrate error reporting into "blockers over time" scans table (also possibly the graph?)
- [ ] Discussion/Fit into roadmap (@azdak 3/16): the eternal Custom Rules question
- [ ] Discussion/Fit into roadmap (@azdak 3/16): the even more eternal "exclude the CMS header/footer" question ๐
- [ ] (@azdak / @heythisischris proposed 2/4) Add wiki-style issue descriptions for blocker page, potentially open-source repo. LLM for single blocker issue description and next steps generation?