Is your feature request related to a problem? Please describe.
Frequently the feature summaries in Chromestatus, while factual, are hard for people who aren't close to the project to grasp. Sometimes they focus on implementation details or correct summaries of technical facts - but they usually don't convey why the feature matters, contexts where developers could use it, and so on.
For Fugu API features, typically I rewrite all the summaries before we send them out in newsletters. By then, though, the original summary will have propagated to other places, and my more human-friendly summaries don't get used much.
Additionally, often our fearless writer likes to suggest summary revisions - but he has no way to propose these and get feedback from the original author. He can only edit and replace.
Describe the solution you'd like
I think we could use one of the following.
A mechanism allowing a tech writer to propose a rewrite and to get feedback, without simply replacing the original text.
Alternately, another field for another summary of the sort I'm describing here.
jpmedley
commented
2 years ago
Is your feature request related to a problem? Please describe.
Frequently the feature summaries in Chromestatus, while factual, are hard for people who aren't close to the project to grasp. Sometimes they focus on implementation details or correct summaries of technical facts - but they usually don't convey why the feature matters, contexts where developers could use it, and so on. For Fugu API features, typically I rewrite all the summaries before we send them out in newsletters. By then, though, the original summary will have propagated to other places, and my more human-friendly summaries don't get used much. Additionally, often our fearless writer likes to suggest summary revisions - but he has no way to propose these and get feedback from the original author. He can only edit and replace.
Describe the solution you'd like
I think we could use one of the following.
/cc @jpmedley