Process of post authoring and submission

1. Create a new branch with the name of the author as prefix, something like gianmaria/my-new-shiny-post, Starting from master branch
2. Create or link a GitHub issue that gives context to the post,
3. When you believe that your post is finished, open a pull request against master branch (optional: rebase on master branch before the PR so you will include any modification done to the master branch after your branch started)

** You can use field publishDate to determine a publication date, this will permit you to merge the PR before the actual publishing. Once the branch will be closed the post will be scheduled.

front-matter instructions here

Remember to set draft to false or remove it entirely. Draft is not used because all new post are in dedicated branch.

Rules

These are the rules that will be applied before post publishing

• @MattVSTS should review English content (opz @giuliov )
• We should have at least two approver (for English post we have already @MattVSTS / @giuliov)
• Pr will be approved and merged on master branch
• GitHub action will update the site, the post will be published (unless publishDate is in the future for scheduled posts)

Relaunch

• We still need to add relaunch trigger on build that will relaunch post on Twitter o other sources.

Fixes

• Once your post is published, to fix the content you should

1. Open a new branch starting from master (ex gianmaria/fix-post-xxx)
2. Do the correction
3. Create a PR against master branch.

Approval process will be lighter and based on the size of the PR.