So that the publishers know what changes you made before they publish it.
So that anyone checking the revision history for whatever reason knows what happened.
So that we know you're serious about your change.
"tweaked a typo change".
"Fixed a typo: niternet changed to internet".
Added new paragraph directly below "Internet settings" header.
Straight away if you know it doesn't require discussing.
You shouldn't, this needs discussing.
You will need to consult the Knowledge Base Police.
This is OK to be left how it is.
Typo and grammar correction, broken links, and the correction of obvious errors.
A straightforward change that does not require any discussion.
A change which will need minor discussion before editing.
Only when you see a broken link in an article.
The edit may be inaccurate, or may not need changing at all.
To see if anyone else is on it first and give and accept feedback from other members on it.
It boosts the stats in the Contribute section, which is always good right?
To brag about the edit you're making, so that everyone knows how great you are.
Identify which Knowledge Gardener is leading the change.
Confirm that the suggestion will be included, and to insert it in the List of pending changes.
All suggestions should be approved or rejected within 7 days.
Historical reference, opinion, advertisement, etc.
Giffgaff specific things that are current.
Members who are looking for information whether it's for themselves or to become an Approved Helper.
New up to date information.
Important information that all giffgaffers will need to know.
Up to date descriptions of the giffgaff service.
Giffgaff products and services.
Factual and neutral information.
Information on other giffgaffers.
A wiki for all giffgaff related items.
It is for getting as much information regarding everything giffgaff, that's up to date and factual.
It is used for advertising your affiliate link.
It is much like a museum where you can learn about the history of giffgaff.
It is used to get information about other members for members that ask on the community.
AROUSE it before saving it
Ensuring you have enough kudos in order to make the change.
Information has quirky images and font styles.
Delete the previous article and start from scratch.
Make up new ones, for the hell of it.
Absolutely, in fact more tags the merrier.
No, we don't want to clog up the KB articles with multiple tags.
It depends on what the subject is, depending on how many tags you can have for it.
This ensure that whatever a member is searching, they will find the relevant KB article.
This is because we like to have pages and pages of tags, no matter what they are, linked to KB articles.
We are addicted to adding tags to anything and everything.
Tags look cool and organised.
Edit current KB articles so information is up to date and grammatically correct.
To write stories and scenarios for the KB.
Makes sure the KB is fun and quirky, with emoticons that makes it easier for other members.
Editors read facts found on Google and then writes them up for the Knowledge Base.
A publisher's role is to be the bee's knees and be 100% positive information is correct before publishing an article.
A publisher is able to publish all changes to official giffgaff pages such as our 4G page.
A publisher creates content for KB as well as threads in top tips and ensures that information is correct.
A publisher is a single member of staff who approves all edits and changes to Knowledge Base articles.
Answer any questions that can't be answered by other members.
Provide new information as it comes in.
Resolve disputes between members.
All that has been mentioned.
It gives members the ability to keep gaining knowledge when you cross reference KB articles together.
Links make the page look pretty.
It's so we know how many times a link has been clicked, so we know what members are mostly unsure about.
This is for our own benefit which may or may not involve a secret KB club.
Inform you of all the editors and publishers and any updates that are happening within the KB
Let you know what is happening in the world of Approved Helpers
Tell you if there are any errors that can be found within the KB
To look pretty and organised with what is happening in the KB
Easily understood for everyone who reads it, including English-As-A-Second-Language Eva and Velma.
Written in paragraphs of facts without bulletpoints as it is then easier to read.
Full of short fun facts, it doesn't matter if it's in text speech either.
Written in a way that only people who know technology will understand.
Absolutely not. Our KB needs to be accessible and understood by everyone. Including people who don't 'get' technology.
Sure, as long as also it explains what that term means.
Yep, its perfectly fine.
If an article has lots of information it breaks the page into sections, making it easier to navigate.
They can be used to link multiple pages together.
They are used as a base for all links within the KB
They are used every time there's a bulletpoint in an article
A link that reloads the page and takes the clicker to specific place on the page.
A link that takes the clicker through to a place on the page they are currently on without reloading the page.
A link that looks like an anchor. Ahoy.
A link in the chain that holds an anchor onto the ship it's part of.
The image isn't too large or small.
The image is clearly explained in text within the article.
The title of the image clearly explains what is contained in the image
There's an image of a cat somewhere within the article.
You're not allowed to use images in an article.
That the title text (part of the image HTML) clearly explains what the image is.
That any information conveyed by the image is also clearly in the text of the article.
Don't use images.
Images are easier to see, so use them instead.
It makes it easier to find the relevant article for members.
To make it easier to keep the KB up to date.
Because we have more important things to do, like making fruitcakes.