These docs should cover the entire lifecycle of your CoreOS machines. Anyone can submit changes to these docs via Github. For more in-depth support, jumping into #coreos on IRC or emailing the dev list are recommended.
CoreOS runs on most cloud providers, virtualization platforms and bare metal servers. Running a local VM on your laptop is a great dev environment. Following the Quick Start guide is the fastest way to get set up.
Follow these guides to connect your machines together as a cluster. etcd is the primary clustering mechanism and is used for orchestration between CoreOS machines. Stay tuned for some exciting developments in this area.
Managing the lifecycle of your containers is the most important task of running a CoreOS cluster. Today CoreOS includes the primatives to build distributed systems — docker, etcd and systemd. Stay tuned for tools that integrate these building blocks together.
Configuration values are distributed within the cluster for your applications to read. Values can be changed programatically and smart applications can reconfigure automatically. You'll never have to run Chef on every machine in order to change a single config value ever again.
Most users will never have to build CoreOS from source or modify it in any way. If you have a need to modify CoreOS, we provide an SDK that allows you to build your own developer images. We also provide OEM functionality for cloud providers and other companies that need to customize CoreOS to run within their environment.