Skip to content

Week of 2/16 - Development Standup Thread #586

@azdak

Description

@azdak

6-Month Roadmap

New

  • (2/18 roadmap meeting) "Teams" section in https://equalify.uic.edu/user-guide/user-roles is pretty unclear and leading to some confusion about a "team" feature, and not a reference to the Equalify instance. Need to clarify this language
  • (2/18 roadmap meeting) Need to add specifics on which rulesets veraPDF and axe-core are using to scan to documentation

Outanding

@azdak To Dos:

  • (@azdak proposed 2/9) Add created by: to Audits screen
  • (From 2/5 Service Team Meeting) Audits page filtering
  • (@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) Audits screen: Add Sort by to table view
  • 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

@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.
  • (From 2/5 Service Team Meeting) Look into production email deliverability (reported from testing)
  • Quick scan wrap-up
    • 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
  • Fix rate-limit issues in Equalify Hub!
  • 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?)

Metadata

Metadata

Labels

PunchlistOmnibus thread for tracking sprint/to-do progress

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions