A wiki is a hypertext publication collaboratively edited and managed by its own audience directly using a web browser. When you hear the word ‘wiki’, you most likely think immediately of Wikipedia, the most famous online encyclopedia. In fact, except Wikipedia and the server software behind, MediaWiki, you can find many other Wiki or Wiki software. In this article, we’ll introduce you the easiest way to create your own powerful Wiki on computer, setup a portable DokuWiki instance on Windows PC. Even beginners can install and configure their personal Wiki on local computers without any learning curve.
DokuWiki has many advantages compared to similar Wiki software.
- Easy to install and use
- Low system requirements
- Built-in Access Control Lists
- Large variety of extensions
- Over 50 languages supported
- Device independent
- Open Source
Wikis are quick to update and new pages are easily added. Designed for collaboration while maintaining a history of every change, DokuWiki could be used as
- Corporate Knowledge Base
- Private notebook
- Software manual
- Project workspace
- CMS – intranet
Download DokuWiki for Windows
Get it from its official website here https://download.dokuwiki.org/
The Candidate Release is recommended for most users. Make sure to select MicroApache (Windows). This component include a minimal webserver with PHP in your download so you don’t have to install third-party server tools like XAMPP, Wampserver. It helps you quickly run DokuWiki on your Windows PC or even an USB stick without extra installation. This is recommended for personal, single-user use only.
DokuWiki is available in a whole bunch of languages. You can save space by removing the language packs you won’t need.
Choose from some of the most popular plugins. We can skip this for now as we don’t need any to get started. We only need them to extend the functions of our Wiki site.
Click Download at the upper section or hit the Start download at the bottom to download the latest DokuWiki installer on to your PC.
The latest DokuWiki installer is merely 2.5MB without the web server software and additional plugins. With the MicroApache (Windows) included, the installer is only 8.8MB, still very small compared to MediaWiki which takes up to about 150MB for the latest version 1.34.1.
Unzip DokuWiki on Windows computer
DokuWiki package will be wrapped in tgz container. This is a very common UNIX archiving format similar to the popular ZIP format many Microsoft Windows user probably know. You will need an extraction tool to extract it on your Windows computer. You can choose 7-zip, PeaZip, IZArc, TUGZip, Simplyzip, WinZIP, WinRAR, WinACE or other similar tools. No need to install any of these tools if you already have one zip/unzip software installed on your PC.
Install & run the free Wiki on your Windows PC
DokuWiki provides us the easiest way to create our own powerful Wiki on local computer or network. Follow these steps to setup a portable DokuWiki instance in Windows.
Copy the extracted DokuWiki folder to a USB stick or your computer hard drive. Under the DokuWikiStick folder, you can find two subfolders and an executable file, dokuwiki, server and run.cmd.
Double click to run run.cmd file, the Windows command prompt opens. DokuWiki on a stick started, your web browser will now open http://localhost:8800. The DokuWiki Installer opens on your web browser.
The web installer will be English. You can however change it to your own language from the top right corner. Then fill in the required information. If you are the only one who will use this Wiki site on your computer, you can disable ACL. Click Save button at the bottom to finish the configuration. You can go to delete the install.php file in the dokuwiki folder. Then head to your Wiki site.
This is the welcome page of your Wiki site on local machine. Your wiki needs to have a start page. If the start page doesn’t exist, the Welcome page will be the home page.
Under the “Create your first pages“, there will be a link to the start page. Follow that link and create the first page of your Wiki site.
Stop DokuWiki site
In the Windows command prompt window where shows the status of your Wiki site, press any key to stop DokuWiki site and service.
This guide provides instructions on how to install and configure MediaWiki, both manually, and by easier alternatives. Installing more than one wiki and installing existing wikis are also covered. The appendices provide links to more detailed installation notes for specific system configurations and other less common uses of the software.
- 1 Upgrade guide
- 2 Manual installation
- 2.1 Summary
- 2.2 Main installation guide
- 3 Alternatives to manual installation
- 4 Wiki families (multiple wikis)
- 4.1 Installing MediaWiki more than once
- 4.2 Multiple wikis with one MediaWiki
- 5 Installing an existing wiki
- 6 Appendices
- 6.1 Advanced uses
- 6.2 Advanced configuration
- 6.3 Installation assistance
- 6.4 System-specific instructions
- 6.5 Notes
- 7 See also
If you are already running MediaWiki, see the Upgrade guide.
For experienced users, here is the quick version of the installation instructions. Most users (like if you don’t know how to install or check for the prerequisite software on your computer) will want to follow the main installation guide.
- Check that your system meets the following minimum requirements. (See Installation requirements for more details. Make sure to also check the RELEASE NOTES shipped with MediaWiki for requirements.) You’ll need:
- MediaWiki (current stable version is 1.37.1)
- A web server such as Apache or IIS
- Local or command line access is needed for running maintenance scripts
- PHP 7.3.19/7.4.3+
- with Perl Compatible Regular Expressions
- with Standard PHP Library
- with JSON support
- A database server, that is, one of the following:
- MySQL 5.5.8+
- PostgreSQL 9.2+
- SQLite 3.8+
Image thumbnailing requires additional programs. Parsoid (required by VisualEditor) and other services have their own requirements.
- Download MediaWiki(direct link to download the stable release version) and extract the archive to a web-accessible folder on your computer.
- Point your browser to the directory where MediaWiki was extracted and follow the link to the setup screen. It should be in the form http://domain/directory/mw-config/index.php . Replace directory with the path to your extracted MediaWiki folder. If installing on a local machine, replace domain with localhost . If you install locally and later want to access your wiki from domain, then you will need to change LocalSettings.php from localhost to domain. If installed on a remote server, replace domain with your server’s domain name (e.g. www.myserver.com).
- Follow the on-screen instructions to complete the process.
These instructions are deliberately brief. There is a lot that could go wrong, so if in doubt, you are advised to read the full instructions!
Main installation guide
- Before installing MediaWiki, read these:
- Manual:What is MediaWiki?
- Manual:MediaWiki feature list
- Manual:Installation requirements – Check these before going any further!
- Manual:Installing MediaWiki
- Configuring MediaWiki
- Manual:Config script – Initial configuration using the configuration script
- Manual:System administration – Further configuration
- Manual:Extensions – Installing extensions
Alternatives to manual installation
If your head is swimming from reading the above — or you feel frustrated, stuck, or lost — this section is for you.
You can avoid manual installation by using a pre-integrated MediaWiki software appliance, hosting services with 1-click installation, or wiki farms.
If you are installing for development or testing, consider using MediaWiki-Vagrant, a set of configuration scripts for Vagrant that automate the creation and update of a virtual machine that runs MediaWiki and your choice of extensions and services.
Official docker images are released on Docker Hub.
You can also use community resources based on platforms such as Docker. This is managed by Jenkins and should be kept up-to-date for some time.
These are community based resources and should always be treated with some measure of caution. Use at your own risk.
|Warning:||Programs provided by webhosts to automatically install applications such as MediaWiki can, and frequently do, mishandle the process, resulting in errors and a failure to install MediaWiki. If you encounter this problem, it does not mean that you cannot install MediaWiki; all it means is that you should install manually following these steps. There are benefits to doing this, including more control over where on the server and file path you want to install it, the ability to use a shared database, or the ability to control more features of the wiki during the installation.|
Wiki families (multiple wikis)
A wiki family is more than one wiki installed on the same computer.
Installing MediaWiki more than once
One approach is to install multiple instances of MediaWiki (such as with a software bundle like the Bitnami MediaWiki Stack) in different directories – one for each wiki. For example, you want an enterprise wiki and a personal wiki, and you want to keep them totally separate.
Multiple wikis with one MediaWiki
You could use a single installation of MediaWiki for multiple wikis, by either:
- Using a different database for each wiki. See $wgDBname .
- Using a different database prefix for each wiki. See $wgDBprefix .
Installing an existing wiki
Some users wish to install MediaWiki with Wikipedia, Wiktionary, or some other wiki loaded. This is useful for reading offline, for conducting experiments, and for mirroring/forking.
The main (but not necessarily the easiest) method for doing this is to install MediaWiki and then import. See Manual:FAQ#Wiki importing.
(Non-MediaWiki solutions, such as Xowa and Kiwix, can be found at Database download, and are probably the best options).
The following pages give instructions about how to install/configure MediaWiki for other, less common purposes.
The following pages cover some of the more advanced configuration options:
- FAQ: FAQ#Installation and configuration
- #mediawikiconnect channel on IRC
- mediawiki-l is the high-traffic mailing list to ask for support.
The following pages give more detailed installation instructions aimed at specific systems. However, by and large Manual:Installing MediaWiki is more up to date, and better written than the per system docs, and as such it is recommended you first consult Manual:Installing MediaWiki before looking at a per system installation documents.
Want to create your own personal wiki? These websites will help you make your own wiki for free (or a small price).
If you’re looking to create a wiki page, there are quite a few web apps that can help. Some require you to pay for the service; others let you make a free wiki.
If you’re wondering how to create a wiki, here are several sites you should check out today because they’ll make the process a lot easier.
MediaWiki is one of the most popular wiki platforms on the web. It is entirely open source and lets you create a wiki for free.
Originally used on Wikipedia, the site now also provides the backend for many other common wiki sites, including Wiktionary, Wikimedia Commons, and Wikidata.
The platform’s biggest selling point is its impressive customization options. There are more than 1,900 extensions, 900 configuration settings, and support for 300 languages.
To use MediaWiki, you need to have a server that runs PHP and a compatible SQL database. Other notable features include support for rich content, edit tracking, namespaces (so multiple pages can exist with the same name), and templates.
Lots of people don’t have the time nor the technical expertise to use a complex wiki platform like MediaWiki. If you want a more straightforward way to create a wiki, check out SlimWiki. The site makes it easy to make a wiki for your company, group, or project.
The wiki owners can choose who is able to change the content—other users can either be editors or have read-only permissions. Content on SlimWiki follows a Collections to Pages hierarchy. You can group as many pages as you want into a Collection.
SlimWiki is free for up to three users. Thereafter, each user costs $5 per month. Paid accounts also offer custom domains, page exports, public pages, and 1 GB of storage space per user.
Under the hood, Wikidot is a wiki hosting service—a.k.a., a “wiki farm.” On a wiki farm, a single instance of the wiki’s code runs on an array of servers. The site’s admins are responsible for maintaining the servers and managing individual wiki’s spaces.
Let’s talk about features. Wikidot offers unlimited pages, an unlimited number of revisions, custom CSS themes, backups, and an unlimited number of members of public wikis.
The free version supports five private users. Each user gets 300 MB of storage space in the free version. For $49.90 per month, the storage limit rises to 30 GB, and the number of private users increases to 10. The most expensive plan costs $239.90 per month, offering unlimited users and 200 GB of storage.
4. Tiki Wiki
Tiki Wiki is a free-to-use open source wiki-based content management system like MediaWiki. You don’t need HTML knowledge to create a wiki on Tiki Wiki, but if you have the skills, HTML editing is available.
If you’re using Tiki Wiki to make your own wiki, you’ll be able to enjoy a WYSIWYG editor, complete revision history retention, revision comparison tools, and wiki RSS feeds.
You can organize pages by category and/or tag, and organize groups of pages into a hierarchy. If needed, the wiki’s admins can lock particular pages to prevent further editing. As you’d expect, you can embed content, easily manage backlinks, and manage user permissions. You can adjust the permissions based on the type of material to be edited.
Tiki Wiki has an impressive library of plugins. If you need to add extra functionality to your wiki, you should be able to find what you need amidst the hundreds of extensions.
At first glance, DokuWiki is very similar to MediaWiki and Tiki Wiki–it’s open source and free to use. However, it boasts a much easier learning curve. If you’re not tech savvy and you value ease-of-use, this could be the wiki platform for you.
Toolbars and access bars make editing pages a breeze, breadcrumbs are supported for easy navigation, and there’s a vast number of plugins to extend a wiki’s functionality.
DokuWiki boasts some cool automated features. They include future links (pages that don’t yet exist are highlighted in red), backlinks, tables of contents, and indexing. The site also offers templates. First-time wiki makers will find them useful.
Fandom (known as Wikia until early 2019) is another easy-to-use wiki site for anyone who wants to create a free wiki. Fandom accepts wikis on any subject matter, but the majority of wikis on the site coalesce around books, films, video games, and TV series.
The wiki pages are powered by the MediaWiki backend. This allows users to benefit from many of the platform’s benefits without worrying about hosting and other technical issues.
The original Wikia was founded back in 2004 by Jimmy Wales—the same person who launched Wikipedia. Indeed, Wikia (and thus Fandom) has often been referred to as the commercial, for-profit arm of the non-profit Wikipedia site.
7. Make Your Own Wikipedia Page
Anyone can register as a Wikipedia editor and create a Wikipedia page. It’s easy to create content for a page that’s missing (denoted by a red link). Just log in with your account, add the necessary material and sources, and hit Publish Changes.
Of course, just because anyone can edit Wikipedia doesn’t mean there is a free-for-all. The site’s other editors will swiftly remove articles about yourself, your company, your band, your family, your sports team, and so on. Before you know it, you might have a Wikipedia edit war on your hands.
Remember, new pages need to be noteworthy enough to go into an encyclopedia. Aside from personal pages, content such as essays and original research will not be accepted.
Create Your Own Personal Wiki With OneNote
Although it’s not a website, you might consider using OneNote if you want to make a personal wiki. The app offers many of the same features as the dedicated wiki sites, including wiki syntax, page linking, and tables of contents.
Wikipedia hasn’t changed much since it was introduced two decades ago. But you can make it better and enjoy it more with these free apps and tools.
Dan joined MakeUseOf in 2014 and has been Partnerships Director since July 2020. Reach out to him for inquires about sponsored content, affiliate agreements, promotions, and any other forms of partnership. You can also find him roaming the show floor at CES in Las Vegas every year, say hi if you’re going. Prior to his writing career, he was a Financial Consultant.
Subscribe to our newsletter
Join our newsletter for tech tips, reviews, free ebooks, and exclusive deals!
Get the highlights in your inbox every week.
When you think of the word “wiki,” examples like MediaWiki or DokuWiki probably come to mind. They’re open source, useful, powerful, and flexible. They can be great tools for collaborating, working on your own, or just organizing the piles of information in your life.
On the other hand, those wikis are also big. They need quite a bit of additional digital plumbing to run. For many of us, this is overkill, especially if we only want to use wikis on our desktops.
If you want to get that wiki feeling on your desktop without dealing with all of that plumbing, you easily can. There are a number of solid lightweight wikis that can help you organize your information, keep track of your task, manage your notes, and more.
Let’s take a look at three of those lightweight, desktop wikis.
Zim Desktop Wiki
Zim Desktop Wiki (Zim, for short) is relatively small, quite fast, and easy to use. It’s built around the concept of notebooks, which are collections of wiki pages on a single topic or grouping.
Each notebook can contain any number of pages, and you can link between those pages using either CamelCase (a favorite of wiki users everywhere) or using an option on the toolbar. You can format your pages with Zim’s wiki markup or, again, by clicking a button on the toolbar.
Zim lets you export your pages into several formats, including HTML, LaTeX, ReStructuredText, and Markdown. You can also take advantage of Zim’s numerous plugins to add spell checking, an equation editor, a table editor, and more to the application.
attr__field_file_image_caption[und][format]__panopoly_wysiwyg_text attr__field_folder[und]__9402″ height=”437″ src=”https://opensource.com/sites/default/files/zim.png” title=”Zim Desktop Wiki” typeof=”foaf:Image” width=”550″ />
Zim Desktop Wiki
TiddlyWiki isn’t a piece of software, it’s a large HTML file. Weighing in at around 2MB, TiddlyWiki is one of the most flexible options out there. You can store the file on your computer, put it on a network drive, or carry it with you on a flash drive. But don’t let TiddlyWiki’s outward simplicity fool you, it’s a very powerful tool.
To use TiddlyWiki, you create what are called “tiddlers.” Tiddlers are items on your wiki, such as notes, journal entries, bookmarks, and task lists. A tiddler can be anything you want it to be. When working with your tiddlers, you can add wiki markup using TiddlyWiki’s version of WikiText and also images. TiddlyWiki even packs a rudimentary paint application.
If that wasn’t enough, TiddlyWiki has a built-in set of plugins, which let you change the editor for your tiddlers, add tools to help import data from Evernote, do mathematical typography, render Markdown, and more.
attr__field_file_image_caption[und][format]__panopoly_wysiwyg_text attr__field_folder[und]__9402″ height=”400″ src=”https://opensource.com/sites/default/files/tiddlywiki.png” title=”TiddlyWiki” typeof=”foaf:Image” width=”700″ />
While not the prettiest of applications, the venerable WikiPad gets the job done, and gets it done very well.
When you want to create a set of notes around a topic, such as information for an article you’re writing or a project plan, you create a new wiki page. From there, you add sub-pages and link them together by naming those sub-pages using CamelCase. You can create as many wiki pages as you want, and you can have as many of them open (in separate windows) as you need.
In addition, you can add basic formatting using WikiText, and you can also paste images into your wiki pages. When you want to share your wiki pages, you can post them online or print them—WikidPad has a very good HTML export feature.
WikidPad only comes in the form of a Windows installer or a source code archive. It doesn’t have packages for popular distributions. However, you don’t have to compile the software to use it with Linux. The WikidPad wiki has simple, but detailed instructions for launching the software from the command line.
attr__field_file_image_caption[und][format]__panopoly_wysiwyg_text attr__field_folder[und]__9402″ height=”402″ src=”https://opensource.com/sites/default/files/wikidpad.png” title=”WikidPad” typeof=”foaf:Image” width=”620″ />
Do you have a favorite lightweight or desktop wiki that helps keep you organized? Feel free to share it with our community by leaving a comment.
The wiki allows experts in various areas вЂ“ client knowledge, specific business processes, transactional details, etc. вЂ“ to share their knowledge for an overall business benefit. Access to a shared internal knowledge base increases your teamвЂ™s collective knowledge. It also reduces time spent searching for information, streamlines onboarding and training processes, and ensures preservation of institutional knowledge by continuously capturing team membersвЂ™ knowledge.В
How to create an internal company wiki
Setting up an internal wiki for your business can be relatively easy if you use the right tool. Traditional wikis have numerous limitations:В they may be overly complex, unintuitive, or require too much time spent searching by the user. Fortunately, better options are available.
With a user-friendly internal wiki tool, you can build a company wiki thatвЂ™s easy to search, edit, and navigate with a sensible content hierarchy. Your internal wiki should allow linking between your pages, integrate with your other knowledge management tools, and provide permissions and access rights management.
Here are some simple steps to follow to implement your ideal internal wiki:
Select your softwareВ
You want a tool that offers all of the features mentioned above. In most cases, you are also looking for software that is either very easy to install or configure or skips these steps and works right from your browser. Integration with your companyвЂ™s other tools are key to keeping your internal wiki up to date and providing value to your team. Learn more about choosing a knowledge management software.
Import content or start creating
With software that supports integration, you can easily import your companyвЂ™s existing content into your new internal wiki. The right tool also makes creating and editing new content an easy-to-understand, user-friendly process.
Implement internal links
Adding internal links to related, similar, or complementary content on internal wiki pages can make it more efficient for team members to find what they need. Adding internal links to additional content on the wiki allows your users to enhance their understanding about a specific topic or process.В
Decide on permissions and access rights
You will need to configure your internal wikiвЂ™s permissions and access rights based on what content should be shared with everyone in your company versus what should be private or only available to certain teams. Permissions can be set to determine who is allowed to edit your content, as well as which employees should access your account settings and billing information.В
Welcome your team to the wiki and solicit involvementВ
A well-designed wiki welcome page can explain its intended benefits for employees and provide guidance on how to use it. It can also answer questions about searches, editing permissions, and key contacts. To make sure your company derives the most benefit from an internal wiki, encourage team members to regularly contribute, calling attention to their areas of expertise and offering incentives for adding and editing content, when appropriate.
Benefits of internal wikis
Company wikis are generally very easy to set up and populate initially, which can make them a great solution for getting started in knowledge management. Anyone familiar with Wikipedia can understand how they work, and many solutions are offered as part of other software packages (ex: Confluence is part of AtlassianвЂ™s larger software packages, including Jira and Trello). Here are some other benefits of internal wikis:
Content creation and editing
Internal wikis usually have simple content management systems (CMS) that allow anyone to create and format long form or short form knowledge. The functionality usually includes the ability to create outlines or bullets, hyperlinks, different heading levels, colors, as well image embed functionality.
While you may want to wall off certain sections, wikis are designed to be edited by anyone. Allowing everyone at the company to add what they know makes it easy for subject matter experts to add their know-how to a system that can be accessed by all.
в¤ґ Upgrade your company wiki with Guru
Guru supports you so you can support your customers.
Challenges of traditional internal wikis
Traditional wikis quickly become outdated and difficult to manage as your team grows and your knowledge scales, which leads to declining usage within your company. While real-time collaboration is generally easy with traditional corporate wikis, there are some major drawbacks to using them as long term knowledge management and content management solutions.
Knowledge and ownership verification
ItвЂ™s not always easy to see when each piece of knowledge in a traditional company wiki was last updated. You may need to implement a separate, consistent cycle to review ownership and information in order to ensure your teams are using the most up-to-date information.
Internal wiki structure
While the actual information added to a wiki is totally up to you and your company, the internal architecture of a traditional wiki is generally top-down, with overarching topics leading to more granular pages. While it makes initial setup easy, it can make maintenance more difficult over time, as itвЂ™s not always obvious what pieces of company information relate to each other. That lack of visibility often means that some pieces of knowledge being updated while others are left to go stale, leading to internal conflicts. This can especially impact new employees who donвЂ™t have the institutional knowledge needed to navigate knowledge conflicts.
Many company wiki tools offer integrations into team communications software like Slack or Microsoft Teams, but the extent of those integrations varies widely from tool to tool. Some may allow you to search for and preview a piece of knowledge, but force you to go to the portal to see the rest of the information. Others allow you to initially capture information from conversations, but require you to log into the portal again to edit or organize it. Look for wiki solutions that allow you to have full access from wherever you work.
In this article
You can add and edit wiki pages directly on GitHub or locally using the command line.
Wikis are available in public repositories with GitHub Free and GitHub Free for organizations, and in public and private repositories with GitHub Pro, GitHub Team, GitHub Enterprise Cloud and GitHub Enterprise Server. For more information, see “GitHub’s products.”
Adding wiki pages
- On GitHub.com, navigate to the main page of the repository.
- Under your repository name, click
Editing wiki pages
- On GitHub.com, navigate to the main page of the repository.
- Under your repository name, click
Adding or editing wiki pages locally
Wikis are part of Git repositories, so you can make changes locally and push them to your repository using a Git workflow.
Cloning wikis to your computer
Every wiki provides an easy way to clone its contents down to your computer. You can clone the repository to your computer with the provided URL:
Once you have cloned the wiki, you can add new files, edit existing ones, and commit your changes. You and your collaborators can create branches when working on wikis, but only changes pushed to the default branch will be made live and available to your readers.
About wiki filenames
The filename determines the title of your wiki page, and the file extension determines how your wiki content is rendered.
Wikis use our open-source Markup library to convert the markup, and it determines which converter to use by a file’s extension. For example, if you name a file foo.md or foo.markdown, wiki will use the Markdown converter, while a file named foo.textile will use the Textile converter.
Don’t use the following characters in your wiki page’s titles: \ / : * ? ” | . Users on certain operating systems won’t be able to work with filenames containing these characters. Be sure to write your content using a markup language that matches the extension, or your content won’t render properly.
Help us make these docs great!
All GitHub docs are open source. See something that’s wrong or unclear? Submit a pull request.
by Gina Trapani
A wiki is an editable web site, where any number of pages can be added and the text of those pages edited right inside your web browser. Wiki’s are perfect for a team of multiple people collaboratively editing information ( Wikipedia is the quintessential example of this) but a wiki can also be useful to an individual: as a personal, searchable, versioned, digital notebook.
Imagine storing and editing your to-do lists, bookmarks, snippets of text, project notes, reference material, images from the web or anything you wanted on your home computer from anywhere just using a web browser – no disks, thumb drives, text editors, or file transfers required. This is possible with a personal wiki.
If you’ve got a web hosting plan you can install any number of free wiki packages on your server. If not, it’s easy to install a personal wiki on your home computer to read and write to from any web browser. In this tutorial, we’ll set up a wiki on your home computer so you’ll always have access to a searchable, editable personal notebook.
Notes and disclaimers: Like the previous home server features, keep in mind that running a server and opening a port on your home computer is a risky undertaking. Make sure your PC has all the latest security updates and has been thoroughly scanned for viruses and spyware before we begin.
What you’ll need:
- A Windows PC 
- A zip utility program (the free 7-Zip will do fine)
- An always-on broadband Internet connection
We’re going to use a wiki package called Instiki , which is a perfect beginner’s wiki. Instiki is easy to install and easy to use, and it is written in a language called Ruby. 
Filtrete Smart Air Purifier
Covers 150 sq. ft.
Filter dust, allergens, pollen, pet dander, and viruses all day, every day with this smart purifier. The HEPA filter takes care of 99.97% of air particles to keep your oxygen as clean as possible.
Let’s get started.
Step 1. Install Ruby.
Download Ruby from here . Click on the latest stable release .exe file, which at time of writing is ruby182-15.exe. Run the installer, accept the license agreement and all the default settings, including installing ruby in the C:\ruby\ folder.
Step 2. Install Instiki.
Download Instiki from here , using the .zip package, and unzip using 7-Zip or any zip utility to a folder on your hard drive. Move and rename the folder to C:\instiki\.
Step 3. Run Instiki.
From the Start menu, choose Run, and type cmd to open a Windows command line. Type:
To change into the Instiki directory. Then type:
To start the Instiki server. This is what your output should look like:
Now, leave that window open and switch to your web browser, and go to http://localhost:2500/ to begin Instiki setup. Give your new wiki a name and a password. I’m calling mine “Gina’s Notebook:” (Click on the images for a larger view.)
After you click on the Setup button, you will be asked to enter text into your homepage. Here’s where things get fun. On the right you’ll see a quick guide to Instiki’s wiki syntax, that is, the ways you can bold and italicize your page text, add external links and reference new pages. Instiki uses ‘CamelCase’ to identify page names. So if you type MyToDoList, Instiki will automatically make that a reference to a new page, because it’s several words squashed together mixed case.
Here’s some text I’m putting onto my homepage using Instiki’s syntax:
When you save those changes, you’ll notice that the bold and italics formatting was applied to “need” and “write things down,” that the word Lifehacker was linked to http://lifehacker.com, and that MyToDoList has a question mark next to it, like this:
The question mark next to MyToDoList means that it’s a new page which hasn’t yet been created. Let’s create it by clicking on that question mark and filling in text for your new MyToDoList page in your notebook.
After that’s saved, it looks like this:
Now, if you go back to your home page, you’ll notice MyToDoList now links to your newly-created page, like so:
Woohoo! You’re a wiki master!
Step 4. Password your Instiki web.
If you’re going to be accessing your personal wiki from anywhere, that means anyone else will be able to edit it too – but we don’t want that. Set a password on your Instiki wiki to make it editable and readable by no one but you. Click on the “Edit Web” link inside Instiki. There, set a password for your web so only you and whoever has the password can edit it.
Step 5. Access your personal wiki from anywhere.
If your computer is not behind a router or firewall, you can now read and write to your personal wiki from any Internet-connected computer by typing your home computer’s IP address or domain name  plus :2500 into a web browser’s address bar, like
That extra 2500 addresses Instiki, which runs on port 2500, Ruby’s default port. This works well because if you followed my previous Lifehacker feature on setting up your home web server , you may have Apache web server listening on port 80. They’re different, unconflicting ports so both can run simultaneously, but to reach your Instiki wiki you must add the :2500 at the end of your computer’s address.
Geek to Live: How to set up a personal home web server
by Gina Trapani
If your computer is behind a home router with a firewall, see Lifehacker feature How to access your home server behind a firewall .
Geek to Live: How to access a home server behind a router/firewall
by Gina Trapani
Some more Instiki tips:
Get your Instiki wiki to start up whenever your computer’s on with a simple batch script. Save the following into a file named startwiki.bat:
Create a Windows shortcut to startwiki.bat and place it into your C:\Documents and Settings\All Users\Start Menu\Programs\Startup\ folder. This will run Instiki when your computer starts up automatically.
Export a read-only HTML version of your web using Instiki for backup or reference on another server.
Create pages liberally, say one for each project or set of bookmarks, and use Instiki’s search feature to find things you’ve written about before.
Use the “Print” view to take a hardcopy of any Instiki page with you on the go.
Most of all, have fun with your new wiki!
Gina Trapani is the editor of Lifehacker. Her special feature Geek to Live appears every Wednesday and Friday on Lifehacker.
 Mac users, you haven’t been left out in the cold. Setting up Instiki on a Mac is a lot less complicated. Use the Mac OS X binary link to download Instiki and omit step 1, installing Ruby. See? Told you it was easier for you. [back to top]
 For more advanced users comfortable with wiki syntax and with a server that supports PHP and MySQL, I’d highly recommend the more fully-featured and free MediaWiki which powers the venerable Wikipedia . [back to top]
 For more information about giving your wiki a memorable domain name, see previous Lifehacker feature Assign a domain name to your home server. [back to top]
Here you will find links to VirtualBox binaries and its source code.
By downloading, you agree to the terms and conditions of the respective license.
If you’re looking for the latest VirtualBox 6.0 packages, see VirtualBox 6.0 builds. Please also use version 6.0 if you need to run VMs with software virtualization, as this has been discontinued in 6.1. Version 6.0 will remain supported until July 2020.
If you’re looking for the latest VirtualBox 5.2 packages, see VirtualBox 5.2 builds. Please also use version 5.2 if you still need support for 32-bit hosts, as this has been discontinued in 6.0. Version 5.2 will remain supported until July 2020.
VirtualBox 6.1.32 platform packages
- Windows hosts
- OS X hosts
- Linux distributions
- Solaris hosts
- Solaris 11 IPS hosts
The binaries are released under the terms of the GPL version 2.
See the changelog for what has changed.
You might want to compare the checksums to verify the integrity of downloaded packages. The SHA256 checksums should be favored as the MD5 algorithm must be treated as insecure!
- SHA256 checksums, MD5 checksums
Note: After upgrading VirtualBox it is recommended to upgrade the guest additions as well.
VirtualBox 6.1.32 Oracle VM VirtualBox Extension Pack
- All supported platforms
Support for USB 2.0 and USB 3.0 devices, VirtualBox RDP, disk encryption, NVMe and PXE boot for Intel cards. See this chapter from the User Manual for an introduction to this Extension Pack. The Extension Pack binaries are released under the VirtualBox Personal Use and Evaluation License (PUEL). Please install the same version extension pack as your installed version of VirtualBox.
VirtualBox 6.1.32 Software Developer Kit (SDK)
The VirtualBox User Manual is included in the VirtualBox packages above. If, however, you would like to take a look at it without having to install the whole thing, you also access it here:
You may also like to take a look at our frequently asked questions list.
VirtualBox older builds
The binaries in this section for VirtualBox before version 4.0 are all released under the VirtualBox Personal Use and Evaluation License (PUEL). As of VirtualBox 4.0, the Extension Pack is released under the VirtualBox Personal Use and Evaluation License and the other packages are released under the terms of the GPL version 2. By downloading, you agree to the terms and conditions of the respective license.
The VirtualBox sources are available free of charge under the terms and conditions of the GNU General Public License, Version 2. By downloading from the below links, you agree to these terms and conditions.
- Browse the source code repository
This is the current development code, which is not necessarily stable.
- View the latest source code changes
- Download the VirtualBox OSE about logo in higher resolutions: 1024×768, 1600×1200.
- Checking out from our Subversion server. This is the current development code, which is not necessarily stable.
After getting the sources in one of the ways listed above, you should have a look at the build instructions.
Please also take a look at our licensing FAQ, in particular regarding the use of the name VirtualBox.
Pre-built VirtualBox VMs
There are some pre-built VMs designed for developers and the curious over on the Oracle Tech Network site.
Select the pages to export:
Learn about XWiki’s concept and why it’s an alternative to Confluence and MediaWiki
- a very robust WYSIWYG editor
- a powerful wiki syntax
- strong rights management
Why use XWiki?
Developed for more than 10 years, XWiki is being used by many high profile companies as:
- Knowledge base
- Collaborative intranet
- Public website
- Business applications
… or other use cases .
XWiki offers a generic platform for developing projects and collaborative applications using the wiki paradigm.
- PlatformXWiki Platform is the generic wiki platform offering runtime services for applications built on top of it.
- FlavorsXWiki Standard is a fully-featured flavor on top of XWiki. It’s also a second generation wiki offering the ability to install and develop small applications inside wiki pages.
- ExtensionsXWiki Extensions allows you to customise your wiki by providing a vast collection of applications that can be installed on top of the default distribution.
- All projects All XWiki software is developed in Java and under the LGPL open source license . Top Level Projects are actively developed by the XWiki Development Team. In order to see all our projects please visit the forge .
All XWiki software is developed in Java and under the LGPL open source license . In order to see all our projects please visit the forge .
Over 600 extensions : applications, macros, skins, plugins, themes, etc.
- Extension Manager
- AppWithin Minutes
- Color Themes
XWiki is a light and powerful development platform that allows you to customize the wiki to your specific needs. Using structured data and in-page-scripting you can create macros and applications that allow you to extend the capabilities of your wiki.
Latest Blog Posts
Highlights of XWiki 13.x cycle
January is here and this means we’ve just finished the XWiki 13.x cycle. It’s time to look back at what we achieved last year, in 2021. Here are some links to visual reports of what was done in 13.x:
XWiki 12.10.11 Released
The XWiki development team is proud to announce the availability of XWiki 12.10.11. This is the final bugfix release for 12.10. This release covers important issues, including 8 blockers, that we have discovered since XWiki 12.10.10 has been released. This release also includes 7 security fixes. .
XWiki 13.10.2 Released
The XWiki development team is proud to announce the availability of XWiki 13.10.2. This is a bugfix release that covers important issues that we have discovered since 13.10.1 has been released. It’s also the first version of the new 13.10.x LTS branch (replacing the 12.10.x branch). .
XWiki 13.10.1 Released
The XWiki development team is proud to announce the availability of XWiki 13.10.1. This is a bugfix release that covers important issues that we have discovered since 13.10 has been released. .
XWiki 13.10 Released
The XWiki development team is proud to announce the availability of XWiki 13.10. Annotations can now be made on HTML content, including AWM applications. Progress on the conversion from Live Table to Live Data continues. A security issue has also been fixed. .
XWiki 13.10 Release Candidate 1 Released
The XWiki development team is proud to announce the availability of XWiki 13.10 Release Candidate 1. Annotations can now be made on HTML content, including AWM applications. Progress on the conversion from Live Table to Live Data continues. A security issue has also been fixed. .
XWiki 13.9 Released
The XWiki development team is proud to announce the availability of XWiki 13.9. This release introduces an experimental realtime Wiki editor (superseding the existing Realtime Collaborative Plain WikiText Editor contributed extension) and an experimental WYSIWYG editor (superseding the existing Visual Realtime Collaborative Editor contributed extension). They are not bundled yet in XWiki Standard, but we plan to do this soon. For developers, there’s a new API available, called Netflux (superseding the existing Realtime Netflux Backend contributed extension), to write realtime-enabled extensions on top of XWiki. This version also contains security fixes. .
XWiki 13.9 Release Candidate 1 Released
The XWiki development team is proud to announce the availability of XWiki 13.9 Release Candidate 1. This release introduces an experimental realtime Wiki editor (superseding the existing Realtime Collaborative Plain WikiText Editor contributed extension) and an experimental WYSIWYG editor (superseding the existing Visual Realtime Collaborative Editor contributed extension). They are not bundled yet in XWiki Standard but we plan to do this soon. For developers there’s a new API available, called Netflux (superseding the existing Realtime Netflux Backend contributed extension), to write realtime-enabled extensions on top of XWiki. .
XWiki 12.10.10 Released
The XWiki development team is proud to announce the availability of XWiki 12.10.10. This is a bugfix release that covers important issues that we have discovered since XWiki 12.10.10 has been released. We strongly encourage users to upgrade to it. .
XWiki 13.8 Released
The XWiki development team is proud to announce the availability of XWiki 13.8. Mostly a developer’s release and some performance improvement for the new LiveData feature. .
Ditch your employee handbook, and consider giving your team a company wiki. A wiki is a website of sorts that allows for collaborative editing by a group of users, just as is true of Wikipedia. The collaborative nature can bring the team together, and save you time training new employees on company policies, new employee guides, document templates and anything else you require.
Wikis allow you to assign permissions to different team members who can edit pages or add new content. You organize different pages by categories and subcategories. The trademark feature of a wiki is the quick transition to related pages by way of hyperlinked keywords.
There are different approaches to building a wiki, and this guide will detail two of the most common routes for setting one up. The first is the easiest route, with user wikis hosted by third-party services and created with customizable interfaces. The second is an advanced method that requires some web coding knowledge.
If you don’t have much technical know-how, then starting a wiki on a wiki-hosting service is likely the best route. Wiki-hosting services host your wiki on their servers and provide the interface for customizing it. These services are sometimes free, with a paid-premium version to unlock all of their features. There are also a select few that run ads on your wiki page, but these are for public pages.
These are some of the more popular services.
Wikidot is an enterprise wiki-hosting service with features for crafting wikis and other professional websites. There is a free version for making public wikis and paid premium versions ($49.90 to $239.90) for hosting private wikis for your companies. It features unlimited pages for your site and storage space for hosting documents and other files that you can share across your company.
Tettra, a wiki-hosting and editing program, is an add-on for the chat program Slack. Team members connected through Slack can edit the wiki, add pages and share documents companywide. Tettra hosts all your content. This is a paid service with different pricing plans depending on the size of your team, starting at $50 per month for up to 20 users and going up to $500 per month for up to 300 users.
Self-hosting a wiki
An option that may prove cheaper than a wiki-hosting service, depending on your circumstances, is to build and host a wiki on your own server or online hosting service. This takes more technical and online coding knowledge but can still be easy and manageable.
First, you’ll need a place to host your wiki. You can use an onsite server that your company already owns, or you can rent online server space. There are some cloud services such as A2 Hosting, HostGator and Bluehost that are optimized for running wiki software. If you plan to make your wiki accessible to the public or available to your employees from anywhere with an internet connection, you’ll also need a web domain.
Otherwise, users will only be able to access the wiki from your local network or a VPN. Since wikis are typically a series of text web pages, they shouldn’t require much space, unless you also want to host bigger file types.
Next, you’ll need wiki software to create and customize your wiki. Some of the more popular programs include:
MediaWiki, an open source program and the same used by Wikipedia. Using it requires basic knowledge of PHP script and CSS code. Even if you’re not familiar with coding, MediaWiki’s website offers detailed instructions on how to install it on your server and customize your wiki. It’s free to download and use.
TikiWiki is a content management system (CMS) with a full suite of website programming features, but by default is a wiki platform with the essential tools to craft your company’s wiki page. This platform has lots of plug-ins available for extra features such embedded video, documents and maps. TikiWiki is open source and free to download.
Building your wiki
Many wiki hosting services, like Wikia and Wikidot, have their own interfaces for adding pages, info boxes and links. These features are usually self-explanatory and come with extensive instructions and support.
Editing your self-hosted wiki is more complicated and will take some web design skills, depending on your software. The common coding language for wiki software and web design software, in general, is CSS. This controls the look and layout of your wiki. Fortunately, you can find lots of premade CSS templates online. All you need to do is copy the code and paste it into the appropriate place in your software.
The other code you need to know is wiki markup, which controls the formatting of your wiki’s content. Instead of a familiar text formatting toolbar, to change the heading type, font, size and other aspects of your wiki, you’ll need to familiarize yourself with wiki markup language. Wiki markup is based on HTML.В
Creating a wiki is a great communication tool to keep employees up to speed on your company’s procedures and rules. It’s a destination to point employees to for basic instruction, which can be easily added to for further clarification.
Wiki-hosting services offer a short learning curve but are less flexible and can be costly to run. Self-hosting, on the other hand, is cheaper due to the amount of open source software, especially if you already have a server to store it on. You may need to learn some coding to proceed if you don’t already have someone on your team who’s knowledgeable in basic online programming.
Multi Monitor App | Virtual Display Screen | Software Video Wall
Multi Monitor Application for Windows
NETWORK DISPLAY MULTI MONITOR SOFTWARE
- Windows Desktop Extension (x10-sion)
- Windows Desktop Duplication (mirroring/cloning)
- KVM (keyboard and mouse remoting) supported by Windows VIEWER
Video Wall Software Engine
The spacedesk Video Wall Software Engine enables convenient and inexpensive setup of display walls using a single PC running on regular Windows 10. Our product supports multicast of Windows desktop screen to up to an unlimeted number of remote display devices.
MAWi Spacewall utilizes spacedesk to turn any Android or Windows device into a powerful AV-over-IP gear for digital signage and video wall setups in a simple, cost-effective way.
The screens can be (i) set as individual displays for standard digital signage purposes, (ii) grouped to clone the same content, (iii) set up on a grid as standard video walls or (iv) set up as Creative video walls where screens of any size and scale are placed at any angle.
Display Driver SDK (Software Development Kit) for Windows
The spacedesk SDK (Software Development Kit) for Windows 10 enables easy and convenient development of solutions for virtual and physical displays.
– Virtual WDDM IddCx Indirect Display Driver (UMDF)
– Virtual HID Keyboard and Touchscreen Driver (UMDF)
– Virtual Mouse Driver (KMDF)
– Image encoding software for Windows
– Network protocol software for Windows, iOS and Android
– Image decoding and rendering software for Windows, iOS and Android
Coronavirus (COVID-19) updates: Safety information for academic year 2021-22
Information and Communication Technologies
- Administration and support services
- Information and Communication Technologies
- Self service
- Connect and communicate
- Sharing and collaboration tools
A wiki is a web-based service, essentially a website, which can be used to share content and documents online in a way that enables and encourages collaboration across teams and individuals. Wikipedia is the most common example of a wiki.
As a member of staff or a student at Imperial College London, you can use your Imperial username and password to access the Confluence Wiki where you can share knowledge and collaborate with your team. You can request your own wiki space and invite others to work with you on a project or complete a repository of information on a particular subject.
If you already use a wiki, you can find helpful documentation in the General Help section.
Requesting wiki space
Wiki spaces can be created for both individuals and departments and are only accessible to Imperial account holders.
To create a new wiki for a department or project, fill out the Request a wiki form or contact the ICT Service Desk and provide:
- the proposed name for wiki space (it may need to be changed);
- a brief description of the intended use of the wiki;
- the name of the department with which the wiki will be associated.
As the person requesting the wiki space, we will give Space Administrator privileges to you, meaning that you are responsible for the content and permissions within the space. Space Administrators can add additional Space Administrators.
Please familiarise yourself with the Collaboration Policy.
If you’ve seen a lot of wikis, but not one for the topic you’d like, why not make your own?
Wikis are great sites dedicated to either a specific topic or collection of topics. Sometimes you may come across that your niche hobby or interest isn’t well-represented in the wiki community. Fortunately, you can remedy this by creating your own, and then let other users across the Web edit the wiki to help you out. Follow these steps to get started:
1. Open a Web browser to Wikia.com.
2. Near the top there will be a Create Wiki button, click on it.
Screenshot Nicole Cozma
3. Pick a name for your wiki, followed by a Web address. The Web address cannot contain any special characters.
Screenshot Nicole Cozma
4. Sign up for an account on Wikia if you don’t have one already. Alternatively, you can log in with Facebook if you don’t want to create a new account.
Screenshot Nicole Cozma
5. Enter a description for the type of wiki you are creating.
Screenshot Nicole Cozma
6. Pick a theme. Like most other details of your wiki, you can change this later if you’d like more time to decide.
Screenshot Nicole Cozma
7. Start editing your wiki!
Screenshot Nicole Cozma
Note: There are edit buttons next to the titles of each section on the main page (as seen above) and you can use the Wikia wiki tools to add new pages/sections to your wiki.
Unique and powerful suite of software to run your entire business, brought to you by a company with the long term vision to transform the way you work. Experience the Operating System for Business. –>
Complete CRM Platform
End-to-end, fully customizable CRM solution for growing businesses and enterprises.
Powerful Financial Platform
Complete accounting software with end-to-end VAT and E-Invoicing compliance for growing businesses and enterprises.
- CRM The complete CRM platform. Sign Up Now
- BackToWork Ensure employee safety at workplace. Sign Up Now
- Desk Omnichannel customer service solution. Sign Up Now
- Forms Simplify data collection. Sign Up Now
- Analytics Analyze your business data. Sign Up Now
- Books Powerful financial platform for growing businesses. Sign Up Now
- People Smart HR management software. Sign Up Now
- Survey Online surveys for every occasion. Sign Up Now
- Mail Secure business email. Sign Up Now
- Creator Build custom apps 10X faster. Sign Up Now
- Projects Plan and track projects. Sign Up Now
- Campaigns Reach and engage your customers. Sign Up Now
- Recruit Applicant tracking system. Sign Up Now
- Sign Sign and send documents. Sign Up Now
- Inventory Online inventory and order management. Sign Up Now
- Social The all-in-one social media management software. Sign Up Now
- Invoice 100% Free invoicing solution. Sign Up Now
- Expense Effortless expense reporting. Sign Up Now
- SalesIQ Convert website visitors into customers. Sign Up Now
- NewContracts Comprehensive contract management software. Sign Up Now
- NewDataPrep Advanced data preparation software. Sign Up Now
- NewCatalyst Build and deploy serverless apps. Sign Up Now
WORK REMOTELY WITH
Online workplace for teams
Workplace unifies your team’s communication, file storage and collaboration.
- Assist Remote support and unattended access solution. Sign Up Now
- Meeting Meeting & webinar solution. Sign Up Now
- Projects Plan and track projects. Sign Up Now
- Sprints Planning and tracking tool for agile teams. Sign Up Now
- Cliq Chat that’s built for work. Sign Up Now
- WorkDrive Online file management for teams. Sign Up Now
- ShowTime Virtual training solution. Sign Up Now
Run your entire business with 45+ integrated applications. With Zoho One, you can manage, connect, and automate business processes across your organization. Experience the Operating System for Business.
Unified customer experience platform.
Unified finance platform for business.
Platform for digital transformation and automation.
All the tools for work in one integrated suite.
Unified HR platform.
We help you align IT to business.
Unified marketing platform.
All Zoho Apps
Sales & Marketing
Give your sales team the perfect set of apps to help close more business deals in less time.
Give your service team the right tools and context necessary to make every customer successful.
Email & Collaboration
Empower your workforce with apps to collaborate and transform the way they work.
- В Mail
- В Meeting
- В Cliq
- В Voice
- В WorkDrive
- В Docs
- В Writer
- В Sheet
- В Show
- В Projects
- В Sprints
- В BugTracker
- В Connect
- В Vault
- В ShowTime
- В NoteBook
- В TeamInbox
- В ZeptoMail
- В Learn
- В Calendar
Focus on your people while our apps automate your human resources processes.
IT & Help Desk
Be right where your customers are with apps to help your business engage with them.
Simplify complex business processes with apps that will make your team’s work easier.
Solve business accounting challenges using our perfect set of finance apps on the cloud.
Empower your business with deep insights, using our modern self-service business intelligence & analytics platform.
Streamline your contract lifecycle and improve efficiency across all aspects of contract management.
Privacy and Zoho
We donвЂ™t own your data, you do.
Trusted by more than 50 million users globally
“Rablab integrated their business operations and increased productivity with Zoho.”
Nicolas Rabouille, Co-founder & Project management
Relief initiatives and remote working resources to help you weather the storm.
Partner with Zoho
Zoho partners with top notch VARs, MSPs, SIs, consultants and technology partners.
Build and sell extensions for Zoho products.
Install extensions that add new features to Zoho products.
Open source home automation that puts local control and privacy first. Powered by a worldwide community of tinkerers and DIY enthusiasts. Perfect to run on a Raspberry Pi or a local server.
Home Assistant integrates with over a thousand different devices and services.
Once started, Home Assistant will automatically scan your network for known devices and allow you to easily set them up.
Once you have integrated all your devices at home, you can unleash Home Assistant’s advanced automation engine to make your home work for you.
- Turn on the light when the sun sets or when coming home
- Alert you when you leave your garage door open.
Home Assistant is not just limited to Home Assistant. Easily install other applications that will help you manage your home.
- Run AdGuard, a DNS-based ad blocker
- Run third party automation engines like NodeRed
- Turn Home Assistant into a Spotify Connect target
Home Assistant keeps your data local, no need for a cloud.
Home Assistant communicates with your devices locally, and will fallback to pulling in data from the cloud if there is no other option. No data is stored in the cloud, and everything is processed locally.
Use the official Home Assistant apps, a convenient companion to quickly control your devices and be notified when things happen in your home, even on your wrist using the Apple Watch.
The apps can also be used to send your location home to use presence detection as part of your automations. Data is sent directly to your home, no access by third-parties.
Home Assistant allows you to get on top of your energy use with its home energy management feature. Gain new insights, optimize your solar panel production, plan energy usage and save money.
Wikis are handy for collecting and sharing information, so it’s no surprise that the internet is full of them. There’s a good chance that you use wikis, or at least regularly stumble across them in search results. This may have prompted you to wonder if you can create a wiki on WordPress and of your own.
While WordPress wasn’t designed with wikis in mind, WordPress’ power and flexibility makes adapting it to the format a simple process. With the right tools and a little effort, you can build a wiki for your business or community, then tweak it until it’s perfect.
The benefits of creating a wiki
Most wikis focus on a specific topic, such as mathematics.
A wiki is a website designed for collecting and sharing information. It’s also a collaborative platform, where multiple authors can make changes to a site. The most obvious example is Wikipedia, but there are thousands of other wikis serving a wide variety of purposes.
Like Wikipedia, a wiki can be a general repository of knowledge. More often, however, they house information about a specific topic or niche. For example, fan communities frequently create wikis as databases about a particular work of fiction or franchise. Wikis can also serve an internal function, such as when a company creates one for its employees.
In short, a wiki is a flexible type of site that can be beneficial in many ways. Like a knowledge base, wikis present an excellent way to centralize information, crowdsource knowledge, and enable people to easily collaborate. Plus, wikis are perfect for creating a sense of community and engagement.
The essential elements of a wiki website
Wikis tend to have a particular type of structure and contain some specific elements. If you’re thinking about building your own wiki, you’ll want to strongly consider incorporating these features:
- A strong organizational structure, with a hierarchy that includes topics and sub-topics.
- Clear navigation, largely provided through internal links in articles.
- Editing features that users can access to make their own changes.
- Tools and spaces for people to communicate and collaborate.
- A user authentication or login system.
This may seem like a lot. However, there are tools that make it easy to create a wiki with these elements. Let’s discuss how to get started.
How to create a wiki using WordPress (in 3 steps)
The first thing you’ll want to do is create a WordPress site to house your wiki. You can adapt an existing site, but we recommend starting with a blank slate so you can set up a strong structure.
Of course, this means you’ll need to set up your new WordPress site on a hosting service, so your wiki will be publicly accessible. There are plenty of excellent web hosts to pick from, and the choice is up to you. After you’ve signed up for a hosting plan and have your website installed, you’ll be ready to get to work!
Step 1: Choose a wiki plugin or theme
By default, WordPress isn’t set up to work well as a wiki. However, you can fix that problem quickly using either a wiki theme or plugin. Either one can get your site set up with the proper structure and tools to create a wiki, but it’s important to keep in mind that themes and plugins come with their own pros and cons.
A plugin is a less intrusive option that works particularly well if you want your wiki to only be a part of your website or if you’re trying to adapt an existing site. Plus, it enables you to use any theme.
On the other hand, a dedicated wiki theme is the easiest way to structure your whole site as a wiki and to make sure it has the right look.
Either way, there are lots of options for wiki themes and wiki plugins. Three good tools to get you started are:
- MyWiki – a free, but basic wiki theme.
- BuddyPress Docs – a free plugin that helps add wiki functionality to the BuddyPress plugin (a free plugin which helps you create a social network. By using BuddyPress, you’re able to give each wiki author a unique profile and enable collaboration).
- Yada Wiki – a basic free wiki plugin.
Current Version: 3.4.1
Last Updated: June 25, 2021
Step 2: Set up a clear organizational structure
Most wikis house a lot of content. Therefore, you’ll need to put a clear organizational structure in place from the beginning. If you let users try to organize content as they upload it, you’re likely to end up with a confusing mess.
Instead, we suggest setting up a system of categories and subcategories when building your wiki:
WordPress’ built-in category system makes this quite easy. Plus, your chosen wiki plugin or theme may come with more customization options. If it doesn’t, you can always install an additional tool such as Real Categories Management.
The important thing is to come up with a list of topics for displaying content, preferably in collaboration with others using the wiki. Try to stick with a small number of high-level topics that can be featured in the main navigation section, supplemented with more specific sub-topics. You’ll probably still need to add new categories over time, but this method simplifies organization.
Step 3: Create and post rules for your community
Finally, it’s a good idea to consider how other people will use your wiki. If there will only be a few approved users, you have less to be concerned about. However, most wikis are open to the general public. This means you have to worry about people making poor-quality or even malicious changes, as well as inconsistency in the way content is created and edited.
To minimize these risks, you’ll want to create a system of rules and guidelines for your wiki’s community. Lay out in clear terms what style you’re looking for, what type of content is and is not acceptable, and what process (if any) needs to be followed when making changes. You’ll also want to consider what kinds of behavior and language are prohibited:
For inspiration, check out Wikipedia’s policies and guidelines and its rules for editors. Once you have clear rules laid out, you’ll need to include them in a prominent place on your wiki itself. Then, you can invite people to start adding content!
One of the best things about the internet is how it enables collaboration and the sharing of knowledge. Wikis have emerged as a simple but effective tool for doing both of these things. By creating a wiki for your business or community, you can centralize information and promote engagement at the same time.
While WordPress isn’t a dedicated wiki platform, it works remarkably well if you want to create a wiki. These three steps will get you started:
- Choose a wiki plugin or theme.
- Set up a clear organizational structure.
- Create and post rules for your community.
Everyone knows Wikipedia, the universal multi-language human-friendly encyclopedia that edited by its users. Wikipedia is built on an open-source top of MediaWiki by a dedicated team of developers.
MediaWiki becomes the first popular Wiki engine, which opened the way to dozens of Wiki engines for multipurpose and specific use.
Companies and teams can use self-hosted Wiki as a collaborative, organized writing platform to document instructions, team activities, software documentation and more.
Here, in this article we collected the best popular open-source, free Libre self-hosted Wiki engines software, as a guide for anyone who wants to create their wiki on their private servers.
Open-source Wiki engines
Wiki.js is our first pick here because it is an enterprise-grade Wiki engine with dozens of features and options. It exceeds other engines in performance, features, and customizations.
In Medevel.com, We are using it to organize our projects documents and keep track of our learning activities.
Wiki.js is a modular system with a large set of modules and extensions. As its community grows, expect more add-ons to be added there.
The other thing that we like about Wiki.js is that we run it locally on our devices: Linux, macOS and Windows.
2- BookStack App
The BookStack App is not just a Wiki Engine, but it works the same. It aims for creating books by easing collaboration among writers and editors, we run it for us and some clients as a Wiki Engine, where they use books as projects.
The application is easy to use for all sort of users with different backgrounds. It allows managing several books, categories, unlimited pages and comes with a powerful history and revision system for editors.
TWiki is not just another Wiki engine, it is also a consummate web application development platform. It comes with all set of wiki features alongside a long list of development tools to build a complex web apps.
TWiki has a library of plugins which extend its functionalities and features.
XWiki is an open-source wiki engine for enterprise. It focuses on productivity, collaboration, and simplicity.
The developers offer a powerful fancy control dashboard with responsive options which works seamlessly on mobile and tablets. It has its set of apps and modules and a developer-friendly API.
XWiki export options can export the content to numerous extensions like PDF, ODT, RTF, XML and HTML.
It supports all soft of file attachments, and offers a full control over the page lifecycle.
XWiki has the traditional Wiki syntax editor and WYSIWYG editor for non-experienced users.
DokuWiki is a popular PHP-based open-source wiki that has been standing for years. It offers a multilingual support as it packed by a large community of experienced users and developer from all over the world.
When it comes to configuration and customization, DokuWiki has a large set of themes, modules, plugins and configuration options, which makes it the right choice for tech-savvy teams.
6- TikiWiki CMS
It may look as a Wiki, but it’s not just another Wiki engine, It is a complete groupware and CMS for teams and enterprise as well as a web app development platform.
TikiWiki features include: editors, forums, form wizard control, custom fields and custom data structure management options, calendar and events management, galleries, survey, quizzes, polls, blogs and more.
PmWiki is a lightweight open-source wiki built with PHP. It offers a spam protection, page editing, revisions, RSS feeds, search tools, page group management and dozens of themes and plugins.
This wiki is pretty straightforward that does not require a steep learning curve. Some may prefer it as a personal wiki engine.
TiddlyWiki has been my favorite wiki on this list, It is an open-source portal one-file wiki that does not even require install. Despite its simple use and look, it has a rich list of features, plugins, and themes.
TiddlyWiki can be customized and modified according as required; however, some customization requires the user to dive deep in documentation and has a good coding experience.
Outline is a fairly new Wiki engine for teams which built on top of Node.JS, React and PostgreSQL.
It has a simple user-interface and rich features list with a dozen of customization options. It offers a docker install which can works seamlessly on Windows, Linux, and macOS.
Keep in mind that the project is under heavy development, which suggest more features in the near future.
Gollum is a GitHub-based Wiki engine for developers to organize software documentation. It uses GitHub repository for markdown files and Gollum engine to control and organize the content.
It features: RSS feed, UML diagram support, BibTeX and citation support, macros and more.
MediaWiki is an open-source Wiki engine that runs Wikipedia. It is the oldest system in the list and some may consider it the king of Wiki engines. It supports almost all available languages as it is easy to install and use.
It is available to download for free for users to host it at their server and start creating, editing and organizing their pages and media content.
MediaWiki has a tremendous list of customization options tips, extensions themes.
In the end
Here, as we listed all popular open-source Wiki engines, It is up to you choosing the one that fits you and your team requirements. We encourage you to narrow it down to three or two, then go throw all features and compare to select the right one.
If you have any other open-source Wiki engine system that we miss, please add it in the comments below.
Outline: An Open-source modern Wiki engine for teams and communities
The Outline app is a free self-hosted wiki engine and collaborative knowledge base for teams. Wiki engines are built to ease collaborative content creation for teams, organizations, and communities. However, many current open-source wiki e. Read more.
Projectify: A TiddlyWiki powered Personal Project manager
TiddlyWiki is a lightweight, portable multipurpose note-taking app. Created by Jeremy Ruston and powered by a strong community, TiddlyWiki became productivity tool for many. Because it is highly customizable and portable, you can use it fo. Read more.
TiddlyWiki : Open source one file wiki that runs everywhere.
I have been using TiddlyWiki for some time now, It’s very useful, productive and most importantly provide me with many options at once with ease of use : taking notes, summarizing my studies, task manager, project management, and writing. W. Read more.
Wikipedia is by far the most popular wiki in the world, currently featuring over 45 million pages in 301 languages. Nearly 500 visitors visit Wikipedia each month, and most of them have no idea that it’s possible to create a website just like Wikipedia for free and without any previous web development experience.
How? With wiki software products. We’ve picked top 5 best self-hosted wiki software products currently available, including the one that powers Wikipedia itself.
Created in 2002 by senior staff scientist at the Wellcome Trust Sanger Institute in Cambridge Heinrich Magnus Manske and later improved by American computer programmer Lee Daniel Crocker, MediaWiki is a free and open source wiki software platform that powers many popular wikis, including Wikipedia, Wiktionary, and Wikimedia Commons.
MediaWiki is written in PHP well-suited for the LAMP stack. Because MediaWiki has been deployed so extensively for so many years, it’s one of the most powerful wiki software platforms out there, offering a long list of features and broad content organization options.
MediaWiki can be used with any world wide language, and it can be further customized using templates and extensions. If there is one major limitation of MediaWiki, it’s the fact that its syntax hasn’t been formally defined, which makes it difficult for third-party developers to create WYSIWYG (What You See is What You Get) editors.
Whereas MediaWiki is being developed with the needs of Wikipedia and other large wikis in mind, TiddlyWiki is best-suited for smaller projects. It structures information in a unique way, using a hypertext card index system that uses Tiddlers as the fundamental units of information in TiddlyWiki.
You can think of Tiddlers as small snippets of information. They work best when they are as small as possible, and they can contain anything from text to images to audio to automatically generated lists. Tiddlers can be reused more than once, making TiddlyWiki perfect for capturing, organizing, and sharing all kinds of information.
DokuWiki is often described as a simpler alternative to MediaWiki. Although it’s available “only” in 50 languages and doesn’t offer nearly as many features as MediaWiki, users love it because of its clean syntax and remarkable ease of maintenance.
Over the years, DokuWiki has proven especially useful in the enterprise setting. Thousands of businesses and organizations use DokuWiki as a corporate knowledge base, project workspace, intranet, and more. DokuWiki doesn’t require too many resources, it’s fully open source, and is compatible with a wide variety of plugins and templates.
Plugins can be installed automatically via the extension manager or manually by copying them to lib/plugins/. For example, there’s a plugin that allows you to mas revert recent edits, one that restricts login access to designated IP addresses, or one that adds a comments section to wiki pages, just to name a few.
XWiki is a free and open source wiki software platform written in Java. It can be used either as a first-generation wiki or a second-generation wiki. According to XWiki, first-generation wikis are used to collaborate on content, while second-generation wikis can be used to create collaborative web applications.
Some examples of what can be created using second-generation wikis such as XWiki include blogs to communicate information or organize it using categories and tags, forums where participants can discuss important topics, task management platforms where users can create and assign tasks for designated projects, and more.
XWiki features a very robust WYSIWYG editor on top of powerful wiki syntax. It can be further extended with over 600 plugins, macros, skins, and themes provided by the XWiki community and core developers. If you’re looking for a powerful multiplatform wiki that emphasizes extensibility, XWiki is a great choice.
All wiki software platforms we’ve mentioned so far have been around for quite some time, and it sometimes shows. Wiki.js is different because it was first released in 2016 as a modern alternative to traditional wiki software platforms. It’s built on Node.js, Git, and Markdown, comes with a powerful visual editor, and is optimized to be low on system resources.
Wiki.js runs on any Linux, Windows, or macOS server, and it has an advanced caching functionality to speed up site access. Just like other wiki software platforms.
How to Install and Configure MediaWiki
To install MediaWiki, you’ll need three things:
- A web server to serve the requested pages to the client browser.
- Apache or IIS.
- PHP to run the software.
- PHP version 7.0.0 or later with Perl Compatible Regular Expressions, Standard PHP Library, JSON support.
- A database to store the pages and site data.
- MySQL 5.5.8+, MariaDB, PostgreSQL 8.3+, or SQLite.
If you meet all the requirements, you can download the latest version of MediaWiki from the official website and extract the archive to a web-accessible folder on your server.
Then, point your web browser of choice to the directory with MediaWiki files. Like this: http://yourwebserver.com/directory/mw-config/index.php.
Finally, follow the provided instructions to finish the setup process. For system-specific installation instructions, visit this page and scroll to the very bottom.
It doesn’t matter whether you’re a cybersecurity expert, a passionate cook, or a master underwater basket weaver—you too can share your knowledge using one of the wiki software platforms described in this article and perhaps even create a thriving community of people who share the same interests as you.
About the author
David Morelo is a professional content writer in the technology niche, covering everything from consumer products to emerging technologies and their cross-industry application
Media Wikiを使用するには、apache Webサーバー、MySQLデータベース、およびPHP 5が必要です。それらを1つずつ設定するオプションがありますが、EasyPHPはマウスを数回クリックするだけですべてのインストールに注意します。
インストールプロセスの最後に、EasyPHPがシステムトレイに表示されます。 システムトレイのショートカットを使用すると、Webサーバーの管理部分にアクセスできます。 最初に確認したいのは、「管理」ページです。 このページでは、Webサーバーで実行されている内容の概要を説明します。 このページが表示されている場合、これは動作中のWebサーバーがあり、MediaWikiをインストールする準備ができていることを意味します。
EasyPHPは「www」ディレクトリを作成し、このフォルダの下にその分布を抽出するとMedia Wikiをピックアップします。 Windowsユーザーの場合は、tarファイルであるMediaWikis配布ファイル形式に精通していない可能性があります。心配しないで、単にインストールしてください7zip、「Www」フォルダの下でMediaWikiを抽出するために使用します。 Youveが完了すると、EasyPHPは管理ページにこのフォルダを表示します。
インストールプロセスの最後に、ウィザードはLocalSettings.phpというファイルを生成します。 このファイルには設定の山があり、MediaWikiはマニュアルこれらの設定の意味を教えてくれます。 このファイルを先に抽出したMediaWikiフォルダ内に入れます。
このページには、「ログイン/アカウントの作成」リンク、「編集」タブ、「特別なページ」リンクの3つの重要なリンクがあります。 箱から出して、Wikiにアカウントを持っていない人でも、誰でもWikiを編集できます。 Wikiを保護する場合は、次のコマンドをLocalSettings.phpファイルに追加します。
ページの編集を開始する場合は、 [編集] タブに移動します。 You必要があるかもしれWikiマークアップを学ぶコンテンツを編集します。 最初は厄介かもしれませんが、十分な練習をすれば、これらのマークアップは多くの時間を節約できることがわかります。
右上隅には、新しいアカウントを作成するためのリンクがあります。 そのリンクをクリックしてユーザーアカウントを作成し、そのアカウントを適切なユーザーグループに割り当てます。 ユーザーグループについて詳しく知りたい場合は、 [スペシャルページ] リンクをクリックします。 特別なページでは、Wikiのあらゆる種類の管理ツールにアクセスできます。 壊れたページをチェックしたり、ユーザーを追加または削除したりすることができますが、今日のチュートリアルでは、「ログイン/サインアップ」ページ、設定ページ、ユーザー権利管理ページの3つのセクションを調べます。
「ログイン/アカウント作成」ページを使用すると、ユーザーを作成し、所有している任意のユーザーグループに割り当てることができます。 あなたがたくさんのユーザーを持っているならば、それらを一つずつ加えることは最も効率的な方法ではないかもしれません。 問題ありません。ユーザーのインポート拡張機能CSVファイルを使用して複数のユーザーを作成します。 拡張機能を拡張機能フォルダーにダウンロードし、このコマンドをLocalSettings.phpに配置します。
$ WgGroupPermissions [‘Trusted’] [‘sendemail’] = false;
EasyPHPシステムトレイのショートカットからPHP.iniファイルを開くことができます。 Upload_max_file_sizeは、Wikiにアップロードできる画像のサイズを決定し、PHPはファイルを2 MBに制限します。 より大きなファイルをアップロードする必要がある場合は、この変数に20 M (20メガバイト) などの大きな値を付けます。
Media Wikiはあらゆる種類のファイルタイプ、PDF、Microsoft office、Open Officeをサポートしていますが、このPHPコードをLocalSettings.phpファイルに追加する必要があります。
好みのページに移動すると、Wikiのスキンギャラリーが見つかります。 これらの選択に満足できない場合は、からすぐに使用できるスキンを作成するか、さらに良い方法でインストールできます。MediaWikiのギャラリー。 好きなものをダウンロードして、スキンフォルダの下に置きます。
Science fiction. Fantasy. The universe. And related subjects.
How to Create a Wiki to Support Your Fantasy Worldbuilding
As a fantasy writer, I am often asked how I keep all the worldbuilding details straight. I have a lot after all: multiple constructed languages, maps, races, countries, social customs… the list goes on.
So how do I keep track of it all?
That’s why I have a wiki.
I had no idea this wasn’t a normal practice for most writers until I began speaking to my peers and discovered that why no, many of them do not keep all their worldbuilding details in an easily accessible, location agnostic depository. In fact, organizing information seems to be such a daunting prospect for so many writers that they shy from the epic second world fantasies or science fiction stories which would require it. And if they DO put their notes somewhere in the cloud, it’s in the form of Google Drive pages which they then must sort through in order to find the pertinent information.
No, my friends. There is a better way. Let me help you to find the path.
Click to enlarge.
So most people are familiar with wikis through that big ol’ grandfather, Wikipedia, and probably give no thought at all to the idea wikis do not have to be crowdsourced or publicly available. They are efficient ways to organize information, which you want if you’re going to find that information quickly enough to do anything with it.
There are two main wiki types. Publicly hosted wiki and privately hosted wiki. What’s the difference?
Buy it Now
Publicly hosted wikis are wikis you create on someone else’s server space, using software some else controls. It’s a bit like having a social media account, except you don’t have to give anyone else access. Why would you want to do it this way? Well, ease, for one thing. Free accounts on a variety of platforms are available on the internet, and you don’t have to do a thing except sign up for an account and enter your worldbuilding information. Set your account to private (and make sure you’re using a wiki site where this is an option) and you’re the only one who’ll ever know how many times you’ve changed your villain’s origin story. Except now you’ll also be able to access that information anywhere you can check your twitter feed.
The downside (you knew there was a catch, right?) is you don’t really control the information you place up on that shared space. Sites who provide free options may also demand you keep your account active, which means if you move on to another project or are juggling multiple projects you may have to remember to keep logging in or the wiki might not be there when you return. Also, since nothing is ever really free, be prepared to share your wiki information with some ad space or find limitations placed on how much information you can store or who else can access it.
The other option is a private wiki. That’s when you put a wiki on server space you control (either because it’s your equipment or because you’re renting space on someone else’s) using software you control and have uploaded yourself (either purchased or freely available). The plus side is you control everything. That’s also the downside. As long as you have server space, the data is yours, which means if you’re already paying for a web site, it’s quite possible there won’t be any additional monetary output required. That’s how I did it, and I now have separate wikis for every universe I’ve created.
Click to enlarge.
In my case, I started out on a publicly hosted site, outgrew it/became dissatisfied with it, and then turned to a private wiki. After looking around at my options, I settled on DokuWiki (as I didn’t want to deal with MySQL) and I’ve been happy with it. Is it perfect? Oh no. But it gets the job done with a minimum of fuss. There’s a wealth of add-ons available to customize my wiki needs. No one can look at my notes I don’t want to (assuming they even know to try). It has a learning curve (as to be expected) but the tutorials are easy find.
Once I’ve developed the main themes I want to explore, I’ll create a wiki for the project and start creating entries, organized with such cleverly named folders as ‘characters’ and ‘atlas.’ I try to put as much information on the wiki as I can, which often includes details which may not ever make it on to the page. This is a pre-production stage in my writing where I’m creating communities, cultures, and characters for the sheer damn joy of it. As I do this, I start to see places where conflict is inevitable, where group A will rub group B the wrong way, where historical events in the past have dramatic consequences in the story’s present. This all leads to a thing I like to call “plot.”
Then, like any good design doc, I allow for the idea some or none of this will survive contact with my real enemy: the actual writing process. Because hey, that’s an act of discovery. Inevitably ideas expand, shift, are discarded or violently rebel. I always start with a detailed plot, but some of that plot won’t make it to the finish line. So after I finish writing, there’s a period where I need to go back through the wiki and update the information so I have it for next time. I used to slack off on this part, but now that I have more people than just myself interested in this information, I’m trying to be more diligent.
Click to enlarge.
What will work best for you? That’s going to be for you to decide. Like the writing process itself, it will likely require some experimentation. Ideally, you’re looking for ease of use and accessibility (you should be able to reach the wiki from anyplace where you would find yourself writing). A wiki that you find frustrating or which you can only use under special circumstances is a wiki that you will quickly stop using, defeating the whole purpose.
Now go forth and document your amazing worlds.
Do you have questions about building your own story wiki ? Leave then in the comments, and Jenn will respond in a post next week!
Jenn Lyons lives in Atlanta, Georgia with her husband, three cats, and a nearly infinite number of opinions on anything from mythology to the correct way to make a martini. Her debut epic fantasy novel, The Ruin of Kings publishes with Tor Books on February 5th.
In this article we will see what is a wiki software, its uses and applications, the best wiki software with premium, free and opensource wiki options.
What is a Wiki Software?
A ‘wiki software’ is a software which is used to create a collaborative environment known as a “Wiki”.
With the help of wiki software, people can collaboratively create, edit, and share content on the Wiki.
The wiki software is installed on a web server and usually runs as a web application, and the contents of the wiki are typically stored in a database.
Wiki software is also known as Wiki engine, and many of them are free and open-source wiki software which requires a wiki hosting. Usually, companies use these wiki software on their company intranets to create a private wiki network for themselves. There are also hosted wiki solutions where the company gives the wiki software and wiki hosting.
Note: Sometimes a Wiki is misspelled as ‘Wikki’, example people search the web for a “Personal Wikki’.
If you are interested in creating an internal wiki website, you should read our guide to creating an internal wiki website using WordPress.
Uses of Wiki Software
You could use a wiki software on a public-facing wiki, private network wiki or a personal wiki. Wiki software can be used in different ways based on use cases. They are,
- As an internal wiki software for your team collaboration
- As an enterprise / corporate wiki software for storing and sharing your company’s knowledge
- A classroom wiki software for teachers to share materials with students
- As a simple personal wiki software for taking notes
Best Wiki Software
So many wiki tools are available. Discussions on social forums like Reddit and Quora are never-ending. We have read many of them and found some of the best options. Some are free and open-source wiki software, and some are premium wikis.
Premium Wiki Software
As the name suggests, you have to pay to get these wiki software. They simply self-hosted software (you need to hosting separately) or You can get hosted wiki software as a service (SAAS). The best about getting a premium tool is that you get dedicated support and it’s much better than merely relying on community support.
Note: If you’re not interested in paying for a wiki software you can skip down this part to the free and open-source wiki software list.
Pygame requires Python; if you don’t already have it, you can download it from python.org. It’s recommended to run the latest python version, because it’s usually faster and has better features than the older ones. Bear in mind that pygame has dropped support for python 2.
The best way to install pygame is with the pip tool (which is what python uses to install packages). Note, this comes with python in recent versions. We use the –user flag to tell it to install into the home directory, rather than globally.
To see if it works, run one of the included examples:
Next steps. ¶
- Having a go at one of the tutorials.
- Or dive right into the pygame Docs
Further info on installation¶
Hopefully the installation instructions above worked for you. If not, please read some alternative installation methods, and extra details below.
Wheels are available for x86 and x64 architectures on Linux and Windows, and for x64 and arm64 on Mac. If pip doesn’t find a wheel for your platform, it will try to compile pygame from source (see below).
pygame requires a “newer” pip. If pygame starts compiling from source and fails, first try upgrading pip.
This comes with pygame already installed on the default raspbian installation.
Make sure you install python with the “Add python to PATH” option selected. This means that python, and pip will work for you from the command line.
There is documentation with python for the “windows installation steps”
Recent versions of Mac OS X require pygame 2¶
If your examples aren’t running and you are using a recent version of Mac OS X; try this line to install pygame instead:
(note the w on the end). If it doesn’t work for you, please see the /wiki/MacCompile instructions.
Unix Binary Packages¶
Many Linux and BSD distributions have their own packages of Pygame. These may have an older version of Pygame than the wheels, but have been carefully tested with other packages in that distribution.
|Distribution||Python 3 package||Debian/Ubuntu||python3-pygame||Fedora||python3-pygame|
FreeBSD also has an active pygame package. While techinicaly it isn’t binary, it is automatically built and installed by the ports manager. See the FreeBSD package page for more information. http://www.freebsdports.info/ports/devel/py-game.html
Gentoo has a builtin package for pygame. This is compiled for your system as it installs, similar to BSD, http://packages.gentoo.org/package/dev-python/pygame
Installing From Source¶
Compiling and installing pygame is handled by Python’s distutils. Pygame also comes with some scripts to automatically configure the flags needed to build pygame. Use the “setup.py” script to start the installation.
The first time you run the setup script, it will call the “config.py” script. This will build a “Setup” file which stores all the information needed to compile. The “config.py” will do a good job of detecting what dependencies are available and where they are located. If it isn’t perfect, it is easy to build your own, or edit the created “Setup” text file. This “Setup” file is a simple Makefile-like text file. It defines variables needed to use each dependency, and then enables all the pygame modules with found dependencies. If you have trouble compiling, you should be able to easily fix any problems inside the “Setup” file.
Running the “setup.py” script will call distutils to build and install the pygame package. Distutils actually supports a wide variety of compile and install options. running “python setup.py help” will start to show you the different options available. You can change many things like install locations, compiler to use, and more. Calling the “setup.py” script with no arguments and it will just ask you if you want the default flags needed to compile and install.
Some of the .c files are generated by Cython from .pyx files. Running “setup.py cython” will update them.
Windows Compiling Info
You can compile pygame on windows with mingw (gcc for windows) and also with visual studio. Up to date details can be found here: CompileWindows
Unix Compiling Info
Compiling from linux shouldn’t give you any problems. One thing you must keep in mind is that most linux RPM packages separate the actual library from the “dev” files needed to compile. To build you will need to make sure the packages like “SDL-dev” are installed.
You can check to see if SDL is ready to be built from by running the command sdl-config and seeing if it is found. If the sdl-config script is not on the path (or you have more than one?) Set the environment variable SDL_CONFIG to its location.
Sometimes you will have the SDL libraries installed in once location, and the other SDL libraries in another. This tricks the pygame config scripts, but you can help it out by setting the environment LOCALBASE to a path prefix where the other libraries are. The common case for this is SDL installed in /usr and other SDL libs installed in /usr/local. The command for this situation is “LOCALBASE=/usr/local python setup.py install“.
Mac OS X Compiling Info¶
Up to date instructions for compiling on Mac OS X can be found here: MacCompile
- Wiki settings
- Using Wiki
- Wiki FAQ
This page explains how students and teachers can use the Wiki activity and explores ways to make the most of it in your Moodle course.
- 1 Creating the first page
- 2 Adding more pages
- 3 Navigating page to page
- 4 Wiki editing in general
- 5 Deleting pages
- 6 Why use a wiki?
- 7 Ideas for using wikis
- 7.1 Group lecture notes
- 7.2 Group Project management
- 7.3 Brainstorming
- 7.4 Contribute to other wikis
- 7.5 Collaborative story-telling
- 8 See also
Creating the first page
- Once the wiki is set up, a user will click the link and reach the following screen:
Adding more pages
- Type the name of your page inside double brackets. (top image in screenshot below) You can preview it by clicking the “preview” button towards the bottom of the screen.
- Press the “save” button.
- Now click the link in italics for one of the pages (bottom image in screenshot below) and you will be prompted to create it in the same way you create the first page:
- A page once created no longer has italics.
Navigating page to page
To navigate pages, you have to create your own hyperlinks. Fortunately it is easy. Copy the URL at the top of one page into a hyperlink on another page. Save your work and now when that hyperlink is activated, the Wiki goes to that page.
For example, if you have a table of contents, each entry can have a link to a respective page. From the other pages, you can have a return hyperlink back to the Table of Contents. Copy/paste the return hyperlink onto other pages and save time.
Note: Non-Boost themes have a New option from the navigation block for creating new pages, but you will still need to copy and paste the name of the new page onto the immediate parent page and surround it with double brackets. This creates a link to your new page and makes it accessible from the main Wiki page. Otherwise nobody will recognise the so-called lost new page.
Wiki editing in general
Depending on the type of the wiki, there are several ways to edit your page. But don’t worry: The best thing of a wiki is, that nothing is lost. The old version will be there – and if someone changes your version of the page – your version will also be there. The options for editing, commenting viewing history, map and files may all be accessed from tabs at the top (1 in screenshot below) and if you are using a non-Boost theme, also from links in the navigation block (2 in screenshot below):
- The View tab allows users to display and view the wiki page.
- The Edit tab users to edit the wiki page.
- The Comments tab allows users to see and add comments about the wiki – providing comments are enabled on the site.
- The History tab allows users to see what has been altered in the wiki. Compare edits by clicking the “Compare Selected” button. Click the “Restore” button of the version you wish to restore if the latest edit is unsuitable
- The Map tab allows users to view areas of the wiki such as a list of pages, updated or orphaned pages etc. (Orphaned pages are pages not linked to anywhere.)
- To select what you want to see, click the Map menu dropdown box.
- The Files tab allows users to access any files which have been added to the wiki.Only the teacher role can by default add and manage files to the Files tab, but you can allow students to add and manage them with a permissions override to the Manage wiki files capability (mod/wiki:managefiles) in any particular wiki.
- The Administration tab is available to editing teachers in the course to delete page versions or selected pages. Clicking the “list all” button will list available pages to delete. The first page of the wiki cannot be deleted.
Teachers and other users with the mod/wiki:managewiki capability can delete any page or page version, with the exception of the first page, via the Administration tab.
Why use a wiki?
Wikis are a simple, flexible tool for collaboration. They can be used for everything from simple lists of web links to building entire encyclopedias. As an example, Wikipedia is the largest wiki in the world. In your own class it’s important to have a plan for your wiki so students know how it fits in with their learning. If it’s an individual wiki, will they be graded? Is it simply a staging area for group work that will be submitted as assignments later? Will you let the students be completely responsible for the work? How will you deal with offensive content? The great advantage of a wiki is that all edits are clearly visible and reversible.
Ideas for using wikis
Group lecture notes
Creating a wiki for group lecture notes after a lecture gives students a chance to combine all their notes. Those that missed information can get it from their peers. The group can also decide what information is critical and give it proper emphasis. Group lecture notes could be done with the entire class, if it is small enough, or with small working groups. Groups can also compare notes for further discussion and refinement.
Group Project management
A teacher assigning a group project can give students a place to work by creating a wiki with the group mode enabled. This will give each group their own space to record research, to develop outlines and to create the final product.
Brainstorming is a non-judgmental group creative process in which group members are encouraged to give voice to any ideas they personally consider relevant to the group exercise. In a face-to-face meeting, a brainstorming facilitator will usually stand in front of a big piece of paper and elicit ideas from the participants in the room. A teacher can create an online version of this process by setting up a wiki for the entire class or for smaller student groups and asking people to submit ideas around a brainstorming topic. People can add ideas as they occur and link to other pages for elaboration.
Contribute to other wikis
A teacher might assign his or her class the task of contributing to Wikipedia, Wikiversity, or to another wiki on the Web, on any class topic, perhaps by assigning students to groups (or making it a class project if the class is small enough and the topic broad enough) and challenging them to collaboratively create an article they would feel confident posting to a public-information space. Students will use the course wiki to create drafts of the article they will eventually publish to the community at the end of the semester.
Younger students could be encourage to work together on a wiki to build up a story -each adding a sentence following on from the previous contribution.