EOS is an experimental PHP 5.5+ CMF/S built on top of the Laravel 5 framework. EOS is meant to be Page/Document Centric, lightweight, and flexible. The end goal is to allow developers to quickly turn HTML mockups in to live pages quickly. Bonus points for HHVM Compability, ya?

• Finish merging various experiments in to: core & plugins
• Finish functional prototype of backend

####EOS Management ** command line management utility / wrapper for artisan, composer, etc

####Multi-CSS Framework capable layout system

• Bootstrap
• YAML
• etc

####RESPONSIVE ALL THE THINGS

Templating/Design goals

• Provide a set of commonly used page layout skeletons (or chunks of layouts) similar to what can be found in the Dell Design Library

• Bonus points for an algorithm that can analyze a tempolate and "see what you were trying to do" and provide a better implementation of layout

####Page / eosWebDocument A page is simply a route (page alias, slug, whatever), a layout, a collection of content nodes, and some basic web/app meta data. At the end of the day, a template engine is sent an eosWebDocument as the data to render.

The Raw HTML skeleton / structure of a page, sans CSS, Content, or Scripts. A layout may contain layout chunks and defines Content Zones

A portion of a Layout which is reusable or which may be overridden in certain contexts. A layout chunk can also define content zones. Content Zones missing from an overridden layout chunk will be disregarded

The named Blade/Mustache/Twig or a specific XPATH to a region of your page layout where module output can written

• content_nodes is a generic content table that can contain different sorts of content pieces *Similar concept as in ModX "ContentElement" (modDocument, modSnippet, modChunk)
• nodeTypes enumaration: eosDocument, eosDocumentChunk

A theme is the collection of LESS/SASS portions of a Template

The whole thing. A collection of layouts, themes (css & images), and javascript resources