diff --git a/docs/第三方服务/重睛鸟代码溯源.md b/docs/第三方服务/重睛鸟代码溯源.md
index 83d1542..5cd1639 100644
--- a/docs/第三方服务/重睛鸟代码溯源.md
+++ b/docs/第三方服务/重睛鸟代码溯源.md
@@ -62,6 +62,6 @@ sidebar_position: 1
## 用户操作流程
-
+
用户操作流程
diff --git a/i18n/en/code.json b/i18n/en/code.json
new file mode 100644
index 0000000..600e961
--- /dev/null
+++ b/i18n/en/code.json
@@ -0,0 +1,308 @@
+{
+ "theme.ErrorPageContent.title": {
+ "message": "This page crashed.",
+ "description": "The title of the fallback page when the page crashed"
+ },
+ "theme.NotFound.title": {
+ "message": "Page Not Found",
+ "description": "The title of the 404 page"
+ },
+ "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.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.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.caution": {
+ "message": "caution",
+ "description": "The default label used for the Caution admonition (:::caution)"
+ },
+ "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.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.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": {
+ "message": "{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.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.blog.sidebar.navAriaLabel": {
+ "message": "Blog recent posts navigation",
+ "description": "The ARIA label for recent posts in the blog sidebar"
+ },
+ "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.CodeBlock.wordWrapToggle": {
+ "message": "Toggle word wrap",
+ "description": "The title attribute for toggle word wrapping button of code block lines"
+ },
+ "theme.DocSidebarItem.toggleCollapsedCategoryAriaLabel": {
+ "message": "Toggle the collapsible sidebar category '{label}'",
+ "description": "The ARIA label to toggle the collapsible sidebar category"
+ },
+ "theme.NavBar.navAriaLabel": {
+ "message": "Main",
+ "description": "The ARIA label for the main navigation"
+ },
+ "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.TOCCollapsible.toggleButtonLabel": {
+ "message": "On this page",
+ "description": "The label used by the button on the collapsible TOC component"
+ },
+ "theme.navbar.mobileLanguageDropdown.label": {
+ "message": "Languages",
+ "description": "The label for the mobile language switcher dropdown"
+ },
+ "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.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.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.SearchBar.noResultsText": {
+ "message": "No results"
+ },
+ "theme.SearchBar.seeAll": {
+ "message": "See all results"
+ },
+ "theme.SearchBar.seeAllOutsideContext": {
+ "message": "See results outside {context}"
+ },
+ "theme.SearchBar.searchInContext": {
+ "message": "See all results in {context}"
+ },
+ "theme.SearchBar.label": {
+ "message": "Search",
+ "description": "The ARIA label and placeholder for search button"
+ },
+ "theme.SearchPage.existingResultsTitle": {
+ "message": "Search results for \"{query}\"",
+ "description": "The search page title for non-empty query"
+ },
+ "theme.SearchPage.emptyResultsTitle": {
+ "message": "Search the documentation",
+ "description": "The search page title for empty query"
+ },
+ "theme.SearchPage.searchContext.everywhere": {
+ "message": "everywhere"
+ },
+ "theme.SearchPage.documentsFound.plurals": {
+ "message": "1 document found|{count} documents found",
+ "description": "Pluralized label for \"{count} documents found\". 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.SearchPage.noResultsText": {
+ "message": "No documents were found",
+ "description": "The paragraph for empty search result"
+ },
+ "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"
+ }
+}
diff --git a/i18n/en/docusaurus-plugin-content-blog/options.json b/i18n/en/docusaurus-plugin-content-blog/options.json
new file mode 100644
index 0000000..9239ff7
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-blog/options.json
@@ -0,0 +1,14 @@
+{
+ "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"
+ }
+}
diff --git a/i18n/en/docusaurus-plugin-content-docs/current.json b/i18n/en/docusaurus-plugin-content-docs/current.json
new file mode 100644
index 0000000..1a8fcf2
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current.json
@@ -0,0 +1,54 @@
+{
+ "version.label": {
+ "message": "Next",
+ "description": "The label for version current"
+ },
+ "sidebar.defaultSidebar.category.快速开始": {
+ "message": "Quick start",
+ "description": "The label for category 快速开始 in sidebar defaultSidebar"
+ },
+ "sidebar.defaultSidebar.category.代码库管理": {
+ "message": "Code base management",
+ "description": "The label for category 代码库管理 in sidebar defaultSidebar"
+ },
+ "sidebar.defaultSidebar.category.组织管理": {
+ "message": "Organization management",
+ "description": "The label for category 组织管理 in sidebar defaultSidebar"
+ },
+ "sidebar.defaultSidebar.category.疑修(Issue)": {
+ "message": "Issue",
+ "description": "The label for category 疑修(Issue) in sidebar defaultSidebar"
+ },
+ "sidebar.defaultSidebar.category.合并请求(PR)": {
+ "message": "PR",
+ "description": "The label for category 合并请求(PR) in sidebar defaultSidebar"
+ },
+ "sidebar.defaultSidebar.category.DevOps引擎(Engine)": {
+ "message": "DevOps Engine",
+ "description": "The label for category DevOps引擎(Engine) in sidebar defaultSidebar"
+ },
+ "sidebar.defaultSidebar.category.维基(Wiki)": {
+ "message": "Wiki",
+ "description": "The label for category 维基(Wiki) in sidebar defaultSidebar"
+ },
+ "sidebar.defaultSidebar.category.机器人(Bot)": {
+ "message": "Bot",
+ "description": "The label for category 机器人(Bot) in sidebar defaultSidebar"
+ },
+ "sidebar.defaultSidebar.category.第三方服务": {
+ "message": "Third party service",
+ "description": "The label for category 第三方服务 in sidebar defaultSidebar"
+ },
+ "sidebar.defaultSidebar.category.通知": {
+ "message": "Notification",
+ "description": "The label for category 通知 in sidebar defaultSidebar"
+ },
+ "sidebar.defaultSidebar.category.个人主页建站": {
+ "message": "Personal home page building site",
+ "description": "The label for category 个人主页建站 in sidebar defaultSidebar"
+ },
+ "sidebar.defaultSidebar.category.服务协议": {
+ "message": "Service agreement",
+ "description": "The label for category 服务协议 in sidebar defaultSidebar"
+ }
+}
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/Bot市场/_category_.json b/i18n/en/docusaurus-plugin-content-docs/current/Bot市场/_category_.json
new file mode 100644
index 0000000..15c2c5a
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/Bot市场/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "机器人(Bot)",
+ "position": 8
+}
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/Bot市场/bot安装.md b/i18n/en/docusaurus-plugin-content-docs/current/Bot市场/bot安装.md
new file mode 100644
index 0000000..241b85c
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/Bot市场/bot安装.md
@@ -0,0 +1,20 @@
+---
+sidebar_label: 'bot installation'
+sidebar_position: 1
+---
+
+# bot installation
+
+Bot installation is an important module for bot installation and management control, which mainly includes bot installation, installation query, installation management and other functions.
+
+In the bot details page, after the user clicks the "Install this Bot" button, he can see the permission information required for the bot to work. The installation can proceed if the user agrees to grant the bot the relevant permissions required. The user can choose to install the bot into all warehouses (all warehouses owned by the user) or select a specified warehouse for installation.
+
+
+
+In the personal "Settings" or "warehouse Settings", the user can see the current installed Bot, click the "configuration" button to configure the bot installation, click the "uninstall" button to uninstall.
+
+
+
+In the bot installation and configuration page, users can master the installation location and working status of the bot. If the user needs to change the bot's working warehouse, the installation location can be changed. The working status of bot includes activation and suspension. Users can adjust the status of bot according to their needs, and suspending or activating it will affect the access permission of bot to warehouse data.
+
+
\ No newline at end of file
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/Bot市场/bot市场.md b/i18n/en/docusaurus-plugin-content-docs/current/Bot市场/bot市场.md
new file mode 100644
index 0000000..ef943c5
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/Bot市场/bot市场.md
@@ -0,0 +1,24 @@
+---
+sidebar_label: 'bot market'
+sidebar_position: 4
+---
+
+# Bot Market
+
+Bot market is an important module for Bot sharing and reuse, mainly including bot search and discovery, details view and other functions.
+
+The bot market homepage displays the brief information of all the bots that have been put on the market, including the bot's avatar, name, developer, introduction and installation times, etc. Users can preliminatively judge whether the bot meets their project needs according to these basic information.
+
+In the bot market homepage, users can select a specific bot type, screen out a specific classification of bots, and search and select within this category.
+
+In addition, the user searches by entering a keyword in the search bar to retrieve the relevant bot whose content contains the specified keyword.
+
+Users can use a combination of category filtering and keyword search to narrow down the scope and quickly find the bot in the market that meets the relevant needs of the project.
+
+
+
+In the bot Market page, the user clicks on the specified bot card to access the bot details page. The Bot details page contains the bot's avatar, name, developer, type and detailed introduction information, so that users can master the bot's introduction here and further determine whether to install it in the specified warehouse.
+
+
+
+In the bot details page, if the user thinks that the bot meets the needs of his project, he can click the "Install this Bot" button to understand the permission information of the bot and install it in the specified warehouse. More information about the installation can be found in the "Bot Installation" section.
\ No newline at end of file
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/Bot市场/bot开发.md b/i18n/en/docusaurus-plugin-content-docs/current/Bot市场/bot开发.md
new file mode 100644
index 0000000..95abb83
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/Bot市场/bot开发.md
@@ -0,0 +1,22 @@
+---
+sidebar_label: 'bot development'
+sidebar_position: 3
+---
+
+# Bot Development
+
+bot development is an important module for developers to register bots.
+
+In the personal "Settings", the user can see the list of registered bots, click the corresponding bot "Edit" button to configure the registered bot; Click the "Bot Register" button to start registering a new bot.
+
+
+
+In the registration page, developers need to fill in the relevant information of bot registration, including bot name, Webhook address, detailed introduction, etc. The system will verify the legitimacy of the information entered by developers to ensure the integrity and validity of all bot information. In addition, the system will automatically generate the unique identity of the bot, and at the same time, the relevant interface of the GitLink platform will be called to generate the bot's identity certificate information, including the client key and private key.
+
+Developers need to use these identity information combined with the platform interface for bot identity authentication, and then call the relevant interface to complete the relevant functions of the bot.
+
+Platform development API link (pending)：https://www.gitlink.org.cn/docs/api#introduction
+
+
+
+
\ No newline at end of file
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/Bot市场/bot配置.md b/i18n/en/docusaurus-plugin-content-docs/current/Bot市场/bot配置.md
new file mode 100644
index 0000000..d4e10cc
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/Bot市场/bot配置.md
@@ -0,0 +1,23 @@
+---
+sidebar_label: 'bot configuration'
+sidebar_position: 2
+---
+
+# Bot configuration
+
+Bot configuration is an important module for bot maintenance and configuration, which mainly includes bot basic information maintenance, permission & subscription event management, advanced option configuration and other functions.
+
+In the maintenance of Bot basic information, developers can see the basic information of the bot, and modify the bot's avatar, name, Webhook address, etc., as needed.
+
+
+
+In bot permissions & Subscription event management, developers can assign different permissions and levels to bots according to the needs of accessing warehouse resources, such as increasing the code base permissions, and changing the write permissions of pull requests to read permissions. Developers can also change the list of events currently subscribed to by the bot, such as subscribing to codebase push, canceling pull requests to assign subscriptions, etc., in order to update and upgrade bot features.
+
+
+
+
+In the advanced Bot option configuration, developers can change the public and private state of the bot, thus affecting the scope of use of the bot. It is important to note that a bot in its public state cannot become private if another repository is already installed. Developers can choose to put the bot on the market, and need to fill in the listing information, including market introduction, main function, secondary function and other information.
+
+Developers can also delete and transfer bots, and initiating a transfer means changing ownership of the bot, requiring the recipient's username to be entered. After the recipient confirms acceptance, the ownership change of bot can be completed. If the recipient refuses, the transfer operation will be cancelled.
+
+
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/DevOps引擎/_category_.json b/i18n/en/docusaurus-plugin-content-docs/current/DevOps引擎/_category_.json
new file mode 100644
index 0000000..813fd86
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/DevOps引擎/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "DevOps引擎(Engine)",
+ "position": 6
+}
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/DevOps引擎/代码流水线.md b/i18n/en/docusaurus-plugin-content-docs/current/DevOps引擎/代码流水线.md
new file mode 100644
index 0000000..8a8e8e9
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/DevOps引擎/代码流水线.md
@@ -0,0 +1,12 @@
+---
+sidebar_label: 'Code pipeline'
+sidebar_position: 5
+---
+# Code pipeline
+The pipeline can be configured in the form of code (YAML format) by first selecting the code pipeline and corresponding branches:
+
+ 
+
+ Edit pipeline code, the pipeline name description, trigger, global parameters, execution serial/concurrent and pipeline orchestration concepts are the same as the graphic pipeline, described as follows:
+
+
\ No newline at end of file
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/DevOps引擎/参数配置.md b/i18n/en/docusaurus-plugin-content-docs/current/DevOps引擎/参数配置.md
new file mode 100644
index 0000000..16216ae
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/DevOps引擎/参数配置.md
@@ -0,0 +1,15 @@
+---
+sidebar_label: 'Parameter configuration'
+sidebar_position: 2
+---
+
+# Parameter configuration
+
+It can be used in the pipeline to realize dynamic parameter configuration. There are three types: string, number, and Boolean.
+
+ 
+
+
+You can obtain parameters in the pipeline configuration in the following ways:
+
+ 
\ No newline at end of file
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/DevOps引擎/图形流水线.md b/i18n/en/docusaurus-plugin-content-docs/current/DevOps引擎/图形流水线.md
new file mode 100644
index 0000000..8a13292
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/DevOps引擎/图形流水线.md
@@ -0,0 +1,50 @@
+---
+sidebar_label: 'Graphic pipeline'
+sidebar_position: 4
+---
+
+# Graphic pipeline
+## Basic information
+You can edit the name and description of the pipeline
+
+Pipeline names in the same warehouse must be unique
+
+
+
+## trigger
+Note: When pipelining, the trigger should be placed before the start node; Currently, only one trigger can be added to an pipeline
+
+* Timing trigger cron: You can set the trigger time by filling in the cron expression
+
+
+* Event trigger GitLink_Webhook: gives common code change event triggers, including pushing code, merging requests, and creating tags
+
+
+## Global parameter
+
+After being added, it can be used in the current pipeline
+
+
+
+example
+
+
+
+## Concurrent execution
+
+
+
+When enabled, the same pipeline can execute n pipeline instances concurrently (we get one pipeline instance for each trigger);
+
+
+
+If this parameter is disabled, subsequent instances are queued during the execution of the current pipeline instance (a maximum of five instances can be queued). The current instance completes execution, and the next instance starts execution.
+
+
+
+
+## Pipelining
+
+Each pipeline must have a start node, an end node, and at least one task node. Supports serial and parallel orchestration.
+
+
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/DevOps引擎/密钥设置.md b/i18n/en/docusaurus-plugin-content-docs/current/DevOps引擎/密钥设置.md
new file mode 100644
index 0000000..47f3169
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/DevOps引擎/密钥设置.md
@@ -0,0 +1,16 @@
+---
+sidebar_label: 'Key Settings'
+sidebar_position: 3
+---
+
+ # Key Settings
+
+The account password, key, and certificate are stored in the key management. After the configuration, they can be directly used in the pipeline to avoid leakage risks caused by direct input.
+
+
+
+Use example
+
+Note: In the node input parameters, the drop-down option is the key type. You need to configure the key in advance to select and use it in the pipeline
+
+
\ No newline at end of file
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/DevOps引擎/引擎简介.md b/i18n/en/docusaurus-plugin-content-docs/current/DevOps引擎/引擎简介.md
new file mode 100644
index 0000000..e90f1f2
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/DevOps引擎/引擎简介.md
@@ -0,0 +1,13 @@
+---
+sidebar_label: 'Engine'
+sidebar_position: 1
+---
+
+ # Engine
+
+Engine is a DevOps tool from GitLink that builds development, test, and deployment pipelines through simple node orchestration to create automated software delivery processes.
+It can achieve continuous code integration, so that developers can find quality problems as early as possible, quickly locate and fix, improve the efficiency and quality of software development; Automated code scanning, compilation, packaging, and unit testing free the development team from repetitive work and focus on more valuable things.
+
+
+
+In the engine page, users can create and edit a graphical pipeline or code pipeline, set external parameters, manage keys, and so on.
\ No newline at end of file
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/DevOps引擎/执行记录查询.md b/i18n/en/docusaurus-plugin-content-docs/current/DevOps引擎/执行记录查询.md
new file mode 100644
index 0000000..594c3e0
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/DevOps引擎/执行记录查询.md
@@ -0,0 +1,10 @@
+---
+sidebar_label: 'Perform a record query'
+sidebar_position: 6
+---
+
+ # Perform a record query
+
+You can view the pipeline running status
+
+ 
\ No newline at end of file
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/intro.md b/i18n/en/docusaurus-plugin-content-docs/current/intro.md
new file mode 100644
index 0000000..c93fae2
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/intro.md
@@ -0,0 +1,19 @@
+---
+sidebar_label: "Introduce"
+label: "介绍"
+sidebar_position: 1
+slug: /intro
+---
+
+# About GitLink
+GitLink (true Open Source) is an open source innovation service platform officially designated by CCF. It aims to take "serving open source innovation" as its mission, "becoming the gathering place of open source innovation" as its vision, adhering to the values of "innovation, openness, collaboration and sharing", and is committed to empowering large-scale open source collaborative innovation. Create an open source innovation ecology for incubation of innovation achievements and training of new engineering talents!
+
+ 
+
+# Platform Features
+- **Distributed collaborative development** : Support online file editing, branch management, contribution statistics, warehouse copy, merge requests;
+- **One-stop process management** : Support doubt repair, milestone, notification reminder, label archive, Wiki document, organization management;
+- **Efficient pipeline operation and maintenance** : Provide lightweight workflow engine, and support custom configuration, static scanning, product construction;
+- **Multi-level code analysis** : Support code traceability analysis, license risk analysis, open source vulnerability detection and reinforcement suggestions;
+- **Multi-dimensional user Profile** : Support development activity statistics, contribution calendar, capability modeling, role and professional positioning analysis.
+
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/个人主页建站/_category_.json b/i18n/en/docusaurus-plugin-content-docs/current/个人主页建站/_category_.json
new file mode 100644
index 0000000..9fdc768
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/个人主页建站/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "个人主页建站",
+ "position": 13
+}
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/个人主页建站/建站工具.md b/i18n/en/docusaurus-plugin-content-docs/current/个人主页建站/建站工具.md
new file mode 100644
index 0000000..fe91bdd
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/个人主页建站/建站工具.md
@@ -0,0 +1,69 @@
+---
+sidebar_label: 'Site building tool'
+sidebar_position: 2
+---
+# Personal website building tool
+
+Personal homepage is a free static web hosting service that can be used to host static personal homepage, personal blog and other static pages. Different tools for personal website building are as follows
+
+### Hugo tool
+
+
+To create a repository using the Hugo tool, you need to modify the baseURL in the config.toml file in the code repository
+Change the value to the website address displayed in the personal website service,
+For example: now have a website address is http://KingChan.gitlink.net
+The config. The baseURL in toml should be http://KingChan.gitlink.net
+ 
+
+Click Submit after modification
+ 
+After the submission is complete, deployment begins
+ 
+Static page preview
+ 
+
+### jekyll tool
+
+For jekyll project:
+To create a personal site using the jekyll tool, you need to modify the baseurl and url values in the _config.yml file in the code repository. The jekyll configuration file is special and needs to be based on the website address displayed in the personal site construction service
+Content modifies two values.
+For example: now have a website address is http://KingChan.gitlink.net
+The result is as follows:
+baseurl: "/"
+url: "http://KingChan.gitlink.net"
+
+ 
+
+Click Submit changes when the changes are complete
+ 
+After the submission is complete, go to the site construction service to start deployment
+ 
+
+ 
+
+### hexo tool
+
+If it is a hexo project:
+For repositories created using the Hexo tool, you need to change the url in the _config.yml file in the code repository
+Change the value to the website address displayed in the personal website service,
+For example: now have a website address is http://KingChan.gitlink.net
+
+So _config. The url in toml should be http://KingChan.gitlink.net
+
+ 
+
+Click Submit changes when the changes are complete
+ 
+After the submission is complete, go to the site construction service to start deployment
+
+ 
+
+ 
+
+ 
+
+### file tool
+Document formatting tool, which deployable all files under the selected branch.
+
+
+Note: All of the above tools can use the gh-pages branch, when the gh-pages branch is selected at deployment time, it will be deployed according to the document format tool, that is, all files under the branch are deployed.
\ No newline at end of file
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/个人主页建站/站点创建流程.md b/i18n/en/docusaurus-plugin-content-docs/current/个人主页建站/站点创建流程.md
new file mode 100644
index 0000000..7cb0f87
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/个人主页建站/站点创建流程.md
@@ -0,0 +1,50 @@
+---
+sidebar_label: 'Station construction process'
+sidebar_position: 1
+---
+# Personal website building process
+### My site
+Move the mouse to the profile picture position in the upper right corner and click Settings to enter the My Settings interface
+
+
+
+Click on the left pane of Personal Site - My site
+
+
+
+### Create a site
+
+In the My site interface, click the New site button to enter the new site interface
+
+On the New Site screen, enter a site name, which will be displayed in the My Sites list
+
+And choose the corresponding site building tools and themes, we provide you with 3 different tools, each tool 10 kinds of themes, a total of 30 kinds for you to choose
+
+
+
+When you're done, click the blue button at the bottom of the page: Create Site
+
+
+
+So you have a website and you have a repository of code.
+
+In the service column of the warehouse personal site service operation interface, here you can view some of your site status, site name, website address, site tool, site time
+
+### Deploy the site
+
+
+
+Click the Go to Deploy button, select the branch you want to deploy and click OK
+
+
+
+After waiting for the program to run for a while, some server deployment information will be returned to you
+
+Once the deployment is successful, you can access the site. Click on the website address to get there
+
+
+
+### Deployment complete
+
+
+
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/代码库管理/WebIDE.md b/i18n/en/docusaurus-plugin-content-docs/current/代码库管理/WebIDE.md
new file mode 100644
index 0000000..299f616
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/代码库管理/WebIDE.md
@@ -0,0 +1,41 @@
+---
+sidebar_label: 'WebIDE'
+sidebar_position: 9
+---
+
+### **1. Language Service **
+● Support syntax highlighting in nearly 40 languages
+● Support JavaScript/TypeScript, HTML, CSS, JSON, Markdown based on the Language Server Protocol (LSP) language features, with intelligent prompt and outline information and single-file jump.
+● Support Java, Go, Python, C++, Php based on Tree Sitter online language service capabilities, providing viewing references, symbol search and other features
+
+### **2. WebIDE Entry **
+From the Gitlink warehouse home page, click the Web IDE button to enter
+
+
+### **3. Branch **
+Support branch switching: Click the branch name in the lower left corner to switch branches.
+
+
+### **4. Search for **
+It currently supports code search within the Gitlink repository (supporting word matching and file filtering) and file search.
+
+
+### **5. Line highlight **
+Support single or multiple lines of highlighting, click the line number to highlight the line, hold down Shift to select multiple consecutive lines.
+
+
+### **6. Blame**
+Supports viewing single-line blame information, and displays details after the hover.
+
+
+### **7. Graph**
+graph view is supported to view branch commits history and file changes for each commit, as well as file diff viewing. Click Git Graph at the bottom left corner of the status bar or enter View Git Graph in the command panel to open the Git Graph view.
+
+
+### **8. WebSCM**
+You can create a new branch in the Super Edition, modify the code and see the change file list in the SCM panel, write a commit message and submit it to Gitlink. If you want to quickly modify some files, you can directly submit the code through the speed version without local modification.
+
+### **9. Code running online **
+●Integration of skypack based on the more lightweight CodeSwing plug-in, you can run front-end code in the speed version.
+● Integration of Pyodide-based Code-Runner-For-Web plug-in, you can run Python to the browser.
+
\ No newline at end of file
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/代码库管理/Webhook.md b/i18n/en/docusaurus-plugin-content-docs/current/代码库管理/Webhook.md
new file mode 100644
index 0000000..f847c84
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/代码库管理/Webhook.md
@@ -0,0 +1,38 @@
+---
+sidebar_label: 'Webhook'
+sidebar_position: 8
+---
+ ### **1. Webhook module entry **
+On the project home page, click the "Warehouse Settings" button and then click the "Network Hook" button to enter the Webhook module of the warehouse.
+ 
+
+ ### **2. Add Webhook**
+Click the Add Webhook button to access the Webhook configuration page.
+
+ 
+ 
+
+ ### **3. Edit Webhook**
+After adding Webhooks, as shown in the figure below, each Webhook can be edited by clicking the "Edit" button on the right.
+
+ 
+
+ ### **4. Delete the Webhook**
+After adding Webhooks, as shown in the figure below, you can delete each Webhook by clicking the "Delete" button on the right.
+
+ 
+
+ ### **5. Types of events supported by Webhook **
+In GitLink, Webhooks support the following types of events:
+- Push: git is pushed to the repository
+- Code base: Creates or deletes a code base
+- Create: Creates a branch or label
+- Delete: Deletes a branch or label
+- Merge request: The merge request is opened, closed, reopened, or edited
+- Merge request assignment: The merge request is assigned or unassigned
+- Merge request revenue milestone: Merge requests are recorded or cancelled in the milestone
+- Merge request is commented: Merge request comments are created, edited, or deleted
+- Merge Request tag: The tag of the merge request is updated or cleared
+- Merge request review: The merge request is approved, rejected, or submitted for review, the review thread is resolved or not resolved
+- The merge request is synchronized: The merge request is synchronized
+
\ No newline at end of file
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/代码库管理/_category_.json b/i18n/en/docusaurus-plugin-content-docs/current/代码库管理/_category_.json
new file mode 100644
index 0000000..82c9af5
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/代码库管理/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "代码库管理",
+ "position": 2
+}
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/代码库管理/仓库创建.md b/i18n/en/docusaurus-plugin-content-docs/current/代码库管理/仓库创建.md
new file mode 100644
index 0000000..e86bc0c
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/代码库管理/仓库创建.md
@@ -0,0 +1,11 @@
+---
+sidebar_label: 'Warehouse creation'
+sidebar_position: 1
+---
+### **1. Warehouse create entry **
+Users can create a warehouse by clicking the button in the upper right corner of the platform home page and the "New" button in the personal home participation project module.
+
+
+### **2. Fill in the basic information **
+Enter the new project page, as shown in the following figure, fill in the owner, project name, project ID and other information, click "Create project" button to complete the creation.
+
\ No newline at end of file
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/代码库管理/仓库设置.md b/i18n/en/docusaurus-plugin-content-docs/current/代码库管理/仓库设置.md
new file mode 100644
index 0000000..f062dbc
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/代码库管理/仓库设置.md
@@ -0,0 +1,11 @@
+---
+sidebar_label: 'Warehouse setup'
+sidebar_position: 2
+---
+### **1. Warehouse setup entrance **
+In the warehouse home page, click the "warehouse Settings" button to enter the warehouse Settings module. The repository setup allows you to modify basic project information, manage members, configure Webhooks, set up branches, and install bots.
+
+
+### **2. Basic Settings **
+After entering the warehouse setting module, click the "Basic Setting" button to enter the basic setting module, as shown in the following figure, you can modify the basic information of the project such as project name, project identifier, project introduction, project category, project language, etc. Click Transfer to transfer the warehouse to another user or organization. Click Delete this Warehouse to delete the warehouse.
+
\ No newline at end of file
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/代码库管理/代码提交.md b/i18n/en/docusaurus-plugin-content-docs/current/代码库管理/代码提交.md
new file mode 100644
index 0000000..1ef8af7
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/代码库管理/代码提交.md
@@ -0,0 +1,24 @@
+---
+sidebar_label: 'Code submission'
+sidebar_position: 3
+---
+
+
+## GitLink code submission
+
+- **Submitted by** : geekchen
+- **Date** : 2024.5.27
+
+## 1. Submit the code directly on the webpage:
+
+ **Next:**
+
+## 2. Upload local code files through git (can be a single file, can be a folder composed of multiple files) [non-code can also be up loaded]
+**Open git bash in the corresponding directory and type the following command :**
+git add +[The code file you want to submit]
+git commit -m "xxx" [xxx is your own note of submission information]
+git push
+**The diagram is as follows:**
+
+
+
\ No newline at end of file
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/代码库管理/分支管理.md b/i18n/en/docusaurus-plugin-content-docs/current/代码库管理/分支管理.md
new file mode 100644
index 0000000..15fb73f
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/代码库管理/分支管理.md
@@ -0,0 +1,9 @@
+---
+sidebar_label: 'Branch management'
+sidebar_position: 5
+---
+
+Click on the branch in the code warehouse to directly enter the branch management interface, as shown below.
+
+In this interface, we can delete branches, new branches, view deleted branches and other operations, you can also view the information of each branch change, or download a branch, also support to set the default branch, of course, there is only one default branch, you can also set in the branch setting interface as shown in the following figure.
+
\ No newline at end of file
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/代码库管理/成员管理.md b/i18n/en/docusaurus-plugin-content-docs/current/代码库管理/成员管理.md
new file mode 100644
index 0000000..e8fe516
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/代码库管理/成员管理.md
@@ -0,0 +1,29 @@
+---
+sidebar_label: 'Member management'
+sidebar_position: 7
+---
+### **1. Member Management Entry **
+In the warehouse home page, click the "warehouse Settings" button, and then click the "member management" button, you can enter the member management module, as shown in the figure below.
+
+
+### **2. Filter and search project members **
+After entering the member management module, you can filter the type of project members by pressing the "Role screening" button, and search the specific project members by pressing the "Search" button, as shown in the following figure.
+
+
+### **3. Filter and search project members **
+After entering the member management module, you can add project members by pressing the "Add member" button. After the specific user is retrieved from the search box on the left and selected, click the "Add member" button to successfully add project members.
+
+
+### **4. Project member rights management **
+After entering the member management module, click the role bar to the right of the project member, and you can select the permission level for the project member, as shown in the following figure.
+
+
+
+#### ***4.1. Member Rights Description ***
+On the GitLink platform, warehouse member permissions can be divided into the following types:
+
+
+
+### **5. Delete project members **
+After entering the member management module, click the "Delete" button to the right of the project member to delete the renamed project member, as shown in the following figure.
+
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/代码库管理/文件管理.md b/i18n/en/docusaurus-plugin-content-docs/current/代码库管理/文件管理.md
new file mode 100644
index 0000000..ba58931
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/代码库管理/文件管理.md
@@ -0,0 +1,11 @@
+---
+sidebar_label: 'File management'
+sidebar_position: 4
+---
+
+We can directly see and manage files in the code warehouse, as shown in the following figure.
+
+You can see the corresponding branch of the file and all the information of the file, and you can see the latest changes in the file and the change person.
+We can directly click the file button on the left to upload files or create new files (note that files are not folders, if you want to upload folders, you need to use git).
+On the left, you can open the file directory, and directly find the file you want to view and preview it directly, as shown in the following figure.
+
\ No newline at end of file
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/代码库管理/标签和发行版管理.md b/i18n/en/docusaurus-plugin-content-docs/current/代码库管理/标签和发行版管理.md
new file mode 100644
index 0000000..75d104f
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/代码库管理/标签和发行版管理.md
@@ -0,0 +1,29 @@
+---
+sidebar_label: 'Label and distribution management'
+sidebar_position: 6
+---
+### **1. Tags and distribution management entry **
+In the main page of the warehouse, click the "code base" button, and then click the "label" button, you can enter the label and release management module, as shown in the figure below.
+
+
+### **2. Remove tags **
+After entering the label and distribution management module, click the "Delete" button on the right side of the label to achieve the deletion operation of the label, as shown in the following figure.
+
+
+### **3. View the distribution **
+After entering the label and release management module, click the "Release" button to view the release of the project, as shown in the figure below.
+
+
+### **4. Create a distribution **
+After entering the label and distribution management module, click the "Create distribution" button on the right side of the label to quickly create the distribution bound to the label, as shown in the following figure.
+
+
+### **5. Change the distribution **
+After entering the label and release management module, click the Modify button on the right side of the release, you can enter the modify page of the release, as shown in the figure below. After modifying the release, click Save Release to save the modified content.
+
+
+
+### **6. Delete the distribution **
+After entering the label and distribution management module, click the Delete button on the right side of the distribution, you can enter the delete page of the distribution, as shown below.
+
+
\ No newline at end of file
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/合并请求/_category_.json b/i18n/en/docusaurus-plugin-content-docs/current/合并请求/_category_.json
new file mode 100644
index 0000000..15eab23
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/合并请求/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "合并请求(PR)",
+ "position": 5
+}
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/合并请求/代码评审.md b/i18n/en/docusaurus-plugin-content-docs/current/合并请求/代码评审.md
new file mode 100644
index 0000000..37cb305
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/合并请求/代码评审.md
@@ -0,0 +1,16 @@
+---
+sidebar_label: 'Code review'
+sidebar_position: 3
+---
+
+# Code Review
+1. Click the "Code Review" button at the upper right corner of the merge request interface to enter the code review interface, as shown below.
+
+2. After entering the interface, we can see the relevant information of the merger, such as the submitted file, the modified file, the difference before and after the modification of the file, etc. Click the edit button in the upper right corner to edit the submitted code, as shown in the following figure.
+
+3. After editing, click Save. At this time, a modification window will pop up at the lower left corner of the interface, and the code comparison before and after review will appear in the file browsing box. You can view the code modified during the review process, and after confirming that the review information is correct, enter the review information in the modification box and submit it (note that the review information cannot be empty), as shown below.
+
+4. After reviewing the file and submitting the review information, return to the management merge request interface, where we can see the review log under the "Submit" option, and finally merge the request, as shown below.
+
+
+Summary: The code review function is helpful for managers to modify the submitted code when managing merge requests, which is convenient for managers to control the overall code warehouse. The disadvantage is that the operability of code modification is not as good as the local IDE, but if the code is fine-tuned, this is a very good and convenient function!👍👍👍😁
\ No newline at end of file
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/合并请求/创建合并请求.md b/i18n/en/docusaurus-plugin-content-docs/current/合并请求/创建合并请求.md
new file mode 100644
index 0000000..34e6feb
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/合并请求/创建合并请求.md
@@ -0,0 +1,22 @@
+---
+sidebar_label: 'Create merge request'
+sidebar_position: 2
+---
+
+# Create a merge request
+
+1. Enter the "** Merge Request (PR)**" interface of the project that needs to initiate a merge request, and click the "** New Merge Request **" button at the top to enter the merge request release interface, as shown below:
+
+
+
+
+
+2. Select the ** source branch ** and ** target branch ** that need to be merged, where the source branch is the branch that has completed code development and needs to merge its code changes, and the target branch is the branch that wants to merge the code changes, either other branches under the same warehouse (branch) or branches under the source warehouse that are copied;
+
+3. After the branch is selected, fill in the title and description of the merge request to provide the reviewer with information to assist in understanding the merge request, thus speeding up the merge request review process (see section *** Code Review ***);
+
+4. In addition, users can also specify reviewers, add milestones, markers, and priorities in the sidebar on the right (merge request is essentially a query, and these operations have the same or similar meanings as those in the query module, so you can refer to the introduction of the query chapter to help understand);
+
+5. After filling in the final information, click the "** Create **" button at the bottom to submit your first merge request🎉🎉🎉！
+
+
\ No newline at end of file
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/合并请求/合并模式简介.md b/i18n/en/docusaurus-plugin-content-docs/current/合并请求/合并模式简介.md
new file mode 100644
index 0000000..88ec672
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/合并请求/合并模式简介.md
@@ -0,0 +1,100 @@
+---
+sidebar_label: 'Introduction to Merge Mode'
+sidebar_position: 4
+---
+
+# Introduction to merge mode
+
+After the reviewer has reviewed the code changes submitted by the developer, he or she can decide whether to merge those submissions into the master branch.
+
+However, there are multiple merge modes for submission merging between different branches. The following figure shows the merge modes supported in GitLink, including **Merge request **, ** change base and merge **, ** change base merge --no-ff** and ** compress commit and merge **.
+
+
+
+1. **Merge request**
+
+**Merge request** is the most commonly used merge mode, the following picture is an example, the developer in the main branch 'master' commit 3 pull development branch 'dev', and then submit A, B, C, and then merge on the 'master' branch.
+
+Fast forward to the merger:
+
+
+
+Fast forward to the merger:
+
+
+
+** Note ** : As you can see, the process of merging is to move the `master` pointer directly to the `dev` pointer, this merger is called ** fast forward (fast-forward) **, the reason why this situation is because after committing 3, there is no new commit on the `master` branch. So the merge can be done by fast-forwarding the 'master' pointer directly; However, if there are also new commits on the `master` branch, substantial merging is required, as shown in the following two diagrams:
+
+Before merging, after committing A on the `dev` branch and before committing B, 4 is committed on the `master` branch, then merging the `dev` branch can not simply fast forward, but compare the changes on the two branches, and then merge;
+
+Non-fast-forward pre-merger:
+
+
+
+
+After the merge, commit A, B, and C will be added to the `master` commit record according to the timeline, and a new commit D will be generated to record the merge event. In addition, if a conflict occurs during the merge process, that is, two branches make changes to the same file, the conflict needs to be handled manually; This merge method is **non-fast-forward (no fast-forward)**, which is also the default method in **merge request** mode!
+
+After the non-fast-forward merger:
+
+
+
+For ease of understanding, you can view the commit record on the merged `master` branch in a linear manner
+
+
+
+**Summary** : In **Merge Request** mode, the default **non-fast forward** merge development branch to the `master` branch, and **non-fast forward** mode will generate a special commit to record the merge event!
+
+2. **Change base and merge**
+
+From the submission records on the `master` branch after the **merge request**, it can be seen that the submission records of the two branches may cross together, which may cause trouble for subsequent development, and the **change base and merge** can solve this problem.
+
+**Base change and merge** includes two operations: **base change**, **merge**. The first is to change the base, the following example, `dev` branch is pulled out from the commit 3, so commit 3 is the base of `dev`, and change the base operation is to change the base of `dev`, so that it becomes the latest commit on the `master` branch. Of course, there may be conflicts during the base change process, which needs to be handled manually.
+
+Before basing:
+
+
+
+After basing and before merging:
+
+
+
+
+After the `dev` branch changes base, there is no 'update' commit for the `master` branch, so merge at this time, and you get the following result
+
+After the merger:
+
+
+
+**Summary** : In **change base and merge** mode, the development branch `dev` can first change the base operation, so that the submission on it looks like it is carried out on the basis of the latest submission of the `master` branch, and then merge back to the `master` branch by **fast forward** way, so as to play the role of sorting out the submission record!
+
+3. **Change base merger --no-ff**
+
+Because **base change and merge** when the merge operation is performed, the default is **fast forward**, so that there is no special commit on the `master` branch to record the merge event. So you can use the `--no-ff` (**no fast-forward**) option to declare the **non-fast-forward** merge.
+
+`--no-ff` Before merger:
+
+
+
+`--no-ff` post-merger：
+
+
+
+**Summary** : With the `--no-ff` option, it is possible to explicitly state that a **non-fast-forward** method is used when merging, so that a commit recording of the merge event can be added to the `master` branch!
+
+4. **Compress submission and merge**
+
+In development branches such as `dev` or `feature`, developers will commit multiple times in order to complete a certain requirement, but these trivial commit information will make the commit record on `master` bloated and chaotic after merging back into the `master` branch, so it is necessary to compress these commits before merging. As shown in the figure, the compression operation is performed on the `master` branch, essentially applying the changes made on the `dev` branch to the files maintained by the `master` branch, then saving these changes with a new commit5, and finally committing.
+
+Before compression:
+
+
+
+After compression, before submission:
+
+
+
+After submission:
+
+
+
+**Summary**: Before merging, first compress the trivial commits on the development branch, you can make the commit information on the `master` branch more concise, but note that this merging mode is essentially the `master` branch saves the changes on `dev` at once, and creates a new commit record of these changes, so the committer has changed!
\ No newline at end of file
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/合并请求/合并请求关联疑修.md b/i18n/en/docusaurus-plugin-content-docs/current/合并请求/合并请求关联疑修.md
new file mode 100644
index 0000000..0a7714f
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/合并请求/合并请求关联疑修.md
@@ -0,0 +1,6 @@
+---
+sidebar_label: 'Merge requests for associated revisions'
+sidebar_position: 5
+---
+
+# Merge requests for associated revisions
\ No newline at end of file
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/合并请求/合并请求简介.md b/i18n/en/docusaurus-plugin-content-docs/current/合并请求/合并请求简介.md
new file mode 100644
index 0000000..998a21d
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/合并请求/合并请求简介.md
@@ -0,0 +1,18 @@
+---
+sidebar_label: 'Introduction to merge request'
+sidebar_position: 1
+---
+
+# Merge Request brief
+
+**Pull Request** is a way to merge code changes between two software repositories in modern distributed software development. It is usually used for fork repositories to submit code changes to the fork repository (source repository), and it is also a very good team collaboration way to contribute to team projects or open source projects. When you pull and modify someone else's warehouse code, inform the manager of the original warehouse of your changes, and request it to merge your changes, this process is called **merge request**.
+
+**The Merge Request (PR)** module in GitLink provides both merge request creation and management functions:
+
+- Support for creating (initiating) code merge requests to the source repository or other branches of the same repository;
+
+- On the other hand, it is also for the warehouse manager to manage, review and finally determine whether the merge request sent by others to the warehouse is included in the warehouse.
+
+The Merge Request (PR) management module is shown below:
+
+
\ No newline at end of file
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/平台公告/_category_.json b/i18n/en/docusaurus-plugin-content-docs/current/平台公告/_category_.json
new file mode 100644
index 0000000..3b682ad
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/平台公告/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "平台公告",
+ "position": 99
+}
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/平台公告/平台公告.md b/i18n/en/docusaurus-plugin-content-docs/current/平台公告/平台公告.md
new file mode 100644
index 0000000..b9dca77
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/平台公告/平台公告.md
@@ -0,0 +1,19 @@
+---
+sidebar_label: 'Platform announcement'
+sidebar_position: 1
+---
+
+
+**Dear gitlink users:**
+
+We are excited to announce that a new version of the gitlink website will be available in mid-July! This update will bring a number of new features and improvements designed to enhance your user experience and site usage efficiency.
+
+In the new version, you can expect a smoother interface and more intuitive operations to help you find the information and features you need faster. We will also add some new features, such as user profiles, real-time notifications, etc., so that you can better manage and share your projects.
+
+In addition, we will also improve the security and stability of the website to ensure the security of your data and information. We are committed to providing you with a high-quality platform that makes it easier for you to work with your team, manage your code base, and achieve project success.
+
+We hope you will continue to support the gitlink website and look forward to your experience on the new version! If you have any comments or suggestions, please feel free to contact our maintenance team (Grade 21 Software engineering professional Yang Yizhe team), we will be happy to help you.
+
+Thank you for your support of gitlink!
+
+Dear Yang Yizhe maintenance team
\ No newline at end of file
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/快速开始/_category_.json b/i18n/en/docusaurus-plugin-content-docs/current/快速开始/_category_.json
new file mode 100644
index 0000000..c826d66
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/快速开始/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "快速开始",
+ "position": 1
+}
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/快速开始/创建第一个开源项目.md b/i18n/en/docusaurus-plugin-content-docs/current/快速开始/创建第一个开源项目.md
new file mode 100644
index 0000000..e3fbb00
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/快速开始/创建第一个开源项目.md
@@ -0,0 +1,24 @@
+---
+sidebar_label: 'Create your first open source project'
+sidebar_position: 2
+---
+
+# Create your first open source project
+
+## 1. New project
+
+The platform provides a "New" button that allows users to quickly create a new public or private project from scratch with a click.
+
+
+
+## 2. Fill in the project information
+
+Fill in the basic information of the project.
+
+
+
+## 3. The creation is successful
+
+Click Create Project and enter the project home page after the project is successfully created.
+
+
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/快速开始/导入GitHub等第三方Git项目.md b/i18n/en/docusaurus-plugin-content-docs/current/快速开始/导入GitHub等第三方Git项目.md
new file mode 100644
index 0000000..f58d308
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/快速开始/导入GitHub等第三方Git项目.md
@@ -0,0 +1,92 @@
+---
+sidebar_label: 'Import third-party Git projects such as GitHub'
+sidebar_position: 5
+---
+
+# Import to third-party Git projects like GitHub
+
+## 1. Import the project
+
+Select **Import Project** on the home page
+
+
+
+## 2. Fill in the information
+
+Enter the address and information of the third-party Git project to be imported. If the imported project is a private repository, enter the user token of the target platform for authorization.
+
+
+
+## 3. Authorization verification
+
+When using the GitLink platform to import open source projects of other platforms (such as GitHub and Gitee), if the project is private, it cannot be imported through normal channels, and you need to enter the token value of the permission of the corresponding platform for verification.
+
+
+
+Here are some typical token acquisition methods for open source platforms.
+
+### GitHub token acquisition method
+
+1. Log in to GitHub account
+
+2. Access the settings menu under the user profile picture
+
+ 
+
+3. Access the Developer settings at the bottom
+
+ 
+
+4. Access Token (classic) in the jump page and create a new classic token (if the token is saved).
+
+ 
+
+5. On the token configuration page, enter the token usage and ensure that repo is selected for the token. Otherwise, the token import fails
+
+ 
+
+ Click Create button
+
+ 
+
+6. Copy the token
+
+ 
+
+ Enter the token into the GitLink Import Project authentication field
+
+ 
+
+### Gitee token obtaining mode
+
+1. Log in to the Gitee account
+
+2. Access the Settings menu under the user profile picture
+
+ 
+
+3. Visit the "Private Token" menu under the "Security Settings" bar
+
+ 
+
+4. Click Generate New Token and configure the token name on the token generation page, make sure the "project" permission option is checked for the token, and save the token
+
+ 
+
+ 
+
+5. After the successful token generation pop-up, copy the token and enter the token into the GitLink Import project authentication field
+
+ 
+
+ 
+
+## 4. Import successfully
+
+The message indicates that you are migrating from a third-party Git project address
+
+
+
+If the migration succeeds, the project is successfully imported
+
+
\ No newline at end of file
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/快速开始/提交第一行代码.md b/i18n/en/docusaurus-plugin-content-docs/current/快速开始/提交第一行代码.md
new file mode 100644
index 0000000..a8b37a2
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/快速开始/提交第一行代码.md
@@ -0,0 +1,22 @@
+---
+sidebar_label: 'Submit the first line of code'
+sidebar_position: 3
+---
+
+# Submit first line of code
+
+# 1. Edit the code
+
+Click the Edit button to start editing the code.
+
+
+
+# 2. Submit the code
+
+Write the code in the edit box, fill in the change information after writing and submit the change.
+
+
+
+## 3. Code update is successful
+
+After submitting the code, the code is updated successfully.
\ No newline at end of file
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/快速开始/搜索开源项目.md b/i18n/en/docusaurus-plugin-content-docs/current/快速开始/搜索开源项目.md
new file mode 100644
index 0000000..8555909
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/快速开始/搜索开源项目.md
@@ -0,0 +1,44 @@
+---
+sidebar_label: 'Search Open source Projects'
+sidebar_position: 4
+---
+
+# Search open source projects
+
+## 1. Open Source project page introduction
+
+The "Project" module aggregates and manages all managed projects and mirrored projects on the GitLink platform, and users can enter the project name keyword to search, and can also filter projects by project category.
+
+Enter the "Project" module, and the left side lists the project type and project category. Among them, the project types mainly include open source hosted projects and open source mirror projects. The project categories mainly include: cloud computing, big data, blockchain, Internet of Things, machine learning, artificial intelligence, smart healthcare, and others.
+
+
+
+The right side shows the basic information of all projects, including creator, project name, project introduction, page views, project category, update time, number of likes, number of forks and other information. Users can search for specific projects through keyword search, and can also sort projects according to update time, creation time, number of forks, number of likes and so on.
+
+
+
+Users can click on the project name to enter the project details, view and participate in the open source project development.
+
+## 2. Search for open source projects
+
+There are two search boxes to search for
+
+### Open Source project search box
+
+Search item:
+
+
+
+Search results:
+
+
+
+### Menu bar search box
+
+Search item:
+
+
+
+Search results:
+
+
\ No newline at end of file
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/快速开始/注册GitLink账号.md b/i18n/en/docusaurus-plugin-content-docs/current/快速开始/注册GitLink账号.md
new file mode 100644
index 0000000..851dc17
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/快速开始/注册GitLink账号.md
@@ -0,0 +1,27 @@
+---
+sidebar_label: 'Register a GitLink account'
+sidebar_position: 1
+---
+
+# Register a GitLink account
+
+## 1. Click ** Register Now ** button
+
+
+
+## 2. Fill in the registration information
+
+- Mobile number registration
+
+ 
+
+- Email registration
+
+ 
+
+## 3. Registration completed
+
+After filling in the required information, click Register. After successful registration, you will enter the personal homepage
+
+
+
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/服务协议/GitLink服务协议.md b/i18n/en/docusaurus-plugin-content-docs/current/服务协议/GitLink服务协议.md
new file mode 100644
index 0000000..c6c5b85
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/服务协议/GitLink服务协议.md
@@ -0,0 +1,34 @@
+---
+sidebar_label: 'GitLink service agreement'
+sidebar_position: 1
+---
+
+Dear users, hello!
+
+Welcome to use the GitLink platform. Before using the GitLink Platform, please carefully read and abide by the GitLink Service Agreement (hereinafter referred to as the "Agreement"). Please be sure to read carefully and fully understand the terms of the Agreement.
+When you click "read and agree to this Service Agreement" during the registration process, successfully registering as a user of the GitLink Platform in accordance with the registration process means that you have fully read, understood and fully accepted all terms of this Agreement. You undertake to accept and abide by the provisions of this Agreement, and you shall not claim that this Agreement is invalid or certain provisions of this Agreement are invalid, or require the cancellation of this Agreement on the grounds that you have not read the contents of this Agreement.
+
+## 一、GitLink Platform Rights and obligations
+1. Respect for user privacy: Respecting user privacy and ensuring user privacy security is a basic policy of GitLink platform;
+2. Management of Platform users: GitLink Platform manages platform registered users according to national laws, local laws and international laws and other standards as well as the rules of the industry;
+3. Deal with user feedback: The relevant staff of GitLink platform will timely deal with user feedback problems and give timely replies.
+
+## 二、Rights and Obligations of Users
+When using the GitLink platform, users must comply with the following principles:
+
+1. Comply with the relevant laws and regulations of China;
+2. Do not use network services for illegal purposes;
+3. Do not interfere with and disrupt network services;
+4. Comply with all network protocols, regulations, procedures and practices for the use of network services;
+5. Do not transmit any illegal, harassing, defamatory, abusive, threatening, hurtful, vulgar, obscene and other information;
+6. Not to transmit any information that incites others to commit criminal acts;
+7. Users shall not intentionally or negligently damage the legitimate rights and interests of GitLink Platform.
+
+## 三、About responsibility
+In view of the special nature of the network service, the User agrees that the GitLink team has the right to change, interrupt and upgrade part of the network service with prior notice. The GitLink team does not guarantee that network services will not be interrupted, but promises to quickly restore service within an affordable time for users, while ensuring the security and reliability of user data.
+
+## 四、Modification of the Terms of Service
+The GitLink team reserves the right to modify this Agreement as necessary, and in the event of any change, these terms may be updated by the GitLink team without prior notice, and the revised terms will effectively replace the original Terms of Service once published on the website. You can always check the latest version of the Terms of Service.
+
+
+The GitLink team reserves the right of final interpretation of this Agreement.
\ No newline at end of file
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/服务协议/_category_.json b/i18n/en/docusaurus-plugin-content-docs/current/服务协议/_category_.json
new file mode 100644
index 0000000..e3ee1cb
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/服务协议/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "服务协议",
+ "position": 100
+}
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/疑修/_category_.json b/i18n/en/docusaurus-plugin-content-docs/current/疑修/_category_.json
new file mode 100644
index 0000000..71829c3
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/疑修/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "疑修(Issue)",
+ "position": 4
+}
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/疑修/标记管理.md b/i18n/en/docusaurus-plugin-content-docs/current/疑修/标记管理.md
new file mode 100644
index 0000000..e675967
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/疑修/标记管理.md
@@ -0,0 +1,24 @@
+---
+sidebar_label: 'Mark management'
+sidebar_position: 6
+---
+
+# Tag Management
+
+In the content editing page of doubtful repair, you can set marks according to the types of doubtful repair. The existence of marks facilitates the screening of target doubtful repair in the doubtful repair list, and improves the efficiency of project development management.
+GitLink defaults to defect, Feature, question, Support, task, assist, shelved, document, Test, and repeat, each with a different meaning and color symbol:
+
+- **Defects:** indicates an unexpected problem or error;
+- **Function:** indicates new function application;
+- **Doubt:** indicates doubt;
+- **Support:** Indicates a specific function or requirement;
+- **Task:** Indicates the task to be assigned;
+- **Assistance:** indicates the need for community user assistance;
+- **Shelved:** indicates that this issue will not be continued for the time being;
+- **Documentation:** indicates documentation material supplement;
+- **Test:** indicates the need to test;
+- **Repeat:** indicates that a similar revision already exists.
+
+
+In addition, **project members** can modify the meaning or color of the mark, create new marks and delete marks according to their needs or habits.
+
\ No newline at end of file
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/疑修/疑修列表.md b/i18n/en/docusaurus-plugin-content-docs/current/疑修/疑修列表.md
new file mode 100644
index 0000000..3cdb1bc
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/疑修/疑修列表.md
@@ -0,0 +1,13 @@
+---
+sidebar_label: 'List of Issue'
+sidebar_position: 4
+---
+# List of Issue
+
+For all issues created during the process of project development, can be suspected in **Issue** interface unified view, as shown in the figure below for [TruelyOpenSource] indeed (https://www.gitlink.org.cn/Gitlink/forgeplus) under the project of suspected Issue list.
+
+
+
++ **Create Issue**：Under the Issue list interface, clicking the“**Create Issue**”button allows for the creation of a new issue, as detailed in the ***Issue created*** section；
+
++ **Filter issue** : The list of issue supports different criteria, including publisher, mark (see ***Mark management***), milestone (see ***Milestone Management***), person in charge, status and start/end date, etc.; It also supports keyword search and sorting by various sorting rules.
\ No newline at end of file
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/疑修/疑修创建.md b/i18n/en/docusaurus-plugin-content-docs/current/疑修/疑修创建.md
new file mode 100644
index 0000000..332299c
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/疑修/疑修创建.md
@@ -0,0 +1,20 @@
+---
+sidebar_label: 'Issue created'
+sidebar_position: 2
+---
+# Issue created
+
+1. Enter the "**Code base**" interface of the project that needs to be released, and click the "**+Doubtful repair**" button at the top to enter the doubtful repair release interface, as shown in the following picture:
+
+
+
+2. Start to create the doubt modifier, including the doubt modifier title and content. When entering the doubt modifier content, you can adopt the simple and flexible [Markdown syntax](https://markdown.com.cn/) and click the function button above at the same time; Then upload the required attachment content; Finally click the "**Create**" button to submit your first doubtful fix🎉🎉🎉
+
+
+
+3. In addition, when creating a doubt modifier, you can use the symbol **`#`** to quickly add the doubt modifier that needs to be referenced, and then provide auxiliary information for the current doubt modifier; As shown in the figure below, after typing **`#`**, a list of referable doubtful fixes will pop up. After sliding the mouse or entering the doubtful fix number to select the doubtful fix that needs to be referenced, a link to the doubtful fix will be automatically added🔗
+
+
+
+
+
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/疑修/疑修状态变更.md b/i18n/en/docusaurus-plugin-content-docs/current/疑修/疑修状态变更.md
new file mode 100644
index 0000000..4635a56
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/疑修/疑修状态变更.md
@@ -0,0 +1,19 @@
+---
+sidebar_label: 'Issue state change'
+sidebar_position: 3
+---
+# Issue state change
+
+**Issue** is essentially a development task, and the development task with the development of activities, its status will change, and "**status**" is used to track and record the change of development activities. As shown in the figure, the **status** of the issue in GitLink includes five categories: "New", "solving", "solved", "closed" and "rejected", which are used to indicate the progress of the development task.
+
+
+
++ **Added** : The default status of the newly created issue is "Added";
+
++ **Being resolved** : If a created issue is in the process of being resolved, change the issue status to "Being resolved" at this time;
+
++ **Solved** : The issue has been solved by the developer, and its status can be changed to "Solved".✅；
+
++ **Off** : Issues that have been solved or are not necessary to continue can be set to "off";
+
++ **Reject** : If the developer assigned to fix the issue refuses to process the issue, the issue can be set to Reject status❌.
\ No newline at end of file
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/疑修/疑修简介.md b/i18n/en/docusaurus-plugin-content-docs/current/疑修/疑修简介.md
new file mode 100644
index 0000000..39464f6
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/疑修/疑修简介.md
@@ -0,0 +1,17 @@
+---
+sidebar_label: 'Introduction to Issue'
+sidebar_position: 1
+---
+# Introduction to Issue
+
+**Issue** management module mainly provides project team members with **development task** release, assignment, tracking and other functional services.
+
+
+
+**Notes**
+
+1. **Xiu** is a post that can track the progress of development tasks, so it supports participants' replies and comments, see ***Comments and operation records*** section;
+
+2. The default types (marks) of **Issue** include defects, functions, tasks, support, weekly reports, etc., see the section ***Mark Management*** for details;
+
+3. You can set the start and end time for **Issue**, and designate the person responsible for solving the task, the day before the deadline for Issue, the system will automatically send a reminder message for the task publisher and the assigned person.
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/疑修/评论及操作记录.md b/i18n/en/docusaurus-plugin-content-docs/current/疑修/评论及操作记录.md
new file mode 100644
index 0000000..a654b3b
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/疑修/评论及操作记录.md
@@ -0,0 +1,18 @@
+---
+sidebar_label: 'Comments and operational records'
+sidebar_position: 5
+---
+
+# Comments and operation records
+### Comments
+Each session is equivalent to a post that can be tracked, so it supports comments and replies, not just project members, but anyone can comment and reply under a session, post questions or opinions, and communicate.
+
+
+### Statement of issue
+Users can issue a "doubt repair statement" for any doubt repair, leaving their own ideas for the solution of the doubt repair. Click "Statement" on the right side of the details of the revision, you can edit the message, click "confirm" after editing, you can release the statement, as shown in the picture below:
+
+
+### Operation record
+Anyone can create a modifier, but note that non-project members can only modify the modifier they create, and project members have permission to modify all the modifier.
+All editing actions for a doubt, including **Create doubt, add leader, remove leader, change status, change priority, add mark, remove mark, add milestone, remove milestone, set associated branch, remove associated branch, set start date, and set end date**, are recorded in the action log.
+
\ No newline at end of file
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/疑修/里程碑管理.md b/i18n/en/docusaurus-plugin-content-docs/current/疑修/里程碑管理.md
new file mode 100644
index 0000000..0c6f254
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/疑修/里程碑管理.md
@@ -0,0 +1,34 @@
+---
+sidebar_label: 'Milestone management'
+sidebar_position: 7
+---
+
+# Milestone Management
+
+### Milestone introduction
+Milestones are mainly used by the project team to provide support for project development and version release, and each milestone can be associated with multiple development tasks.
+
+### Create milestones
+Project members can create milestones based on the following steps:
+1. Enter the **"Milestone screen"** of the target project. The list of created milestones is displayed on the screen. All created milestones can be divided into two categories: **"Closed"** and **"Open"**.
+2. Click the **"+Create Milestone"** button at the top to enter the milestone creation interface;
+
+
+3. After filling in the title (required), description (required), deadline (optional), click **"Create Milestone"** in the lower right corner to complete the creation of a new milestone.
+
+
+### Associated milestones
+Project members can associate fixes to milestones so that milestones contain a clear list of fixes. The main steps are as follows:
+1. Click the target query in the query list;
+2. Edit the Milestone property and select the milestone to be associated.
+
+
+### Other operations
+- **Open milestones**
+- **Close Milestones**
+- **Editing Milestones**
+- **Delete milestones**
+
+The above operations can be processed in the milestone list to achieve the target milestone, as shown in the following figure:
+
+
\ No newline at end of file
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/第三方服务/WebIDE.md b/i18n/en/docusaurus-plugin-content-docs/current/第三方服务/WebIDE.md
new file mode 100644
index 0000000..5f49627
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/第三方服务/WebIDE.md
@@ -0,0 +1,122 @@
+---
+sidebar_label: 'WebIDE'
+sidebar_position: 9
+
+---
+## WebIDE background
+The traditional code hosting platform provides Git/SVN management of the code warehouse, which can do code browsing, code review, defect management, CI pipeline and other code-related activities on the platform. Among them, the editor component used for code browsing and code review is generally CodeMirror, and the code highlighting uses highlight.js, often providing only the scene of reading the code. Ant R & D performance Department cloud R & D team through self-developed OpenSumi framework and based on OpenSumi framework for the Web IDE (no remote container) scene of the fast version of the Web IDE framework, It collids with the internal code hosting platform to create innovative, browser-only, IDE style code reading, code writing, code submission, code running, code review and other scenarios, which greatly improves the efficiency of users' code reading, code review, light research and development and other scenarios on the code hosting platform. This Ant R & D efficiency cloud R & D team and CCF (China Computer Society) GitLink code hosting platform cooperation, the internal speed version of the Web IDE applied to the Gitlink code hosting platform, to solve a lot of experience problems that have been feedback by users for a long time.
+
+## Web IDE core competencies
+The standard version marked with containers, the speed version IDE mainly read, write, run, submit and other aspects were explored:
+
+**1. Read:**
+- a. Adapted to a variety of code hosting platforms, such as Gitlink, Github, Gitlab and other code hosting platforms, businesses can easily use code services
+- b. Built-in syntax highlighting support for dozens of common languages including Java, TS/JS, C++, Go, Python, Rust, and more
+- c. Supports code reading aid plug-ins such as Git Blame and GitGraph
+
+**2. Write:**
+- a. Supports online language services such as HTML, CSS, JS, and Markdown, and supports error diagnosis
+-b. The browser file system
+
+**3. Run:**
+- a. Supports the front-end code running scheme based on Skypack
+- b. Supports Python running based on Pyodide
+
+**4. Submit:**
+- a. Supports WebSCM and provides branch switching, adding, and code submission capabilities
+
+If the browser IDE components represented by CodeMirror and Monaco are Web IDE 1.0, then the fastest version of the Web IDE with the above capabilities is Web IDE 2.0. The Super version Web IDE solution was launched in Ant in April 2021, and carried out many scenarios such as code reading, code review, online written test, code inspection result feedback, and lightweight online research and development. vscode.dev and github dev were launched in August of the same year. The super version of the Web IDE takes advantage of the high scalability of the OpenSumi framework, and the business can customize the modules and plug-ins more deeply, so that the business has more imagination space.
+
+## Code reading
+When reading code on the code hosting platform, it is often necessary to see where the current method is referenced and where the current interface is implemented. The Super version Web IDE provides the ability of editor + plug-in to solve the above user needs:
+
+
+ Code Reference View
+Gitlink completes the ability to view the editor Blame by implementing the Blame plugin:
+
+
+ Current line author, modification date View
+
+
+## Code review
+Users of the code review feature have long reported the following questions:
+
+- 1. Lack of language services, low reading efficiency: lack of code highlighting, prompt, jump, view reference and outline functions
+- 2. Poor browsing experience of large PR: statistics show that Gitlink PR has an average of 14-17 change files, and the traditional code Review interaction is generally the streaming display of code Diff components. For some scenarios with many change files and large internal files, the review experience is poor, and it often takes a long time to wait.
+- 3. The code modification process is heavy and time-consuming: the code Diff component only has the ability to read, and it cannot quickly modify some spelling or lint errors, which needs to be modified and submitted after finding the corresponding file locally. In response to the above needs, Ant Cloud R&D team and Gitlink have created an IDE style code review scenario:
+
+
+ Code review in IDE mode
+- 1. Change tree a. You can browse the change tree in tile and tree form b. Change Tree Using OpenSumi Recycle, you can also view change files by virtual scrolling in high performance
+- 2. Toolbar a. Provides basic Settings for the IDE editor, such as font size, encoding, ignoring final Spaces, etc. b. Quick Switching Comparison between the current branch version and the baseline c. Quick locating of change files, viewing Settings, and quick execution of shortcut keys
+- 3. Editor a. Folding non-changed content through monaco fold capability b. Custom comment component embedded editor
+In addition to the above capabilities, Gitlink also supports quick code changes during code review:
+
+
+Code can be modified during code review
+
+## Gitlink Web IDE
+Gitlink code reading scene although access to the fast version of the IDE editor, but the file tree, code search, shortcut keys, IDE skin, etc., are very different from the IDE used in the usual development habits, and most users just clone the code to the local code reading, although ensuring a consistent experience, but the whole link is cumbersome and time-consuming.
+Based on this insight, Ant Cloud R&D team and Gitlink launched the Gitlink Web IDE, which can quickly open the Web IDE to access and read the project warehouse code with one click, realize the seamless connection between the project and the IDE, and maintain the daily preferences and habits of R&D students. It is also perfectly compatible with the Gitlink code hosting platform. More importantly, by running a super fast IDE directly on the browser without a container, you can ensure an instant experience.
+
+#### **1. Quick experience **
+You can experience it from the Gitlink Warehouse home page Web IDE entry
+
+Gitlink WebIDE Entrance
+
+#### **2. Code Viewing Experience **
+Code browsing experience consistent with traditional ides. File trees, skin styles, and shortcuts are available.
+#### **3. Language features **
+- 1. Support syntax highlighting in nearly 40 languages
+- 2. Supports Language Server Protocol (LSP) language features based on JavaScript/TypeScript, HTML, CSS, JSON, and Markdown, with intelligent prompts, outline information, and jumps within a file.
+
+JS Language Service Tips
+
+- 3. Provide Java, Go, Python, C++, Php online language service capabilities, support simple definition jump, find references and other functions, so that everyone more convenient to read the code
+
+
+Python View references
+
+#### **4. Branch creation and Switchover **
+Click the branch name in the lower left corner to create/switch branches.
+
+
+ Branch creation and switching
+
+
+#### **5. File search **
+Use CMD/Ctrl + P to invoke the file search panel
+
+
+ File Search panel
+
+#### **6. Line highlight **
+To highlight a single or multiple lines, click the line number to highlight the line, and hold down Shift to select multiple consecutive lines.
+
+Multiple selected lines are highlighted
+
+#### **7. Blame**
+Supports viewing single-line blame information, and displays details after the hover.
+
+Blame detailed information
+
+#### **8. Graph**
+graph view is supported to view branch commits history and file changes for each commit, as well as file diff viewing. Click Git Graph at the bottom left corner of the status bar or enter View Git Graph in the command panel to open the Git Graph view.
+
+Graph detailed information
+
+
+#### **9.WebSCM**
+It is very common for development to develop multiple requirements in parallel on a daily basis, often changing some small but necessary logic, and perhaps your local environment is already developing the next requirement, frequent branch switching and parallel changes are prone to error. Switch branch change submissions quickly with the Gitlink Web IDE without interrupting the local development process.
+
+WebSCM
+
+
+#### **10. Code running online **
+Currently, without containers, most applications can only run front-end code. The Gitlink Web IDE integrates the lighter CodeSwing plug-in based on skypack, which can run front-end code in the super speed version, and the code version is managed using Gitlink. Combined with the above WebSCM capabilities, front-end code initialization, writing, previewing, and code submission can be done in under a minute.
+
+Front-end code run
+
+With the development of Webassembly technology, some back-end languages can also run in the browser, and at Google IO 2021, StackBlitz showed off their most recent technology: WebContainer, the ability to compile the language runtime into Webassembly to run on the browser. The Code-Runner For-Web plug-in, combined with Pyodide, already moves Python running into the browser, and the new Zoom Edition also integrates the plug-in by default.
+
+Python code run
\ No newline at end of file
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/第三方服务/_category_.json b/i18n/en/docusaurus-plugin-content-docs/current/第三方服务/_category_.json
new file mode 100644
index 0000000..a1d9d5b
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/第三方服务/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "第三方服务",
+ "position": 9
+}
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/第三方服务/跨平台代码同步.md b/i18n/en/docusaurus-plugin-content-docs/current/第三方服务/跨平台代码同步.md
new file mode 100644
index 0000000..91c5d94
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/第三方服务/跨平台代码同步.md
@@ -0,0 +1,84 @@
+---
+sidebar_label: 'Cross-platform code synchronization service'
+sidebar_position: 2
+---
+
+### Function introduction
+
+Cross-platform warehouse code synchronization service is used for the bidirectional synchronization of warehouse code between different code hosting platforms. Users bind warehouse branches of different platforms. When a push event of any warehouse branch is monitored by webhook, the code push will be automatically synchronized to another warehouse in real time to realize automatic synchronization of branches and submission information between different platforms (code hosting platforms are limited to github and gitee).
+
+
+
+
+The synchronization service not only meets the requirement of synchronization of the branch of the code base of two platforms, but also supports the synchronization of the code warehouse of up to three platforms, as shown in the following figure
+
+
+
+### Configure bidirectional synchronization
+
+1. Open the Services tab of the code base where synchronization is to be created, and enable the cross-platform code synchronization service.
+
+
+
+2. configure cross-platform synchronization warehouse, support github and gitee. You need to enter the code base address (both git address and website access address are supported) and configure the corresponding token for authorization synchronization. Pay attention to the permission of the token and whether it has expired.
+Github configuration: Personal profile picture →Settings→Developer Settings→Personal access tokens (classic)→Generate new token→ Check repo button → Save
+2. configure cross-platform synchronization warehouse, support github and gitee. You need to enter the code base address (both git address and website access address are supported) and configure the corresponding token for authorization synchronization. Pay attention to the permission of the token and whether it has expired.
+Github configuration: Personal profile picture →Settings→Developer Settings→Personal access tokens (classic)→Generate new token→ Check repo button → Save
+Gitee is configured as follows: Profile picture → Settings → Private Token → Generate new token → Check projects permissions → Submit
+
+
+
+3. When the synchronization warehouse is created for the first time, the user needs to manually create a webhook in the code base of the target warehouse to listen to the push event of the warehouse, so as to push the code to other synchronization warehouses to complete the synchronization. The synchronization steps are as follows:
+
+① Click the "Copy Link" button to copy the address used by the platform to receive webhook requests
+
+
+
+
+②Go to the webhook page of the target warehouse and create a webhook. Take github as an example
+
+
+
+③Paste the link and ensure that the webhook supports push event listening and has been successfully activated
+
+
+
+4. After the warehouse configuration binding is complete, the specified synchronization branches of the two warehouses need to be bound to establish the first synchronization direction. Note: The policy for the first synchronization is unidirectional code push. Select the synchronization direction carefully to enable synchronization to avoid code overwriting
+
+
+
+5. complete the binding of the branch, and immediately execute a synchronization according to the selected synchronization direction after binding. The webhook then monitors that any branch has code push and pushes the code to the synchronization code of another bound branch in real time
+
+
+
+### Manage synchronization branches
+
+
+After the synchronization branch configuration is complete, the user can complete a series of operations in the synchronization branch list
+① Add and bind a new synchronization branch. For example, Develop branches have been established in two warehouses and synchronization of feature branches needs to be established. You can add
in real time.
+② Query the latest synchronization time and synchronization status between two branches. If the synchronization fails, you can query the reason for the log analysis failure in the synchronization record.
+③ Add synchronous warehouse, if you have bound github synchronous warehouse, want to import a warehouse in gitee for development, and want to complete real-time branch synchronization of multiple warehouses.
+④ View the synchronization configuration, which can be used to query the address of the synchronization warehouse, GitLink is used to accept the address of the third-party webhook request, and update the token. In case of token expiration
+⑤ Query synchronization records, including the code change party, synchronization time, synchronization status and commt id of previous synchronization, and query synchronization logs.
+After the synchronization branch configuration is complete, the user can complete a series of operations in the synchronization branch list
+① Add and bind a new synchronization branch. For example, Develop branches have been established in two warehouses and synchronization of feature branches needs to be established. You can add
in real time.
+② Query the latest synchronization time and synchronization status between two branches. If the synchronization fails, you can query the reason for the log analysis failure in the synchronization record.
+③ Add synchronous warehouse, if you have bound github synchronous warehouse, want to import a warehouse in gitee for development, and want to complete real-time branch synchronization of multiple warehouses.
+④ View the synchronization configuration, which can be used to query the address of the synchronization warehouse, GitLink is used to accept the address of the third-party webhook request, and update the token. In case of token expiration
+⑤ Query synchronization records, including the code change party, synchronization time, synchronization status and commt id of previous synchronization, and query synchronization logs.
+⑥ Stop and start synchronization, which is equivalent to a synchronization switch and can be started and stopped at any time
+
+
+
+### Precautions
+
+1. When establishing synchronization, the tool will push the code once according to the first synchronization direction selected by the user. Please choose the synchronization direction carefully to avoid the risk of code being overwritten. After synchronization is established, the push event triggered by the webhook will be synchronized to the other party. Do not submit code in multiple warehouses at the same time to prevent conflicts.
+2, currently only support personal warehouse synchronization, organizational warehouse synchronization is not supported, please look forward to
+3. During the configuration, check whether the token permission includes warehouse read and write. At the same time, please check whether the token has expired. If it has expired, please click [view synchronous configuration] button to enter the page to update the token
.
+1. When establishing synchronization, the tool will push the code once according to the first synchronization direction selected by the user. Please choose the synchronization direction carefully to avoid the risk of code being overwritten. After synchronization is established, the push event triggered by the webhook will be synchronized to the other party. Do not submit code in multiple warehouses at the same time to prevent conflicts.
+2, currently only support personal warehouse synchronization, organizational warehouse synchronization is not supported, please look forward to
+3. During the configuration, check whether the token permission includes warehouse read and write. At the same time, please check whether the token has expired. If it has expired, please click [view synchronous configuration] button to enter the page to update the token
.
+4. During the configuration, carefully check whether the listening events of Webhooks of other platforms contain push events and whether webhooks are activated
+
+
+
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/第三方服务/重睛鸟代码溯源.md b/i18n/en/docusaurus-plugin-content-docs/current/第三方服务/重睛鸟代码溯源.md
new file mode 100644
index 0000000..bd97250
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/第三方服务/重睛鸟代码溯源.md
@@ -0,0 +1,67 @@
+---
+sidebar_label: "Heavy eye bird code traceability"
+sidebar_position: 1
+---
+
+## Code analysis entry
+
+
+
+ Code analysis entry
+Page description:
+1. Users can click the "Service" menu tab to enter the service page.
+2. The warehouse manager can turn on/off the visibility of the code analysis menu in the project navigation in the "Warehouse Settings" tab, as shown below:
+
+
+
+ Project navigation
+
+## Code analysis detection
+
+
+
+Code analysis detection
+
+
+
+ New analysis
+Page description:
+1. This page is displayed when there is no historical analysis record.
+2. The "New Analysis" button is only visible to warehouse administrators. When warehouse developers, observers, and visitors visit this page, the New Analysis button is not visible.
+3. Click the "New Analysis" button to determine whether to enable the code analysis function.
+
+## Branch selection
+
+
+
+ Branch selection
+Page description :
+1. When the user clicks the "New Analysis" button, it pops up that the new analysis needs to select and fill in the branch.
+2. The detection type and detection parameters in the figure are default values, which are not allowed to be modified by users. They are displayed here on the interface and only serve to prompt users and let them know.
+3. Click "Start Detection" here to start detection based on the selected branch and create a new detection list.
+
+## Tabular presentation
+
+
+
+Tabular presentation
+Page description :
+1. When the number of rows in the detection list exceeds one row, the filter drop-down box of the branch name is provided on the left of the "New Analysis" button, and the options in the drop-down box are the sets of branches in the list. If the warehouse has branches 1, 2, 3, 4, 5, and there are branches 3 and 4 in this list, then the branch type in the drop-down box is only 3 and 4.
+2. When a new analysis task is being detected, a percentage progress bar is displayed in the detection status to display the existing progress.
+3. Click the "Rescan" button, and a pop-up window for new analysis will pop up. This pop-up window saves all the last configured branch information, and the detected branch cannot be modified (the drop-down box of the branch is gray). After confirming the creation, a new detection data is added.
+
+## Result presentation
+
+
+
+Result presentation
+Page description:
+1. The user clicks the "View" button in the code detection "operation" list, and the result display page will be expanded on the current page. When the user clicks the "View" button again, the result display page is withdrawn; When the user clicks the "View" button of other test records, the result page of other test records will be expanded, and the currently expanded result display page will be retrieved;
+2. When the detection state is "failed" or the current state is "Testing", the "View" button will be grey and cannot be clicked;
+3, the result display page fetch code traceability existing pages, embedded in GitLink can be, no need to design again.
+
+## User operation flow
+
+
+
+User operation flow
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/组织管理/_category_.json b/i18n/en/docusaurus-plugin-content-docs/current/组织管理/_category_.json
new file mode 100644
index 0000000..bb58afa
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/组织管理/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "组织管理",
+ "position": 3
+}
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/组织管理/组织创建及设置.md b/i18n/en/docusaurus-plugin-content-docs/current/组织管理/组织创建及设置.md
new file mode 100644
index 0000000..a77f561
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/组织管理/组织创建及设置.md
@@ -0,0 +1,31 @@
+---
+sidebar_label: 'Organization creation and set'
+sidebar_position: 2
+---
+# Organization Creation
+
+ In *https://www.gitlink.org.cn* page click the "+" symbol at the top of the navigation can organize the new operation.
+
+ 
+
+ Input in the new page **organization account** , **organization name**, **description** ,**region**,**visibility** and **organization head** information, click the "**create organization**" button to complete the organization's creation.
+
+ 
+
+## Organization account
+
+ 
+
+ **注**：只能使用以字母、数字开头，包含字母、数字、下划线、横杠等，长度4到20个字符
+
+## Organization name and description
+
+ 
+
+ **Note** : This field is required and must not be blank
+
+## Visibility
+
+ 
+
+ **Note** : There are three categories of visibility: public, restricted (visible only to logged in users), and private (visible only to organization members).
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/组织管理/组织团队管理.md b/i18n/en/docusaurus-plugin-content-docs/current/组织管理/组织团队管理.md
new file mode 100644
index 0000000..489e522
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/组织管理/组织团队管理.md
@@ -0,0 +1,34 @@
+---
+sidebar_label: 'Organize team management'
+sidebar_position: 3
+---
+# Organize team management
+
+## Create an organizational team
+Click the "New Team" button on the organization information page to create a team that belongs to that organization (the platform creates an "Owners" team by default, with the organization's creators as members).
+
+On the team creation page, enter the team identity, team name, team description, project permissions, and version library permissions, and click "New Team" to complete the creation of the team.
+
+ 
+
+## View the organization team
+
+Click on a team name in the organization information page to view the details of the team, which includes the team name, description and other information, in addition to listing the members and projects associated with the team.
+
+ 
+
+## Manage and organize the team
+
+Click the "Team Settings" button in the team information page to manage the team
+
+ - Basic Settings: Modify the basic information of a project, such as the name and description.
+ 
+
+ - Team member management: Add new members to the team or remove existing members.
+ 
+
+ - Team Project management: Associate new projects (projects that the organization has already created) or remove associated projects for the team.
+ 
+
+
+
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/组织管理/组织成员管理.md b/i18n/en/docusaurus-plugin-content-docs/current/组织管理/组织成员管理.md
new file mode 100644
index 0000000..df59481
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/组织管理/组织成员管理.md
@@ -0,0 +1,23 @@
+---
+sidebar_label: 'Members Management'
+sidebar_position: 4
+---
+ In the member management interface, we can see all the members involved in a project as well as their email numbers and roles, roles are divided into manager, developer and reporter, the difference between the three is that the authority is inconsistent, the manager is the highest level role has all the rights, other rights decline. As shown in the figure below, you can also invite new members to the group or adjust the role level of the team members, or delete the team members as required.
+ 
+# Members Management
+
+ **Member Management** in the **repository Settings** in the project managed by an individual can enter the member management interface
+
+ 
+
+## Member query and add
+In the member management interface, you can query and add organization members
+
+ 
+
+## Member invitation permission Settings
+The administrator can set the permissions for inviting members
+ 
+In addition, you can copy the invite link to make it easier to invite members to join the project
+
+ **Note** : This feature is only visible to administrators
\ No newline at end of file
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/组织管理/组织简介.md b/i18n/en/docusaurus-plugin-content-docs/current/组织管理/组织简介.md
new file mode 100644
index 0000000..dba5023
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/组织管理/组织简介.md
@@ -0,0 +1,28 @@
+---
+sidebar_label: 'Organization Profile'
+sidebar_position: 1
+---
+
+# Organization Profile
+
+Organizations are shared accounts where business and open source projects collaborate across multiple projects simultaneously, with sophisticated security and management features. Multiple individual accounts can collaborate on shared projects by joining the same organizational account.
+
+Your team can collaborate on GitLink by using an organization account, which acts as a container for shared work and gives the work a unique name and brand. At the same time, the platform supports organizations to publish news updates on the "Organization Details" page, showing content such as project overview and warehouse details
+
+ 
+
+## As an organization owner
+
+Managing your organization effectively is your mission.
+
+The organization provides a centralized collaboration and sharing center for your teams to work together, share resources and communicate more effectively.
+
+To simplify access management and enhance collaboration, you can create nested teams that reflect the group structure. You can group people according to their roles or projects and assign tasks.
+
+ 
+
+The platform also enables organization owners to manage custom Settings for data access.
+
+## As a member of the organization
+
+You can collaborate with an unlimited number of people on multiple projects through organization, with like-minded people, through division of labor and writing, participate in the development process, publish or work on problems.
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/组织管理/组织项目管理.md b/i18n/en/docusaurus-plugin-content-docs/current/组织管理/组织项目管理.md
new file mode 100644
index 0000000..5687eb6
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/组织管理/组织项目管理.md
@@ -0,0 +1,12 @@
+---
+sidebar_label: 'Organizational project management'
+sidebar_position: 5
+---
+## Create an organization project
+
+Click the "New Project" button on the organization information page to create a hosted or mirrored project that belongs to that organization.
+
+ 
+
+ **Note** : In the drop-down option of the "Owner" column, you can select: Individual, organization, team
+
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/维基/_category_.json b/i18n/en/docusaurus-plugin-content-docs/current/维基/_category_.json
new file mode 100644
index 0000000..9072bcc
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/维基/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "维基(Wiki)",
+ "position": 7
+}
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/维基/模板导入及导出.md b/i18n/en/docusaurus-plugin-content-docs/current/维基/模板导入及导出.md
new file mode 100644
index 0000000..9cf6181
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/维基/模板导入及导出.md
@@ -0,0 +1,15 @@
+---
+sidebar_label: 'Import and export templates'
+sidebar_position: 2
+---
+
+# Indeed Open Source Help Center
+
+## Template import and export management
+#### 1. Import the template
+By clicking the **Import template** button on the wiki interface, you can import local txt, markdown and other formats to create Wiki documents. At present, this function of the platform is still under development and testing
+
+#### 2. Export the template
+At present, this function of the platform is still under development and testing
+
+
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/维基/维基页面管理.md b/i18n/en/docusaurus-plugin-content-docs/current/维基/维基页面管理.md
new file mode 100644
index 0000000..6acf20f
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/维基/维基页面管理.md
@@ -0,0 +1,23 @@
+---
+sidebar_label: 'Wiki page management'
+sidebar_position: 1
+---
+
+
+# Indeed Open Source Help Center
+
+## Wiki interface management
+#### 1. Wiki interface
+The GitLink project has arranged a special **Wiki interface** to show some aspects of the project
+
+
+#### 2. Create wiki content
+In the initial Wiki interface, click **Create Wiki document** or **Import Template** to edit Wiki document
+
+
+#### 3. Edit the Wiki documentation
+Click **Create Wiki Document** to jump to the edit screen, the initial content is a blank document
+
+You can also import templates by checking *Add template*. The templates provided by the platform include *weekly report* and *monthly report* formats
+
+After editing, click Save in the lower left corner
\ No newline at end of file
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/通知/_category_.json b/i18n/en/docusaurus-plugin-content-docs/current/通知/_category_.json
new file mode 100644
index 0000000..aabbf21
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/通知/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "通知",
+ "position": 10
+}
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/通知/通知简介.md b/i18n/en/docusaurus-plugin-content-docs/current/通知/通知简介.md
new file mode 100644
index 0000000..42374ba
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/通知/通知简介.md
@@ -0,0 +1,29 @@
+---
+sidebar_label: 'Notification introduce'
+sidebar_position: 1
+---
+
+# Indeed Open Source Help Center
+
+## Notice brief
+#### 1. Notification type
+GitLink divides notifications into two types: "system notifications" and "@me" :
+* System notifications include "My status", "I created or am responsible for", "I manage the warehouse" three types of notifications:
+
+| System notification type | System notification content |
+| ----------- | ----------- |
+| My status | account has permission to change; To be pulled into or out of tissue; To be pulled in or out of the project; A new practice has been assigned to me; There are new merge requests assigned to me; |
+| Changes in the | status that I have created or am responsible for; Merge request status changes; |
+| The warehouse I manage | has some new repairs. There are new merge requests; There is a change in membership; Warehouse Settings are changed; |
+* "@me" notification currently supports using @ function to notify users in the dynamic list of user home page, course home page, and project home page:
+For example, when submitting doubtful repairs on the project home page, enter @ and select @other users from the drop-down list.
+ 
+
+#### 2. View notifications
+After login, you can view the number of notifications received next to your profile picture in the upper right corner of the platform. Move the cursor to the notification button to display the drop-down list to view the notifications of "System Notification" and "@Me" respectively. In the lower right corner of the drop-down list, all messages can be read with one click; Click the notification to jump to the notification details screen.
+
+
+
+
+Click the notification button to enter the message notification interface. On the "My Notifications" interface, you can select "Forward View Unread messages" and "All Messages have been Read with one click".
+
\ No newline at end of file
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/通知/通知设置.md b/i18n/en/docusaurus-plugin-content-docs/current/通知/通知设置.md
new file mode 100644
index 0000000..71c1063
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-docs/current/通知/通知设置.md
@@ -0,0 +1,20 @@
+---
+sidebar_label: 'Notification Settings'
+sidebar_position: 2
+---
+
+
+# Indeed Open Source Help Center
+
+## Notification Settings
+#### 1. Go to the notification setting page
+Click the notification button on the home page to enter the notification setting interface;
+
+
+Or select Settings from the profile picture drop-down list to enter the message notification setting interface;
+
+
+#### 2. Set notification
+Notification Management allows you to set the mode of receiving notifications. By default, all notifications are received by means of in-site messages. You can add email modes for important notification types by selecting this option.
+
+
\ No newline at end of file
diff --git a/i18n/en/docusaurus-plugin-content-pages/index.md b/i18n/en/docusaurus-plugin-content-pages/index.md
new file mode 100644
index 0000000..32d921d
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-pages/index.md
@@ -0,0 +1,102 @@
+
+# Get Started quickly
+The help documentation will help you understand how to use the GitLink platform, and let's contribute to open source innovation together!
+
+ View all documents
+ Introduction to Open source
+
+
+
diff --git a/i18n/en/docusaurus-plugin-content-pages/open.md b/i18n/en/docusaurus-plugin-content-pages/open.md
new file mode 100644
index 0000000..dd480c0
--- /dev/null
+++ b/i18n/en/docusaurus-plugin-content-pages/open.md
@@ -0,0 +1,40 @@
+Back
+
+
+
+# Open Source project introduction
+
+## What is open source?
+
+Open source means that software source code is open to the public, allowing anyone to view, use, modify, and distribute. Open source software is transparent, collaborative and sustainable, and attracts developers from all over the world to participate in an open way.
+
+## Benefits of open source
+
+- ** Transparency ** : The source code of open source software is open to everyone, and users can clearly understand the implementation principle of the software, increasing trust.
+** Collaboration ** : Open source software engages developers from around the world, forming a large community to work together to improve the software and share experiences and technologies.
+** Sustainability ** : Open source software generally has a longer life cycle because they do not rely on the support of a single entity.
+
+## Open source project classification
+
+### 1. Sort by license
+
+- **GPL License ** : Requires derivative works to be under the same license, ensuring that the code is free and open.
+- **MIT License ** : Allows the use, modification, and distribution of code without making the modified code open.
+- **Apache License ** : Similar to the MIT license, but with patent licensing provisions.
+
+### 2. Sort by type
+
+- ** Operating system ** : such as the Linux operating system.
+- ** Programming language ** : such as Python, JavaScript, etc.
+- ** Tool library ** : such as TensorFlow, React, etc.
+
+## How to participate in open source projects
+
+1. ** Find projects you're interested in ** : Browse projects on platforms like GitLink and choose the one that matches your skills and interests.
+2. ** Read the documentation ** : Have a deep understanding of the project's documentation and code, and be familiar with the existing contribution specifications and processes.
+3. ** Submit Contributions ** : You can contribute by submitting bug reports, fixing documentation errors, writing new features, etc.
+4. ** Networking and Learning ** : Join the project community to communicate and learn from other developers and share experiences.
+
+## Conclusion
+
+Open source projects are an important enabler of technology development, and by participating in open source projects, we can continuously improve our technical capabilities while also contributing to the open source community. It is hoped that more people can join the open source project and jointly promote the progress of science and technology.
diff --git a/i18n/en/docusaurus-theme-classic/footer.json b/i18n/en/docusaurus-theme-classic/footer.json
new file mode 100644
index 0000000..14f8999
--- /dev/null
+++ b/i18n/en/docusaurus-theme-classic/footer.json
@@ -0,0 +1,62 @@
+{
+ "link.title.社区": {
+ "message": "community",
+ "description": "The title of the footer links column with title=社区 in the footer"
+ },
+ "link.title.支持与服务": {
+ "message": "Support and service",
+ "description": "The title of the footer links column with title=支持与服务 in the footer"
+ },
+ "link.title.加入我们": {
+ "message": "Join us",
+ "description": "The title of the footer links column with title=加入我们 in the footer"
+ },
+ "link.item.label.网站首页": {
+ "message": "homepage",
+ "description": "The label of footer link with label=网站首页 linking to https://www.gitlink.org.cn"
+ },
+ "link.item.label.关于我们": {
+ "message": "About us",
+ "description": "The label of footer link with label=关于我们 linking to https://www.gitlink.org.cn/aboutus"
+ },
+ "link.item.label.教学实践": {
+ "message": "Teaching practice",
+ "description": "The label of footer link with label=教学实践 linking to https://www.gitlink.org.cn/educoder"
+ },
+ "link.item.label.合作伙伴": {
+ "message": "Business partner",
+ "description": "The label of footer link with label=合作伙伴 linking to https://forum.trustie.net/forums/5030/detail"
+ },
+ "link.item.label.API文档": {
+ "message": "API documentation",
+ "description": "The label of footer link with label=API文档 linking to https://forgeplus.trustie.net/docs/api"
+ },
+ "link.item.label.Git常用命令": {
+ "message": "Git Common Commands",
+ "description": "The label of footer link with label=Git常用命令 linking to https://git-scm.com"
+ },
+ "link.item.label.引擎使用手册": {
+ "message": "Engine manual",
+ "description": "The label of footer link with label=引擎使用手册 linking to https://forum.gitlink.org.cn/forums/7487/detail"
+ },
+ "link.item.label.服务协议": {
+ "message": "Service agreement",
+ "description": "The label of footer link with label=服务协议 linking to https://forum.trustie.net/forums/5029/detail"
+ },
+ "link.item.label.官网邮箱：gitlink@ccf.org.cn": {
+ "message": "Official website Email:gitlink@ccf.org.cn",
+ "description": "The label of footer link with label=官网邮箱：gitlink@ccf.org.cn linking to https://www.gitlink.org.cn"
+ },
+ "link.item.label.QQ群": {
+ "message": "QQ group",
+ "description": "The label of footer link with label=QQ群 linking to https://www.gitlink.org.cn"
+ },
+ "link.item.label.公众号": {
+ "message": "Public account",
+ "description": "The label of footer link with label=公众号 linking to https://www.gitlink.org.cn"
+ },
+ "copyright": {
+ "message": "©Copyright 2024 CCF 开源发展委员会
Powered by Trustie& IntelliDE 京ICP备13000930号
",
+ "description": "The footer copyright"
+ }
+}
diff --git a/i18n/en/docusaurus-theme-classic/navbar.json b/i18n/en/docusaurus-theme-classic/navbar.json
new file mode 100644
index 0000000..8817fe3
--- /dev/null
+++ b/i18n/en/docusaurus-theme-classic/navbar.json
@@ -0,0 +1,30 @@
+{
+ "logo.alt": {
+ "message": "gitlink",
+ "description": "The alt text of navbar logo"
+ },
+ "item.label.帮助中心": {
+ "message": "Help center",
+ "description": "Navbar item with label 帮助中心"
+ },
+ "item.label.回到主页": {
+ "message": "Back to Home",
+ "description": "Navbar item with label 回到主页"
+ },
+ "item.label.更多开源": {
+ "message": "More Open source",
+ "description": "Navbar item with label 更多开源"
+ },
+ "item.label.GitHub": {
+ "message": "GitHub",
+ "description": "Navbar item with label GitHub"
+ },
+ "item.label.Gitee": {
+ "message": "Gitee",
+ "description": "Navbar item with label Gitee"
+ },
+ "item.label.Stack Overflow": {
+ "message": "Stack Overflow",
+ "description": "Navbar item with label Stack Overflow"
+ }
+}
diff --git a/static/img/di_san_fang/重晴鸟代码溯源/用户操作流程（新）.png b/static/img/di_san_fang/重晴鸟代码溯源/用户操作流程.png
similarity index 100%
rename from static/img/di_san_fang/重晴鸟代码溯源/用户操作流程（新）.png
rename to static/img/di_san_fang/重晴鸟代码溯源/用户操作流程.png