msgid "Copy the tracking ID to insert it in Odoo."
msgstr ""
#: ../../website/optimize/google_analytics.rst:20
msgid "Go to the *Configuration* menu of your Odoo's Website app. In the settings, turn on Google Analytics and paste the tracking ID. Then save the page."
msgstr ""
#: ../../website/optimize/google_analytics.rst:27
msgid "To make your first steps in Google Analytics, refer to `Google Documentation. <https://support.google.com/analytics/answer/1008015?hl=en/>`__"
msgid "A preliminary step is creating a Google Analytics account and entering the tracking ID in your Website's settings (see :doc:`google_analytics`)."
msgid "Then you can create a Client ID. Enter the name of the application (e.g. Odoo) and the allowed pages on which you will be redirected. The *Authorized JavaScript origin* is your Odoo's instance URL. The *Authorized redirect URI* is your Odoo's instance URL followed by '/google_account/authentication'."
msgid "Go through the Consent Screen step by entering a product name (e.g. Google Analytics in Odoo). Feel free to check the customizations options but this is not mandatory. The Consent Screen will only show up when you enter the Client ID in Odoo for the first time."
msgid "Search Engine Optimization (SEO) is a set of good practices to optimize your website so that you get a better ranking in search engines like Google. In short, a good SEO allows you to get more visitors."
msgid "Some examples of SEO rules: your web pages should load fast, your page should have one and only one title ``<h1>``, meta tags (alt-tag, title-tag) should be consistent with the content, your website should have a ``/sitemap.xml`` file, etc."
msgid "To guarantee Odoo Website and Odoo eCommerce users have a great SEO, Odoo abstracts all the technical complexities of SEO and handles everything for you, in the best possible way. This will be explained here below."
msgid "Every web page should define the ``<title>`` and ``<description>`` meta data. These information elements are used by search engines to promote your website. They are automatically generated based on page title & content, but you can finetune them. Make sure they fit the content of the page, otherwise you will be downgraded by search engines."
msgid "In order to write quality content and boost your traffic, Odoo provides a ``<keyword>`` finder. Those keywords are the searches you want to head towards your website. For each keyword, you see how it is used in the content (H1, H2, page title, page description, page content) and what are the related searches in Google. The more keywords are used the better."
msgid "If your website is in multiple languages, you can use the Promote tool for every language of a single page and set specific title, description and search tags."
msgid "**Odoo Slides**: publish all your Powerpoint or PDF presentations. Their content is automatically indexed on the web page. Example: `https://www.odoo.com/slides/public-channel-1 <https://www.odoo.com/slides/public-channel-1>`__"
msgid "**Odoo Forum**: let your community create contents for you. Example: `https://odoo.com/forum/1 <https://odoo.com/forum/1>`__ (accounts for 30% of Odoo.com landing pages)"
msgid "**Odoo Mailing List Archive**: publish mailing list archives on your website. Example: `https://www.odoo.com/groups/community-59 <https://www.odoo.com/groups/community-59>`__ (1000 pages created per month)"
msgid "The 404 page is a regular page, that you can edit like any other page in Odoo. That way, you can build a great 404 page to redirect to the top content of your website when visitors get lost in invalid URLs."
msgid "Social media is built for mass sharing. If lots of people share your content on social media, then it's likely more people will link to it, and links are a huge factor for SEO ranking."
msgid "Odoo allows to link all your social network accounts in your website footer. All you have to do is to refer all your accounts in your company settings."
msgid "Drop the building block *Share* on any page you want your visitors to share. By clicking the icon, they are prompted to share the page in their social media wall."
msgid "Most social media use a picture of the picture to decorate the share post. Odoo uses the website logo by default but you can choose any other image of your page in the Promote tool."
msgid "Drop the building block *Facebook Page* to display a widget of your Facebook business page and encourage visitors to follow it. You can display the timeline, the next events and the messages."
msgid "You can compare how your website rank, in terms of SEO, against Odoo using WooRank free services: `https://www.woorank.com <https://www.woorank.com>`__"
msgid "**/fr\\_FR** = page language. This part of the URL is removed if the visitor browses the main language of the website Thus, the main version of this page is: https://www.mysite.com/shop/product/my-great-product-31"
msgid "**/shop/product** = every module defines its own namespace (/shop is for the catalog of the eCommerce module, /shop/product is for a product page)."
msgid "**my-great-product** = by default, this is the slugified title of the product this page refers to. But you can customize it for SEO purposes. A product named \"Pain carré\" will be slugified to \"pain-carre\". Depending on the namespace, this could be different objects (blog post, page title, forum post, forum comment, product category, etc.)."
msgid "When an Odoo page has a pager, the page number is set directly in the URL (does not have a GET argument). This allows every page to be indexed by search engines. Example:"
msgid "In short, just change the title of a blog post or the name of a product, and the changes will apply automatically everywhere in your website. The old link still works for links coming from external websites, with a 301 redirect to not lose the SEO link juice."
msgid "Search engines boost ranking of secure HTTPS/SSL websites. So, by default all Odoo Online instances are fully based on HTTPS. If the visitor accesses your website through a non HTTPS url, it gets a 301 redirect to its HTTPS equivalent."
msgid "But every link posted by a contributor that links to an external website is \"nofollow\". In that way, you do not run the risk of people posting links on your website to third-party websites which have a bad reputation."
msgid "Note that, when using the forum, contributors having a lot of Karma can be trusted. In such case, their links will not have any ``rel=\"nofollow\"`` attribute."
msgid "In this example, fr\\_FR is the language of the page. You can even have several variations of the same language: pt\\_BR (Portuguese from Brazil) , pt\\_PT (Portuguese from Portugal)."
msgid "To let search engines know that the second URL is the French translation of the first URL, Odoo will add an HTML link element in the header. In the HTML <head> section of the main version, Odoo automatically adds a link element pointing to the translated versions of that webpage;"
msgid "You do not get penalized by search engines if your page is not translated yet. Indeed, it's not a duplicated content, but a different version of the same content."
msgid "When a visitor lands for the first time on your website (e.g. yourwebsite.com/shop), they may automatically be redirected to a translated version according to their browser language preference: (e.g. yourwebsite.com/fr\\_FR/shop)."
msgid "To force a visitor to stick to the default language, you can use the code of the default language in your link, example: yourwebsite.com/en\\_US/shop. This will always land visitors to the English version of the page, without using the browser language preferences."
msgid "The time to load a page is an important criteria for search engines. A faster website not only improves your visitor's experience, but gives you a better page ranking. Some studies have shown that, if you divide the time to load your pages by two (e.g. 2 seconds instead of 4 seconds), the visitor abandonment rate is also divided by two. (25% to 12.5%). One extra second to load a page could `cost $1.6b to Amazon in sales <http://www.fastcompany.com/1825005/how-one-second-could-cost-amazon-16-billion-sales>`__."
msgid "Fortunately, Odoo does all the magic for you. Below, you will find the tricks Odoo uses to speed up your page loading time. You can compare how your website ranks using these two tools:"
msgid "When you upload new images, Odoo automatically compresses them to reduce their sizes (lossless compression for .PNG and .GIF and lossy compression for .JPG)."
msgid "From the upload button, you have the option to keep the original image unmodified if you prefer to optimize the quality of the image rather than performance."
msgid "Odoo compresses images when they are uploaded to your website, not when requested by the visitor. Thus, it's possible that, if you use a third-party theme, it will provide images that are not compressed efficiently. But all images used in Odoo official themes have been compressed by default."
msgid "When you click on an image, Odoo shows you the Alt and title attributes of the ``<img>`` tag. You can click on it to set your own title and Alt attributes for the image."
msgstr ""
#: ../../website/optimize/seo.rst:361
msgid "When you click on this link, the following window will appear:"
msgid "Odoo's pictograms are implemented using a font (`Font Awesome <https://fortawesome.github.io/Font-Awesome/icons/>`__ in most Odoo themes). Thus, you can use as many pictograms as you want in your page, they will not result in extra requests to load the page."
msgid "this CSS file is shared and cached amongst pages, so that when the visitor clicks on another page, the browser doesn't have to even load a single CSS resource."
msgid "**Pre-processed:** The CSS framework used by Odoo is Bootstrap. Although a theme might use another framework, most of `Odoo themes <https://www.odoo.com/apps/themes>`__ extend and customize Bootstrap directly. Since Odoo supports Less and Sass, you can modify CSS rules instead of overwriting them through extra CSS lines, resulting in a smaller file."
msgid "**Concatenated:** every module or library you might use in Odoo has its own set of CSS, Less or Sass files (eCommerce, blogs, themes, etc.). Having several CSS files is great for the modularity, but not good for the performance because most browsers can only perform 6 requests in parallel resulting in lots of files loaded in series. The latency time to transfer a file is usually much longer than the actual data transfer time, for small files like .JS and .CSS. Thus, the time to load CSS resources depends more on the number of requests to be done than the actual file size."
msgid "To address this issue, all CSS / Less / Sass files are concatenated into a single .CSS file to send to the browser. So a visitor has **only one .CSS file to load** per page, which is particularly efficient. As the CSS is shared amongst all pages, when the visitor clicks on another page, the browser does not even have to load a new CSS file!"
msgid "The CSS sent by Odoo includes all CSS / Less / Sass of all pages / modules. By doing this, additional page views from the same visitor will not have to load CSS files at all. But some modules might include huge CSS/Javascript resources that you do not want to prefetch at the first page because they are too big. In this case, Odoo splits this resource into a second bundle that is loaded only when the page using it is requested. An example of this is the backend that is only loaded when the visitor logs in and accesses the backend (/web)."
msgid "If the CSS file is very big, Odoo will split it into two smaller files to avoid the 4095 selectors limit per sheet of Internet Explorer. But most themes fit below this limit."
msgid "Then, a cached version is stored server-side (so we do not have to pre-process, concatenate, minify at every request) and browser-side (so the same visitor will load the CSS only once for all pages they visit)."
msgid "Most visitors of your website will only need the first two bundles, resulting in a maximum of two Javascript files to load to render one page. As these files are shared across all pages, further clicks by the same visitor will not load any other Javascript resource."
msgid "If you work in debug mode, the CSS and Javascript are neither concatenated, nor minified. Thus, it's much slower. But it allows you to easily debug with the Chrome debugger as CSS and Javascript resources are not transformed from their original versions."
msgid "If you activate the CDN feature in Odoo, static resources (Javascript, CSS, images) are loaded from a Content Delivery Network. Using a Content Delivery Network has three advantages:"
msgid "Cache resources efficiently (no computation resources usage on your own server)"
msgstr ""
#: ../../website/optimize/seo.rst:501
msgid "Split the resource loading on different services allowing to load more resources in parallel (since the Chrome limit of 6 parallel requests is by domain)"
msgid "You can configure your CDN options from the **Website Admin** app, using the Configuration menu. Here is an example of configuration you can use:"
msgid "The HTML pages can be compressed, but this is usually handled by your web server (NGINX or Apache)."
msgstr ""
#: ../../website/optimize/seo.rst:517
msgid "The Odoo Website builder has been optimized to guarantee clean and short HTML code. Building blocks have been developed to produce clean HTML code, usually using Bootstrap and the HTML editor."
msgid "As an example, if you use the color picker to change the color of a paragraph to the primary color of your website, Odoo will produce the following code:"
msgid "Websites that are not mobile-friendly are negatively impacted in search engine rankings. All Odoo themes rely on Bootstrap to render efficiently according to the device: desktop, tablet or mobile."
msgid "Javascript, images and CSS resources have an URL that changes dynamically when their content change. As an example, all CSS files are loaded through this URL: `http://localhost:8069/web/content/457-0da1d9d/web.assets\\_common.0.css <http://localhost:8069/web/content/457-0da1d9d/web.assets_common.0.css>`__. The ``457-0da1d9d`` part of this URL will change if you modify the CSS of your website."
msgid "In addition to being fast, Odoo is also more scalable than traditional CMS and eCommerce (Drupal, Wordpress, Magento, Prestashop). The following link provides an analysis of the major open source CMS and eCommerce compared to Odoo when it comes to high query volumes: `*https://www.odoo.com/slides/slide/197* <https://www.odoo.com/slides/slide/odoo-cms-performance-comparison-and-optimisation-197>`__"
msgid "The sitemap points out pages to index to search engine robots. Odoo generates a ``/sitemap.xml`` file automatically for you. For performance reasons, this file is cached and updated every 12 hours."
msgid "By default, all URLs will be in a single ``/sitemap.xml`` file, but if you have a lot of pages, Odoo will automatically create a Sitemap Index file, respecting the `sitemaps.org protocol <http://www.sitemaps.org/protocol.html>`__ grouping sitemap URL's in 45000 chunks per file."
msgid "``<lastmod>`` : last modification date of the resource, computed automatically based on related object. For a page related to a product, this could be the last modification date of the product or the page."
msgid "``<priority>`` : modules may implement their own priority algorithm based on their content (example: a forum might assign a priority based on the number of votes on a specific post). The priority of a static page is defined by it's priority field, which is normalized (16 is the default)."
msgid "Structured Data Markup is used to generate Rich Snippets in search engine results. It is a way for website owners to send structured data to search engine robots; helping them understand your content and create well-presented search results."
msgid "Odoo implements micro data as defined in the `schema.org <http://schema.org>`__ specification for events, eCommerce products, forum posts and contact addresses. This allows your product pages to be displayed in Google using extra information like the price and rating of a product:"
msgid "When indexing your website, search engines take a first look at the general indexing rules of the a``/robots.txt`` file (allowed robots, sitemap path, etc.). Odoo automatically creates it. Its content is:"
msgid "It means that all robots are allowed to index your website and there is no other indexing rule than specified in the sitemap to be found at following address."
msgid "You can customize the file *robots* in developer mode from *Settings --> Technical --> User Interface --> Views* (exclude robots, exclude some pages, redirect to a custom Sitemap). Make the Model Data of the view *Non Updatable* to not reset the file after system upgrades."
msgid "By default, your Odoo Online instance and website have a *.odoo.com* domain name, for both the URL and the emails. But you can change to a custom one (e.g. www.yourcompany.com)."
msgid "Your website address is as important to your branding as the name of your business or organization, so put some thought into changing it for a proper domain. Here are some tips:"
msgid "Feel free to buy an email server to have email addresses using your domain name. However don't buy any extra service to create or host your website. This is Odoo's job!"
msgid "Create a CNAME record *www.yourdomain.com* pointing to *mywebsite.odoo.com*. If you want to use the naked domain (e.g. yourdomain.com), you need to redirect *yourdomain.com* to *www.yourdomain.com*."
msgid "Until recently, Odoo users needed to use a third-party CDN service provider such as CloudFlare to enable SSL."
msgstr ""
#: ../../website/publish/domain_name.rst:89
msgid "It is not required anymore: Odoo generates the certificate for you automatically, using integration with `Let's Encrypt Certificate Authority and ACME protocol <https://letsencrypt.org/how-it-works/>`__. In order to get this, simply add your domain name in your customer portal (a separate certificate is generated for each domain name specified)."
msgstr ""
#: ../../website/publish/domain_name.rst:92
msgid "If you already use CloudFlare or a similar service, you can keep using it or simply change for Odoo. The choice is yours."
msgid "If you set up a custom domain *mydomain.com* name for *mydatabase.odoo.com*, Google indexes your website under both names. This is a limitation of the Odoo cloud platforms/"
msgid "Odoo’s Multi-Websites opens up broad possibilities of diversification and customer segmentation for your business. A multiplied audience and boosted revenue are now just a few clicks away!"
msgstr ""
#: ../../website/publish/multi_website.rst:12
msgid "Each website can work in a fully independent way, with its theme, branding, domain name, header & footer, pages, languages, products, blog posts, forum, slides, events, live chat channels, etc. Let’s go for a tour!"
msgstr ""
#: ../../website/publish/multi_website.rst:18
msgid "Setup"
msgstr ""
#: ../../website/publish/multi_website.rst:20
msgid "To create a new website, go to :menuselection:`Website --> Configuration → Settings`. The button, *Create a new website*, lays in the first section."
msgstr ""
#: ../../website/publish/multi_website.rst:28
msgid "In the upcoming prompt, set a name for your new website and a specific domain name. Leave empty to publish the new website under the default domain of your Odoo database. You can later set some country groups to redirect visitors to it using Geo IP."
msgstr ""
#: ../../website/publish/multi_website.rst:36
msgid "Then, select a theme. This new website might have an entirely different purpose or audience than the first one. So feel free to go for a different theme!"
msgstr ""
#: ../../website/publish/multi_website.rst:40
msgid "Once the theme is selected, you can start to build the homepage of your website. Follow the purple drops; they will help you in the first steps."
msgstr ""
#: ../../website/publish/multi_website.rst:48
msgid "If you run Odoo Online, don’t forget to redirect any new domain name to your Odoo database (CNAME) and to authorize it Odoo-side. `Read <https://www.odoo.com/documentation/user/online/website/publish/domain_name.html>`__"
msgstr ""
#: ../../website/publish/multi_website.rst:52
msgid "Create the menu"
msgstr ""
#: ../../website/publish/multi_website.rst:54
msgid "The new website has a default menu with all the installed applications. To edit it, click *Pages > Edit Menu*. Moving forward you only edit the menu of the current website."
msgstr ""
#: ../../website/publish/multi_website.rst:59
msgid "Switch from one website to another"
msgstr ""
#: ../../website/publish/multi_website.rst:62
msgid "As easy as ABC! There is a website switcher in the right corner of the edit bar. Switching to another website will connect to the domain of this website. If you use another domain for the website, the user is requested to sign in."
msgstr ""
#: ../../website/publish/multi_website.rst:71
msgid "When switching, you are redirected to the same domain path on the other website (e.g.,/shop/myproduct). If this URL is not used, you will be redirected to a 404 page but suggested to create a new page from there."
msgstr ""
#: ../../website/publish/multi_website.rst:74
msgid "Add features"
msgstr ""
#: ../../website/publish/multi_website.rst:76
msgid "The website apps you install (e.g., Slides, Blogs) are made available on all your websites. You can, of course, keep them hidden in one website by removing the menu item."
msgstr ""
#: ../../website/publish/multi_website.rst:80
msgid "Each website comes with a high range of specific options in the settings. First, select the website to configure."
msgstr ""
#: ../../website/publish/multi_website.rst:86
msgid "Then, take a look at the options flagged with the earth icon. It means they only impact the very website you are working on."
msgstr ""
#: ../../website/publish/multi_website.rst:92
msgid "You can, for instance, set specific :"
msgstr ""
#: ../../website/publish/multi_website.rst:94
msgid "languages,"
msgstr ""
#: ../../website/publish/multi_website.rst:96
msgid "domain names,"
msgstr ""
#: ../../website/publish/multi_website.rst:98
msgid "social media links,"
msgstr ""
#: ../../website/publish/multi_website.rst:100
msgid "customer portal mode (B2C vs. B2B),"
msgstr ""
#: ../../website/publish/multi_website.rst:102
msgid "dedicated live chat channels,"
msgstr ""
#: ../../website/publish/multi_website.rst:104
msgid "etc."
msgstr ""
#: ../../website/publish/multi_website.rst:106
msgid "The other options are global and apply to all your websites."
msgstr ""
#: ../../website/publish/multi_website.rst:109
msgid "Manage domain names"
msgstr ""
#: ../../website/publish/multi_website.rst:111
msgid "As said earlier, your websites can either share the same domain name or use a specific one. If you share it and want to adapt the content per region, set country groups in the setting of each website. Visitors will be redirected to the right website using Geo IP."
msgstr ""
#: ../../website/publish/multi_website.rst:120
msgid "Geo IP is installed by default in Odoo Online. If you run Odoo on-premise, don’t forget to install *Geoip* library."
msgstr ""
#: ../../website/publish/multi_website.rst:123
msgid "`Read the full documenation about domain names here <https://www.odoo.com/documentation/user/online/website/publish/domain_name.html>`__,"
msgstr ""
#: ../../website/publish/multi_website.rst:126
msgid "Customize the visitor experience"
msgstr ""
#: ../../website/publish/multi_website.rst:129
msgid "The customer experience can be customized very profoundly thanks to the menu \\*Customize\\*. All the visual options available there are specific to each website. Go through the different pages to adapt them to this new audience. Focus on workflows, and automatic pages (eCommerce checkout, blogs, events, etc.) as the number of available options is higher there."
msgstr ""
#: ../../website/publish/multi_website.rst:139
msgid "Publish specific content per website"
msgstr ""
#: ../../website/publish/multi_website.rst:142
msgid "Like static pages, any content created from the front-end (product, blog post, etc.) is always only published in the current website. You can change that from the edit form view in the backend and leave the *Website* field blank. This will publish it in all the websites."
msgstr ""
#: ../../website/publish/multi_website.rst:150
msgid "Here are all the objects that you can link to *either one or all the websites*:"
msgstr ""
#: ../../website/publish/multi_website.rst:153
msgid "Products"
msgstr ""
#: ../../website/publish/multi_website.rst:155
msgid "Product Categories for eCommerce"
msgstr ""
#: ../../website/publish/multi_website.rst:157
msgid "Blogs"
msgstr ""
#: ../../website/publish/multi_website.rst:159
msgid "Slide Channels"
msgstr ""
#: ../../website/publish/multi_website.rst:161
msgid "Forums"
msgstr ""
#: ../../website/publish/multi_website.rst:163
msgid "Events"
msgstr ""
#: ../../website/publish/multi_website.rst:165
msgid "Job Positions"
msgstr ""
#: ../../website/publish/multi_website.rst:168
msgid "When you create the record from the backend and publish it, typically a product or an event, it is made available in all websites."
msgstr ""
#: ../../website/publish/multi_website.rst:172
msgid "Publish a page in all websites"
msgstr ""
#: ../../website/publish/multi_website.rst:174
msgid "A new static page is created and only made available in the current website. You can duplicate it to other websites from :menuselection:`Website --> Configuration → Pages`. To do so, leave the *Website* field empty."
msgstr ""
#: ../../website/publish/multi_website.rst:178
msgid "If you want to duplicate it in just one other website, duplicate the page and set the new website."
msgstr ""
#: ../../website/publish/multi_website.rst:184
msgid "When you edit the page again, the change only affects the current website. A new page is duplicated and tied up to the website. The original page still being linked to all websites."
msgstr ""
#: ../../website/publish/multi_website.rst:189
msgid "By grouping pages by URL in the page manager, you quickly find the original page behind each edited page."
msgstr ""
#: ../../website/publish/multi_website.rst:196
msgid "Multi-companies"
msgstr ""
#: ../../website/publish/multi_website.rst:198
msgid "Each website can be linked to a specific company of your system, in a multi-companies environment."
msgstr ""
#: ../../website/publish/multi_website.rst:204
msgid "With such a configuration, only company-related data appear on the website (products, jobs, events, etc.)."
msgstr ""
#: ../../website/publish/multi_website.rst:207
msgid "Website editors can only view and edit the pages of the records they have access to, typically the ones belonging to their current company (and to their subsidiaries, or child companies in Odoo language). And so is it for visitors."
msgstr ""
#: ../../website/publish/multi_website.rst:213
msgid "If websites are multi-companies, you don’t change company when switching websites. To change the company and see the related content, use the company selector in the menu."
msgstr ""
#: ../../website/publish/multi_website.rst:219
msgid "Configure your eCommerce website"
msgstr ""
#: ../../website/publish/multi_website.rst:221
msgid "eCommerce is a crucial feature in the multi-websites environment. We made it so that the entire flow can be customized to fit the very audience of each website."
msgstr ""
#: ../../website/publish/multi_website.rst:226
msgid "Products only available on one website"
msgstr ""
#: ../../website/publish/multi_website.rst:228
msgid "We already saw earlier how to publish a specific record in only one website. You will find the \\*Website\\* field in the eCommerce tab of the product edit form. Empty means available in all websites."
msgstr ""
#: ../../website/publish/multi_website.rst:236
msgid "Products available on *some* websites"
msgstr ""
#: ../../website/publish/multi_website.rst:238
msgid "To make a product available on some websites, but not all of them, you should duplicate the product for each website."
msgstr ""
#: ../../website/publish/multi_website.rst:241
msgid "If you need a unique reference to manage in your inventory, you should install *Manufacturing\\ and create *Kits* BoMs (bills of materials). Each kit will link each published “virtual” product to the main reference managed in your inventory. That way, any item sold from your website will be converted into the storable item in the delivery order."
msgstr ""
#: ../../website/publish/multi_website.rst:248
msgid "Pricelists"
msgstr ""
#: ../../website/publish/multi_website.rst:250
msgid "To manage specific prices by websites, you can activate *Multiple Sales Prices per Product* in Website settings."
msgstr ""
#: ../../website/publish/multi_website.rst:253
msgid "Then, go to :menuselection:`Website --> Products → Pricelists` to create additional pricelists. Read `Pricelists Documentation <https://www.odoo.com/documentation/user/online/ecommerce/maximizing_revenue/pricing.html>`__,"
msgstr ""
#: ../../website/publish/multi_website.rst:256
msgid "If you need help. Select a website to make a pricelist only available on this website."
msgstr ""
#: ../../website/publish/multi_website.rst:262
msgid "Leaving the field empty means that you make it work in all websites if *Selectable* is selected. Otherwise, it makes it only available for backend operations of Sales and Point of Sale applications."
msgstr ""
#: ../../website/publish/multi_website.rst:267
msgid "Payment Acquirers and Delivery Methods"
msgstr ""
#: ../../website/publish/multi_website.rst:269
msgid "By default, published payment acquirers and delivery methods are deployed in all websites. You could already use specific payment acquirers per country using Geo IP by defining countries in their configuration. Now you can also do it per website by filling in the *Website* field."
msgstr ""
#: ../../website/publish/multi_website.rst:275
msgid "Customer accounts"
msgstr ""
#: ../../website/publish/multi_website.rst:277
msgid "There is a setting to choose how to manage customer accounts in Website settings. You can either allow customers to use one account through all the websites or compel them to create one account for each website. This last option is convenient if your websites shouldn’t be related to each other in the visitor mind."
msgstr ""
#: ../../website/publish/multi_website.rst:287
msgid "Technical hints for customization"
msgstr ""
#: ../../website/publish/multi_website.rst:289
msgid "If you want to publish custom objects on the website, here are a few tips to make it work with multi websites:"
msgstr ""
#: ../../website/publish/multi_website.rst:293
msgid "Sitemap: don’t forget the domain in the route to only publish"
msgstr ""
#: ../../website/publish/multi_website.rst:293
msgid "available records in each website’s sitemap."
msgstr ""
#: ../../website/publish/multi_website.rst:297
msgid "Access: you should call the method"
msgstr ""
#: ../../website/publish/multi_website.rst:296
msgid "*can_access_from_current_website* in the controller to make sure the visitor can see a record in the current website."
msgstr ""
#: ../../website/publish/multi_website.rst:301
msgid "Search: when a list of records is displayed, don’t forget to specify"
msgstr ""
#: ../../website/publish/multi_website.rst:300
msgid "the domain to only display records available for the current website."
msgid "There are two ways to translate your website, you can do it manually or automatically with the Gengo App. If you want to do it automatically, go to the **App** module and Install **Automated translations through Gengo Api** and **Website Gengo Translator**. If you want to do it manually, don't install anything, and follow the next step."
msgid "You will see that Now, next to English there is also French, which means that the page for the translation has been created. You can also see that some of the text has been translated automatically."
msgid "There, if you have installed the Gengo Translator, You will see that next to the **Translate** button you also have a button **Translate automatically**. Once you click on that button, you will be asked some information on your account. If you don't have an account yet, go to `*https://gengo.com/auth/form/login/* <https://gengo.com/auth/form/login/>`__ in order to create one. You need to ask for a public key and a private key."
msgid "Now you can see that most of the content is highlighted in yellow or in green. The yellow represents the content that you have to translate by yourself. The green represents the content that has already been translated automatically."
