USWDS-Site - What's new: Create posts_short directory and add new items

[amyleadem]

Summary

• Created an alternative directory for "short posts", which are entries to the news feed that do not have a related posts page. These short posts include a header, a short summary, and a link to another (non-posts) location.
  • To do this, I added a _/posts_short directory to the site and moved all "what's new" content that did not have an attached post to this directory.
  • The items inside _posts_short will be integrated with the items inside _posts in the "What's new" feed.
• Added multiple post files to the What's new page for October and November.

Related PRs

This PR is the first step in the effort to re-organize and update the content and layout of the what's new page. I broke the prototype work into three different PRs so that we can lower the review burden. Here is my proposed merge order for the PRs:

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

Related issue

Closes #2989

The README instructions for creating posts and post-previews will be added in #3047.

Preview link

• What's new page
• All news and updates page

Problem statement

Outdated content on what's new page

What's new page is out of date after recent page merge and reworking how content can be added. Need new news items added.

Post previews added to _posts generated empty pages

Adding preview-only items to the /_posts directory caused the site to build empty posts, which is unnecessary and bad for SEO.

Solution

Outdated content on what's new page

Blurbs were written up for events from October and November, reviewed and approved with feds and posts were created.

Post previews added to _posts generated empty pages

We created a separate collection for /_posts_short and set the output for this collection to false. This means that no pages will be generated for these files.

Anatomy of a short post

Example data structure for short posts with a link

---
title: USWDS 3.9.0 is out now
tags:
 - Releases
excerpt: USWDS version 3.9.0 is out now!
preview_url: https://github.com/uswds/uswds/releases/tag/v3.9.0
---

Example data structure for short posts without a link

---
title: Sunsetting the USWDS 1.0 documentation site
tags:
 - Product updates
excerpt: It's been over five years since we launched USWDS 2.0 and moved on from USWDS v1. We archived the USWDS v1 documentation site a few years back, and at the end of 2024 we'll be taking it offline. Content will likely still be available via archive.org.
preview_url: none
---

Testing and review

Content

• Confirm the content is correct and relevant and links work.
• Confirm the "Sunsetting the USWDS 1.0 documentation site" renders as expected (with no link in the header)
• Confirm posts are appearing in the expected order

Devs

• Confirm the what's new feed incorporates items from both /_posts and /_post-previews in the expected sort order
  • Because of its assigned date of 12/01/2024, the "Post test" item should appear in the feed in between "November monthly call Q&A" and "USWDS Figma design kit beta is live". Screenshot of expected order:
    
• Confirm pages are NOT generated for items in /_post-previews
  • For example, http://localhost:4000/post_previews/2024-12-12-nov-mc-QA/ should return a 404. If you change output: false to output:true in _config.yml in your local build, you should no longer get a 404 for that url.
• Confirm pages are generated for items in /_posts
  • For example, Post test should exist and have expected content
• Confirm no link is added to the "Sunsetting the USWDS 1.0 documentation site" preview on the All news and updates page
• Confirm the directory structure and "post_previews" name is intuitive and makes sense
• Confirm the code meets standards

[amyleadem]

Note

There is a new html-proofer build error. I will work on building a fix in a separate PR.

[mejiaj]

Verified changes and resolved comments. Thanks @amyleadem.

[finekatie]

This is looking good! Great work, Amy and team!

[amyleadem]

Note: I updated the base branch on this PR to go into a feature branch instead of main. This feature branch will allow us to review each section independently while still merging all the what's new updates together.