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

VBA Pilot MVP - Drupal content modeling & spec work #13096

Closed
davidmpickett opened this issue Mar 28, 2023 · 10 comments
Closed

VBA Pilot MVP - Drupal content modeling & spec work #13096

davidmpickett opened this issue Mar 28, 2023 · 10 comments
Labels
Content strategy CMS team practice area Editor experience Pertaining to CMS user experience as Editors Epic Issue type Facilities Facilities products (VAMC, Vet Center, etc) Regional office CMS managed VBA product owned by the Facilities team sitewide UX

Comments

@davidmpickett
Copy link
Contributor

davidmpickett commented Mar 28, 2023

How do we go from a high level diagram to actionable Drupal tickets?

@davidmpickett davidmpickett added Facilities Facilities products (VAMC, Vet Center, etc) Regional office CMS managed VBA product owned by the Facilities team labels Mar 28, 2023
@davidmpickett davidmpickett added the Needs refining Issue status label Mar 28, 2023
@davidmpickett davidmpickett changed the title Scope Drupal work for VBA Regional Office MVP Spec Drupal work for VBA Regional Office MVP Mar 28, 2023
@swirtSJW
Copy link
Contributor

@davidmpickett typically we spec it out like you have done (or less than you have done ;) ), then identify what parts can be built separately, and what parts must go together. Then we spin up the tickets from there.

@omahane
Copy link
Contributor

omahane commented Mar 28, 2023

I'd also suggest having some design work done for the CMS editorial experience so that we know what the expectations are. For instance, with a lot of other content we are doing some custom wizardry:

  • Bringing in content from related entities, based on a selection, either for a Tooltip or added to the WYSIWYG
  • We have fields that are disabled but visible
  • We have fields are are completely hidden to editors

@swirtSJW
Copy link
Contributor

swirtSJW commented Mar 28, 2023

Off the cuff I think the tickets would look like this

  • Design for VBA fieldset on VA Service Taxonomy
  • Design for Service Location paragraph
  • Design for Service Region
  • Design for VBA Facility
  • Design for VBA Facility Service
  • Add VBA fieldset to VA Service Taxonomy
  • Refactor Service location paragraph
  • Create VBA Service Region
  • Add fields to VBA Facility
  • Add fields to VBA Facility Service

They don't all have to be done in that order... they could be interwoven if needed.

@kmariepat-cityfriends
Copy link

kmariepat-cityfriends commented Mar 29, 2023

@davidmpickett AC wise, I would be interested in seeing:

  • I expect a detailed content model spec is created for all of the following content types (are these all content types? see my question below)
  • VBA Service Region
  • VBA menu
  • VA Services taxonomy (VBA fieldset)
  • VBA Facility Service
  • VBA Facility
  • Service location

What are the drupal terms for the above, they are referred to as entities in the description of this card, is that a highest level grouping term. I know some of these are what is known as a content type in drupal, what are the others known as?

@davidmpickett
Copy link
Contributor Author

Entity > Content > Node > Content Type
VBA Service Region
VBA Facility Service
VBA Facility

Entity > Content > Node > Paragraph Type
Service location

Entity > Content > Taxonomy Term > Vocabulary
VA Services taxonomy

Entity > Configuration > Menu
VBA menu

@kmariepat-cityfriends
Copy link

kmariepat-cityfriends commented Mar 29, 2023

Next Steps: chat with CMS collab cycle to determine which is most important to work on first, our proposed first priorities are below:

  • Service Location paragraph
  • Service Region

@jilladams
Copy link
Contributor

@kmariepat-cityfriends added to Sprint 81 (based on Slack that this is a sprint goal)

@davidmpickett davidmpickett reopened this Mar 30, 2023
@davidmpickett davidmpickett added Epic Issue type and removed Needs refining Issue status labels Mar 30, 2023
@jilladams jilladams added Content strategy CMS team practice area Content CMS team practice area and removed temp_fac_epic_scrub labels Jun 23, 2023
@jilladams jilladams changed the title Spec Drupal work for VBA Regional Office MVP Content Spec Drupal work for VBA Regional Office MVP Jun 27, 2023
@jilladams jilladams added the Editor experience Pertaining to CMS user experience as Editors label Jun 27, 2023
@davidmpickett davidmpickett changed the title Content Spec Drupal work for VBA Regional Office MVP Drupal content modeling & spec work for VBA Regional Office MVP Jul 26, 2023
@xiongjaneg
Copy link
Contributor

@davidmpickett I stubbed out some UX review tickets to follow implementation tickets.

@davidmpickett
Copy link
Contributor Author

@xiongjaneg This VBA epic is nearly closable, just need decision on whether 15757 is Pilot MVP or National MVP

@xiongjaneg
Copy link
Contributor

@davidmpickett Michelle and I did discuss moving supplemental status to National MVP given the tight timeline, so closing sounds right. I'll move the last ticket and close the epic.

@Agile6MSkinner Agile6MSkinner changed the title EPIC: VBA Pilot MVP - Drupal content modeling & spec work VBA Pilot MVP - Drupal content modeling & spec work Jun 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Content strategy CMS team practice area Editor experience Pertaining to CMS user experience as Editors Epic Issue type Facilities Facilities products (VAMC, Vet Center, etc) Regional office CMS managed VBA product owned by the Facilities team sitewide UX
Projects
None yet
Development

No branches or pull requests

6 participants