Introduction to Rangers Knowledge Base

RangersKB is based on one of the most popular wiki engine - TWiki. TWiki is known for its robust, ease of use, flexibility and powerfulness. For years, it has been backed by a huge developing and supporting community. TWiki itself comes with many built-in features including

• Version Control
• Search Capability
• WYSIWYG Editor
• Fine-grained Access Control
• RSS/Atom feeds and e-mail notification
• ...

For detailed information on TWiki please go to their web site or wikipedia page.

*Notice: Due to recent change of the TWiki governance model and release terms, community had forked a new project called Foswiki while the TWiki trademark and web site (twiki.net) had been kept under control by the original founder for commercial purpose in the future. Future version of RangersKB will follow the community to follow the Foswiki project. But to the end users of every version of RangersKB, it has no impact what-so-ever.

RangersKB is licensed and delivered as a separate software which runs within the TWiki container. Addition to the existing features that TWiki provides, RangersKB provides

• A hierachical view of the content in a navigation tree
• A easy-to-use UI
• Templates and forms for publishing workflow management and access control
• Pre-defined reports
• ...

Key Features of Ranger Knowledge Base

• Cached Navigation Tree

  • What is a cached navigation tree anyway? A lot of web based content management software, KB softwares provide a navigation tree to show the list of articles in a structured way for easy browsing of the content. However, not all the navigation tree are cached. With a non-cached navigation tree, everytime you interact with the tree, the tree will have to be downloaded from the web server all over again along with other page content. It adds a lot of overhead to the web server, but more importantly, the user experience is not as good as a cached navigation tree. A cached navigation tree is cached in your browser after being downloaded. It can be navigated locally in the browser without a chatty communication with the web server. Also, the loading of the articles are independent to the navigation tree.

    Cached Navigation Tree	Cached Navigation Tree

    Microsoft MSDN and IBM Information Center are two examples of the use of cached navigation tree. Just imagine, when you are navigating in MSDN, everytime when you expand a node on the navigation tree, the page and the tree get refreshed again. That will give you an idea why it sucks to not have a cached navigation tree.

• DB-Free

  • Most content management softwares or KB softwares rely on backend databases. Thanks to TWiki/Foswiki's text file engine, RangersKB is totally DB-free. You don't need to worry about adding another DBA or paying for DB license cost, hosting cost. You can be sure that there is no comprimise in terms of performance and scalability.

• Publishing Workflow

  • A new artcle is originally created in a draft area where only the author and moderators can access. It will be made public only when the moderator approves and submits the document into the production area.

Comparison between Rangers Knowledge Base and Similar Products

Pricing

For a limited time, you can get the RangersKB for $198.98, plus free upgrade and update for the first year including complimentary email support. Unlike other competitors, RangersKB doesn't limit the number of articles, or the number of "seats". You can have as many users as you need, and the size of the KB can grow as big as your hardware can handle. While the size increases along the way, you may buy more licenses and create a RangersKB cluster with mutiple servers to satisfy your requirements of scalability and high availability.

This is a promotional offer, and hurry, it won't last.

Please click here to proceed to order page. You will need to register an account if you have not done so.