Adding or Updating Simple Content without an Account<\/h2>\n
Under Contribute on the Knowledge Base menu, you will find a set of links to:<\/p>\n
- \n
- Add\/Update a Download<\/a><\/li>\n
- Add\/Update a Video<\/a><\/li>\n
- Add\/Update a Service or Utility<\/a><\/li>\n
- Add\/Update a Member Website<\/a><\/li>\n<\/ul>\n
Each of these of these will take you to a simple form for the relevant content type, where you specify:<\/p>\n
- \n
- A title.<\/li>\n
- One or more of:\n
- \n
- The relevant categories for the entry;<\/li>\n
- The relevant \u0192h<\/span><\/span> versions;<\/li>\n
- A skill level (where appropriate);<\/li>\n
- Additional search terms that will help Knowledge Base users find the entry.<\/li>\n<\/ul>\n<\/li>\n
- Possibly, a URL (depending on what content you’re creating).<\/li>\n
- A simple text description of the content you’re creating, which will be used to create the main body of the content. If you’re replacing an existing entry,\u00a0 (preferably) supply a complete new entry or provide clear and simple instructions for the changes to be made on your behalf.<\/li>\n
- Your FHUG user id and email address (this will not be displayed or saved in the Knowledge Base, but will be used to verify that you are a member of FHUG).<\/li>\n
- Whether this is a completely new entry, or a total replacement for an existing entry with the same title<\/strong>.<\/li>\n<\/ul>\n
If you haven’t specified a mandatory item (marked with a *) you will not be able to submit your suggestion.<\/p>\n
Once you’ve submitted your suggestion, and it passes the site’s spam filter, it will be reviewed to check that (1) you are the FHUG user you say you are; and (2) that there is no malicious content (sad, but necessary these days). If everything is OK, it will then be published. If your submission is associated with a file, we will contact you by email to ask for the file.<\/p>\n
If you want to add extra links, images etc. to your simple content, you will need to edit it with an editor’s account<\/a>.<\/p>\n
<\/p>\n
<\/a>Editing with an Editor’s Account<\/h2>\n
An Editor’s account will allow you to create or edit all content types (Articles, Downloads, Links, Glossary items) and add or edit items in the Media Library which can be then be included in content. You’ll need to familiarise yourself with your Editor’s Dashboard<\/a>; with the structure of various content types; with the Knowledge Base style guides for content and layout\/appearance<\/a>; and how to use the Knowledge Base editor. If you’re going to request an Editor’s Account, please familiarise yourself with the User Help<\/a> first, which outlines the key content types and navigation facilities.<\/p>\n
Requesting an Editor’s Account<\/h3>\n
Under Contribute on the Knowledge Base menu, there’s a link to Request an Editor’s Account<\/a>. Provide your FHUG User ID and email address, which will be checked against the FHUG membership list; once you’ve been verified, you’ll be emailed details of your Editor’s account (which will have the same name as your FHUG User ID).<\/p>\n
We recommend the first thing you do when your account is created is change your password (on your Profile page).<\/p>\n
<\/a>Welcome to Your Dashboard<\/h3>\n
When you log in, you will be be presented with your Dashboard and some useful links for editors.<\/p>\n
![\"\"](\"data:image\/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==\")
<\/div>\nDown the left you can see a menu of the content types you can edit.<\/p>\n
- \n
- Media is the library of image files, downloads etc.<\/li>\n
- Glossary terms are very brief descriptions of key terms that will pop-up on hover in other content, with a link to more detailed information.<\/li>\n
- Code Snippets are Lua code snippets for use by plugin developers.<\/li>\n
- Downloads, KB Articles, Member Websites, and Services & Utilities are the main content types within the Knowledge Base.<\/li>\n
- Revisions shows changes to existing articles proposed by yourself which are awaiting review before publication.<\/li>\n
- On your Profile page, you can change your email and password, and the colour scheme for your dashboard. Most of the other information is not used and can safely be left blank.<\/li>\n
- Tools does not currently offer you any functionality and can be ignored.<\/li>\n<\/ul>\n
.<\/div>
<\/div>\nSelect a content type, and choose whether to Add New (create a new piece of content) or select All… to see existing content, as shown in the next screenshot. From the Dashboard left hand menu, you can also view a list of all the Search Terms<\/a> that have been created, and create new ones.<\/p>\n
<\/div>\nHovering over the content title shows its editing options in a menu that appears underneath.<\/p>\n- \n
- Edit allows you to edit the content;.<\/li>\n
- Quick Edit allows you to edit some of the fields associated with the content (but not the content itself).<\/li>\n
- View shows you the content as an ordinary user would see it.<\/div><\/div><\/li>\n<\/ul>\n
Both Add New and Edit take you to the same editing screen.<\/p>\n
<\/p>\n
Creating or Editing Content<\/h3>\n
<\/div>\n- \n
- A typical word-processor style toolbar gives you access to formatting and the ability to add links, images, videos, tables, columns and code elements.<\/li>\n
- Hovering over any of the buttons pops up a tool tip to show their function.<\/li>\n
- There is also some Knowledge Base-specific functionality.<\/div><\/div><\/li>\n<\/ul>\n
The First Sentence<\/h4>\n
The first sentence of a piece of content is used to summarise the content on the summary page of items within a particular category (topic, download type etc.) so it is important to make this first sentence a succinct summary of the content that will let readers know if they wish to view it. Do not preface it with it with ‘Introduction’ or similar; that’s a waste of a word wherever an excerpt appears. Avoid using shortcodes and creating links within this first sentence as they will not show up in summaries or tooltips, which can yield very odd results lacking vital information.<\/p>\n
Style Guidance<\/h4>\n
<\/div>\nThe style guidance for layout\/appearance is available to you at any point when you’re editing. You can see a brief summary of key points, or invoke a pop-up of the full guide to check something without leaving the editor.<\/div><\/div>\nWorking with Links<\/h4>\n
From the toolbar, you can create a link to:<\/p>\n
- \n
- another piece of content in the Knowledge Base<\/li>\n
- an external web page<\/li>\n
- another place within the page you are editing (an anchor).<\/li>\n<\/ul>\n
To link to an anchor, navigate to the destination you want to use and press the anchor (bookmark)
button; give the anchor a single word identifier. Then when you create a link, you will have the option of linking to that anchor. Note: when you create a multi-page article, anchors following page breaks will not be visible and you will need to link to the relevant content using the full URL including the anchor.<\/p>\nIf you need to edit a link, click on it within the editor and you will find options to edit the link or remove it.<\/p>\n
You must<\/strong> verify that all links you create or edit (anywhere in the Knowledge Base) work as you expect. Admins will check for broken links on an irregular basis, but it is your<\/strong> responsibility when creating or editing content to include functioning links.<\/p>\n
Working with Images<\/h4>\n
- \n
- Inserting an image (using the Insert\/Edit Image button on the toolbar), or simply copying and pasting the image inserts an image from elsewhere on the Internet into the content you’re editing. It will not be available to other pages within the Knowledge Base (unless they also embed it from the original source). However, it might be useful if (for example) you want to display a page from the target website within content such Services & Utilities and Member’s Websites, where it is unlikely to be relevant elsewhere. Note that changes to the original image will not be reflected in the Knowledge Base.<\/li>\n
- One special class of image (\u0192h<\/span><\/span> user interface icons) is discussed under Knowledge Base Shortcodes and Other Customisation<\/a>.<\/li>\n
- To make changes to the way an image is displayed, click on it and you will get a menu of alignment options, a remove option and an edit (pencil) option.<\/li>\n
- If you want to use an image that you think might get re-used, use the Add Media button above the toolbar. You can use an image that has already been placed in the Media Library<\/a>, or you can upload a new image. If you subsequently make changes to the way it is displayed on a page, you can choose to do that on a single page or everywhere that it’s used (if you decide to do it everywhere, it is your<\/strong> responsibility to check that your changes look OK everywhere it is used.) See Managing Media<\/a> for more information on how to do this.<\/li>\n<\/ul>\n
Working with Videos<\/h4>\n
- \n
- If you include a video, it will also be included in the video showcase.\u00a0 Add the YouTube video URL in the Video URL field for a KB article. The video showcase will show the first few words of content, so make that clear and punchy, and keep the title short. Check how things look on the Videos page and adjust if necessary.<\/li>\n
- There is a shortcode available for legacy content, but we expect that new content will not need it.<\/li>\n
- DO NOT add the video url directly into the content. Doing so will result in a team of trained ninjas tracking you down and administering a severe slap on the wrist. Also some grumpy KB admins, and honestly… you’d prefer the ninjas.<\/li>\n<\/ul>\n
Working with PDFs<\/h4>\n
To link to a PDF (you can’t upload one to the Media Library), insert an image of the first page (or other representative image) and set the image to link to a custom URL (the URL of the PDF).\u00a0 The PDF will open in a lightbox.<\/p>\n
Downloadable Files<\/h4>\n
- \n
- If you need to add a link to a downloadable file, use the download shortcode<\/a>.<\/li>\n<\/ul>\n
Working with Tables and Columns<\/h4>\n
The Table tool is self-explanatory, but please remember to size table columns in % (using the Table icon > Cell > Table Cell properties with a column selected) to make them responsive.<\/p>\n
The Columns tool is powerful, once you’ve understood a few basics:<\/p>\n
- \n
- It works by inserting shortcodes (an instruction to WordPress in [ ])<\/li>\n
- You can create equal width columns, or Advanced Layouts of mixed widths.<\/li>\n
- There are Utilities available to make sure text following a column element is correctly spaced.<\/li>\n<\/ul>\n
If you intend to use the Columns tool, you should watch this brief demo to get the best out of it. (Skip the first 40 seconds because the Columns tool is already installed and activated).<\/p>\n\n
Inserting Code<\/h4>\n
You have two options for including code within content.<\/p>\n
The simplest way is to use the <> Code button on the toolbar to mark
a piece of text as code<\/code>.<\/p>\nIf you want to add a more complex piece of code with syntax highlighting etc. (such as you’ll find in a Code Snippet) then use the {…} Code Insert button. There is no custom syntax highlighting for \u0192h<\/span><\/span> data expressions, etc. so <> is the recommended option except for Lua Code Snippets<\/a>.<\/p>\n
Knowledge Base Shortcodes and Other Customisation<\/h4>\n
There are a few \u0192h<\/span><\/span>-specific shortcodes defined for use in the Knowledge Base, and where such a shortcode exists you must<\/strong> use it (to ensure that the Knowledge Base still works even when external resources move):<\/p>\n
- \n
- Type [fH] or use the fH button on the toolbar to insert \u0192h<\/span><\/span><\/li>\n
- Type [fh_menu]
Some > Menu> String<\/code>[\/fh_menu] to highlight an instruction to navigate to the menu position Some > Menu > String<\/a>, or use the fH Menu button on the toolbar to insert a placeholder shortcode for a menu string.<\/li>\n- <\/a>Type [help]
page reference|page description<\/code>[\/help] to display a link to a page within the \u0192h<\/span><\/span> version 6 help file online; [help7]page reference|page description<\/code>[\/help7] to display a link to a page within the \u0192h<\/span><\/span> version 7 help file online; and [writingplugin]page reference|page descriptio<\/code>n[\/writingplugin] to display a link to a page within the \u0192h<\/span><\/span>version 7 plugins help file online .\n- \n
- To get the page reference and page description, you need, navigate to the page in the relevant online Help file. The page description is the title of the page. To get the page reference click Get Link<\/em> towards the top left (underneath Contents<\/em>, Index<\/em> and Search)<\/em>. The page reference you need is the word between ‘#’ and ‘.html’ in the url for the page.<\/li>\n
- Tip: The Help file link Welcome to Family Historian<\/a> will take you to the V6 help file so you can navigate to the page you need and find the id in the url, and the page title; likewise Welcome to Family Historian<\/a> will take you to the V7 help file.<\/li>\n<\/ul>\n<\/li>\n
- Type [topic]
topic number|topic title<\/code>[\/topic] to link to a FHUG forum discussion, or cut and paste the shortcode from the relevant topic in the forums (click on the * next to the topic title), to display e.g.\u00a0 Please read BEFORE posting<\/a><\/li>\n- Type [plugin]
plugin-page-ref|plugin name<\/code>[\/plugin] to link to the plugin store.\u00a0 Plugin-page-ref is the unique identifier for the plugin, visible at the end the url (following the last \/) when you go to the plugin page in the Plugin Store, and plugin name is the name of the plugin.\u00a0 So [plugin]record-census-data-uk-2|Record Census Data (UK)[\/plugin] will yield Record Census Data (UK)<\/a>.<\/li>\n- <\/a>Type [download]
url|download title<\/code>[\/download] to insert a link to a downloadable file from the media library. The resultant downloaded file will have spaces in the file name instead of hyphens or dashes.\u00a0 To get the fileurl<\/code>, upload the file to the Media Library and click Copy the link (on the right) instead<\/strong> of<\/strong> Insert into…<\/li>\n<\/ul>\n<\/a>Often, when you’re describing actions within the \u0192h<\/span><\/span> User Interface, it’s clearer to show an icon than it is to simply name it. ‘Click Customise’ is not as clear as ‘Click
Customise’. If you click on the \u0192h<\/span><\/span> Icons button above the editor, you’ll find the common user interface icons for you to copy and paste as images into content.\u00a0 Once you have pasted an icon, you need to adjust its alignment and size. Click on it and click the pencil, then in the css class type cs_v and click update. It does not alter on the edit screen but will be the right size and alignment when the page is viewed.<\/p>\n<\/p>\nAccordions<\/h4>\n
You can use the Accordion button to create a piece of content that is hidden until the user chooses to view it, and then remains visible until they choose to close it. It creates a Header (which can be styled as h3, h4 or h5 ) and a placeholder to add the content.<\/p>\n
<\/p>\n
Table of Contents<\/h4>\n
The Table of Contents will be automatically generated from Heading levels 2, 3 and 4. Do not<\/strong> disable the Fixed ToC.<\/p>\n
Glossary Entries<\/h4>\n
Do not<\/strong> disable the Glossary for your post, unless you’re confident that you are not referring to anything in the Glossary.<\/p>\n
If you use a term or phrase that is in the Glossary, it will be highlighted the first time it occurs on the page. You do not need to do anything to achieve this, other than ensure the Glossary entries you need have been created. It is your<\/strong> responsibility to create<\/a> any missing entries that your content requires.<\/p>\n
If you are using a word or phrase that appears in the Glossary but also has an everyday meaning (e.g. note), you can add a shortcode like this:<\/p>\n[glossary-ignore]
note<\/code>[\/glossary-ignore]\nto prevent the glossary pop up appearing on that instance of the term.<\/p>\n
More Fields<\/h4>\n
Some forms of content have More Fields below the main body, and you should not forget to populate these if relevant.<\/p>\n
Help file references<\/h5>\n
Knowledge Base Articles can have 2 optional help file links\u00a0 associated with them (one for V6 and one for V7); these should be used to avoid repeating information that is in the relevant Help File(s)<\/p>\n
- \n
- Enter it in the field provided as
page reference|page description<\/code><\/li>\n- The page reference you need is the word before ‘.htm’ in the url for the page; and the description should be the title of the help page.\n
- \n
- Tip: Welcome to Family Historian<\/a> will take you to the V6 help file so you can navigate to the page you need and find the id in the url, and the page title; and Welcome to Family Historian<\/a> will take you to the V7 help file so you can navigate to the page you need and find the id in the url, and the page title.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n
Forum Topics<\/h5>\n
For Knowledge Base articles, there may be relevant discussions in the FHUG forums. Enter them here, one link per line.<\/p>\n
- \n
- Type [topic]
topic number|topic title<\/code>[\/topic] to link to a FHUG forum discussion, or cut and paste the shortcode from the relevant topic in the forums (click on the * next to the topic title), to display e.g.\u00a0 Please read BEFORE posting<\/a><\/li>\n<\/ul>\nUseful External Links<\/h5>\n
For Knowledge Base articles, you may wish to provide links to external sites without breaking the flow of your article.\u00a0 This is particularly true if there are a lot of relevant external links, and\/or you want to enable readers to easily find the links in one convenient place.<\/p>\n
Insert the links here, with a brief description of what each is.<\/p>\n
<\/a>Show on Front Screen<\/h5>\n
For Knowledge Base articles, you have the option to mark an article as important enough to be linked from the front page of the site rather than from within its topic page.<\/p>\n
Use this sparingly, or it will become meaningless, and note the caveat<\/a> about how you need to add topics to the article.<\/p>\n
Download<\/h5>\n
Downloads, unsurprisingly, need a file to download; you should use the Add File button to add the relevant file to the Media library<\/a>.<\/p>\n
External Website<\/h5>\n
Links (Services & Utilities, and Member Websites) need an external website link. Enter only the URL of the website as plain text. When displayed, it will be displayed with the name of the content.<\/p>\n
<\/p>\n
Categories and Search Terms<\/h3>\n
All content must be Categorised before publication; you may also want to include extra Search Terms. Both mechanisms are designed to make it easier for readers to find the content that will help them.<\/p>\n
Categories<\/h4>\n
<\/div>\n<\/div>\n<\/div><\/div>\nBefore you publish your content, you must allocate it to one or more categories or sub-categories:<\/p>\n
- \n
- A topic for Articles (as shown here)<\/li>\n
- A download type for Downloads<\/li>\n
- A website type for Member Websites<\/li>\n
- A link type for Services & Utilities.<\/li>\n<\/ul>\n
This determines where it shows up as users browse the site. You can put your content in more than one category, but think carefully before you do this, as it may be confusing for some users.<\/p>\n
<\/a>However, for articles, the FAQs (Frequently asked questions) topic is a special case and should be assigned (in addition to any other topics) if the question warrants a prime position on the home page of the Knowledge Base. You should also note that, if you mark something to be shown on the front screen<\/a>, you must put in a topic<\/strong> and optionally a sub-topic (rather than just a sub-topic).<\/p>\n
For most content types you will also have to choose one or more \u0192h<\/span><\/span> versions for which the content is relevant; and one or more skill levels. Users can filter searches on version and\/or skill level.\u00a0 If the content is version- or skill level-agnostic, select all the versions or skill-levels; if the content is usable by a number of skill-levels or relevant to a number of \u0192h<\/span><\/span> versions, select all the relevant skill levels\/\u0192h<\/span><\/span> versions.<\/p>\n
<\/a>Search Terms<\/h4>\n
<\/div>\nFor most content types, you also have the option of including additional search terms.<\/p>\nThese should be words or phrases that don’t appear in the content, but which users might use to search for it. For example, ‘recover’ on an article about restoring a backup.<\/p>\n
Please take some time<\/strong> to consider what would best be included here, so that the search experience for users is as good as we can make it.<\/div>
<\/div>\n<\/p>\n
Publishing New Content<\/h2>\n
<\/div>\nWhen you first create a piece of content, it is created as a Draft<\/em> and is not visible to anyone without an editor’s account.\u00a0 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.<\/p>\nWhen 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.<\/p>\n
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.\u00a0 (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.<\/p>\n
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.<\/p>\n
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.<\/p>\n
Note: Experienced editors also get the option to publish at a particular date\/time. We are not using this feature within the Knowledge Base.<\/sup><\/div>
<\/div>\nModifying Existing Content<\/h2>\n
Experienced Editors<\/h3>\n
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.<\/p>\n
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<\/strong> 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.<\/p>\n
Less Experienced Editors<\/h3>\n
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.\u00a0 (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<\/strong> in the Title to avoid Editors approving it prematurely<\/p>\n<\/div>\nReviewing Content<\/h2>\n
When reviewing content created by less experienced editors:<\/p>\n
- \n
- Check for compliance with the Style Guide<\/a><\/li>\n
- Check for factual errors and material omissions<\/li>\n
- Check for and question advice that goes against common genealogical practice, or advocates (for example) unethical or illegal behaviour<\/li>\n<\/ul>\n
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.\u00a0 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.<\/p>\n
Do not<\/strong>:<\/p>\n
- \n
- Alter somebody’s writing style<\/li>\n
- Alter the advice given without reaching agreement with the editor first<\/li>\n<\/ul>\n
<\/p>\n
<\/a>Managing Media<\/h2>\n
- \n
- Most of your interaction with the Media Library will be in the context of adding, replacing and changing the display of media items within the context of an article etc.<\/li>\n
- However, you can view the contents of the Media Library using the Media button on your dashboard. In particular, you can get a list of content items where a media file is used, so that you can assess the impact of any changes you’re intending to make to something in the library.<\/li>\n
- If you replace a Media Library item in a piece of content, this may result in an old item that is no longer used.\u00a0 Admins will review the library on an irregular basis and tidy it up as necessary.<\/li>\n
- You can add new media in advance of it being required; this might be useful if you want to bulk upload a set of screenshots, for example.<\/li>\n<\/ul>\n
<\/a>Code Snippets<\/h2>\n
Code Snippets are very simple pieces of content. They have:<\/p>\n
- \n
- a title<\/li>\n
- a body<\/li>\n
- an \u0192h<\/span><\/span> version<\/li>\n<\/ul>\n
The body should:<\/p>\n
- \n
- Describe what the snippet does\/how it works<\/li>\n
- Include one of more code blocks containing the snippet and related code (e.g. usage examples) constructed using {…} on the editor toolbar\n
- \n
- Make sure you select Lua highlighting<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n
When viewed, the code blocks will be highlighted to show the Lua syntax, and have an icon when you hover over a code block to copy it to the clipboard for pasting into a plugin.<\/p>\n
<\/a>Creating Glossary Entries<\/h2>\n
Glossary items are very simple but important pieces of content.<\/p>\n
- \n
- The Glossary Term Title is the word or phrase that, when used in another piece of content, will trigger the display of the Glossary pop-up the first time it is encountered. Matching is not case sensitive.<\/li>\n
- The pop-up is limited to the first 40 words of the glossary entry; take care to make this a meaningful definition of the term.\u00a0 The entire entry should be less than 40 words.<\/li>\n
- You can also define Additional key terms for an entry \u2014 terms which don’t match the Glossary Term Title but which should still lead to the same term definition (to cater for differences in terminology for the same thing by different authors, or to associate e.g. both Events and Attributes with the Fact Glossary entry).<\/li>\n
- If users click on the Glossary pop-up, there are a number of options:\n
- \n
- The default option is to display the whole of the Glossary item \u2014 this allows for a simple definition just a little longer than 40 words.\u00a0 Do not use this option.<\/strong><\/li>\n
- Alternatively, a Glossary term can define an internal or external link that will be opened. An internal link might be a long article on using some aspect of \u0192h<\/span><\/span>. An external link might be to guidance on some aspect of genealogy best practice.<\/li>\n
- We recommend you set internal links to open in the same window, and external links to open in a new window (the default); and also to mark the links as “No Follow”.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n
Deleting Content<\/h2>\n
- Alternatively, a Glossary term can define an internal or external link that will be opened. An internal link might be a long article on using some aspect of \u0192h<\/span><\/span>. An external link might be to guidance on some aspect of genealogy best practice.<\/li>\n
- The default option is to display the whole of the Glossary item \u2014 this allows for a simple definition just a little longer than 40 words.\u00a0 Do not use this option.<\/strong><\/li>\n
- Make sure you select Lua highlighting<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n
- Check for compliance with the Style Guide<\/a><\/li>\n
- Type [topic]
- The page reference you need is the word before ‘.htm’ in the url for the page; and the description should be the title of the help page.\n
- Tip: The Help file link Welcome to Family Historian<\/a> will take you to the V6 help file so you can navigate to the page you need and find the id in the url, and the page title; likewise Welcome to Family Historian<\/a> will take you to the V7 help file.<\/li>\n<\/ul>\n<\/li>\n
- Type [fh_menu]
- Type [fH] or use the fH button on the toolbar to insert \u0192h<\/span><\/span><\/li>\n
- If you need to add a link to a downloadable file, use the download shortcode<\/a>.<\/li>\n<\/ul>\n
- Add\/Update a Video<\/a><\/li>\n
![\"\"](\"https:\/\/fhug.org.uk\/kb\/wp-content\/uploads\/2020\/10\/Dashboard-300x233.png\")
<\/div>\n![\"\"](\"https:\/\/fhug.org.uk\/kb\/wp-content\/uploads\/2020\/05\/Article-list-1024x340.png\")
<\/div>\n![\"\"](\"https:\/\/fhug.org.uk\/kb\/wp-content\/uploads\/2020\/05\/edit-1-1024x468.png\")
<\/div>\n![\"\"](\"https:\/\/fhug.org.uk\/kb\/wp-content\/uploads\/2020\/10\/styleguide-300x246.png\")
<\/div>\n![\"\"](\"https:\/\/fhug.org.uk\/kb\/wp-content\/uploads\/2020\/05\/bookmark.png\")
button; give the anchor a single word identifier. Then when you create a link, you will have the option of linking to that anchor. Note: when you create a multi-page article, anchors following page breaks will not be visible and you will need to link to the relevant content using the full URL including the anchor.<\/p>\n![](\"https:\/\/fhug.org.uk\/kb\/wp-content\/uploads\/2020\/helpv6\/familyconnectionmapper_6.png\")
Customise’. If you click on the ![\"\"](\"https:\/\/fhug.org.uk\/kb\/wp-content\/uploads\/2020\/06\/icon-formatting-1024x485.png\"){kind=icon}
<\/p>\n![\"\"](\"https:\/\/fhug.org.uk\/kb\/wp-content\/uploads\/2020\/05\/topics-288x300.png\")
<\/div>\n![\"\"](\"https:\/\/fhug.org.uk\/kb\/wp-content\/uploads\/2020\/05\/versions-300x251.png\")
<\/div>\n![\"\"](\"https:\/\/fhug.org.uk\/kb\/wp-content\/uploads\/2020\/06\/Annotation-2020-06-07-184659-300x204.png\")
<\/div>![\"\"](\"https:\/\/fhug.org.uk\/kb\/wp-content\/uploads\/2020\/05\/searchterms-300x187.png\")
<\/div>\n![\"\"](\"https:\/\/fhug.org.uk\/kb\/wp-content\/uploads\/2020\/05\/publish.png\")
![\"\"](\"https:\/\/fhug.org.uk\/kb\/wp-content\/uploads\/2020\/10\/Submit-for-Review.png\")
<\/div>\n![\"\"](\"https:\/\/fhug.org.uk\/kb\/wp-content\/uploads\/2020\/10\/Pending-Revision-300x259.png\")
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.\u00a0 (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<\/strong> in the Title to avoid Editors approving it prematurely<\/p>\n