Luminis Content Management Suite System Fundamentals

1
Luminis Content Management Suite System
Fundamentals

• Galway-Mayo Institute of Technology

2
House Keeping

• Schedule
• Breaks
• Lunch
• Training Materials
• Workbook -
• User Credentials
• PowerPoint

3
Objectives

• Understand the key features and functionality of
  Luminis CMS and Site Studio.
• Create and manage sites, webviews, and layouts
• Create and manage content
• Participate in workflows
• Understand Luminis CMS navigation functionality
  and create persistent navigation links
• Identify policy and process decision points
  related to the implementation of Luminis CMS

4
Luminis CMS Overview
5
What is Luminis CMS?
Luminis CMS provides the tools and environment
that enable your people to create, maintain,
re-use, and deliver timely and accurate web
content.
Luminis CMS
Consumers
Internal
Source Content
External
People
Published Content
Policies Procedures
Websites/Devices
6
SITES / Workgroups

• Assigned users may access all content contained
  within the site.
• Assigned users may include
• Content Contributors (CC)
• Content Managers (CM)
• Site Managers (SM)

7
WEBVIEW / Content Container

• Holds content
• Tells the content where it will be published
• Publishing Configuration Server where content
  will be published
• URL Server directory where content will reside

8
SITE
SHARED FOLDER
9
Product Demonstration
10
Known Issues

• Issue Multiple users performing the exact same
  action at the same time (i.e. Open, Edit, Save,
  etc.) may crash the system. As few as 8 users
  clicking on the edit button at the same time may
  crash the system.
• Workaround A few seconds between user actions
  will prevent a crash.
• Issue Show Items pull-down list of 25 and/or 50
  sometimes does not display any items.
• Workaround click on another tab or action (e.g.
  Inbox or Classic, Cancel or Breadcrumb, etc.) or
  logoff/logon.
• Issue System may time out (see your System Admin
  for info on what the time-out configuration
  setting is) do to no activity and may display a
  Severe or Timeout Error.
• Workaround Logon again.

11
Workbook Activities
12
Training URL

• http//mallum3.sct.com/lcms

13
Training Credentials
All passwords asdf
14
Section A Site Studio Overview

• Prerequisite for using Site Studio Page 5
• JRE plugin installed
• IE sp2 or Firefox 1.5
• Site Studio Navigation
• My Sites
• Inbox
• My Files
• Subscriptions
• Answer the questions on Page 8

15
Section B Site Setup

• Create a Site
• Assign User Roles
• Create Webviews

16
Content Management Steps
Site Manager
Content Manager
Create site
Content Contributor
Assign user roles
Create webview(s)
Import supporting files
Create components
Frequent Tasks
Create layout(s)
Create pages
Edit submit pages
Occasional Tasks
Approve publish pages
Set persistent navigation
17
SITES / Workgroups

• Assigned users may access all content contained
  within the site.
• Assigned users may include
• Content Contributors (CC)
• Content Managers (CM)
• Site Managers (SM)

18
Creating Sites

• Site Name Your name OR the name of your
  department
• Site Short Name An abbreviation of your Site
  Name (all lower case, no numeric characters)
• Site Default Page Expiration Leave the field
  empty
• Site Description Describe the purpose of the
  site
• Default Workflow Template Immediate Launch

19
Content Management Steps
Site Manager
Content Manager
Create site
Content Contributor
Assign user roles
Create webview(s)
Import supporting files
Create components
Frequent Tasks
Create layout(s)
Create pages
Edit submit pages
Occasional Tasks
Approve publish pages
Set persistent navigation
20
Luminis CMS Roles

• Five user roles
• Content Contributor
• Content Manager
• Site Manager
• Template Developer
• System Administrator
• User roles are managed on a site-by-site basis

21
Luminis CMS Roles Defined

• Content Contributor (CC) Responsible for
  entering and updating content and participating
  in workflows. De-centralized and non-technical.
• Content Manager (CM) Responsible for initiating
  and managing workflows. Ensures site content is
  up to date. De-centralized and non-technical.
• Site Manager (SM) Responsible for creating and
  managing sites including sub-sites, users and
  permissions. De-centralized and non-technical.
• Template Developer (TD) Responsible for
  developing XML and JSP templates to support the
  system. Centralized and technical.
• System Administrator (SA) Responsible for
  administration (jobs, publishing, etc.) of the
  Luminis CMS. Centralized and technical.

22
Permission Sets

• Approve workflow tasks
• Assign workflow tasks
• Create edit content
• Import files
• Create manage sites users
• Create manage webviews, layouts site
  navigation
• Create components
• Create templates
• Import test templates
• Manage and configure the CMS system

CM
CC
SM
TD
SA
23
Assigning Users and Role Management

• Content Contributor jhxcc
• Content Manager jhxcm
• Site Manager jhxsm

• Switch between tabs to assign users to the
  appropriate role

24
Content Management Steps
Site Manager
Content Manager
Create site
Content Contributor
Assign user roles
Create webview(s)
Import supporting files
Create components
Frequent Tasks
Create layout(s)
Create pages
Edit submit pages
Occasional Tasks
Approve publish pages
Set persistent navigation
25
WEBVIEW / Content Container

• Holds content
• Tells the content where it will be published
• Publishing Configuration Server where content
  will be published
• URL Server directory where content will reside

26
Creating Webviews

• Webview Name Site Name Public WV
• Publishing Configuration Public Website HTML
• Use the webview names from the worksheet

27
Creating Webviews continued

• Base Path Institution specific path
• Extended Path Site Short Name

28
Section C Creating Content

• Import Supporting Files
• Create a Layout Component and a Layout
• Create Pages
• Subscribe to Content
• Submit Content to Workflow

29
Content Management Steps
Site Manager
Content Manager
Create site
Content Contributor
Assign user roles
Create webview(s)
Import supporting files
Create components
Frequent Tasks
Create layout(s)
Create pages
Edit submit pages
Occasional Tasks
Approve publish pages
Set persistent navigation
30
Importing Supporting Files

• Import either a JPG or GIF image

31
Content Management Steps
Site Manager
Content Manager
Create site
Content Contributor
Assign user roles
Create webview(s)
Import supporting files
Create components
Frequent Tasks
Create layout(s)
Create pages
Edit submit pages
Occasional Tasks
Approve publish pages
Set persistent navigation
32
Components

• Components are chunks of content
• Components should be used when you want to
  publish a single chunk of content in more than
  one place

33
Creating Components

• Name jhx_component (e.g. jhx_adm_subhdr_comp)
• All other fields are optional
• use the component names on the worksheet

34
Content Management Steps
Site Manager
Content Manager
Create site
Content Contributor
Assign user roles
Create webview(s)
Import supporting files
Create components
Frequent Tasks
Create layout(s)
Create pages
Edit submit pages
Occasional Tasks
Approve publish pages
Set persistent navigation
35
Template and Layout
36
Creating Layouts

• Layout Name JHX_IM_ltSite Namegt_Layout
• Default Workflow Manager Approval or Immediate
  Launch
• Derived parent layout interior-page-ltworkflowgt-l
  ayout

37
Content Management Steps
Site Manager
Content Manager
Create site
Content Contributor
Assign user roles
Create webview(s)
Import supporting files
Create components
Frequent Tasks
Create layout(s)
Create pages
Edit submit pages
Occasional Tasks
Approve publish pages
Set persistent navigation
38
Creating Pages

• Name index
• Title JHX ltSite Namegt Home
• All other fields are optional

39
Creating Pages continued

• Page Layout Select the radio button next to the
  layout you just created
• Click Finish Edit

40
Content Management Steps
Site Manager
Content Manager
Create site
Content Contributor
Assign user roles
Create webview(s)
Import supporting files
Create components
Frequent Tasks
Create layout(s)
Create pages
Edit submit pages
Occasional Tasks
Approve publish pages
Set persistent navigation
41
Editing pages

• Web pages and components can be edited using the
  WYSIWYG editor.

42
Submit content to workflow

• Once the content is ready for publication it is
  submitted to workflow.
• The workflow is dependent on either the layout
  default workflow for web pages and the site
  default workflow for components, images, and
  imported content.

43
Subscribing to webviews and content

• Files, folders, or Webviews that you frequently
  work with can be subscribed to for quick access.
• Content that you subscribe to is available from
  the Subscription tab.
• Adding items to the Subscription tab is similar
  to setting Webpages as favorites or bookmarks in
  your Internet browser
• Lets subscribe to the GMIT webview, and the
  pages in your webview

44
Section D Using Workflow

• Assign, Act On, and Approve Workflow Tasks
• Quickflows

45
Content Management Steps
Site Manager
Content Manager
Create site
Content Contributor
Assign user roles
Create webview(s)
Import supporting files
Create components
Frequent Tasks
Create layout(s)
Create pages
Edit submit pages
Occasional Tasks
Approve publish pages
Set persistent navigation
46
Approving Content

• If you submit Manager Approval content to
  workflow the Content Manager for the site will
  receive an Approve notification in their Site
  Studio Inbox.

47
Workflow Overview

• Default Workflows
• Manager Approval
• Immediate Launch
• Pages map to the default workflow template
  defined by the layout.
• Components, images, and imported content map to
  the default workflow template defined by the
  site.

48
Initiating Workflows

• Content Managers and Site Managers can Assign
  Tasks to Content Contributors within their site.
• Content Contributors, Content Managers, and Site
  Managers can submit content to workflow.

49
Assigning a Manager Approval Task
50
Assigning a Task (CM or SM)

• Workflows are assigned from the Site
• Workflow Template Manager Approval
• Comment Optional
• Attached Documents index

51
Responding to a Task (CC)

• Click Edit
• Click Accept
• Edit the document
• Click Finish

52
Approving Submitted Content (CM)

• Click Approve
• Click Accept
• View the document
• Optional Edit the document
• Click Forward

53
Quickflows

• A Quickflow is used to request input from one or
  more individuals about content
• By sending a Quickflow you can show them the page
  so that they have a context for their
  contributions
• If a user that you are including in the Quickflow
  has permissions to edit the page then they can
  also make changes as part of the task
• When you create a Quickflow you
• select the user or users that need to respond,
• set a priority that will display with the task in
  their inbox,
• create instructions specific to the tasks and,
• set routing and approval options.

54
Section E Managing Navigation

• Set up Navigation
• Persistent Navigation
• Page to Page navigation

55
Content Management Steps
Site Manager
Content Manager
Create site
Content Contributor
Assign user roles
Create webview(s)
Import supporting files
Create components
Frequent Tasks
Create layout(s)
Create pages
Edit submit pages
Occasional Tasks
Approve publish pages
Set persistent navigation
56
Managing Persistent Navigation

• Persistent navigation is defined and managed by
  Site Managers
• Persistent navigation is defined for each webview
• Persistent navigation link types
• Childview
• Site Document
• URL

57
Managing Page-To-Page Navigation

• Page-to-page navigation is defined and managed by
  the content editors (SMs, CMs, and CCs)
• Hyperlinks in page body content created in
  WYSIWYG editor

58
Creating Persistent Navigation

• Link Name Your name
• Click Add Child View Your Webview
• Link Name Use your imagination
• Click Add Site Document Any document other
  than index in your webview
• Click Done

59
Team Activity
60
Team Activity

• Scenario You must design and build the Site
  Studio environment for a test Luminis CMS focus
  area, including
• Site(s)
• Subsites(s)
• Webview(s)
• Layout(s)
• User permissions
• Web pages
• Workflow assignments

61
Content Management Steps
Site Manager
Content Manager
Create site
Content Contributor
Assign user roles
Create webview(s)
Import supporting files
Create components
Frequent Tasks
Create layout(s)
Create pages
Edit submit pages
Occasional Tasks
Approve publish pages
Set persistent navigation
62
Getting Started Site Design

• Answer the following questions to help determine
  the best way to organize your site.
• Which site should we base our activity on?
• Users Are the same people working on all the
  content that will be contained within the site?
• Workflow Should all images, components, and
  imported content follow the same approval
  process?
• Navigation How many levels of navigation will
  the web pages require?
• Paths What URLs do you want your web pages to
  have? Do you have a standard web directory
  structure you would like to follow?

63
Site Design continued

• Q Users Are the same people working on all the
  content that will be contained within the site?
• A Yes. All content can reside within the same
  site.
• A No. Separate sites should be created for each
  group of people who will be working on common
  content.
• Q Workflow Should all images, components, and
  imported content follow the same approval
  process?
• A Same as above
• Note Review workflow templates

64
Workflow Templates

• Assign Task Content Managers and Site Managers
  may select from the list of available workflows
  for each new task.
• Site Default Workflow Template Sets the site
  default workflow for images, components, and
  imported content.
• Layout Default Workflow Sets the default
  workflow for all pages derived from that layout.

65
Site Design continued

• Q Navigation How many levels of navigation will
  the web pages require?
• A One. You will only need one webview
• A More than one. You will need a webview for
  each level of navigation you plan to create.
• Q Paths What URLs do you want your web pages to
  have?
• A All URLs will build off the main URL (e.g.,
  /hr, /hr/jobs.shtml, /hr/benefits.shtml, etc.).
  You will only need one webview.
• A All URLs will stem off the root (e.g., /hr,
  /jobs, /benefits, etc.). You will need a webview
  for each URL and/or web directory folder you plan
  to create.

66
Thank you for your participation
67
Section F Managing Luminis Portal Content

• Automated Luminis Channel Creation
• Luminis Targeted Content Channels

68
Publish Using Automated Luminis Channel Creation
(ALCC)
69
Publish to Luminis Targeted Content Channels
(LTCC)
Component managed by Student Government
Component managed by Student Services
70
Content Contributor Tasks

• Viewing content
• Subscribing to content and folders
• Importing content
• Creating and modifying web pages
• Subscribing to content and folders
• Responding to workflow tasks
• Content Contributor Summary
• Key policy and process decision points
• User needs

71
Site Manager Tasks

• Creating sites, webviews, and layouts
• Managing user permissions
• Creating components
• Creating persistent navigation
• Site Manager Summary
• Key policy and process decision points
• User needs

72
Content Manager Tasks

• Understanding default workflows and the workflow
  process
• Assigning and responding to workflow tasks
• Content Manager Summary
• Key policy and process decision points
• User needs