Pimki in a Personal Information Manager based on Instiki's Wiki technology. Besides all the rich features and excellent look of Instiki, a few features have been added, such as: a personal blog, todo lists, graphical mapping, quick-links, advanced search and others.

Ruwiki is a simple, extensible Wiki-clone written in Ruby. It supports both CGI and WEBrick interfaces, templates, and CSS formatting. This Wiki differs from most other Wikis in that it supports project namespaces, so that two topics may be named the same for differing projects without colliding or having to resort to odd naming conventions. Please see the ::Ruwiki project in the running Wiki for more information. Ruwiki %RV#% has German and Spanish translations available.

Instiki is a Wiki Clone written in Ruby that ships with an embedded webserver. You can setup up an Instiki in just a few steps. Possibly the simplest wiki setup ever.

Another Ruby Wiki. See http://www.soks.org for details

Wiki2Go is a Ruby Wiki with the usual features plus anti-wikispam tools, graph drawing and ruby code formatting extensions and can optionally be backed by a CVS repository

Generates code for (primative) a SQL-based wiki within your Rails app.

Generates code for (primative) a SQL-based wiki within your Rails app.

Ribit is a Wiki implemented in Ruby. Main goal was to to stick to XHTML Basic so that contents could easily shown on mobile devices.

deplate is a ruby based tool for converting documents written in an unobtrusive, wiki-like markup to LaTeX, HTML, "HTML slides", or docbook. It supports page templates, embedded LaTeX code, footnotes, citations, bibliographies, automatic generation of an index, table of contents etc. It can be used to create web pages and (via LaTeX or Docbook) high-quality printouts from the same source. deplate probably isn't suited for highly technical documents or documents that require a sophisticated graphical layout. For other purposes it should work fine. deplate aims to be modular and easily extensible. It is the accompanying converter for the Vim viki plugin. In the family of wiki engines, the choice of markup originated from the emacs-wiki.

Please see the Wiki found at: http://bxms.rubyforge.org/wiki/wiki.pl

Wiki‚ð*ì‚Á‚Ä‚Ý‚é

A text parsing engine. The syntax is defined outside the engine as regex-based rules, in YAML or Ruby. It supports layering and multiple output types. Rules for Markdown to HTML are included, with optional layered extensions for tables and wikilinks.

cheat prints cheat sheets from cheat.errtheblog.com, a wiki-like repository of programming knowledge.

Junebug is a minimalist ruby wiki running on Camping.

Junebug is a minimalist ruby wiki running on Camping.

Although made popular by Windows, INI files can be used on any system thanks to their flexibility. They allow a program to store configuration data, which can then be easily parsed and changed. Two notable systems that use the INI format are Samba and Trac. More information about INI files can be found on the [Wikipedia Page](http://en.wikipedia.org/wiki/INI_file). ### Properties The basic element contained in an INI file is the property. Every property has a name and a value, delimited by an equals sign *=*. The name appears to the left of the equals sign and the value to the right. name=value ### Sections Section declarations start with *[* and end with *]* as in `[section1]` and `[section2]` shown in the example below. The section declaration marks the beginning of a section. All properties after the section declaration will be associated with that section. ### Comments All lines beginning with a semicolon *;* or a number sign *#* are considered to be comments. Comment lines are ignored when parsing INI files. ### Example File Format A typical INI file might look like this: [section1] ; some comment on section1 var1 = foo var2 = doodle var3 = multiline values \ are also possible [section2] # another comment var1 = baz var2 = shoodle

With dokkit you can: * generate static websites * generate many types of documents in many formats * write your documents using a simple wiki syntax and obtain high quality output (with pdflatex) * generate different output formats from the same source document * use models to quickly generate the documents you want (technical report, howto, guides, presentation, website, etc.) * simply derive new documentation models from the existing ones * simply modify existing models to fit your needs For more information about dokkit visit the website[http://dokkit.rubyforge.org/]

OWLScribble converts a specific set of wiki text markup into HTML. (The syntax used in the markup is a knockoff of the markup used by OpenWiki; the 'OWL' in OWLScribble means "OpenWiki-like".) The OWLScribble.each_wiki_link method provides a way to customize the HTML produced for individual in-wiki page links. (Since the URLs for such links is custom to each site, and the user may wish to perform DB queries to control the display and/or linking of various links.) The OWLScribble.each_wiki_command method provides a way to handle special processing instructions used in the markup.

The TagTreeScanner class provides a generic framework for creating a nested hierarchy of tags and text (like XML or HTML) by parsing text. An example use (and the reason it was written) is to convert a wiki markup syntax into HTML.

Wikitext is a fast wikitext-to-HTML translator written in C.