cmsimple 0.2.0

data/.gitignore

@@ -0,0 +1,31 @@
+.DS_Store
+.bundle
+.idea
+.rake_tasks
+.rvmrc
+.powenv
+REVISION
+vendor/bundle
+.rake_tasks~
+mkmf.log
+
+# Local config files
+database.yml
+schema.rb
+
+# Logs
+log
+log/*.log
+log/*.pid
+
+# Tempfiles
+tmp/**/*
+tmp/
+coverage
+capybara*
+
+# test app
+spec/rails_app/db/migrate/**.cmsimple.rb
+spec/rails_app/public/uploads/
+
+Gemfile.lock

data/.rspec

@@ -0,0 +1 @@
+--colour

data/.travis.yml

@@ -0,0 +1,16 @@
+rvm:
+  - 1.9.2
+  - 1.9.3
+gemfile: Gemfile.ci
+before_script:
+  - mysql -e 'create database cmsimple_test;'
+  - 'cp spec/rails_app/config/database.travis.yml spec/rails_app/config/database.yml'
+  - bundle exec rake db:migrate
+  - 'sh -e /etc/init.d/xvfb start'
+env:
+  - DISPLAY=':99.0' CUCUMBER_OPTS='-f progress' CI_WAIT_TIME=10
+script: bundle exec rake --trace
+notifications:
+  email:
+    - cmsimple@modeset.com
+

data/Gemfile

@@ -0,0 +1,20 @@
+source :rubygems
+
+gem 'mysql2'
+gem 'jquery-rails'
+
+gem 'multi_json', '>= 1.3.4'
+
+# gem 'mercury-rails', :path => '~/work/libraries/ruby/gems/mercury'
+gem 'mercury-rails', git: 'git://github.com/jejacks0n/mercury.git', ref: '227df218e4f28d797ecf42da73452b8073a672b7'
+
+# Gems used only for assets and not required
+# in production environments by default.
+group :assets do
+  gem 'sass-rails'
+  gem 'coffee-rails'
+  gem 'uglifier'
+end
+
+# Specify your gem's dependencies in ..gemspec
+gemspec

data/Gemfile.ci

@@ -0,0 +1,5 @@
+eval File.read(File.join(File.dirname(__FILE__), 'Gemfile'))
+
+group :test do
+  gem "phantomjs-linux"
+end

data/LICENSE

@@ -0,0 +1,19 @@
+Copyright (c) 2013 Mode Set, LLC
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of
+this software and associated documentation files (the "Software"), to deal in
+the Software without restriction, including without limitation the rights to
+use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
+of the Software, and to permit persons to whom the Software is furnished to do
+so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

data/README.md

@@ -0,0 +1,118 @@
+# CMSimple
+
+[![Build Status](https://secure.travis-ci.org/modeset/cmsimple.png?branch=master)](http://travis-ci.org/modeset/cmsimple)
+[![Code Climate](https://codeclimate.com/badge.png)](https://codeclimate.com/github/modeset/cmsimple)
+
+CMSimple is an easy-to-use but extensible CMS wrapped around the Mercury editor (https://github.com/jejacks0n/mercury), written as a Rails engine.
+
+## Getting Started
+
+Add the gem to your Gemfile
+
+```ruby
+gem 'cmsimple', github: 'modeset/cmsimple'
+```
+
+Run the install generator
+
+```shell
+rails g cmsimple:install
+```
+
+## Templates
+
+CMSimple templates are just views. They get rendered from the Cmsimple::FrontController inside the CMSimple engine. The core of a view is the render_region helper which indicates where in the dom a region is rendered and which region to render. There are two ways to invoke the region. The first is by just telling it what region you want to render. With this method you still have to tell Mercury how to find and associate the region. Below is an example:
+
+```erb
+<h1 id='page_title' class="page-heading" data-mercury='full'>
+  <%= render_region :page_title do %>
+    Placeholder
+  <% end %>
+</h1>
+```
+
+Above we are using an h1 as the region container for our content. And we are telling Mercury to use a "full" region. Please note that the id of the element must match the region name passed into the helper in this use case as the id is how Mercury references regions.
+
+You can also tell the helper to render the container by providing the tag: :element argument in the options hash. The options hash also takes the region type (:full, :snippets, :simple are supported) and an html option which gets handed to the content_tag helper so you can provide options for building out the content_tag container.
+
+```erb
+<%= render_region :aside_navigation, region_type: :snippets, tag: :div, html: {class: 'aside'} do %>
+<% end %>
+```
+
+### Notes
+
+There are a couple of things to keep in mind as you maintain and augment templates. The first is that you should try to keep regions consistently named. If a user changes the template that they want to use if the regions are not named the same the content will not display in the new template. Of course this isn't always possible, for example the home page template is very different from any of the content templates.
+
+Another item to note about this behavior is that if a user switches a template in draft mode and saves the content, if they attempt to revert back to the previous template they may permanently loose content in regions where the names are not available between templates. This is not the case if a user has published a page as they can then just revert to a previous version of the page to regain the content.
+
+Regions must always be contained by block level elements (i.e. the tag: :div declaration). This is actually a limitation of the browser. A specifically onerous element is the &lt;p&gt; tag. Since the W3C spec indicates that no block level elements can be children of the &lt;p&gt; tag, the browser will attempt to correct the content by moving it outside the tag. This results in a lot of confusion and strange looking rendered content.
+
+## Snippets
+
+[Cells](https://github.com/apotonick/cells) are how CMSimple implement Mercury's idea of snippets. Snippets are meant to be a way for authors to be able to utilize content that requires more complicated html to render. In general authors don't want to learn html, but often a design for a template can require a very specific html markup with associated classes in order for the css to be able to layout the page properly. Snippets provide this framework.
+
+Snippets have 3 required parts in order to provide basic functionality, the *_cell.rb Cell class (which is essentially like a mini controller), the display view and the options view
+
+* The cell class has three "actions", or states as cells calls them, display, preview, and options. Display is used to render the snippet into the template. Preview is used when a new snippet is added to a region via Mercury. It makes an ajax request for the preview so that the author can see the snippet in real time. 99% of the time preview just calls through to display. Options is where we create the form where the author will provide the content for a snippet.
+
+* The display view is just a normal rails view where you render your snippet. The best practice is to map all of the snippet options as instance variables in your action so that the view doesn't need to refer to a snippet. This allows easy updating and keeps the views simple.
+
+* The options view is where you create your form for telling Mercury what options are to be persisted for a given snippet. It is important to note that Mercury will only save options that exist in the form (more on this later). We are currently using Formtastic to create all the forms in this project.
+
+### Snippet options
+
+Snippet options are the most complex part of a snippet. This stems from trying to understand how Mercury serializes snippets and how they get re-rendered. Essentially Mercury can only persist what is in an options form. This means that _any_ data that needs to be captured and maintained throughout a snippets life must have an input in the form.
+
+* Changing the wrapper element of a snippet
+    
+    In order to change the wrapper tag (it defaults to a div) you need to provide a hidden input into the options form called "wrapperTag".
+
+    ```erb
+    <%= hidden_field_tag :wrapperTag, 'li' %>
+    ```
+    The above sets the wrapper tag to be an li instead of a div.
+
+### Images in snippets
+
+CMSimple has an image library where you can manage all of your images and then insert them into a region. From an authors standpoint setting an image in a snippet is no different. However on the development side it is not as clear cut. The reasoning for this is that CMSimple has to know which images are editable in a snippet and which are not. This is determined by a data attribute data-snippet-image. This attribute contains the name of the snippet option where the url to the image will be stored. Normally this is just "image" (see the content highlight snippet for an example). In a simple case this is all that is required to configure CMSimple to be able to update an image in a snippet. See the example
+code below.
+
+```erb
+<img data-snippet-image="image" data-image-geometry="<150x<80" src="<%= @image.presence || 'http://placehold.it/60x80/' %>" alt="alt" />
+```
+
+The code above obviously does a bit more than set the image reference. This is two fold, first we want to provide the author a placeholder image that is an appropriate size so they know which image to replace (the img tag has to exist for this all to work). We accomplish this by checking if the image option has been set and if not we just a place holder image. The second attribute you see is the data-image-geometry attribute. This is used to automatically filter the image library by images that are of "recommended" size. We don't ever restrict an author from using an image we just suggest what was originally intended.
+
+### Creating snippets
+
+Beyond the items mentioned above the only other requirement for creating snippets is telling Mercury that they exist. This happens via the app/views/cmsimple/_snippet_list.html.erb partial. You need to add a new li with an img that has a data attribute data-snippet="name_of_snippet" the attribute name has to match the name of the cell. I can hear you saying "that sounds like a lot to remember". Well that is why there is a generator for creating snippets.
+
+```shell
+rails g cmsimple:snippet snippet_name field1 field2
+```
+
+Field1 and field2 are the options you want the author to be able to enter data for. The generator will create the cell and the display and options view as well as add itself to the snippet_list partial.
+
+
+## Contributing
+
+To run the test suite for CMSimple, you will need to do the following:
+
+1. Setup the DB for testing
+  1. Configure a `database.yml` in the demo rails app6 (see spec/rails_app/config/database.example.yml)
+  2. Run setup tasks: `rake app:db:setup` and `rake app:db:test:prepare`
+2. Run specs
+  1. `rake spec`
+  2. Wait.
+
+
+## License
+
+Licensed under the [MIT License](http://creativecommons.org/licenses/MIT/)
+
+Copyright 2012 [Mode Set](https://github.com/modeset)
+
+
+## Make Code Not War
+![crest](https://secure.gravatar.com/avatar/aa8ea677b07f626479fd280049b0e19f?s=75)

data/Rakefile

@@ -0,0 +1,47 @@
+#!/usr/bin/env rake
+begin
+  require 'bundler/setup'
+rescue LoadError
+  puts 'You must `gem install bundler` and `bundle install` to run rake tasks'
+end
+begin
+  require 'rdoc/task'
+rescue LoadError
+  require 'rdoc/rdoc'
+  require 'rake/rdoctask'
+  RDoc::Task = Rake::RDocTask
+end
+
+RDoc::Task.new(:rdoc) do |rdoc|
+  rdoc.rdoc_dir = 'rdoc'
+  rdoc.title    = 'CMSimple'
+  rdoc.options << '--line-numbers'
+  rdoc.rdoc_files.include('README.rdoc')
+  rdoc.rdoc_files.include('lib/**/*.rb')
+end
+
+APP_RAKEFILE = File.expand_path("../spec/rails_app/Rakefile", __FILE__)
+load 'rails/tasks/engine.rake'
+
+Bundler::GemHelper.install_tasks
+
+# Rspec
+require 'rspec/core/rake_task'
+
+# Teabag
+desc "Run the javascript specs"
+task :teabag => "app:teabag"
+
+# Cucumber
+require 'cucumber/rake/task'
+
+Cucumber::Rake::Task.new(:cucumber) do |t|
+  # t.cucumber_opts = "features --format pretty"
+end
+RSpec::Core::RakeTask.new(:spec) do |t|
+  t.pattern = "./spec/**/*_spec.rb"
+end
+
+# Default should run all three
+task :default => [:spec, :teabag, :cucumber]
+

data/app/assets/javascripts/cmsimple.js

@@ -0,0 +1,61 @@
+ /* CMSimple / Mercury manifest
+  *
+  * Vendor dependencies
+  *
+  * Minimum jQuery requirements are 1.7
+  *= require jquery-1.7
+  *= require jquery_ujs
+  *
+  *= require jquery.to-json
+  *
+  * Underscore.js
+  *= require underscore-1.3.1
+  *
+  * Moment.js
+  *= require moment-1.6.2
+  *
+  * Spine.js (spine-rails)
+  *= require spine
+  *= require spine/ajax
+  *= require spine/relation
+  *= require spine/route
+  *
+  * Haml Coffee Templates
+  *= require hamlcoffee
+  *
+  * Mercury specifics
+  *
+  * Add all requires for the support libraries that integrate nicely with Mercury Editor.
+  * require mercury/support/history
+  *
+  * Mercury configuration
+  *= require cmsimple/mercury/config
+  *
+  * Require Mercury Editor itself.
+  *= require mercury/mercury
+  *
+  *= require jquery.ui.nestedSortable-1.3.4
+  *= require jquery-serializeObject
+  *
+  * Require any localizations you wish to support
+  * Example: es.locale, or fr.locale -- regional dialects are in each language file so never en_US for instance.
+  * require mercury/locales/swedish_chef.locale
+  *
+  * Custom Mercury handlers for CMSimple
+  *= require cmsimple/mercury/handlers
+  *
+  * CMSimple Editor
+  *
+  *= require cmsimple/lib/namespaces
+  *= require cmsimple/lib/support
+  *
+  *= require cmsimple/panels/page_metadata
+  *= require cmsimple/panels/publish
+  *= require cmsimple/panels/sitemap
+  *= require cmsimple/panels/redirects
+  *= require cmsimple/panels/images
+  *= require cmsimple/panels/versions
+  *
+  *= require cmsimple/controllers/editor
+  *
+  */

data/app/assets/javascripts/cmsimple/controllers/editor.coffee

@@ -0,0 +1,102 @@
+#= require cmsimple/models/page
+
+class CMSimple.Editor extends Spine.Controller
+  el: 'body'
+  constructor: (page)->
+    super()
+    @setCurrentPage(page)
+    @initializeMercury()
+
+    @routes
+      '/editor/*path': (params)=>
+        path = "/#{params.match[1]}"
+        @routeToPath(path)
+      '/editor': (params)=>
+        @routeToPath('/')
+
+    @bind 'pathLoaded', @proxy @ensureProperState
+    @bind 'pathLoaded', =>
+      @checkPublishedState()
+
+    CMSimple.Page.bind 'refresh', @proxy @checkPublishedState
+
+    @initialLoad ->
+      Spine.Route.setup(history: true)
+
+  initialLoad: (callback)->
+    @initializing = true
+    callback.call()
+    @initializing = false
+
+  routeToPath: (path)->
+    if @current_page and @current_page.path() is path
+      @loadPath(path)
+    else
+      @loadNewPageFromPath(path)
+
+  setCurrentPage: (page)->
+    return unless page
+    @current_page.unbind() if @current_page
+    @current_page = page
+    CMSimple.Editor.current_page = @current_page
+    @current_page.save(ajax: false) if @current_page.isNew()
+    @current_page.bind 'reload', @proxy @reload
+    @current_page.bind 'version', @proxy @viewVersion
+
+  loadNewPageFromPath: (path)->
+    @setCurrentPage(CMSimple.Page.forPath(path))
+    @loadCurrentSnippets()
+    @loadPath(path)
+
+  initializeMercury: ->
+    @mercury = new Mercury.PageEditor(null, saveStyle: 'json')
+
+    Mercury.on 'saved', =>
+      CMSimple.Page.fetch(id: @current_page.id)
+    Mercury.one 'ready', =>
+      @checkPublishedState()
+
+    @loadCurrentSnippets()
+
+  loadCurrentSnippets: ->
+    Mercury.Snippet.clearAll()
+    Mercury.Snippet.load(@current_page.snippets())
+
+  reload: ->
+    if @pathChange(@current_page.editPath())
+      @navigate @current_page.editPath()
+    else
+      @loadPath @current_page.path()
+
+  viewVersion: (page, version)->
+    @navigate "#{page.editPath()}?version=#{version}"
+
+  loadPath: (path)->
+    return unless path
+    if @initializing
+      #spine doesn't proxy the queryparams through when loading so we have to grab it ourselves
+      queryParams = window.location.search.replace('?', '')
+    else
+      [path, queryParams] = path.split('?')
+    @mercury.loadIframeSrc _([path, queryParams]).compact().join('?')
+    @trigger 'pathLoaded', path, queryParams
+
+  pathChange: (path)->
+    matches = window.location.href.match(/[http|https]:\/\/.[^\/]*(\/editor\/?.*)/)
+    currentPath = matches[1]
+    currentPath isnt path
+
+  ensureProperState: (path, queryParams)->
+    if queryParams?.match(/version=/)
+      $('.mercury-button').not('.mercury-historyPanel-button').addClass('disabled')
+      Mercury.one 'ready', -> Mercury.trigger('focus:window')
+    else
+      $('.mercury-button').not('.mercury-historyPanel-button').removeClass('disabled')
+
+  checkPublishedState: (record)->
+    publishButton = $('.mercury-publish-button')
+    if @current_page.reinflate().unpublished_changes
+      publishButton.addClass('unpublished')
+    else
+      publishButton.removeClass('unpublished')
+

data/app/assets/javascripts/cmsimple/lib/namespaces.coffee

@@ -0,0 +1,3 @@
+window.CMSimple ?= {}
+CMSimple.Panels ?= {}
+

data/app/assets/javascripts/cmsimple/lib/support.coffee

@@ -0,0 +1,4 @@
+
+$.ajaxSetup
+  cache: false
+

data/app/assets/javascripts/cmsimple/mercury/config.js

@@ -0,0 +1,462 @@
+/*!
+ * Mercury Editor is a CoffeeScript and jQuery based WYSIWYG editor.  Documentation and other useful information can be
+ * found at https://github.com/jejacks0n/mercury
+ *
+ * Supported browsers:
+ *   - Firefox 4+
+ *   - Chrome 10+
+ *   - Safari 5+
+ *
+ * Copyright (c) 2011 Jeremy Jackson
+ *
+ * Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated
+ * documentation files (the "Software"), to deal in the Software without restriction, including without limitation the
+ * rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit
+ * persons to whom the Software is furnished to do so, subject to the following conditions:
+ *
+ * The above copyright notice and this permission notice shall be included in all copies or substantial portions of the
+ * Software.
+ *
+ * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
+ * WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
+ * COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
+ * OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+ *
+ */
+window.Mercury = {
+
+  // # Mercury Configuration
+  config: {
+    // ## Toolbars
+    //
+    // This is where you can customize the toolbars by adding or removing buttons, or changing them and their
+    // behaviors.  Any top level object put here will create a new toolbar.  Buttons are simply nested inside the
+    // toolbars, along with button groups.
+    //
+    // Some toolbars are custom (the snippets toolbar for instance), and to denote that use _custom: true.  You can
+    // then build the toolbar yourself with it's own behavior.
+    //
+    // Buttons can be grouped, and a button group is simply a way to wrap buttons for styling -- they can also handle
+    // enabling or disabling all the buttons within it by using a context.  The table button group is a good example
+    // of this.
+    //
+    // It's important to note that each of the button names (keys), in each toolbar object must be unique, regardless
+    // of if it's in a button group, or nested, etc.  This is because styling is applied to them by name, and because
+    // their name is used in the event that's fired when you click on them.
+    //
+    // Button format: `[label, description, {type: action, type: action, etc}]`
+    //
+    // ### The available button types are:
+    //
+    // - toggle:    toggles on or off when clicked, otherwise behaves like a button
+    // - modal:     opens a modal window, expects the action to be one of:
+    //   1. a string url
+    //   2. a function that returns a string url
+    // - lightview: opens a lightview window (like modal, but different UI), expects the action to be one of:
+    //   1. a string url
+    //   2. a function that returns a string url
+    // - panel:     opens a panel dialog, expects the action to be one of:
+    //   1. a string url
+    //   2. a function that returns a string url
+    // - palette:   opens a palette window, expects the action to be one of:
+    //   1. a string url
+    //   2. a function that returns a string url
+    // - select:    opens a pulldown style window, expects the action to be one of:
+    //   1. a string url
+    //   2. a function that returns a string url
+    // - context:   calls a callback function, expects the action to be:
+    //   1. a function that returns a boolean to highlight the button
+    //   note: if a function isn't provided, the key will be passed to the contextHandler, in which case a default
+    //         context will be used (for more info read the Contexts section below)
+    // - mode:      toggle a given mode in the editor, expects the action to be:
+    //   1. a string, denoting the name of the mode
+    //   note: it's assumed that when a specific mode is turned on, all other modes will be turned off, which happens
+    //         automatically, thus putting the editor into a specific "state"
+    // - regions:   allows buttons to be enabled/disabled based on what region type has focus, expects the action to be:
+    //   1. an array of region types (eg. ['full', 'markdown'])
+    // - preload:   allows some dialog views to be loaded when the button is created instead of on first open, expects:
+    //   1. a boolean true / false
+    //   note: this is only used by panels, selects, and palettes
+    //
+    // Separators are any "button" that's not an array, and are expected to be a string.  You can use two different
+    // separator styles: line ('-'), and spacer (' ').
+    //
+    // ### Adding Contexts
+    //
+    // Contexts are used callback functions used for highlighting and disabling/enabling buttons and buttongroups.  When
+    // the cursor enters an element within an html region for instance we want to disable or highlight buttons based on
+    // the properties of the given node.  You can see examples of contexts in, and add your own to:
+    // `Mercury.Toolbar.Button.contexts` and `Mercury.Toolbar.ButtonGroup.contexts`
+    toolbars: {
+      primary: {
+        save:                  ['Save', 'Save this page'],
+        preview:               ['Preview', 'Preview this page', { toggle: true, mode: true }],
+        publish:               ['Publishing', 'Manage the publishing of this page'],
+        sep1:                  ' ',
+        undoredo:              {
+          undo:                ['Undo', 'Undo your last action'],
+          redo:                ['Redo', 'Redo your last action'],
+          sep:                 ' '
+          },
+        insertLink:            ['Link', 'Insert Link', { modal: '/mercury/modals/link.html', regions: ['full', 'markdown'] }],
+        insertMedia:           ['Images', 'Insert Media (images and videos)', {panel: function(){ return new CMSimple.Panels.ImageLibrary('media'); }}],
+        insertTable:           ['Table', 'Insert Table', { modal: '/mercury/modals/table.html', regions: ['full', 'markdown'] }],
+        insertCharacter:       ['Character', 'Special Characters', { modal: '/mercury/modals/character.html', regions: ['full', 'markdown'] }],
+        snippetPanel:          ['Snippet', 'Snippet Panel', { panel: '/cmsimple/snippets' }],
+        sep2:                  ' ',
+        editMetadata:          ['Page Info', 'Edit Page Metadata'],
+        historyPanel:          ['History', 'Page Version History', {panel: function(){ return new CMSimple.Panels.Versions('history'); }}],
+        sep4:                  ' ',
+        sitemap:               ['Site Map', 'List of pages in the site', {panel: function(){ return new CMSimple.Panels.Sitemap('sitemap'); }}],
+        redirects:             ['Redirects', 'List of redirects in the site', {panel: function(){ return new CMSimple.Panels.Redirects('redirects'); }}],
+        // sep4:                  ' ',
+        // notesPanel:            ['Notes', 'Page Notes', { panel: '/mercury/panels/notes.html' }]
+        },
+
+      editable: {
+        _regions:              ['full', 'markdown', 'snippets'],
+        predefined:            {
+          style:               ['Style', null, { select: '/mercury/selects/style.html', preload: true }],
+          sep1:                ' ',
+          formatblock:         ['Block Format', null, { select: '/mercury/selects/formatblock.html', preload: true }],
+          sep2:                '-'
+          },
+        colors:                {
+          backColor:           ['Background Color', null, { palette: '/mercury/palettes/backcolor.html', context: true, preload: true, regions: ['full'] }],
+          sep1:                ' ',
+          foreColor:           ['Text Color', null, { palette: '/mercury/palettes/forecolor.html', context: true, preload: true, regions: ['full'] }],
+          sep2:                '-'
+          },
+        decoration:            {
+          bold:                ['Bold', null, { context: true }],
+          italic:              ['Italicize', null, { context: true }],
+          overline:            ['Overline', null, { context: true, regions: ['full'] }],
+          strikethrough:       ['Strikethrough', null, { context: true, regions: ['full'] }],
+          underline:           ['Underline', null, { context: true, regions: ['full'] }],
+          sep:                 '-'
+          },
+        script:                {
+          subscript:           ['Subscript', null, { context: true }],
+          superscript:         ['Superscript', null, { context: true }],
+          sep: '-'
+          },
+        justify:               {
+          justifyLeft:         ['Align Left', null, { context: true, regions: ['full'] }],
+          justifyCenter:       ['Center', null, { context: true, regions: ['full'] }],
+          justifyRight:        ['Align Right', null, { context: true, regions: ['full'] }],
+          justifyFull:         ['Justify Full', null, { context: true, regions: ['full'] }],
+          sep:                 '-'
+          },
+        list:                  {
+          insertUnorderedList: ['Unordered List', null, { context: true }],
+          insertOrderedList:   ['Numbered List', null, { context: true }],
+          sep:                 '-'
+          },
+        indent:                {
+          outdent:             ['Decrease Indentation'],
+          indent:              ['Increase Indentation'],
+          sep:                 '-'
+          },
+        table:                 {
+          _context:            true,
+          insertRowBefore:     ['Insert Table Row', 'Insert a table row before the cursor', { regions: ['full'] }],
+          insertRowAfter:      ['Insert Table Row', 'Insert a table row after the cursor', { regions: ['full'] }],
+          deleteRow:           ['Delete Table Row', 'Delete this table row', { regions: ['full'] }],
+          insertColumnBefore:  ['Insert Table Column', 'Insert a table column before the cursor', { regions: ['full'] }],
+          insertColumnAfter:   ['Insert Table Column', 'Insert a table column after the cursor', { regions: ['full'] }],
+          deleteColumn:        ['Delete Table Column', 'Delete this table column', { regions: ['full'] }],
+          sep1:                ' ',
+          increaseColspan:     ['Increase Cell Columns', 'Increase the cells colspan'],
+          decreaseColspan:     ['Decrease Cell Columns', 'Decrease the cells colspan and add a new cell'],
+          increaseRowspan:     ['Increase Cell Rows', 'Increase the cells rowspan'],
+          decreaseRowspan:     ['Decrease Cell Rows', 'Decrease the cells rowspan and add a new cell'],
+          sep2:                '-'
+          },
+        rules:                 {
+          horizontalRule:      ['Horizontal Rule', 'Insert a horizontal rule'],
+          sep1:                '-'
+          },
+        formatting:            {
+          removeFormatting:    ['Remove Formatting', 'Remove formatting for the selection', { regions: ['full'] }],
+          sep2:                ' '
+          },
+        editors:               {
+          htmlEditor:          ['Edit HTML', 'Edit the HTML content', { regions: ['full'] }]
+          }
+        },
+
+      snippets: {
+        _custom:               true,
+        actions:               {
+          editSnippet:         ['Edit Snippet Settings'],
+          sep1:                ' ',
+          removeSnippet:       ['Remove Snippet']
+          }
+        }
+      },
+
+
+    // ## Region Options
+    //
+    // You can customize some aspects of how regions are found, identified, and saved.
+    //
+    // className: Mercury identifies editable regions by a className.  This classname has to be added in your HTML in
+    // advance, and is the only real code/naming exposed in the implementation of Mercury.  To allow this to be as
+    // configurable as possible, you can set the name of the class.  When switching to preview mode, this configuration
+    // is also used to generate a class to indicate that Mercury is in preview mode by appending it with '-preview' (so
+    // by default it would be mercury-region-preview)
+    //
+    // identifier: This is used as a unique identifier for any given region (and thus should be unique to the page).
+    // By default this is the id attribute but can be changed to a data attribute should you want to use something
+    // custom instead.
+    //
+    // dataAttributes: The dataAttributes is an array of data attributes that will be serialized and returned to the
+    // server upon saving.  These attributes, when applied to a Mercury region element, will be automatically serialized
+    // and submitted with the AJAX request sent when a page is saved.  These are expected to be HTML5 data attributes,
+    // and 'data-' will automatically be prepended to each item in this directive. (ex. ['scope', 'version'])
+    regions: {
+      attribute: 'data-mercury',
+      identifier: 'id',
+      dataAttributes: []
+      // determineType: function(region){},
+      },
+
+
+    // ## Snippet Options / Preview
+    //
+    // When a user drags a snippet onto the page they'll be prompted to enter options for the given snippet.  The server
+    // is expected to respond with a form.  Once the user submits this form, an Ajax request is sent to the server with
+    // the options provided; this preview request is expected to respond with the rendered markup for the snippet.
+    //
+    // method: The HTTP method used when submitting both the options and the preview.  We use POST by default because a
+    // snippet options form may contain large text inputs and we don't want that to be truncated when sent to the
+    // server.
+    //
+    // optionsUrl: The url that the options form will be loaded from.
+    //
+    // previewUrl: The url that the options will be submitted to, and will return the rendered snippet markup.
+    //
+    // **Note:** `:name` will be replaced with the snippet name in the urls (eg. /mercury/snippets/example/options.html)
+    snippets: {
+      method: 'POST',
+      optionsUrl: '/cmsimple/snippets/:name/options',
+      previewUrl: '/cmsimple/snippets/:name/preview'
+      },
+
+
+    // ## Image Uploading
+    //
+    // If you drag images from your desktop into regions that support it, it will be uploaded to the server and inserted
+    // into the region.  You can disable or enable this feature, the accepted mime-types, file size restrictions, and
+    // other things related to uploading.
+    //
+    // **Note:** Image uploading is only supported in some region types, and some browsers.
+    //
+    // enabled: You can set this to true, or false if you want to disable the feature entirely.
+    //
+    // allowedMimeTypes: You can restrict the types of files that can be uploaded by providing a list of allowed mime
+    // types.
+    //
+    // maxFileSize: You can restrict large files by setting the maxFileSize (in bytes).
+    //
+    // inputName: When uploading, a form is generated and submitted to the server via Ajax.  If your server would prefer
+    // a different name for how the image comes through, you can change the inputName.
+    //
+    // url: The url that the image upload will be submitted to.
+    //
+    // handler: You can use false to let Mercury handle it for you, or you can provide a handler function that can
+    // modify the response from the server.  This can be useful if your server doesn't respond the way Mercury expects.
+    // The handler function should take the response from the server and return an object that matches:
+    // `{image: {url: '[your provided url]'}`
+    uploading: {
+      enabled: false,
+      allowedMimeTypes: ['image/jpeg', 'image/gif', 'image/png'],
+      maxFileSize: 1235242880,
+      inputName: 'image[image]',
+      url: '/mercury/images',
+      handler: false
+      },
+
+
+    // ## Localization / I18n
+    //
+    // Include the .locale files you want to support when loading Mercury.  The files are always named by the language,
+    // and not the regional dialect (eg. en.locale.js) because the regional dialects are nested within the primary
+    // locale files.
+    //
+    // The client locale will be used first, and if no proper locale file is found for their language then the fallback
+    // preferredLocale configuration will be used.  If one isn't provided, and the client locale isn't included, the
+    // strings will remain untranslated.
+    //
+    // enabled: Set to false to disable, true to enable.
+    //
+    // preferredLocale: If a client doesn't support the locales you've included, this is used as a fallback.
+    localization: {
+      enabled: false,
+      preferredLocale: 'swedish_chef-BORK'
+      },
+
+
+    // ## Behaviors
+    //
+    // Behaviors are used to change the default behaviors of a given region type when a given button is clicked.  For
+    // example, you may prefer to add HR tags using an HR wrapped within a div with a classname (for styling).  You
+    // can add your own complex behaviors here and they'll be shared across all regions.
+    //
+    // If you want to add behaviors to specific region types, you can mix them into the actions property of any region
+    // type.
+    //
+    //     Mercury.Regions.Editable.actions.htmlEditor = function() {}
+    //
+    // You can see how the behavior matches up directly with the button names.  It's also important to note that the
+    // callback functions are executed within the scope of the given region, so you have access to all it's methods.
+    behaviors: {
+      //foreColor: function(selection, options) { selection.wrap('<span style="color:' + options.value.toHex() + '">', true) },
+      htmlEditor: function() { Mercury.modal('/mercury/modals/htmleditor.html', { title: 'HTML Editor', fullHeight: true, handler: 'htmlEditor' }); }
+      },
+
+
+    // ## Global Behaviors
+    //
+    // Global behaviors are much like behaviors, but are more "global".  Things like save, exit, etc. can be included
+    // here.  They'll only be called once, and execute within the scope of whatever editor is instantiated (eg.
+    // PageEditor).
+    //
+    // An example of changing how saving works:
+    //
+    //     save: function() {
+    //       var data = top.JSON.stringify(this.serialize(), null, '  ');
+    //       var content = '<textarea style="width:500px;height:200px" wrap="off">' + data + '</textarea>';
+    //       Mercury.modal(null, {title: 'Saving', closeButton: true, content: content})
+    //     }
+    //
+    // This is a nice way to add functionality, when the behaviors aren't region specific.  These can be triggered by a
+    // button, or manually with `Mercury.trigger('action', {action: 'barrelRoll'})`
+    globalBehaviors: {
+      exit: function() { window.location.href = this.iframeSrc() },
+      newPage: function(){ Mercury.modal('/pages/new', { title: 'Create a New Page', handler: 'newPage' }); },
+      editMetadata: function() { Mercury.modal('/pages/'+ CMSimple.Editor.current_page.id + '/edit', { title: 'Page Metadata', handler: 'editMetadata' }); },
+      publish: function() { Mercury.modal('/pages/'+ CMSimple.Editor.current_page.id + '/publish', { title: 'Publish Page', handler: 'publish' }); }
+      },
+
+
+    // ## Ajax and CSRF Headers
+    //
+    // Some server frameworks require that you provide a specific header for Ajax requests.  The values for these CSRF
+    // tokens are typically stored in the rendered DOM.  By default, Mercury will look for the Rails specific meta tag,
+    // and provide the X-CSRF-Token header on Ajax requests, but you can modify this configuration if the system you're
+    // using doesn't follow the same standard.
+    csrfSelector: 'meta[name="csrf-token"]',
+    csrfHeader: 'X-CSRF-Token',
+
+    // ## Editor URLs
+    //
+    // When loading a given page, you may want to tweak this regex.  It's to allow the url to differ from the page
+    // you're editing, and the url at which you access it.
+    editorUrlRegEx: /([http|https]:\/\/.[^\/]*)\/editor\/?(.*)/i,
+
+    // ## Hijacking Links & Forms
+    //
+    // Mercury will hijack links and forms that don't have a target set, or the target is set to _self and will set it
+    // to _parent.  This is because the target must be set properly for Mercury to not get in the way of some
+    // functionality, like proper page loads on form submissions etc.  Mercury doesn't do this to links or forms that
+    // are within editable regions because it doesn't want to impact the html that's saved.  With that being explained,
+    // you can add classes to links or forms that you don't want this behavior added to.  Let's say you have links that
+    // open a lightbox style window, and you don't want the targets of these to be set to _parent.  You can add classes
+    // to this array, and they will be ignored when the hijacking is applied.
+    nonHijackableClasses: [],
+
+
+    // ## Pasting & Sanitizing
+    //
+    // When pasting content into Mercury it may sometimes contain HTML tags and attributes.  This markup is used to
+    // style the content and makes the pasted content look (and behave) the same as the original content.  This can be a
+    // desired feature or an annoyance, so you can enable various sanitizing methods to clean the content when it's
+    // pasted.
+    //
+    // sanitize: Can be any of the following:
+    // - false: no sanitizing is done, the content is pasted the exact same as it was copied by the user
+    // - 'whitelist': content is cleaned using the settings specified in the tag white list (described below)
+    // - 'text': all html is stripped before pasting, leaving only the raw text
+    //
+    // whitelist: The white list allows you to specify tags and attributes that are allowed when pasting content.  Each
+    // item in this object should contain the allowed tag, and an array of attributes that are allowed on that tag.  If
+    // the allowed attributes array is empty, all attributes will be removed.  If a tag is not present in this list, it
+    // will be removed, but without removing any of the text or tags inside it.
+    //
+    // **Note:** Content is *always* sanitized if looks like it's from MS Word or similar editors regardless of this
+    // configuration.
+    pasting: {
+      sanitize: 'whitelist',
+      whitelist: {
+        h1:     [],
+        h2:     [],
+        h3:     [],
+        h4:     [],
+        h5:     [],
+        h6:     [],
+        table:  [],
+        thead:  [],
+        tbody:  [],
+        tfoot:  [],
+        tr:     [],
+        th:     ['colspan', 'rowspan'],
+        td:     ['colspan', 'rowspan'],
+        div:    ['class'],
+        span:   ['class'],
+        ul:     [],
+        ol:     [],
+        li:     [],
+        b:      [],
+        strong: [],
+        i:      [],
+        em:     [],
+        u:      [],
+        strike: [],
+        br:     [],
+        p:      [],
+        hr:     [],
+        a:      ['href', 'target', 'title', 'name'],
+        img:    ['src', 'title', 'alt']
+        }
+      },
+
+
+    // ## Injected Styles
+    //
+    // Mercury tries to stay as much out of your code as possible, but because regions appear within your document we
+    // need to include a few styles to indicate regions, as well as the different states of them (eg. focused).  These
+    // styles are injected into your document, and as simple as they might be, you may want to change them.
+    //
+    // {{regionClass}} will be automatically replaced with whatever you have set in the regions.class config directive.
+    injectedStyles: '' +
+      '[data-mercury]       { min-height: 10px; outline: 1px dotted #09F } ' +
+      '[data-mercury]:focus { outline: none; -webkit-box-shadow: 0 0 10px #09F, 0 0 1px #045; box-shadow: 0 0 10px #09F, 0 0 1px #045 }' +
+      '[data-mercury].focus { outline: none; -webkit-box-shadow: 0 0 10px #09F, 0 0 1px #045; box-shadow: 0 0 10px #09F, 0 0 1px #045 }' +
+      '[data-mercury]:after { content: "."; display: block; visibility: hidden; clear: both; height: 0; overflow: hidden; }' +
+      '[data-mercury] table { border: 1px dotted red; min-width: 6px; }' +
+      '[data-mercury] th    { border: 1px dotted red; min-width: 6px; }' +
+      '[data-mercury] td    { border: 1px dotted red; min-width: 6px; }' +
+      '[data-mercury] .mercury-textarea       { border: 0; box-sizing: border-box; -moz-box-sizing: border-box; -webkit-box-sizing: border-box; resize: none; }' +
+      '[data-mercury] .mercury-textarea:focus { outline: none; -webkit-box-shadow: none; -moz-box-shadow: none; box-shadow: none; }' +
+      '.selected-image { outline: 2px dotted #ff00ff }'
+  },
+
+  // ## Silent Mode
+  //
+  // Turning silent mode on will disable asking about unsaved changes before leaving the page.
+  silent: false,
+
+  // ## Debug Mode
+  //
+  // Turning debug mode on will log events and other various things (using console.debug if available).
+  debug: false,
+
+  // The onload method is provided as a callback in case you want to override default Mercury Editor behavior.  It will
+  // be called directly after the Mercury scripts have loaded, but before anything has been initialized.  It's a good
+  // place to add or change functionality.
+  onload: function() {
+    //Mercury.PageEditor.prototype.iframeSrc = function(url) { return '/testing'; }
+  },
+
+};