-
-
Notifications
You must be signed in to change notification settings - Fork 156
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
2024 in review blogpost #985
base: master
Are you sure you want to change the base?
Conversation
images not optimized yet, first draft
Co-authored-by: tetrapod <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great. Haven't found much else going through the text
Co-authored-by: Patrick Exner (FlameLizard) <[email protected]>
Co-authored-by: John Veness <[email protected]>
Co-authored-by: John Veness <[email protected]>
Co-authored-by: John Veness <[email protected]>
Co-authored-by: John Veness <[email protected]>
Co-authored-by: John Veness <[email protected]>
@JohnVeness thanks for the in-depth review! |
Co-authored-by: John Veness <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a few comments. I think it still needs some work and maybe the scope of it is too big.
I compressed all the non-compressed images (.jpg and .png to .webp) and put them all in the same directory (/year-in-review-2024) |
Co-authored-by: John Veness <[email protected]>
Co-authored-by: John Veness <[email protected]>
better selection thanks to member feedback
Co-authored-by: John Veness <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Co-authored-by: Rémi Verschelde <[email protected]>
cherry picks instead of trying to be all-encompassing
doubled up on the newsletter CTA
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
Co-authored-by: John Veness <[email protected]>
thanking john and syntax <3
blue cherries because why not
CC @coppolaemilio
Still TODO: