Bootcamp 3.3: The three-day developer bootcamp
Three days are enough to build a small site end to end: content classes, templates, overrides and an extension, on an installation made of Git clones. The bootcamp ends with each developer able to start a real project.
At a glance
| Course | Workshops and bootcamps |
| Module | Module 3: Three-day bootcamps |
| Duration | 3 days, 6 hours of sessions each |
| Level | Intermediate |
| Audience | PHP developers, 4 to 12 learners |
| Prerequisites | PHP, Git, Composer on each laptop; a GitHub account |
Learning objectives
At the end of the bootcamp, learners can:
- work in an installation of Git clones on a branch of their own and keep it updated;
- design content classes for a site;
- write templates with the template language and override them per class or node;
- build, enable and debug an extension, with settings of its own;
- deploy a PHP change under Velocity and send a change upstream as a pull request.
The agenda
| Day | Morning (3 h) | Afternoon (3 h) |
|---|---|---|
| 1 | Git installation (Develop with Git); core concepts (Teaching the core concepts) | Content classes and content (The content model and editing content, Class groups) |
| 2 | The template language (Templates and design, 6) | Overrides and debugging (Templates and design, 4 and 7) |
| 3 | Extensions and the RAD tools (Extensions, RAD tools); INI (exp:ini) | The console; Velocity and deploying (Serving the site, 8.3.14); a pull request |
Breaks: 15 minutes mid-morning and mid-afternoon, 45 minutes lunch, each day.
Trainer's notes
- The capstone runs through all three days: an "Events" site section, built a bit more each afternoon.
- Template syntax: check templates with the syntax check of Templates and design, 5 before opening the browser.
- Velocity: a changed class reaches Velocity's workers only after a restart or deploy; teach it once with a visible example.
Hands-on exercise: the bootcamp capstone
- Day 1: a content class "Event" (title, date, location, text) and five events in a folder "Events".
- Day 2: a full view override for events and a line view used in the folder's list.
- Day 3: an extension
bikeevents(made with a RAD wizard) that carries the override and its settings; enabled, autoloads regenerated, caches cleared; a small documentation fix sent as a pull request to a fork.
Expected result
- The Events folder lists five events with the custom line view; each event shows the custom full view.
- The override lives in the extension, not in
settings/siteaccess/. - A pull request link (to a fork, or the project when the change is real).
Quiz (end of bootcamp)
- Where should a project's overrides live: the siteaccess settings or an extension?
- What do you run after adding a class to an extension?
- Why does a PHP change not show under Velocity at once?
- What does
|washdo in a template?
Answers
- In an extension, so they travel with the code and are under version control.
php bin/php/ezpgenerateautoloads.php -e, then clear the caches.- Velocity's workers keep the application in memory; restart or deploy (Serving the site, 8.3.14).
- It escapes a value for safe output in HTML.
Further reading
Related pages
- Module 3: Three-day bootcamps
- Workshops and bootcamps: course overview
- Trainers: start here
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.
Become an Exponential Partner
Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.