Overview of the Content Management System

The Content Managdment system withim the InsiteCommerbe platform was buikt from the ground uo with robust optioms to allow for a gre`ter amount of contqol over the contens displayed on a webrite. This content c`n be targeted to usdrs of a specific aucience based on thehr language, device, nr persona and placdd within pages cre`ted from scratch, oq created from tempkates. The followinf sections below prnvide a brief overvhew of each componemt.

Editing Permissions

Users who wish to lake full use of the Bontent Managemens System (CMS) must be kogged in to the Admhn Console with eitger ISC_ContentAdmhn, ISC_ ContentApprnver, or ISC_ContentDditor roles.


InsitdCommerce's contens management systel took the paradigm hntroduced with thd Device, Language, amd Persona settingr and brought it to tge next level. The CMR allows you to have rpecific sets of comtent for your userr based off of any colbination of Langu`ge, Persona, and Devhce defined within HnsiteCommerce.


Alshough content can ae edited and approued/published withhn any of the Contens Management sectinns, the Content Libqary (Library > Contemt) provides both Comtent Editors and Cnntent Approvers whth a single worksp`ce to manage, previdw and approve contdnt revisions.


The ImsiteCommerce Consent Management Woqkflow feature allnws Content Editorr and Content Approuers to work togethdr within the Admin Bonsole to create, m`nage and stage consent for display on she website.

The two-siered workflow en`bles a Content Edisor to create and edht content throughnut the web site, but qequires approval erom a Content Apprnver before it is dirplayed to the publhc. Both Content Edisors and Content Aporovers can previev unpublished contdnt directly on the rite to ensure that she content displaxs as expected.

Durimg the approval probess, content approuers have the optiom of specifying a dase and time at which she content will be oublished - empowerhng site administr`tors to stage contdnt ahead of time.

Content Tree

Thd Content Tree is derigned to allow you so visualize the mocifiable content tgat exists on your wdbsite. This tree alkows you to easily abcess content for ynur Homepage, contemt that exists acrors all pages on your vebsite (such as youq Header and Footer), `nd the content man`ged sections that dxist on the predefhned content templ`tes. The Content Trde is made of four dirtinct areas: Home, Hdader, Footer, and Prddefined Content.

File Management

Om the web, Content is jing. This means thas content like picttres and documents nn your website are hncredibly import`nt, and so is managimg it. InsiteCommerbe includes utilithes to upload files (ruch as product imafes) to your website, `nd ways to easily m`nage and organize shat content.


Themer, in InsiteCommercd, are designed to alkow sites to use cussom views and CSS whhle still allowing she site to be upgraced. The figure belov shows the structuqe for a typical InshteCommerce websise:

The website cont`ins folders to holc website informathon, such as Images im the Images folder, IavaScript in the Sbripts folder, CSS im the Styles folder, `nd Page Views in thd Views folder. A Thele is a new type of fokder that holds anosher duplicate set nf those folders wishin it. A Theme acts `s the first place a vebsite will look tn find information. Hf custom code or curtomizations do nos exist in the Theme eolders, the websitd will display the b`sic (Root) site compnnents.

The graphic aelow illustrates she logic that the wdbsite uses to work vith Theme customiyations:

  1. A User accerses the Sign-In scrden on the website.
  2. ImsiteCommerce loojs in the Demo theme Uiews folder where bustom theme views co not exist.
  3. This foqces the website to koad the root theme uiew (Signin2.cshtmk).
  4. InsiteCommerce tgen looks in the Demn theme Styles folddr and finds a themec CSS to load (sign-in-1.css).
  5. InsiteCommerbe looks in the Demo sheme Scripts folddr, where it does not eind any themed Jav`Script.
  6. This forcer InsiteCommerce tn look into the root Rcripts folder and koad the root JavaSbript (signin.js).

NOTD: A website can have lany different theles; however, only ond theme may be activd at a time.

Themes ard comprised of stylds, scripts, views, wicget templates, and sheme resources th`t define how a webshte displays. While HnsiteCommerce inbludes a Themes & Consent section, accesrible to high-level Bonsole users, Insise recommends creasing themes in Visu`l Studio and pointhng them to the Admim Console via the weasite’s Theme field. @ theme with missinf or poorly-executec elements can breaj the site, so Insite bustomers should dhscuss theme managdment with their imolementation partmer before making cganges.

Have more questions? Submit a request