Decide between subdomains / subdirectories / multiple sites / one site?
Our older Cascade instance is still all one Global site (using Targets), but this year we are redeveloping the websites from scratch.
The question has been raised about changing from site subdomains to subdirectories, e.g.
liberalarts.udmercy.edu —> udmercy.edu/liberalarts
We were told by Beacon Technologies that we would enjoy easier sharing/maintenance of common page elements (design / look & feel, etc.) if we keep content all together in one domain/site in Cascade Server.
Would anyone share their thoughts / experience about this?
QUESTION 1: Is it actually more difficult to maintain common design across Cascade Server Sites than if you keep all web content within the same Cascade Site?
The other advantage we're told of going from subdomains to subdirectories is that the subdirectories approach provides some kind of boost in search engine results for combined site content.
Also, is this whole question extraneous? For example:
QUESTION 2: Is it possible to maintain separate Cascade Sites but have them publish to subdirectories within a single live website?
I hope this was clear.
Thanks much, in advance.
Jon
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 Penny on 09 Nov, 2015 08:09 PM
Hi Jon,
To be as detailed as possible, please see my thoughts inline. Thanks!
We would definitely recommend breaking content into sites. It is pretty easy to centralize all of your design elements into one site and then share it across multiple sites.
I have heard this as well.
Yes. Definitely. This is what a lot of Cascade Server clients do. For each site, you can determine if it should go to a subdomain or a sub folder. That is up to you.
Moving from Global to sites will mean that you will be able to more easily share elements and content across sites.
Please let me know if I missed anything. Thanks!
2 Posted by Wing Ming Chan on 09 Nov, 2015 08:53 PM
Hi Jon,
Centralizing common assets shared by various sites will reduce maintenance tremendously. For example, you can have a single RWD design and implementation in a site shared by multiple other sites. When a page is moved from one site to another site, it will adapt to its environment, picking up specific site information, without any modification to the page. This approach will also reduce the number of content types. We actually use only one RWD content type in the entire Cascade installation, and converting a non-responsive site to a responsive site just requires running a web service script.
Wing
3 Posted by whitenjg on 13 Nov, 2015 08:33 PM
Thank you, Penny and Wing!
Tim closed this discussion on 02 Dec, 2015 04:10 PM.