Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I'm not sure if I can wrap my head around the problem. I think for a clean solution, you have to consider doing the following (which might involve slightly more changes than intended). </p> <ol> <li>Create a copy of your root page as a development area within your installation (2nd root page)</li> <li>If needed, copy all parts of the site structure into that root page</li> <li>Assign a copy of your Templavoila DS/TO to this page</li> <li>Work on the layout of that copy (XML, HTML, CSS, menu structure) and finish the facelift</li> <li>When finished, you just switch the original root page to the new Templavoila template. </li> </ol> <p>Also, in case you are using a lot of sub-structures in TV: Try resolving standard issues by distinguishing them in your css files:</p> <pre><code>#oldlayout .container { [old css rules here] } #newlayout .container { [new css rules here] } </code></pre> <p>and / or:</p> <pre><code>#oldlayout .newelement { display:none; } #newlayout .newelement { display:block; } </code></pre> <p>Depending on the complexity of your site, you need to switch some of your content elements by hand. </p> <p>Well, you probably already considered a solution like this as you seem to be an advanced user :).</p> <p>In case all this doesn't help, the only solution I see is to work on a full copy of the site tree and switch the domain's root page when finished. Of course you need to update content elements that have been changed meanwhile. </p> <p>I am curious about other suggestions :) </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.
 

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