Getting Started

Login to your control panel and go to Content > CMS.

The CMS will display a list of several root files and folders that represent all of the HTML pages used by your website which are immediately editable.

Begin by clicking on the Rakeback folder to expan it. This will reveal a list of poker site glance pages that may or may not be available to your skin. Clicking on the icon to the left of the name of each file will open the code editor and reveal the HTML code pertaining to that particular section of your site.

Most of the text you will be translating will appear in the color black. Be aware however, that just because text appears in black does not mean that it is safe to edit! See below for examples of text or code to avoid.

{% offer_page "cake-poker" %}
<div id="pas_glance">
<h1 class="pas">{{ offer.name }} Rakeback</h1>
<img src="{{ tld }}{{ offer.image }}" class="pas_logo" alt=""/>
<h2 class="pas">{{ offer.reward }} Rakeback at {{ offer.name }}</h2>
<h3 class="pas">{{ offer.network }} Network</h3>

Code you should NOT edit

The following is a non comprehensive list of items you should not edit when you translate your site:

• Tokens - Any text enclosed in {{ double curly braces }}
• HTML - Most text enclosed in < brackets > should not be altered
• CSS Files - Includes template CSS, Site CSS and all files in the CSS folder.
• Javascript Files - Includes all files in the Javascript Folder

Suggested Files to Translate

css folder >

DO NOT TRANSLATE.

Emails folder >

• all .txt files contained here.

javascript folder >

DO NOT TRANSLATE.

layout folder >

• footer.html (this contains bottom navigation items such as ‘Home’, ‘Sign Up’, etc.)
• layout.html (primarily contains top navigation items)

my-account folder >

• all files/directories may be translated.

navigation folder >

• The *_widget.html files here have very little to translate, only the word ‘Promotions’ at the top of each file.

promotions folder >

• /archives > no translation.
• all other files/directories may be translated.

rakeback folder >

These are what used to be referred to as ‘glance pages’.

• all files may be translated.

rakeback-news folder >

• both files contain minimal text for translation.

refer-a-friend folder >

• all files/directories may be translated.

signup-forms folder >

• all files/directories may be translated EXCEPT:
• /site-signup-form/site-signup-add-by.html > DO NOT TRANSLATE.

support folder >

• all files/directories may be translated.

user-login folder >

• all three .html files have text that can be translated.

root directory >

• all files, except:
• googlehostedservice.html > DO NOT TRANSLATE. This page is used only for setting up Google Apps.
• robots.txt > DO NOT TRANSLATE. This page is used by web spiders/crawlers for indexing your page.
• sitemap.xml > DO NOT TRANSLATE.

Text You Cannot Directly Translate

Some text cannot be translated directly through the Content Management System. In particular, when text is called by a token, you will find no reference to it in the CMS.

When you encounter this, you may be able to translate this text indirectly through the Word Translation feature.

To do so, go to Content > Word Translation in your control panel navigation.

You can then fill out the forum using the English term and context provided. The software will then search your site for any instances of the words used in this form and automatically translate them for you.

It is important to remember that this is not a substitute for the above steps. You will still have to translate most of the text directly, however this tool will be important for text that cannot be edited directly.