Please support our Web Development advertiser: Programming Forums
Sep 6th, 2005, 10:02 am
What is a Wiki?
I have seen the word before when installing eGroupware, a web-based emailing and calendar program that could give Microsoft Exchange a real run for the money. But I haven't had the chance to really think about what a Wiki was until I used Wikipedia, and looked at the technology. Wiki's are cool!
According to Wikipedia, a Wiki "... enables documents to be written collectively (co-authoring) in a simple markup using a web browser. A single page in a wiki is referred to as a "wiki page", while the entire body of pages, which are usually highly interconnected via hyperlinks, is called "the doodle"; in effect, a very simple database."
This sounds very cool! I can think of a number of uses:
* College academic groups using one to write a report. No longer do you need to email the attachment from person to person, and keep track of everyone's little change.
* Business groups using the Wiki to write and store business documents, such as marketing materials, technical specification sheets, and parts lists. Again, no need to keep track of potentially hundreds of email attachments and other materials.
* IT departments for documentation purposes. Keep track of deployed assets, as they can be easily edited when an asset moves or is retired.
But I also see some problems:
* Anyone can edit the Wiki, meaning the information could be under attack. Nothing seems to be in place to protect the data from malicious vandalism, such as the changing of little details here and there to make the document inaccurate, and not easy to access. Note that a number of Wiki's have version control information, along with editing information, so someone could go back and restore the data, but that takes time (money!) to do.
* A Wiki is not a blog. It is not ideally setup to be a blog. Then again, I think about the "use the right tool for the right job" philosophy.
Some Wiki software developers:
* Socialtext (you host it, not free, has lots of options and features)
* pbwiki (someone else hosts it, has features)
* projectforum (you host it, free basic version)
* egroupware (has a wiki module)
I have seen the word before when installing eGroupware, a web-based emailing and calendar program that could give Microsoft Exchange a real run for the money. But I haven't had the chance to really think about what a Wiki was until I used Wikipedia, and looked at the technology. Wiki's are cool!
According to Wikipedia, a Wiki "... enables documents to be written collectively (co-authoring) in a simple markup using a web browser. A single page in a wiki is referred to as a "wiki page", while the entire body of pages, which are usually highly interconnected via hyperlinks, is called "the doodle"; in effect, a very simple database."
This sounds very cool! I can think of a number of uses:
* College academic groups using one to write a report. No longer do you need to email the attachment from person to person, and keep track of everyone's little change.
* Business groups using the Wiki to write and store business documents, such as marketing materials, technical specification sheets, and parts lists. Again, no need to keep track of potentially hundreds of email attachments and other materials.
* IT departments for documentation purposes. Keep track of deployed assets, as they can be easily edited when an asset moves or is retired.
But I also see some problems:
* Anyone can edit the Wiki, meaning the information could be under attack. Nothing seems to be in place to protect the data from malicious vandalism, such as the changing of little details here and there to make the document inaccurate, and not easy to access. Note that a number of Wiki's have version control information, along with editing information, so someone could go back and restore the data, but that takes time (money!) to do.
* A Wiki is not a blog. It is not ideally setup to be a blog. Then again, I think about the "use the right tool for the right job" philosophy.
Some Wiki software developers:
* Socialtext (you host it, not free, has lots of options and features)
* pbwiki (someone else hosts it, has features)
* projectforum (you host it, free basic version)
* egroupware (has a wiki module)
This blog entry was written by kc0arf. It has received 2,248 views, 5 comments, and 1 linkback. It was promoted to featured status Sep 6th, 2005.
•
•
•
•
advertising apple blog browser business data dell development economy email facebook firefox gaming google government hacking hardware ibm intel internet iphone ipod itunes linux mac malware microsoft mobile mozilla mp3 music news open source privacy search security software sony spam stocks technology ubuntu video virtualization vista web windows yahoo youtube
All Recent Tags Comments (Newest First)
alc6379 | Cookie... That's it | Sep 10th, 2005
•
•
•
•
Quick trivia:
What does Wiki stand for?
Wiki is an acronym for What I Know Is...
http://wiki.java.net/bin/view/Javapedia/Glossary#W
What does Wiki stand for?
Wiki is an acronym for What I Know Is...
http://wiki.java.net/bin/view/Javapedia/Glossary#W
Catweazle | Grandad | Sep 7th, 2005
•
•
•
•
A Wiki should be really thought of as a collaborative website development tool. They're far more than a document creation tool, and can include forums, chat, storage and heaps more features.
cscgal | The Queen of DaniWeb | Sep 7th, 2005
•
•
•
•
Yes, but either way, we are talking about hundreds of individual pages.
jwenting | duckman | Sep 7th, 2005
•
•
•
•
They CAN be used for single documents. In that case the document is effectively cut up into paragraphs or short chapters with each becoming a page.
Of course we're talking about rather large documents here, such as scientific research project results which can run into hundreds of pages.
Effectively a wiki is a reader-editable e-book when used as such.
Of course we're talking about rather large documents here, such as scientific research project results which can run into hundreds of pages.
Effectively a wiki is a reader-editable e-book when used as such.
cscgal | The Queen of DaniWeb | Sep 6th, 2005
•
•
•
•
Wikis are NOT used to edit single documents, such as reports. In addition, they are not used to handle a relatively small collection of documents. Rather, they are used to handle large collections of data. The reason for this is because there are two criteria for wikis. The first is that they are fully editable by everyone. The second is that common words and phrases between wiki documents are interlinkable. For example, you'll notice that each time a phrase or "special" word appears in a wikipedia article, it is hyperlinked to its own article. The idea behind this is that they are an interlinkable group of documents about related topics, where each word in one article that has its own wiki article is hyperlinked to it. In essense, they are a collection of articles ala a massive index.
Post Comment
•
•
•
•
Only community members can start a blog or comment on blog entries. You must register or log in to contribute.
•
•
•
•
•
•
•
•
DaniWeb Web Development Marketplace
Related Blog Entries
- One small step for Google, one giant leap for Flash Designers! (13 Days Ago)
- Microsoft shows JQuery some love (14 Days Ago)
- Firefox 3.03 Released. (15 Days Ago)
- Firefox 3.0.3 on way real soon (17 Days Ago)
- Freelance website designer (18 Days Ago)
- Don't Like Political Ads? Write Your Own (20 Days Ago)
- New Pint-Sized PC Packs a Punch (23 Days Ago)
- Google Desktop: a glimpse of the future? (27 Days Ago)
- In Google Chrome, Cracks Appear (Sep 3rd, 2008)
- Dont Bash Chrome it's doing better in it's first beta then Internet Explorer 8. (Sep 3rd, 2008)
Related Forum Threads
- Alternative option to WIKI (PHP)
- Daniweb Wiki? (DaniWeb Community Feedback)
- Suggested Protection (Windows 9x / Me)
- new window in Internet Explorer is always blank (Web Browsers)
- wiki pages (PHP)
- Wiki ! (HTML and CSS)
- can log inbto linux (*nix Software)
Featured Entry