-
Notifications
You must be signed in to change notification settings - Fork 70
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
Implement Centralized Content for VBA #14699
Comments
Question for @swirtSJW and @omahane:
|
One other thing I want to call out that might be a stretch is that the requested model for spotlights is slightly more complex than Vet Center (I think). Rather than 1 national + up to 2 local for a total of 1-3, they want to ensure all three slots are always use, by having 2 national backfills for when no local content is there. This might be worth breaking off as a bonus enhancement for fast-follow, since it would only directly affect National Editors. |
Needs the text for the documenter paragraph and the field. Sync with Dave P. on this. When CC is created, the paragraph type is needed and a field documenter above it that tells the national editor more info about where it's going to appear and what should be in it. |
Christian's work is blocked by my review of
|
Per my chat with @omahane - the answer to this question is yes. Adding |
Copy and pasting the current content of the node here so I can recommend changes
|
Names are hard note: |
Side question for @omahane @swirtSJW about Centralized Content that could spin off into it's own ticket: Do the Product and Applied to fields actually do anything? They seem like vestigial fields that were intended to help with documentation, and information that previously would have been populated there could now live in Content Model Documentation instead? |
@davidmpickett I'm not sure if they have any effect. I think they're just self-documenting. |
@omahane - proposed changes in bold. Notes in italics
|
I don't see any way to set the cardinality of a paragraph distinct from the cardinality of the field that references it. I think it makes sense to have three of these and they get filled in by national editors and are used as 1, 2 or all 3, depending on the number of facility-specific spotlight items. @xiongjaneg Spotlight is not something that's been captured as a field in the Facility (if that is indeed where it should go) (CC: @davidmpickett ) |
They do not currently apply to anything in a systemic/automated way. They are locked down fields for editors and were intended to give as much context as possible to the what and where. It is similar but different than a Content Model Document. The product field does not change the behavior of the node itself but it does tie it to the product taxononmy and at some point can help surface these at a product level. It is easy now while we only have 8 Centralized content nodes to recognise what goes where, but this was built with there potentially being hundreds. |
@omahane Closing based on demo. |
Description
Drupal implementation for VBA Centralized Content is built based on spec #13799. See comments in that ticket for screenshots. There is no spreadsheet version of this spec, because it uses existing fields & screenshots suffice.
Acceptance Criteria
The text was updated successfully, but these errors were encountered: