As a Professional Services Consultant, I want to be able to use a modular, organized system of branches to allow trainees to follow along with live code examples during training sessions.

The modules will be independent of one another, and therefore reusable in any order, on any given day. They will be branches named according to this standard in the BikeRide repo:

/v1.5.1/devtrain/modulename/[0-9] where /modulename/ is the name of the module, and [0-9] represents an unsigned integer representing a step taken during live coding of examples in teaching the given module. The version number which is required at the beginning of the branch name will represent the latest stable version of eZ Platform at the time of preparation, and subsequent versions will be updated via an automated (and quality tested) process to rebase the latest versions of eZ Platform and eZ Enterprise, along with any updates to the steps required to stay forward-compatible with future releases.

The topics targeted for module creation are those listed below, based on the Developer Training Agenda:

Day 1

Discover Symfony 2 ( EZP-26464 )

• Files and directories structure
• Bundles
• Front controller and environments
• Request and Response
• Routing & Controllers
• Debug Toolbar & Web Profiler

Templating with Twig

• Twig introduction
• Automatic escape
• Functions
• Filters
• Variables

Day 2 + 3
eZ CMS

• Siteaccess configuration
• Content Type & Content
• Location
• Roles and policies
• Rest API
• eZ Architecture

eZ meets Symfony2

• Dependency Injection
• Container
• eZ Platform Twig Helper & Functions
• EzPublishCoreBundle
• Http Cache

Dig into the Public API

• Initialization
• Fetch a content
• Search & Pagination
• Create & Update content