Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Steven 33 posts 166 karma points
    Mar 06, 2017 @ 09:24
    Steven
    0

    Hey guys,

    Just a quick note to say 'THANKS' for such a great package ...

    I am used to working with Umbraco V6 in webforms modus with mostly dynamic model razor scripting so this package gives me a great start into using MVC with typed model razor scripting ... it is even that great I am considering using it 'out of the box' ( with maybe some changes here and there ... one is a 'programmer' after all :-) ).

    Having said that ... a couple of 'quick questions' ...

    • I already have existing sites with my own document types etc ( but luckily already in a very similar 'loosely coupled way - no 'fixed' page content'... in your experience ... is there an 'easy way' in 'migrating' the data ? I either can convert the existing document types into yours or 'incorporate' my document types into your structure ...
    • 'Multi-language' front-end content support ... is this foreseen in the template ? How do you guys typically address this 'functionality' within Umbraco ?

    Thanks,

    Steven

  • Sotiris Filippidis 286 posts 1501 karma points
    Mar 06, 2017 @ 20:30
    Sotiris Filippidis
    100

    Thanks Steven,

    Well, about migrating data, I really can't say, but I don't think there is some direct way to do that anyway. My doctypes are largely compositions of standard "base" documents, so I think you'll have better luck incorporating yours into my structure, but it's just a guess.

    Multilanguage - yes, the package supports multilanguage. You just have to create two (or more) roots (home pages), each with a different language. All resources that can be localized are in the Dictionary and there are no loose literal strings in the partials and the templates.

    The multi language approach this package follows is the "separate content trees" approach, which means that each language can have its own structure. This means you can't go from a specific page in one language to a corresponding page in another - doing so would require you to relate the two pages and write code to take the relation under consideration.

    Also, (and I'm sorry for that) you'll have to implement your own language switcher, which is not difficult but I admit I was lazy and didn't create one :)

Please Sign in or register to post replies

Write your reply to:

Draft