blacklight 3.8.2 → 4.0.0.pre6

data/doc/Home.md

@@ -1,77 +0,0 @@
-#
-[[https://github.com/projectblacklight/projectblacklight.github.com/raw/master/images/logo.png]]
-
-## Introduction
-
-Blacklight is an open source, Ruby on Rails engine/gem that provides a discovery interface for  [Apache Solr](http://lucene.apache.org/solr). Blacklight provides a basic user interface with a search box, facet constraints, stable document urls, etc., all of which is customizable via Rails (templating) mechanisms.  Blacklight accommodates heterogeneous data, allowing different information displays for different types of objects. 
-
-Some other features include:
-
-* Stable URLs for search and record pages allow users to bookmark, share, and save search queries for later access
-* Every Blacklight search provides RSS and Atom Responses of search results
-* For certain types of solr documents, an OpenURL/Z39.88 COinS object is embedded in each document, which allows plugins like Zotero to easily extract data from the page.
-* Blacklight supports OpenSearch, a collection of simple formats for the sharing of search results.
-* Faceted searching
-* Search queries can be targeted at specific sets of fields
-* Results sorting
-* Tools for exporting records to Refworks or Endnote, sending records via Email or SMS, or as a formatted citation.
-
-A [demo application](http://demo.projectblacklight.org) uses the latest version of Blacklight to display a basic library catalog.
-
-> NOTE: This wiki provides developer documentation for the latest Blacklight release. For documentation of older releases, see the end of this page.
-
-## Getting Started
-* [[Quickstart Guide|Quickstart]]
-* [[Site Search|http://projectblacklight.org/search.html]]
-* [[Demo|http://demo.projectblacklight.org]]
-* [[Example installations|Examples]]
-* [[Release Notes And Upgrade Guides]]
-
-
-## Developing your application
-* [[Blacklight Configuration]]: Search results, facets, query fields
-* [[Providing your own view templates]]: Overriding the out-of-the-box Blacklight templates the Rails way.
-* [[User Authentication]]: Connecting Blacklight with an existing Authentication system
-* [[Extending or Modifying Blacklight Search Behavior]] How to change the way the Blacklight discovery feature works.
-* [[Internationalization]]: Translating (or simply customizing) the Blacklight copy
-* [[Common Blacklight Patterns]]
-* [[Indexing your data into Solr]]
-* [[Additional Blacklight-specific Solr documentation|README_SOLR]]
-* [[Blacklight on Heroku]]
-* [[Pagination]]: Advise on how to customize pagination with Kaminari
-
-
-## Support
-Don't be scared to ask a question on the [[Blacklight mailing list|http://groups.google.com/group/blacklight-development]]. We appreciate you checking the documentation first and asking an educated question, but don't beat your head against the wall -- sometimes the existing documentation may be out of date and inaccurate.
-
-In order to reduce spam, the first time you post your email will be held in a moderation queue, but as soon as your first message is approved your posts won’t be held for moderation any longer. 
-
-Some Blacklight developers aso hang out on our IRC channel, usually during North American office hours. On `chat.freenode.net`, channel `#blacklight`. Stop in and say hi, we're happy to help with questions when we have time. [[http://freenode.net/faq.shtml]].
-
-* [[Bug Tracker|https://github.com/projectblacklight/blacklight/issues/]]
-* [[Mailing List|http://groups.google.com/group/blacklight-development]]
-* [[Jenkins Continuous Integration|http://hudson.projectblacklight.org]]
-
-## Contributing to Blacklight
-
-* [[Contributing to Blacklight]]
-* [[Community Principles]]
-* [[How to release a version]]
-* [[Testing]]
-
-## Releases
-Blacklight releases are published on the [[Rubygems.org blacklight project|https://rubygems.org/gems/blacklight]].
-
-For a list of features and bugfixes in Blacklight releases, see the [[Release announcements|Release Notes And Upgrade Guides]] on this wiki.
-
-### Older Documentation
-This wiki provides developer documentation for the ```master``` branch of Blacklight, which may include documentation of features not present in every Blacklight version. For documentation of specific Blacklight releases, see also:
-
-* [[Home]]
-* [[Blacklight 3.x|https://github.com/projectblacklight/blacklight/tree/release-3.8/doc]]
-* [[Blacklight 3.0 or 3.1|https://github.com/projectblacklight/blacklight/tree/release-3.1/doc]]
-* [[Blacklight 2.x|https://github.com/projectblacklight/blacklight/tree/v2.9-frozen/doc]] for all Blacklight 2.x releases; version-specific documentation is also available:
-    * [[Blacklight 2.7|https://github.com/projectblacklight/blacklight/tree/v2.7.0/doc]]
-    * [[Blacklight 2.6|https://github.com/projectblacklight/blacklight/tree/v2.6.0/doc]]
-    * [[Blacklight 2.5|https://github.com/projectblacklight/blacklight/tree/v2.5.0/doc]]
-    * [[Blacklight 2.4|https://github.com/projectblacklight/blacklight/tree/v2.4.2/doc]]

data/doc/How-to-release-a-version.md

@@ -1,37 +0,0 @@
-Before releasing, ensure that you're on the master branch.  Run all  tests and ensure that they pass. Also check the [[hudson site|http://hudson.projectblacklight.org/hudson/]] to make sure tests are passing.
-    ```bash
-    $ ./test_support/bin/test.sh 
-    ```
-
-1.  Create a release branch, wit the format release-{major}.{minor}
-    ```bash
-    $ git checkout -b release-{major}.{minor}
-    # Switched to a new branch 'release-{major}.{minor}'
-    ```
-
-1. Update the version number in ./VERSION
-    ```
-    {major}.{minor}.{patch}
-    ```
-
-1. Update the links in the readme files to point at the correct version so we're not linking to the documents in master which may not be correct for the specific tagged release (change "master" to version number)
-
-1. Fix GitHub issue tracker to know about the release
-      * Create a milestone in GitHub for the NEXT version.
-      * Move any open tickets for released version to the next version.
-      * Mark the milestone as released.
-
-1. Write an upgrade guide for [[Release Notes And Upgrade Guides]].
-
-1. Prepare announcement
-  * Include URL to GitHub closed issues for version 
-  * Include URL to github commits between tags. github can show all commits between two versions with a URL of this form: [[http://github.com/projectblacklight/blacklight/compare/v2.5.0...v2.6.0]]  Replace with previous version and current release version tags. 
-  * Include URL to the Github wiki [[Release Notes And Upgrade Guides]].
-
-1. Release the gem 
-```bash
-$ rake release
-```
-
-1. Announce
-  * Write emails announcing the release to Blacklight Development 

data/doc/Indexing-your-data-into-solr.md

@@ -1,5 +0,0 @@
-Blacklight uses Solr as its data index. Blacklight is agnostic as to how that Solr index gets populated. Many Blacklight contributors work in university libraries and have to deal with library data in the MARC format. The Blacklight out-of-the-box demo and test suite is geared towards that use case.
-
-## What’s the relationship between Blacklight and SolrMarc?
-
-However, one excellent way to index lots of MARC records into Solr quickly is to use SolrMarc. Some of the same people are active in both projects, e.g, Bob Haschart from UVA and Naomi Dushay from Stanford University. SolrMarc is not a Blacklight-specific project, it is also used by VuFind and other projects, and is a separate project that exists in its own right.

data/doc/Integration-with-Rails-Footnotes.md

@@ -1,20 +0,0 @@
-[[Rails Footnotes|https://github.com/josevalim/rails-footnotes]] is a helpful plugin that displays footnotes in your application for easy debugging, such as sessions, request parameters, cookies, filter chain, routes, queries, etc. Installing Rails Footnotes is very easy, just add this to your Gemfile:
-```ruby
-gem 'rails-footnotes', '>= 3.7', :group => :development
-```
-
-And add something like this to config/initializers/footnotes.rb to run the Footnotes plugin:
-```ruby
-if defined?(Footnotes) && Rails.env.development?
-  Footnotes.run!
-end
-```
-
-To add RSolr debugging information to the footnotes panel, you can use the [[RSolr Footnotes|https://github.com/cbeer/rsolr-footnotes]] gem by adding this to your Gemfile:
-```ruby
-gem "rsolr-footnotes", :group => :development
-```
-
-RSolr footnotes will capture every solr request with basic performance information and provide a link back to the Solr request URL.
-
-[[https://github.com/projectblacklight/projectblacklight.github.com/raw/master/images/rsolr_footnotes_example.png|frame|alt=Example of RSolr Footnotes in the Blacklight Demo App]]

data/doc/Pagination.md

@@ -1,38 +0,0 @@
-Blacklight uses [kaminari](https://github.com/amatsuda/kaminari) for providing pagination of Solr responses. 
-
-One motivation for this is so a pagination view theme can be provided that you can use for your custom code with ordinary ActiveRecord or anything else kaminari can handle, to have consistency between the rest of your app's pagination and Blacklight's Solr response pagination. 
-
-## How it works
-
-The Blacklight #paginate_params helper method takes an RSolr::Response, and converts it to something Kaminari #paginate can handle. (Basically just by translating some attribute names). So you could call:
-
-    paginate( paginate_params(@response) )  # where @response is an RSolr::Response
-
-But there's a shortcut Blacklight helper method which compacts this, #paginate_rsolr_response:
-
-    paginate_solr_response @response, :theme => 'blacklight'
-
-The `theme => 'blacklight'` part will be passed through kaminari, and tell kaminari to use the theme that the Blacklight plugin supplies at [app/views/kaminari/blacklight](https://github.com/projectblacklight/blacklight/tree/master/app/views/kaminari/blacklight)
-
-Any other arguments of ordinary kaminari paginate can also be passed in there. If all client code uses #paginate_solr_response, it also provides a 'hook' for local apps to completely over-ride pagination rendering, perhaps not even using kaminari. 
-
-Additionally, we sometimes want to output a "Showing X through Y of N" message, which kaminari doesnt' have a way to do by default, so we just provide our own way in a Blacklight view helper method, which takes a RSolr::Response too:
-
-    render_pagination_info(@response)
-
-## Changing the kaminari theme
-
-If you want to change how pagination links are rendered, the easiest/cleanest thing to do is to over-ride the 'blacklight' theme that the Blacklight plugin defines. Copy the view templates in Blacklight source at app/views/kaminari/blacklight to your own local app/views/kaminari/blacklight.  You actually only need to copy files you'll want to modify, templates not overridden with a local copy will still be found by kaminari from the Blacklight gem.  You can use any techniques available for creating a kaminari theme when editing these files, including over-riding more kaminari view templates if available. See the kaminari documentation. 
-
-There are other ways you could change how Blacklight pagination renders, but by doing it this way, any code (in core Blacklight or additional plugins you install) that tries to render pagination using kaminari with 'blacklight' theme will get your locally defined theme. 
-
-The "pagination info" (showing X through Y of N) is not part of the kaminari theme, but just a blacklight view helper method, #render_pagination_info.  To change this, just over-ride this method [[over-ride locally|CUSTOMIZING]] like any other Blacklight view helper method. 
-
-## Using kaminari theme for your own pagination
-
-Your local app may show pagination of ActiveRecord objects, that you'd like to appear consistent with other Blacklight pagination. Just use kaminari to show the pagination HTML, with the theme :blacklight.  This technique can be used for anything kaminari can paginate, such as Mongoid et al, in addition to ActiveRecord. Fetch the ActiveRecords using ordinary kaminari techniques (see kaminari docs) and then:
-
-    paginate @my_active_records, :theme => 'blacklight'
-
-That's it. There's currently no great way to display the #render_pagination_info for anything but RSolr::Response. 
-

data/doc/Providing-your-own-view-templates.md

@@ -1,109 +0,0 @@
-> TODO: Validate this page for Blacklight 4.x!
-
-# Customizing the User Interface
-## Layouts 
-
-The built-in Blacklight controllers all by default use a Rails view layout called "blacklight", that lives in the Blacklight source. This ends up being a bit confusing, but is the best way we have at present to have out of the box default using a layout with full functionality, without stepping on a possibly existing local 'application' layout. 
-
-To change what layout the Blacklight controllers use, simply implement a method #layout_name in your local application_controller.rb that returns the name of the layout you'd like them to use. 
-
-```ruby
-# [from app/controllers/application_controller.rb]
-class ApplicationController < ActionController::Base
-  ...
-    def layout_name
-       "application"
-    end
-  ...
-end
-```
-
-When implementing your own layout instead of using the stock one, you may want to look at the Blacklight app/views/layouts/blacklight.html.erb file to see what helper methods are called there, to maintain full Blacklight functionality you may want to call these same helper methods. 
-
-* `render_head_content` renders content within the
-  html `<head>` tag, which includes document-specific alternative
-formats as well as tags generated by plugins, etc.
-* `sidebar_items` renders features including sidebar content, e.g. facet
-  lists.
-* flash messages
-* user util links
-
-## Overriding Views (templates and partials)
-As a Rails Engine, you can easily override views in your app. You can see what views and partials are provided by looking in `[[./app/views|https://github.com/projectblacklight/blacklight/tree/master/app/views]]` inside the Blacklight source.
-
-Once you find the view you'd like to change, you should create a file with the same name and relative path in your own application (e.g. if you wanted to override [[./app/views/catalog/_show_partials/_default.html.erb|https://github.com/projectblacklight/blacklight/blob/master/app/views/catalog/_show_partials/_default.html.erb]] you would create ./app/views/catalog/_show_partials/_default.html.erb in your local application. Frequently, you will start by copying the existing Blacklight view and modifying it from there.
-
-It is generally recommended that you override as little as possible, in order to maximize your forward compatibility. Look to override either a small, focused partial template, or a helper method of partial template called from a larger template, so your application's version can call out to those same helpers or partial templates within blacklight core code. 
-
-## Overriding the CatalogController
-Overriding the Blacklight `CatalogController` implementation is easy, and the skeleton of the `CatalogController` is generated into your application for you when you install Blacklight. 
-
-See the [[Extending or Modifying Blacklight Search Behavior]] for tips and approaches to customizing the catalog.
-
-## Overriding Other Controllers
-
-1. Find the controller you're interested in blacklight's app/controllers/  . 
-2. Create a file with the same name in your local app/controllers. 
-3. This file requires the original class, and then re-opens it to add more methods.
- 
-```ruby
-require "#{Blacklight.controllers_dir}/some_controller"
-
-class SomeController < ApplicationController
-   # custom code goes here
-end
-```
-
-In that "custom code goes here", you can redefine certain methods (action methods or otherwise) to do something different.  You can also add new methods (again action methods or otherwise), etc. 
-
-It's kind of hard to call 'super' to call original functionality: 
-
-* the ruby language features here make 'super' unavailable, although you can work around that confusingly with the rails #alias_method_chain method. 
-* but more importantly, action methods in particular don't really suit themselves to being over-ridden and called by super, because the original implementation often does something you'd want to change but there's no easy way to 'undo' -- calling 'render', which can only be called once. 
-
-So basically, if you find yourself wanting to access some functionaltiy in the original implementation of a method that you also want to over-ride -- the best solution is probably to refactor Blacklight core code to put that functionality in a subsidiary method, so you can over-ride the action method entirely but call that logic from core.  Action methods should be short and sweet anyway. 
-
-
-## Custom View Helpers
-
-(This is accurate for Blacklight 3.1.1 and subsequent. Before that, things were messier). 
-
-One of the most common things you might need to do is create a view helper -- especially to override some Blacklight behavior implemented in it's own view helpers. The first step is looking at Blacklight source to determine what view helper method you want to override. 
-
-Blacklight comes packaged with several view helper modules. There is a BlacklightHelper in (blacklight source) app/helpers/blacklight_helper.rb , and several others that correspond to specific controller. (Note, depending on version of Rails and configuration, all helpers may get loaded for every request, even ones that are named to correspond only to a particular other controller). 
-
-If you simply created a local helper with the same name as a helper in Blacklight, that will end up preventing the Blacklight helper from being loaded at all though, which is not what you want to do to override. 
-
-We've structured each Blacklight view helper module into two parts to make it easy to selectively over-ride methods. For instance, here's Blacklight's app/helpers/blacklight_helper.rb:
-
-```ruby
-module BlacklightHelper
-  include Blacklight::BlacklightHelperBehavior
-end
-```
-
-Now, the actual methods will be found in app/helpers/blacklight/blacklight_helper_behavior.rb instead. 
-
-If you want to over-ride a helper method, copy the wrapper blacklight_helper into your local app, with the 'include' line, and now you can individually over-ride methods from BlacklightHelperBehavior, and the other methods you don't over-ride will still have their default implementation. 
-
-YOUR `app/helpers/blacklight_helper.rb`
-
-```ruby
-module BlacklightHelper
-  include Blacklight::BlacklightHelperBehavior
-
-  def application_name
-    "Bestest University Search"
-  end
-end
-```
-
-One helper you might want to over-ride for customization is #render_document_partial (currently defined in [[blacklight_helper|https://github.com/projectblacklight/blacklight/blob/master/app/helpers/blacklight_helper.rb]]), which you can over-ride to choose differnet local partial views to display a document on search results or detail page, possibly varying depending on type of document according to your own local logic. 
-
-## Adding in your own CSS or Javascript
-
-Within your local application, you can use the [[Rails Asset Pipeline|http://guides.rubyonrails.org/asset_pipeline.html]] to manipulate javascript and css documents.
-
-**todo??** better instructions for over-riding BL's built in CSS using SASS? (jrochkind thought jamesws wrote such already, but can't find them now)
-
-The Blacklight generator added a file to your app at `./app/assets/stylesheets/blacklight_themes/standard.css.scss`, elements of the BL default theme can be customized or over-ridden there. If there's something you want to do but aren't sur e the best way, feel free to ask on the listserv. 

data/doc/Quickstart.md

@@ -1,116 +0,0 @@
-Blacklight is a Ruby on Rails Engine plugin, meaning it provides a small application that runs inside an existing Ruby on Rails project.  For notes on upgrading Blacklight, check out our [[Release Notes And Upgrade Guides]] index.
-
-## Pre-requisites
- * Ruby 1.9 or higher (consider using [[RVM|https://rvm.beginrescueend.com/rvm/install/]] or [[RBEnv|http://rbenv.org/]] to manage your Ruby version). 
- * Java 1.5 or higher (in order to run solr under a java servlet container)
- * **For Windows users**: You may want to use [RailsInstaller](http://railsinstaller.org/) to get a Ruby on Rails environment.
-
-> NOTE: We run our continuous integration tests against Ruby 1.9.3, Ruby 1.8.7, JRuby and REE using the latest release of Rails, although we highly recommend using Ruby 1.9 and Rails 3.2.
-
-In addition, you should have the Bundler and Rails ruby gems installed:
-
-```bash
-$ gem install bundler
-$ gem install rails
-```
-
-## Install and Use
-
-1. Create a new rails 3 application
-
-    ```bash
-    $ rails new my_app      
-    #      create  
-    #      create  README
-    #      create  Rakefile
-    #      create  config.ru
-    #      create  .gitignore
-    #      create  Gemfile
-    #      [...]
-
-    $ cd my_app
-    ```
-
-    Rails automatically created an `public/index.html` file. However, Blacklight will provide a default `root` route for your application, so you probably want to remove it:
-
-    ```bash
-    $ rm public/index.html
-    ```
-
-2. Append this line to your application's `Gemfile`
-
-    ```ruby
-    gem 'blacklight'
-    ```
-
-    Especially if you are running on Linux, you may have to add `gem 'therubyracer'` to your gemfile, to get a Javascript runtime needed by the asset pipeline. 
-
-    then, update the bundle
-
-    ```bash
-    $ bundle install
-    ```
-
-3. Install blacklight using Devise for user authentication: 
-
-    ```bash
-    $ gem install devise
-    $ rails generate blacklight --devise
-    ```
-    If you would prefer to integrate with an alternative user authentication provider, see the [[User Authentication]] documentation. You can also install with no support for logged in users simply by omitting the devise install, and generating blacklight with `rails generate blacklight` (no --devise argument).
-
-4. Run your database migrations to create Blacklight's database tables:
-
-    ```bash
-    $ rake db:migrate
-    ```
-
-5. You will need to install and configure Solr. You can install
-Blacklight's example Solr configuration (using the jetty servlet container) that is configured to work with
-the Blacklight defaults:
-
-    ```bash
-    $ rails generate blacklight:jetty
-    ```
- 
-    Alternatively, you can also install your own copy of Solr or point Blacklight at an existing Solr server ( referred to in your `config/solr.yml`). The Blacklight
-configuration must match your Solr configuration. In addition, Blacklight has minor expectations about the Solr configuration and schemas. You can generate the Blacklight demonstration solrconfig and schema files using:
-
-    ```bash
-    $ rails generate blacklight:solr_conf path/to/output/directory/
-    ```
-  
-    **For Windows Users: ** This step will only work on *nix platforms. You can manually download and extract a tagged version of [blacklight-jetty](https://github.com/projectblacklight/blacklight-jetty/tags). After extracting the file, you need to update the `config/solr.yml` file to add a `jetty_path` key to your test environment, e.g.:
-
-    ```yaml
-    test: &test
-       url: http://localhost:8983/solr
-       jetty_path: C:\path\to\jetty 
-    ```
-
-
-6.  Make sure your Solr server is running. If you installed the Blacklight demo Solr/Jetty package, you can start the Jetty/Solr server using:
-
-    ```bash
-    $ java -jar jetty/start.jar &
-    ```
-
-6. Index some data. You can index test MARC records provided Blacklight running:
-
-    ```bash
-    $ rake solr:marc:index_test_data
-    ```
-
-7. Start up your application
-
-    ```bash
-    $ rails server
-    ```
-
-Visit the catalog at [[http://localhost:3000/catalog]]. You should see the Blacklight interface with 30 MARC records for testing. Additional MARC records are available from the [[blacklight-data|https://github.com/projectblacklight/blacklight-data]] repository. These can be ingested into Solr using SolrMarc, 
-
-```bash
-$ rake solr:marc:index MARC_FILE=(path to file)
-```
-
-See [[Configuring and Customizing Blacklight]] for information about how to customize the Blacklight user interface, search experience, and more.

data/doc/README.md

@@ -1,77 +0,0 @@
-#
-[[https://github.com/projectblacklight/projectblacklight.github.com/raw/master/images/logo.png]]
-
-## Introduction
-
-Blacklight is an open source, Ruby on Rails engine/gem that provides a discovery interface for  [Apache Solr](http://lucene.apache.org/solr). Blacklight provides a basic user interface with a search box, facet constraints, stable document urls, etc., all of which is customizable via Rails (templating) mechanisms.  Blacklight accommodates heterogeneous data, allowing different information displays for different types of objects. 
-
-Some other features include:
-
-* Stable URLs for search and record pages allow users to bookmark, share, and save search queries for later access
-* Every Blacklight search provides RSS and Atom Responses of search results
-* For certain types of solr documents, an OpenURL/Z39.88 COinS object is embedded in each document, which allows plugins like Zotero to easily extract data from the page.
-* Blacklight supports OpenSearch, a collection of simple formats for the sharing of search results.
-* Faceted searching
-* Search queries can be targeted at specific sets of fields
-* Results sorting
-* Tools for exporting records to Refworks or Endnote, sending records via Email or SMS, or as a formatted citation.
-
-A [demo application](http://demo.projectblacklight.org) uses the latest version of Blacklight to display a basic library catalog.
-
-> NOTE: This wiki provides developer documentation for the latest Blacklight release. For documentation of older releases, see the end of this page.
-
-## Getting Started
-* [[Quickstart Guide|Quickstart]]
-* [[Site Search|http://projectblacklight.org/search.html]]
-* [[Demo|http://demo.projectblacklight.org]]
-* [[Example installations|Examples]]
-* [[Release Notes And Upgrade Guides]]
-
-
-## Developing your application
-* [[Blacklight Configuration]]: Search results, facets, query fields
-* [[Providing your own view templates]]: Overriding the out-of-the-box Blacklight templates the Rails way.
-* [[User Authentication]]: Connecting Blacklight with an existing Authentication system
-* [[Extending or Modifying Blacklight Search Behavior]] How to change the way the Blacklight discovery feature works.
-* [[Internationalization]]: Translating (or simply customizing) the Blacklight copy
-* [[Common Blacklight Patterns]]
-* [[Indexing your data into Solr]]
-* [[Additional Blacklight-specific Solr documentation|README_SOLR]]
-* [[Blacklight on Heroku]]
-* [[Pagination]]: Advise on how to customize pagination with Kaminari
-
-
-## Support
-Don't be scared to ask a question on the [[Blacklight mailing list|http://groups.google.com/group/blacklight-development]]. We appreciate you checking the documentation first and asking an educated question, but don't beat your head against the wall -- sometimes the existing documentation may be out of date and inaccurate.
-
-In order to reduce spam, the first time you post your email will be held in a moderation queue, but as soon as your first message is approved your posts won’t be held for moderation any longer. 
-
-Some Blacklight developers aso hang out on our IRC channel, usually during North American office hours. On `chat.freenode.net`, channel `#blacklight`. Stop in and say hi, we're happy to help with questions when we have time. [[http://freenode.net/faq.shtml]].
-
-* [[Bug Tracker|https://github.com/projectblacklight/blacklight/issues/]]
-* [[Mailing List|http://groups.google.com/group/blacklight-development]]
-* [[Jenkins Continuous Integration|http://hudson.projectblacklight.org]]
-
-## Contributing to Blacklight
-
-* [[Contributing to Blacklight]]
-* [[Community Principles]]
-* [[How to release a version]]
-* [[Testing]]
-
-## Releases
-Blacklight releases are published on the [[Rubygems.org blacklight project|https://rubygems.org/gems/blacklight]].
-
-For a list of features and bugfixes in Blacklight releases, see the [[Release announcements|Release Notes And Upgrade Guides]] on this wiki.
-
-### Older Documentation
-This wiki provides developer documentation for the ```master``` branch of Blacklight, which may include documentation of features not present in every Blacklight version. For documentation of specific Blacklight releases, see also:
-
-* [[Home]]
-* [[Blacklight 3.x|https://github.com/projectblacklight/blacklight/tree/release-3.8/doc]]
-* [[Blacklight 3.0 or 3.1|https://github.com/projectblacklight/blacklight/tree/release-3.1/doc]]
-* [[Blacklight 2.x|https://github.com/projectblacklight/blacklight/tree/v2.9-frozen/doc]] for all Blacklight 2.x releases; version-specific documentation is also available:
-    * [[Blacklight 2.7|https://github.com/projectblacklight/blacklight/tree/v2.7.0/doc]]
-    * [[Blacklight 2.6|https://github.com/projectblacklight/blacklight/tree/v2.6.0/doc]]
-    * [[Blacklight 2.5|https://github.com/projectblacklight/blacklight/tree/v2.5.0/doc]]
-    * [[Blacklight 2.4|https://github.com/projectblacklight/blacklight/tree/v2.4.2/doc]]