People should be able to use backdrop without needing to know how to create or modify a theme.
(This initiative was originally titled "Include several ready-to-use themes" but the name has been changed to allow other implementation options.)
Many potential users of Backdrop are not themselves skilled visual designers, and don’t have access to (or the resources to afford) a suitable designer. We should offer site builders the capability to create usable sites even if they lack either the technical ability to edit the HTML, PHP, CSS, JavaScript, and media elements that comprise most themes, or the design skills necessary to select visually-pleasing options. Or both! Backdrop is a content management system, we shouldn't require our users to bring to the table anything besides the content they are looking to manage.
For an initial MVP, I propose that we find or construct three or four ready-to-go themes, and either include them with the basic download, or make them a one-click install. In order to be usable by the most inexperienced user, the themes should be:
- Usable out of the box, without requiring any customization, programming, or configuration.
- Fully tested and debugged, so that the can be expected to work for a common set of defined use cases
- Limited in number, so that anybody needed to support Backdrop will know how many ready-to-go themes are available and what they are
- Fully documented, so that users know what to expect without having to explore the themes themselves.
Once again, I think WordPress does a good job with this. In WordPress, It's possible to "try on" a theme without committing to it, which I think is both cool and useful.
The PMC has voted that Theme development should not be necessary to use Backdrop CMS should be an official Backdrop initiative.
Luke (@cellear) you are it's lead, and we would love an update from you each week in the developer meeting, starting next week. If you can't make the meeting that's fine, but please drop an update here in these comments :)