Automattic / Automattic/cortext
Prepare WordPress Playground publishing
- Dominant language
- JavaScript
- Stars
- 51
- Forks
- 2
- Avg merge
- 3h 12m
- Merged PRs (30d)
- 8
Description
Part of #283.
Cortext should have a public Playground link that installs the same ZIP we publish in GitHub Releases. The demo blueprint can live in this repo, while the official gallery entry should use WordPress Playground's bundled resource flow.
- [ ] Add the demo blueprint in the Cortext repo.
- [ ] Add a README link for trying Cortext in Playground.
- [ ] Document how the demo blueprint is built and verified.
- [ ] Add the gallery blueprint files for `WordPress/blueprints`.
- [ ] Open the `WordPress/blueprints` PR after the first GitHub Release ZIP exists.
Contributor guide
Research direction
Start with issue #283, then inspect the Cortext README and the repository's existing release setup before creating the demo blueprint. Done means the repo blueprint, Playground README link, build and verification documentation, and WordPress/blueprints gallery files are present, with the gallery PR opened only after the first GitHub Release ZIP exists.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, wordpress
- Domain
- devops, documentation, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100