Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pages & Performance Refactor #494

Open
8 of 23 tasks
azdak opened this issue Nov 25, 2024 · 1 comment
Open
8 of 23 tasks

Pages & Performance Refactor #494

azdak opened this issue Nov 25, 2024 · 1 comment
Assignees

Comments

@azdak
Copy link
Collaborator

azdak commented Nov 25, 2024

Currently most actions and functionality in the app is based on Properties, which contain actual individual urls that can only be added by URL OR sitemap. This is both confusing to users and makes basic functionality like scanning across subdomains or tracking the status of homepages across several URLs difficult or impossible. This update will make Pages the fundamental entity in Equalify, and make Properties tag-like containers of pages that can be added or removed at will. It will also include performance enhancements to improve app responsiveness.

  • Refactor scan polling system to remove Property dependencies and improve performance
    • Refactor/Rewrite
    • Switch to new polling system for ingesting scans from scan.equalify.app
    • Test new polling system
  • New "Pages" screen
    • New getPages API endpoint
    • Pages listing table with serverside pagination
    • New sendPagesToScan API endpoint
    • Enable sending pages to scan from Pages table
    • Pages table styling
  • "Single Page Detail" screen
    • Scan history table
  • New "Add Pages" screen
    • Add new Add Pages API endpoint
    • Add pages input form, accepting multiple urls or sitemaps
    • Connect input form to API
    • Fix Styling
    • CSV Support
  • "Properties" refactor
    • Enable adding to and removing pages/sitemaps from Properties
    • List pages on Property Detail screen
  • Remove Property dependencies from any other existing API calls
  • Add "failed" state to scans (May need further discussion)
@azdak azdak self-assigned this Nov 25, 2024
@bbertucc
Copy link
Member

Thanks. Can you put down a budget and timeline?

@bbertucc bbertucc added this to the December 2 Sprint milestone Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants