gf-Soks 1.0.4

data/templates/default/content/How%20to%20get%20the%20latest%20Soks%20from%20cvs.textile

@@ -0,0 +1,45 @@
+h1. How to get the latest Soks from cvs
+
+Note.  Soks now uses Darcs rather than CVS for development.
+
+If you can't wait for the next release of Soks, then you can get a copy out of the source control system.  Note that the cvs copy of Soks *{color:red}may have serious bugs*, so please don't try and upgrade a running site with it. 
+
+There are now three repositories:
+* [[Soks-stable => changes to soks-stable]], that contains code that has been, or will shortly be, released.
+* [[Soks-testing => changes to soks-stable]], that contians code that will probably make it to the next release.  www.soks.org uses the code from here.
+* [[Soks-development => changes to soks-development]], that contains ideas and experiments.
+
+There is a repository browser at http://www.counsell.org/darcs.
+
+h2. Just download and go
+
+I will try and maintain an up to date tar.gz copy of the repositories.  Unfortunately, until I find a way to hook into Darcs to create this on every change, it may not be 100% up to date.
+
+# @wget http://www.counsell.org/darcs/soks-stable/soks-stable.tar.gz@
+# @tar -xvzf soks-stable.tar.gzip@
+# @cd soks-stable@ and play
+
+Substitute soks-development or soks-testing for soks-stable if you require a different version.
+
+h2. Using Darcs
+
+Steps:
+# If you don't have a copy of darcs, get it from www.darcs.net
+# Go into a terminal
+# @cd wherever_you_want_to_download_soks_to@
+# @darcs get http://www.counsell.org/darcs/soks-stable@
+# @cd soks-stable@ and play.
+
+To update a repository you allready have:
+# @cd wherever_you_downloaded_soks@
+# @darcs pull http://www.counsell.org/darcs/soks-stable@
+# Note, you can use this to pull specific patches from different versions of soks.
+
+To send me a patch:
+# @cd wherever_you_downloaded_soks@
+# @darcs record@ to save your changes to your local copy
+# Send it to me:
+** @darcs send@ if your machine and firewall are configured so that sendmail works.
+** @darcs send -o=patch-file.txt@ then e-mail darcs@soks.org with the patch-file attached.
+
+Tag: Include this page in the distribution

data/templates/default/content/How%20to%20hack%20soks.textile

@@ -0,0 +1,66 @@
+h1. How to hack soks
+
+Here are some pointers to help you figure out where to make whatever changes and improvements you desire.  Soks's licence is liberal, so please do whatever you want, but I would appreciate any improvements you can send me ( tamc@rubyforge.com ).
+
+* bin - contains the soks-create-wiki.rb file
+* contrib - contains code from other people.  Currently Redcloth and Diff:LCS 
+** _Could these dependencies be resolved directly by RubyGems in future Soks releases?_
+** They _could_, but I'd have to figure out how to make rake package the gem differently from the zip and tgz file, so it has seemed simpler just to include them for now.
+* lib - contains the soks code
+* template - contains the defaults used by soks-create-wiki.rb when creating a new wiki.  This folder is copied over, and the show.rb template filled out.
+
+h2. template
+
+* start.rb - contains the default ruby file used by soks-create-wiki.rb, this is written using erb
+* attachments - contains the stuff that will be statically loaded when running a wiki, such as images and stylesheets. In particular you may want to replace logo.png
+* views - contains the default templates see Improving the style of this wiki for a few notes on this
+* content - contains the initial content for the wiki.  The .textile files are flatfile text files containing the textile for a page.  The title of the page is the filename (and has usually been url_encoded).  Any .yaml files in here contain arrays containing the change history of the page
+* version - contains the version number of this wiki.  Used by soks-create-wiki.rb to see if it needs upgrading.
+
+h2. lib
+
+* soks.rb - Just requires all the other files
+* soks-utils.rb - Contains various utility classes, EventQueue, Notify and some extensions to String to url_encode and decode
+* soks-storage.rb - Contains a module which is mixed into the Wiki class to allow it to be saved
+* soks-model.rb - Contains the model of the wiki: Wiki, Page and Revision
+* soks-view.rb - Contains the classes that turn the wiki into html: View, WikiRedCloth, Links, RollingMatch
+* soks-servlet.rb - Contains the webrick server that passes commands to and from the View object
+* soks-default-helpers.rb - Contains optional classes that a Wiki can load to provide added functionality.  These are called when changes are made to the site.  They include: AutomaticUpdateCrossLinks, AutomaticRecentChanges, AutomaticOnePageIndex, AutomaticMultiPageIndex, AutomaticSummary, AutomaticCalendar and AutomaticUpcomingEvents.
+* authenticators.rb - Contains some extra authenticators to extend those already provided by Webrick. Namely  NotAuthentication and OnePasswordAuthentication
+
+h3. soks-utils.rb
+
+* Notify - This is an improvement on the Observable mix-in. 
+* EventQueue - This is used by Notify to inform observers in sequence of an event taking place, while allowing the original triggering class to continue.
+
+h3. soks-model.rb
+
+A Wiki class has many Page classes which have many Revision classes.  ImagePage and AttachmentPage are subclasses of Page that return different textile.
+
+The Wiki class decides what type of page to create based on its name.  All AttachmentPage pages have names that start with 'Attached ', all ImagePage pages have names that start with 'Picture of'. This is defined in the @page_classes instance variable of the Wiki class.
+
+The Wiki loads all the pages from file into a hash.  When pages are changed it writes a copy to disk immediately.  It has a thread that watches the disk for any changes to the files.
+
+h3. soks-view.rb
+
+The View object does the business.  It is called by the soks-servlet, and then proceeds to call an appropriate method on the Wiki model. It may then Notify any observing AutomaticHelpers of any changes, before proceeding to render the html.  This rendering happens in two places: First the Page.textile is turned into html by WikiRedCloth. then an appropriate ERB file is loaded and called.
+
+The WikiRedCloth overrides the to_html method of redcloth to add a number of methods that do the automatic page insertion and automatic linking. The automatic linking is actually carried out in the RollingMatch class. A record of the links between pages is kept in the Links class and then written to each page object.  
+
+The ERB files are loaded from disk.  The appropriate erb file is selected by looking for the pattern ClassName_viewname.rhtml (e.g. Page_edit.rhtml). If that page doesn't exist then the process is repeated with the Page's superclass.  The ERB files are cached.
+
+h3. soks-servlet.rb
+
+This runs a Webrick server to interact with the user.   The server can be stopped by sending an interupt (ctrl-c).
+
+The server has two handlers, a WEBrick::HTTPServlet::FileHandler for doing the dynamic content (which is attached to any url starting in /attachment/) and a WikiServlet for the dynamic content.
+
+The WikiServlet service method takes a look at the request url. If it is '/' it redirects to '/view/Home Page'.  If it only has one slash in it (e.g. '/Home Page') then it assumes that it is equivalent to '/view/Home Page'. If it has two or more slashes in it (e.g. '/edit/Home Page' ) then it splits the url into a command ('edit') and the rest ('Home Page'). If the WikiServlet responds to doCommand (e.g. doEdit) then control is passed to that method.  Otherwise it is assumed the command is the name of a view (e.g. 'print') and is therefore passed as is to the View object. 
+
+The WikiServlet deals with file uploads by separately writing the uploaded file to the 'attachments' directory and also asking the 'View' object to create or revise an ImagePage object whose content is the filename of the uploaded file. 
+
+h4. soks-default-helpers.rb
+
+These are a series of classes that may be optionally loaded by a wiki's start.rb script. They receive notifications of page changes from the View object and can use this information to update other pages in the wiki. See automatic summaries for a little more detail.
+
+Tag: Include this page in the distribution

data/templates/default/content/How%20to%20import%20a%20site%20from%20instiki.textile

@@ -0,0 +1,15 @@
+h1. How to import a site from instiki
+
+[[ Instiki => www.instiki.org ]] is great, and was definitely an inspiration for this site.  If, however, you wish to import a wiki from instiki to here then you need to:
+
+# Launch your instiki wiki
+# Go to 'export' and click on 'Markup (textile)'
+# Unzip the downloaded folder.
+# Create a soks wiki: <code>soks-create-wiki.rb</code>
+# Stop the wiki <code>ctrl-c</code>
+# Copy the contents of the downloaded folder (step 3) into soks-wiki/content
+# Start the wiki <code>ruby soks-wiki/start.rb</code>
+
+Your instiki content should then appear.  Note that all the links still work, but that all the pages have their WikiWord names.
+
+Tag: Include this page in the distribution

data/templates/default/content/How%20to%20import%20data.textile

@@ -0,0 +1,41 @@
+h1. How to import data into a Soks wiki
+
+*The basic question:* How can I import data into Soks?  (both pages and attachments)
+
+I have a table worth of information that I would like to load into my Soks wiki.  Each row of the table will become a page and each row has a PDF file associated with it.
+
+What would be the process of dumping my tabular data in the wiki?  Do I merely need to dump out @.textile@ versions of the pages in the contents directory (properly escaped)?  Do I need the YAML revision companions?  Do I merely dump the PDF files in the @attachments@ directory (with proper @.textile@ files also placed in @contents@)?
+
+So far, I have something like,
+<pre>
+projects.each do |p|
+ name = CGI.escape("2005 ii Proposal: #{p.organization}: #{p.title}")
+ File.open(name+'.textile','w') do |f|
+  f.puts "h2. #{p.title}"
+  f.puts
+  f.puts "|Author:|#{p.author}|"
+  f.puts "|Organization:|#{p.organization}|"
+  f.puts "|FTE:|#{p.fte}"
+  f.puts "|Beneficiary:|#{p.beneficiary}|"
+  f.puts "|Submission:|Attached #{p.proposal.gsub(/\s/,'+').sub(/\..*?$/,'')}|"
+ end
+end
+</pre>
+
+Am I heading in the correct direction? --Bil
+
+Yes.  comments:
+# You don't need to escape the file-names, Soks should detect they are not escaped and correct them.
+# You don't need to create revisions files, Soks will create them automatically.
+# If a revision file exists, but is out of date, Soks will bring the revision file up to date.
+# (I think you have realised this, but just in case) To import the PDFs, you need to both put them in the attachment directory and create a page in the content directory whose name starts 'attached ' and whose content is @/attachment/filenameof.pdf@
+# You can do this while the wiki is running (soks periodically scans the content folder and updates itself with any changes[1]) but if you are adding a lot of files it is best to stop the wiki while the changes are made.
+-- tamc2
+
+An alternative (only appropriate if you plan to update the wiki from the database frequently) would be to write a helper class that you call from start.rb and that uses the @wiki.revise(pagename, content, author) methods.
+
+A third alternative would be to use DRb (e.g. write @require 'drb'@  @DRb.start_service( 'druby://localhost:9001', view)@ somewhere in your start.rb file) and then write a script (or use irb) to remotely call the @wiki.revise( pagename, content, author) methods.
+
+fn1.  Changes detected by looking at the file's timestamp, not its content.
+
+Tag: Include this page in the distribution

data/templates/default/content/How%20to%20install%20Soks.textile

@@ -0,0 +1,33 @@
+h1. How to install Soks
+
+h2. Requirements
+
+# Essential: Ruby 1.8.2 from http://www.ruby-lang.org/en/
+# Preferred: Ruby Gems from http://rubyforge.org/projects/rubygems/
+
+h2. The easy install
+
+If you have ruby gems, type:
+
+@gem install Soks@
+
+then
+
+@soks-create-wiki.rb@ (Gems should have installed this in your path so you can type it anywhere, if it hasn't, look in your ruby library under @gems/Soks-X.X.X/bin/@ )
+
+...and then surf to http://localhost:8000
+
+h2. The harder install
+
+Download the latest version of Soks from http://rubyforge.org/frs/?group_id=481
+
+<pre>
+<code>
+tar -xvzf Soks-x.x.x.tgz
+ruby Soks-x.x.x/bin/soks-create-wiki.rb
+</code>
+</pre>
+
+...and then surf to http://localhost:8000
+
+Tag: Include this page in the distribution

data/templates/default/content/How%20to%20password%20protect%20your%20wiki.textile

@@ -0,0 +1,53 @@
+h1. How to password protect your wiki
+
+You can specify what authentication to be used based on a regular expression match against the url used to access the page.
+
+Open @start.rb@ in your wiki directory. Un-comment and edit the authenticators section and edit the array.  The format is [  [ first regexp to match against title, authenticator to use ],  [ second regexp to match against title, authenticator to use ] ... ]. For example:
+
+h2. No authentication
+
+The following matches against all the standard 'non editing commands' and doesn't ask for any authentication:
+
+<code>[ %r{/(view|rss|print|find|meta)/.*}, WEBrick::HTTPAuth::NoAuthenticationRequired.new ]</code>
+
+h2. No uploads
+
+The following doesn't permit any file or picture uploads:
+
+<code>[ %r{/upload/.*}, WEBrick::HTTPAuth::NotPermitted.new ]</code>
+
+h2. Site wide password
+
+The following asks for a site wide password to edit or save changes to the home page:
+
+<code>[ %r{/(edit|save)/home page}, WEBrick::HTTPAuth::SiteWidePassword.new('password','You need to enter the site wide password to edit the home page') ]</code>
+
+h2. Per-user passwords
+
+The following uses the standard WEBrick authentication system on any page whose name starts with private. The standard WEBrick authentication uses a database of usernames and passwords.  See [[ Gnome's Guide => http://shogo.homelinux.org/~ysantoso/webrickguide/html/html_webrick.html ]] for details.
+
+<code>[ %r{/(view|edit|save)/private.*},WEBrick::HTTPAuth::BasicAuth.new( :UserDB => htpasswd, :Realm => realm ) ]</code>
+
+The following is the default. For any page it just asks for a username, but the password can be left blank.
+
+<code>[ %r{.*}, WEBrick::HTTPAuth::AskForUserName.new( 'No password, just enter a name') ]</code>			
+BasicAuth isn't very secure as it transfers passwords over plaintext. If you can cope with some incompatability with very old browsers, DigestAuth is more secure. To implement DigestAuth:
+
+# run this command: @htdigest -c /path/to/your/soks-wiki/htdigest "name of your realm" yourusername@ and enter your password. On gentoo, the full path is @/usr/sbin/htdigest2@
+# Add this line into start.rb, inside the authenticators= block: @[ %r{/(view|edit|save)/private.*},WEBrick::HTTPAuth::DigestAuth.new( :UserDB => WEBrick::HTTPAuth::Htdigest.new('/path/to/your/soks-wiki/htdigest'), :Realm => "name of your realm") ]@
+
+h2. Multiple authentication systems
+
+To further-complicate your login woes, there is a nifty trick you can pull with the way Soks does its authentications. Because it creates a separate instance of the authenticator for each regexp, you can stack 'em :) Say you want to restrict viewing to those who have an account, but you don't want everyone to be able to edit. The first step is to create two htdigest files. One will have those who can read, the other those who can write. When you make these files, ensure that the realms are identical. Now assign the htdigest.write to the (edit|save) bits, and the htdigest.read to the (view|print|etc) bits. The annoying bit is that users who can edit need to be added to both files, but it makes up for it by users not having to login again when they want to edit. 
+
+----
+
+h2. Suggestions / The future
+
+Is there any means to changing the authentication on the fly like how the editable "sidebar page" works?  (Have a "master" page that is access controlled, on which one would put other page links that would then become access controlled.) --Bil
+
+Can someone point me to an example (or outline the steps) to having the user names checked for validity by an LDAP server ?  (Note: I asked a similar question on the Webricken mailing list.) --Bil
+
+Not used LDAP myself, but the example at http://dataspill.org/posts/show/4 seems to show how one might communicate with the LDAP server to check valididty.  This would need to be inserted into a WEBrick authenticator. If you just duplicate the code of an existing WEBrick authenticator (e.g. 1.8/webrick/httpauth/basicath.rb) you should be able to do a few tweaks to the authenticate method to get what you want.  --tamc2
+
+Tag: Include this page in the distribution

data/templates/default/content/How%20to%20re%2Dbuild%20the%20page%20cache.textile

@@ -0,0 +1,71 @@
+h1. How to re-build the page cache
+
+If you upgrade, or something goes wrong, or you just delete the contents of the cache directory in your wiki, then it will be rebuilt automatically.  Unfortunately this can take quite a long time for very large wikis (I have a 4,500 page wiki).  I will try and improve this in a future version of soks, but in the mean time, you can write yourself a small script to rebuild the cache by duplicating the start.rb script in your wiki folder and modifying it to be something like this.
+
+<pre>
+<code>
+#!/usr/local/bin/ruby
+
+# This file is to rebuild the cache.  Don't blindly copy, but make your start.rb look like this.
+
+$LOG = Logger.new(STDOUT)
+$LOG.level = Logger::DEBUG
+$LOG.datetime_format = "%Y-%m-%d %H:%M:%S"
+
+#Add the required libraries to the search path
+begin
+	require 'rubygems'
+	require_gem 'Soks', '~> 1.0.0'
+	$LOG.info 'Loaded Soks 1.0.0 from gem'
+rescue LoadError
+	$LOG.info "Soks Gem version 1.0.0 could not be found"
+	$:.push( "/usr/lib/ruby/gems/1.8/gems/Soks-1.0.0/lib","/usr/lib/ruby/gems/1.8/gems/Soks-1.0.0/lib/helpers","/usr/lib/ruby/gems/1.8/gems/Soks-1.0.0//contrib" )
+	require 'soks'
+	$LOG.info 'Loaded Soks libraries from /usr/lib/ruby/gems/1.8/gems/Soks-1.0.0/lib","/usr/lib/ruby/gems/1.8/gems/Soks-1.0.0/lib/helpers","/usr/lib/ruby/gems/1.8/gems/Soks-1.0.0//contrib'
+end
+
+root_directory = File.expand_path( File.dirname( __FILE__) )
+$MESSAGES = YAML.load( IO.readlines("#{root_directory}/views/messages.yaml").join )
+banned_titles = IO.readlines("#{root_directory}/banned_titles.txt").map { |title| title.strip }
+
+module Notify
+	def notify( event, *messages)
+		#raise "Sorry! Shutting down..." if @shutting_down
+		#self.event_queue.event( event, messages )
+	end
+end
+
+class View
+	def shutdown
+		@wiki.save_cache(REDCLOTH_CACHE_NAME,@redcloth_cache)
+	end
+end
+
+wiki = Wiki.new( "#{root_directory}/content", "#{root_directory}/caches" )
+wiki.load_all_pages
+wiki.shutdown
+$LOG.info "Written page cache"
+
+view = View.new( wiki, "http://localhost:9999", "#{root_directory}/views" )
+view.name = 'A Soks Wiki'
+view.description = 'A Soks Wiki for you!'
+view.reload_erb_each_request = false
+view.dont_frame_views = ['print','rss','listrss','linksfromrss']
+view.redcloth_hard_breaks = false
+view.author_to_email_conversion = '@address-not-known.com'
+
+wiki.each do |pagename, page| 
+	view.rollingmatch[ page.name ] = page
+end
+
+wiki.each do |pagename, page| 
+	view.redcloth( page )
+end
+
+wiki.shutdown
+view.shutdown
+$LOG.info "Written view cache"
+</code>
+</pre>
+
+Tag: Include this page in the distribution

data/templates/default/content/How%20to%20report%20a%20bug.textile

@@ -0,0 +1,9 @@
+h1. How to report a bug
+
+I really appreciate bug reports.
+
+Please click [[ here => http://www.soks.org/edit/BugTypeATitleHere ]] or go to http://www.soks.org and create a new page whose title starts with bug:, e.g. @bug: does not make tea@.
+
+In that page, please give as much information as you can and leave some contact details.
+
+Tag: Include this page in the distribution

data/templates/default/content/How%20to%20upgrade%20soks.textile

@@ -0,0 +1,32 @@
+h1. How to upgrade
+
+First download the latest release of soks:
+
+Preferably:
+# Install rubygems from http://rubyforge.org/projects/rubygems/
+# @gem update Soks@ (you may need to be root first)
+
+Alternatively
+# Download the tar or zip file from http://rubyforge.org/projects/soks/
+# Unzip or untar it
+# Change into the soks directory
+
+h2. This will always work...
+
+Then execute the command. 
+
+# @soks-create-wiki.rb --destination-dir=path/to/your/wiki@ and it will guide you through the upgrade.
+
+If you haven't touched your start.rb file, then you are good to go.  Otherwise you will need to edit the new start.rb file in your wiki to your tastes, the way this is set up changed substantially in v1-0-0, but it should be clear enough.
+
+Should anything go wrong, or you need to revert, a pristine copy of your wiki is created in YourWikiName-bak-0.
+
+h2. But this is quicker if it is only a minor upgrade
+
+If your wiki is v1-0-0 or above then I have changed the version numbering system, so that if the version you wish to upgrade to only changes the last digit, you don't need to go through the full upgrade.
+
+If you use gems, then your wiki should automatically use the new version next time you start it.  Otherwise edit start.rb in your wiki to point to the new version of soks that you downloaded.
+
+Note that I may make minor improvements to the way the wiki looks, which will not appear in your wiki if you follow this method.  If you want to make sure they do, copy the contents of the soks/templates/default/views directory to your soks-wiki/views directory. 
+
+Tag: Include this page in the distribution

data/templates/default/content/How%20to%20use%20the%20Automatic%20Helper%20classes.textile

@@ -0,0 +1,12 @@
+h1. Automatic Helpers
+
+Soks has a range of helper classes:
+* Automatic summaries - Scan for other wiki pages and create new pages that have lists of relevant pages (e.g. Known Bugs)
+* Automatic counters - Watch for certain events and count them (e.g. most popular pages, most frequent visitor, most prolific author)
+* Automatic importers - Look outside the wiki and do things like mirroring rss feeds, or the contents of an e-mail folder
+* Automatic maintenance helpers - Prune old revisions, merge others, permanently remove deleted pages etc.
+* Automatic exporters - Take data from the wiki and put it elsewhere.
+
+The api for classes to modify the wiki is pretty simple, so you should be able to create what you want pretty quickly.
+
+Tag: Include this page in the distribution

data/templates/default/content/How%20to%20use%20this%20wiki.textile

@@ -0,0 +1,30 @@
+h1. Pointers on how to use this wiki
+
+h2. Adding Pages
+
+There are several ways to add pages to soks:
+# Click on the 'add a new page'
+# Highlight the text on the page you wish to link from and press crtl-n[1]
+# Type the title of the page you wish to create and click search, there will be a link to create the page at the bottom of the search results.
+# As you are editing a page, put the title of a new page in square brackets like this: <notextile>[[ title of the new page ]]</notextile>.  When you save the page, a link will be created that permits you to create a new page.
+
+Yes, this means it is very easy to create orphaned pages. No I don't think this is a problem, because there is a site index.
+
+fn1. This only works on some browsers.  It doesn't seem to work on Mac Firefox or Mac OmniWeb. It does on Mac Safari.  Please report your successes and failures.
+
+h2. Editing Pages
+
+* To edit a page, click edit this page at the bottom of the page. 
+* The pages are written in textile.  A reference is at http://hobix.com/textile/quick.html
+* Links to other pages within this wiki, and to web addresses, and to e-mail addresses, happen automatically
+* To force a link put it inside double square brackets e.g. <notextile>[[a forced link]]</notextile>
+* To alias a link: <notextile> [[ a different name for </notextile>=><notextile> site index ]] </notextile>
+* To insert another page: <notextile>[ [ insert site index ]]</notextile>
+* This is particularly usefull if you want to insert a picture: <notextile>[ [ insert picture of the soks logo ]]</notextile>
+* It can also be usefull to save one step in directing people to download an attached file: <notextile>[ [ insert attached file to download ]]</notextile>.
+
+h2. Searching
+
+The search box on the right takes a single regular expression.
+
+Tag: Include this page in the distribution

data/templates/default/content/List%20of%20changes.textile

@@ -0,0 +1,10 @@
+h1. List of changes
+
+There are three list of changes pages, all created automatically from submissions to the darcs repository:
+# Changes to soks-stable contains the changes that actually make it to a release.
+# Changes to soks-testing gives a flavour of what (might) be coming in the next couple of releases.
+# Changes to soks-development gives a sense of experiments with the code, some of which might make it to a release.
+
+If you wish to see changes from before the switch to darcs (i.e. version 1.0.1 and before) please see the list of changes for older versions.
+
+Tag: Include this page in the distribution

data/templates/default/content/News%3A%20Version%201%2D0%2D0%20released.textile

@@ -0,0 +1,19 @@
+h1. Version 1-0-0 released
+
+It gives me great pleasure to announce the sixth public release of Soks as v1-0-0.  There have been a lot of changes, and much of Soks has now stabalised so I've decided to call it a beta rather than an alpha.  When I iron out a few more bugs I might even be confident in calling it stable.
+
+See how to install soks, or how to upgrade soks for instructions.  There is a full list of list of changes and some known bugs, but in brief:
+
+* Page titles can now have any punctuation, and the wiki urls look slightly prettier.
+* Two new RSS feeds, one of which contains all the pages linked to from a particular page, the other that includes edits made to the contents of linked pages.  These are both useful in conjunction with the automatic summary classes.
+* Some popular pages, authors, visitors counters (not enabled by default)
+* The wiki can now save cache of page data and views when the wiki is shutdown.  This makes starting the wiki again much faster.
+* The way that all the settings are made has completely changed, hopefully to make it clearer, and to enable several wiki's to be mounted on the same Webrick server.
+* Some maintenance helpers, that can periodically slim the wiki (these are not enabled by default)
+* Can now include several static file handlers
+
+There has also been quite a lot of refactoring and bug fixing, all though some (not critical) bugs remain.  With the shift in version numbering, I plan to offer a 1-0-x series of releases as soon as I fix bugs until this release is thoroughly stable.  I will add features to a 1-1-0 release.
+
+
+
+Tag: Include this page in the distribution