Blog Approval Best Practices?

Hey

We have a process in place for blog posts on our external customer community. All blog posts are written by colleagues, and are required to go through an editorial review to ensure they are of sufficient standard before publication is allowed. This includes items like Alt and Title tags, SEO keywords and tags etc.

We have a group setup that is only accessible for Arm employees (access is given by the Employee site role). This group is the only place the Employee site role is able to create blog posts:

At a high level the process is as follows:

1. Blog post owner drafts their post in the group's blog application.
2. They ensure it meets our technical writing and graphics guides requirements (images on brand, all required metadata is provided etc. Step 2 in the image above links to a page where we detail everything a post needs before it can be published).
3. The blog post owner then moves to step 3 and creates a forum thread requesting a review.
4. A member of the Content Services team (that owns blogs in the community) will carry out a review of the post.  We have a tool called Acrolinx that houses a technical dictionary and checks spelling, grammar, and style. An example of a review looks like this:
5. Once the review is complete, the post is then scheduled for publication in the relevant blog.

This means pretty much all blog posts need to be signed off before review, and from a scaling perspective, it can create a bottleneck. To address this we have created training for our blog publishers, that allows them to self create, review, and then publish as long as they have successfully completed the training. The Content Services team then periodically spot checks their content to ensure it is of a correct standard.

The training is critical for us to scale the number of people creating blog content, and also to educate them on the value of accessible content (for example, 60% of visitors to our site are countries where English is not the primary language).

Thanks

Oli

Hey

We have a process in place for blog posts on our external customer community. All blog posts are written by colleagues, and are required to go through an editorial review to ensure they are of sufficient standard before publication is allowed. This includes items like Alt and Title tags, SEO keywords and tags etc.

We have a group setup that is only accessible for Arm employees (access is given by the Employee site role). This group is the only place the Employee site role is able to create blog posts:

At a high level the process is as follows:

1. Blog post owner drafts their post in the group's blog application.
2. They ensure it meets our technical writing and graphics guides requirements (images on brand, all required metadata is provided etc. Step 2 in the image above links to a page where we detail everything a post needs before it can be published).
3. The blog post owner then moves to step 3 and creates a forum thread requesting a review.
4. A member of the Content Services team (that owns blogs in the community) will carry out a review of the post.  We have a tool called Acrolinx that houses a technical dictionary and checks spelling, grammar, and style. An example of a review looks like this:
5. Once the review is complete, the post is then scheduled for publication in the relevant blog.

This means pretty much all blog posts need to be signed off before review, and from a scaling perspective, it can create a bottleneck. To address this we have created training for our blog publishers, that allows them to self create, review, and then publish as long as they have successfully completed the training. The Content Services team then periodically spot checks their content to ensure it is of a correct standard.

The training is critical for us to scale the number of people creating blog content, and also to educate them on the value of accessible content (for example, 60% of visitors to our site are countries where English is not the primary language).

Thanks

Oli