search

18F / site-scanning

The code base for the first Site Scanning engine
https://digital.gov/site-scanning
18 stars 9 forks source link

Digital Dashboard user assessment #391

Closed anjunainaustin closed 4 years ago

anjunainaustin commented 4 years ago

Assess if/how Digital Dashboard can become a Site Scanner user

Acceptance Criteria

  1. Marina understands the boundaries and highlights of what Site Scanner can do enough to relay it accurately to others.
  2. We know which existing product features Marina thinks would add value to Digital Dashboard's short-term and long-term goals.
  3. We gauge the amount of effort required on our end so that DD is fed all the data she wants, and ID'd if/how it fits into our existing roadmap.

Potential constraints to address

  1. We may need to also involve Dan Pomeroy and Justin Grimes into these conversations.
timothy-spencer commented 4 years ago

Pinged Marina in slack and email!

timothy-spencer commented 4 years ago

Pinged in email again. Says she will be in the office tomorrow.

timothy-spencer commented 4 years ago

Had chat with Marina.

  1. I believe Marina understands what we can do and what we can't do (we can scan pretty much as many domains as need be, but we are a scanner, not a crawler), and she understands that we intend to be a service that anybody can query for information about sites.
  2. I think that almost everything we have will be useful if it supports understanding how well a site is implementing the standards in the 21st century IDEA act. The pshtt scan was very interesting to her, though it sounds like pa11y and some sort of mobile-friendly scan might also be useful. The other aspect that is useful is just removing the burden of scanning from them. Apparently it's only doable on a monthly basis right now for them.
  3. I think that this fits very well into our roadmap. We have always had "add more scans" in the roadmap, so if they are able to say what kind of data they want and how it might be collected, we can start adding it. There are only two technical hurdles that I can think of: We might need to add some more dns subdomains to our project from their list, which may or may not be easily accessible. Some of their needs might require crawling or other technically difficult things, like "we need a score on how pretty a website is". Probably not that actual requirement, but something like that might be hard to do.

The big takeaway is that she's interested in knowing more and starting "real talk". She wanted to know costs, and I said that this was up in the air right now. She is expecting you to contact her soon!