custom v cms

Post on 05-Dec-2014

6.881 Views

Category:

Technology

3 Downloads

Preview:

Click to see full reader

DESCRIPTION

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

TRANSCRIPT

Custom V CMS

(don’t take sides)

Hi

I am Diana Mounter

Hi

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

Hi

Co-founded theLocal Government Web Network(visit lgwebnetwork.org)

(Very proud and excited about it)

Hi

I do

Project ManagementGraphic & Web DesignFront-end development(and... IA, system design, support CMS bla bla bla...)

(Content Management System)

CMS

CustomCustom building a

web application

Custom V CMS

(don’t take sides)

Custom V CMS

My Story

New Job

First big project:Re-development of corporate website!!!(and all the other little “mini” sites)

we must streamline

ContentManagement

Systems

the solution to your problems!

Not technical

Multiple authors

Authors can’t change styles

Review paths

Can add on modules and customise to your needs

It worked!

It worked... for a while

The side effects of success

The people wanted MORE!

blogs, video, forums, image maps etc.blogsforums videos

image mapsonline

payments

Before I knew it...

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

• Makes upgrading more complicated

• Can increase maintenance costs

• More things to break = more things to fix

• You might have to compromise on functionality

The side effects of stretching your CMS

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

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

Leave the CMS doing what its meant to:

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

Leave the CMS doing what its meant to:Content Management

Now what?

Hmmm...what about a Custom Build?

the right project

What I thought about Custom builds...

Oooh excitement!

Oooh excitement!

Ruby on Rails

agile development

Oooh excitement!

Ruby on Rails

agile development

flexibility

build what you want

Oooh excitement!

Ruby on Rails

agile developmentcool stuff

flexibility

creativity

build what you want

So, why not the CMS?

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

1. Forms :(

FORMS

[screen-shot]

2. More applications

[screen-shots]

[screen-shots]

3. A place to share

Members Forum

Blog

4. Build an archive

5. Reflect creativity

[screen-shot]

Why was this important?

User generated content made the site richer

User generated content made the site richerI’m glad we didn’t compromise

So, why not the CMS?

The CMS couldn’t do...

“Fun” formsBlogs and forumsVideo or Audio

User Generated ContentRSS feeds

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

Or we would have had tocustomise the CMS

(again)

“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

...don’t forget your CMS

lots of linksXML Feeds

lots of linksXML Feeds

brandingPRESS RELEASES!

event photos

lots of linksXML Feeds

brandingPRESS RELEASES!

event photos RSS FeedsEmail subscriptionsTwitter

Branding and Design

Branding and DesignUser Experience

Branding and DesignUser ExperienceWhere 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.

intuitivesimpleprovide instructionsshow examples

If it’s all new, make it:

Tips to help you makethe choice between

CMSand

Custom

1. Learn the limits of your CMS

1. Learn the limits of your CMS2. Have clearly defined goals

1. Learn the limits of your CMS2. Have clearly defined goals3. Don’t take on to much

3. Don’t take on to much

1. Learn the limits of your CMS2. Have clearly defined goals3. Don’t take on to much4. Get HELP from an expert if you’re not

1. Learn the limits of your CMS2. Have clearly defined goals3. Don’t take on to much4. Get HELP from an expert if you’re not

(make sure they are unbiased)

Choose the option that:The platform supportsBest matches the goalsThat you can support

Consider what the “expert” recommends

If you do decide to pack up your bags...

and go Custom

Choose the right people for the job!

(that probably isn’t your CMS vendors)

(that probably isn’t your CMS vendors)

Sorry!

Give your developers:

Give your developers:

• Requirements (not tech spec)

Give your developers:

• Requirements (not tech spec)

• Freedom (they are the experts)

Give your developers:

• Requirements (not tech spec)

• Freedom (they are the experts)

• and Accountability.

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

Custom?

(tell him its a trial)

you don’t need to take sides

Custom V CMS

Leave the door open to Custom builds

Leave your CMS doing what its good at

then maybe you’ll find Zen

Thanks!

Questions?

top related