In the project I am working has got new requirements !!

They want us to include additional language without creating more publications (as we already have 2 more besides English) and that for specific CTs and PTs. I was thinking to use a language parameter from which I can get a set of specific pages/components with that language parameter defined.

Am i going right way..of course it will be a whole new level of customization for... but has this been done before.. I mean like creating all localized content in the same publication.

Any answers much appreciated.

  • When you state "localizations" are you referring to Publications or the published website(s)? – Dylan .. Mark Saunders Oct 31 at 12:28
  • Yup.. Publications – Bhawna Jain Nov 1 at 4:00
  • 1
    It seems to me you're working against the real differentiator in the CMS here (specifically for translation/localization). I'd be more interested in understanding the case for not using blueprinting. Otherwise, I guess you're just going to create /content/language_x/ content folders - (and SG). At this point you'll be managing more content with no link to assess - what's been translated/localized etc. and the OOTB translation tools will not likely play nice with this configuration. – Dylan .. Mark Saunders Nov 1 at 11:58

Not using BluePrinting for languages is definitely not going the right way.

For example, you won’t be able to use Translation Manager to do translation.

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.