Glossary

Welcome! » Content Control » Glossary

Content: [[include include:languages pagename=content]]

LOOK at content-2 too : the new layout… : content-2
LOOK at content-3 too: ( table layout ) : content-3
( a quick shot without long thinking! )

Level	Title	Description	Link
-	Beginners & essentials
-	what is a wiki	Explanation	what-is-a-wiki-site
-	what is a wiki-farm	Explanation	what-is-a-wiki-farm
-	what is wikidot	Explanation	what-is-wikidot
-	what is an account	When we need it	what-is-an-account
-	E-mail adress	Why we need it	what-about-e-mail-adress
-	User.id's	Why and when we need it	what-about-userid
-	Terms of Service	legal issues & conventions	terms of service
-	Copy rights..lefts	cell-content	cell-content
@	Novice
@	create an account	Explanation	create-an-account
@	Login At Wikidot	not anonmymous	login-at-wikidot
@	Logout from Wikidot	end wikidot-session	logout-from-wikidot
@	Edit Your Profile	Edit Your Profile	Edit-Your-Profile
@	Join a wiki	Get membership	join-a-wiki
@	Find A Page	Search & List pages	Find-A-Page
@	First edits
@	Edit A Page	Edit A Page	Edit-A-Page
@	Page Option Buttons	Page Option Buttons	Page-Option-Buttons
@	Start a New Page	Start a New Page	Start-a-New-Page
@	Page Title	Page Title - How to edit?	page-title
@	Editing FAQ	Editing FAQ	Editing-FAQ
@	Introduction To Images	How to embedd images	Introduction-To-Images
@	Upload an Image	How to upload images	Upload-an-Image
@	Link to a Wiki Page	Link to a Wiki Page	Link-to-a-Wiki-Page
@	Forum Option Buttons	Forum Option Buttons	Forum-Option-Buttons
@@	First Site
@@	Start A Wiki	Start A Wiki	Start A Wiki
@@	First Steps On A New Wiki	First Steps On A New Wiki	First Steps On A New Wiki
@@	Special Edits
@@@	Special Site Setups
@@@	Forum summary
@@@@	For high level User
@@@@	Overall issues
@@@@	about this handbook
@@@@	Conventions	How to translate?	Translations
@@@@	Multilingual	How is this build?	Magic Language Navigation

Beginners ( = essentials)

- what is a wiki what-is-a-wiki-site
- what is a wikifarm
- what is wikidot
- what is an account

- what is meaning the needed email-adress
- what about User.id's
- Legal issues ( terms of Sevrvice)
- Copy rights..lefts
- create an account
- login / logout
- Private messaging & Notifications
- Profile settings
- how to Join a site ?

First edits:

- Novice edits
- standard "widgtes" using
- create the first pages
- how does a forum work
- first posts
- first threads

First creation of a site

- Thoughts about target group of visitors
- design / layout ( forum ? private/public)
- Naming ( Url )
- Title ( not the URL ! )
- technical settings ( permissions ) for pages
- Forum imstallation
- Forum permissions
- Menu structure ( nav)
- Inviting Members, Email

Second edit step:

- Sophisticated technic (includes, modules)
- Divs, Span ,
- embellish text
- Image upload , embeding
- File upload, download

Forum related issues:

- where to store images,
- Forum installation
- Forum permissions
- Spam in Forum & Pages - what to do

Second Site Step:

- Nav + categories designed
- Private - Unauthorized categories
- Page Tags
- Special List of pages
- Backup done - save it
- delete a wiki
- restore a wiki

Third level for users:

- CSS - Themes
- RSS & Feeders
- get moderator
- get invited to be admin
- Spam in Forum & Pages - what to do
- abuse users - ban, block

Overall:

( means I have no idea where to put these issues)
- "Content" page ( with such structure overview as a new "start-2" page
- Known issues
- Snippets
- How-Tos where they belongs to..
- adsense API
- glossary

About:

( content is all about the handbook technic, the multilingual layout, the translate conventions)
- Conventions for translations ( for thge Handbook)
- technic with magic translations

Perhaps links to <before page and after> page ?

Regards Helmut

Links:

Tags: content structure to_be_revised

Translations

This page has to be rewritten and the include:languages has to be cleaned from [[include include:languages pagename=actualpagename]] which is not necessary anymore

This page describes the conventions neccessary for translation of the handbook into other languages (localisation).

Please - if You want to contribute any translation into your language - feel free to do so, but keep an eye on the conventions written here!

And if You have any proposals write them down in our forum here ( menu at left top ) or on the coffee table in the community forum:

http://community.wikidot.com/forum/c-11432/coffee-table

The idea is to have language-dependent categories in the handbook site.

This means
all english document pages belong to the (namespace/ category) en:
all french document pages (direct translations from the english original) belong to fr:.
all german document pages belong to category de:

The "Title" can be / should be in your original language, but the url - the "page name" after he language category - has to be always in english!" Or the navigation would never find the parallel page with another language-category.

The page names itself should be in their local language, ( like fr:glossaire for en:glossary)
but (if necessary and easily possible), redirected from the direct "copied" original page fr:glossary.

The language codes to be used are defined in the ISO standard:

http://www.gnu.org/software/gettext/manual/gettext.html#Language-Codes

If you want to add another language go to en:add-another-language page!

All listings in a specific language can be done with the Pages module :

[[module Pages category="de"]] a.s.o.

The Page tags Cloud works with categories too.

The main (start) page (Welcome page) on the left side is then only the starting point into other (even english!) categories!

Typical page name for the "virtual start page of " the "handbook" in german ( german "Welcome page") :

"www.handbook.wikidot.com/de:start ! - please change the "de:" to YOUR language code (see down the link) .

Do not forget to copy the nav:side panel to your language category nav:side-xy.
Any admin can than join the (category - dependent!) nav:side-xy to the correct language-category.
And change the "edit this panel" to the correct new nav:side-xy !

The in all roots -included include:languages page should be changed to new languages too!

Categories:
all languages shall have their own category, English included in order to list english tags in the corresponding nav:side.
Yes, it is possible to have one nav:side per category.
Thus nav:side-en nav:side-fr nav:side-de
- gerdami 30/7 at 20:26

French series

I just started the french series and it is really easy to create fr:pages by adding the prefix fr: and keeping the original pagename but translating the page title.
All pages should have its equivalent in the other languages. Keeping the original English name will give no problem for me to link to non-yet-existing de:what-ever-page-name.
Moreover, with the tool Wanted pages we can list easily missing pages. They are listed alphabetically with the fr: prefix. Easy.
- gerdami 30/7 at 21:37

English

Once a reference English page name has been chosen, it is not suitable to rename it (except from the beginning) … fr: and de: … would not be renamed automatically.
From now, the original list-all-pages lists all pages (all languages mixed) => we should now RENAME ALL English doc pages to en:pages.
Do not forget the + show dependencies !!!
- gerdami 30/7

Let us open a forum for translators in this wiki, one section per language, plus one for the reference language, and may be (I'm not sure) a per page forum.
- gerdami 30/7

Tags: category convention language localisation to_be_revised translations

What Is A License ?: [[include include:languages pagename=what-is-a-license]]

This article is meant as a general introduction to licenses. As the specific laws will vary from place to place and given the fact that the author is not a lawyer, please do not consider this legal advice.
Thanks to hartnell for his words here, the founder of Game Design Novice - a typical Wikidot Site created from him with the free Wikidot software - it is Open Source!

What is a License?

In amateur game programming and design you hear about licenses all the time, especially when games and resources are distributed across the internet. In fact, even the text of and resources provided by Game Design Novice, are available under the terms of a license. What are these things, that we call licenses? What use are they? Do you really need one? This article will answer those questions.

Copyright

Before there can be a license, there must be copyright. Someone must own the rights to something. This is very important. Because if someone doesn't own the copyright, the material in question is public domain and therefore no license is needed.

Copyright, of course, is the legal right to control your work. Many people believe that copyright is the right to "profit" from your work. While this is certainly part of it, you can't profit from your work if you cannot control it. If anyone, anywhere, at anytime can copy your work, there is no reason for anyone to pay for it, they can just copy it.

Therefore, copyright gives you the legal right to determine who can and cannot make copies of your work.

The End User License

Whenever you buy and install software, you agree to what is commonly titled "The End User License". When you buy Adobe Photoshop or any other commercial software, you do not actually own the software. You do, however, own the CD that it came on. However, the program itself still belongs to the company who owns the copyright. The End User License gives you permission to use that software under certain conditions, assuming that you have paid for the permission to use it. The most common conditions of use under an End User License are:

That you only use the software on one computer. After all, that's all you've paid to get permission for.
That you do not make copies of it.
That you do not hold the company responsible for any damages the software does.

The Group License

With an End User License it is assumed that one person has paid for permission to make one copy of the software. This copy is not necessarily a back-up copy and such laws are not discussed in this article. Instead, you must realize that when you install the software, you are making a copy of it. The copy is from CD to your computer.

The Group License is an option with many software packages and helps us illustrate the "permission" aspect of licenses. A group license grants further permission for the software to be copied on more than one computer. Often the limit is based on a finite limit (say 5) of computers, or all of the computers at a location (at one school). Naturally, since you are buying more instances of permission with a Group License, it costs quite a bit more.

Copyleft

The above two sections describe how a copyright holder sells permission to people who want to use their work. The permission, and the terms for gaining that permission, are encompassed in the license. But what if someone wants to retain copyright over a work and doesn't want money for someone to use it? What if they do not even care if someone asks for permission in the traditional sense (buying a product, or a friendly email)? Enter Copyleft.

A copyleft license such as a Creative Commons license or a GNU license gives permission for someone to use a copyrighted work under simple and easy to understand conditions without the exchange of money. For example, Game Design Novice is licensed under the Creative Commons Attribution 2.5 License. Under this license, you are allowed to use anything you see here (unless stated otherwise) for any reason as long as you follow one condition: you attribute the work to "The Game Designers of Game Design Novice" and link to the page you got it from.

In short, since money is not involved, and work is used more or less freely, Creative Commons and GNU licenses are a way for an author to get credit. In fact, if someone decides to use your work without following your conditions, there's nothing you can do about it without spending a large amount of money on lawyers. Here, in the Copyleft world, we tend to work on an honor system.

How to set and choose the license for your wiki

Go to your site manager yoursite.wikidot.com/admin:manage.
You can set different licenses for different categories of pages.

You will get a page with following content:

It is very important to clarify the copyright and ownership issues for your site. We highly recommend setting an open "copyleft" license that allows making the Content more or less free to copy, modify and use.

This is particularly important when your Site is created and edited collaboratively.

Read more about Creative Commons licenses, use a wizard to select the proper license or just visit Creative Commons.

Choose the category (typical example list here):

_default
admin
css
forum
nav
system

or set Inherit from "_default" for the others..

Choose the license:
( see list next paragraph)

Licenses supported

(copied from Site manager)

Creative Commons Attribution-ShareAlike 3.0 License (recommended)
Creative Commons Attribution 3.0 License
Creative Commons Attribution-NoDerivs 3.0 License
Creative Commons Attribution-NonCommercial 3.0 License
Creative Commons Attribution-NonCommercial-ShareAlike 3.0 License
Creative Commons Attribution-NonCommercial-NoDerivs 3.0 License
Creative Commons Attribution Share Alike 2.5
Creative Commons Attribution 2.5
Creative Commons Attribution No Derivatives 2.5
Creative Commons Attribution Non-commercial 2.5
Creative Commons Attribution Non-commercial Share Alike 2.5
Creative Commons Attribution Non-commercial No Derivatives 2.5
GNU Free Documentation License 1.2
Standard copyright (not recommended)
Other: Custom license text: (max 300 characters ) - A few HTML tags are allowed: <a>, <img/>, <br/>, <strong>, <em>

Wikidot Terms of Service

Licences are part of Wikidot Terms of Service (TOS)
which can be read at http://www.wikidot.com/legal:terms-of-service

Conclusion

And there you have it, the bare minimum you need to know about licenses.
You will find the chosen license on a wikidot.com site as the last line at the bottom of any page! Have a look and you will find here:

"Unless stated otherwise Content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License"