New Knowledebase on FHUG


Colin Spencer
 

The new Knowledge Base platform is now ready for migration to start (apart, of course, for the bugs that you eagle-eyed lot will find). Many thanks to Valkrider (Colin) for doing much of the technical heavy lifting (he's much more familiar with WordPress than I am, and doesn't complain at all when I say 'but it would be better if we could just...')

We've focused on making it easy to find content, and to do this, consulted best practice guidelines for a load of Knowledge Bases across the Internet.

The interface is deliberately uncluttered and uncomplicated -- you find the content you want by one of two methods:
  1. Structured browsing by content type and category/sub-category.
  2. A single Search box that works consistently everywhere, and will search the content as written (filtered by content type if you wish) plus category terms and any additional search terms assigned by the article's author to make a piece of content more 'discoverable'. (My perennial example: there will be an article about restoring data from a backup, but it will also have the search term 'recover' because not everybody reaches for the same word for the same thing).
Editing is more straightforward than the old KB as well. For those people who don't want to do more than submit their website, or a download, or recommend a service or utility, they can fill in a simple form (without registering for an account, but quoting their FHUG account details) and after spam-checking and review by an administrator, the content will be published. For people who want to do more complex editing, once they've applied for an editor's account, it's basically standard WordPress editing with some FH specific customisations to make life easier and some simplifications to enforce consistency.

Take a look: New Knowledge Base.

Note: some of the content is test content or has been migrated by a script and needs 'reviewing/sorting out' during the migration process; other content is in the process of being migrated article by article.

There's a style guide in place that addresses formatting and layout (based on best practice for readability), to keep everything looking consistent, but we haven't made any assumptions about the types of articles we will eventually end up with (as we started discussing at Towards a style guide for the new Knowledgebase (17458).)

Our preference is that we focus on migrating existing content first (improving the quality and discoverability if necessary as we go) in parallel with a continued discussion about the types of new content we want to add. Ideally, we'll get all existing content over before FH7 hits, so we only have to make changes in one KB for FH7. Once existing content is across (or discarded), work can start on adding new content (How-To Guides etc.)

We have resources set up for migration: there's an article on how to do it and anyone who applies for an editor's account during the migration period will be given access to the relevant Trello boards (used for tracking migration activity) and a closed mailing list to discuss migration issues (so as not to clutter up the FHUG forums with stuff that's meaningless to most people).

A couple of migration notes: We're going to leave Plugin Help pages where they are in the old KB because of their specific formatting requirements -- they will continue to work as long as needed; and Ancestral Sources documentation will be handled as a separate migration project once the main migration is complete.

So... please volunteer to help the migration and sign up for an editor's account -- the more volunteers we get the faster it will go. Even if you only do one article or a few of the simpler content types, it will really help!

If you want an editor's account you need to be a member of the FHUG forumĀ  so make sure you join that if you haven't already. You just use your username on the FHUG forum to sign up for an editors account.
--

Colin Spencer