Tips & Tricks for End Users

Tips & Tricks for End Users

2008 Cascade Server User’s Conference

Justin Klingman, Manager, Web Design & Content Management

Beacon Technologies, Inc.

September 22, 2008

09/22/2008 2008 Cascade Server User's Conference 1

Introduction

Who am I?


– 10 th -year anniversary

– Automate, Grow, and Showcase Your

Business

– Custom Software Development, Search

Engine Marketing, Web Design & Content

Management


Introduction

My Cascade Server World

– Purchased in April 2005 as “PublishXML”

– Used as a Software as a Service (SaaS)

– 26 customers, 65 sites, 60 total users

– 2-system architecture for performance

– 7 separate instances

– Partner with Hannon Hill

– Participate on the Product Advisory Council

– Conduct end-user training


Introduction

Session geared towards both end users and managers

Focusing on tips & tricks to effectively implement, manage and use Cascade

Server

Let’s make this interactive…feel free to interrupt me!


Introduction

What we’ll cover:

– Smart Implementations

– Repurposing Content

– Using Data Definitions

– Integrating Scripting Languages

– Managing Search Engine Marketing Efforts

– Controlling Flash Applications

– Documentation and Training End Users


Smart Implementations

“Plan and Think Ahead”



Template Set-up

It’s tempting to create a new template for every different page look & layout

Try to keep a minimal number of templates

Advantages:

– Less to keep up with

– Quicker, easier redesign

What are some ideas for consolidating the use of templates?

09/22/2008 7 2008 Cascade Server User's Conference


Template Set-up

Use CSS for minor layout alterations

– Example:

2 different content layouts for a site:

– Page w/ Right Column

– Page w/o Right Column

– How do they all run off of one template?

Create additional CSS file that overrides main site CSS

Create XSL that calls CSS file

Apply appropriate XSL to page using Configuration Sets

Set up Asset Factory for each Configuration Set



Data Definitions

Key: Think long-term!

– “How can we design this so that it can be easily modified in the future?”

Always use, even if just one WYSIWYG editor region

– Can expand Data Definition to add functionality

– If not used, may have to edit 100s of pages to apply a Data Definition in the future



Data Definitions

Try not to use one Data Definition for multiple applications

Can be applied to each page using

Content Types in 5.5.2



Metadata Sets

Always use unique Metadata Set per site

Can be applied to each page using

Content Types in 5.5.2

Just like with Data Definitions, think about expansion

Consider using separate Metadata Sets for Pages, Files, Folders, External Links

Create individual Asset Factories for each type of asset per site


Repurposing Content


Repurposing Content

Gives your site users multiple formats

Publish your site in the following formats:

– Print-friendly

– Lite HTML / Handheld Devices

– PDF, Word Documents

– XML / RSS

– Multiple Languages

Repurpose content across multiple pages


Using Data Definitions


Using Data Definitions

Use Target CSS to control the following attributes of your WYSIWYG editor:

– Font family / size / color

– Background color

– Width of the content region (Firefox only)


Integrating

Scripting Languages


Integrating Scripting Languages

WYSIWYG editor doesn’t play nice with scripting languages without special code

Most scripting languages can’t be run inside Cascade (exception: some

JavaScript)

How do we get scripting code into

Cascade Server?



Use Server-Side Includes (SSI)

– Allows developers full control over their code without using Cascade

– Protects code from modification, deletion



Adding SSI below the content region

– Create include files outside Cascade

– Create a stylesheet for each include file

– Add a template region just below DEFAULT

Used to attach SSI stylesheet to page

Allows end user to maintain introductory content

– Attach appropriate stylesheet

– When published, application will be displayed



Adding SSI Inline

– Insert SSI within the body of content, floating left or right, in between paragraphs

– Allows more flexibility for end user to position applications within content region

– Allows end user ability to add their own applications



– End users insert an HTML module into

WYSIWYG editor that contains SSI

Use CSS to create identifiable box

Use inline CSS to allow end user to specify width/height of area, alignment properties

[system-view:internal] tags will prevent internal

CSS code from being published

– Disadvantages:

[system-view] tags show in editor

Module can accidently be deleted very easily



Put scripting code in XSL

Add scripting code directly into editor without SSI

– Use HTML view

– <!--#START-CODE and #END-CODE 

– Disadvantage: code cannot be seen within the editor, and can be easily deleted


Managing Search Engine

Marketing Efforts



Marketing Efforts

One of Cascade’s great benefits: producing search engine-friendly sites

Controlling the <title> tag using Metadata Set

– Past: Search engines relied heavily on “keyword” and

“description” metadata fields

– Present: Still uses “description”, but now key in on <title> text

– SEM team wanted to control <title> per page

– Added custom metadata field called “SEO Title”

Added template region within <title> tag

XML and XSL display standard <title> (e.g. “Company > Services”)

SEM team enters different title (e.g. “Web Design | eCommerce

Website Design”) to override standard title



Marketing Efforts

Set up SEM template regions

– Include Google Analytics scripts on each page

– Allows SEM analysts to add code to a certain page, such as a conversion tracking script or other metadata

Use Data Definitions

– Add SEM-specific fields for key phrase mgmt.

Set up a separate SEM page type

– Create key phrase-rich landing pages


Cascade and

Flash Applications


Cascade and Flash Applications

Flash becoming more popular, but difficult to maintain

Beacon’s challenge: Empower end users to maintain apps’ content, imagery, etc. using Cascade

Solution:

– Develop Flash app that reads an XML file

– Develop Data Definitions for content entry

– Publish content as XML file for Flash to read


Cascade and Flash Applications

All-Flash Site:

– Site has two versions: Flash, and non-Flash / non-JavaScript version for search engines

– Build normal site in Cascade

– Repurpose content:

Full HTML (non-Flash / non-JavaScript version)

HTML from the WYSIWYG editor (Flash version)

– HTML is read by Flash player, creating the page

– Navigation published as XML, read by Flash to build menu system


Documentation and

Training for End Users


Documentation and


Create your own user’s manual

– Hannon Hill Knowledge Base is great, but too much information for an end user

– Nobody knows more about your implementation than you

– Lay out like a tutorial and use screenshots

– Keep it up-to-date with version releases

– Takes time & effort, but end users will thank you!


Documentation and


Training Tips

– Walk through the entire manual using pages they’ll use

– No individual workstations (my opinion)

– If possible, conduct training in-person

– Slow down!


Questions?

09/22/2008

My Contact Information:

Justin Klingman


http://www.beacontechnologies.com/

336.232.5685 jklingman@beacontechnologies.com

2008 Cascade Server User's Conference 32

Tips & Tricks for End Users

Tips & Tricks for End Users

Smart Implementations

“Plan and Think Ahead”

Repurposing Content

Using Data Definitions

Integrating

Scripting Languages

Managing Search Engine

Marketing Efforts

Cascade and

Flash Applications

Documentation and

Training for End Users

Questions?

Related documents

Products

Support

Tips & Tricks for End Users