Wiki Edits with Moderation on a Knowledge Base
OfflineHello all,
I am looking for ideas on how other Igloo users are managing wiki edits on a knowledge base.
For some background, our knowledge base is separated into Policies, Procedures, and Forms & Resources.
- Since policies tend to be larger pieces of information, we are keeping policies as PDFs, and embedding in a wiki to display the same way that our procedures appear.
- Procedures are wikis.
- Forms & Resources use folders.
What I am working through is identifying a streamlined process for our content contributors who frequently edit procedures. Right now, all requests are coming to me in various forms; Word Documents, PDF, email requests, etc. and I am making edits to the appropriate procedures. I would like to open drafted content updates to a group of individuals who are responsible for maintaining procedural information.
Road blocks:
- Moderation is not available on edits.
- Edits to published content cannot be drafted; all edits must take place at once and are published live.
- Procedural wikis can also be lengthy, include embedded PDFs, images, subheadings, and other formatting that is not conducive to "copy and paste" in a new wiki, where moderation could occur.
Ideas:
- Moderated comments on the wiki articles, so content contributors can document edits as needed. Content contributors could indicate if more edits are coming or if information is complete.
- Allowing live edits which would be monitored by myself daily, so I can catch formatting needs. This would mean content would be published with incorrect formatting and display issues before I am able to correct.
- I would consider making a duplicate of each wiki in a separate environment where content contributors can edit and I can review for publication, however, "copy and paste" does not maintain formatting and this would be a manual process.
Thank you for reading and for any ideas!
1 Conclusion
Hi Sara,
Great question and format for it, thank you! I think you're on to something with your very last bullet.
- You can have a sort of "pit stop" draft wiki channel.
- Editors Copy/Paste the existing wiki into a new article and publish it (with or without moderation depending on your access model) to its temporary pit-stop channel. From there you can view the changes side-by-side and choose which ones to adjust in the "live" version.
- To solve for formatting, switch to "code view" and copy/paste content into that view.
5 Replies
Hi Sara,
Great question and format for it, thank you! I think you're on to something with your very last bullet.
Hi Brigid Towler
Thank you for the response. I did consider the code view, for more accurate formatting. The road blocks there are infrequent users accidentally changing code of the live procedure and/or not feeling comfortable accessing code view to begin with. I can see this being a pain point in the process. The alternative would be I duplicate a procedure using code view once edits are requested. Once again, this adds another step which results in a bulky process for my content contributors. Any thoughts?
I'm with you on the pros and cons, Sara Ellington!
Moderated comments would take the pressure off the content contributors but keep the edits for yourself. You can follow each article and allow the live edits, checking them as you get notifications - of course as you noted, this has pros and cons too!
Your 3 approaches all work, it might come down to what works best for you and your team. And it might differ by channel.
Interested to hear what ideas others might have!
Hi Brigid Towler
We are proceeding with a separate wiki environment for Content Contributors where I will duplicate wikis as needed, using code view to copy. This way wikis can be saved as drafts and moderated once edits are completed. A downside, however, is images inability to be copied and pasted from one wiki to another. We found that even if images are inserted into the wiki using the WYSIWYG editor, once copied from code view and pasted to the original wiki location, the images break after publication. This means I must replace all images within a wiki at final publication, duplicating the work of inserting an image. If there are any other recommendations to replacing images, I would be happy to hear.
Thanks!
Sara Ellington please write to support@igloosoftware.com on that one, thank you!