Tips from Implementing Commonspot

1
Tips from Implementing Commonspot
2
Todays Speakers

• John Fendrick
• President, Woodbourne Solutions
• Fendrick_at_woodbournesolutions.com
• Kent Lynch
• Sr. Associate, Woodbourne Solutions
• klynch_at_woodbournesolutions.com

3
Why Commonspot?

• Content Management Solution
• Why not Spectra?
• Leverages Cold Fusion
• Simple Web Publishing
• Template-driven Web Pages
• Access-based Roles Privileges
• Approval Workflow

4
Architecture

5
Why Commonspot?

• Dynamic Self-Updating Page Indexes
• Scheduled Personalized Content
• Verity Search
• Extend with Cold Fusion code
• Customization with Renderers

6
Why Commonspot?

• Keywords
• Extended with Browser
• Dynamic Page Generation
• Page Caching
• Distributed Administration Security
• By Site/Subsite

7
What did NICHD want?

• Use Intranet as Lever for Organizational Change
• Mirror Organizational Hierarchy
• Institute/Center/Branch
• Common Look Feel
• Low Maintenance/Easy to Use
• Reuse Existing CF code
• Breadcrumb
• Custom Search

8

9

• Create Page

10
CF Application

• Standard Parts of CF Application
• Application.cfm
• Header.cfm
• Body
• Footer.cfm

11
Variables Scope

• If you need it Look for it first.
• CommonSpot has an extensive amount of data
  available in memory.
• Show scope dumps
• Customizing Application/Session/Request scopes
• custom-application.cfm
• Avoid variable collision create a custom
  structure
• Code sample
• Custom-application.cfm
• If newly created requires a service restart
• Non-hierarchical.

12
Custom CF Code

• The 3 Ws
• What to code
• Code samples (old vs. new)
• Where to code
• customcf directory
• How to integrate into CommonSpot
• slide

13
Look Feel

• Out of the box www.paperthin.com

14
Page Templates

• Customize look and feel in single location
• Security

15

16
Subsites

• Subsites Segregate Content
• Show on Breadcrumb
• Template Variables
• ws_siteOAM

17
Customizing Base Template

• How to edit code
• templates/template-basepage.cfm
• show code
• ct-render-named-element
• acts as a container for custom code
• all other code is cached
• Go to commonspot and edit base template
• Only have to do this once.
• Dropping in custom cold fusion code like before.
• All templates across all subsites will inherit
  this custom look

18
Template Variables

• Needed a way to define multi sub-directories as a
  single subsite
• Solution template variables
• Exist on a sub-site level
• Defined in backend
• namevalue pairs
• Structured Scope
• Request.subsite.templatevariables
• subsite dump.
• Code
• get_site.cfm
• page_jumper.cfm

19
Metadata

• Additional Data for Page/Link/etc
• Very Useful
• Create/Define on various levels
• Provides a simple UI for non-technical endusers
• Values set at a page level
• Scope
• Request.Metadata

20
(No Transcript)
21
Page Indexes

• No more coding list pages
• Automatic
• Filter based upon Permissions
• Customization

22
Custom Renderer

• Where to code (../renderhandlers)
• How to register / Slide
• How it works
• CommonSpot allows access to ElementInfo
  structure.
• We can modify and pass back OR
• We can intercept and display ourselves.
• ElementInfo structure
• Code (quick-link)

23

• Questions?
• Thank You