cyn.in combines the capabilities of collaboration tools like wikis, blogs, file repositories, micrologs instant discussions, other social applications into a seamless platform.

Like an application server, WebGUI handles all the mundane tasks such as database connectivity, session
management, and security. Then, WebGUI goes one step further. In WebGUI, custom applications can be built; once
built, those applications can be reused over and over throughout a site.

WebGUI provides power, versatility, and security. Everything in WebGUI is a template; this means everything in
WebGUI can be customized to meet an organization’s specific needs. Navigation menus can be configured and site
styles can be branded to make any site look and feel the way the organization intends. Existing applications can be
modified to perform and look as envisioned. WebGUI is made to perform to your standards. This is why WebGUI is
Web Done Right.

Users without programming skills can create web applications. Developers can extend the functionality of TWiki with Plugins. TWiki fosters information flow within an organization; lets distributed teams work together seamlessly and productively; and eliminates the one-webmaster syndrome of outdated intranet content.

Deki Wiki is similar to CMS web frameworks like Drupal, Mambo, Joomla and DotNetNuke, but a wiki in nature; therefore making it community-centric and significantly easier for end-users to participate. Also, it has a complete application programming interface (API) for programmers and extending Deki Wiki can be done in any programming language.

PmWiki’s key features include:

Custom look-and-feel: A site administrator can quickly change the appearance and functions of a PmWiki site by using different skins and HTML templates. If you can’t find an appropriate skin already made, you can easily modify one or create your own.

Access control: PmWiki password protection can be applied to an entire site, to groups of pages, or to individual pages. Password protection controls who can read pages, edit pages, and upload attachments. PmWiki’s access control system is completely self-contained, but it can also work in conjunction with existing password databases, such as .htaccess, LDAP servers, and MySQL databases.

Customization and plugin architecture: One principle of the PmWikiPhilosophy is to only include essential features in the core engine, but make it easy for administrators to customize and add new markup. Hundreds of features are already available by using extensions (called “recipes”) that are available from the PmWiki Cookbook.

Some of the main features of this wiki engine are as follows:

Support for different types of embedded elements, advanced (but optional) access control, with user registration, password management and provision for user profiles; advanced syntax highlighting; several page-related features, including full revision control, comments, categories, text searching, page cloning etc;
RSS feeds, WikiPing client functionality; a web-based wizard to install the package and to upgrade from WakkaWiki.

Pages use MediaWiki’s wikitext format, so that users without knowledge of XHTML or CSS can edit them easily.

When a user submits an edit to a page, MediaWiki writes it to the database, but without deleting the previous versions of the page, thus allowing easy reverts in case of vandalism or spamming. MediaWiki can manage image and multimedia files, too, which are stored in the filesystem. For large wikis with lots of users, MediaWiki supports caching and can be easily coupled with Squid proxy server software.