Spec Centralized Content content type for VBA

[kmariepat-cityfriends]

Description

AS A VBA national editor
I WANT to see modify content that applies to all ROs nationwide
SO THAT I have a streamlined editing experience, and that national content is standardized (COPE)

AS A Drupal engineer,
I WANT a technical design document
SO THAT there is nothing ambiguous about the implementation requirements.

AS A PO, CMS team member or stakeholder
I WANT to see a detailed content spec
SO THAT I can review the design before implementation

Example artifact

• Drupal Content Spec Template
• Drupal Content Spec TEMPLATE.xlsx

Supporting documents

• VBA RO designs, Sketch Centralized Content = annotated in Sketch comments.
• VBA Content Model diagram (Mural)
• Five previous specs combined into one
• Centralized Content intro video

ACs

Sprint 92 ACs - 5 points

• [Dave] Elements in the VBA FE design that will be determined at a national level for all Regional Office pages (e.g. spotlights, national hotline CTA) are documented.

Sprint 93 AC - 5points

• Draft document of content design - do not need spreadsheet, bc these fields are all using existing paragraph types. Dev is unblocked.
• Review implementation of Centralized Content content type for Vet Centers
  • We will adapt the existing Centralized Content node type to accommodate our data needs. Existing Centralized Content form: https://prod.cms.va.gov/node/add/centralized_content
  • We will create a single VBA RO Centralized Content node. Vet Centers is already set up this way. Their CC node: https://staging.cms.va.gov/node/16142/edit. (Staging CMS uses a standardized password.)
• Review backlog for Vet Center centralized content tickets to see where effort overlaps / dupes / opportunities to satisfy multiple tickets with this work
• Implementation ticket is updated with takeaways from the review - Implement Centralized Content for VBA #14699
• Review document with Product and Drupal engineering
• Share Centralized Content topic dive with CMS team for review / awareness

[laflannery]

After looking at other existing Spotlight CMS patterns and discussing with Michelle, we talked through what the standard spotlight pattern should look like going forward and would ideally like VBA to use this if possible:

• It is based on what Vet Center is currently using but with some labeling changes
  
• Featured content:
  • Change label to Spotlight content - this will help with consistency and lessen confusion by aligning CMS and FE naming conventions
• Section Header
  • Change label to Title - section is a term used very specifically for something else within the CMS so should be avoided whenever possible to refer to other things.
  • Keep field as required
  • Keep field as a text input
  • Keep character limit at 80
• All other fields (Description and Call to Action fields) can remain the same including all existing character limits and labeling.

[davidmpickett]

Given that this content type is very heavily tied to the FE design, I would suggest that we do not spec this out until after usability research is complete and any updates to the design are implemented.

[mmiddaugh]

Summary of business feedback/decisions from Office of Strategic engagement:

Design should include

• Gov Delivery
• national social media only (no local)
• 1 centralized/national spotlight with 2 local/editor level spotlights
• AVA and VERA

[mmiddaugh]

We'll need to consider events sooner than later as it is a significant method of delivering services at some locations. Spotlights will not offer the flexibility needed for the number of events or variety of locations.

Use case: Honolulu Regional Office lists 9+ events occurring this week.

Snapshot from July 19

[mmiddaugh]

"Other nearby locations" should be programmatically addressed - let's not leave this to editors.

[jilladams]

From team refinement: this could go into FE hard coded for MVP launch.
Or, we can Drupalize now.
Next step: FE architecture conversation to understand difference in the lift if the data is hard coded. And: effort from CMS team, including CMS Collab Cycle.

[davidmpickett]

Summary of business feedback/decisions from Office of Strategic engagement:

Design should include

• Gov Delivery

@mmiddaugh Double-checking an assumption here. Is Gov Delivery per facility? Or is it just national.

[xiongjaneg]

drupalize or hardcode for mvp

Drupalize:

• not a lot to be gained by delaying
• a change relies on the CMS editor, fewer points of failure with one person

Hardcode:

• in the past, before hardcoding, there had to be a front end ticket to remove it first
• a consideration might be not knowing what the content might be
• shifts the work down the road to the front end
• a change relies more people, relies on a pull request
• increases likelihood the editor will want to make a change they can't do and will need help with

Decision
-proceed with drupalize for MVP

Next steps

• This ticket needs to be refined for MVP

[jilladams]

• Before his PTO this week, Dave will annotate the mockup to indicate which fields should be centralized content.
• Steve or Christian can then use that to complete this ticket, and consider the rest of the data, to finalize a plan for implemenation.

[davidmpickett]

New page in sketch file with annotations about Drupal vs Hardcoded

[davidmpickett]

All annotations

Drupal annotations

Hardcoded annotations

[jilladams]

Tracked 5 points from Sprint 92. We'll need new estimate for ACs in Sprint 93.

[jilladams]

From scrum:

• We don't need a spreadsheet version of this spec, bc it uses existing fields & screenshots suffice.
• CMS folk can run with this.

[davidmpickett]

Review backlog for Vet Center centralized content tickets to see where effort overlaps / dupes / opportunities to satisfy multiple tickets with this work

Step 0 for this AC - I just went and tagged a whole bunch of issues with the Centralized Content label so there is a clear way to see the product/feature history

[davidmpickett]

• SPIKE: Support tokens in Entity Field Fetch, for inserting local values into nationally managed content #4195 - tagged @swirtSJW for review on relevance/value
• Improve display of centralized content on local content where it is embedded #4055 - fleshed out the ticket with examples and recommendations

[jilladams]

from Scrum:

• Jane / Jill to discuss Centralized Content ownership with Michelle. (related slack thread)
• ANy updates made on behalf of VBA should be documented by the Facilities in existing docs.

[davidmpickett]

From refinement last week: the follow up ticket is ready to go. I think this is safe to close