Release blog post design and process
Requirements
- New blog post design.
- There should be a process to allow any GitLab team member to easily add/edit content, including text and media assets.
- GitLab team members should not need to be too tech-savvy and be able to add/edit content without or with minimal help. For example, sales + marketing should be able to do this.
- It should be hard for GitLab team members to break something.
- It should be easy for GitLab team members to collaborate.
Solution and process
- Easy Markdown template to follow.
- People edit the template directly.
- No confusing styling or markup in the template, so as to achieve above requirements.
- Lock content a few days prior to 22nd, to allow for copyediting and other tweaks.
- All team members should contribute.
- Product folks are responsible for their particular area, but individual engineers and other folks should also contribute as makes sense.
- Product folks should coordinate entire flow and structure and content.
Design
- Header section
- Introduction section
- Recap section for major releases
- Body section
- Footer section
- Upgrade / install section
- Marketing content / links