-
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
VACMS-15714 Add VAMC System Police content type #16169
Conversation
I added perms. |
a7ad318
to
2873d9d
Compare
2873d9d
to
86292d0
Compare
86292d0
to
8389684
Compare
8389684
to
d23b5b0
Compare
196713a
to
b49f094
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
description: 'A page about how Veterans see VA Police information for a VAMC system.' | ||
help: '' | ||
new_revision: true | ||
preview_mode: 1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
NITPICK:
I know that editors aren't going to be seeing the UI yet (or ever?), but we probably don't need a preview option enabled.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All QA steps passed successfully. No issues form me! Nice work!
This looks good to me! I'm curious to know if the link text/link URL can be combined like @laflannery suggested, but if that isn't possible then this is still approved from a UX perspective. |
@dsasser spotted that too. I will remove it. Good catch. |
@laflannery and @thejordanwood This is the default rendering for the Spotlight content paragraph. If we wanted that to render like a normal CTA it would affect everywhere it is used, and would probably be an issue for CMS Platform Team, not product teams. I believe the original intent of it rendering as separate fields was for proofing the destination separately from the title. As opposed to preview. It was a conscious choice that may or may not match our current approach. |
Good find. Something is up. I am looking into it. |
Small note that when this is set it should be 'VA police' lowercase p per copy edits from CAIA |
d3f7409
to
a8d2cf3
Compare
a8d2cf3
to
8bed400
Compare
@davidmpickett There is a choice to be made: What established pattern do we have you ask??? |
4fecdca
to
53c5054
Compare
* VACMS-15714 Add VAMC System Police content type * VACMS-15714 Add VAMC Police permissions. * VACMS-15714 Add alias pattern for VA Police. * VACMS-15714 Add auto title, fields and formatting to VAMC police. * VACMS-15714 Add CM document. * VACMS-15714 Make alias based on node title. * Remove preview link. * Add base field override. * VACMS-15714 Show cc labels and change title. * VACMS-15714 Add National term definition. * Add VA Police and supplemental status to workbenc access. * VACMS-15714 Show title field so menu title will populate. * VACMS-15714 Remove breadcrumb settings changes that snuck in.
Description
Relates to #15714
Testing done
Screenshots
QA steps
What needs to be checked to prove this works?
What needs to be checked to prove it didn't break any related things?
What variations of circumstances (users, actions, values) need to be checked?
As an admin
Accessibility QA
As an admin or content editor
For context there are no editor editable fields on this content type. They will all be set by an install script.
UX QA
As an admin or content editor
For context there are no editor editable fields on this content type. They will all be set by an install script.
Definition of Done
Select Team for PR review
CMS Team
Public websites
Facilities
User support
Accelerated Publishing
Is this PR blocked by another PR?
DO NOT MERGE
Does this PR need review from a Product Owner
Needs PO review
CMS user-facing announcement
Is an announcement needed to let editors know of this change?