Automatically generate "what's new" section for the docs landing page for new releases

[natalie-bernhard]

Idea originated in Slack thread

From @dmuelle : "Having some what's new content on the overview page would make better use of the space than what we've got currently. In WL we have the What is new in this release of Liberty page that we update for each release. We could do something similar on the overview page, maybe just the section headings and a brief description, linking out to release post for more. Not many people go to the Overview page on purpose but it is what you get when you click Docs from the homepage. I can mock something up if youre interested"

From @mbroz2 : "I wonder if we could automatically generate a 'what's new' section in docs overview that would include a link to the corresponding blog post, as well as links to new doc pages or new sections in existing pages......."
"would probably have to happen in a github action that creates a PR (similar to release/beta blog post creation), rather then at build time, since the latter would be too risky for something so visible" (this is similar to how we handle certs)

[natalie-bernhard]

TO DO: Check analytics to see docs landing page traffic; this will help to determine the priority of the issue

[mbroz]

Please subscribe the correct @mbroz2 not me :)

[natalie-bernhard]

Notes from 5/4 Site Meeting

• This page does not have significant content, so interaction analytics will likely be low, this should not determine the priority of the issue
• Include headlines from the release blog and one to two sentences explaining the feature (possibly automate pulling these headlines)
• Point users from release blog to Docs “what’s new?” with link (this could be added to release blog template)
• Each version has a “What’s new” for that specific version; include version in “What’s New” section title to reinforce this to the user (ex. "What's new in 23.0.0.4?")

[steven1046]

This will require research into how we want to automate pulling in the content from the release blog, or where the blog gets its content.