Boldly going where others fear to tread... Andy Savin Web Services - - PowerPoint PPT Presentation

▶

boldly going where others fear to tread

Boldly going where others fear to tread... Andy Savin Web Services - - PowerPoint PPT Presentation

Sep 02, 2023 474 likes •764 views

Boldly going where others fear to tread... Andy Savin Web Services University of Bath A.D.Savin@bath.ac.uk Overview Why we needed a CMS Summary of CMS selection process Helpful discoveries Issues we faced Modifications we

slide-1

SLIDE 1

Boldly going where others fear to tread...

Andy Savin Web Services University of Bath A.D.Savin@bath.ac.uk

slide-2

SLIDE 2

Overview

 Why we needed a CMS  Summary of CMS selection process  Helpful discoveries  Issues we faced  Modifications we have made  How staff have adapted to using it  Our plans for the future

Andy Savin Web Services University of Bath A.D.Savin@bath.ac.uk

slide-3

SLIDE 3

Why did we need a CMS?

 Information bottleneck

Andy Savin Web Services University of Bath A.D.Savin@bath.ac.uk

slide-4

SLIDE 4

Why did we need a CMS?

 Information bottleneck  Inconsistent page style

Andy Savin Web Services University of Bath A.D.Savin@bath.ac.uk

slide-5

SLIDE 5

Why did we need a CMS?

 Information bottleneck  Inconsistent page style  Different levels of expertise

Andy Savin Web Services University of Bath A.D.Savin@bath.ac.uk

slide-6

SLIDE 6

Why did we need a CMS?

 Information bottleneck  Inconsistent page style  Different levels of expertise  Content repetition and inaccuracy

Andy Savin Web Services University of Bath A.D.Savin@bath.ac.uk

slide-7

SLIDE 7

Why did we need a CMS?

 Information bottleneck  Inconsistent page style  Different levels of expertise  Content repetition and inaccuracy  Hard to maintain (Dreamweaver templates)

Andy Savin Web Services University of Bath A.D.Savin@bath.ac.uk

slide-8

SLIDE 8

Summary of CMS selection process

 Started with a huge list of requirements

Andy Savin Web Services University of Bath A.D.Savin@bath.ac.uk

slide-9

SLIDE 9

Summary of CMS selection process

 Started with a huge list of requirements  Looked at several commercial products

Andy Savin Web Services University of Bath A.D.Savin@bath.ac.uk

slide-10

SLIDE 10

Summary of CMS selection process

 Started with a huge list of requirements  Looked at several commercial products  Put case forward for open source

Andy Savin Web Services University of Bath A.D.Savin@bath.ac.uk

slide-11

SLIDE 11

Summary of CMS selection process

 Started with a huge list of requirements  Looked at several commercial products  Put case forward for open source  Refined requirements by removing less important

Andy Savin Web Services University of Bath A.D.Savin@bath.ac.uk

slide-12

SLIDE 12

Summary of CMS selection process

 Started with a huge list of requirements  Looked at several commercial products  Put case forward for open source  Refined requirements by removing less important  Finally chose OpenCms

Better user interface
Most configurable and extensible
Java

Andy Savin Web Services University of Bath A.D.Savin@bath.ac.uk

slide-13

SLIDE 13

Helpful discoveries

 Templating and properties

Andy Savin Web Services University of Bath A.D.Savin@bath.ac.uk

slide-14

SLIDE 14

Helpful discoveries

 Ability to have dynamic CSS

Andy Savin Web Services University of Bath A.D.Savin@bath.ac.uk

slide-15

SLIDE 15

Helpful discoveries

 Templating and properties  Ability to have dynamic CSS  User specific rich-text editor configuration

Andy Savin Web Services University of Bath A.D.Savin@bath.ac.uk

slide-16

SLIDE 16

Helpful discoveries

 Templating and properties  Ability to have dynamic CSS  User specific rich-text editor configuration  XML content types

Andy Savin Web Services University of Bath A.D.Savin@bath.ac.uk

slide-17

SLIDE 17

Helpful discoveries

 Templating and properties  Ability to have dynamic CSS  User specific rich-text editor configuration  XML content types  OCEE package allows LDAP integration

Andy Savin Web Services University of Bath A.D.Savin@bath.ac.uk

slide-18

SLIDE 18

Issues we have faced

 Database storage space  Large amount of content not in the CMS

Andy Savin Web Services University of Bath A.D.Savin@bath.ac.uk

slide-19

SLIDE 19

Modifications we have made

 Page macros

 Contact information  Research profiles and publications  Table contents  News  Content from other pages

Andy Savin Web Services University of Bath A.D.Savin@bath.ac.uk

slide-20

SLIDE 20

Modifications we have made

 Page macros

{{bathPeople:personlist=csmads,ccsajm:display=list}}

Andy Savin Web Services University of Bath A.D.Savin@bath.ac.uk

slide-21

SLIDE 21

Modifications we have made

 On demand static export rules

Andy Savin Web Services University of Bath A.D.Savin@bath.ac.uk

slide-22

SLIDE 22

Modifications we have made

 Breadcrumbs

Andy Savin Web Services University of Bath A.D.Savin@bath.ac.uk

slide-23

SLIDE 23

Modifications we have made

 Integration with applications we develop

Andy Savin Web Services University of Bath A.D.Savin@bath.ac.uk

slide-24

SLIDE 24

Modifications we have made

 Admin tools

 Unlock  Publish  Find and Replace

Andy Savin Web Services University of Bath A.D.Savin@bath.ac.uk

slide-25

SLIDE 25

How staff have adapted to using it

 Generally good feedback  Allows departments to work in their own way  Some fear of losing the ability to edit HTML  Initial aversion to a new system quickly overcome  Training easier and quicker than with Dreamweaver

Andy Savin Web Services University of Bath A.D.Savin@bath.ac.uk

slide-26

SLIDE 26

The CMS is simple and straightforward to use, making it easy for adding new information and links to existing web pages. I would recommend the CMS for anyone who is setting up a new website, particularly if you only have very little previous experience in designing websites.

How staff have adapted to using it

“

Andy Savin Web Services University of Bath A.D.Savin@bath.ac.uk

”

slide-27

SLIDE 27

Our plans for the future

 As many sites in the CMS as possible  More dynamic content  More integration  Releasing more modules back to the community

Andy Savin Web Services University of Bath A.D.Savin@bath.ac.uk

slide-28

SLIDE 28

Questions

Andy Savin Web Services University of Bath A.D.Savin@bath.ac.uk