Update content on Park booking page

[JLWade]

Description:

As a potential park visitor, I want to easily view and understand info on the booking page of DUP so that I can book a pass.

This ticket is to update text and content on park booking page to align with best web content practices and plain language. Please note many updates are capitalizations and hyperlink updates.

Updates found here: https://bcgov.sharepoint.com/:w:/r/teams/031072/_layouts/15/Doc.aspx?sourcedoc=%7BA34EA26A-4F09-4BAC-B27C-4D3018643484%7D&file=day-use-pass-system-mount-seymour-v0.1.docx&wdLOR=cB7A430E5-82D6-44AF-BC63-A2A1501CD792&action=default&mobileredirect=true

Current view:

Figma link: https://www.figma.com/file/2lQW8InOa0lEiUiMeGmeNC/Day-Use-Pass?type=design&node-id=4441%3A9725&mode=design&t=St5SW8v1cpTULiyZ-1

Acceptance Criteria:

updated content found in link above

On the park booking page...

• [x] 1. content is updated in the yellow important booking info box. Copy matches what was changed in #338 from this document here
• [x] 2. content is updated in the trail info box that pops up.
• [x] 3. content is updated in the grey guidelines box.

Development Checklist:

• [ ] ...
• [ ] ...
• [ ] ...

Dependencies

• Blocked by
• Blocking

Wireframe(s):

Workflows:

Definition of Ready (Note: If any of these points are not applicable, mark N/A)

• [ ] User story is included
• [ ] User role and type are identified
• [ ] Acceptance criteria are included
• [ ] Wireframes are included
• [ ] Design / Solution is accepted by Product Owner
• [ ] Dependencies are identified (technical, business, regulatory/policy)
• [ ] Story has been estimated (under 13 pts)

Definition of Done

• In progress:
  • [ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
  • [ ] UI meets accessibility requirements
  • [ ] Unit tests are written
  • [ ] Work is traceable in GitHub
  • [ ] PR linked to ticket number
  • [ ] If needed/required - Dev adds flag/label to highlight any migration steps necessary prior to PROD deployment
• Code review:
  • [ ] Code is peer reviewed and has passed CI/CD tests
• QA:
  • [ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
  • [ ] Code is potentially shippable to the production environment
  • [ ] Functional features have been tested and passed by QA
  • [ ] UI components tested by designer
  • [ ] Code is deployed to PROD when moved to 'done' column (unless requested otherwise by PO)
• PO Review:
  • [ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
  • [ ] Reviewed and approved by Product Owner

Notes:

[JLWade]

ticket in blocked to save for when David is ready to pick up for onboarding

[ndelraye]

Marshall has approved attached updates, this ticket is ready to go

[davidclaveau]

Should be good to review!

[manuji]

Tested on TEST: Passed

• Verified that the copy updates requested in the 3 locations of the individual park pages have been done.
• There is a minor differences between the Figma designs and the implementation, but not a blocker for the PROD deployment.
• Passing to PO review for approval to deploy to PROD. @JLWade

The differences are:

• The first sentence inside the yellow box is given as a bullet point in Figma but implementation is not. Test environment is below;

Figma file is below;

[JLWade]

Thanks for the flag Manuji - I think we can leave as is and update figma when we can. Moving to done