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

[LUPEYALPHA-760] EY scaffolding + landing page #3026

Merged
merged 10 commits into from
Jul 30, 2024

Conversation

AbigailMcP
Copy link
Contributor

@AbigailMcP AbigailMcP commented Jul 24, 2024

Context

  • We are adding a new journey and policy to the service: 'Claim an early years financial incentive payment'.
  • This PR contains the bare-bones models for the provider journey only.
  • In the future, there will also be a practitioner journey which will support the same claim submitted via this provider journey.

Changes in this PR

  • Adds models (journey, eligibility, session, session_answers, slug_sequence, policy) for
    the new EarlyYearsPayment::Provider journey.
  • Adds basic happy path spec that visits the landing page.
  • Adds basic view and content for landing page as per the prototype
  • Includes the new journey config in the seeds
  • Adds migration to create early_years_payment_eligibilities
  • Hides the start button on the landing page when the journey is closed via the admin.

Out of scope

  • Whole documents section
  • Links to consent form and privacy notice

Guidance to review

How do we feel about the journey name Journeys::EarlyYearsPayment::Provider?
What about the journey name as it appears on the admin 'Manage service' page?

Prototype: https://claim-additi-main-9yrds6vyxcsd.herokuapp.com/landing-page

  • Head to /early-years-payment-provider/landing-page and compare against the prototype
  • Head to /admin/journey_configurations, turn the journey off
  • Head back to the landing page and check the 'Start now' button has disappeared
Screenshot 2024-07-26 at 11 19 37 Screenshot 2024-07-26 at 11 20 00 Screenshot 2024-07-26 at 10 52 50

@AbigailMcP AbigailMcP force-pushed the LUPEYALPHA-760-ey-landing-page branch from 12cc246 to db39d8f Compare July 24, 2024 09:53
Copy link
Contributor

@slorek slorek left a comment

Choose a reason for hiding this comment

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

Note there will be two journeys supporting this policy, so we may consider naming this journey clearly as the Provider journey.

@AbigailMcP AbigailMcP force-pushed the LUPEYALPHA-760-ey-landing-page branch from d9d8256 to 5ea832f Compare July 25, 2024 14:08
@AbigailMcP AbigailMcP marked this pull request as ready for review July 25, 2024 14:55
@AbigailMcP AbigailMcP added the deploy Deploy a review app for this PR label Jul 26, 2024
@AbigailMcP AbigailMcP force-pushed the LUPEYALPHA-760-ey-landing-page branch from aa717eb to 430bff0 Compare July 29, 2024 09:04

<p class="govuk-body">
You can find more information about employment contracts on the
<%= govuk_link_to("ACAS website", "#") %>.
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@cwadsworthdfe - could you let me know where this should link to?

Choose a reason for hiding this comment

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

thanks! updated

@cwadsworthdfe
Copy link

I've reviewed this and happy to approve.

  • Landing page replicates the prototype
  • Service can be turned on and off and start now button behaviour is correct
  • Journey name split is clear too in manage services

Thanks! @AbigailMcP

Copy link
Contributor

@rjlynch rjlynch left a comment

Choose a reason for hiding this comment

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

This all looks good to me 👍

Comment on lines 8 to 9
if Rails.env.production?
"https://www.example.com" # TODO: update to correct guidance
Copy link
Contributor

Choose a reason for hiding this comment

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

For FE i ended up removing this. from what I could tell, stakeholders wanted the landing page to be the start page

Copy link
Contributor Author

Choose a reason for hiding this comment

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

ahh thank you! i think that's the same for EY - i'll remove too 👍

@AbigailMcP AbigailMcP force-pushed the LUPEYALPHA-760-ey-landing-page branch from 64ad60a to 724ad48 Compare July 30, 2024 09:13
@AbigailMcP AbigailMcP force-pushed the LUPEYALPHA-760-ey-landing-page branch from 724ad48 to 6de10f7 Compare July 30, 2024 09:58
- Add models (journey, eligibility, session, session_answers, slug_sequence, policy) for
 the new EarlyYearsPayment journey.
- Add basic happy path spec that visits the landing page.
- Add basic view for landing page
- Include the new journey config in the seeds
- Add migration to create early_years_payment_eligibilities.
Missing:
- Links
- Document downloads and styling
- Contents list styling, TBC
Change the journey from EarlyYearsPayment to EarlyYearsPayment::Provider since
there will be a second journey relating to the practitioner answers
@AbigailMcP AbigailMcP force-pushed the LUPEYALPHA-760-ey-landing-page branch from 6de10f7 to a8a4596 Compare July 30, 2024 10:36
@AbigailMcP AbigailMcP merged commit 6f61ab6 into master Jul 30, 2024
14 checks passed
@AbigailMcP AbigailMcP deleted the LUPEYALPHA-760-ey-landing-page branch July 30, 2024 10:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deploy Deploy a review app for this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants