Skip to content
Snippets Groups Projects
Commit 13a7bb46 authored by Heather McNamee's avatar Heather McNamee
Browse files

added info about new site and adding heather and axil as devs

parent 3e2bd5a4
No related branches found
No related tags found
No related merge requests found
Loading
Loading
@@ -55,14 +55,17 @@ Here's how it works.
on those in parallel.
2. Add a post
- You'll write your blog post in Markdown.
- Follow examples under [/source/_posts](https://gitlab.com/gitlab-com/www-gitlab-com/tree/master/source/_posts)
- Follow examples under [/source/posts](https://gitlab.com/gitlab-com/www-gitlab-com/tree/master/source/posts)
- Follow the [style guide](https://gitlab.com/gitlab-com/blog-posts/blob/master/STYLEGUIDE.md)
- Files end in .html.md
3. Create a MR to prompt a review
- Make the MR in WIP mode. Meaning add WIP to the title so it won't be merged accidentally.
- Make the MR in WIP mode. Meaning add WIP: to the title so it won't be merged accidentally.
- cc @nearlythere to prompt a review
- Add @nearlythere and @axil as developers on your project so they can make changes directly.
4. Review
- You will get a formal/style review. Does it follow the style guide? Is it easy to follow?
- You will get a technical review. A technical review will ensure everything works as expected and follows our best practices.
- You'll get a "eagle eyes" copy edit for any final issues with grammar.
5. Finally we'll schedule and we'll publish!
 
(If these steps aren't clear, you can also create a
Loading
Loading
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment