Split Documentation into starting with Vagrant vs. starting with the VM

Issue Background

Hi,

since for the release we will publish a VM, I assume that part of the current documentation, focused on Vagrant, will not be generic any more but specific to the deployment method.

So the documentation should split in two, if the previous assumption is correct:

• Documentation specific to the deployment method
  • VM image
  • Vagrant
• Documentation independent of the deployment method, that explains how to set up B@D.

The we have the documentation, as we have now, that is more specific to the board.

Does it makes sense to have each docu in a different wiki page?

Best Regards

Agustin Benito Bethencourt Principal Consultant - FOSS at Codethink agustin.benito@codethink.co.uk

Issue description

Create separate pages for the different starting points of the users.

• Getting Started using Vagrant
• Getting Started using the pre-built VM

Acceptance criteria

This issue can be closed when the two document paths have been published.

• Link to the Getting started page using Vagrant
• Link to the Getting started using B@D box page
• The above pages are linked in the following pages: ciptesting , cross reference to each other at the end of the document , feature page, interesting links in the readme file of the B@D repo, instruction column of the table in the download page.