For those of you using Lithium's blogging component, how are you managing workflows? For example, we need approved contributors to be able to post something for review, then have it approved before it goes live.
I saw this posted as an idea here: https://community.lithium.com/t5/Product-Ideas/Need-a-better-blogging-workflow/idc-p/270554#M11950
But there's no way people haven't found a workaround as this is an essential feature.
We use Lithium Reach to publish blogs now but prior to that we used the native community blog component to publish. In both cases though only internal staff were given the opportunity to submit blog content.
That said, I have been thinking about ways that a blog could be opened to allow user participation, which would need to be approved before going live. As an initial trial we are using a email dropbox for contributors to submit content as a word document and our community managers are publishing on their behalf through the Lithium Reach platform.
I have not tried to implement this to test if it works but my idea for a more formalised process was as follows;
- setting up a new blog that would be used as an approval area
- set the default access level for the blog so that users can create an article but NOT read them
This would effectively create a hidden blog that only users granted access (moderators, admins and anyone else you granted access to view) could actually see the submitted content. The process for your approvers would then be to;
- review newly submitted blogs, making adjustments as required
- rejected blogs either deleted or moved another board created to house rejected content (as a way of keeping a record)
- approved blogs moved from the approval blog to the appropriate live blog
The drawback would be that the publish date, and hence the sort order, would be based on when the user submitted rather than when you approved.
Thanks for your insight @DanK. We're actually not using Reach at this time - but it's good to know what others are doing.
Hi @sherrie! Apologies for the delay on this.
At Lithium, when we post natively to our Community Blog, we do have a workflow that seems to work swimmingly for us. We typically float the content in a word document via email for initial drafting/editing. Contingent on the blog author (internal/external), we do one of two things:
- For internal: As an admin, I give permission to the user to for the specific blog to be a “guest blogger” and then I switch user to actually schedule posting for the blog under their name. I send out the draft link for final approval, and encourage anyone to make edit directly to blog, where they see fit.
- For external: If one doesn’t already exist, I create an account on our Community and then I assign them to guest blog**(temporary access) for a blog, and same process as above, with me going on and posting on their behalf.
**With the above processes, I am better able to maintain proper formatting (Lithium style) as well as keep the tone of our blogs consistent (informative, yet relaxed and, at times, humorous tone. )
** I elect to make them a “guest blogger” as opposed to a “blog author” because it limits their access, so they can’t fudge with anything too much.
Hope this is helpful.