anchor.diff:    c.create_project_from_blueprint(blueprint, auth_token: TOKEN)
   end
   ----
  +
  
positive.code: }
  ----
  
  [source,ruby]
  ----
  require 'gooddata'
  
negative.code: 
  You might want to store the blueprint definition in a file. There is an obvious benefit and drawback to doing that in Ruby. The benefit is that it is programmable so you can do more magic if you need to. The biggest drawback is that is tying you to Ruby and this cannot be used by other tooling easily. We also provide another variant of the blueprint and that is its JSON serialization. While not programmable it is much more open to other languages so it is our preferred way to use it when we save to file.
  
  This is a blueprint in JSON that is the same as the one in previous example. Store it to a file and let's spin up a project using this one.
  
  [source,javascript]
  ----
  {
  