RubyGems - noodall-ui - Versions diffs - 0.0.2 - Mend

noodall-ui 0.0.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (542) hide show

data/demo/views/layouts/application.html.erb ADDED Viewed

@@ -0,0 +1,121 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
+<!--
+  HTML5 - When your ready to do so
+  <!doctype html>
+  <html lang="en">
+-->
+<head>
+<title><%#= Settings.site_name %> - <%= page_title %></title>
+<!-- Always force latest IE rendering engine (even in intranet) & Chrome Frame
+     Remove this if you use the .htaccess -->
+<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
+<!--  Mobile Viewport Fix
+      j.mp/mobileviewport & davidbcalhoun.com/2010/viewport-metatag
+device-width : Occupy full width of the screen in its current orientation
+initial-scale = 1.0 retains dimensions instead of zooming out if page height > device height
+maximum-scale = 1.0 retains dimensions instead of zooming in if page width < device width
+-->
+<meta name="viewport" content="width=device-width; initial-scale=1.0; maximum-scale=1.0;">
+<meta name="description" content="<%=h page_description %>" />
+<meta name="keywords" content="<%=h page_keywords %>" />
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+<meta http-equiv="content-language" content="en" />
+<meta name="author" content="<%#= Settings.site_name %>" />
+<meta name="copyright" content="<%= Time.now.year %>, <%#= Settings.site_name %>" />
+<meta name="Geo.Country" content="GB" />
+<meta name="Geo.Region" content="GB-BST" />
+<!-- so:Style Sheets -->
+  <%= stylesheet_link_tag 'reset', 'layout', 'skin', 'typography', 'forms', :media => 'screen,tv,projection' %>
+  <!--[if lte IE 8]><link href="/stylesheets/ie8.css" media="screen" rel="Stylesheet" type="text/css" /><![endif]-->
+  <!--[if lte IE 7]><link href="/stylesheets/ie.css" media="screen" rel="Stylesheet" type="text/css" /><![endif]-->
+<!-- eo:Style Sheets -->
+<!-- Place favicon.ico and apple-touch-icon.png in the root of your domain and delete these references -->
+<link rel="shortcut icon" href="/favicon.ico">
+<link rel="apple-touch-icon" href="/apple-touch-icon.png">
+<!-- so:JavaScripts -->
+  <script src="http://www.google.com/jsapi" type="text/javascript"></script>
+  <script type="text/javascript">
+    google.load("jquery", "1.4");
+    google.load("swfobject", "2.2");
+  </script>
+  <%= javascript_include_tag 'rails', 'cufon-yui', 'fancybox', 'carousel.lite', 'application' %>
+  <%= csrf_meta_tag %>
+<!-- so:JavaScripts -->
+<%= yield :head %>
+<!--
+    Asynchronous google analytics: mathiasbynens.be/notes/async-analytics-snippet
+    change the UA-XXXXX-X to be your site's ID
+    Now at the top cos google said so!
+-->
+  <script>
+   var _gaq = [['_setAccount', 'UA-XXXXX-X'], ['_trackPageview']];
+   (function(d, t) {
+    var g = d.createElement(t),
+        s = d.getElementsByTagName(t)[0];
+    g.async = true;
+    g.src = '//www.google-analytics.com/ga.js';
+    s.parentNode.insertBefore(g, s);
+   })(document, 'script');
+  </script>
+</head>
+</head>
+<body id="<%= page_id %>" class="<%= page_class %>">
+<div id="wrapper">
+<div id="header">
+  <h1><a href="/" id="logo">Site Name</a></h1>
+</div>
+    <!-- so:main-navigation -->
+    <ul class="nav" id="main-nav">
+      <li></li>
+    </ul>
+    <!-- so:main-navigation -->
+    <div id="content">
+      <%= yield %>
+    </div>
+    <%= form_tag(noodall_search_path, :method => :get, :class => 'search') do %>
+      <%= text_field_tag :q, params[:q], :value => 'Enter keyword(s) here'  %>
+      <%= submit_tag 'Search' %>
+    <% end %>
+    <div id="footer">
+      <!-- so:main-navigation -->
+        <ul class="nav" id="footer-nav">
+          <li></li>
+        </ul>
+      <!-- eo:main-navigation -->
+      <%= yield :footer %>
+    </div>
+</div>
+<!--[if IE]><script type="text/javascript"> Cufon.now(); </script><![endif]-->
+<!-- Last Updated: <%#= GlobalUpdateTime::Stamp.read %> -->
+</body>
+</html>

data/demo/views/nodes/page_a.html.erb ADDED Viewed

@@ -0,0 +1,14 @@
+<h1><%=h @node.title %></h1>
+<%= component(@node, 'main_slot_0') %>
+<div id="body"><%= @node.body.html_safe %></div>
+<%= component(@node, 'small_slot_0') %>
+<%= component(@node, 'small_slot_1') %>
+<%= component(@node, 'small_slot_2') %>
+<%= component(@node, 'small_slot_3') %>
+<%= component(@node, 'wide_slot_0') %>
+<%= component(@node, 'wide_slot_1') %>
+<%= component(@node, 'wide_slot_2') %>

data/demo/views/nodes/page_b.html.erb ADDED Viewed

@@ -0,0 +1,9 @@
+<h1><%=h @node.title %></h1>
+<%= component(@node, 'main_slot_0') %>
+<div id="body"><%= @node.body.html_safe %></div>
+<%= component(@node, 'wide_slot_0') %>
+<%= component(@node, 'wide_slot_1') %>
+<%= component(@node, 'wide_slot_2') %>

data/demo/views/nodes/page_c.html.erb ADDED Viewed

@@ -0,0 +1,12 @@
+<h1><%=h @node.title %></h1>
+<%= component(@node, 'main_slot_0') %>
+<div id="body"><%= @node.body.html_safe %></div>
+<%= component(@node, 'wide_slot_0') %>
+<%= component(@node, 'wide_slot_1') %>
+<%= component(@node, 'wide_slot_2') %>

data/features/change_templates.feature ADDED Viewed

@@ -0,0 +1,25 @@
+@cms
+Feature: Change templates
+  In order to change the style of a page without the need to delete it a website editor should be able to change the template of a node
+  Scenario: Change template
+    Given a page exists using the "Page A" template
+    And I am editing the content
+    When I follow "Change Template"
+    And I choose "Page C"
+    And I press "Change"
+    And I visit the content page
+    Then the page should be in the "Page C" template
+  Scenario: Prevent Template Change if sub content not allowed in new template
+    Given a page exists using the "Page A" template
+    And that page has "Page A" subpages
+    And that page has a "Page A" parent
+    And I am editing the content
+    When I follow "Change Template"
+    And I choose "Page C"
+    And I press "Change"
+    Then I should see "Template cannot be changed as sub content is not allowed in this template"
+    When I visit the content page
+    Then the page should be in the "Page A" template

data/features/content_templates.feature ADDED Viewed

@@ -0,0 +1,18 @@
+Feature: Content Templates
+  In order to change how the content looks and acts on the website a website editor will be able to select from predetermined templates
+  Scenario: Create Root Content
+    Given I create a new root
+    Then I should be able select a template from the following:
+     | Template           |
+     | Page A             |
+     | Page C             |
+  Scenario Outline: Create Child Content
+    Given I create a new child under an ancestor in "<Ancestor Template Name>" template
+    Then I should be able select a template from the "<Allowed Templates>"
+    Examples:
+     | Ancestor Template Name | Allowed Templates       |
+     | Page A                 | Page A, Page B, Page C  |
+     | Page C                 | Page C, Page B          |

data/features/gallery_component.feature ADDED Viewed

@@ -0,0 +1,22 @@
+@wip
+Feature: Gallery Component
+  To provide the ability to show many images on the website, website editors will be able
+  to create a gallery of images within a template
+  Background:
+    Given I am signed in as a website editor
+  @javascript
+  Scenario: Gallery Module
+    Given I am editing content
+    When I click a "Wide" component slot
+    And select the "Gallery" component
+    And fill in the following within the component:
+      | Title       | Big Promotion                     |
+      | Description | A really big thing is happening!  |
+    Then I add some images to from the asset library
+    And I press "Save" within the component
+    And I press "Publish"
+    And I visit the content page
+    Then I should see the gallery thumbnails

data/features/manage_assets.feature ADDED Viewed

@@ -0,0 +1,28 @@
+Feature: Manage assets
+In order to allow easy access to documents whilst editing a website editor will be able to easily upload, browse and modify documents
+  Scenario: Upload an Asset
+    Given I am using the asset library
+    When I upload a file
+    And enter tags
+    Then it should appear in the asset library
+    When I follow "Show"
+    Then I should see "Viewing"
+    When I follow "Edit"
+    Then I should see "Editing Asset"
+  Scenario: Browse Assets
+    Given files have been uploaded to the asset library
+    When I am using the asset library
+    Then I should be able to browse assets by content type
+    And I should be able to browse assets by tags
+  @javascript
+  Scenario: Insert an asset
+    Given files have been uploaded to the asset library
+    When I am editing content
+    And I click the editor "Insert Asset" button
+    And follow "Images"
+    And I click "Add" on an Asset
+    Then the "Image" asset should appear in the content editor

data/features/manage_content_tree.feature ADDED Viewed

@@ -0,0 +1,42 @@
+Feature: Manage Content Tree
+  In order to provide up to date information in a structured manner on the website a website editor will be able to manage the content in a tree structure
+  Background:
+    Given the website has been populated with content based on the site map
+  Scenario: Browse Content Tree
+    Given I am on the content admin page
+    Then I should see a list of the roots
+    When I click on a root
+    Then I should see a list the of the root’s children
+    When I click on a child
+    Then I should see a list of the child’s children
+  Scenario: Create Root Content
+    Given I am on the content admin page
+    Then I should be able to create a new root
+    And I should see the root listed within the roots
+  Scenario: Create Sub Content
+    Given I am on the content admin page
+    When I click on a root
+    Then I should be able to create a new child
+    And I should see the child listed within the root’s children
+  Scenario: Delete Content
+    Given I am on the content admin page
+    Then I should be able to delete content
+    And the content and all of it’s sub content will be removed from the website
+  Scenario: Reorder Children
+    Given I am on the content admin page
+    When I click on a root
+    Then I should be able change the order of the root’s children
+  @javascript
+  Scenario: Move Child to another Parent
+    Given I am on the content admin page
+    When I click on a root
+    Then I should be able to move a child content to another parent
+    And I should see the child listed within the other parent’s children

data/features/preview.feature ADDED Viewed

@@ -0,0 +1,8 @@
+@cms @wip
+Feature: PREVIEW CONTENT
+  A preview function will allow a website editor to view how content will look before they save it
+  Scenario: Preview Content
+    Given I am editing content
+    And I click preview
+    Then I should see how the content will look in the website

data/features/promo_component.feature ADDED Viewed

@@ -0,0 +1,18 @@
+Feature: Promo Component
+  In order to promotional information on a page a website editor will be able
+  to add text and image content wthin component slots
+  @javascript
+  Scenario: Add a promo component
+    Given I am signed in as a website editor
+    And I am editing content
+    When I click a "Small" component slot
+    And select the "Promo" component
+    And fill in the following within the component:
+      | Title       | Big Promotion                     |
+      | Description | A really big thing is happening!  |
+      | Link        | http://wearebeef.co.uk            |
+    And I press "Save" within the component
+    And I press "Publish"
+    And I visit the content page
+    Then I should see "Big Promotion"

data/features/publish_content.feature ADDED Viewed

@@ -0,0 +1,28 @@
+Feature: Publish Content
+In order to control when content is available on the website a website administrator will be able to define the time period for which content is published
+  Scenario: Publish content
+    Given content exists
+    When I publish the content
+    Then the content should be visible on the website
+    When I save content as draft
+    Then the content should not be visible on the website
+  Scenario: Publish content for set period
+    Given content exists
+    And I publish content between "20th July 2010" and "30th July 2010"
+    And today is "15th July 2010"
+    Then the content should not be visible on the website
+    When today is "25th July 2010"
+    Then the content should be visible on the website
+    When today is "5th August 2010"
+    Then the content should not be visible on the website
+  Scenario: Publish content for set period
+    Given today is "5th August 2010"
+    And published content exists with publish to date: "30th July 2010"
+    Then the content should not be visible on the website
+    When I am editing the content
+    And I clear the publish to date
+    Then the content should be visible on the website

data/features/search.feature ADDED Viewed

@@ -0,0 +1,12 @@
+Feature: Search
+  To allow website visitors to easily find content the website will have a keyword search facility that searches all content on the site
+  Background:
+    Given there is content that can be searched
+  Scenario: Search
+    Given I enter a search term in the search input
+    And press "Search"
+    Then I should see a paginated list of content that matches my search term ordered by relevance

data/features/sitemap.feature ADDED Viewed

@@ -0,0 +1,9 @@
+@website
+Feature: SITE MAP
+  In order to allow website visitors to see on overview of the entire site the website will
+  provide a site map showing all content on the website
+  Scenario: View Site Map
+    Given the website has been populated with content based on the site map
+    When I am on the site map page
+    Then I should see a tree style list that contains all content

data/features/step_definitions/asset_steps.rb ADDED Viewed

@@ -0,0 +1,66 @@
+Given /^I am using the asset library$/ do
+  visit noodall_admin_assets_path
+end
+When /^I upload a file$/ do
+  click_link "Upload"
+  fill_in "Title", :with => "A loverly asset"
+  attach_file("File", "#{Rails.root}/spec/files/beef.png")
+end
+When /^enter tags$/ do
+  fill_in "Tags", :with => "you, me, things, stuff"
+  fill_in "Description", :with => "Some nice info"
+  click_button "Create"
+end
+Then /^it should appear in the asset library$/ do
+  page.should_not have_content('Errors')
+  page.should have_content('A loverly asset')
+end
+Given /^files have been uploaded to the asset library$/ do
+  20.times { Factory(:asset) }
+  20.times { Factory(:document_asset) }
+  20.times { Factory(:video_asset) }
+  20.times { Factory(:asset, :title => "Tagged Asset", :tags => ['RAC','lorem','dolar']) }
+end
+Then /^I should be able to browse assets by content type$/ do
+  within(:css, "ul.choices") { click_link "Images" }
+  page.should_not have_content('Document asset')
+  page.should_not have_content('Video asset')
+  within(:css, "ul.choices") { click_link "Documents" }
+  page.should_not have_content('Image asset')
+  page.should_not have_content('Video asset')
+  within(:css, "ul.choices") { click_link "Videos" }
+  page.should_not have_content('Document asset')
+  page.should_not have_content('Image asset')
+end
+Then /^I should be able to browse assets by tags$/ do
+  within(:css, "ul.choices") { click_link "Images" }
+  within(:css, "div#tags") { click_link "RAC" }
+  page.should_not have_content('Image asset')
+end
+When /^I click the editor "([^"]*)" button$/ do |button_name|
+  within('.mceToolbar') do
+    click_link button_name
+  end
+end
+When /^I click "([^"]*)" on an Asset$/ do |button_name|
+  within('#browser-list ul li:first') do
+    click_link button_name
+  end
+end
+Then /^the "([^"]*)" asset should appear in the content editor$/ do |asset_type|
+  within_frame('node_body_ifr') do
+    page.should have_css("#tinymce img[src^='/media/']")
+  end
+end

data/features/step_definitions/cms_node_steps.rb ADDED Viewed

@@ -0,0 +1,126 @@
+Given /^the website has been populated with content based on the site map$/ do
+  seed_file = File.join(Rails.root, "demo", "seeds.rb")
+  load(seed_file)
+end
+When /^I click on a root$/ do
+  @_page = Noodall::Node.roots.last
+  within("tbody tr:last") { click_link "Children" }
+end
+Then /^I should see a list the of the root’s children$/ do
+  @_page.children.each do |child|
+    page.should have_content(child.title)
+  end
+end
+When /^I click on a child$/ do
+  @_child = @_page.children.first
+  within(:css, "tbody tr:first") { click_link "Children" }
+end
+Then /^I should see a list of the child’s children$/ do
+  @_child.children.each do |gchild|
+    page.should have_content(gchild.title)
+  end
+end
+Then /^I should be able to create a new root$/ do
+  click_link 'New'
+  fill_in 'Title', :with => 'New Root'
+  click_button 'Create'
+  page.should have_content(' was successfully created.')
+end
+Then /^I should see the root listed within the roots$/ do
+  visit noodall_admin_nodes_path
+  page.should have_content('New Root')
+end
+Then /^I should be able to create a new child$/ do
+  click_link 'New'
+  fill_in 'Title', :with => 'New Child'
+  click_button 'Create'
+  page.should have_content(' was successfully created.')
+end
+Then /^I should see the child listed within the root’s children$/ do
+  visit noodall_admin_node_nodes_path(@_page)
+  page.should have_content('New Child')
+end
+Then /^I should be able to delete content$/ do
+  @_deleted_node = Noodall::Node.roots.last
+  @_deleted_node_children = @_deleted_node.children
+  within(:css, 'table tbody tr:last') { click_link "Delete" }
+  page.should have_content("deleted")
+end
+Then /^the content and all of it’s sub content will be removed from the website$/ do
+  lambda { visit node_path(@_deleted_node) }.should raise_error(MongoMapper::DocumentNotFound)
+  @_deleted_node_children.each do |child|
+    lambda { visit node_path(child) }.should raise_error(MongoMapper::DocumentNotFound)
+  end
+end
+Then /^I should be able to move a child content to another parent$/ do
+  @_child = @_page.children.first
+  @_new_parent = Noodall::Node.roots.first
+  within(:css, "table tbody tr#node-#{@_child.id}") { click_link "Edit" }
+  # Simulates what we are now doing with JS
+  click_link "Advanced"
+  within(:css, '#parent-title' ) { click_link "Edit" }
+  within(:css, 'ol.tree' ) { click_link @_new_parent.title }
+  click_button 'Draft'
+end
+Then /^I should see the child listed within the other parent’s children$/ do
+  visit noodall_admin_node_nodes_path(@_new_parent)
+  within('tbody') do
+    page.should have_content(@_child.title)
+  end
+end
+Then /^I should be able change the order of the root’s children$/ do
+  table = table(tableish("table tr", 'td, th'))
+  title = table.hashes[2]['Title'] # 2 as zero index
+  within(:css, 'table tbody tr:nth(3)') { click_link "up" }
+  table = table(tableish("table tr", 'td, th'))
+  table.hashes[1]['Title'].should == title
+  within(:css, 'table tbody tr:nth(2)' ) { click_link "down" }
+  within(:css, 'table tbody tr:nth(3)' ) { click_link "down" }
+  table = table(tableish("table tr", 'td, th'))
+  table.hashes[3]['Title'].should == title
+end
+When /^I create a new child under an ancestor in "([^"]+)" template$/ do |template_title|
+  template = template_title.downcase.gsub(' ','_')
+  #create the ancester
+  parent = Factory(template.to_sym)
+  visit noodall_admin_node_nodes_path(parent)
+  click_link 'New'
+end
+Then /^I should be able select a template from the "([^"]+)"$/ do |sub_template_string|
+  sub_templates = sub_template_string.split(', ')
+  sub_templates.each do |sub_template|
+    choose sub_template
+  end
+end
+Then /^I should see a list of the roots$/ do
+  Noodall::Node.roots.each do |root|
+    page.should have_content(root.title)
+  end
+end