How to Add Content to the Knowledge Base

Publishing New Content

When you first create a piece of content, it is created as a Draft and is not visible to anyone without an editor’s account.  While you are working on it, you should Save Draft at regular intervals, using the panel towards the top of the right hand pane of your editing window. You can Preview your work whenever you wish; and Save Draft when you’ve finished for now, and then return at a later date.

When you’re happy with what you’ve done you can Publish it immediately (which makes it visible to everyone) if you’re an experienced Editor, or Submit for Review if you have less experience.

If you Submit for Review, a more experienced Editor will check what you’ve done and either approve it for publication or send you an email with some suggested changes.  (If the changes are simple, they may edit the content themselves before approving it). If they approve publication, you will receive an email notifying you.

Please don’t Submit for Review until you’re certain you’ve finished editing, to (1) avoid experienced Editors doing unnecessary review work and (2) avoid publication of something that needs further edits.

Note: Once Published, if you subsequently return to edit a piece of content you will Update it rather than Save Draft and Publish. To unpublish something you should set the status to Draft.

Note: Experienced editors also get the option to publish at a particular date/time. We are not using this feature within the Knowledge Base.

Modifying Existing Content

Experienced Editors

Experienced editors can make quick/minor changes to published content (e.g. fix a broken link or typo, add or delete a few sentences) without changing the content status. If in doubt, consider whether you can complete the changes in a brief editing session.

If an experienced Editor wants to make more extensive changes to published content (changes that don’t fit into the description above), they should save any changes as a Pending Revision (to avoid existing content being made unavailable while it’s being edited) and include DO NOT REVIEW in the Title to avoid other Editors approving prematurely. Once they’re happy that all changes are complete, they should modify the Title and Approve their own Edit.

Less Experienced Editors

Less experienced editors can make changes to existing content, but must save them as a Pending Revision. A more experienced Editor will check what you’ve done and either approve it for publication or send you an email with some suggested changes.  (If the changes are simple, they may edit the content before approving it). If they approve publication, you will receive an email notifying you. If you save a Pending |revision to return to it later, please include DO NOT REVIEW in the Title to avoid Editors approving it prematurely

Reviewing Content

When reviewing content created by less experienced editors:

  • Check for compliance with the Style Guide
  • Check for factual errors and material omissions
  • Check for and question advice that goes against common genealogical practice, or advocates (for example) unethical or illegal behaviour

If changes needed are small (e.g. typos or style guide compliance) you should make the changes yourself and approve the content. For more substantial matters, you should advise the person who prepared the content what needs to be done.  If there is disagreement on how/if the content should be changed that cannot be resolved between you, open a discussion in the FHUG forums to get a wider range of input and reach a consensus there.

Do not:

  • Alter somebody’s writing style
  • Alter the advice given without reaching agreement with the editor first