of SilverStripe 2 2005 • An Application Framework as well as a CMS • Customise it with PHP code, not with UI • Simple, intuitive UI • Site navigation generated from a page tree • Customisable data model • Solid publication workflow
solid international community • Ingo and Philipp had written a German book • ...then translated it to English! • SilverStripe 2.4 had just been released What was happening in 2010? In the SilverStripe community
websites were starting to become important • Mainly early-adopters or people with big budgets • Responsive design not yet mainstream • Social media increasingly important What was happening in 2010? Elsewhere in the world
designs • Responsive web design the norm • Lots of great frameworks • Some say “don’t tie your app to a single framework”—hexagonal architecture CMS & Web Trends 2015
Experience Management • A.K.A Personalisation • Of most interest to bigger customers • Sitecore, Adobe Experience Manager • Data journalism • Blurring lines between “app”, “data”, and “content” CMS & Web Trends 2015
is well-established—does anyone not use some kind of VM? • Containerisation the next wave • Apps increasingly built around micro-services The C Word 2015
SilverStripe to be a better citizen of the PHP ecosystem. • Namespacing • Flexibility over folder structure (use Composer’s vendor/ folder) • Including putting code outside the webroot • PSR-4 auto-loader • Simpler bootstrap • Smaller modules Interoperability What’s coming in SilverStripe 4
downloads still available, but they will come with composer.phar • We will rely more on Composer features such as auto-loading • This will make it easier to replace components such as Mailer with 3rd party implementations • We want to have less code to maintain! Composer for all What’s coming in SilverStripe 4
and draft/published for all your content • Pages • Files • Content blocks • An intuitive experience for users that care • An even more intuitive experience for users that don’t Something about versioning What’s coming in SilverStripe 4
UX takes a front-seat • Open-source projects are traditionally developer-led • Development of the CMS needs to be driven by users’ needs and not framework limitations Richer authoring tools