Smart Cascade Server Implementations & Strategies

1. Smart Cascade ServerImplementations & Strategies 2009 Cascade Server User’s Conference Justin Klingman, Manager, Web Design & Content Management Beacon Technologies, Inc. September 28, 2009 2009 Cascade Server User's Conference

2. Introduction • Who am I? • Beacon Technologies, Inc. • Automate, Grow, and Showcase Your Business • Cascade Server Consultation, Development, & Hosting • Custom Software Development, Search Engine Marketing, Web Design, Creative Media, Hosting 2009 Cascade Server User's Conference

3. Introduction • My Cascade Server World • Purchased in April 2005 as “PublishXML” • Used as a Software as a Service (SaaS) • 27 customers, 48 sites, 77 users • 2-system architecture for optimal performance • 11 managed instances • Official partner of Hannon Hill • Participate on the Product Advisory Council • Conduct end-user training 2009 Cascade Server User's Conference

4. Introduction • Session geared towards both end users and managers • Tips & tricks to smartly implement, manage and use Cascade Server • Smart Implementations • Integration with Dynamic Applications • Managing Search Engine Marketing Efforts • Controlling Flash Applications • Documentation and Training End Users 2009 Cascade Server User's Conference

5. Smart Implementations 2009 Cascade Server User's Conference

6. Smart Implementations • “Plan & Think Ahead” • What is your ultimate Web strategy? • All sites share common template • Sites have individual template • Flexibility for each department • “How can we implement Cascade Server to grow with us?” 2009 Cascade Server User's Conference

7. Smart ImplementationsTemplates • It’s tempting to create a new template for every different page look & layout • Consolidate templates • Advantages: • Less to keep up with • Centralize development efforts • Quicker, easier redesign 2009 Cascade Server User's Conference

8. Smart ImplementationsTemplates • Ideas for consolidating templates • Keep minimal HTML in templates • Only have structure-level HTML • Keep regions of HTML in blocks & formats and use like SSI • Use multiple Configuration Sets instead 2009 Cascade Server User's Conference

9. Smart ImplementationsTemplates • Use CSS for minor layout alterations • Example: 2 different content layouts: • 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 format that calls CSS file • Apply appropriate format to page using Configuration Sets • Set up Asset Factory for each Configuration Set 2009 Cascade Server User's Conference

10. Smart ImplementationsData Definitions • Key: Think long-term! • Always use, even if just one WYSIWYG editor region • Can add to Data Definition functionality • If not used, may have to apply Data Definitions to 100s of pages in the future • Try not to use one Data Definition for multiple applications 2009 Cascade Server User's Conference

11. Smart ImplementationsMetadata Sets • Use unique Metadata Sets per site • Just like with Data Definitions, thinklong-term • Consider using separate Metadata Sets for Pages, Files, Folders, External Links • Create individual Asset Factories for each type of asset per site 2009 Cascade Server User's Conference

12. Smart ImplementationsIndex Blocks • When not used properly, can hurt performance • Use same blocks in different regions with similar indexing needs • Only index what you need 2009 Cascade Server User's Conference

13. Integration withDynamic Applications 2009 Cascade Server User's Conference

14. Integration withDynamic Applications • WYSIWYG editor doesn’t play nice with scripting languages without special code • Most scripting languages can’t be run inside Cascade (exception: JavaScript) 2009 Cascade Server User's Conference

15. Integration withDynamic Applications • 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 2009 Cascade Server User's Conference

16. Integration withDynamic Applications • Adding SSI below the content region • Create include files outside Cascade • Create a format for each include file • Add a template region just below DEFAULT • Used to attach SSI format to page • Allows end user to maintain introductory content • Attach appropriate format • When published, application will be displayed 2009 Cascade Server User's Conference

17. Integration withDynamic Applications • 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 2009 Cascade Server User's Conference

18. Integration withDynamic Applications • End users insert SSI into WYSIWYG • Use [system-view] tags & CSS to create 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:internal] tags show in editor • Module can accidently be deleted 2009 Cascade Server User's Conference

19. Integration withDynamic Applications • 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 easily be deleted 2009 Cascade Server User's Conference

20. Managing Search Engine Marketing Efforts 2009 Cascade Server User's Conference

21. Managing Search Engine Marketing Efforts • One of Cascade’s great benefits: producing search engine-friendly sites • Set up SEM template regions • Include 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. 2009 Cascade Server User's Conference

22. ControllingFlash Applications 2009 Cascade Server User's Conference

23. ControllingFlash Applications • Flash is very popular, but difficult to maintain • The Challenge: Empower end users to maintain Flash apps’ content & imagery, 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 2009 Cascade Server User's Conference

24. ControllingFlash 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 2009 Cascade Server User's Conference

25. Documentation andTraining for End Users 2009 Cascade Server User's Conference

26. Documentation andTraining for End Users • Create your own user’s manual • Hannon Hill Knowledge Base 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 2009 Cascade Server User's Conference

27. Documentation andTraining for End Users • Training Tips • Walk through the entire manual using Cascade pages they’ll use • If possible, conduct training in-person • Slow down! 2009 Cascade Server User's Conference

28. Questions? My Contact Information: Justin Klingman Beacon Technologies, Inc. http://www.beacontechnologies.com/ 336.232.5685 | jklingman@beacontechnologies.com 2009 Cascade Server User's Conference