Timeline for Localized content within same localization
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 5, 2019 at 3:01 | history | tweeted | twitter.com/StackTridion/status/1081385055967211521 | ||
| Dec 31, 2018 at 6:33 | answer | added | Jonathan Williams | timeline score: 2 | |
| Dec 30, 2018 at 16:02 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Nov 30, 2018 at 15:35 | answer | added | Rick Pannekoek | timeline score: 1 | |
| Nov 30, 2018 at 12:01 | history | edited | Marko Milic♦ | CC BY-SA 4.0 |
added 2 characters in body
|
| Nov 1, 2018 at 11:58 | comment | added | Dylan .. Mark Saunders | 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. | |
| Nov 1, 2018 at 4:00 | comment | added | Bhawna Jain | Yup.. Publications | |
| Oct 31, 2018 at 12:28 | comment | added | Dylan .. Mark Saunders | When you state "localizations" are you referring to Publications or the published website(s)? | |
| Oct 31, 2018 at 10:06 | history | asked | Bhawna Jain | CC BY-SA 4.0 |