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

USWDS-Site - What's new: Prototype phase 2 of what's new page #2967

Open
amyleadem opened this issue Nov 14, 2024 · 8 comments · May be fixed by #3094
Open

USWDS-Site - What's new: Prototype phase 2 of what's new page #2967

amyleadem opened this issue Nov 14, 2024 · 8 comments · May be fixed by #3094
Assignees
Labels
Affects: Content Relates to content

Comments

@amyleadem
Copy link
Contributor

amyleadem commented Nov 14, 2024

Summary

Create a prototype that organizes the content on the what's new page with a clear visual hierarchy.

Tasks

  • Clarify categories
  • Show changelog updates
  • Cater to different audiences - stakeholders, design, dev, etc
  • Consider adding links to monthly calls and showcase pages
  • Consider showing multiple tags for easier visual categorization
  • Optimize code structure - automate where possible (See related comment)
@github-actions github-actions bot added the Status: Triage We're triaging this issue and grooming if necessary label Nov 14, 2024
@amyleadem amyleadem self-assigned this Nov 14, 2024
@amyleadem amyleadem moved this to Scheduled in USWDS Core Project Data Nov 14, 2024
@amyleadem amyleadem moved this from Scheduled to Needs refinement in USWDS Core Project Data Nov 14, 2024
@amyleadem amyleadem added Needs: Refinement We need to give this issue more detail Affects: Content Relates to content labels Nov 14, 2024
@amyleadem amyleadem removed the Status: Triage We're triaging this issue and grooming if necessary label Nov 21, 2024
@amyleadem amyleadem moved this from Needs refinement to On deck in USWDS Core Project Data Nov 25, 2024
@amyleadem amyleadem moved this from On deck to In progress in USWDS Core Project Data Nov 25, 2024
@amyleadem
Copy link
Contributor Author

amyleadem commented Jan 29, 2025

Update

Currently prototyping layouts/wireframe in this Mural board (🔒). Aiming to meet with the content/comms team to review and refine by the end of this week.

@amyleadem
Copy link
Contributor Author

amyleadem commented Feb 7, 2025

Update

@amyleadem
Copy link
Contributor Author

Updating the complexity from 3 to 7 points

@amyleadem amyleadem linked a pull request Feb 11, 2025 that will close this issue
@dct2023
Copy link

dct2023 commented Feb 12, 2025

@amyleadem Can you share what impacted the complexity? Could the initial scope of this could be completed this sprint and we can add new scoped changes to the next? That way we can review as a team how those new scoped items weigh against the other tasks that we need to complete.

@amyleadem
Copy link
Contributor Author

amyleadem commented Feb 12, 2025

@dct2023 Good callout. I think the issue is that I started mixing the prototype with the build phase. We are on track for getting this prototype issue into FFR/Done status for this sprint. I can create a follow-on issue for the "build" phase to refine the code for production.

Let me know if you have any questions or concerns.

@amyleadem amyleadem moved this from In progress to Peer Review in USWDS Core Project Data Feb 12, 2025
@amyleadem amyleadem moved this from Peer Review to Initial Fed Review in USWDS Core Project Data Feb 13, 2025
@amyleadem amyleadem moved this from Initial Fed Review to Fed Final Review in USWDS Core Project Data Feb 13, 2025
@mejiaj
Copy link
Contributor

mejiaj commented Feb 18, 2025

@amyleadem can we create a feature branch to merge prototype work into, close this issue, and use that feature branch to start work in #3113?

@amyleadem
Copy link
Contributor Author

@mejiaj I have a slightly different merge strategy (more details below), but I am open to marking this prototype as done and moving on to the production build work.

Merge strategy

The PR for this prototype is a combination of three different PRs and branches. Because the prototype does a lot and touches hundreds of files, my merge strategy is to unwind this work back to the original three branches and merge each into a feature branch. This should simplify the review effort, especially since the first PR is already if FFR.

I propose the following merge order:

  1. USWDS-Site - What's new: Create posts_short directory and add new items #3064 (this is in FFR)
    1. Adds short post content type and creates new posts
  2. USWDS-Site: Enhance what's new page layout #3115
    1. Updates the layout of the what's new and all news pages without the consolidated changelog
  3. Add a consolidated What's New changelog view #3091
    1. Adds consolidated changelog and updates existing changelog data

@dct2023
Copy link

dct2023 commented Feb 20, 2025

Confirmed this was completed and additional work items live elsewhere.

@dct2023 dct2023 moved this from Fed Final Review to Done in USWDS Core Project Data Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Affects: Content Relates to content
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants