A simple, Git-powered wiki with a sweet API and local frontend.

A micro library providing objects with Publish-Subscribe capabilities. Both synchronous (in-process) and asynchronous (out-of-process) subscriptions are supported. Check out the Wiki for articles, guides and examples: https://github.com/krisleech/wisper/wiki

Creole is a lightweight markup language (http://wikicreole.org/).

Remote feature management for Cucumber. Bumps extends {Cucumber}[http://cukes.info] by allowing you to pull feature content and push run results to and from a remote server. This means that your feature files no longer need to live with your steps and other code. This also means that you can publish the results of a Cucumber run to another system. Bumps has been designed to work with {Bumpybot}[http://github.com/brentsnook/bumpybot] (a Google Wave robot) but it can be used with any server that meets the {push/pull contract}[http://wiki.github.com/brentsnook/bumps/push-pull-contract]. See the {wiki}[http://wiki.github.com/brentsnook/bumps] for more details.

wikiscript-parser - wikitext/script parser (builds abstract syntax tree 'n' more)

Wikipedia-API is a ruby wrapper for the MediaWiki API

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.

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

An HTML::Pipeline filter for WikiMedia-style wiki links.

wikiscript - scripts for wikipedia (get wikitext for page, parse tables 'n' links, etc.)

http://wiki.github.com/iori/wparser/ This package is Wiki Format Parser. Wiki => html

The docgenerator-gem create documents with export feature as LaTeX, HTML, Creole (a common wiki markup, see http://www.wikicreole.org ), conTeXt (only rudimentory), plain text (not very good supported) and Wiki-markup like Wikimedia (no support any longer). This gem extends the docgenerator-gem with a Creole-parser.

WikipediaWrapper is a ruby gem that extracts information from Wikipedia and makes the information available in an easy-to-use API. All information is extracted using the Wikipedia/MediaWiki API.

Wikidotrb is a Ruby library inspired by wikidot.py, providing utility functions to interact with the Wikidot platform, making it easier to automate and manage content.

Ruby client for the Wikipedia API

= Ungulate According to Wikipedia, this can mean "hoofed animal". Camels have hooves. This is a gem for uploading and processing images using an Amazon Web Services stack. It comes with a few goodies: * ungulate_server.rb - simple queue runner that expects a YAML-encoded job description for RMagick * Ungulate::FileUpload - a model for e.g. Rails that does some cryptography stuff - example to follow * A view helper for Rails: "ungulate_upload_form_for" == Installation gem install ungulate == Documentation http://wiki.github.com/camelpunch/ungulate/ == Note on Patches/Pull Requests * Fork the project. * Make your feature addition or bug fix. * Add tests for it. This is important so I don't break it in a future version unintentionally. * Commit, do not mess with rakefile, version, or history. (if you want to have your own version, that is fine but bump version in a commit by itself I can ignore when I pull) * Send me a pull request. Bonus points for topic branches. == Copyright Copyright (c) 2011 Camel Punch Limited. See LICENSE for details.

Given a Wikipedia article, generate a tree of linked articles from the summary of the first.

MySpaceID lets your users log on using their MySpace account info, after which their MySpaceID data becomes available; that is, your web servers will be able to communicate with our web servers and request user data. This SDK project contains examples of the base API code necessary to make signed requests against the MySpaceID REST API. To use the MySpaceID API, you first need to register on the MySpace Developer Site, create an app, and obtain a consumer key and secret. Information about these procedures, and about MySpaceID in general, is available at the MySpaceID Developer Wiki: http://wiki.developer.myspace.com/index.php?title=Category:MySpaceID The MySpaceID Ruby SDK enables you to work with MySpace data using the OpenStack (OpenID, OAuth etc) and the MySpace REST APIs via easy-to-use high level interfaces. The best way to implement your own application is to take an existing sample and customize it. Working Examples in this SDK: * OAuth - make signed requests * OpenID + OAuth Hybrid - delegated login, and making signed requests Documentation * Ruby SDK Documentation Summary: samples/rails/README * Ruby SDK - API Documentation: http://myspaceid-ruby-sdk.googlecode.com/svn/trunk/doc/index.html

A quick and simple responsive project wiki theme for jekyll sites and GitHub Pages.

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