-
Notifications
You must be signed in to change notification settings - Fork 39
How to proof read a blog post
When proof-reading a blog post, consider the following aspects:
-
Pull Request to
master
Make sure that the PR is branched from the master and made to the master. -
SEO-friendly title
Analyze the blog post title for SEO-friendliness. Use this Headline Analyzer. In the best case, the post will have a green headline score. If not, try to come up with a better solution -
Correct size of header image
Make sure that the size of the header image is 1700:850. -
Location of header image.
Make sure that the image is correctly stored regarding private/public indication and is correctly linked in the frontmatter of the post. -
Date of post publication
Make sure that the date of the post (mentioned in the front matter) as well as the date in the file name match. The date should be the publication date for the post, not the date of creation. When changing the publication date, due to postponements, make sure that both, the date in the front matter as well as the filename, will be changed. -
Category
Make sure that the category in the layout of the post is assigned correctly. -
Rendering
Make sure that the post in general is rendered correctly, i.e. that the the post looks nicely, without any weird breaks or misaligned pictures, code examples etc. -
Markdown Style Guide
In general, ensure that these guidelines are applied. -
About the author section
Make sure that there is a YAML file entry for the author and that the id is correctly included in the front matter. Furthermore, you need to ensure that you have as many authors as author ids. You cannot enter two author names but only add one author id.