Welcome to the CMS Training Portfolio

Add New Weblog Entry Drafts ()

Tabs, Content Groups, Span#, and You

Tuesday, August 18, 2015

I realize that I've been more than a bit neglectful on keeping up with the CMS blog postings and so I wanted to share a few things over a few blog posts that came up this week that would probable be helpful for a lot of folks.

There's at least three different ways that tabs are implemented within the CMS, each with varying degrees of complexity.  I'll talk about the more complex variety, which offers quite a bit of flexibility but can be somewhat confusing. 

Deb Rydman and Marsha Squires were playing around with the /exchanges portion of the CMS and had some difficulty figuring out how to make callouts go away from some of the tabs.  The first attachment shows what a callout is:



Drilling down, we see that these tabs are part of a block, with data type "tabs_with_column_blocks with id".  Here's the data for this particular tab:



For this particular data definition, semantically, tabs contain 1 or more tab content groups, and each tab content group contains one or more block groups (listed as "A Block Group").   Each "A Block Group" within a "Tab Content Group" allows you to link to existing content, such as the callout of Arthur.  In addition to the familiar WYSIWIG and the "A Block Group" sections to link to additional content, each tab content group has a field listed as "Span#".  What's this "Span#" and why is it here?

The "Span#" represents the relative width of the content, expressed as the numerator of the fraction x/12.  So if you want a particular tab content group to take up half of the available area, you would express that as 6 in each of the "Span#" fields within the tab content group sections, because 6/12 = 1/2.  Similarly, if you want to split the area into 3/4 and 1/4, then the Span# fields would have 8 and 4 respectively as is shown in that image.  Something to note: the Span# numbers must add up to 12 over the entire set of tab content groups under a specific tab.

Tabs get a little confusing to be sure. Once the skeleton is set up, its relatively straightforward to make changes though, and we're always happy to help others out. Kudos to Deb and Marsha for persevering!


    CMS Manager Duties

    Monday, May 13, 2013

    Participate in this blog by suggesting additions or edits to this list and request the training you would like to have to meet these goals.

    We will be conducting CMS training in both of our CMS Manager meetings on June 6,  and July 11.

     The duties of a CMS manager

    • View sites monthly
      • personnel listing are up to date
      • event listing are up to date
      • notices are up to date
      • contact info and hours are current and correct
      • academic listing are appropriate for the active semester
      • content is displaying correctly
      • review google analytics
    • Ensure each site has an active editor - or cover for them. Keep the list of contributors current (Forward deletions and additions to the CMS Administrators - John or Dave)
    • Help contributors understand the following:
      • What is the purpose of the site? 
      • How important is this site to student success?
      • Who is the audience of the site? - age, demographic, reading level, needs.
      • What is out of date on the site? - pages content, personnel, events, notices, course or program listings.
      • What does the department get phone calls about that should be more obvious on the website.
      • Are the FAQ pages meeting the needs? Events? Notices? Content?
    • Train contributors to how to edit and monitor each type of page in their site
      (How to do much of this is explained here http://www.uas.alaska.edu/cms/tasks/index.html )
      • regular wysiwyg page content
      • faq
      • tabbed or column pages
      • content blocks
      • events
      • notices
      • personnel pages (dir file), 'references' into the directory, and the personnel listings
      • address pages (dir file) and the contact numbers and hours display on their site
      • editing forms (CMS administrators can help set up the form template if you need one)
      • pdf and image preparation and uploading
      • metadata
      • how to review google analytics (if approprate)
    • Report to your Deans and Directors on the health of the sites each semester.



      FORUM: Recent Topics

      Title Latest Post
      July Training 2011 07/18/11 04:44 PM (David Klein)
      View: Topic Index   Search