Trying to find out if Concrete5 can work this way. . .
Permalink
Hi - we are just about to select Concrete5 as our new CMS, but I really need to know if it can work as follows, before we commit to it:
We have a global website with regional offices.
We would like to create one global site, but tag all content as either Global (Default) or as one of the regions.
There would be a selector in the Header of the site for the user to select Global, or one of the regions.
Where no local (regional) content is set, the global default would display.
Where the regional team have create local regional content for that slot, this would be displayed.
Therefore the regional teams can create as much local content as they need, but they don't 'need' to do this - the default content will show if now regional content exists.
I'm thinking this is fairly standard way a modern dynamic CMS would work, but could someone please confirm that this is, or can be, how Concrete5 works also?
Many thanks for any feedback on this question.
Regards,
Mark
We have a global website with regional offices.
We would like to create one global site, but tag all content as either Global (Default) or as one of the regions.
There would be a selector in the Header of the site for the user to select Global, or one of the regions.
Where no local (regional) content is set, the global default would display.
Where the regional team have create local regional content for that slot, this would be displayed.
Therefore the regional teams can create as much local content as they need, but they don't 'need' to do this - the default content will show if now regional content exists.
I'm thinking this is fairly standard way a modern dynamic CMS would work, but could someone please confirm that this is, or can be, how Concrete5 works also?
Many thanks for any feedback on this question.
Regards,
Mark
FYI: As of 5.7.3, Multilingual is now part of the core .
Many thanks both for your reply.
Using the International feature 'might' work...but it sounds possibly a bit of a hack rather than a core feature.
What I mean is that I would have expected the targeting of content to be a fundamental part of the CMS, and I'm slightly concerned if I use International for this then what happens when we do want to manage versions of the site in additional languages? Maybe the concept will just extend to this, but it also might get in the way.
Also I'm a bit concerned about the comment that it will 'copy the tree' - as, if you really mean 'copy' then that implies you end up with two sources of content that then need to be managed separately, whereas what I'm after is a link to single default content where appropriate, with overriding local content where needed (which might be what you mean, I just wasn't sure).
Anyway, thanks again for the feedback, which is helpful.
I think I'll need to dig a bit further.
Cheers,
Mark
Using the International feature 'might' work...but it sounds possibly a bit of a hack rather than a core feature.
What I mean is that I would have expected the targeting of content to be a fundamental part of the CMS, and I'm slightly concerned if I use International for this then what happens when we do want to manage versions of the site in additional languages? Maybe the concept will just extend to this, but it also might get in the way.
Also I'm a bit concerned about the comment that it will 'copy the tree' - as, if you really mean 'copy' then that implies you end up with two sources of content that then need to be managed separately, whereas what I'm after is a link to single default content where appropriate, with overriding local content where needed (which might be what you mean, I just wasn't sure).
Anyway, thanks again for the feedback, which is helpful.
I think I'll need to dig a bit further.
Cheers,
Mark
the multilingual add-on could do the trick. This is valid for 5.6.3, I havent experimented with the multilingual function in 5.7, but it "should" do the same.
You could set up your "default" content as english language content and the other bits in their respective language.
Once you've built your site in english, the multilingual add-on will just copy the site tree (the content will be the same english) and translate the regional content in their respective languages.
Now if you dont translate - it will just stay the same.
You could change the "language switcher block" to suit the names of your regional offices instead of showing the country flags.