WordPress / WordPress/wordpress-playground
Communicate new features
Open
Nobody has claimed this yet.
[Type] Marketing
- Dominant language
- JavaScript
- Stars
- 2k
- Forks
- 462
- Avg merge
- 18h 44m
- Merged PRs (30d)
- 33
Description
Let's start communicating new Playground releases to the community.
To do:
- The form of communication is established. It would likely resemble Interactivity API Status update more than What's new in Gutenberg 15.6.
- A recurring post is published on make.wordpress.org/meta/ with the news about recent work in Playground.
- Playground maintains a (rolling?) Changelog to make the above process easier
Optional, to be discussed:
- Playground maintains a list of "releases" with news in each release to make the project history easy to reason about on GitHub.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked Interactivity API status update and What's new in Gutenberg examples to compare communication formats. Define the recurring Playground post and rolling changelog process described in the issue, including how recent work will be selected and published. Done means the communication format, recurring publication, and changelog approach are established.
Written by the indexing model from the issue text.
Assessment
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100