1 / 23

Tips from Implementing Commonspot

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?

luana
Télécharger la présentation

Tips from Implementing Commonspot

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Tips from Implementing Commonspot

  2. Today’s Speakers John Fendrick • President, Woodbourne Solutions • Fendrick@woodbournesolutions.com Kent Lynch • Sr. Associate, Woodbourne Solutions • klynch@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. Create Page

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

  10. 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.

  11. 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

  12. Look & Feel • Out of the box: www.paperthin.com

  13. Page Templates • Customize look and feel in single location • Security

  14. Subsites • Subsites Segregate Content • Show on Breadcrumb • Template Variables • ws_site=OAM

  15. 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

  16. 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

  17. 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

  18. Page Indexes • No more coding list pages • Automatic • Filter based upon Permissions • Customization

  19. 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)

  20. Questions? Thank You

More Related