Centralizing assets/components

tdb's Avatar


02 Jun, 2016 07:08 PM

We haven't done much in the way of centralizing assets within Cascade. Instead we've been copying previous sites, but each site is basically independent at that point.

We're going to be developing a new framework for multiple sites to use, and would like to centralize as much as possible since they'll all be using similar layouts, etc.

Are there best practices in Cascade that we could use?

Which components can be centralized (formats, data definitions, images, CSS, etc.), and which can't or shouldn't be?

Should the centralized content be in a "site" or would it be in the Global area?

Any and all advice you might have along these lines would be appreciated.

  1. 1 Posted by Wing Ming Chan on 02 Jun, 2016 07:12 PM

    Wing Ming Chan's Avatar


    You may want to look at my Standard Model:


    I implemented the new Hannon Hill site in less than four days, using the reusable core.


  2. 2 Posted by tdb on 03 Jun, 2016 12:56 PM

    tdb's Avatar

    Thank you Wing, I will definitely check it out. So far it looks fascinating.

  3. 3 Posted by Wing Ming Chan on 03 Jun, 2016 02:50 PM

    Wing Ming Chan's Avatar

    I have just learned that Nova Southeastern University http://www.nova.edu/ has implemented a one-region template associated with a couple of content types, using my design, in a very short period of time.


  4. Tim closed this discussion on 27 Jun, 2016 08:58 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac