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

layout: node--step_by_step (Step-by-Step) #8651

Open
7 of 12 tasks
Tracked by #17701
amponce opened this issue Apr 6, 2022 · 0 comments
Open
7 of 12 tasks
Tracked by #17701

layout: node--step_by_step (Step-by-Step) #8651

amponce opened this issue Apr 6, 2022 · 0 comments
Labels
Accelerated Publishing Needs refining Issue status next-build FE Repository that will replace content-build. Uses NextJS, builds static pages.

Comments

@amponce
Copy link

amponce commented Apr 6, 2022

Description

We need a layout for Step by Step content. Example pages:

Acceptance Criteria

  • Step by step page content renders correctly
  • The layout output is consistent with the existing output of content-build (visually and functionally)

Tasks

Preview Give feedback
  1. 0 of 1
    Accelerated Publishing Needs refining next-build
  2. 0 of 6
    jtmst
  3. 2 of 8
    Accelerated Publishing next-build
    jtmst
  4. Accelerated Publishing
    penny-lischer
  5. 3 of 3
    Accelerated Publishing Needs refining next-build
    tjheffner
  6. Accelerated Publishing
    penny-lischer
  7. 0 of 6
    Accelerated Publishing next-build
    tjheffner

Supporting detail

CMS field implementation: https://prod.cms.va.gov/admin/structure/types/manage/step_by_step/fields

Content build template: https://github.com/department-of-veterans-affairs/content-build/blob/main/src/site/layouts/step_by_step.drupal.liquid

Content build base GraphQl query: https://github.com/department-of-veterans-affairs/content-build/blob/main/src/site/stages/build/drupal/graphql/nodeStepByStep.graphql.js

API query for individual node: https://prod.cms.va.gov/jsonapi/node/step_by_step/769ed6f8-1cc8-4941-825e-40fa9cc9d35b?include=field_alert_single,field_buttons,field_contact_information,field_primary_category,field_other_categories,field_related_benefit_hubs,field_related_information,field_steps,field_tags

Includes:

field_alert_single
field_buttons
field_contact_information
field_primary_category
field_other_categories
field_related_benefit_hubs
field_related_information
field_steps
field_tags

Note: the includes for this are very nested. Many of these fields are also on Resources & Support, and I recommend looking at its query for equivalents. There is a mechanism in that query for getting nested includes.

Logic notes:
You can ignore search for this ticket. We need to implement search separately. It is shared by several content types, and will be done at once.

It looks like there will need to be some conversion of number to word; see numToWord in the content-build template.

@TheBoatyMcBoatFace TheBoatyMcBoatFace added the next-build FE Repository that will replace content-build. Uses NextJS, builds static pages. label Dec 23, 2022
@jilladams jilladams added the CMS Team CMS Product team that manages both editor exp and devops label Jan 25, 2023
@timcosgrove timcosgrove added Accelerated Publishing and removed CMS Team CMS Product team that manages both editor exp and devops Platform CMS Team labels Jul 3, 2023
@timcosgrove timcosgrove changed the title Component: node--step_by_step component: node--step_by_step (Step-by-Step) Jul 17, 2023
@timcosgrove timcosgrove changed the title component: node--step_by_step (Step-by-Step) layout: node--step_by_step (Step-by-Step) Jan 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Accelerated Publishing Needs refining Issue status next-build FE Repository that will replace content-build. Uses NextJS, builds static pages.
Projects
None yet
Development

No branches or pull requests

5 participants