add locale settings

docs/advanced-development/pipeline-yaml.mdx

@@ -2,118 +2,6 @@
 sidebar_position: 4
 ---
 
-# YAML для пайплайны
-
-**YAML пайплайна** предоставляет комплексный обзор всей конфигурации вашего пайплайна в формате YAML. Это включает все ноды с их расположением, исполняемым кодом, взаимосвязями и различной технической информацией, которая определяет, как работает пайплайн.
-
-## Доступ к YAML пайплайна
-
-Чтобы получить доступ к конфигурации YAML пайплайна:
-
-1. Нажмите кнопку **More** в интерфейсе пайплайна
-2. Выберите **YAML** из выпадающего меню
-
-![Доступ к YAML пайплайна](../img/pipeline-yaml-1.jpg)
-
-Это откроет редактор YAML, где вы можете его просматривать и изменять.
-
-## Структура YAML
-
-YAML пайплайна следует определенной иерархической структуре:
-
-### 1. Метаданные пайплайна
-```yaml
-name: Pipeline Name
-version: 1
-description: Pipeline description
-readme: {}
-category:
-  _id: category_id
-  title: Category
-```
-
-Этот раздел содержит базовую информацию о пайплайне, включая название, описание и категоризацию.
-
-### 2. Конфигурация запуска
-```yaml
-start:
-  nodes:
-    - first_node_id
-```
-
-Определяет, какая нода служит стартовой точкой для выполнения пайплайна.
-
-### 3. Входы и выходы
-```yaml
-inputs:
-  string1:
-    title: String 1
-    type: string
-    # Параметры входных данных
-
-outputs:
-  json_output:
-    title: JSON
-    type: json
-    # Параметры выходных данных
-```
-
-Здесь определены все входы и выходы для всех нод, размещённые на рабочем пространстве пайплайны.
-
-### 4. Потоки (соединения нод)
-```yaml
-flows:
-  connection_name:
-    from: source_node
-    output: output_parameter
-    to: target_node
-    input: input_parameter
-```
-
-Этот раздел описывает, как данные передаются между нодами, связывая выходы одной ноды с входами другой.
-
-### 5. Конфигурация нод
-```yaml
-nodes:
-  node_id:
-    version: 1
-    title: Node Title
-    source: node|catalog
-    execution: rapid|regular|deferred|protracted
-    script: |
-      // JavaScript код
-    inputs:
-      # Определения входов ноды
-    outputs:
-      # Определения выходов ноды
-    arrange:
-      # Расположение ноды
-```
-
-Каждая нода в пайплайне полностью описана со всеми параметрами и кодом.
-
-## Редактирование и сохранение
-
-При внесении изменений в YAML пайплайна:
-
-1. **Внесите свои изменения** в редакторе YAML
-2. **Нажмите Save** внизу интерфейса
-3. **Проверьте индикатор состояния** - зеленый индикатор "Saved" появится справа, если нет ошибок
-
-![Интерфейс редактора YAML](../img/pipeline-yaml-2.jpg)
-
-Любые синтаксические ошибки или проблемы конфигурации будут выделены, предотвращая операцию сохранения до их устранения.
-
-## Возврат в рабочее пространство пайплайна
-
-Чтобы вернуться в визуальное рабочее пространство пайплайна:
-
-- Нажмите синюю кнопку **Pipeline** слева в интерфейсе
-
-Это переключит вас обратно в графический редактор пайплайна.
-
---- eng ---
-
 # Pipeline YAML
 
 **Pipeline YAML** provides a comprehensive overview of your entire pipeline configuration in YAML format. This includes all nodes with their positioning, executable code, relationships, and various technical information that defines how the pipeline operates.

i18n/de/code.json

@@ -1,313 +0,0 @@
-{
-  "theme.ErrorPageContent.title": {
-    "message": "This page crashed.",
-    "description": "The title of the fallback page when the page crashed"
-  },
-  "theme.BackToTopButton.buttonAriaLabel": {
-    "message": "Scroll back to top",
-    "description": "The ARIA label for the back to top button"
-  },
-  "theme.blog.archive.title": {
-    "message": "Archive",
-    "description": "The page & hero title of the blog archive page"
-  },
-  "theme.blog.archive.description": {
-    "message": "Archive",
-    "description": "The page & hero description of the blog archive page"
-  },
-  "theme.blog.paginator.navAriaLabel": {
-    "message": "Blog list page navigation",
-    "description": "The ARIA label for the blog pagination"
-  },
-  "theme.blog.paginator.newerEntries": {
-    "message": "Newer entries",
-    "description": "The label used to navigate to the newer blog posts page (previous page)"
-  },
-  "theme.blog.paginator.olderEntries": {
-    "message": "Older entries",
-    "description": "The label used to navigate to the older blog posts page (next page)"
-  },
-  "theme.blog.post.paginator.navAriaLabel": {
-    "message": "Blog post page navigation",
-    "description": "The ARIA label for the blog posts pagination"
-  },
-  "theme.blog.post.paginator.newerPost": {
-    "message": "Newer post",
-    "description": "The blog post button label to navigate to the newer/previous post"
-  },
-  "theme.blog.post.paginator.olderPost": {
-    "message": "Older post",
-    "description": "The blog post button label to navigate to the older/next post"
-  },
-  "theme.tags.tagsPageLink": {
-    "message": "View all tags",
-    "description": "The label of the link targeting the tag list page"
-  },
-  "theme.colorToggle.ariaLabel": {
-    "message": "Switch between dark and light mode (currently {mode})",
-    "description": "The ARIA label for the navbar color mode toggle"
-  },
-  "theme.colorToggle.ariaLabel.mode.dark": {
-    "message": "dark mode",
-    "description": "The name for the dark color mode"
-  },
-  "theme.colorToggle.ariaLabel.mode.light": {
-    "message": "light mode",
-    "description": "The name for the light color mode"
-  },
-  "theme.docs.breadcrumbs.navAriaLabel": {
-    "message": "Breadcrumbs",
-    "description": "The ARIA label for the breadcrumbs"
-  },
-  "theme.docs.DocCard.categoryDescription.plurals": {
-    "message": "1 item|{count} items",
-    "description": "The default description for a category card in the generated index about how many items this category includes"
-  },
-  "theme.docs.paginator.navAriaLabel": {
-    "message": "Docs pages",
-    "description": "The ARIA label for the docs pagination"
-  },
-  "theme.docs.paginator.previous": {
-    "message": "Previous",
-    "description": "The label used to navigate to the previous doc"
-  },
-  "theme.docs.paginator.next": {
-    "message": "Next",
-    "description": "The label used to navigate to the next doc"
-  },
-  "theme.docs.tagDocListPageTitle.nDocsTagged": {
-    "message": "One doc tagged|{count} docs tagged",
-    "description": "Pluralized label for \"{count} docs tagged\". Use as much plural forms (separated by \"|\") as your language support (see https://www.unicode.org/cldr/cldr-aux/charts/34/supplemental/language_plural_rules.html)"
-  },
-  "theme.docs.tagDocListPageTitle": {
-    "message": "{nDocsTagged} with \"{tagName}\"",
-    "description": "The title of the page for a docs tag"
-  },
-  "theme.docs.versionBadge.label": {
-    "message": "Version: {versionLabel}"
-  },
-  "theme.docs.versions.unreleasedVersionLabel": {
-    "message": "This is unreleased documentation for {siteTitle} {versionLabel} version.",
-    "description": "The label used to tell the user that he's browsing an unreleased doc version"
-  },
-  "theme.docs.versions.unmaintainedVersionLabel": {
-    "message": "This is documentation for {siteTitle} {versionLabel}, which is no longer actively maintained.",
-    "description": "The label used to tell the user that he's browsing an unmaintained doc version"
-  },
-  "theme.docs.versions.latestVersionSuggestionLabel": {
-    "message": "For up-to-date documentation, see the {latestVersionLink} ({versionLabel}).",
-    "description": "The label used to tell the user to check the latest version"
-  },
-  "theme.docs.versions.latestVersionLinkLabel": {
-    "message": "latest version",
-    "description": "The label used for the latest version suggestion link label"
-  },
-  "theme.common.editThisPage": {
-    "message": "Edit this page",
-    "description": "The link label to edit the current page"
-  },
-  "theme.common.headingLinkTitle": {
-    "message": "Direct link to {heading}",
-    "description": "Title for link to heading"
-  },
-  "theme.lastUpdated.atDate": {
-    "message": " on {date}",
-    "description": "The words used to describe on which date a page has been last updated"
-  },
-  "theme.lastUpdated.byUser": {
-    "message": " by {user}",
-    "description": "The words used to describe by who the page has been last updated"
-  },
-  "theme.lastUpdated.lastUpdatedAtBy": {
-    "message": "Last updated{atDate}{byUser}",
-    "description": "The sentence used to display when a page has been last updated, and by who"
-  },
-  "theme.navbar.mobileVersionsDropdown.label": {
-    "message": "Versions",
-    "description": "The label for the navbar versions dropdown on mobile view"
-  },
-  "theme.NotFound.title": {
-    "message": "Page Not Found",
-    "description": "The title of the 404 page"
-  },
-  "theme.tags.tagsListLabel": {
-    "message": "Tags:",
-    "description": "The label alongside a tag list"
-  },
-  "theme.AnnouncementBar.closeButtonAriaLabel": {
-    "message": "Close",
-    "description": "The ARIA label for close button of announcement bar"
-  },
-  "theme.admonition.caution": {
-    "message": "caution",
-    "description": "The default label used for the Caution admonition (:::caution)"
-  },
-  "theme.admonition.danger": {
-    "message": "danger",
-    "description": "The default label used for the Danger admonition (:::danger)"
-  },
-  "theme.admonition.info": {
-    "message": "info",
-    "description": "The default label used for the Info admonition (:::info)"
-  },
-  "theme.admonition.note": {
-    "message": "note",
-    "description": "The default label used for the Note admonition (:::note)"
-  },
-  "theme.admonition.tip": {
-    "message": "tip",
-    "description": "The default label used for the Tip admonition (:::tip)"
-  },
-  "theme.admonition.warning": {
-    "message": "warning",
-    "description": "The default label used for the Warning admonition (:::warning)"
-  },
-  "theme.blog.sidebar.navAriaLabel": {
-    "message": "Blog recent posts navigation",
-    "description": "The ARIA label for recent posts in the blog sidebar"
-  },
-  "theme.CodeBlock.wordWrapToggle": {
-    "message": "Toggle word wrap",
-    "description": "The title attribute for toggle word wrapping button of code block lines"
-  },
-  "theme.CodeBlock.copied": {
-    "message": "Copied",
-    "description": "The copied button label on code blocks"
-  },
-  "theme.CodeBlock.copyButtonAriaLabel": {
-    "message": "Copy code to clipboard",
-    "description": "The ARIA label for copy code blocks button"
-  },
-  "theme.CodeBlock.copy": {
-    "message": "Copy",
-    "description": "The copy button label on code blocks"
-  },
-  "theme.DocSidebarItem.expandCategoryAriaLabel": {
-    "message": "Expand sidebar category '{label}'",
-    "description": "The ARIA label to expand the sidebar category"
-  },
-  "theme.DocSidebarItem.collapseCategoryAriaLabel": {
-    "message": "Collapse sidebar category '{label}'",
-    "description": "The ARIA label to collapse the sidebar category"
-  },
-  "theme.NavBar.navAriaLabel": {
-    "message": "Main",
-    "description": "The ARIA label for the main navigation"
-  },
-  "theme.navbar.mobileLanguageDropdown.label": {
-    "message": "Languages",
-    "description": "The label for the mobile language switcher dropdown"
-  },
-  "theme.NotFound.p1": {
-    "message": "We could not find what you were looking for.",
-    "description": "The first paragraph of the 404 page"
-  },
-  "theme.NotFound.p2": {
-    "message": "Please contact the owner of the site that linked you to the original URL and let them know their link is broken.",
-    "description": "The 2nd paragraph of the 404 page"
-  },
-  "theme.TOCCollapsible.toggleButtonLabel": {
-    "message": "On this page",
-    "description": "The label used by the button on the collapsible TOC component"
-  },
-  "theme.blog.post.readMore": {
-    "message": "Read more",
-    "description": "The label used in blog post item excerpts to link to full blog posts"
-  },
-  "theme.blog.post.readMoreLabel": {
-    "message": "Read more about {title}",
-    "description": "The ARIA label for the link to full blog posts from excerpts"
-  },
-  "theme.blog.post.readingTime.plurals": {
-    "message": "One min read|{readingTime} min read",
-    "description": "Pluralized label for \"{readingTime} min read\". Use as much plural forms (separated by \"|\") as your language support (see https://www.unicode.org/cldr/cldr-aux/charts/34/supplemental/language_plural_rules.html)"
-  },
-  "theme.docs.breadcrumbs.home": {
-    "message": "Home page",
-    "description": "The ARIA label for the home page in the breadcrumbs"
-  },
-  "theme.docs.sidebar.collapseButtonTitle": {
-    "message": "Collapse sidebar",
-    "description": "The title attribute for collapse button of doc sidebar"
-  },
-  "theme.docs.sidebar.collapseButtonAriaLabel": {
-    "message": "Collapse sidebar",
-    "description": "The title attribute for collapse button of doc sidebar"
-  },
-  "theme.docs.sidebar.navAriaLabel": {
-    "message": "Docs sidebar",
-    "description": "The ARIA label for the sidebar navigation"
-  },
-  "theme.docs.sidebar.closeSidebarButtonAriaLabel": {
-    "message": "Close navigation bar",
-    "description": "The ARIA label for close button of mobile sidebar"
-  },
-  "theme.navbar.mobileSidebarSecondaryMenu.backButtonLabel": {
-    "message": "← Back to main menu",
-    "description": "The label of the back button to return to main menu, inside the mobile navbar sidebar secondary menu (notably used to display the docs sidebar)"
-  },
-  "theme.docs.sidebar.toggleSidebarButtonAriaLabel": {
-    "message": "Toggle navigation bar",
-    "description": "The ARIA label for hamburger menu button of mobile navigation"
-  },
-  "theme.docs.sidebar.expandButtonTitle": {
-    "message": "Expand sidebar",
-    "description": "The ARIA label and title attribute for expand button of doc sidebar"
-  },
-  "theme.docs.sidebar.expandButtonAriaLabel": {
-    "message": "Expand sidebar",
-    "description": "The ARIA label and title attribute for expand button of doc sidebar"
-  },
-  "theme.blog.post.plurals": {
-    "message": "One post|{count} posts",
-    "description": "Pluralized label for \"{count} posts\". Use as much plural forms (separated by \"|\") as your language support (see https://www.unicode.org/cldr/cldr-aux/charts/34/supplemental/language_plural_rules.html)"
-  },
-  "theme.blog.tagTitle": {
-    "message": "{nPosts} tagged with \"{tagName}\"",
-    "description": "The title of the page for a blog tag"
-  },
-  "theme.blog.author.pageTitle": {
-    "message": "{authorName} - {nPosts}",
-    "description": "The title of the page for a blog author"
-  },
-  "theme.blog.authorsList.pageTitle": {
-    "message": "Authors",
-    "description": "The title of the authors page"
-  },
-  "theme.blog.authorsList.viewAll": {
-    "message": "View all authors",
-    "description": "The label of the link targeting the blog authors page"
-  },
-  "theme.blog.author.noPosts": {
-    "message": "This author has not written any posts yet.",
-    "description": "The text for authors with 0 blog post"
-  },
-  "theme.contentVisibility.unlistedBanner.title": {
-    "message": "Unlisted page",
-    "description": "The unlisted content banner title"
-  },
-  "theme.contentVisibility.unlistedBanner.message": {
-    "message": "This page is unlisted. Search engines will not index it, and only users having a direct link can access it.",
-    "description": "The unlisted content banner message"
-  },
-  "theme.contentVisibility.draftBanner.title": {
-    "message": "Draft page",
-    "description": "The draft content banner title"
-  },
-  "theme.contentVisibility.draftBanner.message": {
-    "message": "This page is a draft. It will only be visible in dev and be excluded from the production build.",
-    "description": "The draft content banner message"
-  },
-  "theme.ErrorPageContent.tryAgain": {
-    "message": "Try again",
-    "description": "The label of the button to try again rendering when the React error boundary captures an error"
-  },
-  "theme.common.skipToMainContent": {
-    "message": "Skip to main content",
-    "description": "The skip to content label used for accessibility, allowing to rapidly navigate to main content with keyboard tab/enter navigation"
-  },
-  "theme.tags.tagsPageTitle": {
-    "message": "Tags",
-    "description": "The title of the tag list page"
-  }
-}

i18n/de/docusaurus-plugin-content-blog/2019-05-28-first-blog-post.md

@@ -1,16 +0,0 @@
----
-slug: first-blog-post
-title: First Blog Post
-authors:
-  - slorber
-  - yangshun
-tags:
-  - hola
-  - docusaurus
----
-
-Lorem ipsum dolor sit amet...
-
-<!-- truncate -->
-
-...consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet

i18n/de/docusaurus-plugin-content-blog/2019-05-29-long-blog-post.md

@@ -1,46 +0,0 @@
----
-slug: long-blog-post
-title: Long Blog Post
-authors: yangshun
-tags:
-  - hello
-  - docusaurus
----
-
-This is the summary of a very long blog post,
-
-Use a `<!--` `truncate` `-->` comment to limit blog post size in the list view.
-
-<!-- truncate -->
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet

i18n/de/docusaurus-plugin-content-blog/2021-08-01-mdx-blog-post.mdx

@@ -1,26 +0,0 @@
----
-slug: mdx-blog-post
-title: MDX Blog Post
-authors:
-  - slorber
-tags:
-  - docusaurus
----
-
-Blog posts support [Docusaurus Markdown features](https://docusaurus.io/docs/markdown-features), such as [MDX](https://mdxjs.com/).
-
-:::tip
-
-Use the power of React to create interactive blog posts.
-
-:::
-
-{/* truncate */}
-
-For example, use JSX to create an interactive button:
-
-```js
-<button onClick={() => alert('button clicked!')}>Click me!</button>
-```
-
-<button onClick={() => alert('button clicked!')}>Click me!</button>

i18n/de/docusaurus-plugin-content-blog/2021-08-26-welcome/index.md

@@ -1,34 +0,0 @@
----
-slug: welcome
-title: Welcome
-authors:
-  - slorber
-  - yangshun
-tags:
-  - facebook
-  - hello
-  - docusaurus
----
-
-[Docusaurus blogging features](https://docusaurus.io/docs/blog) are powered by the [blog plugin](https://docusaurus.io/docs/api/plugins/@docusaurus/plugin-content-blog).
-
-Here are a few tips you might find useful.
-
-<!-- truncate -->
-
-Simply add Markdown files (or folders) to the `blog` directory.
-
-Regular blog authors can be added to `authors.yml`.
-
-The blog post date can be extracted from filenames, such as:
-
-- `2019-05-30-welcome.md`
-- `2019-05-30-welcome/index.md`
-
-A blog post folder can be convenient to co-locate blog post images:
-
-![Docusaurus Plushie](./docusaurus-plushie-banner.jpeg)
-
-The blog supports tags as well!
-
-**And if you don't want a blog**: just delete this directory, and use `blog: false` in your Docusaurus config.

i18n/de/docusaurus-plugin-content-blog/authors.yml

@@ -1,22 +0,0 @@
-yangshun:
-  name: Yangshun Tay
-  title: Front End Engineer @ Facebook
-  url: https://github.com/yangshun
-  image_url: https://github.com/yangshun.png
-  page: true
-  socials:
-    x: yangshunz
-    github: yangshun
-slorber:
-  name: Sébastien Lorber
-  title: Docusaurus maintainer
-  url: https://sebastienlorber.com
-  image_url: https://github.com/slorber.png
-  page:
-    # customize the url of the author page at /blog/authors/<permalink>
-    permalink: '/all-sebastien-lorber-articles'
-  socials:
-    x: sebastienlorber
-    linkedin: sebastienlorber
-    github: slorber
-    newsletter: https://thisweekinreact.com

i18n/de/docusaurus-plugin-content-blog/options.json

@@ -1,14 +0,0 @@
-{
-  "title": {
-    "message": "Blog",
-    "description": "The title for the blog used in SEO"
-  },
-  "description": {
-    "message": "Blog",
-    "description": "The description for the blog used in SEO"
-  },
-  "sidebar.title": {
-    "message": "Recent posts",
-    "description": "The label for the left sidebar"
-  }
-}

i18n/de/docusaurus-plugin-content-blog/tags.yml

@@ -1,16 +0,0 @@
-facebook:
-  label: Facebook
-  permalink: /facebook
-  description: Facebook tag description
-hello:
-  label: Hello
-  permalink: /hello
-  description: Hello tag description
-docusaurus:
-  label: Docusaurus
-  permalink: /docusaurus
-  description: Docusaurus tag description
-hola:
-  label: Hola
-  permalink: /hola
-  description: Hola tag description

i18n/de/docusaurus-plugin-content-docs/current.json

@@ -1,18 +0,0 @@
-{
-  "version.label": {
-    "message": "Next",
-    "description": "The label for version current"
-  },
-  "sidebar.tutorialSidebar.category.Tutorial - Basics": {
-    "message": "Tutorial - Basics",
-    "description": "The label for category Tutorial - Basics in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.Tutorial - Basics.link.generated-index.description": {
-    "message": "5 minutes to learn the most important Docusaurus concepts.",
-    "description": "The generated-index page description for category Tutorial - Basics in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.Tutorial - Extras": {
-    "message": "Tutorial - Extras",
-    "description": "The label for category Tutorial - Extras in sidebar tutorialSidebar"
-  }
-}

i18n/de/docusaurus-plugin-content-docs/current/intro.md

@@ -1,47 +0,0 @@
----
-sidebar_position: 1
----
-
-# Tutorial Intro
-
-Let's discover **Piper in less than 5 minutes**.
-
-## Getting Started
-
-Get started by **creating a new site**.
-
-Or **try Docusaurus immediately** with **[docusaurus.new](https://docusaurus.new)**.
-
-### What you'll need
-
-- [Node.js](https://nodejs.org/en/download/) version 18.0 or above:
-  - When installing Node.js, you are recommended to check all checkboxes related to dependencies.
-
-## Generate a new site
-
-Generate a new Docusaurus site using the **classic template**.
-
-The classic template will automatically be added to your project after you run the command:
-
-```bash
-npm init docusaurus@latest my-website classic
-```
-
-You can type this command into Command Prompt, Powershell, Terminal, or any other integrated terminal of your code editor.
-
-The command also installs all necessary dependencies you need to run Docusaurus.
-
-## Start your site
-
-Run the development server:
-
-```bash
-cd my-website
-npm run start
-```
-
-The `cd` command changes the directory you're working with. In order to work with your newly created Docusaurus site, you'll need to navigate the terminal there.
-
-The `npm run start` command builds your website locally and serves it through a development server, ready for you to view at http://localhost:3000/.
-
-Open `docs/intro.md` (this page) and edit some lines: the site **reloads automatically** and displays your changes.

i18n/de/docusaurus-plugin-content-docs/current/tutorial-basics/_category_.json

@@ -1,8 +0,0 @@
-{
-  "label": "Tutorial - Basics",
-  "position": 2,
-  "link": {
-    "type": "generated-index",
-    "description": "5 minutes to learn the most important Docusaurus concepts."
-  }
-}

i18n/de/docusaurus-plugin-content-docs/current/tutorial-basics/congratulations.md

@@ -1,23 +0,0 @@
----
-sidebar_position: 6
----
-
-# Congratulations!
-
-You have just learned the **basics of Docusaurus** and made some changes to the **initial template**.
-
-Docusaurus has **much more to offer**!
-
-Have **5 more minutes**? Take a look at **[versioning](../tutorial-extras/manage-docs-versions.md)** and **[i18n](../tutorial-extras/translate-your-site.md)**.
-
-Anything **unclear** or **buggy** in this tutorial? [Please report it!](https://github.com/facebook/docusaurus/discussions/4610)
-
-## What's next?
-
-- Read the [official documentation](https://docusaurus.io/)
-- Modify your site configuration with [`docusaurus.config.js`](https://docusaurus.io/docs/api/docusaurus-config)
-- Add navbar and footer items with [`themeConfig`](https://docusaurus.io/docs/api/themes/configuration)
-- Add a custom [Design and Layout](https://docusaurus.io/docs/styling-layout)
-- Add a [search bar](https://docusaurus.io/docs/search)
-- Find inspirations in the [Docusaurus showcase](https://docusaurus.io/showcase)
-- Get involved in the [Docusaurus Community](https://docusaurus.io/community/support)

i18n/de/docusaurus-plugin-content-docs/current/tutorial-basics/create-a-blog-post.md

@@ -1,34 +0,0 @@
----
-sidebar_position: 3
----
-
-# Create a Blog Post
-
-Docusaurus creates a **page for each blog post**, but also a **blog index page**, a **tag system**, an **RSS** feed...
-
-## Create your first Post
-
-Create a file at `blog/2021-02-28-greetings.md`:
-
-```md title="blog/2021-02-28-greetings.md"
----
-slug: greetings
-title: Greetings!
-authors:
-  - name: Joel Marcey
-    title: Co-creator of Docusaurus 1
-    url: https://github.com/JoelMarcey
-    image_url: https://github.com/JoelMarcey.png
-  - name: Sébastien Lorber
-    title: Docusaurus maintainer
-    url: https://sebastienlorber.com
-    image_url: https://github.com/slorber.png
-tags: [greetings]
----
-
-Congratulations, you have made your first post!
-
-Feel free to play around and edit this post as much as you like.
-```
-
-A new blog post is now available at [http://localhost:3000/blog/greetings](http://localhost:3000/blog/greetings).

i18n/de/docusaurus-plugin-content-docs/current/tutorial-basics/create-a-document.md

@@ -1,57 +0,0 @@
----
-sidebar_position: 2
----
-
-# Create a Document
-
-Documents are **groups of pages** connected through:
-
-- a **sidebar**
-- **previous/next navigation**
-- **versioning**
-
-## Create your first Doc
-
-Create a Markdown file at `docs/hello.md`:
-
-```md title="docs/hello.md"
-# Hello
-
-This is my **first Docusaurus document**!
-```
-
-A new document is now available at [http://localhost:3000/docs/hello](http://localhost:3000/docs/hello).
-
-## Configure the Sidebar
-
-Docusaurus automatically **creates a sidebar** from the `docs` folder.
-
-Add metadata to customize the sidebar label and position:
-
-```md title="docs/hello.md" {1-4}
----
-sidebar_label: 'Hi!'
-sidebar_position: 3
----
-
-# Hello
-
-This is my **first Docusaurus document**!
-```
-
-It is also possible to create your sidebar explicitly in `sidebars.js`:
-
-```js title="sidebars.js"
-export default {
-  tutorialSidebar: [
-    'intro',
-    // highlight-next-line
-    'hello',
-    {
-      type: 'category',
-      label: 'Tutorial',
-      items: ['tutorial-basics/create-a-document'],
-    },
-  ],
-};
-```

i18n/de/docusaurus-plugin-content-docs/current/tutorial-basics/create-a-page.md

@@ -1,43 +0,0 @@
----
-sidebar_position: 1
----
-
-# Create a Page
-
-Add **Markdown or React** files to `src/pages` to create a **standalone page**:
-
-- `src/pages/index.js` → `localhost:3000/`
-- `src/pages/foo.md` → `localhost:3000/foo`
-- `src/pages/foo/bar.js` → `localhost:3000/foo/bar`
-
-## Create your first React Page
-
-Create a file at `src/pages/my-react-page.js`:
-
-```jsx title="src/pages/my-react-page.js"
-import React from 'react';
-import Layout from '@theme/Layout';
-
-export default function MyReactPage() {
-  return (
-    <Layout>
-      <h1>My React page</h1>
-      <p>This is a React page</p>
-    </Layout>
-  );
-}
-```
-
-A new page is now available at [http://localhost:3000/my-react-page](http://localhost:3000/my-react-page).
-
-## Create your first Markdown Page
-
-Create a file at `src/pages/my-markdown-page.md`:
-
-```mdx title="src/pages/my-markdown-page.md"
-# My Markdown page
-
-This is a Markdown page
-```
-
-A new page is now available at [http://localhost:3000/my-markdown-page](http://localhost:3000/my-markdown-page).

i18n/de/docusaurus-plugin-content-docs/current/tutorial-basics/deploy-your-site.md

@@ -1,31 +0,0 @@
----
-sidebar_position: 5
----
-
-# Deploy your site
-
-Docusaurus is a **static-site-generator** (also called **[Jamstack](https://jamstack.org/)**).
-
-It builds your site as simple **static HTML, JavaScript and CSS files**.
-
-## Build your site
-
-Build your site **for production**:
-
-```bash
-npm run build
-```
-
-The static files are generated in the `build` folder.
-
-## Deploy your site
-
-Test your production build locally:
-
-```bash
-npm run serve
-```
-
-The `build` folder is now served at [http://localhost:3000/](http://localhost:3000/).
-
-You can now deploy the `build` folder **almost anywhere** easily, **for free** or very small cost (read the **[Deployment Guide](https://docusaurus.io/docs/deployment)**).

i18n/de/docusaurus-plugin-content-docs/current/tutorial-basics/markdown-features.mdx

@@ -1,152 +0,0 @@
----
-sidebar_position: 4
----
-
-# Markdown Features
-
-Docusaurus supports **[Markdown](https://daringfireball.net/projects/markdown/syntax)** and a few **additional features**.
-
-## Front Matter
-
-Markdown documents have metadata at the top called [Front Matter](https://jekyllrb.com/docs/front-matter/):
-
-```text title="my-doc.md"
-// highlight-start
----
-id: my-doc-id
-title: My document title
-description: My document description
-slug: /my-custom-url
----
-// highlight-end
-
-## Markdown heading
-
-Markdown text with [links](./hello.md)
-```
-
-## Links
-
-Regular Markdown links are supported, using url paths or relative file paths.
-
-```md
-Let's see how to [Create a page](/create-a-page).
-```
-
-```md
-Let's see how to [Create a page](./create-a-page.md).
-```
-
-**Result:** Let's see how to [Create a page](./create-a-page.md).
-
-## Images
-
-Regular Markdown images are supported.
-
-You can use absolute paths to reference images in the static directory (`static/img/docusaurus.png`):
-
-```md
-![Docusaurus logo](/img/docusaurus.png)
-```
-
-![Docusaurus logo](/img/docusaurus.png)
-
-You can reference images relative to the current file as well. This is particularly useful to colocate images close to the Markdown files using them:
-
-```md
-![Docusaurus logo](./img/docusaurus.png)
-```
-
-## Code Blocks
-
-Markdown code blocks are supported with Syntax highlighting.
-
-````md
-```jsx title="src/components/HelloDocusaurus.js"
-function HelloDocusaurus() {
-  return <h1>Hello, Docusaurus!</h1>;
-}
-```
-````
-
-```jsx title="src/components/HelloDocusaurus.js"
-function HelloDocusaurus() {
-  return <h1>Hello, Docusaurus!</h1>;
-}
-```
-
-## Admonitions
-
-Docusaurus has a special syntax to create admonitions and callouts:
-
-```md
-:::tip My tip
-
-Use this awesome feature option
-
-:::
-
-:::danger Take care
-
-This action is dangerous
-
-:::
-```
-
-:::tip My tip
-
-Use this awesome feature option
-
-:::
-
-:::danger Take care
-
-This action is dangerous
-
-:::
-
-## MDX and React Components
-
-[MDX](https://mdxjs.com/) can make your documentation more **interactive** and allows using any **React components inside Markdown**:
-
-```jsx
-export const Highlight = ({children, color}) => (
-  <span
-    style={{
-      backgroundColor: color,
-      borderRadius: '20px',
-      color: '#fff',
-      padding: '10px',
-      cursor: 'pointer',
-    }}
-    onClick={() => {
-      alert(`You clicked the color ${color} with label ${children}`)
-    }}>
-    {children}
-  </span>
-);
-
-This is <Highlight color="#25c2a0">Docusaurus green</Highlight> !
-
-This is <Highlight color="#1877F2">Facebook blue</Highlight> !
-```
-
-export const Highlight = ({children, color}) => (
-  <span
-    style={{
-      backgroundColor: color,
-      borderRadius: '20px',
-      color: '#fff',
-      padding: '10px',
-      cursor: 'pointer',
-    }}
-    onClick={() => {
-      alert(`You clicked the color ${color} with label ${children}`);
-    }}>
-    {children}
-  </span>
-);
-
-This is <Highlight color="#25c2a0">Docusaurus green</Highlight> !
-
-This is <Highlight color="#1877F2">Facebook blue</Highlight> !

i18n/de/docusaurus-plugin-content-docs/current/tutorial-extras/_category_.json

@@ -1,7 +0,0 @@
-{
-  "label": "Tutorial - Extras",
-  "position": 3,
-  "link": {
-    "type": "generated-index"
-  }
-}

i18n/de/docusaurus-plugin-content-docs/current/tutorial-extras/manage-docs-versions.md

@@ -1,55 +0,0 @@
----
-sidebar_position: 1
----
-
-# Manage Docs Versions
-
-Docusaurus can manage multiple versions of your docs.
-
-## Create a docs version
-
-Release a version 1.0 of your project:
-
-```bash
-npm run docusaurus docs:version 1.0
-```
-
-The `docs` folder is copied into `versioned_docs/version-1.0` and `versions.json` is created.
-
-Your docs now have 2 versions:
-
-- `1.0` at `http://localhost:3000/docs/` for the version 1.0 docs
-- `current` at `http://localhost:3000/docs/next/` for the **upcoming, unreleased docs**
-
-## Add a Version Dropdown
-
-To navigate seamlessly across versions, add a version dropdown.
-
-Modify the `docusaurus.config.js` file:
-
-```js title="docusaurus.config.js"
-export default {
-  themeConfig: {
-    navbar: {
-      items: [
-        // highlight-start
-        {
-          type: 'docsVersionDropdown',
-        },
-        // highlight-end
-      ],
-    },
-  },
-};
-```
-
-The docs version dropdown appears in your navbar:
-
-![Docs Version Dropdown](./img/docsVersionDropdown.png)
-
-## Update an existing version
-
-It is possible to edit versioned docs in their respective folder:
-
-- `versioned_docs/version-1.0/hello.md` updates `http://localhost:3000/docs/hello`
-- `docs/hello.md` updates `http://localhost:3000/docs/next/hello`

i18n/de/docusaurus-plugin-content-docs/current/tutorial-extras/translate-your-site.md

@@ -1,88 +0,0 @@
----
-sidebar_position: 2
----
-
-# Translate your site
-
-Let's translate `docs/intro.md` to French.
-
-## Configure i18n
-
-Modify `docusaurus.config.js` to add support for the `fr` locale:
-
-```js title="docusaurus.config.js"
-export default {
-  i18n: {
-    defaultLocale: 'en',
-    locales: ['en', 'fr'],
-  },
-};
-```
-
-## Translate a doc
-
-Copy the `docs/intro.md` file to the `i18n/fr` folder:
-
-```bash
-mkdir -p i18n/fr/docusaurus-plugin-content-docs/current/
-
-cp docs/intro.md i18n/fr/docusaurus-plugin-content-docs/current/intro.md
-```
-
-Translate `i18n/fr/docusaurus-plugin-content-docs/current/intro.md` in French.
-
-## Start your localized site
-
-Start your site on the French locale:
-
-```bash
-npm run start -- --locale fr
-```
-
-Your localized site is accessible at [http://localhost:3000/fr/](http://localhost:3000/fr/) and the `Getting Started` page is translated.
-
-:::caution
-
-In development, you can only use one locale at a time.
-
-:::
-
-## Add a Locale Dropdown
-
-To navigate seamlessly across languages, add a locale dropdown.
-
-Modify the `docusaurus.config.js` file:
-
-```js title="docusaurus.config.js"
-export default {
-  themeConfig: {
-    navbar: {
-      items: [
-        // highlight-start
-        {
-          type: 'localeDropdown',
-        },
-        // highlight-end
-      ],
-    },
-  },
-};
-```
-
-The locale dropdown now appears in your navbar:
-
-![Locale Dropdown](./img/localeDropdown.png)
-
-## Build your localized site
-
-Build your site for a specific locale:
-
-```bash
-npm run build -- --locale fr
-```
-
-Or build your site to include all the locales at once:
-
-```bash
-npm run build
-```

i18n/de/docusaurus-plugin-content-pages/index.module.css

@@ -1,23 +0,0 @@
-/**
- * CSS files with the .module.css suffix will be treated as CSS modules
- * and scoped locally.
- */
-
-.heroBanner {
-  padding: 4rem 0;
-  text-align: center;
-  position: relative;
-  overflow: hidden;
-}
-
-@media screen and (max-width: 996px) {
-  .heroBanner {
-    padding: 2rem;
-  }
-}
-
-.buttons {
-  display: flex;
-  align-items: center;
-  justify-content: center;
-}

i18n/de/docusaurus-plugin-content-pages/index.tsx

@@ -1,44 +0,0 @@
-import type {ReactNode} from 'react';
-import clsx from 'clsx';
-import Link from '@docusaurus/Link';
-import useDocusaurusContext from '@docusaurus/useDocusaurusContext';
-import Layout from '@theme/Layout';
-import HomepageFeatures from '@site/src/components/HomepageFeatures';
-import Heading from '@theme/Heading';
-
-import styles from './index.module.css';
-
-function HomepageHeader() {
-  const {siteConfig} = useDocusaurusContext();
-  return (
-    <header className={clsx('hero hero--primary', styles.heroBanner)}>
-      <div className="container">
-        <Heading as="h1" className="hero__title">
-          {siteConfig.title}
-        </Heading>
-        <p className="hero__subtitle">{siteConfig.tagline}</p>
-        <div className={styles.buttons}>
-          <Link
-            className="button button--secondary button--lg"
-            to="/docs/intro">
-            Piper Tutorial - 5min
-          </Link>
-        </div>
-      </div>
-    </header>
-  );
-}
-
-export default function Home(): ReactNode {
-  const {siteConfig} = useDocusaurusContext();
-  return (
-    <Layout
-      title={`Hello from ${siteConfig.title}`}
-      description="Description will go into a meta tag in <head />">
-      <HomepageHeader />
-      <main>
-        <HomepageFeatures />
-      </main>
-    </Layout>
-  );
-}

i18n/de/docusaurus-theme-classic/footer.json

@@ -1,42 +0,0 @@
-{
-  "link.title.Docs": {
-    "message": "Docs",
-    "description": "The title of the footer links column with title=Docs in the footer"
-  },
-  "link.title.Community": {
-    "message": "Community",
-    "description": "The title of the footer links column with title=Community in the footer"
-  },
-  "link.title.More": {
-    "message": "More",
-    "description": "The title of the footer links column with title=More in the footer"
-  },
-  "link.item.label.Tutorial": {
-    "message": "Tutorial",
-    "description": "The label of footer link with label=Tutorial linking to /docs/intro"
-  },
-  "link.item.label.Stack Overflow": {
-    "message": "Stack Overflow",
-    "description": "The label of footer link with label=Stack Overflow linking to https://stackoverflow.com/questions/tagged/docusaurus"
-  },
-  "link.item.label.Discord": {
-    "message": "Discord",
-    "description": "The label of footer link with label=Discord linking to https://discordapp.com/invite/docusaurus"
-  },
-  "link.item.label.X": {
-    "message": "X",
-    "description": "The label of footer link with label=X linking to https://x.com/docusaurus"
-  },
-  "link.item.label.Blog": {
-    "message": "Blog",
-    "description": "The label of footer link with label=Blog linking to /blog"
-  },
-  "link.item.label.GitHub": {
-    "message": "GitHub",
-    "description": "The label of footer link with label=GitHub linking to https://github.com/facebook/docusaurus"
-  },
-  "copyright": {
-    "message": "Copyright © 2025 My Piper, Inc. Built with Docusaurus.",
-    "description": "The footer copyright"
-  }
-}

i18n/de/docusaurus-theme-classic/navbar.json

@@ -1,22 +0,0 @@
-{
-  "title": {
-    "message": "Piper.My",
-    "description": "The title in the navbar"
-  },
-  "logo.alt": {
-    "message": "Piper Logo",
-    "description": "The alt text of navbar logo"
-  },
-  "item.label.Tutorials": {
-    "message": "Tutorials",
-    "description": "Navbar item with label Tutorials"
-  },
-  "item.label.Blog": {
-    "message": "Blog",
-    "description": "Navbar item with label Blog"
-  },
-  "item.label.GitHub": {
-    "message": "GitHub",
-    "description": "Navbar item with label GitHub"
-  }
-}

i18n/en/code.json

@@ -1,313 +0,0 @@
-{
-  "theme.ErrorPageContent.title": {
-    "message": "This page crashed.",
-    "description": "The title of the fallback page when the page crashed"
-  },
-  "theme.BackToTopButton.buttonAriaLabel": {
-    "message": "Scroll back to top",
-    "description": "The ARIA label for the back to top button"
-  },
-  "theme.blog.archive.title": {
-    "message": "Archive",
-    "description": "The page & hero title of the blog archive page"
-  },
-  "theme.blog.archive.description": {
-    "message": "Archive",
-    "description": "The page & hero description of the blog archive page"
-  },
-  "theme.blog.paginator.navAriaLabel": {
-    "message": "Blog list page navigation",
-    "description": "The ARIA label for the blog pagination"
-  },
-  "theme.blog.paginator.newerEntries": {
-    "message": "Newer entries",
-    "description": "The label used to navigate to the newer blog posts page (previous page)"
-  },
-  "theme.blog.paginator.olderEntries": {
-    "message": "Older entries",
-    "description": "The label used to navigate to the older blog posts page (next page)"
-  },
-  "theme.blog.post.paginator.navAriaLabel": {
-    "message": "Blog post page navigation",
-    "description": "The ARIA label for the blog posts pagination"
-  },
-  "theme.blog.post.paginator.newerPost": {
-    "message": "Newer post",
-    "description": "The blog post button label to navigate to the newer/previous post"
-  },
-  "theme.blog.post.paginator.olderPost": {
-    "message": "Older post",
-    "description": "The blog post button label to navigate to the older/next post"
-  },
-  "theme.tags.tagsPageLink": {
-    "message": "View all tags",
-    "description": "The label of the link targeting the tag list page"
-  },
-  "theme.colorToggle.ariaLabel": {
-    "message": "Switch between dark and light mode (currently {mode})",
-    "description": "The ARIA label for the navbar color mode toggle"
-  },
-  "theme.colorToggle.ariaLabel.mode.dark": {
-    "message": "dark mode",
-    "description": "The name for the dark color mode"
-  },
-  "theme.colorToggle.ariaLabel.mode.light": {
-    "message": "light mode",
-    "description": "The name for the light color mode"
-  },
-  "theme.docs.breadcrumbs.navAriaLabel": {
-    "message": "Breadcrumbs",
-    "description": "The ARIA label for the breadcrumbs"
-  },
-  "theme.docs.DocCard.categoryDescription.plurals": {
-    "message": "1 item|{count} items",
-    "description": "The default description for a category card in the generated index about how many items this category includes"
-  },
-  "theme.docs.paginator.navAriaLabel": {
-    "message": "Docs pages",
-    "description": "The ARIA label for the docs pagination"
-  },
-  "theme.docs.paginator.previous": {
-    "message": "Previous",
-    "description": "The label used to navigate to the previous doc"
-  },
-  "theme.docs.paginator.next": {
-    "message": "Next",
-    "description": "The label used to navigate to the next doc"
-  },
-  "theme.docs.tagDocListPageTitle.nDocsTagged": {
-    "message": "One doc tagged|{count} docs tagged",
-    "description": "Pluralized label for \"{count} docs tagged\". Use as much plural forms (separated by \"|\") as your language support (see https://www.unicode.org/cldr/cldr-aux/charts/34/supplemental/language_plural_rules.html)"
-  },
-  "theme.docs.tagDocListPageTitle": {
-    "message": "{nDocsTagged} with \"{tagName}\"",
-    "description": "The title of the page for a docs tag"
-  },
-  "theme.docs.versionBadge.label": {
-    "message": "Version: {versionLabel}"
-  },
-  "theme.docs.versions.unreleasedVersionLabel": {
-    "message": "This is unreleased documentation for {siteTitle} {versionLabel} version.",
-    "description": "The label used to tell the user that he's browsing an unreleased doc version"
-  },
-  "theme.docs.versions.unmaintainedVersionLabel": {
-    "message": "This is documentation for {siteTitle} {versionLabel}, which is no longer actively maintained.",
-    "description": "The label used to tell the user that he's browsing an unmaintained doc version"
-  },
-  "theme.docs.versions.latestVersionSuggestionLabel": {
-    "message": "For up-to-date documentation, see the {latestVersionLink} ({versionLabel}).",
-    "description": "The label used to tell the user to check the latest version"
-  },
-  "theme.docs.versions.latestVersionLinkLabel": {
-    "message": "latest version",
-    "description": "The label used for the latest version suggestion link label"
-  },
-  "theme.common.editThisPage": {
-    "message": "Edit this page",
-    "description": "The link label to edit the current page"
-  },
-  "theme.common.headingLinkTitle": {
-    "message": "Direct link to {heading}",
-    "description": "Title for link to heading"
-  },
-  "theme.lastUpdated.atDate": {
-    "message": " on {date}",
-    "description": "The words used to describe on which date a page has been last updated"
-  },
-  "theme.lastUpdated.byUser": {
-    "message": " by {user}",
-    "description": "The words used to describe by who the page has been last updated"
-  },
-  "theme.lastUpdated.lastUpdatedAtBy": {
-    "message": "Last updated{atDate}{byUser}",
-    "description": "The sentence used to display when a page has been last updated, and by who"
-  },
-  "theme.navbar.mobileVersionsDropdown.label": {
-    "message": "Versions",
-    "description": "The label for the navbar versions dropdown on mobile view"
-  },
-  "theme.NotFound.title": {
-    "message": "Page Not Found",
-    "description": "The title of the 404 page"
-  },
-  "theme.tags.tagsListLabel": {
-    "message": "Tags:",
-    "description": "The label alongside a tag list"
-  },
-  "theme.AnnouncementBar.closeButtonAriaLabel": {
-    "message": "Close",
-    "description": "The ARIA label for close button of announcement bar"
-  },
-  "theme.admonition.caution": {
-    "message": "caution",
-    "description": "The default label used for the Caution admonition (:::caution)"
-  },
-  "theme.admonition.danger": {
-    "message": "danger",
-    "description": "The default label used for the Danger admonition (:::danger)"
-  },
-  "theme.admonition.info": {
-    "message": "info",
-    "description": "The default label used for the Info admonition (:::info)"
-  },
-  "theme.admonition.note": {
-    "message": "note",
-    "description": "The default label used for the Note admonition (:::note)"
-  },
-  "theme.admonition.tip": {
-    "message": "tip",
-    "description": "The default label used for the Tip admonition (:::tip)"
-  },
-  "theme.admonition.warning": {
-    "message": "warning",
-    "description": "The default label used for the Warning admonition (:::warning)"
-  },
-  "theme.blog.sidebar.navAriaLabel": {
-    "message": "Blog recent posts navigation",
-    "description": "The ARIA label for recent posts in the blog sidebar"
-  },
-  "theme.CodeBlock.wordWrapToggle": {
-    "message": "Toggle word wrap",
-    "description": "The title attribute for toggle word wrapping button of code block lines"
-  },
-  "theme.CodeBlock.copied": {
-    "message": "Copied",
-    "description": "The copied button label on code blocks"
-  },
-  "theme.CodeBlock.copyButtonAriaLabel": {
-    "message": "Copy code to clipboard",
-    "description": "The ARIA label for copy code blocks button"
-  },
-  "theme.CodeBlock.copy": {
-    "message": "Copy",
-    "description": "The copy button label on code blocks"
-  },
-  "theme.DocSidebarItem.expandCategoryAriaLabel": {
-    "message": "Expand sidebar category '{label}'",
-    "description": "The ARIA label to expand the sidebar category"
-  },
-  "theme.DocSidebarItem.collapseCategoryAriaLabel": {
-    "message": "Collapse sidebar category '{label}'",
-    "description": "The ARIA label to collapse the sidebar category"
-  },
-  "theme.NavBar.navAriaLabel": {
-    "message": "Main",
-    "description": "The ARIA label for the main navigation"
-  },
-  "theme.navbar.mobileLanguageDropdown.label": {
-    "message": "Languages",
-    "description": "The label for the mobile language switcher dropdown"
-  },
-  "theme.NotFound.p1": {
-    "message": "We could not find what you were looking for.",
-    "description": "The first paragraph of the 404 page"
-  },
-  "theme.NotFound.p2": {
-    "message": "Please contact the owner of the site that linked you to the original URL and let them know their link is broken.",
-    "description": "The 2nd paragraph of the 404 page"
-  },
-  "theme.TOCCollapsible.toggleButtonLabel": {
-    "message": "On this page",
-    "description": "The label used by the button on the collapsible TOC component"
-  },
-  "theme.blog.post.readMore": {
-    "message": "Read more",
-    "description": "The label used in blog post item excerpts to link to full blog posts"
-  },
-  "theme.blog.post.readMoreLabel": {
-    "message": "Read more about {title}",
-    "description": "The ARIA label for the link to full blog posts from excerpts"
-  },
-  "theme.blog.post.readingTime.plurals": {
-    "message": "One min read|{readingTime} min read",
-    "description": "Pluralized label for \"{readingTime} min read\". Use as much plural forms (separated by \"|\") as your language support (see https://www.unicode.org/cldr/cldr-aux/charts/34/supplemental/language_plural_rules.html)"
-  },
-  "theme.docs.breadcrumbs.home": {
-    "message": "Home page",
-    "description": "The ARIA label for the home page in the breadcrumbs"
-  },
-  "theme.docs.sidebar.collapseButtonTitle": {
-    "message": "Collapse sidebar",
-    "description": "The title attribute for collapse button of doc sidebar"
-  },
-  "theme.docs.sidebar.collapseButtonAriaLabel": {
-    "message": "Collapse sidebar",
-    "description": "The title attribute for collapse button of doc sidebar"
-  },
-  "theme.docs.sidebar.navAriaLabel": {
-    "message": "Docs sidebar",
-    "description": "The ARIA label for the sidebar navigation"
-  },
-  "theme.docs.sidebar.closeSidebarButtonAriaLabel": {
-    "message": "Close navigation bar",
-    "description": "The ARIA label for close button of mobile sidebar"
-  },
-  "theme.navbar.mobileSidebarSecondaryMenu.backButtonLabel": {
-    "message": "← Back to main menu",
-    "description": "The label of the back button to return to main menu, inside the mobile navbar sidebar secondary menu (notably used to display the docs sidebar)"
-  },
-  "theme.docs.sidebar.toggleSidebarButtonAriaLabel": {
-    "message": "Toggle navigation bar",
-    "description": "The ARIA label for hamburger menu button of mobile navigation"
-  },
-  "theme.docs.sidebar.expandButtonTitle": {
-    "message": "Expand sidebar",
-    "description": "The ARIA label and title attribute for expand button of doc sidebar"
-  },
-  "theme.docs.sidebar.expandButtonAriaLabel": {
-    "message": "Expand sidebar",
-    "description": "The ARIA label and title attribute for expand button of doc sidebar"
-  },
-  "theme.blog.post.plurals": {
-    "message": "One post|{count} posts",
-    "description": "Pluralized label for \"{count} posts\". Use as much plural forms (separated by \"|\") as your language support (see https://www.unicode.org/cldr/cldr-aux/charts/34/supplemental/language_plural_rules.html)"
-  },
-  "theme.blog.tagTitle": {
-    "message": "{nPosts} tagged with \"{tagName}\"",
-    "description": "The title of the page for a blog tag"
-  },
-  "theme.blog.author.pageTitle": {
-    "message": "{authorName} - {nPosts}",
-    "description": "The title of the page for a blog author"
-  },
-  "theme.blog.authorsList.pageTitle": {
-    "message": "Authors",
-    "description": "The title of the authors page"
-  },
-  "theme.blog.authorsList.viewAll": {
-    "message": "View all authors",
-    "description": "The label of the link targeting the blog authors page"
-  },
-  "theme.blog.author.noPosts": {
-    "message": "This author has not written any posts yet.",
-    "description": "The text for authors with 0 blog post"
-  },
-  "theme.contentVisibility.unlistedBanner.title": {
-    "message": "Unlisted page",
-    "description": "The unlisted content banner title"
-  },
-  "theme.contentVisibility.unlistedBanner.message": {
-    "message": "This page is unlisted. Search engines will not index it, and only users having a direct link can access it.",
-    "description": "The unlisted content banner message"
-  },
-  "theme.contentVisibility.draftBanner.title": {
-    "message": "Draft page",
-    "description": "The draft content banner title"
-  },
-  "theme.contentVisibility.draftBanner.message": {
-    "message": "This page is a draft. It will only be visible in dev and be excluded from the production build.",
-    "description": "The draft content banner message"
-  },
-  "theme.ErrorPageContent.tryAgain": {
-    "message": "Try again",
-    "description": "The label of the button to try again rendering when the React error boundary captures an error"
-  },
-  "theme.common.skipToMainContent": {
-    "message": "Skip to main content",
-    "description": "The skip to content label used for accessibility, allowing to rapidly navigate to main content with keyboard tab/enter navigation"
-  },
-  "theme.tags.tagsPageTitle": {
-    "message": "Tags",
-    "description": "The title of the tag list page"
-  }
-}

i18n/en/docusaurus-plugin-content-blog/options.json

@@ -1,14 +0,0 @@
-{
-  "title": {
-    "message": "Blog",
-    "description": "The title for the blog used in SEO"
-  },
-  "description": {
-    "message": "Blog",
-    "description": "The description for the blog used in SEO"
-  },
-  "sidebar.title": {
-    "message": "Recent posts",
-    "description": "The label for the left sidebar"
-  }
-}

i18n/en/docusaurus-plugin-content-docs/current.json

@@ -1,38 +0,0 @@
-{
-  "version.label": {
-    "message": "Next",
-    "description": "The label for version current"
-  },
-  "sidebar.tutorialSidebar.category.Tutorial - Basics": {
-    "message": "Tutorial - Basics",
-    "description": "The label for category Tutorial - Basics in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.Tutorial - Basics.link.generated-index.description": {
-    "message": "5 minutes to learn the most important Docusaurus concepts.",
-    "description": "The generated-index page description for category Tutorial - Basics in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.Tutorial - Extras": {
-    "message": "Tutorial - Extras",
-    "description": "The label for category Tutorial - Extras in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.Pipeline Basics": {
-    "message": "Pipeline Basics",
-    "description": "The label for category Pipeline Basics in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.Pipeline Basics.link.generated-index.description": {
-    "message": "5 minutes to learn the most important Docusaurus concepts.",
-    "description": "The generated-index page description for category Pipeline Basics in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.Advanced development": {
-    "message": "Advanced development",
-    "description": "The label for category Advanced development in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.Deploy pipelines & API": {
-    "message": "Deploy pipelines & API",
-    "description": "The label for category Deploy pipelines & API in sidebar tutorialSidebar"
-  },
-  "sidebar.tutorialSidebar.category.Deploy pipelines & API.link.generated-index.description": {
-    "message": "Simply deploy your pipelines & call via API.",
-    "description": "The generated-index page description for category Deploy pipelines & API in sidebar tutorialSidebar"
-  }
-}

i18n/en/docusaurus-plugin-content-pages/index.module.css

@@ -1,23 +0,0 @@
-/**
- * CSS files with the .module.css suffix will be treated as CSS modules
- * and scoped locally.
- */
-
-.heroBanner {
-  padding: 4rem 0;
-  text-align: center;
-  position: relative;
-  overflow: hidden;
-}
-
-@media screen and (max-width: 996px) {
-  .heroBanner {
-    padding: 2rem;
-  }
-}
-
-.buttons {
-  display: flex;
-  align-items: center;
-  justify-content: center;
-}

i18n/en/docusaurus-plugin-content-pages/index.tsx

@@ -1,44 +0,0 @@
-import type {ReactNode} from 'react';
-import clsx from 'clsx';
-import Link from '@docusaurus/Link';
-import useDocusaurusContext from '@docusaurus/useDocusaurusContext';
-import Layout from '@theme/Layout';
-import HomepageFeatures from '@site/src/components/HomepageFeatures';
-import Heading from '@theme/Heading';
-
-import styles from './index.module.css';
-
-function HomepageHeader() {
-  const {siteConfig} = useDocusaurusContext();
-  return (
-    <header className={clsx('hero hero--primary', styles.heroBanner)}>
-      <div className="container">
-        <Heading as="h1" className="hero__title">
-          {siteConfig.title}
-        </Heading>
-        <p className="hero__subtitle">{siteConfig.tagline}</p>
-        <div className={styles.buttons}>
-          <Link
-            className="button button--secondary button--lg"
-            to="/docs/intro">
-            Create First Pipeline
-          </Link>
-        </div>
-      </div>
-    </header>
-  );
-}
-
-export default function Home(): ReactNode {
-  const {siteConfig} = useDocusaurusContext();
-  return (
-    <Layout
-      title={`Hello from ${siteConfig.title}`}
-      description="Description will go into a meta tag in <head />">
-      <HomepageHeader />
-      <main>
-        <HomepageFeatures />
-      </main>
-    </Layout>
-  );
-}

i18n/en/docusaurus-theme-classic/footer.json

@@ -1,42 +0,0 @@
-{
-  "link.title.Docs": {
-    "message": "Docs",
-    "description": "The title of the footer links column with title=Docs in the footer"
-  },
-  "link.title.Community": {
-    "message": "Community",
-    "description": "The title of the footer links column with title=Community in the footer"
-  },
-  "link.title.More": {
-    "message": "More",
-    "description": "The title of the footer links column with title=More in the footer"
-  },
-  "link.item.label.Tutorial": {
-    "message": "Tutorial",
-    "description": "The label of footer link with label=Tutorial linking to /docs/intro"
-  },
-  "link.item.label.Stack Overflow": {
-    "message": "Stack Overflow",
-    "description": "The label of footer link with label=Stack Overflow linking to https://stackoverflow.com/questions/tagged/docusaurus"
-  },
-  "link.item.label.Discord": {
-    "message": "Discord",
-    "description": "The label of footer link with label=Discord linking to https://discordapp.com/invite/docusaurus"
-  },
-  "link.item.label.X": {
-    "message": "X",
-    "description": "The label of footer link with label=X linking to https://x.com/docusaurus"
-  },
-  "link.item.label.Blog": {
-    "message": "Blog",
-    "description": "The label of footer link with label=Blog linking to /blog"
-  },
-  "link.item.label.GitHub": {
-    "message": "GitHub",
-    "description": "The label of footer link with label=GitHub linking to https://github.com/facebook/docusaurus"
-  },
-  "copyright": {
-    "message": "Copyright © 2025 My Piper, Inc. Built with Docusaurus.",
-    "description": "The footer copyright"
-  }
-}

i18n/en/docusaurus-theme-classic/navbar.json

@@ -1,22 +0,0 @@
-{
-  "title": {
-    "message": "Piper.My",
-    "description": "The title in the navbar"
-  },
-  "logo.alt": {
-    "message": "Piper Logo",
-    "description": "The alt text of navbar logo"
-  },
-  "item.label.Tutorials": {
-    "message": "Tutorials",
-    "description": "Navbar item with label Tutorials"
-  },
-  "item.label.Blog": {
-    "message": "Blog",
-    "description": "Navbar item with label Blog"
-  },
-  "item.label.GitHub": {
-    "message": "GitHub",
-    "description": "Navbar item with label GitHub"
-  }
-}

i18n/ru/code.json

@@ -75,6 +75,9 @@
     "message": "Next",
     "description": "The label used to navigate to the next doc"
   },
+  "theme.docs.versionBadge.label": {
+    "message": "Version: {versionLabel}"
+  },
   "theme.docs.tagDocListPageTitle.nDocsTagged": {
     "message": "One doc tagged|{count} docs tagged",
     "description": "Pluralized label for \"{count} docs tagged\". Use as much plural forms (separated by \"|\") as your language support (see https://www.unicode.org/cldr/cldr-aux/charts/34/supplemental/language_plural_rules.html)"
@@ -83,9 +86,6 @@
     "message": "{nDocsTagged} with \"{tagName}\"",
     "description": "The title of the page for a docs tag"
   },
-  "theme.docs.versionBadge.label": {
-    "message": "Version: {versionLabel}"
-  },
   "theme.docs.versions.unreleasedVersionLabel": {
     "message": "This is unreleased documentation for {siteTitle} {versionLabel} version.",
     "description": "The label used to tell the user that he's browsing an unreleased doc version"
@@ -102,14 +102,14 @@
     "message": "latest version",
     "description": "The label used for the latest version suggestion link label"
   },
-  "theme.common.editThisPage": {
-    "message": "Edit this page",
-    "description": "The link label to edit the current page"
-  },
   "theme.common.headingLinkTitle": {
     "message": "Direct link to {heading}",
     "description": "Title for link to heading"
   },
+  "theme.common.editThisPage": {
+    "message": "Edit this page",
+    "description": "The link label to edit the current page"
+  },
   "theme.lastUpdated.atDate": {
     "message": " on {date}",
     "description": "The words used to describe on which date a page has been last updated"
@@ -134,10 +134,6 @@
     "message": "Tags:",
     "description": "The label alongside a tag list"
   },
-  "theme.AnnouncementBar.closeButtonAriaLabel": {
-    "message": "Close",
-    "description": "The ARIA label for close button of announcement bar"
-  },
   "theme.admonition.caution": {
     "message": "caution",
     "description": "The default label used for the Caution admonition (:::caution)"
@@ -162,6 +158,10 @@
     "message": "warning",
     "description": "The default label used for the Warning admonition (:::warning)"
   },
+  "theme.AnnouncementBar.closeButtonAriaLabel": {
+    "message": "Close",
+    "description": "The ARIA label for close button of announcement bar"
+  },
   "theme.blog.sidebar.navAriaLabel": {
     "message": "Blog recent posts navigation",
     "description": "The ARIA label for recent posts in the blog sidebar"
@@ -222,10 +222,6 @@
     "message": "One min read|{readingTime} min read",
     "description": "Pluralized label for \"{readingTime} min read\". Use as much plural forms (separated by \"|\") as your language support (see https://www.unicode.org/cldr/cldr-aux/charts/34/supplemental/language_plural_rules.html)"
   },
-  "theme.docs.breadcrumbs.home": {
-    "message": "Home page",
-    "description": "The ARIA label for the home page in the breadcrumbs"
-  },
   "theme.docs.sidebar.collapseButtonTitle": {
     "message": "Collapse sidebar",
     "description": "The title attribute for collapse button of doc sidebar"
@@ -238,6 +234,10 @@
     "message": "Docs sidebar",
     "description": "The ARIA label for the sidebar navigation"
   },
+  "theme.docs.breadcrumbs.home": {
+    "message": "Home page",
+    "description": "The ARIA label for the home page in the breadcrumbs"
+  },
   "theme.docs.sidebar.closeSidebarButtonAriaLabel": {
     "message": "Close navigation bar",
     "description": "The ARIA label for close button of mobile sidebar"

i18n/ru/docusaurus-plugin-content-blog/2019-05-28-first-blog-post.md

@@ -1,16 +0,0 @@
----
-slug: first-blog-post
-title: First Blog Post
-authors:
-  - slorber
-  - yangshun
-tags:
-  - hola
-  - docusaurus
----
-
-Lorem ipsum dolor sit amet...
-
-<!-- truncate -->
-
-...consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet

i18n/ru/docusaurus-plugin-content-blog/2019-05-29-long-blog-post.md

@@ -1,46 +0,0 @@
----
-slug: long-blog-post
-title: Long Blog Post
-authors: yangshun
-tags:
-  - hello
-  - docusaurus
----
-
-This is the summary of a very long blog post,
-
-Use a `<!--` `truncate` `-->` comment to limit blog post size in the list view.
-
-<!-- truncate -->
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet
-
-Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque elementum dignissim ultricies. Fusce rhoncus ipsum tempor eros aliquam consequat. Lorem ipsum dolor sit amet

i18n/ru/docusaurus-plugin-content-blog/2021-08-01-mdx-blog-post.mdx

@@ -1,26 +0,0 @@
----
-slug: mdx-blog-post
-title: MDX Blog Post
-authors:
-  - slorber
-tags:
-  - docusaurus
----
-
-Blog posts support [Docusaurus Markdown features](https://docusaurus.io/docs/markdown-features), such as [MDX](https://mdxjs.com/).
-
-:::tip
-
-Use the power of React to create interactive blog posts.
-
-:::
-
-{/* truncate */}
-
-For example, use JSX to create an interactive button:
-
-```js
-<button onClick={() => alert('button clicked!')}>Click me!</button>
-```
-
-<button onClick={() => alert('button clicked!')}>Click me!</button>

i18n/ru/docusaurus-plugin-content-blog/2021-08-26-welcome/index.md

@@ -1,34 +0,0 @@
----
-slug: welcome
-title: Welcome
-authors:
-  - slorber
-  - yangshun
-tags:
-  - facebook
-  - hello
-  - docusaurus
----
-
-[Docusaurus blogging features](https://docusaurus.io/docs/blog) are powered by the [blog plugin](https://docusaurus.io/docs/api/plugins/@docusaurus/plugin-content-blog).
-
-Here are a few tips you might find useful.
-
-<!-- truncate -->
-
-Simply add Markdown files (or folders) to the `blog` directory.
-
-Regular blog authors can be added to `authors.yml`.
-
-The blog post date can be extracted from filenames, such as:
-
-- `2019-05-30-welcome.md`
-- `2019-05-30-welcome/index.md`
-
-A blog post folder can be convenient to co-locate blog post images:
-
-![Docusaurus Plushie](./docusaurus-plushie-banner.jpeg)
-
-The blog supports tags as well!
-
-**And if you don't want a blog**: just delete this directory, and use `blog: false` in your Docusaurus config.

i18n/ru/docusaurus-plugin-content-blog/authors.yml

@@ -1,22 +0,0 @@
-yangshun:
-  name: Yangshun Tay
-  title: Front End Engineer @ Facebook
-  url: https://github.com/yangshun
-  image_url: https://github.com/yangshun.png
-  page: true
-  socials:
-    x: yangshunz
-    github: yangshun
-slorber:
-  name: Sébastien Lorber
-  title: Docusaurus maintainer
-  url: https://sebastienlorber.com
-  image_url: https://github.com/slorber.png
-  page:
-    # customize the url of the author page at /blog/authors/<permalink>
-    permalink: '/all-sebastien-lorber-articles'
-  socials:
-    x: sebastienlorber
-    linkedin: sebastienlorber
-    github: slorber
-    newsletter: https://thisweekinreact.com

i18n/ru/docusaurus-plugin-content-blog/tags.yml

@@ -1,16 +0,0 @@
-facebook:
-  label: Facebook
-  permalink: /facebook
-  description: Facebook tag description
-hello:
-  label: Hello
-  permalink: /hello
-  description: Hello tag description
-docusaurus:
-  label: Docusaurus
-  permalink: /docusaurus
-  description: Docusaurus tag description
-hola:
-  label: Hola
-  permalink: /hola
-  description: Hola tag description

i18n/ru/docusaurus-plugin-content-docs/current.json

@@ -3,16 +3,28 @@
     "message": "Next",
     "description": "The label for version current"
   },
-  "sidebar.tutorialSidebar.category.Tutorial - Basics": {
-    "message": "Tutorial - Basics",
-    "description": "The label for category Tutorial - Basics in sidebar tutorialSidebar"
+  "sidebar.tutorialSidebar.category.Pipeline Basics": {
+    "message": "Pipeline Basics",
+    "description": "The label for category Pipeline Basics in sidebar tutorialSidebar"
   },
-  "sidebar.tutorialSidebar.category.Tutorial - Basics.link.generated-index.description": {
+  "sidebar.tutorialSidebar.category.Pipeline Basics.link.generated-index.description": {
     "message": "5 minutes to learn the most important Docusaurus concepts.",
-    "description": "The generated-index page description for category Tutorial - Basics in sidebar tutorialSidebar"
+    "description": "The generated-index page description for category Pipeline Basics in sidebar tutorialSidebar"
   },
-  "sidebar.tutorialSidebar.category.Tutorial - Extras": {
-    "message": "Tutorial - Extras",
-    "description": "The label for category Tutorial - Extras in sidebar tutorialSidebar"
+  "sidebar.tutorialSidebar.category.Creating Pipelines": {
+    "message": "Creating Pipelines",
+    "description": "The label for category Creating Pipelines in sidebar tutorialSidebar"
+  },
+  "sidebar.tutorialSidebar.category.Advanced development": {
+    "message": "Advanced development",
+    "description": "The label for category Advanced development in sidebar tutorialSidebar"
+  },
+  "sidebar.tutorialSidebar.category.Deploy pipelines & API": {
+    "message": "Deploy pipelines & API",
+    "description": "The label for category Deploy pipelines & API in sidebar tutorialSidebar"
+  },
+  "sidebar.tutorialSidebar.category.Deploy pipelines & API.link.generated-index.description": {
+    "message": "Simply deploy your pipelines & call via API.",
+    "description": "The generated-index page description for category Deploy pipelines & API in sidebar tutorialSidebar"
   }
 }

i18n/ru/docusaurus-plugin-content-docs/current/{tutorial-extras → advanced-development}/_category_.json

@@ -1,6 +1,6 @@
 {
-  "label": "Tutorial - Extras",
-  "position": 3,
+  "label": "Advanced development",
+  "position": 4,
   "link": {
     "type": "generated-index"
   }

i18n/ru/docusaurus-plugin-content-docs/current/advanced-development/creating-custom-node.mdx

@@ -0,0 +1,205 @@
+---
+sidebar_position: 1
+---
+
+# Создание кастомной ноды
+
+Создание кастомных нод позволяет обойти ограничения, которые связаны со стандартной библиотекой нод Piper, или же даже просто улучшить функционал текущих нод.
+
+Давайте создадим кастомную ноду **Merge text to JSON**, которая принимает несколько текстовых строк и объединяет их в один JSON массив.
+
+## **1. Загрузка ноды из библиотеки нод**
+
+Для создания кастомной ноды начните с загрузки существующей ноды, которая наиболее близка к вашим требованиям. Перейдите в библиотеку нод, используя значок **плюс (+)** в верхнем левом углу рабочего пространства пайплайны и выберите ноду **Input Text** для модификации, поскольку в ней минимум кода и она работает со строками.
+
+После добавления ноды откройте её настройки.
+
+![Панель настроек ноды](../img/create-node-1.png)
+
+Панель настроек включает несколько вкладок:
+
+- **Inputs** - Текущие параметры ноды, их настройка, загрузка изображений
+- **Design** - Создание входных и выходных параметров, определение их свойств
+- **Script** - Редактирование кода JavaScript, логика ноды
+- **Environment** - Настройка переменных окружения
+- **Catalog** - Просмотр метаданных ноды и её публикация
+- **YAML** - Доступ к YAML ноды
+
+## **2. Настройка ноды**
+
+Кастомизация начинается со вкладки **Design**, где определяется структура ноды.
+
+![Вкладка Design](../img/create-node-2.png)
+
+### Основные свойства
+- **ID** - Внутреннее имя, используемое в коде (строчные латинские буквы, без пробелов)
+- **Title** - Отображаемое имя, видимое пользователю
+
+Для нашей ноды прежние значения необходимо заменить на:
+- ID: `merge_text_to_json`
+- Title: `Merge text to JSON`
+
+### Добавление входных параметров
+
+Нашей ноде нужно 4 строковых входа. Чтобы добавить новый вход:
+
+1. Раскройте меню-гамбургер **Inputs**
+2. Введите имя нового входа: `string1`
+3. Нажмите **Add**
+
+![Добавление нового входного параметра](../img/create-node-3.png)
+
+Настройте параметры входа:
+- **Type**: string (то есть текст)
+- **Title**: String 1 (название, отображаемое на ноде)
+
+![Настройка свойств входа](../img/create-node-4.png)
+
+Повторите этот процесс для создания входов `string2`, `string3` и `string4`.
+
+Чтобы удалить прежний входной параметр `input_text`, снимите галочку с него в меню Inputs.
+
+![Удаление оригинального входа](../img/create-node-5.png)
+
+Если визуально изменения не произошли, нужно временно открыть другую вкладку и потом вернуться в Design.
+
+### Расширенные настройки входных параметров
+
+Доступ к детальным настройкам входных параметров открывается через меню-гамбургер. 
+
+![Выпадающее меню настроек входных параметров](../img/create-node-6.png)
+
+Доступные опции включают:
+
+- **Order** (число) - Задаёт порядок расположения входов в ноде
+- **Description** (текст) - Текст всплывающей подсказки для параметра
+- **Required** (boolean) - True делает параметр обязательным
+- **Group** (текст) - Группирует связанные настройки
+- **Enum** (текст) - Создает выпадающие списки с предопределенными значениями
+- **Multiline** (boolean) - Расширяет поля String для длинного текста
+- **Min, Max** (число) - Устанавливает ограничения для полей Integer
+- **Step** (число) - Преобразует поле Integer в ползунок с шагом, равным значению Step
+- **Default** - Устанавливает значения по умолчанию
+- **Placeholder** (текст) - Показывает подсказку в пустых полях String
+- **Schema** - Техническое поле для скриптов
+- **Extensions** (текст) - Добавляет специальную функциональность (например, draw-mask для задания маски на загруженном изображении)
+
+![Пример конфигурации расширений](../img/create-node-7.png)
+
+### Настройка выходных параметров
+
+Создайте выходной параметр. Для этого удалите прежний выход `output_text` и добавьте новый `json_output` со следующими параметрами:
+- **Type**: JSON
+- **Title**: JSON
+
+Итогое окно Design должно выглядеть примерно так:
+
+![Отредлактированная вкладка Design](../img/create-node-8.png)
+
+:::tip Совет
+Отслеживайте ваши изменения во вкладке **Inputs**, чтобы видеть, как модификации влияют на структуру ноды.
+:::
+
+Про следующий шаг - написание логики скрипта ноды, в разделе **Вкладка Node Script**.
+
+--- eng ---
+
+# Creating Custom Nodes
+
+Creating custom nodes allows you to bypass limitations associated with Piper's standard node library, or even simply improve the functionality of current nodes.
+
+Let's create a custom **Merge text to JSON** node that takes multiple text strings and combines them into a single JSON array.
+
+## **1. Loading a Node from the Node Library**
+
+To create a custom node, start by loading an existing node that's closest to your requirements. Navigate to the node library using the **plus (+)** icon in the top left corner of the pipeline workspace and select the **Input Text** node for modification, since it has minimal code and works with strings.
+
+After adding the node, open its settings.
+
+![Node Settings Panel](../img/create-node-1.png)
+
+The settings panel includes several tabs:
+
+- **Inputs** - Current node parameters, their configuration, image loading
+- **Design** - Creating input and output parameters, defining their properties
+- **Script** - Editing JavaScript code, node logic
+- **Environment** - Configure environment variables
+- **Catalog** - View node metadata and publish it
+- **YAML** - Access the node's YAML
+
+## **2. Node Configuration**
+
+Customization begins in the **Design** tab, where the node structure is defined.
+
+![Design Tab](../img/create-node-2.png)
+
+### Basic Properties
+- **ID** - Internal name used in code (lowercase Latin letters, no spaces)
+- **Title** - Display name visible to the user
+
+For our node, the previous values need to be replaced with:
+- ID: `merge_text_to_json`
+- Title: `Merge text to JSON`
+
+### Adding Input Parameters
+
+Our node needs 4 string inputs. To add a new input:
+
+1. Expand the **Inputs** hamburger menu
+2. Enter the new input name: `string1`
+3. Click **Add**
+
+![Adding New Input Parameter](../img/create-node-3.png)
+
+Configure the input parameters:
+- **Type**: string (i.e., text)
+- **Title**: String 1 (name displayed on the node)
+
+![Configuring Input Properties](../img/create-node-4.png)
+
+Repeat this process to create inputs `string2`, `string3`, and `string4`.
+
+To remove the previous input parameter `input_text`, uncheck it in the Inputs menu.
+
+![Removing Original Input](../img/create-node-5.png)
+
+If no visual changes occur, you need to temporarily open another tab and then return to Design.
+
+### Advanced Input Parameter Settings
+
+Access to detailed settings is opened through the hamburger menu.
+
+![Input Parameter Settings Dropdown Menu](../img/create-node-6.png)
+
+Available options include:
+
+- **Order** (number) - Sets the order of inputs in the node
+- **Description** (text) - Tooltip text for the parameter
+- **Required** (boolean) - True makes the parameter mandatory
+- **Group** (text) - Groups related settings
+- **Enum** (text) - Creates dropdown lists with predefined values
+- **Multiline** (boolean) - Expands String fields for long text
+- **Min, Max** (number) - Sets constraints for Integer fields
+- **Step** (number) - Converts Integer field to slider with step equal to Step value
+- **Default** - Sets default values
+- **Placeholder** (text) - Shows hints in empty String fields
+- **Schema** - Technical field for scripts
+- **Extensions** (text) - Adds special functionality (e.g., draw-mask for setting masks on uploaded images)
+
+![Example Extension Configuration](../img/create-node-7.png)
+
+### Configuring Output Parameters
+
+Create an output parameter. To do this, delete the previous output `output_text` and add a new `json_output` with the following parameters:
+- **Type**: JSON
+- **Title**: JSON
+
+The final Design window should look something like this:
+
+![Edited Design Tab](../img/create-node-8.png)
+
+:::tip Tip
+Monitor your changes in the **Inputs** tab to see how modifications affect the node structure.
+:::
+
+The next step - writing the node's script logic, is covered in the **Node Script Tab** section.

i18n/ru/docusaurus-plugin-content-docs/current/advanced-development/debug-pipelines.mdx

@@ -0,0 +1,7 @@
+---
+sidebar_position: 5
+---
+
+# Debug pipelines
+
+Will be soon here...

i18n/ru/docusaurus-plugin-content-docs/current/advanced-development/node-script.mdx

@@ -0,0 +1,216 @@
+---
+sidebar_position: 2
+---
+
+# Вкладка Script в настройках ноды
+
+Вкладка **Script** предназначена для размещения кода JavaScript, отвечающего за программную логику ноды. Здесь вы определяете, что именно делает ваша нода - обрабатывает ли она текст, вызывает API, трансформирует данные или выполняет вычисления.
+
+![Интерфейс вкладки Script](../img/script_tab.jpg)
+
+## Структура кода
+
+Все ноды Piper, включая кастомные, следуют определенной структуре JavaScript:
+
+```javascript
+export async function run({ inputs }) {
+    const { FatalError, NextNode } = DEFINITIONS;
+    
+    // Ваш код здесь
+    
+    return NextNode.from({ 
+        outputs: { 
+            // Ваши результаты
+        } 
+    });
+}
+```
+
+Эта структура гарантирует, что ваша нода может правильно получать данные от предыдущих нод и передавать результаты следующим в вашем пайплайне.
+
+### Оригинальный код Input Text
+Базовая нода **Input Text** имеет эту простую структуру:
+
+```javascript
+export async function run({ inputs }) {
+    const { FatalError, NextNode } = DEFINITIONS;
+
+    const text = inputs.input_text;
+
+    return NextNode.from({
+        outputs: {
+            output_text: text
+        }
+    });
+}
+```
+
+### Кастомный код Merge Text to JSON
+Нам нужно заменить это логикой, которая обрабатывает несколько строковых входов и создает JSON массив:
+
+```javascript
+export async function run({ inputs }) {
+    const { FatalError, NextNode } = DEFINITIONS;
+
+    const jsonArray = [];
+
+    if (inputs.string1) {
+        jsonArray.push(inputs.string1);
+    }
+    if (inputs.string2) {
+        jsonArray.push(inputs.string2);
+    }
+    if (inputs.string3) {
+        jsonArray.push(inputs.string3);
+    }
+    if (inputs.string4) {
+        jsonArray.push(inputs.string4);
+    }
+
+    return NextNode.from({
+        outputs: {
+            json_output: jsonArray
+        }
+    });
+}
+```
+## Понимание кастомной логики
+
+Кастомный скрипт реализует следующую логику:
+
+1. **Инициализация пустого массива** - `const jsonArray = []` создает пустой массив для хранения наших текстовых строк
+2. **Проверка каждого входа** - Условия `if` проверяют, что каждый вход имеет значение перед добавлением
+3. **Построение массива** - Только непустые входы добавляются в `jsonArray` с помощью `push()`
+4. **Возврат JSON выхода** - Финальный массив возвращается как `json_output`, соответствуя нашей конфигурации во вкладке Design
+
+Этот подход гарантирует, что:
+- Пустые или неопределенные входы игнорируются
+- Только валидные текстовые строки включаются в финальный JSON массив
+- Формат выхода соответствует JSON типу, который мы определили во вкладке Design
+
+## Типы выполнения
+
+Выберите подходящий тип выполнения в зависимости от того, сколько времени требуется вашей ноде для работы:
+
+|    Тип     |   Время     |     Описание          |
+|------------|-------------|-----------------------|
+| Rapid      | 0-20 sec    | Быстрые операции      |
+| Regular    | 21-60 sec   | Стандартная обработка |
+| Deferred   | 60-120 sec  | Сложные операции      |
+| Protracted | 120-300 sec | Тяжелые задачи обработки |
+
+Для нашей ноды **Merge text to JSON** подходит выполнение **Rapid**, поскольку мы только манипулируем текстовыми строками и нет обращений к стороннему сервису по API.
+
+## Сохранение изменений
+
+Всегда сохраняйте изменения в скрипте, нажимая кнопку **Save** внизу интерфейса. Любые изменения в коде следует сохранять по нажатию клавиши Save внизу интерфейса.
+
+Вкладка Script - эт�� ядро функциональности вашей ноды, где вы преобразуете входные данные в выходные с помощью кода JavaScript.
+
+--- eng ---
+
+# Script Tab in Node Settings
+
+The **Script** tab is designed for placing JavaScript code that handles the node's programmatic logic. Here you define what exactly your node does - whether it processes text, calls APIs, transforms data, or performs calculations.
+
+![Script tab interface](../img/script_tab.jpg)
+
+## Code Structure
+
+All Piper nodes, including custom ones, follow a specific JavaScript structure:
+
+```javascript
+export async function run({ inputs }) {
+    const { FatalError, NextNode } = DEFINITIONS;
+    
+    // Your code here
+    
+    return NextNode.from({ 
+        outputs: { 
+            // Your results
+        } 
+    });
+}
+```
+
+This structure ensures that your node can properly receive data from previous nodes and pass results to the next ones in your pipeline.
+
+### Original Input Text Code
+The basic **Input Text** node has this simple structure:
+
+```javascript
+export async function run({ inputs }) {
+    const { FatalError, NextNode } = DEFINITIONS;
+
+    const text = inputs.input_text;
+
+    return NextNode.from({
+        outputs: {
+            output_text: text
+        }
+    });
+}
+```
+
+### Custom Merge Text to JSON Code
+We need to replace this with logic that processes multiple string inputs and creates a JSON array:
+
+```javascript
+export async function run({ inputs }) {
+    const { FatalError, NextNode } = DEFINITIONS;
+
+    const jsonArray = [];
+
+    if (inputs.string1) {
+        jsonArray.push(inputs.string1);
+    }
+    if (inputs.string2) {
+        jsonArray.push(inputs.string2);
+    }
+    if (inputs.string3) {
+        jsonArray.push(inputs.string3);
+    }
+    if (inputs.string4) {
+        jsonArray.push(inputs.string4);
+    }
+
+    return NextNode.from({
+        outputs: {
+            json_output: jsonArray
+        }
+    });
+}
+```
+
+## Understanding Custom Logic
+
+The custom script implements the following logic:
+
+1. **Initialize empty array** - `const jsonArray = []` creates an empty array to store our text strings
+2. **Check each input** - `if` conditions check that each input has a value before adding
+3. **Build array** - Only non-empty inputs are added to `jsonArray` using `push()`
+4. **Return JSON output** - The final array is returned as `json_output`, matching our configuration in the Design tab
+
+This approach ensures that:
+- Empty or undefined inputs are ignored
+- Only valid text strings are included in the final JSON array
+- The output format matches the JSON type we defined in the Design tab
+
+## Execution Types
+
+Choose the appropriate execution type based on how much time your node requires to work:
+
+|    Type    |   Time      |     Description       |
+|------------|-------------|-----------------------|
+| Rapid      | 0-20 sec    | Fast operations       |
+| Regular    | 21-60 sec   | Standard processing   |
+| Deferred   | 60-120 sec  | Complex operations    |
+| Protracted | 120-300 sec | Heavy processing tasks |
+
+For our **Merge text to JSON** node, **Rapid** execution is suitable since we're only manipulating text strings and there are no API calls to external services.
+
+## Saving Changes
+
+Always save changes to the script by clicking the **Save** button at the bottom of the interface. Any changes to the code should be saved by pressing the Save button at the bottom of the interface.
+
+The Script tab is the core of your node's functionality, where you transform input data into output using JavaScript code.

i18n/ru/docusaurus-plugin-content-docs/current/advanced-development/node-yaml.mdx

@@ -0,0 +1,293 @@
+---
+sidebar_position: 3
+---
+
+# Вкладка YAML в настройках ноды
+
+Вкладка **YAML** объединяет все данные из других вкладок (Design, Script, Environment, Catalog) в единое представление, которое определяет всё о вашей ноде - от технических метаданных до её позиции в рабочем пространстве пайплайна.
+
+![Интерфейс вкладки YAML](../img/node-yaml.png)
+
+## Что такое YAML представление?
+
+Вкладка YAML служит "исходным кодом" вашей ноды. Она объединяет:
+
+- Определения входных и выходных данных из вкладки Design
+- JavaScript код из вкладки Script  
+- Технические метаданные из вкладки Catalog
+- Переменные окружения из вкладки Environment
+- Позиционирование ноды и связи внутри пайплайна
+
+Это полное представление позволяет точно дублировать ноды, копируя их YAML конфигурацию в другие пайплайны.
+
+## Структура YAML
+
+YAML конфигурация организована в логические секции:
+
+### Техническая информация
+```yaml
+_id: merge_text_to_json
+version: 1
+category:
+  _id: processing
+  title: en=Processing;ru=Обработка
+package: custom
+title: en=Merge text to JSON;ru=Объединение текста в JSON
+source: node
+execution: regular
+```
+
+Эти поля определяют идентификатор ноды, версию, классификацию по категориям и привязку к пакету.
+
+### Скрипт выполнения
+```yaml
+script: |-
+  export async function run({ inputs }) {
+      const { NextNode } = DEFINITIONS;
+
+      const jsonArray = [];
+
+      if (inputs.string1) {
+          jsonArray.push(inputs.string1);
+      }
+      if (inputs.string2) {
+          jsonArray.push(inputs.string2);
+      }
+      if (inputs.string3) {
+          jsonArray.push(inputs.string3);
+      }
+      if (inputs.string4) {
+          jsonArray.push(inputs.string4);
+      }
+
+      return NextNode.from({
+          outputs: {
+              json_output: jsonArray
+          }
+      });
+  }
+```
+
+Содержит полный кастомный JavaScript код, который мы написали во вкладке Script.
+
+### Позиционирование ноды
+```yaml
+arrange:
+  x: 170
+  y: 290
+```
+
+Определяет точное положение ноды в рабочем пространстве пайплайна.
+
+### Определения входных/выходных данных
+```yaml
+inputs:
+  string1:
+    title: en=String 1;ru=Строка 1
+    type: string
+    required: false
+  string2:
+    title: en=String 2;ru=Строка 2
+    type: string
+    required: false
+  string3:
+    title: en=String 3;ru=Строка 3
+    type: string
+    required: false
+  string4:
+    title: en=String 4;ru=Строка 4
+    type: string
+    required: false
+
+outputs:
+  json_output:
+    title: en=JSON;ru=JSON
+    type: json
+```
+
+Полные спецификации для всех 4 входных параметров и 1 выходного параметра, которые мы настроили во вкладке Design.
+
+### Информация каталога (опционально)
+```yaml
+catalog:
+  _id: merge_text_to_json
+  version: 1
+  category:
+    _id: service_nodes
+    title: Service Nodes
+  package: service_nodes
+```
+
+Метаданные для публикации и организации вашей кастомной ноды в каталоге.
+
+### Переменные окружения (опционально)
+```yaml
+environment:
+  OPEN_PAAS_USER:
+    title: PaaS user
+    type: string
+    scope: global
+```
+
+Все переменные окружения и API ключи, необходимые для подключения ноды к внешним провайдерам.
+
+## Копирование и повторное использование нод
+
+Самая мощная функция вкладки YAML - возможность создания точных дубликатов ноды:
+
+1. **Скопируйте YAML** - Выделите весь код во вкладке YAML и скопируйте его
+2. **Создайте новую ноду** - Добавьте новую ноду в любой пайплайн
+3. **Вставьте конфигурацию** - Замените YAML новой ноды на скопированный код
+4. **Сохраните изменения** - Нода будет воссоздана с идентичной функциональностью
+
+Этот процесс сохраняет все настройки, код и конфигурацию, делая простым повторное использование любых нод в разных пайплайнах.
+
+## Только для чтения
+
+Вкладка YAML в основном предназначена для просмотра и копирования. Хотя вы можете видеть полную конфигурацию ноды здесь, изменения следует вносить через соответствующие вкладки (Script для изменений кода, Design для модификации входных/выходных данных и т.д.), чтобы обеспечить правильную валидацию и форматирование.
+
+--- eng ---
+
+# YAML Tab in Node Settings
+
+The **YAML** tab combines all data from other tabs (Design, Script, Environment, Catalog) into a unified view that defines everything about your node - from technical metadata to its position in the pipeline workspace.
+
+![YAML Tab Interface](../img/node-yaml.png)
+
+## What is the YAML View?
+
+The YAML tab serves as the "source code" of your node. It combines:
+
+- Input and output definitions from the Design tab
+- JavaScript code from the Script tab  
+- Technical metadata from the Catalog tab
+- Environment variables from the Environment tab
+- Node positioning and connections within the pipeline
+
+This complete representation allows you to precisely duplicate nodes by copying their YAML configuration to other pipelines.
+
+## YAML Structure
+
+The YAML configuration is organized into logical sections:
+
+### Technical Information
+```yaml
+_id: merge_text_to_json
+version: 1
+category:
+  _id: processing
+  title: en=Processing;ru=Обработка
+package: custom
+title: en=Merge text to JSON;ru=Объединение текста в JSON
+source: node
+execution: regular
+```
+
+These fields define the node's identifier, version, category classification, and package binding.
+
+### Execution Script
+```yaml
+script: |-
+  export async function run({ inputs }) {
+      const { NextNode } = DEFINITIONS;
+
+      const jsonArray = [];
+
+      if (inputs.string1) {
+          jsonArray.push(inputs.string1);
+      }
+      if (inputs.string2) {
+          jsonArray.push(inputs.string2);
+      }
+      if (inputs.string3) {
+          jsonArray.push(inputs.string3);
+      }
+      if (inputs.string4) {
+          jsonArray.push(inputs.string4);
+      }
+
+      return NextNode.from({
+          outputs: {
+              json_output: jsonArray
+          }
+      });
+  }
+```
+
+Contains the complete custom JavaScript code that we wrote in the Script tab.
+
+### Node Positioning
+```yaml
+arrange:
+  x: 170
+  y: 290
+```
+
+Defines the exact position of the node in the pipeline workspace.
+
+### Input/Output Definitions
+```yaml
+inputs:
+  string1:
+    title: en=String 1;ru=Строка 1
+    type: string
+    required: false
+  string2:
+    title: en=String 2;ru=Строка 2
+    type: string
+    required: false
+  string3:
+    title: en=String 3;ru=Строка 3
+    type: string
+    required: false
+  string4:
+    title: en=String 4;ru=Строка 4
+    type: string
+    required: false
+
+outputs:
+  json_output:
+    title: en=JSON;ru=JSON
+    type: json
+```
+
+Complete specifications for all 4 input parameters and 1 output parameter that we configured in the Design tab.
+
+### Catalog Information (Optional)
+```yaml
+catalog:
+  _id: merge_text_to_json
+  version: 1
+  category:
+    _id: service_nodes
+    title: Service Nodes
+  package: service_nodes
+```
+
+Metadata for publishing and organizing your custom node in the catalog.
+
+### Environment Variables (Optional)
+```yaml
+environment:
+  OPEN_PAAS_USER:
+    title: PaaS user
+    type: string
+    scope: global
+```
+
+All environment variables and API keys required to connect the node to external providers.
+
+## Copying and Reusing Nodes
+
+The most powerful feature of the YAML tab is the ability to create exact duplicates of nodes:
+
+1. **Copy YAML** - Select all code in the YAML tab and copy it
+2. **Create New Node** - Add a new node to any pipeline
+3. **Paste Configuration** - Replace the new node's YAML with the copied code
+4. **Save Changes** - The node will be recreated with identical functionality
+
+This process preserves all settings, code, and configuration, making it simple to reuse any nodes across different pipelines.
+
+## Read-Only
+
+The YAML tab is primarily intended for viewing and copying. While you can see the complete node configuration here, changes should be made through the appropriate tabs (Script for code changes, Design for input/output modifications, etc.) to ensure proper validation and formatting.

i18n/ru/docusaurus-plugin-content-docs/current/advanced-development/pipeline-yaml.mdx

@@ -0,0 +1,113 @@
+---
+sidebar_position: 4
+---
+
+# YAML для пайплайны
+
+**YAML пайплайна** предоставляет комплексный обзор всей конфигурации вашего пайплайна в формате YAML. Это включает все ноды с их расположением, исполняемым кодом, взаимосвязями и различной технической информацией, которая определяет, как работает пайплайн.
+
+## Доступ к YAML пайплайна
+
+Чтобы получить доступ к конфигурации YAML пайплайна:
+
+1. Нажмите кнопку **More** в интерфейсе пайплайна
+2. Выберите **YAML** из выпадающего меню
+
+![Доступ к YAML пайплайна](../img/pipeline-yaml-1.jpg)
+
+Это откроет редактор YAML, где вы можете его просматривать и изменять.
+
+## Структура YAML
+
+YAML пайплайна следует определенной иерархической структуре:
+
+### 1. Метаданные пайплайна
+```yaml
+name: Pipeline Name
+version: 1
+description: Pipeline description
+readme: {}
+category:
+  _id: category_id
+  title: Category
+```
+
+Этот раздел содержит базовую информацию о пайплайне, включая название, описание и категоризацию.
+
+### 2. Конфигурация запуска
+```yaml
+start:
+  nodes:
+    - first_node_id
+```
+
+Определяет, какая нода служит стартовой точкой для выполнения пайплайна.
+
+### 3. Входы и выходы
+```yaml
+inputs:
+  string1:
+    title: String 1
+    type: string
+    # Параметры входных данных
+
+outputs:
+  json_output:
+    title: JSON
+    type: json
+    # Параметры выходных данных
+```
+
+Здесь определены все входы и выходы для всех нод, размещённые на рабочем пространстве пайплайны.
+
+### 4. Потоки (соединения нод)
+```yaml
+flows:
+  connection_name:
+    from: source_node
+    output: output_parameter
+    to: target_node
+    input: input_parameter
+```
+
+Этот раздел описывает, как данные передаются между нодами, связывая выходы одной ноды с входами другой.
+
+### 5. Конфигурация нод
+```yaml
+nodes:
+  node_id:
+    version: 1
+    title: Node Title
+    source: node|catalog
+    execution: rapid|regular|deferred|protracted
+    script: |
+      // JavaScript код
+    inputs:
+      # Определения входов ноды
+    outputs:
+      # Определения выходов ноды
+    arrange:
+      # Расположение ноды
+```
+
+Каждая нода в пайплайне полностью описана со всеми параметрами и кодом.
+
+## Редактирование и сохранение
+
+При внесении изменений в YAML пайплайна:
+
+1. **Внесите свои изменения** в редакторе YAML
+2. **Нажмите Save** внизу интерфейса
+3. **Проверьте индикатор состояния** - зеленый индикатор "Saved" появится справа, если нет ошибок
+
+![Интерфейс редактора YAML](../img/pipeline-yaml-2.jpg)
+
+Любые синтаксические ошибки или проблемы конфигурации будут выделены, предотвращая операцию сохранения до их устранения.
+
+## Возврат в рабочее пространство пайплайна
+
+Чтобы вернуться в визуальное рабочее пространство пайплайна:
+
+- Нажмите синюю кнопку **Pipeline** слева в интерфейсе
+
+Это переключит вас обратно в графический редактор пайплайна.

i18n/ru/docusaurus-plugin-content-docs/current/deploy-pipelines/_category_.json

@@ -1,8 +0,0 @@
-{
-  "label": "Публикация конвейеров и API",
-  "position": 4,
-  "link": {
-    "type": "generated-index",
-    "description": "Публикуйте свои конвейеры и вызывайте их через API за секунды."
-  }
-}

i18n/ru/docusaurus-plugin-content-docs/current/deploy-pipelines/call-via-api.md

@@ -1,111 +0,0 @@
----
-sidebar_position: 1
----
-
-# Запуск конвейеров и API
-
-После публикации ваши конвейеры можно вызывать с помощью запросов POST/GET.
-
-:::tip Подсказка
-
-Если вы развернули Piper на своем собственном сервере, замените **piper.my** на свое доменное имя.
-
-:::
-
-## Запустить конвейер
-
-```bash
-curl --location --request POST 'https://app.piper.my/api/pipeline-slug/launch' \
---header 'content-type: application/json' \
---header 'api-token: [YOUR_API_KEY_HERE]' \
---data '{
-  "inputs": {
-    name: "Bob Marley",
-    age: 36,
-    died: true
-  }
-}'
-```
-
-:::tip Важно
-
-Тип входных данных может быть только: `boolean` | `number` | `string` 
-
-:::
-
-Некоторые конвейеры принимают JSON в качестве входных данных.
-
-В этом случае JSON все равно необходимо сериализовать в строку.
-
-```json
-{
-  "inputs": {
-    "props": "{ \"name\": \"Bob Marley\", \"age\": 36 }"
-  }
-}
-```
-
-### Изображения и медиафайлы
-
-Существует два способа отправки изображений и других медиафайлов, таких как видео или аудио:
-1. JSON Base64: `data:image/jpeg;base64,...`
-2. Загрузка как артефакта.
-
-#### JSON Base64
-
-```bash
-curl --location --request POST 'https://app.piper.my/api/pipeline-slug/launch' \
---header 'content-type: application/json' \
---header 'api-token: [YOUR_API_KEY_HERE]' \
---data '{
-  "inputs": {
-    image: "data:image/jpeg;base64,..."
-  }
-}'
-```
-
-:::danger Ограничения
-
-Для обеспечения стабильности и производительности JSON ограничен 2048 КБ.
-Большие медиафайлы загружайте как артефакты.
-
-:::
-
-#### Загрузка артефакта
-
-Piper имеет собственное временное хранилище для обработки больших медиафайлов.
-
-```bash
-curl --location --request POST 'https://app.piper.my/api/artefacts' \
---header 'api-token: [YOUR_API_KEY_HERE]' \
--F "file=@/path/to/your/file.jpg"
-```
-
-После загрузки вы получите URL-адрес для доступа к файлу.
-
-:::danger Ограничения
-
-Ваш файл будет автоматически удален примерно через 48 часов.
-
-:::
-
-## Статус конвейера
-
-```bash
-curl --location --request GET 'https://app.piper.my/api/launches/[LAUNCH_ID]/state' \
---header 'api-token: [YOUR_API_KEY_HERE]'
-```
-
-В зависимости от типа конвейера мы рекомендуем проводить опрос каждые 2–5 секунд.
-
-Поскольку выходные данные в конвейере устанавливаются асинхронно, вам необходимо дождаться всех ожидаемых выходных данных.
-
-:::tip Вопрос
-
-> Поддерживаете ли вы вебхуки или потоковые события?
-
-**Это произойдет совсем скоро!**
-
-Пожалуйста, [проголосуйте](https://github.com/my-piper/piper/issues/17), чтобы выразить свою поддержку.
-
-:::