Week of 2/9 - Development Standup Thread

[azdak]

6-Month Roadmap

Discussion

• Monthly reporting; need Hub functionality for this and to get on a regular schedule
• Starting onboarding sprint
• Hanging scans: eg this or this
• Test Scheduled Scan (see this)

Outanding

@azdak To Dos:

• (From 2/5 Service Team Meeting) Audits page filtering
• Remote CSV integration:
  • audits table: add field { external-csv: URL }
  • add as option/step to set external-csv in build audit
  • on scan:
    • if(external-csv) fetch remote csv
    • (error on audit screen if fails)
    • parse remote csv
    • union with existing audit urls (maintain existing URL IDs)
    • scan then runs as normal
  • Audit Screen: URL table should list URLs from last scan but not be editable
  • Audit Screen: indicate external CSV mode and show editable CSV URL
• (@azdak proposed 2/6) Switch blockers table "Active/Ignore" and "HTML/PDF" filter controls to select boxes instead of custom styled (this should add some more visual uniformity and make styling simpler when we later do a more comprehensive restyle)
• (@azdak proposed 2/9) Add created by: to Audits screen
• (@azdak proposed 2/9) Audits screen: Add Sort by Last Opened

@heythisischris To Dos:

• Debug hung scan errors. Simplest repro is deleting a URL from an audit and then scanning causes a hang, but also should do more testing to trigger hung scan state.
• Raga Job Description [NO LONGER NEEDED]
• (@azdak proposed 1/20) Quick scan

Handle URL scheme properly (no need to add https://)
Add some description indicating this is single URL scan,
Adjust audit page to remove "Scan Now", remove graph, remove scan frequency, email notifications- remove everything above Audit Report
Add new route (instead of /audits/, use /quick-scans/)

• (proposed 1/22) Fix URL for prod Hasura
• (@azdak proposed 1/26) Fix window snapping on filter changes
• (From 2/5 Service Team Meeting) Look into production email deliverability (reported from testing)
• (From 2/5 Service Team Meeting) Add details about how crawling works in Equalify vs other tools
• (From 2/5 Service Team Meeting) Add documentation on user roles to the Equalify Hub
• (From 2/9 Team Meeting) Replace login with waitlist sign up per Jemma request.
• (From 2/9 Team Meeting) Hiding feature requests per Blake request.
• 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.
• Monthly reporting; need Hub functionality for this and to get on a regular schedule

Ability to collect and report on KPIs from 1st of each month
First report delivered March 1st, 2026
Should be able to take in markdown content and format pretty, export to PDF (we can even re-use Equalify Hub Updates page template)
It's just like updates, but we are calling it REPORTS. equalify-docs/reports.

New

• (@azdak / @heythisischris proposed 2/4) Add wiki-style issue descriptions for blocker page, potentially open-source repo.
• (Optional/modular) LLM for single blocker issue description and next steps generation

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): This allows any user to be able to deploy, provisioning the script to run on any external environment.
• Create BUILD SCRIPTS 💀: This sets a template to get the code onto servers that are provisioned.
• Determine deployment strategy: Figure out how to handle deployment
• 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

Onboard Features Sprint (1-2 weeks)

• Site onboarding features
  • Lambda for site crawling
  • Integrate onboarding features into Build Audit
• 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

• 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?)

[azdak]

Closed in favor of #586