Presentation for Web Directions South 2008. Taking a look at the dilemma of choosing between Custom Build applications and using your CMS.

1. Custom V CMS
(don’t take sides)

2. I am Diana Mounter
Hi

3. I work for the
Local Government and
Shires Associations of NSW
(LGSA for short)
Hi

4. Co-founded the
Local Government
Web Network
(visit lgwebnetwork.org)
Hi
(Very proud and excited about it)

5. I do
Project Management
Graphic & Web Design
Front-end development
(and... IA, system design, support CMS
bla bla bla...)
Hi

6. CMS
(Content Management System)

7. Custom
Custom building a
web application

8. Custom V CMS
(don’t take sides)

9. Custom V CMS

10. New Job
First big project:
Re-development of
corporate website!!!
(and all the other little
“mini” sites)
My
Story

12. we must streamline

13. Content
Management
Systems
the solution to your problems!

14. Not technical
Multiple authors
Authors can’t change styles
Review paths
Can add on modules and
customise to your needs

15. It worked!

16. It worked... for a while

17. The side effects of success

18. The people wanted MORE!
online
payments image maps
forums videos blogs
blogs, video, forums, image maps etc.

19. Before I knew it...

20. Before I knew it... I’d created a monster!

21. The side effects of stretching your CMS
• Makes upgrading more complicated
• Can increase maintenance costs
• More things to break = more things to fix
• You might have to compromise on functionality

22. Pushing the CMS to perform against its core
functionality wasn’t a good idea.

23. Pushing the CMS to perform against its core
functionality wasn’t a good idea.
Leave the CMS doing what its meant to:

24. Pushing the CMS to perform against its core
functionality wasn’t a good idea.
Leave the CMS doing what its meant to:
Content Management

25. Now what?

26. Hmmm...
what about a Custom Build?

27. the right project

29. What I thought about Custom builds...

30. Oooh excitement!

31. agile development
Oooh excitement!
Ruby on Rails

32. build what you want
agile development
Oooh excitement!
Ruby on Rails
flexibility

33. build what you want
cool stuff
agile development
Oooh excitement!
Ruby on Rails
flexibility
creativity

34. So, why not the CMS?

35. These were our aims for the site:
1. Easy to use Forms
2. Increase number applications
3. Make it a place to share
4. Build an archive of projects
5. Reflect the creativity of the projects

36. 1. Forms :(

37. FORMS

38. [screen-shot]

40. 2. More applications

41. [screen-shots]

42. [screen-shots]

43. 3. A place to share

44. Blog
Membe rs Forum

45. 4. Build an archive

47. 5. Reflect creativity

49. [screen-shot]

50. Why was this important?

51. [video]
Video from Cultural Awards website.
Wagga Wagga City Council
From All Four Corners – Celebrating Diversity: Mitsue
Stockley - Love Lives On
http://culturalawards2008.lgsa.org.au/projects/14-from-all-
four-corners---celebrating-diversity/videos/3

52. User generated content made the site richer

53. User generated content made the site richer
I’m glad we didn’t compromise

54. So, why not the CMS?

55. The CMS couldn’t do...
“Fun” forms
Blogs and forums
Video or Audio
User Generated Content
RSS feeds

56. If we had used the CMS:
One BIG online form (or PDF!)
No blogs or forums, or linked to external site
Links to video and audio
No user Generated Content
(unless we did a lot of cutting and pasting)
No RSS feeds

57. Or we would have had to
customise the CMS
(again)

58. “This is typical! They do these
cheap jobs to save money, but
then they end up spending
more money fixing all the
things that break”
- the plumber

59. ...don’t forget your CMS

60. XML Feeds
lots of links

61. XML Feeds
lots of links
PRESS RELEASES!
branding
event photos

62. XML Feeds
lots of links
PRESS RELEASES!
branding
event photos RSS Feeds
Email subscriptions
Twitter

63. Branding and Design

64. Branding and Design
User Experience

65. Branding and Design
User Experience
Where is your traffic coming from?
What are the users expectations?
Should it be the same or different?
Is it a website or an application?
If application - different expectations.

66. If it’s all new, make it:
intuitive
simple
provide instructions
show examples

67. Tips to help you make
the choice between
CMS
and
Custom

68. 1. Learn the limits of your CMS

69. 1. Learn the limits of your CMS
2. Have clearly defined goals

70. 1. Learn the limits of your CMS
2. Have clearly defined goals
3. Don’t take on to much

71. 3. Don’t take on to much

72. 1. Learn the limits of your CMS
2. Have clearly defined goals
3. Don’t take on to much
4. Get HELP from an expert if you’re not

73. 1. Learn the limits of your CMS
2. Have clearly defined goals
3. Don’t take on to much
4. Get HELP from an expert if you’re not
(make sure they are unbiased)

74. Choose the option that:
The platform supports
Best matches the goals
That you can support
Consider what the “expert” recommends

75. If you do decide to
pack up your bags...
and go Custom

76. Choose the right people for the job!

77. (that probably isn’t
your CMS vendors)

78. (that probably isn’t
your CMS vendors)
Sorry!

79. Give your developers:

80. Give your developers:
• Requirements (not tech spec)

81. Give your developers:
• Requirements (not tech spec)
• Freedom (they are the experts)

82. Give your developers:
• Requirements (not tech spec)
• Freedom (they are the experts)
• and Accountability.

83. and don’t forget to create links with your
CMS based sites.

84. Custom?

85. (tell him its a trial)

86. Custom V CMS
you don’t need to take sides

87. Leave the door open to
Custom builds

88. Leave your CMS doing what its good at

89. then maybe you’ll find Zen

90. Thanks!

91. Questions?