Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If you use a proper CMS (e.g. <a href="http://www.kentico.com/" rel="nofollow">Kentico CMS</a>) that stores content in a database, the backend depends on how the CMS organizes the data in its database.</p> <p>Learn about how the content maintainers will organize the language-dependent content (in the way that you are already thinking about it - content for what defined page sections per language)...and how that will translate into your CMS's underlying organization of the data.</p> <p>Start small, and be systematic - on the input end (i.e. how a content maintainer will go about doing their part) and on the content-consumption end; try to make one simple portion of the site that works with so much redundancy today...work without it; and go from there.</p> <p>For example, focus initially on one simple defined section in one page with content for each language. With that clear, consider a more complicated section that requires organization of content for each of its content areas. Then expand to multiple pages, considering different page types that may have different defined sections (and may already be clear from different master pages they employ).</p> <p>For email templates in particular, I have successfully used a CMS-maintained <a href="http://en.wikipedia.org/wiki/Smarty" rel="nofollow">Smarty</a> template per transactional-email type (e.g. order confirmation, shipment confirmation etcetera) for e-sales - even with ASP.NET being the primary technology on the team. You may need <em># of email types</em> * <em># of languages</em> templates, but it sounds like such an approach could work.</p> <p><em><strong>Also</em></strong>, consider that your CMS very well may expose services whereby you can get the content, such that you do not really have to be directly concerned with how it organizes the backend data.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload