Manage static pages for Spree Commerce.
Clone or download
Pull request Compare This branch is 85 commits ahead of pero-ict-solutions:master.

Spree Static Content

Build Status Code Climate

Good, clean content management of pages for Spree. You can use this to:

  • Add and manage static pages such as an 'About' page.
  • Show a static page instead of existing dynamic pages such as the home page, products pages, and taxon pages.


Using the 'Pages' option in the admin tab, you can add static pages to your Spree install. The page content can be pulled directly from the database, be a separate layout file or rendered as a partial.

In the admin tab, use the 'New page' option to create a new static page.

The title, slug, body, and meta fields will replace their respective page elements on load. The title, slug and body element are all required fields.

Body text provided without a layout / partial being specified will be loaded in the spree_application layout after it is pulled from the database.

Layout and Partial Rendering

To render an entire page without the spree_application layout, specify a relative path to the layout file (eg. spree/layouts/layout_file_name). This file will not be prefixed with an underscore as it is a layout, not a partial.

To render a partial, specify the path in the layout file name and check the 'Render layout as partial' option. The path specified in the layout area will not have an underscore, but it will be required in the filename.

Also note the availability of the render_snippet helper which finds a page by its slug and renders the raw page body anywhere in your view.


Use the 'Show in' checkboxes to specify whether to display the page links in the header, footer or sidebar. The position setting alters the order in which they appear.

Finally, toggle the visibility using the 'Visible' checkbox. If it is unchecked, the page will not be available.


  1. Add these extensions(unfortunately we need them all because of broken dependency on globalize) to your Gemfile with this line:

Spree >= 3.1

gem 'globalize', github: 'globalize/globalize'
gem 'spree_i18n', github: 'spree-contrib/spree_i18n'
gem 'spree_globalize', github: 'spree-contrib/spree_globalize', branch: 'master'
gem 'spree_static_content', github: 'spree-contrib/spree_static_content'

Spree 3.0 and Spree 2.x

gem 'spree_static_content', github: 'spree-contrib/spree_static_content', branch: 'X-X-stable'

The branch option is important: it must match the version of Spree you're using. For example, use 3-0-stable if you're using Spree 3-0-stable or any 3.0.x version.

  1. Install the gem using Bundler:
bundle install
  1. Install Spree Globalize(if you didn't have it before installing spree_static_content)
bundle exec rails g spree_globalize:install
  1. Copy & run migrations
bundle exec rails g spree_static_content:install
  1. Restart your server

If your server was running, restart it so that it can find the assets properly.


See corresponding guidelines

Copyright (c) 2008-2015 Peter Berkenbosch and contributors, released under the New BSD License