Centralizing assets/components
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.
Discussions are closed to public comments.
If you need help with Cascade CMS please
start a new discussion.
Keyboard shortcuts
Generic
| ? | 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
1 Posted by Wing Ming Chan on Jun 02, 2016 @ 07:12 PM
Hi,
You may want to look at my Standard Model:
http://www.upstate.edu/cascade-admin/projects/upstate-implementatio...
I implemented the new Hannon Hill site in less than four days, using the reusable core.
Wing
2 Posted by tdb on Jun 03, 2016 @ 12:56 PM
Thank you Wing, I will definitely check it out. So far it looks fascinating.
3 Posted by Wing Ming Chan on Jun 03, 2016 @ 02:50 PM
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.
Wing
Tim closed this discussion on Jun 27, 2016 @ 08:58 PM.