Model and migration for page blocks
Bug in page migration

We didn't actually create relation between page and translations.
Basic specs for block model
Testing relationship between page and blocks
Included configuration for NoCMS::Pages module
Created initializer and generator

We can now configure noCMS::Page in the Rails app
Changing the block layout config into a hash

We will need to access the layout often, so we better use a hash
Implementing access to the layout fields

Yeah, I know this is a trap. We are not really accesing, just responding, because we are not saving any info yet. But hold on! We're coming!
We create a default simple block layout
Implemented store and recovery of fields info

What we do is just serializing in the database with the standard serialize method from ActiveRecord
We test that we can update those fields without FactoryGirl

Just to make sure we can update_attributes for forms
Solving bug when creating a block with .create

Factory Girl doesn't use .new or .create in its .build and .create methods so we have to test a proper create.

Main problem is in the assign attributes method we have to hack to intercept those attributes that are not really attributes and store them in the fields area
Merge branch 'features/block-contents'
Migration for slug
Slug generation in page model
Great NoCMS Naming bug

When starting to play with controllers and routes it turned out that NoCMS is a headache for naming in Rails, so we rename the module to NoCms
Simple pages controller that finds the page and raise errors

Show view is empty. Right now we are not putting any content
Testing simple pages controller

Right now we don't test any content, just the http status code or the exceptions thrown
Testing page basic content is displayed

It doesn't involve content from blocks, just title and body
Now we test block contents