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

Public - New Designs - Content page #4605

Open
emilyjablonski opened this issue Jan 22, 2025 · 2 comments
Open

Public - New Designs - Content page #4605

emilyjablonski opened this issue Jan 22, 2025 · 2 comments
Assignees
Labels
validated Legitimate bug or issue

Comments

@emilyjablonski
Copy link
Collaborator

emilyjablonski commented Jan 22, 2025

New designs

The content pages are used on pages like the disclaimer, privacy policy, and accessibility statement. Here is an example of what these pages currently look like in core right now: https://bloom.exygy.dev/disclaimer

As part of this ticket, we'll need to create the page header pattern (the full-width, primary-color background with an h1 and optional descriptive text). We'll end up being able to use this pattern across multiple pages. (Note: The pattern folder is established in the single listing page PR).

These pages usually have their content in markdown. We should replace the core disclaimer markdown content with something similar to what's in the Figma file that includes a variety of headings of list elements, so that we can test that they all render as expected. The core content will just be generic, and then will get updated in each jurisdiction.

QA: https://bloom.exygy.dev/disclaimer and https://bloom.exygy.dev/privacy in desktop and mobile

@emilyjablonski emilyjablonski added the validated Legitimate bug or issue label Jan 22, 2025
@sarahlazarich
Copy link
Collaborator

Core, then pull over
No change to links out in doorway (all external) - don't need to toggle, assuming that the content in FAQ won't change
Test this with multiple styles per last paragraph

@sarahlazarich
Copy link
Collaborator

list every page that this touches in the ticket

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
validated Legitimate bug or issue
Projects
None yet
Development

No branches or pull requests

3 participants