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

VACMS-15714 Add VAMC System Police content type #16169

Merged
merged 13 commits into from
Dec 1, 2023

Conversation

swirtSJW
Copy link
Contributor

@swirtSJW swirtSJW commented Nov 20, 2023

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

  1. Go to /admin/structure/types/manage/vamc_system_va_police/document
    • Validate that that the content model document exits with links to design, CAIA and others
  2. Go to /node/add/vamc_system_va_police
  3. Complete all required fields (suggest using VISN 20 - VA Alaska to make selection easier)
    • For menu link title use 'VA Police'
    • save the node
    • Validate that the title becomes 'VA Police'
    • Validate the alias is /alaska-health-care/va-police

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.

  1. Visit https://pr16169-xiwjtl4qmbjrl2kp2oin9dttwrlbc3dt.ci.cms.va.gov/albany-health-care/va-police and evaluate.
  2. Edit the node and evaluate.
  • validate that all is well or create followup issue(s)

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.

  1. Visit https://pr16169-xiwjtl4qmbjrl2kp2oin9dttwrlbc3dt.ci.cms.va.gov/albany-health-care/va-police and evaluate.
  2. Edit the node and evaluate.
  • validate that all is well or create followup issue(s)

Definition of Done

  • Documentation has been updated, if applicable.
  • Tests have been added if necessary.
  • Automated tests have passed.
  • Code Quality Tests have passed.
  • Acceptance Criteria in related issue are met.
  • Manual Code Review Approved.
  • If there are field changes, front end output has been thoroughly checked.

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?

  • Yes, and it's written in issue ____ and queued for publication.
    • Merge and ping the UX writer so they are ready to publish after deployment
  • Yes, but it hasn't yet been written
    • Don't merge yet -- ping the UX writer to write and queue content
  • No announcement is needed for this code change.
    • Merge & carry on unburdened by announcements

@va-cms-bot va-cms-bot temporarily deployed to Tugboat November 20, 2023 04:57 Destroyed
@va-cms-bot va-cms-bot temporarily deployed to Tugboat November 20, 2023 15:33 Destroyed
@swirtSJW
Copy link
Contributor Author

I added perms.

@swirtSJW swirtSJW force-pushed the VACMS-15714-va-police-page branch from a7ad318 to 2873d9d Compare November 20, 2023 15:53
@va-cms-bot va-cms-bot temporarily deployed to Tugboat November 20, 2023 15:53 Destroyed
@swirtSJW swirtSJW force-pushed the VACMS-15714-va-police-page branch from 2873d9d to 86292d0 Compare November 20, 2023 16:57
@va-cms-bot va-cms-bot temporarily deployed to Tugboat November 20, 2023 16:58 Destroyed
@swirtSJW swirtSJW force-pushed the VACMS-15714-va-police-page branch from 86292d0 to 8389684 Compare November 20, 2023 23:02
@va-cms-bot va-cms-bot temporarily deployed to Tugboat November 20, 2023 23:02 Destroyed
@swirtSJW swirtSJW force-pushed the VACMS-15714-va-police-page branch from 8389684 to d23b5b0 Compare November 21, 2023 04:03
@va-cms-bot va-cms-bot temporarily deployed to Tugboat November 21, 2023 04:03 Destroyed
@va-cms-bot va-cms-bot temporarily deployed to Tugboat November 21, 2023 04:22 Destroyed
@swirtSJW swirtSJW force-pushed the VACMS-15714-va-police-page branch from 196713a to b49f094 Compare November 21, 2023 15:07
@va-cms-bot va-cms-bot temporarily deployed to Tugboat November 21, 2023 15:07 Destroyed
@swirtSJW swirtSJW marked this pull request as ready for review November 21, 2023 15:18
@swirtSJW swirtSJW requested review from a team as code owners November 21, 2023 15:18
@va-cms-bot va-cms-bot temporarily deployed to Tugboat November 21, 2023 15:46 Destroyed
@swirtSJW swirtSJW self-assigned this Nov 21, 2023
@laflannery
Copy link
Contributor

  • There is a Preview option at the bottom but I've never seen that in another content type. Is this supposed to be there?
    image
  • Do the link Text and the Link URL have to be separate, is it possible to combine them like it is on the VAMC System page? Having a naked link like this is bad for accessibility.
    Police page
    image
    VAMC System page
    image

dsasser
dsasser previously approved these changes Nov 21, 2023
Copy link
Contributor

@dsasser dsasser left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great to me and QA steps were successful:

Screenshot 2023-11-21 at 10 53 24 AM

I had one minor nitpick but it isn't a blocker.

description: 'A page about how Veterans see VA Police information for a VAMC system.'
help: ''
new_revision: true
preview_mode: 1
Copy link
Contributor

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.

edmund-dunn
edmund-dunn previously approved these changes Nov 21, 2023
Copy link
Contributor

@edmund-dunn edmund-dunn left a 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!

@thejordanwood
Copy link

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.

@swirtSJW
Copy link
Contributor Author

  • There is a Preview option at the bottom but I've never seen that in another content type. Is this supposed to be there?

@dsasser spotted that too. I will remove it. Good catch.

@swirtSJW
Copy link
Contributor Author

  • Do the link Text and the Link URL have to be separate, is it possible to combine them like it is on the VAMC System page? Having a naked link like this is bad for accessibility.
    Police page

@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.

@swirtSJW
Copy link
Contributor Author

Something funky going on with Sections.

When I log in as [email protected] who is in the VA Chillicothe health care section, I can edit a VAMC System VA Police Page that is in the Ann Arbor Section, despite not being able to edit any other content in the Ann Arbor section

Good find. Something is up. I am looking into it.

@davidmpickett
Copy link
Contributor

I am pretty sure I know the answer to this, but just to check.
Is there an easy way to specify a default "Menu link title" for this content type? We will always want it to be "VA Police" = same as the node title. I couldn't find this as a setting in the Site Building interface and I know menus are weird, but just want to ask and confirm

@davidmpickett there is not in the content type itself. But we will set them when we bulk create them.

EDIT: I take that back. We are doing it on other top task pages.

Small note that when this is set it should be 'VA police' lowercase p per copy edits from CAIA

@va-cms-bot va-cms-bot temporarily deployed to Tugboat November 29, 2023 23:27 Destroyed
@swirtSJW swirtSJW force-pushed the VACMS-15714-va-police-page branch from d3f7409 to a8d2cf3 Compare November 30, 2023 22:34
@va-cms-bot va-cms-bot temporarily deployed to Tugboat November 30, 2023 22:34 Destroyed
@swirtSJW swirtSJW force-pushed the VACMS-15714-va-police-page branch from a8d2cf3 to 8bed400 Compare December 1, 2023 17:36
@va-cms-bot va-cms-bot temporarily deployed to Tugboat December 1, 2023 17:36 Destroyed
@swirtSJW
Copy link
Contributor Author

swirtSJW commented Dec 1, 2023

Is there an easy way to specify a default "Menu link title" for this content type? We will always want it to be "VA Police" = same as the node title. I couldn't find this as a setting in the Site Building interface and I know menus are weird, but just want to ask and confirm

@davidmpickett
I found the issue with this. The only way I can prefill the menu link title field is if I show the node title (it is disabled, because auto_entity_label provides the value for the title so it is not editable by anyone) .

image

There is a choice to be made:
A) show a title field that editors can never touch so that menu link title is populated on a page editors will never create themselves
B) Don't show the title which will keep menu link title from being populated on a page that will be built by a script anyway.

What established pattern do we have you ask???
Unfortunately we have both on our top task pages.
image

@va-cms-bot va-cms-bot temporarily deployed to Tugboat December 1, 2023 19:00 Destroyed
@swirtSJW
Copy link
Contributor Author

swirtSJW commented Dec 1, 2023

The permissions issue has been worked out
image

He can only modify police content in chilicothe

image

@va-cms-bot va-cms-bot temporarily deployed to Tugboat December 1, 2023 19:20 Destroyed
@swirtSJW
Copy link
Contributor Author

swirtSJW commented Dec 1, 2023

image

@swirtSJW swirtSJW force-pushed the VACMS-15714-va-police-page branch from 4fecdca to 53c5054 Compare December 1, 2023 20:03
@va-cms-bot va-cms-bot temporarily deployed to Tugboat December 1, 2023 20:03 Destroyed
@swirtSJW swirtSJW merged commit 76febad into main Dec 1, 2023
13 checks passed
@swirtSJW swirtSJW deleted the VACMS-15714-va-police-page branch December 1, 2023 20:03
tjheffner pushed a commit that referenced this pull request Dec 6, 2023
* 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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants