Skip to content

Handbook: Update Gutenberg release documentation to clarify release post workflow #33328

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.

Sign up for GitHub

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

Merged
priethor merged 9 commits into from
Jul 14, 2021
Merged

Handbook: Update Gutenberg release documentation to clarify release post workflow #33328

Changes from 1 commit
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
4335cac
Update release process documentation
priethor Jul 9, 2021
e3e2ab3
Fix typos and formatting.
priethor Jul 9, 2021
cf22f53
Fix formatting.
priethor Jul 9, 2021
e466c4d
Rewording to avoid second person.
priethor Jul 9, 2021
330dd24
Update release.md
priethor Jul 9, 2021
b6916ed
Add a reference to being pinged to coordinate
priethor Jul 9, 2021
cac4953
Update Gutenberg membership requirements.
priethor Jul 9, 2021
93ab896
Fix internal handbook links
priethor Jul 13, 2021
56eb56e
Reword the drafting and publishing, clarify permissions to post on ma…
priethor Jul 13, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update release.md
  • Loading branch information
@priethor
priethor committed Jul 14, 2021
commit 330dd24fa9c341f2d453f646eea6d0a905a0a3b4
2 changes: 1 addition & 1 deletion docs/contributors/code/release.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -82,7 +82,7 @@ Given the big scope of Gutenberg and the high number of pull requests merged in

#### 3. Drafting the release post

Because of the nature of the release post content, responsibilities are divided in this step. While the post **can either be written by the release manager or delegated to another core member** agreed upon in advance, **visual assets should be created by the design team**.
Because of the nature of the release post content, responsibilities are divided in this step. While the post **can either be written by the release manager or delegated to another core member** agreed upon in advance, **visual assets are best created by the design team**.

When possible, the highlighted changes in the release post should include an animation (video or GIF) or a static image of them in use. Choosing between an animation or a static image will depend on the best way to showcase each highlight: while animations are better to demonstrate workflows, more direct highlights can be shown with an image; having too many video players adds a layer of friction for users to see the highlight, whereas too many simultaneous animated GIFs can distract and overwhelm the reader.

Expand Down