Commit 18a638b8 authored by Joshua Lambert's avatar Joshua Lambert

Update release post template, add new item template

parent b28ac280
Pipeline #76679489 passed with stages
in 26 minutes and 9 seconds
Engineer(s): `@engineers` | Product Marketing: `@PMM` | Tech Writer: `@techwriter`
### Content checklist
* [ ] YML filled out for feature
* [ ] Description is informative and focuses on the problem we're solving and the value we're delivering
* [ ] Documentation is updated and linked
* [ ] Screenshot/video is included (optional for secondary items)
### Review
When the above is complete and the content is ready for review, it should be reviewed by Product Marketing and Tech Writing:
* [ ] PMM review
* [ ] Tech writing
#### Checklist for reference
* Make sure feature description is positive and cheerful
* Check Feature name
* Check Feature availability (Core, Starter, Premium, Ultimate badges)
* Feature is added to [`data/features.yml`](https://about.gitlab.com/handbook/marketing/website/#adding-features-to-webpages) (with accompanying screenshots)
* Check all images size < 300KB ([compressed](https://tinypng.com/), max width 1000 pixels)
* Check that documentation is updated and easy to understand
* Check Documentation links (all feature blocks contain `documentation_link`)
* Run the content through an automated spelling and grammar check
* Validate all links are functional
### References (optional)
* Issue:
* Release post:
/label release-post
\ No newline at end of file
......@@ -58,11 +58,11 @@ are made through individual feature YML files, which are reviewed prior to merge
#### Contribution instructions
- Create a new branch from `master` for each feature/deprecation, and open an MR targeted at the `master` branch
- One YML file for each contribution in `data/release_posts/unreleased/`, see `data/release_posts/unreleased/feature_sample.yml` for format and content. Images should be placed in `/images/unreleased/`.
- Create a new branch from `master` for each feature/deprecation, and open an MR targeted at the `master` branch using the `Release Post Item` template.
- One YML file for each contribution in `data/release_posts/unreleased/`, see `data/release_posts/unreleased/feature_sample.yml` for format and content. Images should be placed in `/source/images/unreleased/`.
- Include which section the block belongs to, for example `primary`, `secondary`, or `deprecations`
- Perform the [reviewer checklist](#reviewer-checklist)
- Ask the relevant PMM for the area and a tech writer to [review](#reviewer-checklist) the MR. The MR should be reviewed and approved in time to be merged alongside the feature itself.
- Ask the relevant PMM and tech writer for the group to [review](#reviewer-checklist) the MR. The MR should be reviewed and approved in time to be merged alongside the feature itself, with the PM performing the merge once reviews are complete. If you don't have access to merge, assign the MR to someone who does.
- Content area reminder:
- Primary features
- Improvements (secondary features)
......@@ -132,7 +132,7 @@ The PM leading the post is responsible for adding and checking the following ite
- [ ] Pull `master`, resolve any conflicts
- [ ] Aggregate content from all feature blocks in `data/release_posts/unreleased/` into release post YML. Delete individual files when complete.
- [ ] Move referenced images in `/images/unreleased/` to `/images/X_Y/`.
- [ ] Move referenced images in `/source/images/unreleased/` to `/source/images/X_Y/`.
- [ ] Make sure all features listed in the [direction](https://about.gitlab.com/direction/)
page are included in the post
- [ ] Mention the [Distribution PM](https://about.gitlab.com/handbook/product/categories/#distribution-group) asking them if there's any relevant info to be added to the [upgrade warning](https://about.gitlab.com/handbook/marketing/blog/release-posts#upgrade-warning) section. If not, delete the `upgrade` block in the release post data file
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment