> For the complete documentation index, see [llms.txt](https://docs.babelshark.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.babelshark.net/babelshark-basics/project-modes.md). # Project modes ## Project modes Project can work in different modes. The mode determines the following behavior aspects: * project accepts and saves new source strings, * projects translate strings, * web page/app screen is allowed to display the translation, * translation approval is required to display the translation. ### Collect, no translate The project is in the stage of gathering all the content that needs to be translated, but no actual translation is being done at this stage. ### Translate, no display In this mode mode, the content is being collected and translated, but the translated version is not being displayed to the public. ### Display approved only New translations are being done but only approved translations are displayed to your users. ### Translate all live All content is being translated and immediately displayed to the users as soon as it is translated. ### Display approved, do not translate In this mode, no new translations are being made, and only the approved translations are being displayed to the users. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.babelshark.net/babelshark-basics/project-modes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.