230 likes | 346 Views
Tips from Implementing Commonspot. Today’s Speakers. John Fendrick President, Woodbourne Solutions Fendrick@woodbournesolutions.com Kent Lynch Sr. Associate, Woodbourne Solutions klynch@woodbournesolutions.com. Why Commonspot?. Content Management Solution Why not Spectra?
E N D
Today’s Speakers John Fendrick • President, Woodbourne Solutions • Fendrick@woodbournesolutions.com Kent Lynch • Sr. Associate, Woodbourne Solutions • klynch@woodbournesolutions.com
Why Commonspot? • Content Management Solution • Why not Spectra? • Leverages Cold Fusion • Simple Web Publishing • Template-driven Web Pages • Access-based Roles & Privileges • Approval Workflow
Why Commonspot? • Dynamic Self-Updating Page Indexes • Scheduled & Personalized Content • Verity Search • Extend with Cold Fusion code • Customization with Renderers
Why Commonspot? • Keywords • Extended with Browser • Dynamic Page Generation • Page Caching • Distributed Administration & Security • By Site/Subsite
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
CF Application • Standard Parts of CF Application • Application.cfm • Header.cfm • Body • Footer.cfm
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.
Custom CF Code • The 3 W’s • What to code • Code samples (old vs. new) • Where to code • customcf directory • How to integrate into CommonSpot • slide
Look & Feel • Out of the box: www.paperthin.com
Page Templates • Customize look and feel in single location • Security
Subsites • Subsites Segregate Content • Show on Breadcrumb • Template Variables • ws_site=OAM
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
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 • “name=value” pairs • Structured Scope • Request.subsite.templatevariables • subsite dump. • Code – • get_site.cfm • page_jumper.cfm
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
Page Indexes • No more coding list pages • Automatic • Filter based upon Permissions • Customization
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)
Questions? Thank You