2024 in review blogpost

[MurderVeggie]

CC @coppolaemilio

Still TODO:

• add cover image

[paddy-exe]

Looks great. Haven't found much else going through the text

[MurderVeggie]

@JohnVeness thanks for the in-depth review!

[coppolaemilio]

Left a few comments. I think it still needs some work and maybe the scope of it is too big.

[akien-mga]

I think the concept of "we picked one per month" / "one per technical area" needs to be better introduced (made a suggestion for the technical part), as otherwise it reads a bit like this is a summary of our key achievements this year, when it's mostly about picking one cool thing for each month.

If it was a summary of the key achievements, it would be 90% technological highlights (which is what we spend most of our efforts on) from 4.3 and 4.4-beta1.

But I still think this can work with a bit of tweaking.

[Calinou]

Looks good to me.

[coppolaemilio]

Hopefully the last round of edits:

• The name of the file needs to change from year-in-review-2024.md to 2024-cherry-picks.md
• The category is set to newsletter but should be showcase. I wouldn't bundle the newsletter entries with the regular rss feed.
• Date needs to be edited to the 24th which is when it will probably go out
• To follow the structure of the lists like Platforms and Systems, I would group the lists that only have one item (2D, 3D, Core, Editor, and Documentation) into a list called something like "General" and follow the same structure as the other lists: "sub category title: link"

After those changes I can embed the html form so that people can sign up to the newsletter from there instead of having to visit the form first.

[MurderVeggie]

Hopefully the last round of edits:

* The name of the file needs to change from `year-in-review-2024.md` to `2024-cherry-picks.md`

* The category is set to `newsletter` but should be `showcase`. I wouldn't bundle the newsletter entries with the regular rss feed.

* Date needs to be edited to the 24th which is when it will probably go out

* To follow the structure of the lists like Platforms and Systems, I would group the lists that only have one item (2D, 3D, Core, Editor, and Documentation) into a list called something like "General" and follow the same structure as the other lists: "sub category title: link"

After those changes I can embed the html form so that people can sign up to the newsletter from there instead of having to visit the form first.

Done - as a side note, the previous structure was based on the teams page, we might want to add the "General" headline there as well then to keep it consistent.

[coppolaemilio]

Thanks!