----- Original Message -----
> From: "Matt Micene" <nzwulfin gmail com>
> To: "Jonathan Lebon" <jlebon redhat com>
> Cc: "atomic-devel" <atomic-devel projectatomic io>, "container-tools" <container-tools redhat com>
> Sent: Friday, January 29, 2016 12:48:59 PM
> Subject: Re: [atomic-devel] Landing pages
> The current swing at a Vagrant based doc is here:
> Could we have two Quick Starts depending on if they're
> > familiar with Vagrant or not?
The manageiq website handles this sort of branching pretty nicely:
You choose openstack, ovirt, rhev or vsphere, and each heads off
to a nice short quickstart.
> That's also another topic that came in the original discussion is how many
> X Guides at all levels to we need? Virtualbox vs Libvirt? Vagrant vs Adv
> Vagrant? Fedora vs Centos?
> Here's the discussion that happened on IRC a billion Internet years ago:
> Open to comments and questions
> On Fri, Jan 29, 2016 at 3:39 PM, Jonathan Lebon <jlebon redhat com> wrote:
> > ----- Original Message -----
> > > I agree and am claiming responsibility here. We have an arguably better
> > > experience available currently for Fedora Atomic via Vagrant.
> > This is something that I've been trying to address with
> > Developer Mode as well, although I can see both of them
> > serving their purpose. E.g. Vagrant is much nicer if folks
> > are already set up for it, while Developer Mode is nice for
> > first timers who don't want that upfront investment of
> > setting up and learning Vagrant just to try out Atomic.
> > > So, excuses aside, I'll put together a new Super Quick Start Guide
> > > highlighting the vagrant builds that Dusty and Jason have worked hard on
> > > putting together.
> > Could we have two Quick Starts depending on if they're
> > familiar with Vagrant or not? Or would that be too confusing
> > to present?
Container-tools mailing list
Container-tools redhat com