Recording of training can be found here

These are very brief guidelines to the systems Titan, Spree, and GEAG. Included are videos for uploading as well as a short explanation of each.

Contents

Steps to take before building a page 

The course page is created in Titan CMS, but there is also some manual loading that needs to be done on Spree.

The first phase of uploading these three pages is the Course page on Titan CMS.

LAUNCH PACK DOC FOR DEMONSTRATION PURPOSES

Above as an example of a launch pack that web producers would receive from the Content team. 70% to 80% of this launch pack is content that belongs on the three pages uploaded for each course. This doc also contains any and all information needed to produce the product on all the relevant CMS’ such as Titan CMS, Spree and WordPress.

Titan CMS Course page upload recording (5 min)
NOTE: This recording goes through the CMS instance for a Course page that was uploaded earlier this week. It doesn’t showcase the real upload process, although I do go through the same steps as if it was.

Uploading a course page in Titan CMS takes between 30 to 60 minutes.

Spree includes the slug, meta title, meta description and taxons. This is a small, but important part of our upload and as far as product uploads go this is all that is required in Spree.

Spree is also used to configure whether presentations display on the getsmarter.com website or not.

Spree Course page set up recording (1 min)

This part is fairly quick, but incredibly important as it contains high level pieces of information like the slug, various taxons, and determines the metadata for search engines.

The API Gateway, GEAG, sends content uploaded onto Titan CMS to the edX marketplace through a datastream. This circumvents the necessity to load every Exec Ed product onto their CMS.

There’s nothing for us to do here, though having access and supervision of this is vital to search for and deduce location of errors.