How are folks who are *not* using Reach managing workflow approval on their blogs? Are you using the blog node given this deficiency? In the process of finalizing our implementation, we've identified two options, though there are caveats to each, and I'd love to hear people's thoughts: Nested/promotion design Implementing a blog node restricted to internal users with the BlogAuthor and BlogManager roles. Each post would require n kudos from the peers to ensure quality of content and structure. All posts with Kudos >1 would be reviewed by a restricted subset (Admin or Moderator) who can move the articles to the external blog node once approved. The deficiency here is that there's no real audit or approval notion to this process, and I'm not certain that publication to Google search would happen effectively by a move to the blog node (versus normal publication behaviors). TKB -> Blog publication process Those with specific role-type would have access to a TKB node, redressed and internal. User would submit their drafts within this TKB, allowing for normal TKB workflow approvals. Upon approval, article would be then moved to the blog node as a blog article. Caveats - I don't even know if this will work, given that they're different nodes entirely. Curious to hear how others have implemented their workflows (minus Reach) where necessary. Thanks Jamie
... View more
