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

Facilities Sprint 101 Plan #16572

Closed
xiongjaneg opened this issue Dec 27, 2023 · 8 comments
Closed

Facilities Sprint 101 Plan #16572

xiongjaneg opened this issue Dec 27, 2023 · 8 comments
Assignees
Labels
Epic Issue type Facilities Facilities products (VAMC, Vet Center, etc) Needs refining Issue status sitewide

Comments

@xiongjaneg
Copy link
Contributor

xiongjaneg commented Dec 27, 2023

Schedule Notes

  • Max out Dec. 25 to Jan. 5
  • Martin Luther King Jr. Day
    • A1M holiday
    • Agile Six holiday
    • Civic Actions holiday
    • Friends holiday

Sprint Priorities 🎯

At the end of this sprint, what do we want to have accomplished/delivered?

Tickets for top priority:

Other Sprint Work

UX

Front End

Drupal

@xiongjaneg xiongjaneg added Needs refining Issue status Facilities Facilities products (VAMC, Vet Center, etc) labels Dec 27, 2023
@xiongjaneg xiongjaneg self-assigned this Dec 27, 2023
@mmiddaugh
Copy link
Contributor

mmiddaugh commented Jan 2, 2024

@xiongjaneg I think the AC for Update Figma for VBA RO Pilot MVP after CMS collab cycle touchpoint #15989 would benefit from some discussion during UX sync. There are a lot of parts in the description but only the changes to the Service Region are reflected in the AC.
I think it's a strong 🎯 UX Design candidate.

@xiongjaneg
Copy link
Contributor Author

@mmiddaugh I'll note in the ticket - we pulled out the other two Musts into their own tickets: character counter and error states. Both tickets in this sprint as well.

@mmiddaugh
Copy link
Contributor

I noticed a comment in When a VBA facility name changes the section name needs to change #11628 that the work could be blocked by the Short Name proposal (#15752).

  • I thought we decided that changes to naming conventions weren't ideal given the historical effort to standardize the name.
  • Is the blocker actually the technical discussion to determine options for the URL and Breadcrumbs different than the H1?
    • If so, is this task captured in an issue which might be a candidate for the sprint?

@mmiddaugh
Copy link
Contributor

mmiddaugh commented Jan 2, 2024

@mmiddaugh
Copy link
Contributor

I don't see an estimate but should Audit the Lighthouse Facilities CSV #12016 be prioritized in this sprint or the next?

@aklausmeier
Copy link

@xiongjaneg We will need to come up with another way to refer to the CMS Drupal UI (Editor Experience?) other than "Figma Design" since all files will be in Figma as future state.

@davidmpickett
Copy link
Contributor

I noticed a comment in When a VBA facility name changes the section name needs to change #11628 that the work could be blocked by the Short Name proposal (#15752).

  • I thought we decided that changes to naming conventions weren't ideal given the historical effort to standardize the name.

Per the comments on #15752, you expressed concern about pursuing that but that was before you reengaged with the VBA stakeholders. But then reported that your talks with VBA stakeholders were going well, so it was still an open question.

One thing we identified that would be helpful for having the conversation with stakeholders was designs showing how splitting up the names might look. Jordan created those in ticket #15660. Maybe we should review those in UX Sync this week?

  • Is the blocker actually the technical discussion to determine options for the URL and Breadcrumbs different than the H1?

I think that discussion would actually be part of refining this ticket about the alias pattern: #15155

The Section Name changing problem really has to do with how content governance works in Drupal, more so than any front end aspect of the product. Prescott Vet Center has a documented case of this split.

@xiongjaneg
Copy link
Contributor Author

@mmiddaugh With remaining questions about #11628, let's pull that one from this sprint and replace it with the other one you mentioned #12016

@davidmpickett Let's discuss your comments ^ in UX sync

@xiongjaneg xiongjaneg added the Epic Issue type label Jan 3, 2024
@xiongjaneg xiongjaneg changed the title Draft Facilities Sprint 101 Plan Facilities Sprint 101 Plan Jan 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Epic Issue type Facilities Facilities products (VAMC, Vet Center, etc) Needs refining Issue status sitewide
Projects
None yet
Development

No branches or pull requests

5 participants