SilverStripe 3.0 will focus on improving core features and the user experience. It will separate the CMS from the framework and move to a more flexible object-relational mapper and templating system. Development will be community-driven using Git and follow an agile process with early alpha and beta releases targeted for mid-2011. Backwards compatibility is a priority but some deprecated features may be removed.

1. SilverStripe 3.0 Roadmap SilverStripe UK Meetup, London 3rd March 2011 Jamie Neil <jamie@gpmd.co.uk>

3. Vision for 3.0

4. Development process

5. Highlights

6. Timeline

7. Questions

8. Beer

11. Modularisation

12. Caching

20. Allows decentralised development

24. Separating CMS and Sapphire

25. jQuery UI

26. Flexible templating

27. Performance

28. Configuration

29. Data integrity

30. Module management

31. Versioned assets

32. Data grid

33. Social * Many things still being actively discussed, so all subject to changes

37. Non SQL data sources

38. MySQL to remain core due to module management

41. ModelAdmin?

42. Similar to Django

45. Will make custom themes easier to implement

51. Inclusion

52. $Up

56. Reduced coupling

57. Easier testing

60. }

68. Hard for users and developers to use

73. Permissions model

74. Command line tools (sake)

76. Device independence

77. Better REST api

87. Planning: http://open.silverstripe.org/wiki/planning

88. Mailing List: http://groups.google.com/group/silverstripe-dev

89. Designs: https://github.com/silverstripe/silverstripe-design