# How to get started 1. [Creating your account](#id-1.-creating-your-account) 2. [Creating a new project](#id-2.-creating-a-new-project) 1. [Add project](#id-2.1-add-project) 2. [Verify project](#id-2.2-verify-project) 3. [Syncing your website](#id-3.-syncing-your-website) 1. [Add languages](#id-3.1-add-languages) 2. [Sync pages](#id-3.2-sync-pages) 4. [Translating your website](#id-4.-translating-your-website) 5. [Publishing your website](#id-5.-publishing) 1. [Add custom domain](#id-5.1-add-custom-domain) 2. [Test and go live](#id-5.2-test-and-go-live) ### 1. Creating your account To start using Linguana, you will need to create a new account at . You can sign up with Google or by providing a valid email address and password. ### 2. Creating a new project #### 2.1 Add project
Create new Linguna project
After signing up, you will automatically be prompted to add your first project. When adding a new project, you will need to provide the following information: * **Project name**: for your reference only (your website visitors will never see this) * **Domain URL**: your website domain (this can be a staging subdomain like webflow\.io or framer.app, or your own custom domain) * **Original language**: the language your website is currently written in #### 2.2 Verify project
Add Linguana meta tag
Once you've added your project, you will need to verify it. To do so, just add the provided meta tag to your website's `` section. For example, for Webflow sites, this can be done in *Project Settings -> Custom Code*. By default, you will be provided a staging address on Linguana where you can test your translations. This works just like webflow\.io and framer.app subdomains in Webflow and Framer. ### 3. Syncing your website #### 3.1 Add languages
Add Linguana languages
Now that your project is added and verified, it's time to add the languages that you'd like to translate your site to. Simply click *Add language* in the top right, enter all languages you would like to add, and submit by clicking *Add new languages* in the bottom right. Your project now has new language versions. #### 3.2 Sync pages This step is critical to ensuring you're able to translate your website. Once the new languages have been added, your site still needs to be synced. You'll notice each of the new languages has a *Load* button in place of the page count. You'll have to click this button for each language. Additionally, you'll notice after you load the first language, website crawling will have automatically started. You can monitor the progress in the *Notifications* menu. You'll need to wait for this to finish to translate your website. This shouldn't take more than a few minutes (depending on the size of your website). Keep in mind that if you made any edits to your website, you'll have to re-sync in Linguana for these changes to appear. If you a sync a page (or all pages) for one language, those pages will also be synced in every other language. ### 4. Translating your website
Translate pages on Linguana
Click on the language you wish to start translating, and on the next page you will see a list of all the pages on your website. Pages get imported automatically after crawling your sitemap. If you do not have a sitemap (or if you have any hidden pages), you will need to manually add them by clicking *Import pages* in the top right, entering the page slug, and clicking *Add custom URL*. Each page has a name (usually the page slug, except for the homepage and 404 page), status (*Published* or *Not published*), and an actions menu (where you can sync, translate, publish, unpublish, view, import, export, or delete the page). To translate the text on your page: * Click on page slug * On the left, you'll see the existing source content (text and images) * On the right, there are fields for translated content (text and images) * Once you're done editing the field on the right (either manually or using AI translations), simply click out of the input field or move on to the next one. Linguana will auto-save your translated content. ### 5. Publishing #### 5.1 Add custom domain
Add custom domain on Linguana
By default, you will be able to publish your project to a staging domain (i.e. yourproject.linguana.site). To add a custom domain, simply go to your project settings by expanding the menu right of the *Add language* button, and select *Settings*. There, open the *Custom domains* tab and add a new domain below. Here, you can select if you would like to serve your domain with or without *www* (i.e. [www.domain.com](http://www.domain.com) or just domain.com). This generally does not impact SEO, so it is just a matter of preference. Next, you will need to set up DNS records. To do so, please follow the steps: 1. Remove existing DNS records 2. Add DNS records provided to you in Linguana 3. Remove your custom domain from your website 4. Add linguana subdomain to your website (i.e. linguana.yourdomain.com) 5. Publish your website to linguana subdomain After that is completed and DNS records are propagated, your site should be live. #### 5.2 Test and go live After you translate a page, we suggest you first publish it to the staging *linguana.site* subdomain. After confirming everything is in order, click *Publish* and select the main domain as well. This will publish your translations. *Keep in mind that changes to your site always need to be synced, translated, and published manually.* --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.linguana.io/getting-started/how-to-get-started.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.