Suggestions

From nswccWiki
Jump to: navigation, search

Contents

What do we want to see happen here?

Any ideas?

As a plaything to introduce members to truly collaborative writing it looks like a great idea.

How about a success stories page?

A Solutions to Common Problems page would be good. System (DET / Other) Platform? windows, mac, other.

Current research links? Best practice (globally or NSW?...is there a difference?)

So would the usual Frequently Asked Questions page

I would also like to have a History of the NSWCC page as well

Could some artistic person come up with a NSWCC logo> Remember that we are a subset of the NSWCEG.

Working with Scratch as this has been mentioned by a few people lately

Tutorial Links - Applications Tutorial Links - Windows Tutorial Links - Macintosh

I would like to see a page for lesson ideas for Primary level teachers.

Prefer to keep this wiki as CC only information separate from teaching to keep it consistent.

(A) Put lesson information onto the Australian Leson Exchange site we setup over the long weekend. Aust Lesson Exchange Also includes ALE Moodle ao we can try out Moodle Courses. ALE Moodle

A page or category depending on size devoted to listings of free or open source software and guides associated with that software.

A cleanup gatergory has been created here if you are a first time wiki eiditor tagging a page with this tag will allow more experienced people to easily find your page and help you with formatting and layout. This is not meant to be a stab at anyone wikitext is hard to wrap your head around.

Category Pages

Category pages are special pages that are built by "tagging" entries with a category tag. For example I have created a page called HP Thin Client Auto Login which is surprisingly about auto logging in the thin client PC's. By adding a line
[[Category:OASIS]] 
to the page(s) in question it will automatically add a link to the OASIS Category page. By adding a category as you write the page it allows people to find information and follow links within the wiki a lot easier. If they are reading something on OASIS simply by clicking the category link at the bottom they are taken to a page with a plethora of information and links to other OASIS pages.

Also by using categories it is easier to clean up after yourself or another person if you need to move something around as they are auto generated pages.

Sub categories

As an example I have created a small page on an open source image editing tool called Paint.NET this page is added to the category Graphics Editing this graphics editing category page is then added to the category Free and Open Source Software as a sub category.

Organisation

Ideally we want information to be easy to find. No walls of text etc. Best practices for wikis are lots of smaller pages. For example Instead of writing a page with a whole bunch of similar programs on it, write a separate page for each one and add it to a category for whatever the subject is. Then if people wish to add additional information about a program they can add it to the programs page instead of the what would end up being a much longer page with lots of different bits of information on them.


Note about Table of contents

The table of contents will be automatically generated for any page with more than 3 headings. There are three variables for the ToC:

__NOTOC__ 	Hides ToC on the current page.
__FORCETOC__ 	Forces the table of contents to appear.
__TOC__ 	Places a ToC here (overriding any __NOTOC__). Multiple ToCs are no longer supported.
                If __TOC__ is used multiple times, only the first occurence causes a ToC to appear.

To use any simply place the text anywhere on the page you are editing

Vandalism

Vandalism can be prevented by users actually requesting an account and signing in before being able to edit. I am editing this having supplied no credentials at all. Check the ALE wiki, to see how this was set up. Chris?? any comments?

mark

Chris: In the LocalSettings.php file you need to add the line:

# Disable anonymous editing
$wgGroupPermissions['*']['edit'] = false;

This will require the user to create an account and confirm their email address, before they can contribute to this wiki.

[correction] - they have to confirm "AN EMAIL ADDRESS" - hotmail, yahoo etc are all anonymous.

[Chris:] This is true. No system is perfect... It is creating the balance of being useable and useful, without creating a burden on one or more individuals having to confirm accounts, as well as making it easy to contribute.

Another option would be to authenticate against the mailing list database, this would only allow people on the list to contribute.

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox