[30k]: Search UI

[widal001]

Key links

• Deliverable specification
• Simpler Grants.gov full roadmap
• 10k milestones

Description

• What: Release a basic search page on simpler.grants.gov, potentially hidden behind a feature flag, that allows users to filter and sort funding opportunities, then save and share the link to the results page
• Why: Proves the successful integration of front-end and backend systems and delivers basic search functionality for user testing
• Who: HHS leadership and targeted group of internal and external stakeholders with whom we'd like to conduct user research and testing

Note

For more information about this deliverable please refer to the deliverable specification linked above

[sarahknoppA6]

@sumiat @widal001 Team suggested a v0 without comms and then a separate 30k for search v1 (with comms)

[EOKENAVA]

Weekly Update

What has been done?

• Reviewed draft Figma UI with MH and HHS.

Status
On Track

Risk
None

Deliverable Date
5/14

What will be done?

• Approval of the Figma UI with MH and Emily
• Service blueprint of the grants application process to inform search
• Start to create testing brief (might be dependent on approval)
• Set up the plumbing/flow for API calls
• Mock data set up

[lucasmbrown-usds]

Will the testing brief include our plan for user research, usability testing, etc?

[andycochran]

Will the testing brief include our plan for user research, usability testing, etc?

Yeah. We'll first create a research brief to define what/how/who (template), then a testing plan with a methodology, timeline, script (template).

[EOKENAVA]

Updated Delivery Date - 5/14

[andycochran]

v7 Figma reviewed was just with OG Leadership; no changes requested; ready for development

[EOKENAVA]

Weekly Update

What has been done?

• Received approval of FIGMA from OG Leadership with no additional changes.
• Collected information for service blueprint of grants.gov grantor posting process
• API handling for search page created
• Work started on page layout

Status
On Track

Risk
None

Deliverable Date
5/14

What will be done?

• Develop responsive search input with placeholder text and button.
• Create a research brief (template) that breaks down the design work to be done, the business motivations, and general effort/timeline.

[EOKENAVA]

Weekly Update

What has been done?

• Set up component/markup for Funding Instrument filter
• HHS Approved Search UI Figma
• Created a component that takes the result data returned by the api and displays the results components in a list.

Status
On Track

Risk
None

Deliverable Date
5/14

What will be done?

• Create a research brief (template) that breaks down the design work to be done, the business motivations, and general effort/timeline.
• Investigate roadmap for opportunities for user research

[margaretspring]

Weekly Update

What has been done?

• HHS Approved Search UI Figma
• Feature flag in place to hide Search UI on server component
• Several UI components created for Search page layout and functionality
• Set up pushing query parameters to browser history to preserve UI state and send to live API call
• Set up status, Agency and Funding Instrument filters, pagination, and search terms with query param management
• Robust useSearchFilter hook logic to manage checkbox group state and debouncing updates from the accordion filter component
• Set up mock data for local dev
• Set up flow/architecture for frontend API calls
• Result data returned by the API displays in UI
• Research brief for usability testing has been drafted (in SME review)

Status
On Track

Risk
None

Deliverable Date
5/14

What will be done?

• HSS approval of research brief
• Continue to refine details of UI/UX to match approved Figma Design
• Improve test coverage for server and client components
• Hook up search UI in lower environments (stretch goal)

[margaretspring]

Weekly Update

What has been done?
Design:

• Testing brief has been approved by MH, Emily, Lucas, Julius
• Started drafting the testing plan

Front-end:

• Dynamic tag format in search results — added conditional logic to display the states in varying presentations to match the Search Figma designs, split top-level docker-compose file into a front-end and back-end file to make running each individually simpler, fixed pagination reset issue, setup design with local to local search UI,

• Update search layout to match Figma — add missing "Search terms" label + help text; position sorting select top-right, next to count; fix breadcrumbs indentation; match fonts; adjust whitespace; improve responsive styles

• Started on the SIA for Ethnio

Status
In progress

Risk

• Ethnio procurement and SIA will impact the progression of this work — We can proceed with usability tests with internal SME and grantors, but Ethnio blocks further tests with applicants

Deliverable Date
5/14

What will be done?

• Design: usability testing plan to be completed and sent for review
• Front-end: create server component test for search page, page not found; frontend tests for search components

[lucasmbrown-usds]

@widal001 @margaretspring @sarahknoppA6 -- I'm noticing that the metrics from GitBook aren't in the acceptance criteria of this GitHub ticket (https://app.gitbook.com/o/cFcvhi6d0nlLyH2VzVgn/s/Pm7UEzeiS1tbLCV1SFRu/product/deliverables/specifications/search-user-interface/~/comments/YEV8iAqqa38I45d9Y4gc?node=d36a16da675d4a6dbe59fc8c555e5726#proposed-metrics).

Do we want to copy those over, or is it fine that we don't have them here? What's our best practice for making sure they get implemented by the 30k date of 5/14?

[andycochran]

Weekly Update 4/3

• [10k] Search UI - Analytics
  • status 72 points initially estimates, 82.5 pointed, 68.1 completed
  • ryan OOO for most of the sprint, so limited progress. 10k near completion
  • completed
    • [Task]: Dynamic tag format in search results #1229
    • [Task:] Update search layout to match Figma #1545
• [10k] Search UI – Design and usability testing
  • status 8 points initially estimated, 33 pointed, 22 completed
  • completed
    • [Task]: Search UI – usability testing brief #1300
    • [Task]: Review analytics proposal #1575
• [10k] Search UI - Analytics
  • status 29 points initially estimated, 3 pointed, 3 completed
  • completed
    • [Task]: proposal for tracking GA4 on g.gov #1542
• [10k] Search UI - Feature flags, API, and infrastructure
  • status 29 points initially estimated, 18 pointed, 11 completed

What has been done?

• In-progress search page demo'd at ToT
• Testing plan drafted (still in internal review)
• Internal discussions about analytics, identified most of the work will be in Google Analytics with 1 ticket on dev end perhaps
• proposal for tracking GA sent

Status
In progress

Risk

• (Same as last update) Ethnio procurement and SIA will impact the progression of this work — We can proceed with usability tests with internal SME and grantors, but Ethnio blocks further tests with applicants

Deliverable Date
5/14

What will be done?

• Design: usability testing plan to be reviewed by MicroHealth then sent to HHS
• Error states
• Set up environment vars for dev, stage, and prod
• Create tickets to set up tracking for site analytics

[andycochran]

Weekly Update 4/10

• [10k] Search UI - Create initial search page
  • status 72 points initially estimated, 100.1 pointed, 84.1 completed
  • completed
    • Update Next to 14.1
    • Add eligibility and category filters
    • Frontend tests for search components
• [10k] Search UI – Design and usability testing
  • status 8 points initially estimated, 33 pointed, 22 completed
  • blocked
• [10k] Search UI - Analytics
  • status 29 points initially estimated, 3 pointed, 3 completed
  • completed
    • n/a
• [10k] Search UI - Feature flags, API, and infrastructure
  • status 29 points initially estimated, 18 pointed, 14 completed
  • completed
    • Setup VSCode API Debugger

What has been done?

• Continued work on UI components, filters, and tests
• Usability testing plan still in internal review
• Mentioned at onsite that MH would work on setting up GA4 tracking on g.gov per proposal sent

Status
In progress

Risk

• Usability testing at risk of not beginning by 5/14, blocked by:
  • Incentives
  • Ethnio SIA
  • API work / getting data into an environment that can be used for testing
  • (Note: these do not necessarily block usability tests with internal SMEs)

Deliverable Date
5/14

What will be done?

• Design:
  • Explore alternative paths for user research tooling
  • Usability testing plan review
• Eng:
  • Collapse sidebar/filters on small screens (mobile view)
  • Set up all agencies as filter options
  • Add USWDS error/alert when selecting a page beyond the max page possible
  • Setup i18n with next-intl
  • Search Results Loading indicator
  • Search error state for 400 and 500 errors
  • Frontend tests for server components (search page, page not found)
  • Set up environment vars for dev, stage, and prod
• Product:
  • Create tickets to set up tracking for site analytics

[widal001]

Updates ticket format to reduce discrepancies with the deliverable spec.

[margaretspring]

Weekly Update 4/17

What has been done?

• User research plan sent to MH for pre-approval
• Plan for Ethnio (participant mgmt) revised
• Got access to previous research participant pool (Thanks Adriana!)

Status
In progress

Risk

• Incentives disbursement affects timeline of applicant research. We're moving forward w/ internal stakeholders & grantors (this is all reflected in the research plan)

Deliverable Date
5/14

What will be done?

• Complete all must-have frontend UI work and and temp/seeded data needed for usability testing
• Get research plan approved, craft messaging, and begin recruiting/scheduling research participants (grantors & internal stakeholders)
• Determine SOP for disbursing research incentives (to unblock recruiting applicant participants)
• Spike effort for integrating Google Analytics 4
• User research plan should be sent to Emily/Lucas within the next day or two
• Begin recruiting research participants (internal stakeholders, grantors)

[margaretspring]

Weekly Update 4/24

What has been done?

• Research Plan approved by Lucas & Emily
• Recruitment messaging to grantors drafted, approved by MH
• SOP for disbursing research incentives sent to MH
• Must-have frontend UI work completed in Dev environment (need to confirm w/ Ryan and QA)

Status

• In progress

Risk

• Tremendous/funding blocking participant compensation
  • Not blocking internal stakeholders & grantors
  • TBD: progress w/o compensation for applicants
• Would be best to have UI in place for internal QA before sending out recruitment messages
  • UI will be done this sprint but, depending on when, we may have to wait until next sprint to email participants

Deliverable Date

• 5/14

What will be done?

• Get recruitment messaging approved by Emily, Adriana
• QA the UI in environment used for testing
• Begin recruiting research participants (internal stakeholders, grantors)
• Spike effort for integrating Google Analytics 4
• Complete adding temp data added for usability testing

[lucasmbrown-usds]

When we say "UI will be done this sprint", do we mean we'll have a fully working search experience in the UI in PROD by the end of this sprint (May 1st)?

[andycochran]

Meant the DoDs will be satisfied this sprint. There are some details in the Design/Figma that may be a little rough, and we plan to address in the fast-follow milestone. But functionally, that's what we mean saying the "UI will be done." Please excuse the fuzzy term; as we know, nothing's ever done.

Since the last weekly update was posted, I've started QAing in lowers (just now available today). We're checking to make sure the UI is acceptable for usability testing. Once sure of that, we'll start sending out recruiting emails (likely Monday).

@acouch can you confirm this sprint'll include deploying to prod?

[lucasmbrown-usds]

Sounds good, thanks Andy. Totally understand there will still be some bits and pieces to be worked out.

I'm definitely interested in the PROD deploy, since as we all know, going to PROD always introduces new unexpected wrinkles, and you're never really sure whether things will work in PROD until they're in PROD!

[acouch]

@lucasmbrown-usds agreed about things being in production. This 30K is the UI side of the search page, so the scope of it is focused on just the frontend. The working code is in prod, but it won't show any results until the #972 transformation work is completed, which is scheduled for next sprint. It makes sense to not call this finished until the API work is done.

[lucasmbrown-usds]

Makes sense -- thanks @acouch !

[margaretspring]

Weekly Update 5/1

What has been done?

• QA'd the UI in Prod environment
• Began recruiting & scheduling research participants (internal stakeholders, grantors)
• Started spike for integrating Google Analytics 4
• Added temp data added for usability testing

Status
In Progress

Risk

• If the transformation work isn't complete, the proposed metrics in the deliverable spec may not be completed in this sprint. A few metrics require data which is dependent on the transformation work. Tickets for those metrics are:
  • [Task]: Add GA4 tracking for click-through-rate from search results to the opportunity listing #1889
  • Add GA4 tracking for number of searches made per filter combination #1890
  • Add GA4 tracking for number of searches made per search term #1891
  • Spike: Review GA4 tracking for click-through-rate from a search results page to an opportunity listing #1892
    Broke into separate tickets so that we can tackle quickly, as soon as transformation is done!

Deliverable Date
5/14 pending risks

What will be done?

• Continue setting up Ethnio & GA 4
• Resolve bugs in Search
• Continue recruiting & scheduling research participants
• Begin conducting usability tests

[sarahknoppA6]

Development team has updated anticipated Delivery Date to 6/11 given additional work to improve the data model. https://betagrantsgov.slack.com/archives/C06F55BKLKX/p1714684814304889

[acouch]

Weekly Update 5/8

What has been done?

• Bug fixing and technical debt work
• GA4 setup in dev

Status

• In Progress

Risk

• Spike: Identify how to track how high in the results list the opportunity which was clicked on is for GA #1532
• Delivery depends on the transformation work

Deliverable Date

• 6/11

What will be done?

• GA4 staging

[widal001]

Replacing our old deliverable tickets with a new ticket format

[HartleySan]

Hello. I came across this thread via https://simpler.grants.gov/process, and I'm curious what the status of this API is. Is it usable yet?

We're actively looking for a way to search through US government grants via an API, and this seems like a very promising option, but we can't tell whether it's actually available yet, or actively being worked on, or it will never be completed. Could you please share a status update?

Thank you.