We want to find out what features you'd like to see implemented, (or what problems royally annoy you), on the SilverStripe.org site.
Recently, SilverStripe Ltd did a reconstruction of the SilverStripe.com site. Part of it was that we wanted something splashy to go with launching Dawn™, but we also wanted to migrate our own .com site to SilverStripe CMS 2.4. Since we were upgrading the backend, we figured we might as well work on improving the public facing portions too. Sorta like, "Gee, Doc, so long as I'm going to have to have surgery for my appendix anyway, can you work in a tummy tuck while I'm under?"
We're in the middle of re-writing our user help to be compatible with SilverStripe CMS 2.4.
Well written user help documentation helps us and other SilverStripe developers save time. Every question that customers can answer themselves using user help is a question that they don't have to ask the development team. For that reason, as we shift from 2.3 to 2.4, we'd like to get away from focusing on features and more towards explaining how to accomplish tasks - shifting from "what things are" to "how to get things done." It's a massive re-write that has us practically starting from scratch.
I'm going to be one of 6 people representing New Zealand, against Australia, and the United States, as a member of the Code Blacks team in the competition. I'm honoured to be chosen to represent New Zealand.
The criticism we hear most often from the developer community is that, with the exception of our books, SilverStripe needs to improve its developer documentation. And it's a fair point.
We made some decisions regarding our documentation a while back that we thought would work at the time - a best guess as to how to proceed. But these turned out to limit us in ways we simply didn't foresee.
We've released a module that lets SilverStripe work with PostgreSQL. I've been the primary coder working on the PostgreSQL module for the past year, and the work we did on this, alongside changes to the core Sapphire framework, have been released as part of version 2.4.
Some limitations of MySQL were becoming issues for us over the past few years. One of them was that the storage engines, InnoDB and MyISAM, each had advantages that the other didn't, while Postgres is a single storage engine with all of those benefits, plus more.
We're excited to tell you that we just released SilverStripe version 2.4! This is a major new release and an important milestone for the SilverStripe community, the open source project, and our company.
SilverStripe 2.4 is the culmination of over a year's worth of development. We fixed 391 tickets and had over 1,400 changelog entries. A large number of the patches that went into 2.4 have come from you, the community, and we're especially happy that there's been increasing community involvement.
This week, the website and intranet managers for over one hundred of America's large companies, universities, and government agencies are meeting in Philadelphia at the annual Janus Boye Conference.
By and large, the types of organisations represented at the conference are yet to progress to modern, open source CMS platforms, so we're excited to feature at the conference for the second year and show them what exists in the market.
Each week we're interviewing someone who has made a major contribution to our upcoming release of SilverStripe CMS, version 2.4.
This week we're discussing a hotly desired feature, hierarchical URLs, with the person behind the feature, Andrew Short. Based in Australia, Andrew is a member of our open source community who has worked with SilverStripe CMS for several years. The feature Andrew is discussing here is also colloquially known as "nested URLs."
We're excited to say we're extremely close to releasing a stable version of SilverStripe 2.4.
A month ago we released Release Candidate 1. Thanks to community feedback and continued testing, we're issuing an update today, SilverStripe 2.4 Release Candidate 2. A huge thank you to everyone who has taken the time to download and test this release and file bug reports.
In the countdown to the SilverStripe CMS 2.4 release, we'll be running some interviews with people involved in key aspects of our upcoming release.
First up is Sean Harvey, one of SilverStripe's early employees. Sean has been working for more than a year now on various improvements in SilverStripe to do with the Microsoft platform, and answers some questions put to him below:
SilverStripe is an open source software written in PHP. Why is it important to support Microsoft technology?