Week of 3/23 - Development Standup Thread

[azdak]

6-Month Roadmap
Hung Scan Postmortem
Dev Report - Period ending March 6th

New/Discussion

• (@azdak proposed 3/16) Refactor summary view backend to be less stupid
  • Deploy
• Monthly Report - Release around 4/6
• (Liaisons Meeting 3/26) Add UIC Logo

Outstanding

@azdak To Dos:

• (Michael 3/5) Inconsistent Last Scan Date #589
• (Michael 3/5) Email Notification Not Sent #590 Double-check email delivery fix is working
• (@azdak proposed 3/17) Add URL count to chart tooltip and scans table
• Fix Wordpress plugin - Review here
• Service Request SOP
• Review User Documentation from Amanda
  • Technical Notes (made in doc)
  • Complete Survey

@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.
• 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.
• Work on DB Schema version control and Hasura metadata version control
  • Include in CI/CD
• Building Chrome extension prototype
• Equalify Tech Spec sheet (@heythisischris 3/16)
• (roadmap, 3/19) crawl module
  • add Crawl button to build audit
  • set up lambda for crawling
    • sitemapper? crawlee?
  • set up API endpoint
    • accepts options (depth, etc)
  • on return, table of toggleable URLs in Build Audit

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

[bbertucc]

define "less stupid" @azdak - THANKS

[azdak]

@bbertucc 😂 essentially it's just that the code which was querying the database to generate the audit summaries was written in a pretty simple/naive way (read: I wrote it that way lol), which was causing some performance bottlenecks on the really large audits (like 10k+ blockers). It's now been refactored to be a lot more efficient/fast (and should be pushed to live next day or two!)

[bbertucc]

one other thing that came up is defining a SOP around support requests for @azdak

[azdak]

Closed in favor of #597