CMSMS: Past and Future. Talk given by Ted Kulp.

1. CMSMS: Past and Future
26 Sept. 2009
Ted Kulp, Shift Refresh Inc.

2. Who am I?
• 10 years development
experience
• 12 years in Open Source
• Creator of CMSMS (2004)
• Creator of Silk Framework (2008)
• <plug>Started Shift Refresh, Inc., professional
support and services (2008)</plug>

3. A Brief History of Time
(in relation to CMSMS)
2004-2009 and Beyond

5. First commit!

6. The original default site

7. Some things never change

9. 0.2 - 05 Jul 2004
Content Reordering

10. 0.2 - 05 Jul 2004
Content Reordering
0.4 - 10 Aug 2004
Module API

11. 0.2 - 05 Jul 2004
Content Reordering
0.4 - 10 Aug 2004
Module API
0.5 - 22 Aug 2004
Page Aliases

12. 0.6 - 01 Sep 2004
0.2 - 05 Jul 2004 User Defined Tags
Content Reordering
0.4 - 10 Aug 2004
Module API
0.5 - 22 Aug 2004
Page Aliases

13. 0.6 - 01 Sep 2004
0.2 - 05 Jul 2004 User Defined Tags
Content Reordering
0.10 - 05 Jul 2005 0.4 - 10 Aug 2004
Multiple Content Blocks Module API
0.5 - 22 Aug 2004
Page Aliases

14. 0.6 - 01 Sep 2004
0.2 - 05 Jul 2004 User Defined Tags
Content Reordering
0.10 - 05 Jul 2005 0.4 - 10 Aug 2004
Multiple Content Blocks Module API
0.5 - 22 Aug 2004
Page Aliases
0.13 - 18 May 2006
Pretty URLs

15. 0.6 - 01 Sep 2004
0.2 - 05 Jul 2004 User Defined Tags
Content Reordering
0.10 - 05 Jul 2005 0.4 - 10 Aug 2004
Multiple Content Blocks Module API
1.0!!! - 10 Sep 2006
Module Manager
0.5 - 22 Aug 2004
Page Aliases
0.13 - 18 May 2006
Pretty URLs

16. Why is it called
“Simple”?

17. What’s Next?

18. Why 2.0 didn’t happen
• Overly ambitious for one release
• Relied on a php version that was still too
new
• Not an issue anymore
• Too self controlling, which caused:
• Lack of involvement from the other devs

19. And this means what...?

20. Revised Roadmap
• 2.0 - Q1 2010
• PHP 5.2
• Autoloader
• jQuery w/ UI and integrated AJAX
• ORM
• Module API modifications (using ORM for objects)
• Module API smarty tags (Less php, more smarty in your modules)
• Centralized module templates
• Drag/Drop page admin
• MicroTiny WYSIWYG standard

21. Revised Roadmap
• 2.1
• Tree based page permissions
• Complex content types (think: CCK)
• More separation of pages and content
• Admin panel smartification (Mostly themes,
some admin pages as well)
• FTP Based module installer and upgrade
routines

22. Revised Roadmap
• 2.2
• Multi language
• Support for multiple content per block
• Allows for a default language for overriding when
a secondary language’s content box isn’t filled in
• Allows for alternate page titles and menu text
• API methods to allow modules to hook in their
text as well

23. What’s Missing?
• Multisite
• Too many ways to do this, some of which would make for a coding
nightmare
• Most people want it (we think) for upgrading sites quickly -- In-admin
upgrades (in 2.1) solves this issue
• Versioning
• Have some ideas on how to do this, but it would require some real
fancy interface design. Might work better as a module
• Would like to have some kind of API for modules to use, which
would require a lot of generic serialization handling
• Might work better after the complex content types are up and
running

24. What’s Missing?
• Front End User Integration
• This will happen, we’re just not sure where it fits yet.
• The main issue is that FEU adds SO much functionality, though
we’d want our users to be more generic. This would require
add-on modules to tack on the existing FEU functions.
• Silk Framework
• Going to require PHP 5.3
• Going to require more hacking up of the admin panel to write
it as a “Silk App”
• Will happen, but post 2.2

25. Thank you!
Questions?