Create 2024-02-14-q1-product-announcement.md #8866
Conversation
|
⚡ Deployed with Pantheon Decoupled This build was successfully deployed with Pantheon. You can track the build logs here. 👀 Preview: https://pr-8866-documentation.appa.pantheon.site |
|
⚡ Deployed with Pantheon Decoupled This build was successfully deployed with Pantheon. You can track the build logs here. 👀 Preview: https://pr-8866-documentation.appa.pantheon.site |
|
⚡ Deployed with Pantheon Decoupled This build was successfully deployed with Pantheon. You can track the build logs here. 👀 Preview: https://pr-8866-documentation.appa.pantheon.site |
|
⚡ Deployed with Pantheon Decoupled This build was successfully deployed with Pantheon. You can track the build logs here. 👀 Preview: https://pr-8866-documentation.appa.pantheon.site |
|
⚡ Deployed with Pantheon Decoupled This build was successfully deployed with Pantheon. You can track the build logs here. 👀 Preview: https://pr-8866-documentation.appa.pantheon.site |
|
⚡ Deployed with Pantheon Decoupled This build was successfully deployed with Pantheon. You can track the build logs here. 👀 Preview: https://pr-8866-documentation.appa.pantheon.site |
|
⚡ Deployed with Pantheon Decoupled This build was successfully deployed with Pantheon. You can track the build logs here. 👀 Preview: https://pr-8866-documentation.appa.pantheon.site |
|
Ultimately i defer to you @IngridKwok on the final call here but I'll share some honest friendly feedback based on my initial read of this copy. it feels odd and unlike all the other release notes entries to-date... the format of using emojis for headers instead of h3s but also the content itself is a departure instead of publishing a dedicated release note entry per product change, we're lumping them all in one and re-using marketing language that's very vague and feels a bit watered down.. a release note should talk very specifically about a specific change, and provide a very clear CTA and communicate the values enabled from the given product change for example, the webops certification program copy doesn't cover in detail the value of becoming certified, what's changed since our initial release of the program (now open to all vs invite only) or CTA for how to register etc and to grock that info the reader has to navigate away from reading the release note and the next.js entry, what exactly are we announcing? we've had next.js starter kits prior to q1 this year i'm pretty sure? (side note language like "Q1" feels very weird to me, we don't usually see jargon like that in copy like this) the copy should tell me clearly what was released with a summary of specific details on the exact changes, why i should care, and where to find more details if i want more specifics etc we should have a single entry announcing infra changes like PHP 8.3, like we've done to date (see screenshot at the bottom) a few are things we've already published release note entries for already like file system status report, we shouldn't be announcing any duplicates in subsequent entries like this. we should announce a change once in this section of the docs site and that's it, it's a view of what happened when, and when there are dupes it muddles the chronology and works against the design imo Overall here's what I'd suggest: revisit why are we doing this? do we really need a release note for this one specific marketing deliverable? yes there's overlap in function between marketings quarterly product announcements and release notes published here authored by Product Managers but the two are still very much distinct, i'd argue we don't need this entry at all and we should pivot the effort away from this draft and refocus on making sure we have individual release notes drafted for each item announced on the marketing page with more specific details on what changed, when, why you should care, and what action to take if any is required
|
|
@rachelwhitton @stevector I completely agree with your points regarding the importance of providing specific and detailed information about each product change. Your feedback was a good summary and remind of the purpose of providing clarity and depth in release notes. One aspect I'd like to address is the absence of release notes for the features mentioned in the marketing announcement. This raises an important question about whether we should have a retrospective release note for these features. I can't agree more that there should have been individual release notes to provide detailed information of features mentioned in the marketing announcement, but I didn't see them all. I'm committed to refining the release note to meet our usual standards. On the use of Q1: While I understand that terminology preferences can vary, "Q1" is a widely accepted abbreviation for the first quarter of the year and is commonly used in various business contexts. It provides a concise and standardized way to refer to a specific time period. |
|
@IngridKwok is this still in progress or should we close? |
|
@rachelwhitton Please close this. Thanks! |
@rachelwhitton @stevector Created a release note to summarize the Q1 product announcement, to be published on Feb 14, 2024.