diff --git a/.all-contributorsrc b/.all-contributorsrc
index 325be8578..753598d6c 100644
--- a/.all-contributorsrc
+++ b/.all-contributorsrc
@@ -1841,6 +1841,24 @@
"contributions": [
"code"
]
+ },
+ {
+ "login": "allcontributors[bot]",
+ "name": "allcontributors[bot]",
+ "avatar_url": "https://avatars.githubusercontent.com/in/23186?v=4",
+ "profile": "https://github.com/apps/allcontributors",
+ "contributions": [
+ "doc"
+ ]
+ },
+ {
+ "login": "wandercn",
+ "name": "wander",
+ "avatar_url": "https://avatars.githubusercontent.com/u/77320953?v=4",
+ "profile": "https://www.ffactory.org/",
+ "contributions": [
+ "doc"
+ ]
}
],
"contributorsPerLine": 8,
diff --git a/README.md b/README.md
index 1787e0c70..1ae4001e2 100644
--- a/README.md
+++ b/README.md
@@ -91,9 +91,12 @@ The installation instructions are on the [official website](https://wails.io/doc
## Sponsors
+
This project is supported by these kind people / companies:
-
+
+
+
## FAQ
- Is this an alternative to Electron?
diff --git a/Taskfile.yaml b/Taskfile.yaml
new file mode 100644
index 000000000..c7246260d
--- /dev/null
+++ b/Taskfile.yaml
@@ -0,0 +1,24 @@
+# https://taskfile.dev
+
+version: '3'
+
+vars:
+ GREETING: Hello, World!
+
+tasks:
+ check-contributors:
+ cmds:
+ - npx -y all-contributors-cli check
+
+ update-contributors:
+ cmds:
+ - go run v3/tasks/contribs/main.go
+
+ build-contributors:
+ cmds:
+ - npx -y all-contributors-cli generate
+
+ release:
+ dir: v2/tools/release
+ cmds:
+ - go run release.go
\ No newline at end of file
diff --git a/v2/cmd/wails/internal/version.txt b/v2/cmd/wails/internal/version.txt
index d07897c40..fa49670c7 100644
--- a/v2/cmd/wails/internal/version.txt
+++ b/v2/cmd/wails/internal/version.txt
@@ -1 +1 @@
-v2.3.1
\ No newline at end of file
+v2.4.0
\ No newline at end of file
diff --git a/v2/tools/release/release.go b/v2/tools/release/release.go
index 4c20c8fdc..558299558 100644
--- a/v2/tools/release/release.go
+++ b/v2/tools/release/release.go
@@ -54,13 +54,13 @@ func main() {
}
s.CD("../../../website")
- runCommand("pnpm", "install")
+ runCommand("npx", "-y", "pnpm", "install")
s.ECHO("Generating new Docs for version: " + newVersion)
- runCommand("pnpm", "run", "docusaurus", "docs:version", newVersion)
+ runCommand("npx", "pnpm", "run", "docusaurus", "docs:version", newVersion)
- runCommand("pnpm", "run", "write-translations")
+ runCommand("npx", "pnpm", "run", "write-translations")
// Load the version list/*
versionsData, err := os.ReadFile("versions.json")
@@ -83,5 +83,5 @@ func main() {
s.RM("version-" + oldestVersion + "-sidebars.json")
s.CD("..")
- runCommand("pnpm", "run", "build")
+ runCommand("npx", "pnpm", "run", "build")
}
diff --git a/website/i18n/en/docusaurus-plugin-content-docs/version-v2.0.0-rc.1.json b/website/i18n/en/docusaurus-plugin-content-docs/version-v2.0.0-rc.1.json
deleted file mode 100644
index 49cf4687e..000000000
--- a/website/i18n/en/docusaurus-plugin-content-docs/version-v2.0.0-rc.1.json
+++ /dev/null
@@ -1,38 +0,0 @@
-{
- "version.label": {
- "message": "v2.0.0-rc.1",
- "description": "The label for version v2.0.0-rc.1"
- },
- "sidebar.docs.category.Getting Started": {
- "message": "Getting Started",
- "description": "The label for category Getting Started in sidebar docs"
- },
- "sidebar.docs.category.Reference": {
- "message": "Reference",
- "description": "The label for category Reference in sidebar docs"
- },
- "sidebar.docs.category.Runtime": {
- "message": "Runtime",
- "description": "The label for category Runtime in sidebar docs"
- },
- "sidebar.docs.category.Community": {
- "message": "Community",
- "description": "The label for category Community in sidebar docs"
- },
- "sidebar.docs.category.Showcase": {
- "message": "Showcase",
- "description": "The label for category Showcase in sidebar docs"
- },
- "sidebar.docs.category.Guides": {
- "message": "Guides",
- "description": "The label for category Guides in sidebar docs"
- },
- "sidebar.docs.category.Tutorials": {
- "message": "Tutorials",
- "description": "The label for category Tutorials in sidebar docs"
- },
- "sidebar.docs.link.Contributing": {
- "message": "Contributing",
- "description": "The label for link Contributing in sidebar docs, linking to /community-guide#ways-of-contributing"
- }
-}
diff --git a/website/i18n/en/docusaurus-plugin-content-docs/version-v2.0.0.json b/website/i18n/en/docusaurus-plugin-content-docs/version-v2.0.0.json
deleted file mode 100644
index 421c838e6..000000000
--- a/website/i18n/en/docusaurus-plugin-content-docs/version-v2.0.0.json
+++ /dev/null
@@ -1,38 +0,0 @@
-{
- "version.label": {
- "message": "v2.0.0",
- "description": "The label for version v2.0.0"
- },
- "sidebar.docs.category.Getting Started": {
- "message": "Getting Started",
- "description": "The label for category Getting Started in sidebar docs"
- },
- "sidebar.docs.category.Reference": {
- "message": "Reference",
- "description": "The label for category Reference in sidebar docs"
- },
- "sidebar.docs.category.Runtime": {
- "message": "Runtime",
- "description": "The label for category Runtime in sidebar docs"
- },
- "sidebar.docs.category.Community": {
- "message": "Community",
- "description": "The label for category Community in sidebar docs"
- },
- "sidebar.docs.category.Showcase": {
- "message": "Showcase",
- "description": "The label for category Showcase in sidebar docs"
- },
- "sidebar.docs.category.Guides": {
- "message": "Guides",
- "description": "The label for category Guides in sidebar docs"
- },
- "sidebar.docs.category.Tutorials": {
- "message": "Tutorials",
- "description": "The label for category Tutorials in sidebar docs"
- },
- "sidebar.docs.link.Contributing": {
- "message": "Contributing",
- "description": "The label for link Contributing in sidebar docs, linking to /community-guide#ways-of-contributing"
- }
-}
diff --git a/website/i18n/en/docusaurus-plugin-content-docs/version-v2.1.0.json b/website/i18n/en/docusaurus-plugin-content-docs/version-v2.1.0.json
deleted file mode 100644
index f29e6b248..000000000
--- a/website/i18n/en/docusaurus-plugin-content-docs/version-v2.1.0.json
+++ /dev/null
@@ -1,38 +0,0 @@
-{
- "version.label": {
- "message": "v2.1.0",
- "description": "The label for version v2.1.0"
- },
- "sidebar.docs.category.Getting Started": {
- "message": "Getting Started",
- "description": "The label for category Getting Started in sidebar docs"
- },
- "sidebar.docs.category.Reference": {
- "message": "Reference",
- "description": "The label for category Reference in sidebar docs"
- },
- "sidebar.docs.category.Runtime": {
- "message": "Runtime",
- "description": "The label for category Runtime in sidebar docs"
- },
- "sidebar.docs.category.Community": {
- "message": "Community",
- "description": "The label for category Community in sidebar docs"
- },
- "sidebar.docs.category.Showcase": {
- "message": "Showcase",
- "description": "The label for category Showcase in sidebar docs"
- },
- "sidebar.docs.category.Guides": {
- "message": "Guides",
- "description": "The label for category Guides in sidebar docs"
- },
- "sidebar.docs.category.Tutorials": {
- "message": "Tutorials",
- "description": "The label for category Tutorials in sidebar docs"
- },
- "sidebar.docs.link.Contributing": {
- "message": "Contributing",
- "description": "The label for link Contributing in sidebar docs, linking to /community-guide#ways-of-contributing"
- }
-}
diff --git a/website/i18n/en/docusaurus-plugin-content-docs/version-v2.2.0.json b/website/i18n/en/docusaurus-plugin-content-docs/version-v2.2.0.json
deleted file mode 100644
index 1074035c4..000000000
--- a/website/i18n/en/docusaurus-plugin-content-docs/version-v2.2.0.json
+++ /dev/null
@@ -1,38 +0,0 @@
-{
- "version.label": {
- "message": "v2.2.0",
- "description": "The label for version v2.2.0"
- },
- "sidebar.docs.category.Getting Started": {
- "message": "Getting Started",
- "description": "The label for category Getting Started in sidebar docs"
- },
- "sidebar.docs.category.Reference": {
- "message": "Reference",
- "description": "The label for category Reference in sidebar docs"
- },
- "sidebar.docs.category.Runtime": {
- "message": "Runtime",
- "description": "The label for category Runtime in sidebar docs"
- },
- "sidebar.docs.category.Community": {
- "message": "Community",
- "description": "The label for category Community in sidebar docs"
- },
- "sidebar.docs.category.Showcase": {
- "message": "Showcase",
- "description": "The label for category Showcase in sidebar docs"
- },
- "sidebar.docs.category.Guides": {
- "message": "Guides",
- "description": "The label for category Guides in sidebar docs"
- },
- "sidebar.docs.category.Tutorials": {
- "message": "Tutorials",
- "description": "The label for category Tutorials in sidebar docs"
- },
- "sidebar.docs.link.Contributing": {
- "message": "Contributing",
- "description": "The label for link Contributing in sidebar docs, linking to /community-guide#ways-of-contributing"
- }
-}
diff --git a/website/i18n/en/docusaurus-plugin-content-docs/version-v2.3.0.json b/website/i18n/en/docusaurus-plugin-content-docs/version-v2.4.0.json
similarity index 94%
rename from website/i18n/en/docusaurus-plugin-content-docs/version-v2.3.0.json
rename to website/i18n/en/docusaurus-plugin-content-docs/version-v2.4.0.json
index 32ec6fb1d..4bda777e9 100644
--- a/website/i18n/en/docusaurus-plugin-content-docs/version-v2.3.0.json
+++ b/website/i18n/en/docusaurus-plugin-content-docs/version-v2.4.0.json
@@ -1,7 +1,7 @@
{
"version.label": {
- "message": "v2.3.0",
- "description": "The label for version v2.3.0"
+ "message": "v2.4.0",
+ "description": "The label for version v2.4.0"
},
"sidebar.docs.category.Getting Started": {
"message": "Getting Started",
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/community/links.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/community/links.mdx
similarity index 85%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/community/links.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/community/links.mdx
index df7ba5dd4..0cd36271a 100644
--- a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/community/links.mdx
+++ b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/community/links.mdx
@@ -12,8 +12,7 @@ La [liste définitive](https://github.com/wailsapp/awesome-wails) de liens relat
## Canaux de support
-- [Gophers Slack Channel](https://gophers.slack.com/messages/CJ4P9F7MZ/)
-- [Gophers Slack Channel Invite](https://invite.slack.golangbridge.org/)
+- [Wails Discord Server](https://discord.gg/JDdSxwjhGf)
- [Github Issues](https://github.com/wailsapp/wails/issues)
- [canal de discussion sur la bêta v2](https://github.com/wailsapp/wails/discussions/828)
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/emailit.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/emailit.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/emailit.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/emailit.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/encrypteasy.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/encrypteasy.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/encrypteasy.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/encrypteasy.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/filehound.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/filehound.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/filehound.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/filehound.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/minecraftupdater.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/minecraftupdater.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/minecraftupdater.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/minecraftupdater.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/modalfilemanager.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/modalfilemanager.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/modalfilemanager.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/modalfilemanager.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/mollywallet.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/mollywallet.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/mollywallet.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/mollywallet.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/october.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/october.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/october.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/october.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/optimus.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/optimus.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/optimus.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/optimus.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/portfall.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/portfall.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/portfall.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/portfall.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/restic-browser.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/restic-browser.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/restic-browser.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/restic-browser.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/riftshare.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/riftshare.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/riftshare.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/riftshare.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/scriptbar.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/scriptbar.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/scriptbar.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/scriptbar.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/surge.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/surge.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/surge.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/surge.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/wally.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/wally.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/wally.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/wally.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/wombat.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/wombat.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/wombat.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/wombat.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/ytd.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/ytd.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/ytd.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/ytd.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/community/templates.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/community/templates.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/community/templates.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/community/templates.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/building.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/gettingstarted/building.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/building.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/gettingstarted/building.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/development.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/gettingstarted/development.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/development.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/gettingstarted/development.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/firstproject.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/gettingstarted/firstproject.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/firstproject.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/gettingstarted/firstproject.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/installation.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/gettingstarted/installation.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/installation.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/gettingstarted/installation.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/angular.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/angular.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/angular.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/angular.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/application-development.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/application-development.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/application-development.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/application-development.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/dynamic-assets.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/dynamic-assets.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/dynamic-assets.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/dynamic-assets.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/frameless.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/frameless.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/frameless.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/frameless.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/frontend.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/frontend.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/frontend.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/frontend.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/ides.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/ides.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/ides.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/ides.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/linux-distro-support.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/linux-distro-support.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/linux-distro-support.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/linux-distro-support.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/linux.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/linux.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/linux.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/linux.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/local-development.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/local-development.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/local-development.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/local-development.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/mac-appstore.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/mac-appstore.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/mac-appstore.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/mac-appstore.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/manual-builds.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/manual-builds.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/manual-builds.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/manual-builds.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/migrating.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/migrating.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/migrating.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/migrating.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/mouse-buttons.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/mouse-buttons.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/mouse-buttons.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/mouse-buttons.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/obfuscated.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/obfuscated.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/obfuscated.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/obfuscated.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/overscroll.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/overscroll.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/overscroll.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/overscroll.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/routing.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/routing.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/routing.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/routing.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/signing.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/signing.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/signing.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/signing.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/templates.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/templates.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/templates.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/templates.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/troubleshooting.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/troubleshooting.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/troubleshooting.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/troubleshooting.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/vscode.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/vscode.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/vscode.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/vscode.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/windows-installer.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/windows-installer.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/windows-installer.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/windows-installer.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/windows.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/windows.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/guides/windows.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/guides/windows.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/howdoesitwork.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/howdoesitwork.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/howdoesitwork.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/howdoesitwork.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/introduction.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/introduction.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/introduction.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/introduction.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/reference/cli.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/reference/cli.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/reference/cli.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/reference/cli.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/reference/menus.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/reference/menus.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/reference/menus.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/reference/menus.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/reference/options.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/reference/options.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/reference/options.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/reference/options.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/reference/project-config.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/reference/project-config.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/reference/project-config.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/reference/project-config.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/browser.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/browser.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/browser.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/browser.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/dialog.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/dialog.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/dialog.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/dialog.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/events.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/events.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/events.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/events.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/intro.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/intro.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/intro.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/intro.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/log.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/log.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/log.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/log.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/menu.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/menu.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/menu.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/menu.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/window.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/window.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/window.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/window.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/tutorials/dogsapi.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/tutorials/dogsapi.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/tutorials/dogsapi.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/tutorials/dogsapi.mdx
diff --git a/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/tutorials/helloworld.mdx b/website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/tutorials/helloworld.mdx
similarity index 100%
rename from website/i18n/fr/docusaurus-plugin-content-docs/version-v2.3.0/tutorials/helloworld.mdx
rename to website/i18n/fr/docusaurus-plugin-content-docs/version-v2.4.0/tutorials/helloworld.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/links.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/links.mdx
deleted file mode 100644
index 49cb7843b..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/links.mdx
+++ /dev/null
@@ -1,22 +0,0 @@
----
-sidebar_position: 2
----
-
-# Links
-
-This page serves as a list for community related links. Please submit a PR (click `Edit this page` at the bottom) to submit links.
-
-## Awesome Wails
-
-The [definitive list](https://github.com/wailsapp/awesome-wails) of links related to Wails.
-
-## Support Channels
-
-- [Discord](https://discord.com/invite/JDdSxwjhGf)
-- [Github Issues](https://github.com/wailsapp/wails/issues)
-- [v2 Beta Discussion Board](https://github.com/wailsapp/wails/discussions/828)
-
-## Social Media
-
-- [Twitter](https://twitter.com/wailsapp)
-- [Wails Chinese Community QQ Group](https://qm.qq.com/cgi-bin/qm/qr?k=PmIURne5hFGNd7QWzW5qd6FV-INEjNJv&jump_from=webapi) - Group number: 1067173054
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/emailit.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/emailit.mdx
deleted file mode 100644
index 4a1ebe835..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/emailit.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
-# EmailIt
-
-
-
-
-
-
-[EmailIt](https://github.com/raguay/EmailIt/) is a Wails 2 program that is a markdown based email sender only with nine notepads, scripts to manipulate the text, and templates. It also has a builtin [Node-Red](https://nodered.org/) server, scripts terminal, and the [ScriptBar](https://github.com/raguay/ScriptBarApp) program for displaying results from Node-Red or a script on your system. Documentation is very scarce, but the programs works. It’s built using Wails2 and Svelte, and the download is a universal macOS application.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/encrypteasy.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/encrypteasy.mdx
deleted file mode 100644
index 13c2d8345..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/encrypteasy.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# EncryptEasy
-
-
-
-
-
-
-**[EncryptEasy](https://www.encrypteasy.app) is a simple and easy to use PGP encryption tool, managing all your and your contacts keys. Encryption should be simple. Developed with Wails.**
-
-Encrypting messages using PGP is the industry standard. Everyone has a private and a public key. Your private key, well, needs to be kept private so only you can read messages. Your public key is distributed to anyone who wants to send you secret, encrypted messages. Managing keys, encrypting messages and decrypting messages should be a smooth experience. EncryptEasy is all about making it easy.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/filehound.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/filehound.mdx
deleted file mode 100644
index 78cbfca86..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/filehound.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
-# FileHound Export Utility
-
-
-
-
-
-
-[FileHound Export Utility](https://www.filehound.co.uk/) FileHound is a cloud document management platform made for secure file retention, business process automation and SmartCapture capabilities.
-
-The FileHound Export Utility allows FileHound Administrators the ability to run a secure document and data extraction tasks for alternative back-up and recovery purposes. This application will download all documents and/or meta data saved in FileHound based on the filters you choose. The metadata will be exported in both JSON and XML formats.
-
-Backend built with: Go 1.15 Wails 1.11.0 go-sqlite3 1.14.6 go-linq 3.2
-
-Frontend with: Vue 2.6.11 Vuex 3.4.0 Typescript Tailwind 1.9.6
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/minecraftupdater.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/minecraftupdater.mdx
deleted file mode 100644
index 11247339d..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/minecraftupdater.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Minecraft Updater
-
-
-
-
-
-
-[Minecraft Updater](https://github.com/Gurkengewuerz/MinecraftModUpdater) is a utility tool to update and synchronize Minecraft mods for your userbase. It’s built using Wails2 and React with [antd](https://ant.design/) as frontend framework.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/modalfilemanager.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/modalfilemanager.mdx
deleted file mode 100644
index a7ae8c492..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/modalfilemanager.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
-# Modal File Manager
-
-
-
-
-
-
-[Modal File Manager](https://github.com/raguay/ModalFileManager) is a dual pane file manager using web technologies. My original design was based on NW.js and can be found [here](https://github.com/raguay/ModalFileManager-NWjs). This version uses the same Svelte based frontend code (but it has be greatly modified since the departure from NW.js), but the backend is a [Wails 2](https://wails.io/) implementation. By using this implementation, I no longer use command line `rm`, `cp`, etc. commands. It is fully coded using Go and runs much faster than the previous versions.
-
-This file manager is designed around the same principle as Vim: a state controlled keyboard actions. The number of states isn't fixed, but very programmable. Therefore, an infinite number of keyboard configurations can be created and used. This is the main difference from other file managers.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/mollywallet.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/mollywallet.mdx
deleted file mode 100644
index 534b097ca..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/mollywallet.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
-# Molley Wallet
-
-
-
-
-
-
-[Molly Wallet](https://github.com/grvlle/constellation_wallet/) the official $DAG wallet of the Constellation Network. It'll let users interact with the Hypergraph Network in various ways, not limited to producing $DAG transactions.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/october.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/october.mdx
deleted file mode 100644
index 889d2dd9e..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/october.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
-# October
-
-
-
-
-
-
-[October](https://october.utf9k.net) is a small Wails application that makes it really easy to extract highlights from [Kobo eReaders](https://en.wikipedia.org/wiki/Kobo_eReader) and then forward them to [Readwise](https://readwise.io).
-
-It has a relatively small scope with all platform versions weighing in under 10MB, and that's without enabling [UPX compression](https://upx.github.io/)!
-
-In contrast, the author's previous attempts with Electron quickly bloated to several hundred megabytes.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/optimus.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/optimus.mdx
deleted file mode 100644
index c3eb79507..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/optimus.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
-# Optimus
-
-
-
-
-
-
-[Optimus](https://github.com/splode/optimus) is a desktop image optimization application. It supports conversion and compression between WebP, JPEG, and PNG image formats.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/portfall.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/portfall.mdx
deleted file mode 100644
index 4cc2c63c9..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/portfall.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
-# Portfall
-
-
-
-
-
-
-[Portfall](https://github.com/rekon-oss/portfall) - A desktop k8s port-forwarding portal for easy access to all your cluster UIs
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/restic-browser.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/restic-browser.mdx
deleted file mode 100644
index 1505ce07a..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/restic-browser.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Restic Browser
-
-
-
-
-
-
-[Restic-Browser](https://github.com/emuell/restic-browser) - A simple, cross-platform [restic](https://github.com/restic/restic) backup GUI for browsing and restoring restic repositories.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/riftshare.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/riftshare.mdx
deleted file mode 100644
index 5223e88cf..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/riftshare.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
-# RiftShare
-
-
-
-
-
-
-Easy, Secure, and Free file sharing for everyone. Learn more at [Riftshare.app](https://riftshare.app)
-
-## Features
-
-- Easy secure file sharing between computers both in the local network and through the internet
-- Supports sending files or directories securely through the [magic wormhole protocol](https://magic-wormhole.readthedocs.io/en/latest/)
-- Compatible with all other apps using magic wormhole (magic-wormhole or wormhole-william CLI, wormhole-gui, etc.)
-- Automatic zipping of multiple selected files to send at once
-- Full animations, progress bar, and cancellation support for sending and receiving
-- Native OS File Selection
-- Open files in one click once received
-- Auto Update - don't worry about having the latest release!
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/scriptbar.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/scriptbar.mdx
deleted file mode 100644
index aaa556f92..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/scriptbar.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
-# ScriptBar
-
-
-
-
-
-
-[ScriptBar](https://GitHub.com/raguay/ScriptBarApp) is a program to show the output of the embedded [Node-Red](https://nodered.org) server in the [EmailIt](https://GitHub.com/raguay/EmailIt) application. It also displays the output of scripts on your system. ScriptBar doesn't put them in the menubar, but has them all in a convient window for easy viewing. You can have multiple tabs to have many different things show. You can also keep the links to your most visited web sites.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/surge.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/surge.mdx
deleted file mode 100644
index 2d895dc29..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/surge.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
-# Surge
-
-
-
-
-
-
-[Surge](https://getsurge.io/) is a p2p filesharing app designed to utilize blockchain technologies to enable 100% anonymous file transfers. Surge is end-to-end encrypted, decentralized and open source.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/wally.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/wally.mdx
deleted file mode 100644
index 2a2498f40..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/wally.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
-# Wally
-
-
-
-
-
-
-[Wally](https://ergodox-ez.com/pages/wally) is the official firmware flasher for [Ergodox](https://ergodox-ez.com/) keyboards. It looks great and is a fantastic example of what you can achieve with Wails: the ability to combine the power of Go and the rich graphical tools of the web development world.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/wombat.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/wombat.mdx
deleted file mode 100644
index 54cedacea..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/wombat.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
-# Wombat
-
-
-
-
-
-
-[Wombat](https://github.com/rogchap/wombat) is a cross platform gRPC client.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/ytd.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/ytd.mdx
deleted file mode 100644
index 178ff0529..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/ytd.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
-# Ytd
-
-
-
-
-
-
-[Ytd](https://github.com/marcio199226/ytd/tree/v2-wails) is an app for downloading tracks from youtube, creating offline playlists and share them with your friends, your friends will be able to playback your playlists or download them for offline listening, has an built-in player.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/templates.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/templates.mdx
deleted file mode 100644
index d9a29a6fa..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/templates.mdx
+++ /dev/null
@@ -1,52 +0,0 @@
----
-sidebar_position: 1
----
-
-# Templates
-
-This page serves as a list for community supported templates. Please submit a PR (click `Edit this page` at the bottom) to include your templates. To build your own template, please see the [Templates](../guides/templates.mdx) guide.
-
-To use these templates, run `wails init -n "Your Project Name" -t [the link below[@version]]`
-
-If there is no version suffix, the main branch code template is used by default. If there is a version suffix, the code template corresponding to the tag of this version is used.
-
-Example: `wails init -n "Your Project Name" -t https://github.com/misitebao/wails-template-vue`
-
-:::warning Attention
-
-**The Wails project does not maintain, is not responsible nor liable for 3rd party templates!**
-
-If you are unsure about a template, inspect `package.json` and `wails.json` for what scripts are run and what packages are installed.
-
-:::
-
-## Vue
-
-- [wails-template-vue](https://github.com/misitebao/wails-template-vue) - A template using Vite,Vue and Vue-Router(Support both JavaScript and TypeScript)
-- [wails-vite-vue-ts](https://github.com/codydbentley/wails-vite-vue-ts) - Vue 3 TypeScript with Vite (and instructions to add features)
-- [wails-vite-vue-the-works](https://github.com/codydbentley/wails-vite-vue-the-works) - Vue 3 TypeScript with Vite, Vuex, Vue Router, Sass, and ESLint + Prettier
-
-## Angular
-
-- [wails-angular-template](https://github.com/TAINCER/wails-angular-template) - Angular with TypeScript, Sass, Hot-Reload, Code-Splitting and i18n
-
-## React
-
-- [wails-react-template](https://github.com/AlienRecall/wails-react-template) - A template using reactjs
-- [wails-react-template](https://github.com/flin7/wails-react-template) - A minimal template for React that supports live development
-- [wails-template-nextjs](https://github.com/LGiki/wails-template-nextjs) - A template using Next.js and TypeScript
-
-## Svelte
-
-- [wails-svelte-template](https://github.com/raitonoberu/wails-svelte-template) - A template using Svelte
-- [wails-vite-svelte-template](https://github.com/BillBuilt/wails-vite-svelte-template) - A template using Svelte and Vite
-- [wails-vite-svelte-tailwind-template](https://github.com/BillBuilt/wails-vite-svelte-tailwind-template) - A template using Svelte and Vite with TailwindCSS v3
-- [wails-sveltekit-template](https://github.com/h8gi/wails-sveltekit-template) - A template using SvelteKit
-
-## Elm
-
-- [wails-elm-template](https://github.com/benjamin-thomas/wails-elm-template) - Develop your GUI app with functional programming and a **snappy** hot-reload setup :tada: :rocket:
-
-## Pure JavaScript (Vanilla)
-
-- [wails-pure-js-template](https://github.com/KiddoV/wails-pure-js-template) - A template with nothing but just basic JavaScript, HTML, and CSS
\ No newline at end of file
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/building.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/building.mdx
deleted file mode 100644
index 3e0df3b68..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/building.mdx
+++ /dev/null
@@ -1,21 +0,0 @@
----
-sidebar_position: 6
----
-
-# Compiling your Project
-
-From the project directory, run `wails build`. This will compile your project and save the production-ready binary in the `build/bin` directory.
-
-If you run the binary, you should see the default application:
-
-
-
-
-
-
-
-For more details on compilation options, please refer to the [CLI Reference](../reference/cli.mdx#build).
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/development.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/development.mdx
deleted file mode 100644
index 54dda5faa..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/development.mdx
+++ /dev/null
@@ -1,16 +0,0 @@
----
-sidebar_position: 5
----
-
-# Developing your Application
-
-You can run your application in development mode by running `wails dev` from your project directory. This will do the following things:
-
-- Build your application and run it
-- Bind your Go code to the frontend so it can be called from Javascript
-- Using the power of [vite](https://vitejs.dev/), will watch for modifications in your Go files and rebuild/re-run on change
-- Sets up a [webserver](http://localhost:34115) that will serve your application over a browser. This allows you to use your favourite browser extensions. You can even call your Go code from the console
-
-To get started, run `wails dev` in the project directory. More information on this can be found [here](../reference/cli.mdx#dev).
-
-Coming soon: Tutorial
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/firstproject.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/firstproject.mdx
deleted file mode 100644
index 86036d24b..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/firstproject.mdx
+++ /dev/null
@@ -1,130 +0,0 @@
----
-sidebar_position: 2
----
-
-# Creating a Project
-
-## Project Generation
-
-Now that the CLI is installed, you can generate a new project by using the `wails init` command.
-
-Pick your favourite framework:
-
-
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-
-
-
- Generate a Svelte project using Javascript with:
-
- wails init -n myproject -t svelte
-If you would rather use Typescript:
-
- wails init -n myproject -t svelte-ts
-
-
-
- Generate a React project using Javascript with:
-
- wails init -n myproject -t react
-If you would rather use Typescript:
-
- wails init -n myproject -t react-ts
-
-
-
- Vue用のJavascriptプロジェクトを生成する場合:
-
- wails init -n myproject -t vanilla
-
-Typescriptプロジェクトを生成する場合:
-
- wails init -n myproject -t vanilla-ts
-
-
-
-
-
-
-
-
-There are also [community templates](../community/templates.mdx) available that offer different capabilities and frameworks.
-
-To see the other options available, you can run `wails init -help`. More details can be found in the [CLI Reference](../reference/cli.mdx#init).
-
-## Project Layout
-
-Wails projects have the following layout:
-
-```
-.
-├── build/
-│ ├── appicon.png
-│ ├── darwin/
-│ └── windows/
-├── frontend/
-├── go.mod
-├── go.sum
-├── main.go
-└── wails.json
-```
-
-### Project structure rundown
-
-- `/main.go` - The main application
-- `/frontend/` - Frontend project files
-- `/build/` - Project build directory
-- `/build/appicon.png` - The application icon
-- `/build/darwin/` - Mac specific project files
-- `/build/windows/` - Windows specific project files
-- `/wails.json` - The project configuration
-- `/go.mod` - Go module file
-- `/go.sum` - Go module checksum file
-
-The `frontend` directory has nothing specific to Wails and can be any frontend project of your choosing.
-
-The `build` directory is used during the build process. These files may be updated to customise your builds. If files are removed from the build directory, default versions will be regenerated.
-
-The default module name in `go.mod` is "changeme". You should change this to something more appropriate.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/installation.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/installation.mdx
deleted file mode 100644
index bfadb7275..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/installation.mdx
+++ /dev/null
@@ -1,90 +0,0 @@
----
-sidebar_position: 1
----
-
-# Installation
-
-## Supported Platforms
-
-- Windows 10/11 AMD64/ARM64
-- MacOS 10.13+ AMD64
-- MacOS 11.0+ ARM64
-- Linux AMD64/ARM64
-
-## Dependencies
-
-Wails has a number of common dependencies that are required before installation:
-
-- Go 1.17+
-- NPM (Node 15+)
-
-### Go
-
-Download Go from the [Go Downloads Page](https://go.dev/doc/install).
-
-Ensure that you follow the official [Go installation instructions](https://go.dev/doc/install). You will also need to ensure that your `PATH` environment variable also includes the path to your `~/go/bin` directory. Restart your terminal and do the following checks:
-
-- Check Go is installed correctly: `go version`
-- Check "~/go/bin" is in your PATH variable: `echo $PATH | grep go/bin`
-
-### NPM
-
-Download NPM from the [Node Downloads Page](https://nodejs.org/en/download/). It is best to use the latest release as that is what we generally test against.
-
-Run `npm --version` to verify.
-
-## Platform Specific Dependencies
-
-You will also need to install platform specific dependencies:
-
-
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-
-
-
- Wailsを使用するには、xcodeコマンドラインツールがインストールされている必要があります。 This can be done by running:
- xcode-select --install
-
-
- Wails requires that the WebView2{" "}
- runtime is installed. Some Windows installations will already have this installed. You can check using
- the{" "}
- wails doctor command (see below).
-
-
- Linux required the standard gcc build tools
- plus libgtk3 and libwebkit. Rather than list a ton of commands for different distros, Wails can try to determine
- what the installation commands are for your specific distribution. Run wails doctor after
- installation
- to be shown how to install the dependencies. If your distro/package manager is not supported, please consult the {" "}
- Add Linux Distro guide.
-
-
-
-
-
-## Optional Dependencies
-
-- [UPX](https://upx.github.io/) for compressing your applications.
-
-## Installing Wails
-
-Run `go install github.com/wailsapp/wails/v2/cmd/wails@latest` to install the Wails CLI.
-
-## System Check
-
-Running `wails doctor` will check if you have the correct dependencies installed. If not, it will advise on what is missing and help on how to rectify any problems.
-
-## The `wails` command appears to be missing?
-
-If your system is reporting that the `wails` command is missing, make sure you have followed the Go installation guide correctly. Normally, it means that the `go/bin` directory in your User's home directory is not in the `PATH` environment variable. You will also normally need to close and reopen any open command prompts so that changes to the environment made by the installer are reflected at the command prompt.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/application-development.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/application-development.mdx
deleted file mode 100644
index a618076f1..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/application-development.mdx
+++ /dev/null
@@ -1,194 +0,0 @@
-# Application Development
-
-There are no hard and fast rules for developing applications with Wails, but there are some basic guidelines.
-
-## Application Setup
-
-The pattern used by the default templates are that `main.go` is used for configuring and running the application, whilst `app.go` is used for defining the application logic.
-
-The `app.go` file will define a struct that has 2 methods which act as hooks into the main application:
-
-```go title="app.go"
-type App struct {
- ctx context.Context
-}
-
-func NewApp() *App {
- return &App{}
-}
-
-func (a *App) startup(ctx context.Context) {
- a.ctx = ctx
-}
-
-func (a *App) shutdown(ctx context.Context) {
-}
-```
-
-- The startup method is called as soon as Wails allocates the resources it needs and is a good place for creating resources, setting up event listeners and anything else the application needs at startup. It is given a `context.Context` which is usually saved in a struct field. This context is needed for calling the [runtime](../reference/runtime/intro.mdx). If this method returns an error, the application will terminate. In dev mode, the error will be output to the console.
-
-- The shutdown method will be called by Wails right at the end of the shutdown process. This is a good place to deallocate memory and perform any shutdown tasks.
-
-The `main.go` file generally consists of a single call to `wails.Run()`, which accepts the application configuration. The pattern used by the templates is that before the call to `wails.Run()`, an instance of the struct we defined in `app.go` is created and saved in a variable called `app`. This configuration is where we add our callbacks:
-
-```go {3,9,10} title="main.go"
-func main() {
-
- app := NewApp()
-
- err := wails.Run(&options.App{
- Title: "My App",
- Width: 800,
- Height: 600,
- OnStartup: app.startup,
- OnShutdown: app.shutdown,
- })
- if err != nil {
- log.Fatal(err)
- }
-}
-
-```
-
-More information on application lifecycle hooks can be found [here](../howdoesitwork.mdx#application-lifecycle-callbacks).
-
-## Binding Methods
-
-It is likely that you will want to call Go methods from the frontend. This is normally done by adding public methods to the already defined struct in `app.go`:
-
-```go {16-18} title="app.go"
-type App struct {
- ctx context.Context
-}
-
-func NewApp() *App {
- return &App{}
-}
-
-func (a *App) startup(ctx context.Context) {
- a.ctx = ctx
-}
-
-func (a *App) shutdown(ctx context.Context) {
-}
-
-func (a *App) Greet(name string) string {
- return fmt.Sprintf("Hello %s!", name)
-}
-```
-
-In the main application configuration, the `Bind` key is where we can tell Wails what we want to bind:
-
-```go {11-13} title="main.go"
-func main() {
-
- app := NewApp()
-
- err := wails.Run(&options.App{
- Title: "My App",
- Width: 800,
- Height: 600,
- OnStartup: app.startup,
- OnShutdown: app.shutdown,
- Bind: []interface{}{
- app,
- },
- })
- if err != nil {
- log.Fatal(err)
- }
-}
-
-```
-
-This will bind all public methods in our `App` struct (it will never bind the startup and shutdown methods).
-
-### Dealing with context when binding multiple structs
-
-If you want to bind methods for multiple structs but want each struct to keep a reference to the context so that you can use the runtime functions, a good pattern is to pass the context from the `OnStartup` method to your struct instances :
-
-```go
-func main() {
-
- app := NewApp()
- otherStruct := NewOtherStruct()
-
- err := wails.Run(&options.App{
- Title: "My App",
- Width: 800,
- Height: 600,
- OnStartup: func(ctx context.Context){
- app.SetContext(ctx)
- otherStruct.SetContext(ctx)
- },
- OnShutdown: app.shutdown,
- Bind: []interface{}{
- app,
- otherStruct
- },
- })
- if err != nil {
- log.Fatal(err)
- }
-}
-```
-
-More information on Binding can be found [here](../howdoesitwork.mdx#method-binding).
-
-## Application Menu
-
-Wails supports adding a menu to your application. This is done by passing a [Menu](../reference/menus.mdx#menu) struct to application config. It's common to use a method that returns a Menu, and even more common for that to be a method on the `App` struct used for the lifecycle hooks.
-
-```go {11} title="main.go"
-func main() {
-
- app := NewApp()
-
- err := wails.Run(&options.App{
- Title: "My App",
- Width: 800,
- Height: 600,
- OnStartup: app.startup,
- OnShutdown: app.shutdown,
- Menu: app.menu(),
- Bind: []interface{}{
- app,
- },
- })
- if err != nil {
- log.Fatal(err)
- }
-}
-
-```
-
-## Assets
-
-The great thing about the way Wails v2 handles assets is that it doesn't! The only thing you need to give Wails is an `embed.FS`. How you get to that is entirely up to you. You can use vanilla html/css/js files like the vanilla template. You could have some complicated build system, it doesn't matter.
-
-When `wails build` is run, it will check the `wails.json` project file at the project root. There are 2 keys in the project file that are read:
-
-- "frontend:install"
-- "frontend:build"
-
-The first, if given, will be executed in the `frontend` directory to install the node modules. The second, if given, will be executed in the `frontend` directory to build the frontend project.
-
-If these 2 keys aren't given, then Wails does absolutely nothing with the frontend. It is only expecting that `embed.FS`.
-
-### AssetsHandler
-
-A Wails v2 app can optionally define a `http.Handler` in the `options.App`, which allows hooking into the AssetServer to create files on the fly or process POST/PUT requests. GET requests are always first handled by the `assets` FS. If the FS doesn't find the requested file the request will be forwarded to the `http.Handler` for serving. Any requests other than GET will be directly processed by the `AssetsHandler` if specified. It's also possible to only use the `AssetsHandler` by specifiy `nil` as the `Assets` option.
-
-## Built in Dev Server
-
-Running `wails dev` will start the built in dev server which will start a file watcher in your project directory. By default, if any file changes, wails checks if it was an application file (default: `.go`, configurable with `-e` flag). If it was, then it will rebuild your application and relaunch it. If the changed file was in the assets, it will issue a reload after a short amount of time.
-
-The dev server uses a technique called "debouncing" which means it doesn't reload straight away, as there may be multiple files changed in a short amount of time. When a trigger occurs, it waits for a set amount of time before issuing a reload. If another trigger happens, it resets to the wait time again. By default this value is `100ms`. If this value doesn't work for your project, it can be configured using the `-debounce` flag. If used, this value will be saved to your project config and become the default.
-
-## External Dev Server
-
-Some frameworks come with their own live-reloading server, however they will not be able to take advantage of the Wails Go bindings. In this scenario, it is best to run a watcher script that rebuilds the project into the build directory, which Wails will be watching. For an example, see the default svelte template that uses [rollup](https://rollupjs.org/guide/en/). For [create-react-app](https://create-react-app.dev/), it's possible to use [this script](https://gist.github.com/int128/e0cdec598c5b3db728ff35758abdbafd) to achieve a similar result.
-
-## Go Module
-
-The default Wails templates generate a `go.mod` file that contains the module name "changeme". You should change this to something more appropriate after project generation.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/bleeding-edge.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/bleeding-edge.mdx
deleted file mode 100644
index b81cc79dc..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/bleeding-edge.mdx
+++ /dev/null
@@ -1,55 +0,0 @@
-# Bleeding Edge
-
-## Overview
-
-Wails is in constant development and new releases are regularly "tagged". This usually happens when all the newer code on `master` has been tested and confirmed working. If you need a bugfix or feature that has not yet made it to a release, it's possible to use the latest "bleeding edge" version using the following steps:
-
-- `git clone https://github.com/wailsapp/wails`
-- `cd wails/v2/cmd/wails`
-- `go install`
-
-NOTE: The directory that you cloned the project into will now be called "clonedir".
-
-The Wails CLI will now be at the very latest version.
-
-### Updating your project
-
-To update projects to use the latest version of the Wails library, update the project's `go.mod` and ensure the following line is at the bottom of the file:
-
-`replace github.com/wailsapp/wails/v2 => `
-
-Example:
-
-On Windows: `replace github.com/wailsapp/wails/v2 => C:\Users\leaan\Documents\wails-v2-beta\wails\v2`
-
-On 'nix: `replace github.com/wailsapp/wails/v2 => /home/me/projects/wails/v2`
-
-To revert to a stable version, run:
-
-`go install github.com/wailsapp/wails/v2/cmd/wails@latest`
-
-## Testing a Branch
-
-If you want to test a branch, follow the instructions above, but ensure you switch the branch you want to test before installing:
-
-- `git clone https://github.com/wailsapp/wails`
-- `cd wails`
-- `git checkout -b branch-to-test --track origin/branch-to-test`
-- `cd v2/cmd/wails`
-- `go install`
-
-Make sure you [update your project](#updating-your-project) as described above.
-
-## Testing a PR
-
-If you want to test a PR, follow the instructions above, but ensure you fetch the PR and switch the branch before installing. Please replace `[IDofThePR]` with the ID of the PR shown on github.com:
-
-- `git clone https://github.com/wailsapp/wails`
-- `cd wails`
-- `git fetch -u origin pull/[IDofThePR]/head:test/pr-[IDofThePR]`
-- `git checkout test/pr-[IDofThePR]`
-- `git reset --hard HEAD`
-- `cd v2/cmd/wails`
-- `go install`
-
-Make sure you [update your project](#updating-your-project) as described above.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/dynamic-assets.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/dynamic-assets.mdx
deleted file mode 100644
index 77ad6d09e..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/dynamic-assets.mdx
+++ /dev/null
@@ -1,126 +0,0 @@
-# Dynamic Assets
-
-If you want to load or generate assets for your frontend dynamically, you can achieve that using the [AssetsHandler](../reference/options#assetshandler) option. The AssetsHandler is a generic `http.Handler` which will be called for any non GET request on the assets server and for GET requests which can not be served from the bundled assets because the file is not found.
-
-By installing a custom AssetsHandler, you can serve your own assets using a custom asset server.
-
-## Example
-
-In our example project, we will create a simple assets handler which will load files off disk:
-
-```go title=main.go {16-35,49}
-package main
-
-import (
- "embed"
- "fmt"
- "github.com/wailsapp/wails/v2"
- "github.com/wailsapp/wails/v2/pkg/options"
- "net/http"
- "os"
- "strings"
-)
-
-//go:embed frontend/dist
-var assets embed.FS
-
-type FileLoader struct {
- http.Handler
-}
-
-func NewFileLoader() *FileLoader {
- return &FileLoader{}
-}
-
-func (h *FileLoader) ServeHTTP(res http.ResponseWriter, req *http.Request) {
- var err error
- requestedFilename := strings.TrimPrefix(req.URL.Path, "/")
- println("Requesting file:", requestedFilename)
- fileData, err := os.ReadFile(requestedFilename)
- if err != nil {
- res.WriteHeader(http.StatusBadRequest)
- res.Write([]byte(fmt.Sprintf("Could not load file %s", requestedFilename)))
- }
-
- res.Write(fileData)
-}
-
-func main() {
- // Create an instance of the app structure
- app := NewApp()
-
- // Create application with options
- err := wails.Run(&options.App{
- Title: "helloworld",
- Width: 1024,
- Height: 768,
- Assets: assets,
- BackgroundColour: &options.RGBA{R: 27, G: 38, B: 54, A: 255},
- OnStartup: app.startup,
- AssetsHandler: NewFileLoader(),
- Bind: []interface{}{
- app,
- },
- })
-
- if err != nil {
- println("Error:", err)
- }
-}
-```
-
-When we run the application in dev mode using `wails dev`, we will see the following output:
-
-```
-DEB | [ExternalAssetHandler] Loading 'http://localhost:3001/favicon.ico'
-DEB | [ExternalAssetHandler] Loading 'http://localhost:3001/favicon.ico' failed, using AssetHandler
-Requesting file: favicon.ico
-```
-
-As you can see, the assets handler is called when the default assets server is unable to serve the `favicon.ico` file.
-
-If you right click the main application and select "inspect" to bring up the devtools, you can test this feature out by typing the following into the console:
-
-```
-let response = await fetch('does-not-exist.txt');
-```
-
-This will generate an error in the devtools. We can see that the error is what we expect, returned by our custom assets handler:
-
-
-
-
-
-However, if we request `go.mod`, we will see the following output:
-
-
-
-
-
-This technique can be used to load images directly into the page. If we updated our default vanilla template and replaced the logo image:
-
-```html
-
-```
-
-with:
-
-```html
-
-```
-
-Then we would see the following:
-
-
-
-
-
-:::warning
-Exposing your filesystem in this way is a security risk. It is recommended that you properly manage access
-to your filesystem.
-:::
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/frameless.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/frameless.mdx
deleted file mode 100644
index c7ca5f6c3..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/frameless.mdx
+++ /dev/null
@@ -1,84 +0,0 @@
-# Frameless Applications
-
-Wails supports application that have no frames. This can be achieved by using the [frameless](../reference/options.mdx#frameless) field in [Application Options](../reference/options.mdx#application-options).
-
-Wails offers a simple solution for dragging the window: Any HTML element that has the CSS style `--wails-draggable:drag` will act as a "drag handle". This property applies to all child elements. If you need to indicate that a nested element should not drag, then use the attribute '--wails-draggable:no-drag' on that element.
-
-
-```html
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-```
-
-For some projects, using a CSS variable may not be possible due to dynamic styling. In this case, you can use the `CSSDragProperty` and `CSSDragValue` application options to define a property and value that will be used to indicate draggable regions:
-
-```go title=main.go
-package main
-
-import (
- "embed"
-
- "github.com/wailsapp/wails/v2"
- "github.com/wailsapp/wails/v2/pkg/options"
-)
-
-//go:embed frontend/dist
-var assets embed.FS
-
-func main() {
- // Create an instance of the app structure
- app := NewApp()
-
- // Create application with options
- err := wails.Run(&options.App{
- Title: "alwaysontop",
- Width: 1024,
- Height: 768,
- Assets: assets,
- Frameless: true,
- CSSDragProperty: "widows",
- CSSDragValue: "1",
- Bind: []interface{}{
- app,
- },
- })
-
- if err != nil {
- println("Error:", err)
- }
-}
-```
-
-```html title=index.html
-
-
-
-
-
- alwaysontop
-
-
-
-
-
-
-
-```
-
-:::info Fullscreen
- If you allow your application to go fullscreen, this drag functionality will be disabled.
-:::
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/frontend.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/frontend.mdx
deleted file mode 100644
index 4b192c557..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/frontend.mdx
+++ /dev/null
@@ -1,75 +0,0 @@
-# Frontend
-
-## Script Injection
-
-When Wails serves your `index.html`, by default, it will inject 2 script entries into the `` tag to load `/wails/ipc.js` and `/wails/runtime.js`. These files install the bindings and runtime respectively.
-
-The code below shows where these are injected by default:
-
-```html
-
-
- injection example
-
-
-
-
-
-
-
-
Please enter your name below 👇
-
-
-
-
-
-
-
-
-
-```
-
-### Overriding Default Script Injection
-
-To provide more flexibility to developers, there is a meta tag that may be used to customise this behaviour:
-
-```html
-
-```
-
-The options are as follows:
-
-| Value | Description |
-| ------------------- | ------------------------------------------------ |
-| noautoinjectruntime | Disable the autoinjection of `/wails/runtime.js` |
-| noautoinjectipc | Disable the autoinjection of `/wails/ipc.js` |
-| noautoinject | Disable all autoinjection of scripts |
-
-Multiple options may be used provided they are comma seperated.
-
-This code is perfectly valid and operates the same as the autoinjection version:
-
-```html
-
-
-
- injection example
-
-
-
-
-
-
-
Please enter your name below 👇
-
-
-
-
-
-
-
-
-
-
-
-```
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/ides.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/ides.mdx
deleted file mode 100644
index a20ae4131..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/ides.mdx
+++ /dev/null
@@ -1,113 +0,0 @@
-# IDEs
-
-Wails aims to provide a great development experience. To that aim, we now support generating IDE specific configuration to provide smoother project setup.
-
-Currently, we support [Visual Studio Code](https://code.visualstudio.com/) but aim to support other IDEs such as Goland.
-
-## Visual Studio Code
-
-
-
-
-
-When generating a project using the `-ide vscode` flags, IDE files will be created alongside the other project files. These files are placed into the `.vscode` directory and provide the correct configuration for debugging your application.
-
-The 2 files generated are `tasks.json` and `launch.json`. Below are the files generated for the default vanilla project:
-
-```json title="tasks.json"
-{
- "version": "2.0.0",
- "tasks": [
- {
- "label": "build",
- "type": "shell",
- "options": {
- "cwd": "${workspaceFolder}"
- },
- "command": "go",
- "args": ["build", "-tags", "dev", "-gcflags", "all=-N -l", "-o", "build/bin/myproject.exe"]
- },
- ]
-}
-```
-
-```json title="launch.json"
-{
- "version": "0.2.0",
- "configurations": [
- {
- "name": "Wails: Debug myproject",
- "type": "go",
- "request": "launch",
- "mode": "exec",
- "program": "${workspaceFolder}/build/bin/myproject.exe",
- "preLaunchTask": "build",
- "cwd": "${workspaceFolder}",
- "env": {}
- },
- ]
-}
-```
-
-### Configuring the install and build steps
-
-The `tasks.json` file is simple for the default project as there is no `npm install` or `npm run build` step needed. For projects that have a frontend build step, such as the svelte template, we would need to edit `tasks.json` to add the install and build steps:
-
-```json title="tasks.json"
-{
- "version": "2.0.0",
- "tasks": [
- {
- "label": "npm install",
- "type": "npm",
- "script": "install",
- "options": {
- "cwd": "${workspaceFolder}/frontend"
- },
- "presentation": {
- "clear": true,
- "panel": "shared",
- "showReuseMessage": false
- },
- "problemMatcher": []
- },
- {
- "label": "npm run build",
- "type": "npm",
- "script": "build",
- "options": {
- "cwd": "${workspaceFolder}/frontend"
- },
- "presentation": {
- "clear": true,
- "panel": "shared",
- "showReuseMessage": false
- },
- "problemMatcher": []
- },
- {
- "label": "build",
- "type": "shell",
- "options": {
- "cwd": "${workspaceFolder}"
- },
- "command": "go",
- "args": ["build", "-tags", "dev", "-gcflags", "all=-N -l", "-o", "build/bin/vscode.exe"],
- "dependsOn":[
- "npm install",
- "npm run build"
- ]
-
- },
- ]
-}
-```
-
-:::info Future Enhancement
-
-In the future, we hope to generate a `tasks.json` that includes the install and build steps automatically.
-
-:::
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/linux-distro-support.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/linux-distro-support.mdx
deleted file mode 100644
index 28a224a26..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/linux-distro-support.mdx
+++ /dev/null
@@ -1,101 +0,0 @@
-# Linux Distro Support
-
-## Overview
-
-Wails offers Linux support but providing installation instructions for all available distributions is an impossible task. Instead, Wails tries to determine if the packages you need to develop applications are available via your system's package manager. Currently, we support the following package managers:
-
-- apt
-- dnf
-- emerge
-- eopkg
-- nixpkgs
-- pacman
-- zypper
-
-## Adding package names
-
-There may be circumstances where your distro uses one of the supported package managers but the package name is different. For example, you may use an Ubuntu derivative, but the package name for gtk may be different. Wails attempts to find the correct package by iterating through a list of package names. The list of packages are stored in the packagemanager specific file in the `v2/internal/system/packagemanager` directory. In our example, this would be `v2/internal/system/packagemanager/apt.go`.
-
-In this file, the list of packages are defined by the `Packages()` method:
-
-```go
-func (a *Apt) Packages() packagemap {
- return packagemap{
- "libgtk-3": []*Package{
- {Name: "libgtk-3-dev", SystemPackage: true, Library: true},
- },
- "libwebkit": []*Package{
- {Name: "libwebkit2gtk-4.0-dev", SystemPackage: true, Library: true},
- },
- "gcc": []*Package{
- {Name: "build-essential", SystemPackage: true},
- },
- "pkg-config": []*Package{
- {Name: "pkg-config", SystemPackage: true},
- },
- "npm": []*Package{
- {Name: "npm", SystemPackage: true},
- },
- "docker": []*Package{
- {Name: "docker.io", SystemPackage: true, Optional: true},
- },
- }
-}
-```
-
-Let's assume that in our linux distro, `libgtk-3` is packaged under the name `lib-gtk3-dev`. We could add support for this by adding the following line:
-
-```go {5}
-func (a *Apt) Packages() packagemap {
- return packagemap{
- "libgtk-3": []*Package{
- {Name: "libgtk-3-dev", SystemPackage: true, Library: true},
- {Name: "lib-gtk3-dev", SystemPackage: true, Library: true},
- },
- "libwebkit": []*Package{
- {Name: "libwebkit2gtk-4.0-dev", SystemPackage: true, Library: true},
- },
- "gcc": []*Package{
- {Name: "build-essential", SystemPackage: true},
- },
- "pkg-config": []*Package{
- {Name: "pkg-config", SystemPackage: true},
- },
- "npm": []*Package{
- {Name: "npm", SystemPackage: true},
- },
- "docker": []*Package{
- {Name: "docker.io", SystemPackage: true, Optional: true},
- },
- }
-}
-```
-
-## Adding new package managers
-
-To add a new package manager, perform the following steps:
-
-- Create a new file in `v2/internal/system/packagemanager` called `.go`, where `` is the name of the package manager.
-- Define a struct that conforms to the package manager interface defined in `pm.go`:
-
-```go
-type PackageManager interface {
- Name() string
- Packages() packagemap
- PackageInstalled(*Package) (bool, error)
- PackageAvailable(*Package) (bool, error)
- InstallCommand(*Package) string
-}
-```
-
-- `Name()` should return the name of the package manager
-- `Packages()` should return a `packagemap`, that provides candidate filenames for dependencies
-- `PackageInstalled()` should return `true` if the given package is installed
-- `PackageAvailable()` should return `true` if the given package is not installed but available for installation
-- `InstallCommand()` should return the exact command to install the given package name
-
-Take a look at the other package managers code to get an idea how this works.
-
-:::info Remember
-If you add support for a new package manager, don't forget to also update this page!
-:::
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/migrating.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/migrating.mdx
deleted file mode 100644
index c3b920e05..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/migrating.mdx
+++ /dev/null
@@ -1,187 +0,0 @@
-# Migrating from v1
-
-## Overview
-
-Wails v2 is a significant change from v1. This document aims to highlight the changes and the steps in migrating an existing project.
-
-### Creating the Application
-
-In v1, the main application is created using `wails.CreateApp`, bindings are added with `app.Bind`, then the application is run using `app.Run()`.
-
-Example:
-
-```go title="v1"
- app := wails.CreateApp(&wails.AppConfig{
- Title: "MyApp",
- Width: 1024,
- Height: 768,
- JS: js,
- CSS: css,
- Colour: "#131313",
- })
- app.Bind(basic)
- app.Run()
-```
-
-In v2, there is just a single method, `wails.Run()`, that accepts [application options](../reference/options.mdx#application-options).
-
-```go title="v2"
- err := wails.Run(&options.App{
- Title: "MyApp",
- Width: 800,
- Height: 600,
- Assets: assets,
- Bind: []interface{}{
- basic,
- },
- })
-```
-
-### Binding
-
-In v1, it was possible to bind both arbitrary functions and structs. In v2, this has been simplified to only binding structs. The struct instances that were previously passed to the `Bind()` method in v1, are now specified in the `Bind` field of the [application options](../reference/options.mdx#application-options):
-
-```go title="v1"
- app := wails.CreateApp(/* options */)
- app.Bind(basic)
-```
-
-```go title="v2"
- err := wails.Run(&options.App{
- /* other options */
- Bind: []interface{}{
- basic,
- },
- })
-```
-
-In v1, bound methods were available to the frontend at `window.backend`. This has changed to `window.go`.``
-
-### Application Lifecycle
-
-In v1, there were 2 special methods in a bound struct: `WailsInit()` and `WailsShutdown()`. These have been replaced with 3 lifecycle hooks as part of the [application options](../reference/options.mdx#application-options):
-
-- [OnStartup](../reference/options.mdx#onstartup)
-- [OnShutdown](../reference/options.mdx#onshutdown)
-- [OnDomReady](../reference/options.mdx#ondomready)
-
-Note: [OnDomReady](../reference/options.mdx#ondomready) replaces the `wails:ready` system event in v1.
-
-These methods can be standard functions, but a common practice is to have them part of a struct:
-
-```go title="v2"
- basic := NewBasicApp()
- err := wails.Run(&options.App{
- /* Other Options */
- OnStartup: basic.startup,
- OnShutdown: basic.shutdown,
- OnDomReady: basic.domready,
- })
-...
-type Basic struct {
- ctx context.Context
-}
-func (b *Basic) startup(ctx context.Context) {
- b.ctx = ctx
-}
-...
-```
-
-### Runtime
-
-The runtime in v2 is much richer than v1 with support for menus, window manipulation and better dialogs. The signature of the methods has changed slightly - please refer the the [Runtime Reference](../reference/runtime/intro.mdx).
-
-In v1, the [runtime](../reference/runtime/intro.mdx) was available via a struct passed to `WailsInit()`. In v2, the runtime has been moved out to its own package. Each method in the runtime takes the `context.Context` that is passed to the [OnStartup](../reference/options.mdx#onstartup) method.
-
-```go title="Runtime Example"
-package main
-
-import "github.com/wailsapp/wails/v2/pkg/runtime"
-
-type Basic struct {
- ctx context.Context
-}
-
-// startup is called at application startup
-func (a *App) startup(ctx context.Context) {
- a.ctx = ctx
- runtime.LogInfo(ctx, "Application Startup called!")
-}
-
-```
-
-### Assets
-
-The _biggest_ change in v2 is how assets are handled.
-
-In v1, assets were passed via 2 application options:
-
-- `JS` - The application's Javascript
-- `CSS` - The application's CSS
-
-This meant that the responsibility of generating a single JS and CSS file was on the developer. This essentially required the use of complicated packers such as webpack.
-
-In v2, Wails makes no assumptions about your frontend assets, just like a webserver. All of your application assets are passed to the application options as an `embed.FS`.
-
-**This means there is no requirement to bundle your assets, encode images as Base64 or attempt the dark art of bundler configuration to use custom fonts**.
-
-At startup, Wails will scan the given `embed.FS` for `index.html` and use its location as the root path for all the other application assets - just like a webserver would.
-
-Example: An application has the following project layout. All final assets are placed in the `frontend/dist` directory:
-
-```shell
-.
-├── build/
-├── frontend/
-│ └── dist/
-│ ├── index.html
-│ ├── main.js
-│ ├── main.css
-│ └── logo.svg
-├── main.go
-└── wails.json
-```
-
-Those assets may be used by the application by simply creating an `embed.FS`:
-
-```go title="Assets Example"
-//go:embed frontend/dist
-var assets embed.FS
-
-func main() {
- err := wails.Run(&options.App{
- /* Other Options */
- Assets: assets,
- })
-}
-```
-
-Of course, bundlers can be used if you wish to. The only requirement is to pass the final application assets directory to Wails using an `embed.FS` in the `Assets` key of the [application options](../reference/options.mdx#application-options).
-
-### Project Configuration
-
-In v1, the project configuration was stored in the `project.json` file in the project root. In v2, the project configuration is stored in the `wails.json` file in the project root.
-
-The format of the file is slightly different. Here is a comparison:
-
-
-
-| v1 | v2 | Notes |
-| ------------------ | ---------------- | --------------------------------------------------- |
-| name | name | |
-| description | | Removed |
-| author / name | author / name | |
-| author / email | author / email | |
-| version | version | |
-| binaryname | outputfilename | Changed |
-| frontend / dir | | Removed |
-| frontend / install | frontend:install | Changed |
-| frontend / build | frontend:build | Changed |
-| frontend / bridge | | Removed |
-| frontend / serve | | Removed |
-| tags | | Removed |
-| | wailsjsdir | The directory to generate wailsjs modules |
-| | assetdir | The directory of the compiled frontend assets for `dev` mode. This is normally inferred and could be left empty. |
-| | reloaddirs | Comma separated list of additional directories to watch for changes and to trigger reloads in `dev` mode. This is only needed for some more advanced asset configurations. |
-
-
-
-## Publishing Templates
-
-Publishing a template is simply pushing the files to GitHub. The following best practice is encouraged:
-
-- Remove any unwanted files and directories (such as `.git`) from your frontend directory
-- Ensure that `template.json` is complete, especially `helpurl`
-- Push the files to GitHub
-- Create a PR on the [Community Templates](../community/templates.mdx) page
-- Announce the template on the [Template Announcement](https://github.com/wailsapp/wails/discussions/825) discussion board
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/troubleshooting.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/troubleshooting.mdx
deleted file mode 100644
index b6a73efa5..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/troubleshooting.mdx
+++ /dev/null
@@ -1,137 +0,0 @@
-# Troubleshooting
-
-An assortment of troubleshooting tips.
-
-## The `wails` command appears to be missing?
-
-If your system is reporting that the `wails` command is missing, make sure you have followed the Go installation guide correctly. Normally, it means that the `go/bin` directory in your User's home directory is not in the `PATH` environment variable. You will also normally need to close and reopen any open command prompts so that changes to the environment made by the installer are reflected at the command prompt.
-
-## My application is displaying a white/blank screen
-
-Check that your application includes the assets from the correct directory. In your `main.go` file, you will have something similar to the following code:
-
-```go
-//go:embed frontend/dist
-var assets embed.FS
-```
-
-Check that `frontend/dist` contains your application assets.
-
-### Mac
-
-If this happens on Mac, try adding the following to your `Info.plist`:
-
-```xml
-NSAppTransportSecurity
-
- NSAllowsLocalNetworking
-
-
-```
-
-Reference: https://github.com/wailsapp/wails/issues/1504#issuecomment-1174317433
-
-## Mac application not valid
-
-If your built application looks like this in finder:
-
-
-
-
-
-it's likely that your application's `info.plist` is invalid. Update the file in `build/.app/Contents/info.plist` and check if the data is valid, EG check the binary name is correct. To persist the changes, copy the file back to the `build/darwin` directory.
-
-## Cannot call backend method from frontend with variadic arguments
-
-If you have a backend method defined with variadic parameters, eg:
-
-```go
-func (a *App) TestFunc(msg string, args ...interface{}) error {
- // Code
-}
-```
-
-calling this method from the frontend like this will fail:
-
-```js
-var msg = "Hello: "
-var args = ["Go", "JS"]
-window.go.main.App.TestFunc(msg, ...args).then((result) => {
- //do things here
-}).catch((error) => {
- //handle error
-});
-```
-
-Workaround:
-
-```js
-var msg = "Hello "
-var args = ["Go", "JS"]
-window.go.main.App.TestFunc(msg, args).then((result) => { //without the 3 dots
- //do things here
-}).catch((error) => {
- //handle error
-});
-```
-
-Credit: https://github.com/wailsapp/wails/issues/1186
-
-## I'm having getting proxy errors when trying to install Wails
-
-If you are getting errors like this:
-
-```
-"https://proxy.golang.org/github.com/wailsapp/wails/cmd/wails/@v/list": dial tcp 172.217.163.49:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
-```
-
-it's probably because the official Go Proxy is being blocked (Users in China have reported this). The solution is to set up the proxy manually, eg:
-
-```
-go env -w GO111MODULE=on
-go env -w GOPROXY=https://goproxy.cn,direct
-```
-
-Source: https://github.com/wailsapp/wails/issues/1233
-
-## The generated Typescript doesn't have the correct types
-
-Sometimes the generated Typescript doesn't have the correct types. To mitigate this, it is possible to specify what types should be generated using the `ts_type` struct tag. For more details, please read [this](https://github.com/tkrajina/typescriptify-golang-structs#custom-types).
-
-## When I navigate away from `index.html`, I am unable to call methods on the frontend
-
-If you navigate away from `index.html` to a new html file, the context will be lost. This can be fixed by adding the following imports to the `` section of any new page you navigate to:
-
-```html
-
-
-
-
-```
-
-Source: https://github.com/wailsapp/wails/discussions/1512
-
-## I get `too many open files` errors on my Mac when I run `wails dev`
-
-By default, macOS will only allow you to open a maximum of 256 files. This can affect the `wails dev` command. This limit can be increased by running: `ulimit -n 1024` in the terminal.
-
-FSNotify is [looking to move to Apple's fsevents](https://github.com/fsnotify/fsnotify/issues/11) for Mac. If this isn't completed soon, we will create our own implementation, tracked [here](https://github.com/wailsapp/wails/issues/1733).
-
-## My Mac app gives me weird compilation errors
-
-A few users have reported seeing compilation errors such as the following:
-
-```shell
-# github.com/wailsapp/wails/v2/internal/frontend/desktop/darwin
-In file included from ../../pkg/mod/github.com/wailsapp/wails/v2@v2.0.0-beta.44.2/internal/frontend/desktop/darwin/callbacks.go:9:
-In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX12.1.sdk/System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:12:
-/Library/Developer/CommandLineTools/SDKs/MacOSX12.1.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSBundle.h:91:143: error: function does not return NSString
-- (NSAttributedString *)localizedAttributedStringForKey:(NSString *)key value:(nullable NSString *)value table:(nullable NSString *)tableName NS_FORMAT_ARGUMENT(1) NS_REFINED_FOR_SWIFT API_AVAILABLE(macos(12.0), ios(15.0), watchos(8.0), tvos(15.0));
- ~~~~~~~~~~~~~~ ^ ~
-/Library/Developer/CommandLineTools/SDKs/MacOSX12.1.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSObjCRuntime.h:103:48: note: expanded from macro 'NS_FORMAT_ARGUMENT'
- #define NS_FORMAT_ARGUMENT(A) __attribute__ ((format_arg(A)))
-```
-
-This is *normally* due to a mismatch with the OS version you are running and the version of the XCode Command Line Tools installed. If you see an error like this, try upgrading your XCode Command Line Tools to the latest version.
-
-Source: https://github.com/wailsapp/wails/issues/1806
\ No newline at end of file
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/windows-installer.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/windows-installer.mdx
deleted file mode 100644
index 249ec5527..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/windows-installer.mdx
+++ /dev/null
@@ -1,56 +0,0 @@
-# NSIS installer
-
-
-
-
-
-
-Wails supports generating Windows installers using the [NSIS installer](https://nsis.sourceforge.io/).
-
-## Installing NSIS
-
-### Windows
-
-The installer is available on the [NSIS Download](https://nsis.sourceforge.io/Download) page.
-
-If you use the chocolatey package manager, run the following script:
-
-```
-choco install nsis
-```
-
-If you install NSIS manually, you need to add the *Bin* folder, which contains `makensis.exe`, in your NSIS installation to your path. [Here](https://www.architectryan.com/2018/03/17/add-to-the-path-on-windows-10/) is a good tutorial on how to add to path on Windows.
-
-### Linux
-
-The `nsis` package should be available through your distribution's package manager.
-
-### MacOS
-
-NSIS is available to install through homebrew: `brew install nsis`.
-
-## Generating the installer
-
-When a new project is created, Wails generates the NSIS configuration files in `build/windows/installer`. The config data is read from `installer/info.json` and that is configured to use the project's `wails.json` Info section:
-
-```json
-// ...
- "Info": {
- "companyName": "My Company Name",
- "productName": "Wails Vite",
- "productVersion": "1.0.0",
- "copyright": "Copyright.........",
- "comments": "Built using Wails (https://wails.io)"
- },
-```
-
-To generate an installer for your application, use the `-nsis` flag with `wails build`:
-
-```
-wails build -nsis
-```
-
-The installer will now be available in the `build/bin` directory.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/howdoesitwork.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/howdoesitwork.mdx
deleted file mode 100644
index 95db08724..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/howdoesitwork.mdx
+++ /dev/null
@@ -1,356 +0,0 @@
----
-sidebar_position: 20
----
-
-# How does it work?
-
-A Wails application is a standard Go application, with a webkit frontend. The Go part of the application consists of the application code and a runtime library that provides a number of useful operations, like controlling the application window. The frontend is a webkit window that will display the frontend assets. Also available to the frontend is a Javascript version of the runtime library. Finally, it is possible to bind Go methods to the frontend, and these will appear as Javascript methods that can be called, just as if they were local Javascript methods.
-
-
-
-
-
-## The Main Application
-
-### Overview
-
-The main application consists of a single call to `wails.Run()`. It accepts the application configuration which describes the size of the application window, the window title, what assets to use, etc. A basic application might look like this:
-
-```go title="main.go"
-package main
-
-import (
- "embed"
- "log"
-
- "github.com/wailsapp/wails/v2"
- "github.com/wailsapp/wails/v2/pkg/options"
-)
-
-//go:embed frontend/dist
-var assets embed.FS
-
-func main() {
-
- app := &App{}
-
- err := wails.Run(&options.App{
- Title: "Basic Demo",
- Width: 1024,
- Height: 768,
- Assets: &assets,
- OnStartup: app.startup,
- OnShutdown: app.shutdown,
- Bind: []interface{}{
- app,
- },
- })
- if err != nil {
- log.Fatal(err)
- }
-}
-
-
-type App struct {
- ctx context.Context
-}
-
-func (b *App) startup(ctx context.Context) {
- b.ctx = ctx
-}
-
-func (b *App) shutdown(ctx context.Context) {}
-
-func (b *App) Greet(name string) string {
- return fmt.Sprintf("Hello %s!", name)
-}
-```
-
-### Options rundown
-
-This example has the following options set:
-
-- `Title` - The text that should appear in the window's title bar
-- `Width` & `Height` - The dimensions of the window
-- `Assets` - The application's frontend assets
-- `OnStartup` - A callback for when the window is created and is about to start loading the frontend assets
-- `OnShutdown` - A callback for when the application is about to quit
-- `Bind` - A slice of struct instances that we wish to expose to the frontend
-
-A full list of application options can be found in the [Options Reference](reference/options).
-
-#### Assets
-
-The `Assets` option is mandatory as you can't have a Wails application without frontend assets. Those assets can be any files you would expect to find in a web application - html, js, css, svg, png, etc. **There is no requirement to generate asset bundles** - plain files will do. When the application starts, it will attempt to load `index.html` from your assets and the frontend will essentially work as a browser from that point on. It is worth noting that there is no requirement on where in the `embed.FS` the files live. It is likely that the embed path uses a nested directory relative to your main application code, such as `frontend/dist`:
-
-```go title="main.go"
-//go:embed frontend/dist
-var assets embed.FS
-```
-
-At startup, Wails will iterate the embedded files looking for the directory containing `index.html`. All other assets will be loaded relative to this directory.
-
-As production binaries use the files contained in `embed.FS`, there are no external files required to be shipped with the application.
-
-When running in development mode using the `wails dev` command, the assets are loaded off disk, and any changes result in a "live reload". The location of the assets will be inferred from the `embed.FS`.
-
-More details can be found in the [Application Development Guide](guides/application-development.mdx).
-
-#### Application Lifecycle Callbacks
-
-Just before the frontend is about to load `index.html`, a callback is made to the function provided in [OnStartup](reference/options.mdx#onstartup). A standard Go context is passed to this method. This context is required when calling the runtime so a standard pattern is to save a reference to in this method. Just before the application shuts down, the [OnShutdown](reference/options.mdx#onshutdown) callback is called in the same way, again with the context. There is also an [OnDomReady](reference/options.mdx#ondomready) callback for when the frontend has completed loading all assets in `index.html` and is equivalent of the [`body onload`](https://www.w3schools.com/jsref/event_onload.asp) event in Javascript. It is also possible to hook into the window close (or application quit) event by setting the option [OnBeforeClose](reference/options.mdx#onbeforeclose).
-
-#### Method Binding
-
-The `Bind` option is one of the most important options in a Wails application. It specifies which struct methods to expose to the frontend. Think of structs like "controllers" in a traditional web application. When the application starts, it examines the struct instances listed in the `Bind` field in the options, determines which methods are public (starts with an uppercase letter) and will generate Javascript versions of those methods that can be called by the frontend code.
-
-:::info Note
-
-Wailsで構造体を正しくバインドするためには、構造体の*インスタンス*をオプションで指定してください。
-
-:::
-
-In this example, we create a new `App` instance and then add this instance to the `Bind` option in `wails.Run`:
-
-```go {16,24} title="main.go"
-package main
-
-import (
- "embed"
- "log"
-
- "github.com/wailsapp/wails/v2"
- "github.com/wailsapp/wails/v2/pkg/options"
-)
-
-//go:embed frontend/dist
-var assets embed.FS
-
-func main() {
-
- app := &App{}
-
- err := wails.Run(&options.App{
- Title: "Basic Demo",
- Width: 1024,
- Height: 768,
- Assets: &assets,
- Bind: []interface{}{
- app,
- },
- })
- if err != nil {
- log.Fatal(err)
- }
-}
-
-
-type App struct {
- ctx context.Context
-}
-
-func (a *App) Greet(name string) string {
- return fmt.Sprintf("Hello %s!", name)
-}
-```
-
-You may bind as many structs as you like. Just make sure you create an instance of it and pass it in `Bind`:
-
-```go {8-10}
- //...
- err := wails.Run(&options.App{
- Title: "Basic Demo",
- Width: 1024,
- Height: 768,
- Assets: &assets,
- Bind: []interface{}{
- app,
- &mystruct1{},
- &mystruct2{},
- },
- })
-
-```
-
-When you run `wails dev` (or `wails generate module`), a frontend module will be generated containing the following:
-
-- Javascript bindings for all bound methods
-- Typescript declarations for all bound methods
-- Typescript definitions for all Go structs used as inputs or outputs by the bound methods
-
-This makes it incredibly simple to call Go code from the frontend, using the same strongly typed datastructures.
-
-## The Frontend
-
-### Overview
-
-The frontend is a collection of files rendered by webkit. It's like a browser and webserver in one. There is virtually[^1] no limit to which frameworks or libraries you can use. The main points of interaction between the frontend and your Go code are:
-
-- Calling bound Go methods
-- Calling runtime methods
-
-### Calling bound Go methods
-
-When you run your application with `wails dev`, it will automatically generate Javascript bindings for your structs in a directory called `wailsjs/go` (You can also do this by running `wails generate module`). The generated files mirror the package names in your application. In the example above, we bind `app`, which has one public method `Greet`. This will lead to the generation of the following files:
-
-```bash
-wailsjs
- └─go
- └─main
- ├─App.d.ts
- └─App.js
-```
-
-Here we can see that there is a `main` package that contains the Javascript bindings for the bound `App` struct, as well as the Typescript declaration file for those methods. To call `Greet` from our frontend, we simply import the method and call it like a regular Javascript function:
-
-```javascript
-// ...
-import {Greet} from '../wailsjs/go/main/App'
-
- function doGreeting(name) {
- Greet(name).then((result) => {
- // resultを使って何かする
- })
- }
-```
-
-The Typescript declaration file gives you the correct types for the bound methods:
-
-```ts
-export function Greet(arg1:string):Promise;
-```
-
-The generated methods return a Promise. A successful call will result in the first return value from the Go call to be passed to the `resolve` handler. An unsuccessful call is when a Go method that has an error type as it's second return value, passes an error instance back to the caller. This is passed back via the `reject` handler. In the example above, `Greet` only returns a `string` so the Javascript call will never reject - unless invalid data is passed to it.
-
-All data types are correctly translated between Go and Javascript. Even structs. If you return a struct from a Go call, it will be returned to your frontend as a Javascript class. Note: If you wish to use structs, you **must** define `json` struct tags for your fields!
-
-:::info Note
-Anonymous nested structs are not supported at this time.
-:::
-
-It is possible to send structs back to Go. Any Javascript map/class passed as an argument that is expecting a struct, will be converted to that struct type. To make this process a lot easier, in `dev` mode, a TypeScript module is generated, defining all the struct types used in bound methods. Using this module, it's possible to construct and send native Javascript objects to the Go code.
-
-There is also support for Go methods that use structs in their signature. All Go structs specified by a bound method (either as parameters or return types) will have Typescript versions auto generated as part of the Go code wrapper module. Using these, it's possible to share the same data model between Go and Javascript.
-
-Example: We update our `Greet` method to accept a `Person` instead of a string:
-
-```go title="main.go"
-type Person struct {
- Name string `json:"name"`
- Age uint8 `json:"age"`
- Address *Address `json:"address"`
-}
-
-type Address struct {
- Street string `json:"street"`
- Postcode string `json:"postcode"`
-}
-
-func (a *App) Greet(p Person) string {
- return fmt.Sprintf("Hello %s (Age: %d)!", p.Name, p.Age)
-}
-```
-
-The `wailsjs/go/main/App.js` file will still have the following code:
-
-```js title="App.js"
-export function Greet(arg1) {
- return window['go']['main']['App']['Greet'](arg1);
-}
-```
-
-But the `wailsjs/go/main/App.d.ts` file will be updated with the following code:
-
-```ts title="App.d.ts"
-import {main} from '../models';
-
-export function Greet(arg1:main.Person):Promise;
-```
-
-As we can see, the "main" namespace is imported from a new "models.ts" file. This file contains all the struct definitions used by our bound methods. In this example, this is a `Person` struct. If we look at `models.ts`, we can see how the models are defined:
-
-```ts title="models.ts"
-export namespace main {
-
- export class Address {
- street: string;
- postcode: string;
-
- static createFrom(source: any = {}) {
- return new Address(source);
- }
-
- constructor(source: any = {}) {
- if ('string' === typeof source) source = JSON.parse(source);
- this.street = source["street"];
- this.postcode = source["postcode"];
- }
- }
- export class Person {
- name: string;
- age: number;
- address?: Address;
-
- static createFrom(source: any = {}) {
- return new Person(source);
- }
-
- constructor(source: any = {}) {
- if ('string' === typeof source) source = JSON.parse(source);
- this.name = source["name"];
- this.age = source["age"];
- this.address = this.convertValues(source["address"], Address);
- }
-
- convertValues(a: any, classs: any, asMap: boolean = false): any {
- if (!a) {
- return a;
- }
- if (a.slice) {
- return (a as any[]).map(elem => this.convertValues(elem, classs));
- } else if ("object" === typeof a) {
- if (asMap) {
- for (const key of Object.keys(a)) {
- a[key] = new classs(a[key]);
- }
- return a;
- }
- return new classs(a);
- }
- return a;
- }
- }
-}
-```
-
-So long as you have TypeScript as part of your frontend build configuration, you can use these models in the following way:
-
-```js title="mycode.js"
-import {Greet} from '../wailsjs/go/main/App'
- import {main} from '../wailsjs/go/models'
-
- function generate() {
- let person = new main.Person()
- person.name = "Peter"
- person.age = 27
- Greet(person).then((result) => {
- console.log(result)
- })
- }
-```
-
-The combination of generated bindings and TypeScript models makes for a powerful development environment.
-
-More information on Binding can be found in the [Binding Methods](guides/application-development.mdx#binding-methods) section of the [Application Development Guide](guides/application-development.mdx).
-
-### Calling runtime methods
-
-The Javascript runtime is located at `window.runtime` and contains many methods to do various tasks such as emit an event or perform logging operations:
-
-```js title="mycode.js"
-window.runtime.EventsEmit("my-event", 1);
-```
-
-More details about the JS runtime can be found in the [Runtime Reference](reference/runtime/intro).
-
-[^1]: There is a very small subset of libraries that use features unsupported in WebViews. There are often alternatives and workarounds for such cases.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/introduction.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/introduction.mdx
deleted file mode 100644
index ab616d0a6..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/introduction.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-sidebar_position: 1
----
-
-# Introduction
-
-Wails is a project that enables you to write desktop apps using Go and web technologies.
-
-Consider it a lightweight and fast Electron alternative for Go. You can easily build applications with the flexibility and power of Go, combined with a rich, modern frontend.
-
-### Features
-
-- Native Menus, Dialogs, Theming and Translucency
-- Windows, macOS and linux support
-- Built in templates for Svelte, React, Preact, Vue, Lit and Vanilla JS
-- Easily call Go methods from Javascript
-- Automatic Go struct to Typescript model generation
-- No CGO or external DLLs required on Windows
-- Live development mode using the power of [Vite](https://vite.net/)
-- Powerful CLI to easily Create, Build and Package applications
-- A rich [runtime library](/docs/next/reference/runtime)
-- Applications built with Wails are Apple & Microsoft Store compliant
-
-
-This is [varly](https://varly.app) - a desktop application for MacOS & Windows written using Wails. Not only does it look great, it uses native menus and translucency - everything you'd expect from a modern native app.
-
-
-
-
-
-When clicked, that will open an about message box:
-
-
-
-
-
-
-
-## Linux Specific Options
-
-### Icon
-
-Sets up the icon representing the window. This icon is used when the window is minimized (also known as iconified).
-
-Type: []byte
-
-Some window managers or desktop environments may also place it in the window frame, or display it in other contexts. On others, the icon is not used at all, so your mileage may vary.
-
-NOTE: Gnome on Wayland at least does not display this icon. To have a application icon there, a `.desktop` file has to be used. On KDE it should work.
-
-The icon should be provided in whatever size it was naturally drawn; that is, don’t scale the image before passing it. Scaling is postponed until the last minute, when the desired final size is known, to allow best quality.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/project-config.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/project-config.mdx
deleted file mode 100644
index 3dc1cf002..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/project-config.mdx
+++ /dev/null
@@ -1,51 +0,0 @@
----
-sidebar_position: 5
----
-
-# Project Config
-
-The project config resides in the `wails.json` file in the project directory. The structure of the config is:
-
-```json
-{
- "name": "[The project name]",
- "assetdir": "[Relative path to the directory containing the compiled assets, this is normally inferred and could be left empty]",
- "reloaddirs": "[Additional directories to trigger reloads (comma separated), this is only used for some advanced asset configurations]",
- "frontend:install": "[The command to install node dependencies, run in the frontend directory - often `npm install`]",
- "frontend:build": "[The command to build the assets, run in the frontend directory - often `npm run build`]",
- "frontend:dev": "[This command has been replaced by frontend:dev:build. If frontend:dev:build is not specified will falls back to this command. If this command is also not specified will falls back to frontend:build]",
- "frontend:dev:build": "[This command is the dev equivalent of frontend:build. If not specified falls back to frontend:dev]",
- "frontend:dev:install": "[This command is the dev equivalent of frontend:install. If not specified falls back to frontend:install]",
- "frontend:dev:watcher": "[This command is run in a separate process on `wails dev`. Useful for 3rd party watchers or starting 3d party dev servers]",
- "frontend:dev:serverUrl": "[URL to a 3rd party dev server to be used to serve assets, EG Vite. If this is set to 'auto' then the devServerUrl will be inferred from the Vite output]",
- "wailsjsdir": "[Relative path to the directory that the auto-generated JS modules will be created]",
- "version": "[Project config version]",
- "outputfilename": "[The name of the binary]",
- "debounceMS": 100, // The default time the dev server waits to reload when it detects a change in assets
- "devServer": "[Address to bind the wails dev sever to. Default: localhost:34115]",
- "appargs": "[Arguments passed to the application in shell style when in dev mode]",
- "runNonNativeBuildHooks": false, // Defines if build hooks should be run though they are defined for an OS other than the host OS.
- "preBuildHooks": {
- "GOOS/GOARCH": "[The command that will be executed before a build of the specified GOOS/GOARCH: ${platform} is replaced with the "GOOS/GOARCH". The "GOOS/GOARCH" hook is executed before the "GOOS/*" and "*/*" hook.]",
- "GOOS/*": "[The command that will be executed before a build of the specified GOOS: ${platform} is replaced with the "GOOS/GOARCH". The "GOOS/*" hook is executed before the "*/*" hook.]",
- "*/*": "[The command that will be executed before every build: ${platform} is replaced with the "GOOS/GOARCH".]"
- },
- "postBuildHooks": {
- "GOOS/GOARCH": "[The command that will be executed after a build of the specified GOOS/GOARCH: ${platform} is replaced with the "GOOS/GOARCH" and ${bin} with the path to the compiled binary. The "GOOS/GOARCH" hook is executed before the "GOOS/*" and "*/*" hook.]",
- "GOOS/*": "[The command that will be executed after a build of the specified GOOS: ${platform} is replaced with the "GOOS/GOARCH" and ${bin} with the path to the compiled binary. The "GOOS/*" hook is executed before the "*/*" hook.]",
- "*/*": "[The command that will be executed after every build: ${platform} is replaced with the "GOOS/GOARCH" and ${bin} with the path to the compiled binary.]"
- },
- "info": { // Data used to populate manifests and version info.
- "companyName": "[The company name. Default: [The project name]]",
- "productName": "[The product name. Default: [The project name]]",
- "productVersion": "[The version of the product. Default: '1.0.0']",
- "copyright": "[The copyright of the product. Default: 'Copyright.........']",
- "comments": "[A short comment of the app. Default: 'Built using Wails (https://wails.app)']"
- },
- "nsisType": "['multiple': One installer per architecture. 'single': Single universal installer for all architectures being built. Default: 'multiple']"
-}
-```
-
-This file is read by the Wails CLI when running `wails build` or `wails dev`.
-
-The `assetdir`, `reloaddirs`, `wailsjsdir`, `debounceMS`, `devserver` and `frontenddevserverurl` flags in `wails build/dev` will update the project config and thus become defaults for subsequent runs.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/browser.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/browser.mdx
deleted file mode 100644
index 976ca1d80..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/browser.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
----
-sidebar_position: 7
----
-
-# Browser
-
-These methods are related to the system browser.
-
-### BrowserOpenURL
-
-Opens the given URL in the system browser.
-
-Go: `BrowserOpenURL(ctx context.Context, url string)` JS: `BrowserOpenURL(url string)`
-
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/dialog.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/dialog.mdx
deleted file mode 100644
index bf1dd7246..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/dialog.mdx
+++ /dev/null
@@ -1,283 +0,0 @@
----
-sidebar_position: 5
----
-
-# Dialog
-
-This part of the runtime provides access to native dialogs, such as File Selectors and Message boxes.
-
-:::info Javascript
- Dialog is currently unsupported in the JS runtime.
-:::
-
-### OpenDirectoryDialog
-
-Opens a dialog that prompts the user to select a directory. Can be customised using [OpenDialogOptions](#opendialogoptions).
-
-Go: `OpenDirectoryDialog(ctx context.Context, dialogOptions OpenDialogOptions) (string, error)`
-
-Returns: Selected directory (blank if the user cancelled) or an error
-
-### OpenFileDialog
-
-Opens a dialog that prompts the user to select a file. Can be customised using [OpenDialogOptions](#opendialogoptions).
-
-Go: `OpenFileDialog(ctx context.Context, dialogOptions OpenDialogOptions) (string, error)`
-
-Returns: Selected file (blank if the user cancelled) or an error
-
-### OpenMultipleFilesDialog
-
-Opens a dialog that prompts the user to select multiple files. Can be customised using [OpenDialogOptions](#opendialogoptions).
-
-Go: `OpenMultipleFilesDialog(ctx context.Context, dialogOptions OpenDialogOptions) ([]string, error)`
-
-Returns: Selected files (nil if the user cancelled) or an error
-
-### SaveFileDialog
-
-Opens a dialog that prompts the user to select a filename for the purposes of saving. Can be customised using [SaveDialogOptions](#savedialogoptions).
-
-Go: `SaveFileDialog(ctx context.Context, dialogOptions SaveDialogOptions) (string, error)`
-
-Returns: The selected file (blank if the user cancelled) or an error
-
-### MessageDialog
-
-Displays a message using a message dialog. Can be customised using [MessageDialogOptions](#messagedialogoptions).
-
-Go: `MessageDialog(ctx context.Context, dialogOptions MessageDialogOptions) (string, error)`
-
-Returns: The text of the selected button or an error
-
-## Options
-
-### OpenDialogOptions
-
-```go
-type OpenDialogOptions struct {
- DefaultDirectory string
- DefaultFilename string
- Title string
- Filters []FileFilter
- ShowHiddenFiles bool
- CanCreateDirectories bool
- ResolvesAliases bool
- TreatPackagesAsDirectories bool
-}
-```
-
-| Field | Description | Win | Mac | Lin |
-| -------------------------- | ---------------------------------------------- | --- | --- | --- |
-| DefaultDirectory | The directory the dialog will show when opened | ✅ | ✅ | ✅ |
-| DefaultFilename | The default filename | ✅ | ✅ | ✅ |
-| Title | Title for the dialog | ✅ | ✅ | ✅ |
-| [Filters](#filefilter) | A list of file filters | ✅ | ✅ | ✅ |
-| ShowHiddenFiles | Show files hidden by the system | | ✅ | ✅ |
-| CanCreateDirectories | Allow user to create directories | | ✅ | |
-| ResolvesAliases | If true, returns the file not the alias | | ✅ | |
-| TreatPackagesAsDirectories | Allow navigating into packages | | ✅ | |
-
-### SaveDialogOptions
-
-```go
-type SaveDialogOptions struct {
- DefaultDirectory string
- DefaultFilename string
- Title string
- Filters []FileFilter
- ShowHiddenFiles bool
- CanCreateDirectories bool
- TreatPackagesAsDirectories bool
-}
-```
-
-| Field | Description | Win | Mac | Lin |
-| -------------------------- | ---------------------------------------------- | --- | --- | --- |
-| DefaultDirectory | The directory the dialog will show when opened | ✅ | ✅ | ✅ |
-| DefaultFilename | The default filename | ✅ | ✅ | ✅ |
-| Title | Title for the dialog | ✅ | ✅ | ✅ |
-| [Filters](#filefilter) | A list of file filters | ✅ | ✅ | ✅ |
-| ShowHiddenFiles | Show files hidden by the system | | ✅ | ✅ |
-| CanCreateDirectories | Allow user to create directories | | ✅ | |
-| TreatPackagesAsDirectories | Allow navigating into packages | | ✅ | |
-
-### MessageDialogOptions
-
-```go
-type MessageDialogOptions struct {
- Type DialogType
- Title string
- Message string
- Buttons []string
- DefaultButton string
- CancelButton string
-}
-```
-
-| Field | Description | Win | Mac | Lin |
-| ------------- | ------------------------------------------------------------------------- | --- | --- | --- |
-| Type | The type of message dialog, eg question, info... | ✅ | ✅ | ✅ |
-| Title | Title for the dialog | ✅ | ✅ | ✅ |
-| Message | The message to show the user | ✅ | ✅ | ✅ |
-| Buttons | A list of button titles | | ✅ | |
-| DefaultButton | The button with this text should be treated as default. Bound to `return` | | ✅ | |
-| CancelButton | The button with this text should be treated as cancel. Bound to `escape` | | ✅ | |
-
-#### Windows
-
-Windows has standard dialog types in which the buttons are not customisable. The value returned will be one of: "Ok", "Cancel", "Abort", "Retry", "Ignore", "Yes", "No", "Try Again" or "Continue"
-
-#### Linux
-
-Linux has standard dialog types in which the buttons are not customisable. The value returned will be one of: "Ok", "Cancel", "Yes", "No"
-
-#### Mac
-
-A message dialog on Mac may specify up to 4 buttons. If no `DefaultButton` or `CancelButton` is given, the first button is considered default and is bound to the `return` key.
-
-For the following code:
-
-```go
-selection, err := runtime.MessageDialog(b.ctx, runtime.MessageDialogOptions{
- Title: "It's your turn!",
- Message: "Select a number",
- Buttons: []string{"one", "two", "three", "four"},
-})
-```
-
-the first button is shown as default:
-
-
-
-
-
-
-
-And if we specify `DefaultButton` to be "two":
-
-```go
-selection, err := runtime.MessageDialog(b.ctx, runtime.MessageDialogOptions{
- Title: "It's your turn!",
- Message: "Select a number",
- Buttons: []string{"one", "two", "three", "four"},
- DefaultButton: "two",
-})
-```
-
-the second button is shown as default. When `return` is pressed, the value "two" is returned.
-
-
-
-
-
-
-
-If we now specify `CancelButton` to be "three":
-
-```go
-selection, err := runtime.MessageDialog(b.ctx, runtime.MessageDialogOptions{
- Title: "It's your turn!",
- Message: "Select a number",
- Buttons: []string{"one", "two", "three", "four"},
- DefaultButton: "two",
- CancelButton: "three",
-})
-```
-
-the button with "three" is shown at the bottom of the dialog. When `escape` is pressed, the value "three" is returned:
-
-
-
-
-
-
-
-
-
-#### DialogType
-
-```go
-const (
- InfoDialog DialogType = "info"
- WarningDialog DialogType = "warning"
- ErrorDialog DialogType = "error"
- QuestionDialog DialogType = "question"
- )
-```
-
-### FileFilter
-
-```go
-type FileFilter struct {
- DisplayName string // Filter information EG: "Image Files (*.jpg, *.png)"
- Pattern string // semi-colon separated list of extensions, EG: "*.jpg;*.png"
-}
-```
-
-#### Windows
-
-Windows allows you to use multiple file filters in dialog boxes. Each FileFilter will show up as a separate entry in the dialog:
-
-
-
-
-
-
-
-
-
-#### Linux
-
-Linux allows you to use multiple file filters in dialog boxes. Each FileFilter will show up as a separate entry in the dialog:
-
-
-
-
-
-
-
-
-
-#### Mac
-
-Mac dialogs only have the concept of a single set of patterns to filter files. If multiple FileFilters are provided, Wails will use all the Patterns defined.
-
-Example:
-
-```go
- selection, err := runtime.OpenFileDialog(b.ctx, runtime.OpenDialogOptions{
- Title: "Select File",
- Filters: []runtime.FileFilter{
- {
- DisplayName: "Images (*.png;*.jpg)",
- Pattern: "*.png;*.jpg",
- }, {
- DisplayName: "Videos (*.mov;*.mp4)",
- Pattern: "*.mov;*.mp4",
- },
- },
- })
-```
-
-This will result in the Open File dialog using `*.png,*.jpg,*.mov,*.mp4` as a filter.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/events.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/events.mdx
deleted file mode 100644
index 75e8b0a50..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/events.mdx
+++ /dev/null
@@ -1,38 +0,0 @@
----
-sidebar_position: 2
----
-
-# Events
-
-The Wails runtime provides a unified events system, where events can be emitted or received by either Go or Javascript. Optionally, data may be passed with the events. Listeners will receive the data in the local data types.
-
-### EventsOn
-
-This method sets up a listener for the given event name. When an event of type `eventName` is [emitted](#EventsEmit), the callback is triggered. Any additional data sent with the emitted event will be passed to the callback.
-
-Go: `EventsOn(ctx context.Context, eventName string, callback func(optionalData ...interface{}))` JS: `EventsOn(eventName string, callback function(optionalData?: any))`
-
-### EventsOff
-
-This method unregisters the listener for the given event name, optionally multiple listeneres can be unregistered via `additionalEventNames`.
-
-Go: `EventsOff(ctx context.Context, eventName string, additionalEventNames ...string)` JS: `EventsOff(eventName string, ...additionalEventNames)`
-
-### EventsOnce
-
-This method sets up a listener for the given event name, but will only trigger once.
-
-Go: `EventsOnce(ctx context.Context, eventName string, callback func(optionalData ...interface{}))` JS: `EventsOnce(eventName string, callback function(optionalData?: any))`
-
-### EventsOnMultiple
-
-This method sets up a listener for the given event name, but will only trigger a maximum of `counter` times.
-
-Go: `EventsOnMultiple(ctx context.Context, eventName string, callback func(optionalData ...interface{}), counter int)` JS: `EventsOnMultiple(eventName string, callback function(optionalData?: any), counter int)`
-
-### EventsEmit
-
-This method emits the given event. Optional data may be passed with the event. This will trigger any event listeners.
-
-Go: `EventsEmit(ctx context.Context, eventName string, optionalData ...interface{})` JS: `EventsEmit(ctx context, optionalData function(optionalData?: any))`
-
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/intro.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/intro.mdx
deleted file mode 100644
index 6c02c71cd..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/intro.mdx
+++ /dev/null
@@ -1,73 +0,0 @@
----
-sidebar_position: 1
----
-
-# Introduction
-
-The runtime is a library that provides utility methods for your application. There is both a Go and Javascript runtime and the aim is to try and keep them at parity where possible.
-
-It has utility methods for:
-
-- [Window](window.mdx)
-- [Menu](menu.mdx)
-- [Dialog](dialog.mdx)
-- [Events](events.mdx)
-- [Browser](browser.mdx)
-- [Log](log.mdx)
-
-The Go Runtime is available through importing `github.com/wailsapp/wails/v2/pkg/runtime`. All methods in this package take a context as the first parameter. This context should be obtained from the [OnStartup](../options.mdx#onstartup) or [OnDomReady](../options.mdx#ondomready) hooks.
-
-:::info Note
-
-Whilst the context will be provided to the [OnStartup](../options.mdx#onstartup) method, there's no guarantee the runtime will work in this method as the window is initialising in a different thread. If you wish to call runtime methods at startup, use [OnDomReady](../options.mdx#ondomready).
-
-:::
-
-The Javascript library is available to the frontend via the `window.runtime` map. There is a runtime package generated when using `dev` mode that provides Typescript declarations for the runtime. This should be located in the `wailsjs` directory in your frontend directory.
-
-### Hide
-
-Go: `Hide(ctx context.Context)` JS: `Hide()`
-
-Hides the application.
-
-:::info Note On Mac, this will hide the application in the same way as the `Hide` menu item in standard Mac applications. This is different to hiding the window, but the application still being in the foreground. For Windows and Linux, this is currently the same as `WindowHide`. :::
-
-### Show
-
-Shows the application.
-
-:::info Note On Mac, this will bring the application back into the foreground. For Windows and Linux, this is currently the same as `WindowShow`. :::
-
-Go: `Show(ctx context.Context)` JS: `Show()`
-
-### Quit
-
-Quits the application.
-
-Go: `Quit(ctx context.Context)` JS: `Quit()`
-
-### Environment
-
-Returns details of the current environment.
-
-Go: `Environment(ctx context.Context) EnvironmentInfo` JS: `Environment(): Promise`
-
-#### EnvironmentInfo
-
-Go:
-```go
-type EnvironmentInfo struct {
- BuildType string
- Platform string
- Arch string
-}
-```
-JS:
-```ts
-interface EnvironmentInfo {
- buildType: string;
- platform: string;
- arch: string;
-}
-```
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/log.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/log.mdx
deleted file mode 100644
index e5e6ea7ac..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/log.mdx
+++ /dev/null
@@ -1,130 +0,0 @@
----
-sidebar_position: 3
----
-
-# Log
-
-The Wails runtime provides a logging mechanism that may be called from Go or Javascript. Like most loggers, there are a number of log levels:
-
-- Trace
-- Debug
-- Info
-- Warning
-- Error
-- Fatal
-
-The logger will output any log message at the current, or higher, log level. Example: The `Debug` log level will output all messages except `Trace` messages.
-
-### LogPrint
-
-Logs the given message as a raw message.
-
-Go: `LogPrint(ctx context.Context, message string)` JS: `LogPrint(message: string)`
-
-### LogPrintf
-
-Logs the given message as a raw message.
-
-Go: `LogPrintf(ctx context.Context, format string, args ...interface{})`
-
-### LogTrace
-
-Logs the given message at the `Trace` log level.
-
-Go: `LogTrace(ctx context.Context, message string)` JS: `LogTrace(message: string)`
-
-### LogTracef
-
-Logs the given message at the `Trace` log level.
-
-Go: `LogTracef(ctx context.Context, format string, args ...interface{})`
-
-### LogDebug
-
-Logs the given message at the `Debug` log level.
-
-Go: `LogDebug(ctx context.Context, message string)` JS: `LogDebug(message: string)`
-
-### LogDebugf
-
-Logs the given message at the `Debug` log level.
-
-Go: `LogDebugf(ctx context.Context, format string, args ...interface{})`
-
-### LogInfo
-
-Logs the given message at the `Info` log level.
-
-Go: `LogInfo(ctx context.Context, message string)` JS: `LogInfo(message: string)`
-
-### LogInfof
-
-Logs the given message at the `Info` log level.
-
-Go: `LogInfof(ctx context.Context, format string, args ...interface{})`
-
-### LogWarning
-
-Logs the given message at the `Warning` log level.
-
-Go: `LogWarning(ctx context.Context, message string)` JS: `LogWarning(message: string)`
-
-### LogWarningf
-
-Logs the given message at the `Warning` log level.
-
-Go: `LogWarningf(ctx context.Context, format string, args ...interface{})`
-
-### LogError
-
-Logs the given message at the `Error` log level.
-
-Go: `LogError(ctx context.Context, message string)` JS: `LogError(message: string)`
-
-### LogErrorf
-
-Logs the given message at the `Error` log level.
-
-Go: `LogErrorf(ctx context.Context, format string, args ...interface{})`
-
-### LogFatal
-
-Logs the given message at the `Fatal` log level.
-
-Go: `LogFatal(ctx context.Context, message string)` JS: `LogFatal(message: string)`
-
-### LogFatalf
-
-Logs the given message at the `Fatal` log level.
-
-Go: `LogFatalf(ctx context.Context, format string, args ...interface{})`
-
-### LogSetLogLevel
-
-Sets the log level. In Javascript, the number relates to the following log levels:
-
-| Value | Log Level |
-| ----- | --------- |
-| 1 | Trace |
-| 2 | Debug |
-| 3 | Info |
-| 4 | Warning |
-| 5 | Error |
-
-Go: `LogSetLogLevel(ctx context.Context, level logger.LogLevel)` JS: `LogSetLogLevel(level: number)`
-
-## Using a Custom Logger
-
-A custom logger may be used by providing it using the [Logger](../options.mdx#logger) application option. The only requirement is that the logger implements the `logger.Logger` interface defined in `github.com/wailsapp/wails/v2/pkg/logger`:
-
-```go title="logger.go"
-type Logger interface {
- Print(message string)
- Trace(message string)
- Debug(message string)
- Info(message string)
- Warning(message string)
- Error(message string)
- Fatal(message string)
-}
-```
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/menu.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/menu.mdx
deleted file mode 100644
index 226ff2c68..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/menu.mdx
+++ /dev/null
@@ -1,23 +0,0 @@
----
-sidebar_position: 6
----
-
-# Menu
-
-These methods are related to the application menu.
-
-:::info Javascript
- Menu is currently unsupported in the JS runtime.
-:::
-
-### MenuSetApplicationMenu
-
-Sets the application menu to the given [menu](../menus.mdx).
-
-Go: `MenuSetApplicationMenu(ctx context.Context, menu *menu.Menu)`
-
-### MenuUpdateApplicationMenu
-
-Updates the application menu, picking up any changes to the menu passed to `MenuSetApplicationMenu`.
-
-Go: `MenuUpdateApplicationMenu(ctx context.Context)`
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/window.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/window.mdx
deleted file mode 100644
index d33db2cbf..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/window.mdx
+++ /dev/null
@@ -1,209 +0,0 @@
----
-sidebar_position: 4
----
-
-# Window
-
-These methods give control of the application window.
-
-### WindowSetTitle
-
-Sets the text in the window title bar.
-
-Go: `WindowSetTitle(ctx context.Context, title string)` JS: `WindowSetTitle(title: string)`
-
-### WindowFullscreen
-
-Makes the window full screen.
-
-Go: `WindowFullscreen(ctx context.Context)` JS: `WindowFullscreen()`
-
-### WindowUnfullscreen
-
-Restores the previous window dimensions and position prior to full screen.
-
-Go: `WindowUnfullscreen(ctx context.Context)` JS: `WindowUnfullscreen()`
-
-### WindowIsFullscreen
-
-Returns true if the window is full screen.
-
-Go: `WindowCenter(ctx context.Context)` JS: `WindowCenter()`
-
-### WindowCenter
-
-Centers the window on the monitor the window is currently on.
-
-Go: `WindowReload(ctx context.Context)` JS: `WindowReload()`
-
-### WindowReload
-
-Performs a "reload" (Reloads current page).
-
-Go: `WindowReloadApp(ctx context.Context)` JS: `WindowReloadApp()`
-
-### WindowReloadApp
-
-Reloads the application frontend.
-
-Go: `WindowSetSystemDefaultTheme(ctx context.Context)` JS: `WindowSetSystemDefaultTheme()`
-
-### WindowSetSystemDefaultTheme
-
-Windows only.
-
-Go: `WindowSetDarkTheme(ctx context.Context)` JS: `WindowSetDarkTheme()`
-
-Sets window theme to system default (dark/light).
-
-### WindowSetLightTheme
-
-Windows only.
-
-Go: `WindowSetLightTheme(ctx context.Context)` JS: `WindowSetLightTheme()`
-
-Sets window theme to light.
-
-### WindowSetDarkTheme
-
-Windows only.
-
-Go: `WindowShow(ctx context.Context)` JS: `WindowShow()`
-
-Sets window theme to dark.
-
-### WindowShow
-
-Shows the window, if it is currently hidden.
-
-Go: `WindowHide(ctx context.Context)` JS: `WindowHide()`
-
-### WindowHide
-
-Hides the window, if it is currently visible.
-
-Go: `WindowSetSize(ctx context.Context, width int, height int)` JS: `WindowSetSize(size: Size)`
-
-### WindowIsNormal
-
-Returns true if the window not minimised, maximised or fullscreen.
-
-Go: `WindowGetSize(ctx context.Context) (width int, height int)` JS: `WindowGetSize() : Size`
-
-### WindowSetSize
-
-Sets the width and height of the window.
-
-Go: `WindowSetMaxSize(ctx context.Context, width int, height int)` JS: `WindowSetMaxSize(size: Size)`
-
-### WindowGetSize
-
-Gets the width and height of the window.
-
-Go: `WindowSetMinSize(ctx context.Context, width int, height int)` JS: `WindowSetMinSize(size: Size)`
-
-### WindowSetMinSize
-
-Sets the minimum window size. Will resize the window if the window is currently smaller than the given dimensions.
-
-Setting a size of `0,0` will disable this constraint.
-
-Go: `WindowSetAlwaysOnTop(ctx context.Context, b bool)` JS: `WindowSetAlwaysOnTop(b: Boolen)`
-
-### WindowSetMaxSize
-
-Sets the maximum window size. Will resize the window if the window is currently larger than the given dimensions.
-
-Setting a size of `0,0` will disable this constraint.
-
-Go: `WindowSetPosition(ctx context.Context, x int, y int)` JS: `WindowSetPosition(position: Position)`
-
-### WindowSetAlwaysOnTop
-
-Sets the window AlwaysOnTop or not on top.
-
-Go: `WindowGetPosition(ctx context.Context) (x int, y int)` JS: `WindowGetPosition() : Position`
-
-### WindowSetPosition
-
-Sets the window position relative to the monitor the window is currently on.
-
-Go: `WindowMaximise(ctx context.Context)` JS: `WindowMaximise()`
-
-### WindowGetPosition
-
-Gets the window position relative to the monitor the window is currently on.
-
-Go: `WindowUnmaximise(ctx context.Context)` JS: `WindowUnmaximise()`
-
-### WindowMaximise
-
-Maximises the window to fill the screen.
-
-Go: `WindowToggleMaximise(ctx context.Context)` JS: `WindowToggleMaximise()`
-
-### WindowUnmaximise
-
-Restores the window to the dimensions and position prior to maximising.
-
-Go: `WindowMinimise(ctx context.Context)` JS: `WindowMinimise()`
-
-### WindowIsMaximised
-
-Returns true if the window is maximised.
-
-Go: `WindowUnminimise(ctx context.Context)` JS: `WindowUnminimise()`
-
-### WindowToggleMaximise
-
-Toggles between Maximised and UnMaximised.
-
-Go: `WindowToggleMaximise(ctx context.Context)` JS: `WindowToggleMaximise()`
-
-### WindowMinimise
-
-Minimises the window.
-
-Go: `WindowSetBackgroundColour(ctx context.Context, R, G, B, A uint8)` JS: `WindowSetBackgroundColour(R, G, B, A)`
-
-### WindowUnminimise
-
-Restores the window to the dimensions and position prior to minimising.
-
-Go: `WindowUnminimise(ctx context.Context)` JS: `WindowUnminimise()`
-
-### WindowIsMinimised
-
-Returns true if the window is minimised.
-
-Go: `WindowIsMinimised(ctx context.Context) bool` JS: `WindowIsMinimised() bool`
-
-### WindowSetBackgroundColour
-
-Sets the background colour of the window to the given RGBA colour definition. This colour will show through for all transparent pixels.
-
-Valid values for R, G, B and A are 0-255.
-
-Any value that is not 0 will be considered 255. Any value that is not 0 will be considered 255. :::
-
-Go: `WindowSetBackgroundColour(ctx context.Context, R, G, B, A uint8)` JS: `WindowSetBackgroundColour(R, G, B, A)`
-
-## Typescript Object Definitions
-
-### Position
-
-```ts
-interface Position {
- x: number;
- y: number;
-}
-```
-
-### Size
-
-```ts
-interface Size {
- w: number;
- h: number;
-}
-```
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/tutorials/dogsapi.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/tutorials/dogsapi.mdx
deleted file mode 100644
index f4845fdbe..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/tutorials/dogsapi.mdx
+++ /dev/null
@@ -1,243 +0,0 @@
----
-sidebar_position: 20
----
-
-# Dogs API
-
-
-
-
-
-
-
-:::note This tutorial has been kindly provided by [@tatadan](https://twitter.com/tatadan) and forms part of their [Wails Examples Repository](https://github.com/tataDan/wails-v2-examples). :::
-
-In this tutorial we are going to develop an application that retrieves photos of dogs from the web and then displays them.
-
-### Create the project
-
-Let's create the application. From a terminal enter: `wails init -n dogs-api -t svelte`
-
-Note: We could optionally add `-ide vscode` or `-ide goland` to the end of this command if you wanted to add IDE support.
-
-Now let's `cd dogs-api` and start editing the project files.
-
-### Remove unused code
-
-We will start by removing some elements that we know we will not use:
-
-- Open `app.go` and remove the following lines:
-
-```go
-// Greet returns a greeting for the given name
-func (a *App) Greet(name string) string {
- return fmt.Sprintf("Hello %s, It's show time!", name)
-}
-```
-
-- Open `frontend/src/App.svelte` and delete all lines.
-- Delete the `frontend/src/assets/images/logo-universal.png` file
-
-### Creating our application
-
-Now let's add our new Go code.
-
-Add the following struct declarations to `app.go` before the function definitions:
-
-```go
-type RandomImage struct {
- Message string
- Status string
-}
-
-type AllBreeds struct {
- Message map[string]map[string][]string
- Status string
-}
-
-type ImagesByBreed struct {
- Message []string
- Status string
-}
-```
-
-Add the following functions to `app.go` (perhaps after the existing function definitions):
-
-```go
-func (a *App) GetRandomImageUrl() string {
- response, err := http.Get("https://dog.ceo/api/breeds/image/random")
- if err != nil {
- log.Fatal(err)
- }
-
- responseData, err := ioutil.ReadAll(response.Body)
- if err != nil {
- log.Fatal(err)
- }
-
- var data RandomImage
- json.Unmarshal(responseData, &data)
-
- return data.Message
-}
-
-func (a *App) GetBreedList() []string {
- var breeds []string
-
- response, err := http.Get("https://dog.ceo/api/breeds/list/all")
- if err != nil {
- log.Fatal(err)
- }
-
- responseData, err := ioutil.ReadAll(response.Body)
- if err != nil {
- log.Fatal(err)
- }
-
- var data AllBreeds
- json.Unmarshal(responseData, &data)
-
- for k := range data.Message {
- breeds = append(breeds, k)
- }
-
- sort.Strings(breeds)
-
- return breeds
-}
-
-func (a *App) GetImageUrlsByBreed(breed string) []string {
-
- url := fmt.Sprintf("%s%s%s%s", "https://dog.ceo/api/", "breed/", breed, "/images")
- response, err := http.Get(url)
- if err != nil {
- log.Fatal(err)
- }
-
- responseData, err := ioutil.ReadAll(response.Body)
- if err != nil {
- log.Fatal(err)
- }
-
- var data ImagesByBreed
- json.Unmarshal(responseData, &data)
-
- return data.Message
-}
-```
-
-Modify the `import` section of `app.go` to look like this:
-
-```go
-import (
- "context"
- "fmt"
- "encoding/json"
- "io/ioutil"
- "log"
- "net/http"
- "sort"
-)
-```
-
-Add the following lines to `frontend/src/App.svelte`:
-
-```html
-
-
-
Dogs API
-
-
- Click on down arrow to select a breed
-
-
-
-
-{#if showRandomPhoto}
-
-{/if}
-{#if showBreedPhotos}
- {#each photos as photo}
-
- {/each}
-{/if}
-
-
-```
-
-### Testing the application
-
-To generate the bindings and test the application, run `wails dev`.
-
-### Compiling the application
-
-To compile the application to a single, production grade binary, run `wails build`.
-
-
-
-
-
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/tutorials/helloworld.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/tutorials/helloworld.mdx
deleted file mode 100644
index d1b8e9f98..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/tutorials/helloworld.mdx
+++ /dev/null
@@ -1,118 +0,0 @@
----
-sidebar_position: 10
----
-
-# Hello World
-
-The aim of this tutorial is to get you up and running with the most basic application using Wails. You will be able to:
-
-- Create a new Wails application
-- Build the application
-- Run the application
-
-:::note
-This tutorial uses Windows as the target platform. Output will vary slightly
-depending on your operating system.
-:::
-
-## Create a new Wails application
-
-To create a new Wails application using the default vanilla JS template, you need to run the following command:
-
-```bash
-wails init -n helloworld
-```
-
-You should see something similar to the following:
-
-```
-Wails CLI v2.0.0
-
-Initialising Project 'helloworld'
----------------------------------
-
-Project Name: helloworld
-Project Directory: C:\Users\leaan\tutorial\helloworld
-Project Template: vanilla
-Template Support: https://wails.io
-
-Initialised project 'helloworld' in 232ms.
-```
-
-This will create a new directory called `helloworld` in the current directory. In this directory, you will find a number of files:
-
-```
-build/ - Contains the build files + compiled application
-frontend/ - Contains the frontend files
-app.go - Contains the application code
-main.go - The main program with the application configuration
-wails.json - The project configuration file
-go.mod - The go module file
-go.sum - The go module checksum file
-```
-
-## Build the application
-
-To build the application, change to the new `helloworld` project directory and run the following command:
-
-```bash
-wails build
-```
-
-You should see something like the following:
-
-```
-Wails CLI v2.0.0
-
-App Type: desktop
-Platforms: windows/amd64
-Compiler: C:\Users\leaan\go\go1.18.3\bin\go.exe
-Build Mode: Production
-Skip Frontend: false
-Compress: false
-Package: true
-Clean Build Dir: false
-LDFlags: ""
-Tags: []
-Race Detector: false
-
-Building target: windows/amd64
-------------------------------
- - Installing frontend dependencies: Done.
- - Compiling frontend: Done.
- - Generating bundle assets: Done.
- - Compiling application: Done.
-Built 'C:\Users\leaan\tutorial\helloworld\build\bin\helloworld.exe' in 10.616s.
-```
-
-This has compiled the application and saved it in the `build/bin` directory.
-
-## Run the application
-
-If we view the `build/bin` directory in Windows Explorer, we should see our project binary:
-
-
-
-
-
-
-
-We can run it by simply double-clicking the `helloworld.exe` file.
-
-On Mac, Wails generates a `helloworld.app` file which can be run by double-clicking it.
-
-On Linux, you can run the application using `./helloworld` from the `build/bin` directory.
-
-You should see the application working as expected:
-
-
-
-
-
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/community/links.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/community/links.mdx
deleted file mode 100644
index 49cb7843b..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/community/links.mdx
+++ /dev/null
@@ -1,22 +0,0 @@
----
-sidebar_position: 2
----
-
-# Links
-
-This page serves as a list for community related links. Please submit a PR (click `Edit this page` at the bottom) to submit links.
-
-## Awesome Wails
-
-The [definitive list](https://github.com/wailsapp/awesome-wails) of links related to Wails.
-
-## Support Channels
-
-- [Discord](https://discord.com/invite/JDdSxwjhGf)
-- [Github Issues](https://github.com/wailsapp/wails/issues)
-- [v2 Beta Discussion Board](https://github.com/wailsapp/wails/discussions/828)
-
-## Social Media
-
-- [Twitter](https://twitter.com/wailsapp)
-- [Wails Chinese Community QQ Group](https://qm.qq.com/cgi-bin/qm/qr?k=PmIURne5hFGNd7QWzW5qd6FV-INEjNJv&jump_from=webapi) - Group number: 1067173054
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/filehound.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/filehound.mdx
deleted file mode 100644
index 134365aaf..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/filehound.mdx
+++ /dev/null
@@ -1,16 +0,0 @@
-# FileHound Export Utility
-
-```mdx-code-block
-
-
-
-
-```
-
-[FileHound Export Utility](https://www.filehound.co.uk/) FileHound is a cloud document management platform made for secure file retention, business process automation and SmartCapture capabilities.
-
-The FileHound Export Utility allows FileHound Administrators the ability to run a secure document and data extraction tasks for alternative back-up and recovery purposes. This application will download all documents and/or meta data saved in FileHound based on the filters you choose. The metadata will be exported in both JSON and XML formats.
-
-Backend built with: Go 1.15 Wails 1.11.0 go-sqlite3 1.14.6 go-linq 3.2
-
-Frontend with: Vue 2.6.11 Vuex 3.4.0 Typescript Tailwind 1.9.6
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/community/templates.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/community/templates.mdx
deleted file mode 100644
index 3c24c5d7e..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/community/templates.mdx
+++ /dev/null
@@ -1,54 +0,0 @@
----
-sidebar_position: 1
----
-
-# Templates
-
-This page serves as a list for community supported templates. Please submit a PR (click `Edit this page` at the bottom) to include your templates. To build your own template, please see the [Templates](../guides/templates.mdx) guide.
-
-To use these templates, run `wails init -n "Your Project Name" -t [the link below[@version]]`
-
-If there is no version suffix, the main branch code template is used by default. If there is a version suffix, the code template corresponding to the tag of this version is used.
-
-Example: `wails init -n "Your Project Name" -t https://github.com/misitebao/wails-template-vue`
-
-:::warning Attention
-
-
-**The Wails project does not maintain, is not responsible nor liable for 3rd party templates!**
-
-If you are unsure about a template, inspect `package.json` and `wails.json` for what scripts are run and what packages are installed.
-
-:::
-
-
-## Vue
-
-- [wails-template-vue](https://github.com/misitebao/wails-template-vue) - A template using Vite,Vue and Vue-Router(Support both JavaScript and TypeScript)
-- [wails-vite-vue-ts](https://github.com/codydbentley/wails-vite-vue-ts) - Vue 3 TypeScript with Vite (and instructions to add features)
-- [wails-vite-vue-the-works](https://github.com/codydbentley/wails-vite-vue-the-works) - Vue 3 TypeScript with Vite, Vuex, Vue Router, Sass, and ESLint + Prettier
-
-## Angular
-
-- [wails-angular-template](https://github.com/TAINCER/wails-angular-template) - Angular with TypeScript, Sass, Hot-Reload, Code-Splitting and i18n
-
-## React
-
-- [wails-react-template](https://github.com/AlienRecall/wails-react-template) - A template using reactjs
-- [wails-react-template](https://github.com/flin7/wails-react-template) - A minimal template for React that supports live development
-- [wails-template-nextjs](https://github.com/LGiki/wails-template-nextjs) - A template using Next.js and TypeScript
-
-## Svelte
-
-- [wails-svelte-template](https://github.com/raitonoberu/wails-svelte-template) - A template using Svelte
-- [wails-vite-svelte-template](https://github.com/BillBuilt/wails-vite-svelte-template) - A template using Svelte and Vite
-- [wails-vite-svelte-tailwind-template](https://github.com/BillBuilt/wails-vite-svelte-tailwind-template) - A template using Svelte and Vite with TailwindCSS v3
-- [wails-sveltekit-template](https://github.com/h8gi/wails-sveltekit-template) - A template using SvelteKit
-
-## Elm
-
-- [wails-elm-template](https://github.com/benjamin-thomas/wails-elm-template) - Develop your GUI app with functional programming and a **snappy** hot-reload setup :tada: :rocket:
-
-## Pure JavaScript (Vanilla)
-
-- [wails-pure-js-template](https://github.com/KiddoV/wails-pure-js-template) - A template with nothing but just basic JavaScript, HTML, and CSS
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/gettingstarted/building.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/gettingstarted/building.mdx
deleted file mode 100644
index a1f69f033..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/gettingstarted/building.mdx
+++ /dev/null
@@ -1,22 +0,0 @@
----
-sidebar_position: 6
----
-
-# Compiling your Project
-
-From the project directory, run `wails build`. This will compile your project and save the production-ready binary in the `build/bin` directory.
-
-If you run the binary, you should see the default application:
-
-```mdx-code-block
-
-
-
-
-```
-
-For more details on compilation options, please refer to the [CLI Reference](../reference/cli.mdx#build).
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/gettingstarted/development.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/gettingstarted/development.mdx
deleted file mode 100644
index a0075ef69..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/gettingstarted/development.mdx
+++ /dev/null
@@ -1,16 +0,0 @@
----
-sidebar_position: 5
----
-
-# Developing your Application
-
-You can run your application in development mode by running `wails dev` from your project directory. This will do the following things:
-
-- Build your application and run it
-- Bind your Go code to the frontend so it can be called from Javascript
-- Using the power of [Vite](https://vitejs.dev/), will watch for modifications in your Go files and rebuild/re-run on change
-- Sets up a [webserver](http://localhost:34115) that will serve your application over a browser. This allows you to use your favourite browser extensions. You can even call your Go code from the console
-
-To get started, run `wails dev` in the project directory. More information on this can be found [here](../reference/cli.mdx#dev).
-
-Coming soon: Tutorial
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/gettingstarted/firstproject.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/gettingstarted/firstproject.mdx
deleted file mode 100644
index 3428906ef..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/gettingstarted/firstproject.mdx
+++ /dev/null
@@ -1,130 +0,0 @@
----
-sidebar_position: 2
----
-
-# Creating a Project
-
-## Project Generation
-
-Now that the CLI is installed, you can generate a new project by using the `wails init` command.
-
-Pick your favourite framework:
-
-```mdx-code-block
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-
-
-
- Generate a Svelte project using Javascript with:
-
- wails init -n myproject -t svelte
-
-If you would rather use Typescript:
-
- wails init -n myproject -t svelte-ts
-
-
-
- Generate a React project using Javascript with:
-
- wails init -n myproject -t react
-
-If you would rather use Typescript:
-
- wails init -n myproject -t react-ts
-
-
-
- Generate a Vue project using Javascript with:
-
- wails init -n myproject -t vue
-
-If you would rather use Typescript:
-
- wails init -n myproject -t vue-ts
-
-
-
- Generate a Preact project using Javascript with:
-
- wails init -n myproject -t preact
-
-If you would rather use Typescript:
-
- wails init -n myproject -t preact-ts
-
-
-
- Generate a Lit project using Javascript with:
-
- wails init -n myproject -t lit
-
-If you would rather use Typescript:
-
- wails init -n myproject -t lit-ts
-
-
-
- Generate a Vanilla project using Javascript with:
-
- wails init -n myproject -t vanilla
-
-If you would rather use Typescript:
-
- wails init -n myproject -t vanilla-ts
-
-
-
-```
-
-
-
-There are also [community templates](../community/templates.mdx) available that offer different capabilities and frameworks.
-
-To see the other options available, you can run `wails init -help`. More details can be found in the [CLI Reference](../reference/cli.mdx#init).
-
-## Project Layout
-
-Wails projects have the following layout:
-
-```
-.
-├── build/
-│ ├── appicon.png
-│ ├── darwin/
-│ └── windows/
-├── frontend/
-├── go.mod
-├── go.sum
-├── main.go
-└── wails.json
-```
-
-### Project structure rundown
-
-- `/main.go` - The main application
-- `/frontend/` - Frontend project files
-- `/build/` - Project build directory
-- `/build/appicon.png` - The application icon
-- `/build/darwin/` - Mac specific project files
-- `/build/windows/` - Windows specific project files
-- `/wails.json` - The project configuration
-- `/go.mod` - Go module file
-- `/go.sum` - Go module checksum file
-
-The `frontend` directory has nothing specific to Wails and can be any frontend project of your choosing.
-
-The `build` directory is used during the build process. These files may be updated to customise your builds. If files are removed from the build directory, default versions will be regenerated.
-
-The default module name in `go.mod` is "changeme". You should change this to something more appropriate.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/gettingstarted/installation.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/gettingstarted/installation.mdx
deleted file mode 100644
index 858100bbe..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/gettingstarted/installation.mdx
+++ /dev/null
@@ -1,79 +0,0 @@
----
-sidebar_position: 1
----
-
-# Installation
-
-## Supported Platforms
-
-- Windows 10/11 AMD64/ARM64
-- MacOS 10.13+ AMD64
-- MacOS 11.0+ ARM64
-- Linux AMD64/ARM64
-
-## Dependencies
-
-Wails has a number of common dependencies that are required before installation:
-
-- Go 1.18+
-- NPM (Node 15+)
-
-### Go
-
-Download Go from the [Go Downloads Page](https://go.dev/dl/).
-
-Ensure that you follow the official [Go installation instructions](https://go.dev/doc/install). You will also need to ensure that your `PATH` environment variable also includes the path to your `~/go/bin` directory. Restart your terminal and do the following checks:
-
-- Check Go is installed correctly: `go version`
-- Check "~/go/bin" is in your PATH variable: `echo $PATH | grep go/bin`
-
-### NPM
-
-Download NPM from the [Node Downloads Page](https://nodejs.org/en/download/). It is best to use the latest release as that is what we generally test against.
-
-Run `npm --version` to verify.
-
-## Platform Specific Dependencies
-
-You will also need to install platform specific dependencies:
-
-```mdx-code-block
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-
-
-
- Wails requires that the xcode command line tools are installed. This can be
- done by running xcode-select --install.
-
-
- Wails requires that the WebView2 runtime is installed. Some Windows installations will already have this installed. You can check using the wails doctor command.
-
-
- Linux required the standard gcc build tools plus libgtk3 and libwebkit. Rather than list a ton of commands for different distros, Wails can try to determine what the installation commands are for your specific distribution. Run wails doctor after installation to be shown how to install the dependencies. If your distro/package manager is not supported, please consult the Add Linux Distro guide.
-
-
-```
-
-## Optional Dependencies
-
-- [UPX](https://upx.github.io/) for compressing your applications.
-
-## Installing Wails
-
-Run `go install github.com/wailsapp/wails/v2/cmd/wails@latest` to install the Wails CLI.
-
-## System Check
-
-Running `wails doctor` will check if you have the correct dependencies installed. If not, it will advise on what is missing and help on how to rectify any problems.
-
-## The `wails` command appears to be missing?
-
-If your system is reporting that the `wails` command is missing, make sure you have followed the Go installation guide correctly. Normally, it means that the `go/bin` directory in your User's home directory is not in the `PATH` environment variable. You will also normally need to close and reopen any open command prompts so that changes to the environment made by the installer are reflected at the command prompt.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/guides/application-development.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/guides/application-development.mdx
deleted file mode 100644
index a618076f1..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/guides/application-development.mdx
+++ /dev/null
@@ -1,194 +0,0 @@
-# Application Development
-
-There are no hard and fast rules for developing applications with Wails, but there are some basic guidelines.
-
-## Application Setup
-
-The pattern used by the default templates are that `main.go` is used for configuring and running the application, whilst `app.go` is used for defining the application logic.
-
-The `app.go` file will define a struct that has 2 methods which act as hooks into the main application:
-
-```go title="app.go"
-type App struct {
- ctx context.Context
-}
-
-func NewApp() *App {
- return &App{}
-}
-
-func (a *App) startup(ctx context.Context) {
- a.ctx = ctx
-}
-
-func (a *App) shutdown(ctx context.Context) {
-}
-```
-
-- The startup method is called as soon as Wails allocates the resources it needs and is a good place for creating resources, setting up event listeners and anything else the application needs at startup. It is given a `context.Context` which is usually saved in a struct field. This context is needed for calling the [runtime](../reference/runtime/intro.mdx). If this method returns an error, the application will terminate. In dev mode, the error will be output to the console.
-
-- The shutdown method will be called by Wails right at the end of the shutdown process. This is a good place to deallocate memory and perform any shutdown tasks.
-
-The `main.go` file generally consists of a single call to `wails.Run()`, which accepts the application configuration. The pattern used by the templates is that before the call to `wails.Run()`, an instance of the struct we defined in `app.go` is created and saved in a variable called `app`. This configuration is where we add our callbacks:
-
-```go {3,9,10} title="main.go"
-func main() {
-
- app := NewApp()
-
- err := wails.Run(&options.App{
- Title: "My App",
- Width: 800,
- Height: 600,
- OnStartup: app.startup,
- OnShutdown: app.shutdown,
- })
- if err != nil {
- log.Fatal(err)
- }
-}
-
-```
-
-More information on application lifecycle hooks can be found [here](../howdoesitwork.mdx#application-lifecycle-callbacks).
-
-## Binding Methods
-
-It is likely that you will want to call Go methods from the frontend. This is normally done by adding public methods to the already defined struct in `app.go`:
-
-```go {16-18} title="app.go"
-type App struct {
- ctx context.Context
-}
-
-func NewApp() *App {
- return &App{}
-}
-
-func (a *App) startup(ctx context.Context) {
- a.ctx = ctx
-}
-
-func (a *App) shutdown(ctx context.Context) {
-}
-
-func (a *App) Greet(name string) string {
- return fmt.Sprintf("Hello %s!", name)
-}
-```
-
-In the main application configuration, the `Bind` key is where we can tell Wails what we want to bind:
-
-```go {11-13} title="main.go"
-func main() {
-
- app := NewApp()
-
- err := wails.Run(&options.App{
- Title: "My App",
- Width: 800,
- Height: 600,
- OnStartup: app.startup,
- OnShutdown: app.shutdown,
- Bind: []interface{}{
- app,
- },
- })
- if err != nil {
- log.Fatal(err)
- }
-}
-
-```
-
-This will bind all public methods in our `App` struct (it will never bind the startup and shutdown methods).
-
-### Dealing with context when binding multiple structs
-
-If you want to bind methods for multiple structs but want each struct to keep a reference to the context so that you can use the runtime functions, a good pattern is to pass the context from the `OnStartup` method to your struct instances :
-
-```go
-func main() {
-
- app := NewApp()
- otherStruct := NewOtherStruct()
-
- err := wails.Run(&options.App{
- Title: "My App",
- Width: 800,
- Height: 600,
- OnStartup: func(ctx context.Context){
- app.SetContext(ctx)
- otherStruct.SetContext(ctx)
- },
- OnShutdown: app.shutdown,
- Bind: []interface{}{
- app,
- otherStruct
- },
- })
- if err != nil {
- log.Fatal(err)
- }
-}
-```
-
-More information on Binding can be found [here](../howdoesitwork.mdx#method-binding).
-
-## Application Menu
-
-Wails supports adding a menu to your application. This is done by passing a [Menu](../reference/menus.mdx#menu) struct to application config. It's common to use a method that returns a Menu, and even more common for that to be a method on the `App` struct used for the lifecycle hooks.
-
-```go {11} title="main.go"
-func main() {
-
- app := NewApp()
-
- err := wails.Run(&options.App{
- Title: "My App",
- Width: 800,
- Height: 600,
- OnStartup: app.startup,
- OnShutdown: app.shutdown,
- Menu: app.menu(),
- Bind: []interface{}{
- app,
- },
- })
- if err != nil {
- log.Fatal(err)
- }
-}
-
-```
-
-## Assets
-
-The great thing about the way Wails v2 handles assets is that it doesn't! The only thing you need to give Wails is an `embed.FS`. How you get to that is entirely up to you. You can use vanilla html/css/js files like the vanilla template. You could have some complicated build system, it doesn't matter.
-
-When `wails build` is run, it will check the `wails.json` project file at the project root. There are 2 keys in the project file that are read:
-
-- "frontend:install"
-- "frontend:build"
-
-The first, if given, will be executed in the `frontend` directory to install the node modules. The second, if given, will be executed in the `frontend` directory to build the frontend project.
-
-If these 2 keys aren't given, then Wails does absolutely nothing with the frontend. It is only expecting that `embed.FS`.
-
-### AssetsHandler
-
-A Wails v2 app can optionally define a `http.Handler` in the `options.App`, which allows hooking into the AssetServer to create files on the fly or process POST/PUT requests. GET requests are always first handled by the `assets` FS. If the FS doesn't find the requested file the request will be forwarded to the `http.Handler` for serving. Any requests other than GET will be directly processed by the `AssetsHandler` if specified. It's also possible to only use the `AssetsHandler` by specifiy `nil` as the `Assets` option.
-
-## Built in Dev Server
-
-Running `wails dev` will start the built in dev server which will start a file watcher in your project directory. By default, if any file changes, wails checks if it was an application file (default: `.go`, configurable with `-e` flag). If it was, then it will rebuild your application and relaunch it. If the changed file was in the assets, it will issue a reload after a short amount of time.
-
-The dev server uses a technique called "debouncing" which means it doesn't reload straight away, as there may be multiple files changed in a short amount of time. When a trigger occurs, it waits for a set amount of time before issuing a reload. If another trigger happens, it resets to the wait time again. By default this value is `100ms`. If this value doesn't work for your project, it can be configured using the `-debounce` flag. If used, this value will be saved to your project config and become the default.
-
-## External Dev Server
-
-Some frameworks come with their own live-reloading server, however they will not be able to take advantage of the Wails Go bindings. In this scenario, it is best to run a watcher script that rebuilds the project into the build directory, which Wails will be watching. For an example, see the default svelte template that uses [rollup](https://rollupjs.org/guide/en/). For [create-react-app](https://create-react-app.dev/), it's possible to use [this script](https://gist.github.com/int128/e0cdec598c5b3db728ff35758abdbafd) to achieve a similar result.
-
-## Go Module
-
-The default Wails templates generate a `go.mod` file that contains the module name "changeme". You should change this to something more appropriate after project generation.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/guides/bleeding-edge.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/guides/bleeding-edge.mdx
deleted file mode 100644
index b81cc79dc..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/guides/bleeding-edge.mdx
+++ /dev/null
@@ -1,55 +0,0 @@
-# Bleeding Edge
-
-## Overview
-
-Wails is in constant development and new releases are regularly "tagged". This usually happens when all the newer code on `master` has been tested and confirmed working. If you need a bugfix or feature that has not yet made it to a release, it's possible to use the latest "bleeding edge" version using the following steps:
-
-- `git clone https://github.com/wailsapp/wails`
-- `cd wails/v2/cmd/wails`
-- `go install`
-
-NOTE: The directory that you cloned the project into will now be called "clonedir".
-
-The Wails CLI will now be at the very latest version.
-
-### Updating your project
-
-To update projects to use the latest version of the Wails library, update the project's `go.mod` and ensure the following line is at the bottom of the file:
-
-`replace github.com/wailsapp/wails/v2 => `
-
-Example:
-
-On Windows: `replace github.com/wailsapp/wails/v2 => C:\Users\leaan\Documents\wails-v2-beta\wails\v2`
-
-On 'nix: `replace github.com/wailsapp/wails/v2 => /home/me/projects/wails/v2`
-
-To revert to a stable version, run:
-
-`go install github.com/wailsapp/wails/v2/cmd/wails@latest`
-
-## Testing a Branch
-
-If you want to test a branch, follow the instructions above, but ensure you switch the branch you want to test before installing:
-
-- `git clone https://github.com/wailsapp/wails`
-- `cd wails`
-- `git checkout -b branch-to-test --track origin/branch-to-test`
-- `cd v2/cmd/wails`
-- `go install`
-
-Make sure you [update your project](#updating-your-project) as described above.
-
-## Testing a PR
-
-If you want to test a PR, follow the instructions above, but ensure you fetch the PR and switch the branch before installing. Please replace `[IDofThePR]` with the ID of the PR shown on github.com:
-
-- `git clone https://github.com/wailsapp/wails`
-- `cd wails`
-- `git fetch -u origin pull/[IDofThePR]/head:test/pr-[IDofThePR]`
-- `git checkout test/pr-[IDofThePR]`
-- `git reset --hard HEAD`
-- `cd v2/cmd/wails`
-- `go install`
-
-Make sure you [update your project](#updating-your-project) as described above.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/guides/dynamic-assets.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/guides/dynamic-assets.mdx
deleted file mode 100644
index 40a779381..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/guides/dynamic-assets.mdx
+++ /dev/null
@@ -1,134 +0,0 @@
-# Dynamic Assets
-
-If you want to load or generate assets for your frontend dynamically, you can achieve that using the [AssetsHandler](../reference/options#assetshandler) option. The AssetsHandler is a generic `http.Handler` which will be called for any non GET request on the assets server and for GET requests which can not be served from the bundled assets because the file is not found.
-
-By installing a custom AssetsHandler, you can serve your own assets using a custom asset server.
-
-## Example
-
-In our example project, we will create a simple assets handler which will load files off disk:
-
-```go title=main.go {16-35,49}
-package main
-
-import (
- "embed"
- "fmt"
- "github.com/wailsapp/wails/v2"
- "github.com/wailsapp/wails/v2/pkg/options"
- "net/http"
- "os"
- "strings"
-)
-
-//go:embed all:frontend/dist
-var assets embed.FS
-
-type FileLoader struct {
- http.Handler
-}
-
-func NewFileLoader() *FileLoader {
- return &FileLoader{}
-}
-
-func (h *FileLoader) ServeHTTP(res http.ResponseWriter, req *http.Request) {
- var err error
- requestedFilename := strings.TrimPrefix(req.URL.Path, "/")
- println("Requesting file:", requestedFilename)
- fileData, err := os.ReadFile(requestedFilename)
- if err != nil {
- res.WriteHeader(http.StatusBadRequest)
- res.Write([]byte(fmt.Sprintf("Could not load file %s", requestedFilename)))
- }
-
- res.Write(fileData)
-}
-
-func main() {
- // Create an instance of the app structure
- app := NewApp()
-
- // Create application with options
- err := wails.Run(&options.App{
- Title: "helloworld",
- Width: 1024,
- Height: 768,
- Assets: assets,
- BackgroundColour: &options.RGBA{R: 27, G: 38, B: 54, A: 255},
- OnStartup: app.startup,
- AssetsHandler: NewFileLoader(),
- Bind: []interface{}{
- app,
- },
- })
-
- if err != nil {
- println("Error:", err)
- }
-}
-```
-
-When we run the application in dev mode using `wails dev`, we will see the following output:
-
-```
-DEB | [ExternalAssetHandler] Loading 'http://localhost:3001/favicon.ico'
-DEB | [ExternalAssetHandler] Loading 'http://localhost:3001/favicon.ico' failed, using AssetHandler
-Requesting file: favicon.ico
-```
-
-As you can see, the assets handler is called when the default assets server is unable to serve the `favicon.ico` file.
-
-If you right click the main application and select "inspect" to bring up the devtools, you can test this feature out by typing the following into the console:
-
-```
-let response = await fetch('does-not-exist.txt');
-```
-
-This will generate an error in the devtools. We can see that the error is what we expect, returned by our custom assets handler:
-
-```mdx-code-block
-
-
-
-```
-
-However, if we request `go.mod`, we will see the following output:
-
-```mdx-code-block
-
-
-
-```
-
-This technique can be used to load images directly into the page. If we updated our default vanilla template and replaced the logo image:
-
-```html
-
-```
-
-with:
-
-```html
-
-```
-
-Then we would see the following:
-
-```mdx-code-block
-
-
-
-```
-
-:::warning
-
-
-Exposing your filesystem in this way is a security risk. It is recommended that you properly manage access to your filesystem.
-
-:::
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/guides/frameless.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/guides/frameless.mdx
deleted file mode 100644
index a9370f36f..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/guides/frameless.mdx
+++ /dev/null
@@ -1,85 +0,0 @@
-# Frameless Applications
-
-Wails supports application that have no frames. This can be achieved by using the [frameless](../reference/options.mdx#frameless) field in [Application Options](../reference/options.mdx#application-options).
-
-Wails offers a simple solution for dragging the window: Any HTML element that has the CSS style `--wails-draggable:drag` will act as a "drag handle". This property applies to all child elements. If you need to indicate that a nested element should not drag, then use the attribute '--wails-draggable:no-drag' on that element.
-
-```html
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-```
-
-For some projects, using a CSS variable may not be possible due to dynamic styling. In this case, you can use the `CSSDragProperty` and `CSSDragValue` application options to define a property and value that will be used to indicate draggable regions:
-
-```go title=main.go
-package main
-
-import (
- "embed"
-
- "github.com/wailsapp/wails/v2"
- "github.com/wailsapp/wails/v2/pkg/options"
-)
-
-//go:embed all:frontend/dist
-var assets embed.FS
-
-func main() {
- // Create an instance of the app structure
- app := NewApp()
-
- // Create application with options
- err := wails.Run(&options.App{
- Title: "alwaysontop",
- Width: 1024,
- Height: 768,
- Assets: assets,
- Frameless: true,
- CSSDragProperty: "widows",
- CSSDragValue: "1",
- Bind: []interface{}{
- app,
- },
- })
-
- if err != nil {
- println("Error:", err)
- }
-}
-```
-
-```html title=index.html
-
-
-
-
-
- alwaysontop
-
-
-
-
-
-
-```
-
-:::info Fullscreen
-
-
-If you allow your application to go fullscreen, this drag functionality will be disabled.
-
-:::
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/guides/frontend.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/guides/frontend.mdx
deleted file mode 100644
index 4b192c557..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/guides/frontend.mdx
+++ /dev/null
@@ -1,75 +0,0 @@
-# Frontend
-
-## Script Injection
-
-When Wails serves your `index.html`, by default, it will inject 2 script entries into the `` tag to load `/wails/ipc.js` and `/wails/runtime.js`. These files install the bindings and runtime respectively.
-
-The code below shows where these are injected by default:
-
-```html
-
-
- injection example
-
-
-
-
-
-
-
-
Please enter your name below 👇
-
-
-
-
-
-
-
-
-
-```
-
-### Overriding Default Script Injection
-
-To provide more flexibility to developers, there is a meta tag that may be used to customise this behaviour:
-
-```html
-
-```
-
-The options are as follows:
-
-| Value | Description |
-| ------------------- | ------------------------------------------------ |
-| noautoinjectruntime | Disable the autoinjection of `/wails/runtime.js` |
-| noautoinjectipc | Disable the autoinjection of `/wails/ipc.js` |
-| noautoinject | Disable all autoinjection of scripts |
-
-Multiple options may be used provided they are comma seperated.
-
-This code is perfectly valid and operates the same as the autoinjection version:
-
-```html
-
-
-
- injection example
-
-
-
-
-
-
-
Please enter your name below 👇
-
-
-
-
-
-
-
-
-
-
-
-```
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/guides/ides.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/guides/ides.mdx
deleted file mode 100644
index 5187065ad..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/guides/ides.mdx
+++ /dev/null
@@ -1,116 +0,0 @@
-# IDEs
-
-Wails aims to provide a great development experience. To that aim, we now support generating IDE specific configuration to provide smoother project setup.
-
-Currently, we support [Visual Studio Code](https://code.visualstudio.com/) but aim to support other IDEs such as Goland.
-
-## Visual Studio Code
-
-```mdx-code-block
-
-
-
-```
-
-When generating a project using the `-ide vscode` flags, IDE files will be created alongside the other project files. These files are placed into the `.vscode` directory and provide the correct configuration for debugging your application.
-
-The 2 files generated are `tasks.json` and `launch.json`. Below are the files generated for the default vanilla project:
-
-```json title="tasks.json"
-{
- "version": "2.0.0",
- "tasks": [
- {
- "label": "build",
- "type": "shell",
- "options": {
- "cwd": "${workspaceFolder}"
- },
- "command": "go",
- "args": ["build", "-tags", "dev", "-gcflags", "all=-N -l", "-o", "build/bin/myproject.exe"]
- },
- ]
-}
-```
-
-```json title="launch.json"
-{
- "version": "0.2.0",
- "configurations": [
- {
- "name": "Wails: Debug myproject",
- "type": "go",
- "request": "launch",
- "mode": "exec",
- "program": "${workspaceFolder}/build/bin/myproject.exe",
- "preLaunchTask": "build",
- "cwd": "${workspaceFolder}",
- "env": {}
- },
- ]
-}
-```
-
-### Configuring the install and build steps
-
-The `tasks.json` file is simple for the default project as there is no `npm install` or `npm run build` step needed. For projects that have a frontend build step, such as the svelte template, we would need to edit `tasks.json` to add the install and build steps:
-
-```json title="tasks.json"
-{
- "version": "2.0.0",
- "tasks": [
- {
- "label": "npm install",
- "type": "npm",
- "script": "install",
- "options": {
- "cwd": "${workspaceFolder}/frontend"
- },
- "presentation": {
- "clear": true,
- "panel": "shared",
- "showReuseMessage": false
- },
- "problemMatcher": []
- },
- {
- "label": "npm run build",
- "type": "npm",
- "script": "build",
- "options": {
- "cwd": "${workspaceFolder}/frontend"
- },
- "presentation": {
- "clear": true,
- "panel": "shared",
- "showReuseMessage": false
- },
- "problemMatcher": []
- },
- {
- "label": "build",
- "type": "shell",
- "options": {
- "cwd": "${workspaceFolder}"
- },
- "command": "go",
- "args": ["build", "-tags", "dev", "-gcflags", "all=-N -l", "-o", "build/bin/vscode.exe"],
- "dependsOn":[
- "npm install",
- "npm run build"
- ]
-
- },
- ]
-}
-```
-
-:::info Future Enhancement
-
-
-In the future, we hope to generate a `tasks.json` that includes the install and build steps automatically.
-
-:::
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/guides/linux-distro-support.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/guides/linux-distro-support.mdx
deleted file mode 100644
index 882f8d258..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/guides/linux-distro-support.mdx
+++ /dev/null
@@ -1,104 +0,0 @@
-# Linux Distro Support
-
-## Overview
-
-Wails offers Linux support but providing installation instructions for all available distributions is an impossible task. Instead, Wails tries to determine if the packages you need to develop applications are available via your system's package manager. Currently, we support the following package managers:
-
-- apt
-- dnf
-- emerge
-- eopkg
-- nixpkgs
-- pacman
-- zypper
-
-## Adding package names
-
-There may be circumstances where your distro uses one of the supported package managers but the package name is different. For example, you may use an Ubuntu derivative, but the package name for gtk may be different. Wails attempts to find the correct package by iterating through a list of package names. The list of packages are stored in the packagemanager specific file in the `v2/internal/system/packagemanager` directory. In our example, this would be `v2/internal/system/packagemanager/apt.go`.
-
-In this file, the list of packages are defined by the `Packages()` method:
-
-```go
-func (a *Apt) Packages() packagemap {
- return packagemap{
- "libgtk-3": []*Package{
- {Name: "libgtk-3-dev", SystemPackage: true, Library: true},
- },
- "libwebkit": []*Package{
- {Name: "libwebkit2gtk-4.0-dev", SystemPackage: true, Library: true},
- },
- "gcc": []*Package{
- {Name: "build-essential", SystemPackage: true},
- },
- "pkg-config": []*Package{
- {Name: "pkg-config", SystemPackage: true},
- },
- "npm": []*Package{
- {Name: "npm", SystemPackage: true},
- },
- "docker": []*Package{
- {Name: "docker.io", SystemPackage: true, Optional: true},
- },
- }
-}
-```
-
-Let's assume that in our linux distro, `libgtk-3` is packaged under the name `lib-gtk3-dev`. We could add support for this by adding the following line:
-
-```go {5}
-func (a *Apt) Packages() packagemap {
- return packagemap{
- "libgtk-3": []*Package{
- {Name: "libgtk-3-dev", SystemPackage: true, Library: true},
- {Name: "lib-gtk3-dev", SystemPackage: true, Library: true},
- },
- "libwebkit": []*Package{
- {Name: "libwebkit2gtk-4.0-dev", SystemPackage: true, Library: true},
- },
- "gcc": []*Package{
- {Name: "build-essential", SystemPackage: true},
- },
- "pkg-config": []*Package{
- {Name: "pkg-config", SystemPackage: true},
- },
- "npm": []*Package{
- {Name: "npm", SystemPackage: true},
- },
- "docker": []*Package{
- {Name: "docker.io", SystemPackage: true, Optional: true},
- },
- }
-}
-```
-
-## Adding new package managers
-
-To add a new package manager, perform the following steps:
-
-- Create a new file in `v2/internal/system/packagemanager` called `.go`, where `` is the name of the package manager.
-- Define a struct that conforms to the package manager interface defined in `pm.go`:
-
-```go
-type PackageManager interface {
- Name() string
- Packages() packagemap
- PackageInstalled(*Package) (bool, error)
- PackageAvailable(*Package) (bool, error)
- InstallCommand(*Package) string
-}
-```
-
-- `Name()` should return the name of the package manager
-- `Packages()` should return a `packagemap`, that provides candidate filenames for dependencies
-- `PackageInstalled()` should return `true` if the given package is installed
-- `PackageAvailable()` should return `true` if the given package is not installed but available for installation
-- `InstallCommand()` should return the exact command to install the given package name
-
-Take a look at the other package managers code to get an idea how this works.
-
-:::info Remember
-
-
-If you add support for a new package manager, don't forget to also update this page!
-
-:::
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/guides/migrating.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/guides/migrating.mdx
deleted file mode 100644
index 55b791e61..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/guides/migrating.mdx
+++ /dev/null
@@ -1,187 +0,0 @@
-# Migrating from v1
-
-## Overview
-
-Wails v2 is a significant change from v1. This document aims to highlight the changes and the steps in migrating an existing project.
-
-### Creating the Application
-
-In v1, the main application is created using `wails.CreateApp`, bindings are added with `app.Bind`, then the application is run using `app.Run()`.
-
-Example:
-
-```go title="v1"
- app := wails.CreateApp(&wails.AppConfig{
- Title: "MyApp",
- Width: 1024,
- Height: 768,
- JS: js,
- CSS: css,
- Colour: "#131313",
- })
- app.Bind(basic)
- app.Run()
-```
-
-In v2, there is just a single method, `wails.Run()`, that accepts [application options](../reference/options.mdx#application-options).
-
-```go title="v2"
- err := wails.Run(&options.App{
- Title: "MyApp",
- Width: 800,
- Height: 600,
- Assets: assets,
- Bind: []interface{}{
- basic,
- },
- })
-```
-
-### Binding
-
-In v1, it was possible to bind both arbitrary functions and structs. In v2, this has been simplified to only binding structs. The struct instances that were previously passed to the `Bind()` method in v1, are now specified in the `Bind` field of the [application options](../reference/options.mdx#application-options):
-
-```go title="v1"
- app := wails.CreateApp(/* options */)
- app.Bind(basic)
-```
-
-```go title="v2"
- err := wails.Run(&options.App{
- /* other options */
- Bind: []interface{}{
- basic,
- },
- })
-```
-
-In v1, bound methods were available to the frontend at `window.backend`. This has changed to `window.go`.``
-
-### Application Lifecycle
-
-In v1, there were 2 special methods in a bound struct: `WailsInit()` and `WailsShutdown()`. These have been replaced with 3 lifecycle hooks as part of the [application options](../reference/options.mdx#application-options):
-
-- [OnStartup](../reference/options.mdx#onstartup)
-- [OnShutdown](../reference/options.mdx#onshutdown)
-- [OnDomReady](../reference/options.mdx#ondomready)
-
-Note: [OnDomReady](../reference/options.mdx#ondomready) replaces the `wails:ready` system event in v1.
-
-These methods can be standard functions, but a common practice is to have them part of a struct:
-
-```go title="v2"
- basic := NewBasicApp()
- err := wails.Run(&options.App{
- /* Other Options */
- OnStartup: basic.startup,
- OnShutdown: basic.shutdown,
- OnDomReady: basic.domready,
- })
-...
-type Basic struct {
- ctx context.Context
-}
-func (b *Basic) startup(ctx context.Context) {
- b.ctx = ctx
-}
-...
-```
-
-### Runtime
-
-The runtime in v2 is much richer than v1 with support for menus, window manipulation and better dialogs. The signature of the methods has changed slightly - please refer the the [Runtime Reference](../reference/runtime/intro.mdx).
-
-In v1, the [runtime](../reference/runtime/intro.mdx) was available via a struct passed to `WailsInit()`. In v2, the runtime has been moved out to its own package. Each method in the runtime takes the `context.Context` that is passed to the [OnStartup](../reference/options.mdx#onstartup) method.
-
-```go title="Runtime Example"
-package main
-
-import "github.com/wailsapp/wails/v2/pkg/runtime"
-
-type Basic struct {
- ctx context.Context
-}
-
-// startup is called at application startup
-func (a *App) startup(ctx context.Context) {
- a.ctx = ctx
- runtime.LogInfo(ctx, "Application Startup called!")
-}
-
-```
-
-### Assets
-
-The _biggest_ change in v2 is how assets are handled.
-
-In v1, assets were passed via 2 application options:
-
-- `JS` - The application's Javascript
-- `CSS` - The application's CSS
-
-This meant that the responsibility of generating a single JS and CSS file was on the developer. This essentially required the use of complicated packers such as webpack.
-
-In v2, Wails makes no assumptions about your frontend assets, just like a webserver. All of your application assets are passed to the application options as an `embed.FS`.
-
-**This means there is no requirement to bundle your assets, encode images as Base64 or attempt the dark art of bundler configuration to use custom fonts**.
-
-At startup, Wails will scan the given `embed.FS` for `index.html` and use its location as the root path for all the other application assets - just like a webserver would.
-
-Example: An application has the following project layout. All final assets are placed in the `frontend/dist` directory:
-
-```shell
-.
-├── build/
-├── frontend/
-│ └── dist/
-│ ├── index.html
-│ ├── main.js
-│ ├── main.css
-│ └── logo.svg
-├── main.go
-└── wails.json
-```
-
-Those assets may be used by the application by simply creating an `embed.FS`:
-
-```go title="Assets Example"
-//go:embed all:frontend/dist
-var assets embed.FS
-
-func main() {
- err := wails.Run(&options.App{
- /* Other Options */
- Assets: assets,
- })
-}
-```
-
-Of course, bundlers can be used if you wish to. The only requirement is to pass the final application assets directory to Wails using an `embed.FS` in the `Assets` key of the [application options](../reference/options.mdx#application-options).
-
-### Project Configuration
-
-In v1, the project configuration was stored in the `project.json` file in the project root. In v2, the project configuration is stored in the `wails.json` file in the project root.
-
-The format of the file is slightly different. Here is a comparison:
-
-
-
-| v1 | v2 | Notes |
-| ------------------ | ---------------- | --------------------------------------------------- |
-| name | name | |
-| description | | Removed |
-| author / name | author / name | |
-| author / email | author / email | |
-| version | version | |
-| binaryname | outputfilename | Changed |
-| frontend / dir | | Removed |
-| frontend / install | frontend:install | Changed |
-| frontend / build | frontend:build | Changed |
-| frontend / bridge | | Removed |
-| frontend / serve | | Removed |
-| tags | | Removed |
-| | wailsjsdir | The directory to generate wailsjs modules |
-| | assetdir | The directory of the compiled frontend assets for `dev` mode. This is normally inferred and could be left empty. |
-| | reloaddirs | Comma separated list of additional directories to watch for changes and to trigger reloads in `dev` mode. This is only needed for some more advanced asset configurations. |
-
-
-```
-
-it's likely that your application's `info.plist` is invalid. Update the file in `build/.app/Contents/info.plist` and check if the data is valid, EG check the binary name is correct. To persist the changes, copy the file back to the `build/darwin` directory.
-
-## Cannot call backend method from frontend with variadic arguments
-
-If you have a backend method defined with variadic parameters, eg:
-
-```go
-func (a *App) TestFunc(msg string, args ...interface{}) error {
- // Code
-}
-```
-
-calling this method from the frontend like this will fail:
-
-```js
-var msg = "Hello: ";
-var args = ["Go", "JS"];
-window.go.main.App.TestFunc(msg, ...args)
- .then((result) => {
- //do things here
- })
- .catch((error) => {
- //handle error
- });
-```
-
-Workaround:
-
-```js
-var msg = "Hello ";
-var args = ["Go", "JS"];
-window.go.main.App.TestFunc(msg, args)
- .then((result) => {
- //without the 3 dots
- //do things here
- })
- .catch((error) => {
- //handle error
- });
-```
-
-Credit: https://github.com/wailsapp/wails/issues/1186
-
-## I'm having getting proxy errors when trying to install Wails
-
-If you are getting errors like this:
-
-```
-"https://proxy.golang.org/github.com/wailsapp/wails/cmd/wails/@v/list": dial tcp 172.217.163.49:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
-```
-
-it's probably because the official Go Proxy is being blocked (Users in China have reported this). The solution is to set up the proxy manually, eg:
-
-```
-go env -w GO111MODULE=on
-go env -w GOPROXY=https://goproxy.cn,direct
-```
-
-Source: https://github.com/wailsapp/wails/issues/1233
-
-## The generated Typescript doesn't have the correct types
-
-Sometimes the generated Typescript doesn't have the correct types. To mitigate this, it is possible to specify what types should be generated using the `ts_type` struct tag. For more details, please read [this](https://github.com/tkrajina/typescriptify-golang-structs#custom-types).
-
-## When I navigate away from `index.html`, I am unable to call methods on the frontend
-
-If you navigate away from `index.html` to a new html file, the context will be lost. This can be fixed by adding the following imports to the `` section of any new page you navigate to:
-
-```html
-
-
-
-
-```
-
-Source: https://github.com/wailsapp/wails/discussions/1512
-
-## I get `too many open files` errors on my Mac when I run `wails dev`
-
-By default, macOS will only allow you to open a maximum of 256 files. This can affect the `wails dev` command. This limit can be increased by running: `ulimit -n 1024` in the terminal.
-
-FSNotify is [looking to move to Apple's fsevents](https://github.com/fsnotify/fsnotify/issues/11) for Mac. If this isn't completed soon, we will create our own implementation, tracked [here](https://github.com/wailsapp/wails/issues/1733).
-
-## My Mac app gives me weird compilation errors
-
-A few users have reported seeing compilation errors such as the following:
-
-```shell
-# github.com/wailsapp/wails/v2/internal/frontend/desktop/darwin
-In file included from ../../pkg/mod/github.com/wailsapp/wails/v2@v2.0.0-beta.44.2/internal/frontend/desktop/darwin/callbacks.go:9:
-In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX12.1.sdk/System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:12:
-/Library/Developer/CommandLineTools/SDKs/MacOSX12.1.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSBundle.h:91:143: error: function does not return NSString
-- (NSAttributedString *)localizedAttributedStringForKey:(NSString *)key value:(nullable NSString *)value table:(nullable NSString *)tableName NS_FORMAT_ARGUMENT(1) NS_REFINED_FOR_SWIFT API_AVAILABLE(macos(12.0), ios(15.0), watchos(8.0), tvos(15.0));
- ~~~~~~~~~~~~~~ ^ ~
-/Library/Developer/CommandLineTools/SDKs/MacOSX12.1.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSObjCRuntime.h:103:48: note: expanded from macro 'NS_FORMAT_ARGUMENT'
- #define NS_FORMAT_ARGUMENT(A) __attribute__ ((format_arg(A)))
-```
-
-This is _normally_ due to a mismatch with the OS version you are running and the version of the XCode Command Line Tools installed. If you see an error like this, try upgrading your XCode Command Line Tools to the latest version.
-
-Source: https://github.com/wailsapp/wails/issues/1806
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/guides/windows-installer.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/guides/windows-installer.mdx
deleted file mode 100644
index b0b6e9e1f..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/guides/windows-installer.mdx
+++ /dev/null
@@ -1,58 +0,0 @@
-# NSIS installer
-
-```mdx-code-block
-
-
-
-
-```
-
-Wails supports generating Windows installers using the [NSIS installer](https://nsis.sourceforge.io/).
-
-## Installing NSIS
-
-### Windows
-
-The installer is available on the [NSIS Download](https://nsis.sourceforge.io/Download) page.
-
-If you use the chocolatey package manager, run the following script:
-
-```
-choco install nsis
-```
-
-If you install NSIS manually, you need to add the *Bin* folder, which contains `makensis.exe`, in your NSIS installation to your path. [Here](https://www.architectryan.com/2018/03/17/add-to-the-path-on-windows-10/) is a good tutorial on how to add to path on Windows.
-
-### Linux
-
-The `nsis` package should be available through your distribution's package manager.
-
-### MacOS
-
-NSIS is available to install through homebrew: `brew install nsis`.
-
-## Generating the installer
-
-When a new project is created, Wails generates the NSIS configuration files in `build/windows/installer`. The config data is read from `installer/info.json` and that is configured to use the project's `wails.json` Info section:
-
-```json
-// ...
- "Info": {
- "companyName": "My Company Name",
- "productName": "Wails Vite",
- "productVersion": "1.0.0",
- "copyright": "Copyright.........",
- "comments": "Built using Wails (https://wails.io)"
- },
-```
-
-To generate an installer for your application, use the `-nsis` flag with `wails build`:
-
-```
-wails build -nsis
-```
-
-The installer will now be available in the `build/bin` directory.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/howdoesitwork.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/howdoesitwork.mdx
deleted file mode 100644
index a0bde09e6..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/howdoesitwork.mdx
+++ /dev/null
@@ -1,364 +0,0 @@
----
-sidebar_position: 20
----
-
-# How does it work?
-
-A Wails application is a standard Go application, with a webkit frontend. The Go part of the application consists of the application code and a runtime library that provides a number of useful operations, like controlling the application window. The frontend is a webkit window that will display the frontend assets. Also available to the frontend is a Javascript version of the runtime library. Finally, it is possible to bind Go methods to the frontend, and these will appear as Javascript methods that can be called, just as if they were local Javascript methods.
-
-```mdx-code-block
-
-
-
-```
-
-## The Main Application
-
-### Overview
-
-The main application consists of a single call to `wails.Run()`. It accepts the application configuration which describes the size of the application window, the window title, what assets to use, etc. A basic application might look like this:
-
-```go title="main.go"
-package main
-
-import (
- "embed"
- "log"
-
- "github.com/wailsapp/wails/v2"
- "github.com/wailsapp/wails/v2/pkg/options"
-)
-
-//go:embed all:frontend/dist
-var assets embed.FS
-
-func main() {
-
- app := &App{}
-
- err := wails.Run(&options.App{
- Title: "Basic Demo",
- Width: 1024,
- Height: 768,
- Assets: &assets,
- OnStartup: app.startup,
- OnShutdown: app.shutdown,
- Bind: []interface{}{
- app,
- },
- })
- if err != nil {
- log.Fatal(err)
- }
-}
-
-
-type App struct {
- ctx context.Context
-}
-
-func (b *App) startup(ctx context.Context) {
- b.ctx = ctx
-}
-
-func (b *App) shutdown(ctx context.Context) {}
-
-func (b *App) Greet(name string) string {
- return fmt.Sprintf("Hello %s!", name)
-}
-```
-
-### Options rundown
-
-This example has the following options set:
-
-- `Title` - The text that should appear in the window's title bar
-- `Width` & `Height` - The dimensions of the window
-- `Assets` - The application's frontend assets
-- `OnStartup` - A callback for when the window is created and is about to start loading the frontend assets
-- `OnShutdown` - A callback for when the application is about to quit
-- `Bind` - A slice of struct instances that we wish to expose to the frontend
-
-A full list of application options can be found in the [Options Reference](reference/options).
-
-#### Assets
-
-The `Assets` option is mandatory as you can't have a Wails application without frontend assets. Those assets can be any files you would expect to find in a web application - html, js, css, svg, png, etc. **There is no requirement to generate asset bundles** - plain files will do. When the application starts, it will attempt to load `index.html` from your assets and the frontend will essentially work as a browser from that point on. It is worth noting that there is no requirement on where in the `embed.FS` the files live. It is likely that the embed path uses a nested directory relative to your main application code, such as `frontend/dist`:
-
-```go title="main.go"
-//go:embed all:frontend/dist
-var assets embed.FS
-```
-
-At startup, Wails will iterate the embedded files looking for the directory containing `index.html`. All other assets will be loaded relative to this directory.
-
-As production binaries use the files contained in `embed.FS`, there are no external files required to be shipped with the application.
-
-When running in development mode using the `wails dev` command, the assets are loaded off disk, and any changes result in a "live reload". The location of the assets will be inferred from the `embed.FS`.
-
-More details can be found in the [Application Development Guide](guides/application-development.mdx).
-
-#### Application Lifecycle Callbacks
-
-Just before the frontend is about to load `index.html`, a callback is made to the function provided in [OnStartup](reference/options.mdx#onstartup). A standard Go context is passed to this method. This context is required when calling the runtime so a standard pattern is to save a reference to in this method. Just before the application shuts down, the [OnShutdown](reference/options.mdx#onshutdown) callback is called in the same way, again with the context. There is also an [OnDomReady](reference/options.mdx#ondomready) callback for when the frontend has completed loading all assets in `index.html` and is equivalent of the [`body onload`](https://www.w3schools.com/jsref/event_onload.asp) event in Javascript. It is also possible to hook into the window close (or application quit) event by setting the option [OnBeforeClose](reference/options.mdx#onbeforeclose).
-
-#### Method Binding
-
-The `Bind` option is one of the most important options in a Wails application. It specifies which struct methods to expose to the frontend. Think of structs like "controllers" in a traditional web application. When the application starts, it examines the struct instances listed in the `Bind` field in the options, determines which methods are public (starts with an uppercase letter) and will generate Javascript versions of those methods that can be called by the frontend code.
-
-:::info Note
-
-
-Wailsで構造体を正しくバインドするためには、構造体の*インスタンス*をオプションで指定してください。
-
-:::
-
-
-In this example, we create a new `App` instance and then add this instance to the `Bind` option in `wails.Run`:
-
-```go {16,24} title="main.go"
-package main
-
-import (
- "embed"
- "log"
-
- "github.com/wailsapp/wails/v2"
- "github.com/wailsapp/wails/v2/pkg/options"
-)
-
-//go:embed all:frontend/dist
-var assets embed.FS
-
-func main() {
-
- app := &App{}
-
- err := wails.Run(&options.App{
- Title: "Basic Demo",
- Width: 1024,
- Height: 768,
- Assets: &assets,
- Bind: []interface{}{
- app,
- },
- })
- if err != nil {
- log.Fatal(err)
- }
-}
-
-
-type App struct {
- ctx context.Context
-}
-
-func (a *App) Greet(name string) string {
- return fmt.Sprintf("Hello %s!", name)
-}
-```
-
-You may bind as many structs as you like. Just make sure you create an instance of it and pass it in `Bind`:
-
-```go {8-10}
- //...
- err := wails.Run(&options.App{
- Title: "Basic Demo",
- Width: 1024,
- Height: 768,
- Assets: &assets,
- Bind: []interface{}{
- app,
- &mystruct1{},
- &mystruct2{},
- },
- })
-
-```
-
-When you run `wails dev` (or `wails generate module`), a frontend module will be generated containing the following:
-
-- Javascript bindings for all bound methods
-- Typescript declarations for all bound methods
-- Typescript definitions for all Go structs used as inputs or outputs by the bound methods
-
-This makes it incredibly simple to call Go code from the frontend, using the same strongly typed datastructures.
-
-## The Frontend
-
-### Overview
-
-The frontend is a collection of files rendered by webkit. It's like a browser and webserver in one. There is virtually[^1] no limit to which frameworks or libraries you can use. The main points of interaction between the frontend and your Go code are:
-
-- Calling bound Go methods
-- Calling runtime methods
-
-### Calling bound Go methods
-
-When you run your application with `wails dev`, it will automatically generate Javascript bindings for your structs in a directory called `wailsjs/go` (You can also do this by running `wails generate module`). The generated files mirror the package names in your application. In the example above, we bind `app`, which has one public method `Greet`. This will lead to the generation of the following files:
-
-```bash
-wailsjs
- └─go
- └─main
- ├─App.d.ts
- └─App.js
-```
-
-Here we can see that there is a `main` package that contains the Javascript bindings for the bound `App` struct, as well as the Typescript declaration file for those methods. To call `Greet` from our frontend, we simply import the method and call it like a regular Javascript function:
-
-```javascript
-// ...
-import {Greet} from '../wailsjs/go/main/App'
-
- function doGreeting(name) {
- Greet(name).then((result) => {
- // resultを使って何かする
- })
- }
-```
-
-The Typescript declaration file gives you the correct types for the bound methods:
-
-```ts
-export function Greet(arg1:string):Promise;
-```
-
-The generated methods return a Promise. A successful call will result in the first return value from the Go call to be passed to the `resolve` handler. An unsuccessful call is when a Go method that has an error type as it's second return value, passes an error instance back to the caller. This is passed back via the `reject` handler. In the example above, `Greet` only returns a `string` so the Javascript call will never reject - unless invalid data is passed to it.
-
-All data types are correctly translated between Go and Javascript. Even structs. If you return a struct from a Go call, it will be returned to your frontend as a Javascript class. Note: If you wish to use structs, you **must** define `json` struct tags for your fields!
-
-:::info Note
-
-
-Anonymous nested structs are not supported at this time.
-
-:::
-
-
-It is possible to send structs back to Go. Any Javascript map/class passed as an argument that is expecting a struct, will be converted to that struct type. To make this process a lot easier, in `dev` mode, a TypeScript module is generated, defining all the struct types used in bound methods. Using this module, it's possible to construct and send native Javascript objects to the Go code.
-
-There is also support for Go methods that use structs in their signature. All Go structs specified by a bound method (either as parameters or return types) will have Typescript versions auto generated as part of the Go code wrapper module. Using these, it's possible to share the same data model between Go and Javascript.
-
-Example: We update our `Greet` method to accept a `Person` instead of a string:
-
-```go title="main.go"
-type Person struct {
- Name string `json:"name"`
- Age uint8 `json:"age"`
- Address *Address `json:"address"`
-}
-
-type Address struct {
- Street string `json:"street"`
- Postcode string `json:"postcode"`
-}
-
-func (a *App) Greet(p Person) string {
- return fmt.Sprintf("Hello %s (Age: %d)!", p.Name, p.Age)
-}
-```
-
-The `wailsjs/go/main/App.js` file will still have the following code:
-
-```js title="App.js"
-export function Greet(arg1) {
- return window['go']['main']['App']['Greet'](arg1);
-}
-```
-
-But the `wailsjs/go/main/App.d.ts` file will be updated with the following code:
-
-```ts title="App.d.ts"
-import {main} from '../models';
-
-export function Greet(arg1:main.Person):Promise;
-```
-
-As we can see, the "main" namespace is imported from a new "models.ts" file. This file contains all the struct definitions used by our bound methods. In this example, this is a `Person` struct. If we look at `models.ts`, we can see how the models are defined:
-
-```ts title="models.ts"
-export namespace main {
-
- export class Address {
- street: string;
- postcode: string;
-
- static createFrom(source: any = {}) {
- return new Address(source);
- }
-
- constructor(source: any = {}) {
- if ('string' === typeof source) source = JSON.parse(source);
- this.street = source["street"];
- this.postcode = source["postcode"];
- }
- }
- export class Person {
- name: string;
- age: number;
- address?: Address;
-
- static createFrom(source: any = {}) {
- return new Person(source);
- }
-
- constructor(source: any = {}) {
- if ('string' === typeof source) source = JSON.parse(source);
- this.name = source["name"];
- this.age = source["age"];
- this.address = this.convertValues(source["address"], Address);
- }
-
- convertValues(a: any, classs: any, asMap: boolean = false): any {
- if (!a) {
- return a;
- }
- if (a.slice) {
- return (a as any[]).map(elem => this.convertValues(elem, classs));
- } else if ("object" === typeof a) {
- if (asMap) {
- for (const key of Object.keys(a)) {
- a[key] = new classs(a[key]);
- }
- return a;
- }
- return new classs(a);
- }
- return a;
- }
- }
-}
-```
-
-So long as you have TypeScript as part of your frontend build configuration, you can use these models in the following way:
-
-```js title="mycode.js"
-import {Greet} from '../wailsjs/go/main/App'
- import {main} from '../wailsjs/go/models'
-
- function generate() {
- let person = new main.Person()
- person.name = "Peter"
- person.age = 27
- Greet(person).then((result) => {
- console.log(result)
- })
- }
-```
-
-The combination of generated bindings and TypeScript models makes for a powerful development environment.
-
-More information on Binding can be found in the [Binding Methods](guides/application-development.mdx#binding-methods) section of the [Application Development Guide](guides/application-development.mdx).
-
-### Calling runtime methods
-
-The Javascript runtime is located at `window.runtime` and contains many methods to do various tasks such as emit an event or perform logging operations:
-
-```js title="mycode.js"
-window.runtime.EventsEmit("my-event", 1);
-```
-
-More details about the JS runtime can be found in the [Runtime Reference](reference/runtime/intro).
-
-[^1]: There is a very small subset of libraries that use features unsupported in WebViews. There are often alternatives and workarounds for such cases.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/introduction.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/introduction.mdx
deleted file mode 100644
index 8e38bff21..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/introduction.mdx
+++ /dev/null
@@ -1,75 +0,0 @@
----
-sidebar_position: 1
----
-
-# Introduction
-
-Wails is a project that enables you to write desktop apps using Go and web technologies.
-
-Consider it a lightweight and fast Electron alternative for Go. You can easily build applications with the flexibility and power of Go, combined with a rich, modern frontend.
-
-### Features
-
-- Native Menus, Dialogs, Theming and Translucency
-- Windows, macOS and linux support
-- Built in templates for Svelte, React, Preact, Vue, Lit and Vanilla JS
-- Easily call Go methods from Javascript
-- Automatic Go struct to Typescript model generation
-- No CGO or external DLLs required on Windows
-- Live development mode using the power of [Vite](https://vitejs.dev/)
-- Powerful CLI to easily Create, Build and Package applications
-- A rich [runtime library](/docs/reference/runtime/intro)
-- Applications built with Wails are Apple & Microsoft Store compliant
-
-This is [varly](https://varly.app) - a desktop application for MacOS & Windows written using Wails. Not only does it look great, it uses native menus and translucency - everything you'd expect from a modern native app.
-
-```mdx-code-block
-
-
-```
-
-When clicked, that will open an about message box:
-
-```mdx-code-block
-
-
-
-
-```
-
-### Linux
-
-This defines [Linux specific options](#linux).
-
-Name: Linux Type: `*linux.Options`
-
-#### Icon
-
-Sets up the icon representing the window. This icon is used when the window is minimized (also known as iconified).
-
-Name: Icon Type: `[]byte`
-
-Some window managers or desktop environments may also place it in the window frame, or display it in other contexts. On others, the icon is not used at all, so your mileage may vary.
-
-NOTE: Gnome on Wayland at least does not display this icon. To have a application icon there, a `.desktop` file has to be used. On KDE it should work.
-
-The icon should be provided in whatever size it was naturally drawn; that is, don’t scale the image before passing it. Scaling is postponed until the last minute, when the desired final size is known, to allow best quality.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/reference/project-config.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/reference/project-config.mdx
deleted file mode 100644
index cc9d01aa6..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/reference/project-config.mdx
+++ /dev/null
@@ -1,53 +0,0 @@
----
-sidebar_position: 5
----
-
-# Project Config
-
-The project config resides in the `wails.json` file in the project directory. The structure of the config is:
-
-```json
-{
- "name": "[The project name]",
- "assetdir": "[Relative path to the directory containing the compiled assets, this is normally inferred and could be left empty]",
- "reloaddirs": "[Additional directories to trigger reloads (comma separated), this is only used for some advanced asset configurations]",
- "frontend:install": "[The command to install node dependencies, run in the frontend directory - often `npm install`]",
- "frontend:build": "[The command to build the assets, run in the frontend directory - often `npm run build`]",
- "frontend:dev": "[This command has been replaced by frontend:dev:build. If frontend:dev:build is not specified will falls back to this command. \nIf this command is also not specified will falls back to frontend:build]",
- "frontend:dev:build": "[This command is the dev equivalent of frontend:build. If not specified falls back to frontend:dev]",
- "frontend:dev:install": "[This command is the dev equivalent of frontend:install. If not specified falls back to frontend:install]",
- "frontend:dev:watcher": "[This command is run in a separate process on `wails dev`. Useful for 3rd party watchers or starting 3d party dev servers]",
- "frontend:dev:serverUrl": "[URL to a 3rd party dev server to be used to serve assets, EG Vite. \nIf this is set to 'auto' then the devServerUrl will be inferred from the Vite output]",
- "wailsjsdir": "[Relative path to the directory that the auto-generated JS modules will be created]",
- "version": "[Project config version]",
- "outputfilename": "[The name of the binary]",
- "debounceMS": 100, // The default time the dev server waits to reload when it detects a change in assets
- "devServer": "[Address to bind the wails dev sever to. Default: localhost:34115]",
- "appargs": "[Arguments passed to the application in shell style when in dev mode]",
- "runNonNativeBuildHooks": false, // Defines if build hooks should be run though they are defined for an OS other than the host OS.
- "preBuildHooks": {
- "GOOS/GOARCH": "[The command that will be executed before a build of the specified GOOS/GOARCH: ${platform} is replaced with the "GOOS/GOARCH". The "GOOS/GOARCH" hook is executed before the "GOOS/*" and "*/*" hook.]",
- "GOOS/*": "[The command that will be executed before a build of the specified GOOS: ${platform} is replaced with the "GOOS/GOARCH". The "GOOS/*" hook is executed before the "*/*" hook.]",
- "*/*": "[The command that will be executed before every build: ${platform} is replaced with the "GOOS/GOARCH".]"
- },
- "postBuildHooks": {
- "GOOS/GOARCH": "[The command that will be executed after a build of the specified GOOS/GOARCH: ${platform} is replaced with the "GOOS/GOARCH" and ${bin} with the path to the compiled binary. The "GOOS/GOARCH" hook is executed before the "GOOS/*" and "*/*" hook.]",
- "GOOS/*": "[The command that will be executed after a build of the specified GOOS: ${platform} is replaced with the "GOOS/GOARCH" and ${bin} with the path to the compiled binary. The "GOOS/*" hook is executed before the "*/*" hook.]",
- "*/*": "[The command that will be executed after every build: ${platform} is replaced with the "GOOS/GOARCH" and ${bin} with the path to the compiled binary.]"
- },
- "info": { // Data used to populate manifests and version info.
- "companyName": "[The company name. Default: [The project name]]",
- "productName": "[The product name. Default: [The project name]]",
- "productVersion": "[The version of the product. Default: '1.0.0']",
- "copyright": "[The copyright of the product. Default: 'Copyright.........']",
- "comments": "[A short comment of the app. Default: 'Built using Wails (https://wails.app)']"
- },
- "nsisType": "['multiple': One installer per architecture. 'single': Single universal installer for all architectures being built. Default: 'multiple']",
- "obfuscated": "[Whether the app should be obfuscated. Default: false]",
- "garbleargs": "[The arguments to pass to the garble command when using the obfuscated flag]"
-}
-```
-
-This file is read by the Wails CLI when running `wails build` or `wails dev`.
-
-The `assetdir`, `reloaddirs`, `wailsjsdir`, `debounceMS`, `devserver` and `frontenddevserverurl` flags in `wails build/dev` will update the project config and thus become defaults for subsequent runs.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/reference/runtime/browser.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/reference/runtime/browser.mdx
deleted file mode 100644
index c71ec4a3a..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/reference/runtime/browser.mdx
+++ /dev/null
@@ -1,13 +0,0 @@
----
-sidebar_position: 7
----
-
-# Browser
-
-These methods are related to the system browser.
-
-### BrowserOpenURL
-
-Opens the given URL in the system browser.
-
-Go: `BrowserOpenURL(ctx context.Context, url string)` JS: `BrowserOpenURL(url string)`
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/reference/runtime/dialog.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/reference/runtime/dialog.mdx
deleted file mode 100644
index d2aa9ab6a..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/reference/runtime/dialog.mdx
+++ /dev/null
@@ -1,292 +0,0 @@
----
-sidebar_position: 5
----
-
-# Dialog
-
-This part of the runtime provides access to native dialogs, such as File Selectors and Message boxes.
-
-:::info Javascript
-
-
-Dialog is currently unsupported in the JS runtime.
-
-:::
-
-
-### OpenDirectoryDialog
-
-Opens a dialog that prompts the user to select a directory. Can be customised using [OpenDialogOptions](#opendialogoptions).
-
-Go: `OpenDirectoryDialog(ctx context.Context, dialogOptions OpenDialogOptions) (string, error)`
-
-Returns: Selected directory (blank if the user cancelled) or an error
-
-### OpenFileDialog
-
-Opens a dialog that prompts the user to select a file. Can be customised using [OpenDialogOptions](#opendialogoptions).
-
-Go: `OpenFileDialog(ctx context.Context, dialogOptions OpenDialogOptions) (string, error)`
-
-Returns: Selected file (blank if the user cancelled) or an error
-
-### OpenMultipleFilesDialog
-
-Opens a dialog that prompts the user to select multiple files. Can be customised using [OpenDialogOptions](#opendialogoptions).
-
-Go: `OpenMultipleFilesDialog(ctx context.Context, dialogOptions OpenDialogOptions) ([]string, error)`
-
-Returns: Selected files (nil if the user cancelled) or an error
-
-### SaveFileDialog
-
-Opens a dialog that prompts the user to select a filename for the purposes of saving. Can be customised using [SaveDialogOptions](#savedialogoptions).
-
-Go: `SaveFileDialog(ctx context.Context, dialogOptions SaveDialogOptions) (string, error)`
-
-Returns: The selected file (blank if the user cancelled) or an error
-
-### MessageDialog
-
-Displays a message using a message dialog. Can be customised using [MessageDialogOptions](#messagedialogoptions).
-
-Go: `MessageDialog(ctx context.Context, dialogOptions MessageDialogOptions) (string, error)`
-
-Returns: The text of the selected button or an error
-
-## Options
-
-### OpenDialogOptions
-
-```go
-type OpenDialogOptions struct {
- DefaultDirectory string
- DefaultFilename string
- Title string
- Filters []FileFilter
- ShowHiddenFiles bool
- CanCreateDirectories bool
- ResolvesAliases bool
- TreatPackagesAsDirectories bool
-}
-```
-
-| Field | Description | Win | Mac | Lin |
-| -------------------------- | ---------------------------------------------- | --- | --- | --- |
-| DefaultDirectory | The directory the dialog will show when opened | ✅ | ✅ | ✅ |
-| DefaultFilename | The default filename | ✅ | ✅ | ✅ |
-| Title | Title for the dialog | ✅ | ✅ | ✅ |
-| [Filters](#filefilter) | A list of file filters | ✅ | ✅ | ✅ |
-| ShowHiddenFiles | Show files hidden by the system | | ✅ | ✅ |
-| CanCreateDirectories | Allow user to create directories | | ✅ | |
-| ResolvesAliases | If true, returns the file not the alias | | ✅ | |
-| TreatPackagesAsDirectories | Allow navigating into packages | | ✅ | |
-
-### SaveDialogOptions
-
-```go
-type SaveDialogOptions struct {
- DefaultDirectory string
- DefaultFilename string
- Title string
- Filters []FileFilter
- ShowHiddenFiles bool
- CanCreateDirectories bool
- TreatPackagesAsDirectories bool
-}
-```
-
-| Field | Description | Win | Mac | Lin |
-| -------------------------- | ---------------------------------------------- | --- | --- | --- |
-| DefaultDirectory | The directory the dialog will show when opened | ✅ | ✅ | ✅ |
-| DefaultFilename | The default filename | ✅ | ✅ | ✅ |
-| Title | Title for the dialog | ✅ | ✅ | ✅ |
-| [Filters](#filefilter) | A list of file filters | ✅ | ✅ | ✅ |
-| ShowHiddenFiles | Show files hidden by the system | | ✅ | ✅ |
-| CanCreateDirectories | Allow user to create directories | | ✅ | |
-| TreatPackagesAsDirectories | Allow navigating into packages | | ✅ | |
-
-### MessageDialogOptions
-
-```go
-type MessageDialogOptions struct {
- Type DialogType
- Title string
- Message string
- Buttons []string
- DefaultButton string
- CancelButton string
-}
-```
-
-| Field | Description | Win | Mac | Lin |
-| ------------- | ------------------------------------------------------------------------- | --- | --- | --- |
-| Type | The type of message dialog, eg question, info... | ✅ | ✅ | ✅ |
-| Title | Title for the dialog | ✅ | ✅ | ✅ |
-| Message | The message to show the user | ✅ | ✅ | ✅ |
-| Buttons | A list of button titles | | ✅ | |
-| DefaultButton | The button with this text should be treated as default. Bound to `return` | | ✅ | |
-| CancelButton | The button with this text should be treated as cancel. Bound to `escape` | | ✅ | |
-
-#### Windows
-
-Windows has standard dialog types in which the buttons are not customisable. The value returned will be one of: "Ok", "Cancel", "Abort", "Retry", "Ignore", "Yes", "No", "Try Again" or "Continue"
-
-#### Linux
-
-Linux has standard dialog types in which the buttons are not customisable. The value returned will be one of: "Ok", "Cancel", "Yes", "No"
-
-#### Mac
-
-A message dialog on Mac may specify up to 4 buttons. If no `DefaultButton` or `CancelButton` is given, the first button is considered default and is bound to the `return` key.
-
-For the following code:
-
-```go
-selection, err := runtime.MessageDialog(b.ctx, runtime.MessageDialogOptions{
- Title: "It's your turn!",
- Message: "Select a number",
- Buttons: []string{"one", "two", "three", "four"},
-})
-```
-
-the first button is shown as default:
-
-```mdx-code-block
-
-
-
-
-```
-
-And if we specify `DefaultButton` to be "two":
-
-```go
-selection, err := runtime.MessageDialog(b.ctx, runtime.MessageDialogOptions{
- Title: "It's your turn!",
- Message: "Select a number",
- Buttons: []string{"one", "two", "three", "four"},
- DefaultButton: "two",
-})
-```
-
-the second button is shown as default. When `return` is pressed, the value "two" is returned.
-
-```mdx-code-block
-
-
-
-
-```
-
-If we now specify `CancelButton` to be "three":
-
-```go
-selection, err := runtime.MessageDialog(b.ctx, runtime.MessageDialogOptions{
- Title: "It's your turn!",
- Message: "Select a number",
- Buttons: []string{"one", "two", "three", "four"},
- DefaultButton: "two",
- CancelButton: "three",
-})
-```
-
-the button with "three" is shown at the bottom of the dialog. When `escape` is pressed, the value "three" is returned:
-
-```mdx-code-block
-
-
-
-
-
-
-```
-
-#### DialogType
-
-```go
-const (
- InfoDialog DialogType = "info"
- WarningDialog DialogType = "warning"
- ErrorDialog DialogType = "error"
- QuestionDialog DialogType = "question"
- )
-```
-
-### FileFilter
-
-```go
-type FileFilter struct {
- DisplayName string // Filter information EG: "Image Files (*.jpg, *.png)"
- Pattern string // semi-colon separated list of extensions, EG: "*.jpg;*.png"
-}
-```
-
-#### Windows
-
-Windows allows you to use multiple file filters in dialog boxes. Each FileFilter will show up as a separate entry in the dialog:
-
-```mdx-code-block
-
-
-
-
-
-
-```
-
-#### Linux
-
-Linux allows you to use multiple file filters in dialog boxes. Each FileFilter will show up as a separate entry in the dialog:
-
-```mdx-code-block
-
-
-
-
-
-
-```
-
-#### Mac
-
-Mac dialogs only have the concept of a single set of patterns to filter files. If multiple FileFilters are provided, Wails will use all the Patterns defined.
-
-Example:
-
-```go
- selection, err := runtime.OpenFileDialog(b.ctx, runtime.OpenDialogOptions{
- Title: "Select File",
- Filters: []runtime.FileFilter{
- {
- DisplayName: "Images (*.png;*.jpg)",
- Pattern: "*.png;*.jpg",
- }, {
- DisplayName: "Videos (*.mov;*.mp4)",
- Pattern: "*.mov;*.mp4",
- },
- },
- })
-```
-
-This will result in the Open File dialog using `*.png,*.jpg,*.mov,*.mp4` as a filter.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/reference/runtime/events.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/reference/runtime/events.mdx
deleted file mode 100644
index 48d27f996..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/reference/runtime/events.mdx
+++ /dev/null
@@ -1,37 +0,0 @@
----
-sidebar_position: 2
----
-
-# Events
-
-The Wails runtime provides a unified events system, where events can be emitted or received by either Go or Javascript. Optionally, data may be passed with the events. Listeners will receive the data in the local data types.
-
-### EventsOn
-
-This method sets up a listener for the given event name. When an event of type `eventName` is [emitted](#EventsEmit), the callback is triggered. Any additional data sent with the emitted event will be passed to the callback.
-
-Go: `EventsOn(ctx context.Context, eventName string, callback func(optionalData ...interface{}))` JS: `EventsOn(eventName string, callback function(optionalData?: any))`
-
-### EventsOff
-
-このメソッドは、指定されたイベント名のイベントリスナー設定を解除します。引数の`additionalEventNames`を使用することで、複数のリスナーを一度に解除できます。
-
-Go: `EventsOff(ctx context.Context, eventName string, additionalEventNames ...string)` JS: `EventsOff(eventName string, ...additionalEventNames)`
-
-### EventsOnce
-
-This method sets up a listener for the given event name, but will only trigger once.
-
-Go: `EventsOnce(ctx context.Context, eventName string, callback func(optionalData ...interface{}))` JS: `EventsOnce(eventName string, callback function(optionalData?: any))`
-
-### EventsOnMultiple
-
-This method sets up a listener for the given event name, but will only trigger a maximum of `counter` times.
-
-Go: `EventsOnMultiple(ctx context.Context, eventName string, callback func(optionalData ...interface{}), counter int)` JS: `EventsOnMultiple(eventName string, callback function(optionalData?: any), counter int)`
-
-### EventsEmit
-
-This method emits the given event. Optional data may be passed with the event. This will trigger any event listeners.
-
-Go: `EventsEmit(ctx context.Context, eventName string, optionalData ...interface{})` JS: `EventsEmit(ctx context, optionalData function(optionalData?: any))`
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/reference/runtime/intro.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/reference/runtime/intro.mdx
deleted file mode 100644
index 9cbe28096..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/reference/runtime/intro.mdx
+++ /dev/null
@@ -1,90 +0,0 @@
----
-sidebar_position: 1
----
-
-# Introduction
-
-The runtime is a library that provides utility methods for your application. There is both a Go and Javascript runtime and the aim is to try and keep them at parity where possible.
-
-ユーティリティメソッドには次のようなものがあります:
-
-- [Window](window.mdx)
-- [Menu](menu.mdx)
-- [Dialog](dialog.mdx)
-- [Events](events.mdx)
-- [Browser](browser.mdx)
-- [Log](log.mdx)
-
-The Go Runtime is available through importing `github.com/wailsapp/wails/v2/pkg/runtime`. All methods in this package take a context as the first parameter. This context should be obtained from the [OnStartup](../options.mdx#onstartup) or [OnDomReady](../options.mdx#ondomready) hooks.
-
-:::info Note
-
-
-Whilst the context will be provided to the [OnStartup](../options.mdx#onstartup) method, there's no guarantee the runtime will work in this method as the window is initialising in a different thread. If you wish to call runtime methods at startup, use [OnDomReady](../options.mdx#ondomready).
-
-:::
-
-
-The Javascript library is available to the frontend via the `window.runtime` map. There is a runtime package generated when using `dev` mode that provides Typescript declarations for the runtime. This should be located in the `wailsjs` directory in your frontend directory.
-
-### Hide
-
-Go: `Hide(ctx context.Context)` JS: `Hide()`
-
-Hides the application.
-
-:::info Note
-
-
-Macでこのメソッドを使用すると、標準のMacアプリケーションにおけるメニュー項目の`Hide`と同じ方法で、アプリケーションが非表示になります。 This is different to hiding the window, but the application still being in the foreground. For Windows and Linux, this is currently the same as `WindowHide`.
-
-:::
-
-
-### Show
-
-Shows the application.
-
-:::info Note
-
-
-Macでこのメソッドを使用すると、アプリケーションがフォアグラウンドに戻ります。 For Windows and Linux, this is currently the same as `WindowShow`.
-
-:::
-
-
-Go: `Show(ctx context.Context)` JS: `Show()`
-
-### Quit
-
-Quits the application.
-
-Go: `Quit(ctx context.Context)` JS: `Quit()`
-
-### Environment
-
-Returns details of the current environment.
-
-Go: `Environment(ctx context.Context) EnvironmentInfo` JS: `Environment(): Promise`
-
-#### EnvironmentInfo
-
-Go:
-
-```go
-type EnvironmentInfo struct {
- BuildType string
- Platform string
- Arch string
-}
-```
-
-JS:
-
-```ts
-interface EnvironmentInfo {
- buildType: string;
- platform: string;
- arch: string;
-}
-```
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/reference/runtime/log.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/reference/runtime/log.mdx
deleted file mode 100644
index e5e6ea7ac..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/reference/runtime/log.mdx
+++ /dev/null
@@ -1,130 +0,0 @@
----
-sidebar_position: 3
----
-
-# Log
-
-The Wails runtime provides a logging mechanism that may be called from Go or Javascript. Like most loggers, there are a number of log levels:
-
-- Trace
-- Debug
-- Info
-- Warning
-- Error
-- Fatal
-
-The logger will output any log message at the current, or higher, log level. Example: The `Debug` log level will output all messages except `Trace` messages.
-
-### LogPrint
-
-Logs the given message as a raw message.
-
-Go: `LogPrint(ctx context.Context, message string)` JS: `LogPrint(message: string)`
-
-### LogPrintf
-
-Logs the given message as a raw message.
-
-Go: `LogPrintf(ctx context.Context, format string, args ...interface{})`
-
-### LogTrace
-
-Logs the given message at the `Trace` log level.
-
-Go: `LogTrace(ctx context.Context, message string)` JS: `LogTrace(message: string)`
-
-### LogTracef
-
-Logs the given message at the `Trace` log level.
-
-Go: `LogTracef(ctx context.Context, format string, args ...interface{})`
-
-### LogDebug
-
-Logs the given message at the `Debug` log level.
-
-Go: `LogDebug(ctx context.Context, message string)` JS: `LogDebug(message: string)`
-
-### LogDebugf
-
-Logs the given message at the `Debug` log level.
-
-Go: `LogDebugf(ctx context.Context, format string, args ...interface{})`
-
-### LogInfo
-
-Logs the given message at the `Info` log level.
-
-Go: `LogInfo(ctx context.Context, message string)` JS: `LogInfo(message: string)`
-
-### LogInfof
-
-Logs the given message at the `Info` log level.
-
-Go: `LogInfof(ctx context.Context, format string, args ...interface{})`
-
-### LogWarning
-
-Logs the given message at the `Warning` log level.
-
-Go: `LogWarning(ctx context.Context, message string)` JS: `LogWarning(message: string)`
-
-### LogWarningf
-
-Logs the given message at the `Warning` log level.
-
-Go: `LogWarningf(ctx context.Context, format string, args ...interface{})`
-
-### LogError
-
-Logs the given message at the `Error` log level.
-
-Go: `LogError(ctx context.Context, message string)` JS: `LogError(message: string)`
-
-### LogErrorf
-
-Logs the given message at the `Error` log level.
-
-Go: `LogErrorf(ctx context.Context, format string, args ...interface{})`
-
-### LogFatal
-
-Logs the given message at the `Fatal` log level.
-
-Go: `LogFatal(ctx context.Context, message string)` JS: `LogFatal(message: string)`
-
-### LogFatalf
-
-Logs the given message at the `Fatal` log level.
-
-Go: `LogFatalf(ctx context.Context, format string, args ...interface{})`
-
-### LogSetLogLevel
-
-Sets the log level. In Javascript, the number relates to the following log levels:
-
-| Value | Log Level |
-| ----- | --------- |
-| 1 | Trace |
-| 2 | Debug |
-| 3 | Info |
-| 4 | Warning |
-| 5 | Error |
-
-Go: `LogSetLogLevel(ctx context.Context, level logger.LogLevel)` JS: `LogSetLogLevel(level: number)`
-
-## Using a Custom Logger
-
-A custom logger may be used by providing it using the [Logger](../options.mdx#logger) application option. The only requirement is that the logger implements the `logger.Logger` interface defined in `github.com/wailsapp/wails/v2/pkg/logger`:
-
-```go title="logger.go"
-type Logger interface {
- Print(message string)
- Trace(message string)
- Debug(message string)
- Info(message string)
- Warning(message string)
- Error(message string)
- Fatal(message string)
-}
-```
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/reference/runtime/menu.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/reference/runtime/menu.mdx
deleted file mode 100644
index 68feb7a3f..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/reference/runtime/menu.mdx
+++ /dev/null
@@ -1,27 +0,0 @@
----
-sidebar_position: 6
----
-
-# Menu
-
-These methods are related to the application menu.
-
-:::info Javascript
-
-
-Menu is currently unsupported in the JS runtime.
-
-:::
-
-
-### MenuSetApplicationMenu
-
-Sets the application menu to the given [menu](../menus.mdx).
-
-Go: `MenuSetApplicationMenu(ctx context.Context, menu *menu.Menu)`
-
-### MenuUpdateApplicationMenu
-
-Updates the application menu, picking up any changes to the menu passed to `MenuSetApplicationMenu`.
-
-Go: `MenuUpdateApplicationMenu(ctx context.Context)`
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/reference/runtime/window.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/reference/runtime/window.mdx
deleted file mode 100644
index 6bc4099cb..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/reference/runtime/window.mdx
+++ /dev/null
@@ -1,215 +0,0 @@
----
-sidebar_position: 4
----
-
-# Window
-
-These methods give control of the application window.
-
-### WindowSetTitle
-
-Sets the text in the window title bar.
-
-Go: `WindowSetTitle(ctx context.Context, title string)` JS: `WindowSetTitle(title: string)`
-
-### WindowFullscreen
-
-Makes the window full screen.
-
-Go: `WindowFullscreen(ctx context.Context)` JS: `WindowFullscreen()`
-
-### WindowUnfullscreen
-
-Restores the previous window dimensions and position prior to full screen.
-
-Go: `WindowUnfullscreen(ctx context.Context)` JS: `WindowUnfullscreen()`
-
-### WindowIsFullscreen
-
-Returns true if the window is full screen.
-
-Go: `WindowIsFullscreen(ctx context.Context) bool` JS: `WindowIsFullscreen() bool`
-
-### WindowCenter
-
-Centers the window on the monitor the window is currently on.
-
-Go: `WindowReload(ctx context.Context)` JS: `WindowReload()`
-
-### WindowReload
-
-Performs a "reload" (Reloads current page).
-
-Go: `WindowReloadApp(ctx context.Context)` JS: `WindowReloadApp()`
-
-### WindowReloadApp
-
-Reloads the application frontend.
-
-Go: `WindowSetSystemDefaultTheme(ctx context.Context)` JS: `WindowSetSystemDefaultTheme()`
-
-### WindowSetSystemDefaultTheme
-
-Windows only.
-
-Go: `WindowSetDarkTheme(ctx context.Context)` JS: `WindowSetDarkTheme()`
-
-Sets window theme to system default (dark/light).
-
-### WindowSetLightTheme
-
-Windows only.
-
-Go: `WindowSetLightTheme(ctx context.Context)` JS: `WindowSetLightTheme()`
-
-Sets window theme to light.
-
-### WindowSetDarkTheme
-
-Windows only.
-
-Go: `WindowShow(ctx context.Context)` JS: `WindowShow()`
-
-Sets window theme to dark.
-
-### WindowShow
-
-Shows the window, if it is currently hidden.
-
-Go: `WindowHide(ctx context.Context)` JS: `WindowHide()`
-
-### WindowHide
-
-Hides the window, if it is currently visible.
-
-Go: `WindowSetSize(ctx context.Context, width int, height int)` JS: `WindowSetSize(size: Size)`
-
-### WindowIsNormal
-
-Returns true if the window not minimised, maximised or fullscreen.
-
-Go: `WindowIsNormal(ctx context.Context) bool` JS: `WindowIsNormal() bool`
-
-### WindowSetSize
-
-Sets the width and height of the window.
-
-Go: `WindowSetMaxSize(ctx context.Context, width int, height int)` JS: `WindowSetMaxSize(size: Size)`
-
-### WindowGetSize
-
-Gets the width and height of the window.
-
-Go: `WindowSetMinSize(ctx context.Context, width int, height int)` JS: `WindowSetMinSize(size: Size)`
-
-### WindowSetMinSize
-
-Sets the minimum window size. Will resize the window if the window is currently smaller than the given dimensions.
-
-Setting a size of `0,0` will disable this constraint.
-
-Go: `WindowSetAlwaysOnTop(ctx context.Context, b bool)` JS: `WindowSetAlwaysOnTop(b: Boolen)`
-
-### WindowSetMaxSize
-
-Sets the maximum window size. Will resize the window if the window is currently larger than the given dimensions.
-
-Setting a size of `0,0` will disable this constraint.
-
-Go: `WindowSetPosition(ctx context.Context, x int, y int)` JS: `WindowSetPosition(position: Position)`
-
-### WindowSetAlwaysOnTop
-
-Sets the window AlwaysOnTop or not on top.
-
-Go: `WindowGetPosition(ctx context.Context) (x int, y int)` JS: `WindowGetPosition() : Position`
-
-### WindowSetPosition
-
-Sets the window position relative to the monitor the window is currently on.
-
-Go: `WindowMaximise(ctx context.Context)` JS: `WindowMaximise()`
-
-### WindowGetPosition
-
-Gets the window position relative to the monitor the window is currently on.
-
-Go: `WindowUnmaximise(ctx context.Context)` JS: `WindowUnmaximise()`
-
-### WindowMaximise
-
-Maximises the window to fill the screen.
-
-Go: `WindowToggleMaximise(ctx context.Context)` JS: `WindowToggleMaximise()`
-
-### WindowUnmaximise
-
-Restores the window to the dimensions and position prior to maximising.
-
-Go: `WindowMinimise(ctx context.Context)` JS: `WindowMinimise()`
-
-### WindowIsMaximised
-
-Returns true if the window is maximised.
-
-Go: `WindowIsMaximised(ctx context.Context) bool` JS: `WindowIsMaximised() bool`
-
-### WindowToggleMaximise
-
-Toggles between Maximised and UnMaximised.
-
-Go: `WindowToggleMaximise(ctx context.Context)` JS: `WindowToggleMaximise()`
-
-### WindowMinimise
-
-Minimises the window.
-
-Go: `WindowSetBackgroundColour(ctx context.Context, R, G, B, A uint8)` JS: `WindowSetBackgroundColour(R, G, B, A)`
-
-### WindowUnminimise
-
-Restores the window to the dimensions and position prior to minimising.
-
-Go: `WindowUnminimise(ctx context.Context)` JS: `WindowUnminimise()`
-
-### WindowIsMinimised
-
-Returns true if the window is minimised.
-
-Go: `WindowIsMinimised(ctx context.Context) bool` JS: `WindowIsMinimised() bool`
-
-### WindowSetBackgroundColour
-
-Sets the background colour of the window to the given RGBA colour definition. This colour will show through for all transparent pixels.
-
-Valid values for R, G, B and A are 0-255.
-
-:::info Windows
-
-
-On Windows, only alpha values of 0 or 255 are supported. Any value that is not 0 will be considered 255.
-
-:::
-
-
-Go: `WindowSetBackgroundColour(ctx context.Context, R, G, B, A uint8)` JS: `WindowSetBackgroundColour(R, G, B, A)`
-
-## Typescript Object Definitions
-
-### Position
-
-```ts
-interface Position {
- x: number;
- y: number;
-}
-```
-
-### Size
-
-```ts
-interface Size {
- w: number;
- h: number;
-}
-```
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/tutorials/dogsapi.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/tutorials/dogsapi.mdx
deleted file mode 100644
index 0910a4060..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/tutorials/dogsapi.mdx
+++ /dev/null
@@ -1,249 +0,0 @@
----
-sidebar_position: 20
----
-
-# Dogs API
-
-```mdx-code-block
-
-
-
-
-```
-
-:::note
-
-
-This tutorial has been kindly provided by [@tatadan](https://twitter.com/tatadan) and forms part of their [Wails Examples Repository](https://github.com/tataDan/wails-v2-examples).
-
-:::
-
-
-In this tutorial we are going to develop an application that retrieves photos of dogs from the web and then displays them.
-
-### Create the project
-
-Let's create the application. From a terminal enter: `wails init -n dogs-api -t svelte`
-
-Note: We could optionally add `-ide vscode` or `-ide goland` to the end of this command if you wanted to add IDE support.
-
-Now let's `cd dogs-api` and start editing the project files.
-
-### Remove unused code
-
-We will start by removing some elements that we know we will not use:
-
-- Open `app.go` and remove the following lines:
-
-```go
-// Greet returns a greeting for the given name
-func (a *App) Greet(name string) string {
- return fmt.Sprintf("Hello %s, It's show time!", name)
-}
-```
-
-- Open `frontend/src/App.svelte` and delete all lines.
-- Delete the `frontend/src/assets/images/logo-universal.png` file
-
-### Creating our application
-
-Now let's add our new Go code.
-
-Add the following struct declarations to `app.go` before the function definitions:
-
-```go
-type RandomImage struct {
- Message string
- Status string
-}
-
-type AllBreeds struct {
- Message map[string]map[string][]string
- Status string
-}
-
-type ImagesByBreed struct {
- Message []string
- Status string
-}
-```
-
-Add the following functions to `app.go` (perhaps after the existing function definitions):
-
-```go
-func (a *App) GetRandomImageUrl() string {
- response, err := http.Get("https://dog.ceo/api/breeds/image/random")
- if err != nil {
- log.Fatal(err)
- }
-
- responseData, err := ioutil.ReadAll(response.Body)
- if err != nil {
- log.Fatal(err)
- }
-
- var data RandomImage
- json.Unmarshal(responseData, &data)
-
- return data.Message
-}
-
-func (a *App) GetBreedList() []string {
- var breeds []string
-
- response, err := http.Get("https://dog.ceo/api/breeds/list/all")
- if err != nil {
- log.Fatal(err)
- }
-
- responseData, err := ioutil.ReadAll(response.Body)
- if err != nil {
- log.Fatal(err)
- }
-
- var data AllBreeds
- json.Unmarshal(responseData, &data)
-
- for k := range data.Message {
- breeds = append(breeds, k)
- }
-
- sort.Strings(breeds)
-
- return breeds
-}
-
-func (a *App) GetImageUrlsByBreed(breed string) []string {
-
- url := fmt.Sprintf("%s%s%s%s", "https://dog.ceo/api/", "breed/", breed, "/images")
- response, err := http.Get(url)
- if err != nil {
- log.Fatal(err)
- }
-
- responseData, err := ioutil.ReadAll(response.Body)
- if err != nil {
- log.Fatal(err)
- }
-
- var data ImagesByBreed
- json.Unmarshal(responseData, &data)
-
- return data.Message
-}
-```
-
-Modify the `import` section of `app.go` to look like this:
-
-```go
-import (
- "context"
- "fmt"
- "encoding/json"
- "io/ioutil"
- "log"
- "net/http"
- "sort"
-)
-```
-
-Add the following lines to `frontend/src/App.svelte`:
-
-
-```html
-
-
-
Dogs API
-
-
- Click on down arrow to select a breed
-
-
-
-
-{#if showRandomPhoto}
-
-{/if}
-{#if showBreedPhotos}
- {#each photos as photo}
-
- {/each}
-{/if}
-
-
-```
-
-
-
-
-### Testing the application
-
-To generate the bindings and test the application, run `wails dev`.
-
-### Compiling the application
-
-To compile the application to a single, production grade binary, run `wails build`.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/tutorials/helloworld.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/tutorials/helloworld.mdx
deleted file mode 100644
index 3e198f06b..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/tutorials/helloworld.mdx
+++ /dev/null
@@ -1,124 +0,0 @@
----
-sidebar_position: 10
----
-
-# Hello World
-
-The aim of this tutorial is to get you up and running with the most basic application using Wails. You will be able to:
-
-- Create a new Wails application
-- Build the application
-- Run the application
-
-:::note
-
-
-This tutorial uses Windows as the target platform. Output will vary slightly depending on your operating system.
-
-:::
-
-
-## Create a new Wails application
-
-To create a new Wails application using the default vanilla JS template, you need to run the following command:
-
-```bash
-wails init -n helloworld
-```
-
-You should see something similar to the following:
-
-```
-Wails CLI v2.0.0
-
-Initialising Project 'helloworld'
----------------------------------
-
-Project Name: helloworld
-Project Directory: C:\Users\leaan\tutorial\helloworld
-Project Template: vanilla
-Template Support: https://wails.io
-
-Initialised project 'helloworld' in 232ms.
-```
-
-This will create a new directory called `helloworld` in the current directory. In this directory, you will find a number of files:
-
-```
-build/ - Contains the build files + compiled application
-frontend/ - Contains the frontend files
-app.go - Contains the application code
-main.go - The main program with the application configuration
-wails.json - The project configuration file
-go.mod - The go module file
-go.sum - The go module checksum file
-```
-
-## Build the application
-
-To build the application, change to the new `helloworld` project directory and run the following command:
-
-```bash
-wails build
-```
-
-You should see something like the following:
-
-```
-Wails CLI v2.0.0
-
-App Type: desktop
-Platforms: windows/amd64
-Compiler: C:\Users\leaan\go\go1.18.3\bin\go.exe
-Build Mode: Production
-Skip Frontend: false
-Compress: false
-Package: true
-Clean Build Dir: false
-LDFlags: ""
-Tags: []
-Race Detector: false
-
-Building target: windows/amd64
-------------------------------
- - Installing frontend dependencies: Done.
- - Compiling frontend: Done.
- - Generating bundle assets: Done.
- - Compiling application: Done.
-Built 'C:\Users\leaan\tutorial\helloworld\build\bin\helloworld.exe' in 10.616s.
-```
-
-This has compiled the application and saved it in the `build/bin` directory.
-
-## Run the application
-
-If we view the `build/bin` directory in Windows Explorer, we should see our project binary:
-
-```mdx-code-block
-
-
-
-
-```
-
-We can run it by simply double-clicking the `helloworld.exe` file.
-
-On Mac, Wails generates a `helloworld.app` file which can be run by double-clicking it.
-
-On Linux, you can run the application using `./helloworld` from the `build/bin` directory.
-
-You should see the application working as expected:
-
-```mdx-code-block
-
-```
-
-[FileHound Export Utility](https://www.filehound.co.uk/) FileHound is a cloud document management platform made for secure file retention, business process automation and SmartCapture capabilities.
-
-The FileHound Export Utility allows FileHound Administrators the ability to run a secure document and data extraction tasks for alternative back-up and recovery purposes. This application will download all documents and/or meta data saved in FileHound based on the filters you choose. The metadata will be exported in both JSON and XML formats.
-
-Backend built with: Go 1.15 Wails 1.11.0 go-sqlite3 1.14.6 go-linq 3.2
-
-Frontend with: Vue 2.6.11 Vuex 3.4.0 Typescript Tailwind 1.9.6
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/community/templates.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/community/templates.mdx
deleted file mode 100644
index d7b068c42..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/community/templates.mdx
+++ /dev/null
@@ -1,56 +0,0 @@
----
-sidebar_position: 1
----
-
-# テンプレート
-
-このページでは、コミュニティがサポートしているテンプレートを紹介しています。 このページに新たにテンプレートを含めたい場合は、このページの下側にある`このページを編集`をクリックして、プルリクエストを出してください。 独自テンプレートの作成方法については、[テンプレート](../guides/templates.mdx)ガイドをご覧ください。
-
-これらのテンプレートを使用するには、`wails init -n "プロジェクト名" -t [テンプレートのリンク[@バージョン]]`コマンドを実行してください。
-
-バージョンサフィックスが無い場合は、デフォルトで、メインブランチのコードテンプレートが使用されます。 バージョンサフィックスがある場合は、当該バージョンのタグに対応するコードテンプレートが使用されます。
-
-例: `wails init -n "プロジェクト名" -t https://github.com/misitebao/wails-template-vue`
-
-:::warning 注意
-
-
-**Wailsプロジェクトでは、サードパーティ製テンプレートのメンテナンスは行っておらず、責任も負いません!**
-
-テンプレートについてよく分からない場合は、`package.json`および`wails.json`を確認し、どのようなスクリプトが実行されるのかや、どのようなパッケージがインストールされるのかを調べてください。
-
-:::
-
-
-## Vue
-
-- [wails-template-vue](https://github.com/misitebao/wails-template-vue) - Wails template based on Vue ecology (Integrated TypeScript, Dark theme, Internationalization, Single page routing, TailwindCSS)
-- [wails-vite-vue-ts](https://github.com/codydbentley/wails-vite-vue-ts) - Viteを使用したVue 3 TypeScript (および機能を追加する手順)
-- [wails-vite-vue-the-works](https://github.com/codydbentley/wails-vite-vue-the-works) - Vite、Vuex、Vue Router、SaaS、ESLint + Prettier を使用した Vue 3 TypeScript
-
-## Angular
-
-- [wails-angular-template](https://github.com/TAINCER/wails-angular-template) - TypeScript、Sass、ホットリロード、コード分割、i18n を使用した Angular
-
-## React
-
-- [wails-react-template](https://github.com/AlienRecall/wails-react-template) - reactjsを使用したテンプレート
-- [wails-react-template](https://github.com/flin7/wails-react-template) - ライブ開発をサポートしたReactの最小テンプレート
-- [wails-template-nextjs](https://github.com/LGiki/wails-template-nextjs) - Next.js、TypeScript を使用したテンプレート
-- [wails-vite-react-ts-tailwind-template](https://github.com/hotafrika/wails-vite-react-ts-tailwind-template) - A template for React + TypeScript + Vite + TailwindCSS
-
-## Svelte
-
-- [wails-svelte-template](https://github.com/raitonoberu/wails-svelte-template) - Svelteを使用したテンプレート
-- [wails-vite-svelte-template](https://github.com/BillBuilt/wails-vite-svelte-template) - SvelteおよびViteを使用したテンプレート
-- [wails-vite-svelte-tailwind-template](https://github.com/BillBuilt/wails-vite-svelte-tailwind-template) - TailwindCSS v3を含んだ、SvelteおよびViteを使用したテンプレート
-- [wails-sveltekit-template](https://github.com/h8gi/wails-sveltekit-template) - SvelteKitを使用したテンプレート
-
-## Elm
-
-- [wails-elm-template](https://github.com/benjamin-thomas/wails-elm-template) - 関数型プログラミングと**高速な**ホットリロードを使ったGUIアプリ開発 :tada: :rocket:
-- [wails-template-elm-tailwind](https://github.com/rnice01/wails-template-elm-tailwind) - Combine the powers :muscle: of Elm + Tailwind CSS + Wails! Hot reloading supported.
-
-## ピュアJavaScript (バニラ)
-
-- [wails-pure-js-template](https://github.com/KiddoV/wails-pure-js-template) - 基本的なJavaScript、HTML、CSSのみを含むテンプレート
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/gettingstarted/development.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/gettingstarted/development.mdx
deleted file mode 100644
index b26c3c546..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/gettingstarted/development.mdx
+++ /dev/null
@@ -1,16 +0,0 @@
----
-sidebar_position: 5
----
-
-# アプリの開発
-
-プロジェクトディレクトリのルート上で`wails dev`コマンドを実行すると、アプリを開発モードで起動することができます。 コマンドを実行すると下記の処理が実行されます:
-
-- アプリをビルドしたのち、起動する
-- Goのコードをフロントエンドにバインドし、Javascriptから呼び出せるようにする
-- Using the power of [Vite](https://vitejs.dev/), will watch for modifications in your Go files and rebuild/re-run on change
-- ブラウザからアプリを操作できるようにする[Webサーバ](http://localhost:34115)を立ち上げる。 これにより、任意のブラウザ拡張機能を利用できる。 JavascriptのコンソールからGoのコードを呼び出すこともできる
-
-アプリ開発を始めるときは、プロジェクトディレクトリ上で`wails dev`コマンドを実行しましょう。 詳しくは、[こちら](../reference/cli.mdx#dev)をご覧ください。
-
-近日中にチュートリアルを公開予定です。
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/gettingstarted/firstproject.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/gettingstarted/firstproject.mdx
deleted file mode 100644
index 8ce6453d7..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/gettingstarted/firstproject.mdx
+++ /dev/null
@@ -1,130 +0,0 @@
----
-sidebar_position: 2
----
-
-# プロジェクトの開始
-
-## プロジェクトの生成
-
-CLIのインストールが終わったら、`wails init`コマンドで新しいプロジェクトを生成しましょう。
-
-好きなフレームワークを選択してください:
-
-```mdx-code-block
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-
-
-
- Generate a Svelte project using Javascript with:
-
- wails init -n myproject -t svelte
-
-If you would rather use Typescript:
-
- wails init -n myproject -t svelte-ts
-
-
-
- Generate a React project using Javascript with:
-
- wails init -n myproject -t react
-
-If you would rather use Typescript:
-
- wails init -n myproject -t react-ts
-
-
-
- Generate a Vue project using Javascript with:
-
- wails init -n myproject -t vue
-
-If you would rather use Typescript:
-
- wails init -n myproject -t vue-ts
-
-
-
- Generate a Preact project using Javascript with:
-
- wails init -n myproject -t preact
-
-If you would rather use Typescript:
-
- wails init -n myproject -t preact-ts
-
-
-
- Generate a Lit project using Javascript with:
-
- wails init -n myproject -t lit
-
-If you would rather use Typescript:
-
- wails init -n myproject -t lit-ts
-
-
-
- Generate a Vanilla project using Javascript with:
-
- wails init -n myproject -t vanilla
-
-If you would rather use Typescript:
-
- wails init -n myproject -t vanilla-ts
-
-
-
-```
-
-
-
-様々な機能やフレームワークを提供する[コミュニティテンプレート](../community/templates.mdx)を利用することもできます。
-
-プロジェクト生成時に使用可能なオプションを確認するには、`wails init -help`を実行してください。 詳しくは、[CLIリファレンス](../reference/cli.mdx#init)を参照してください。
-
-## プロジェクトのディレクトリ構成
-
-Wailsのプロジェクトディレクトリの構成は次のとおりです:
-
-```
-.
-├── build/
-│ ├── appicon.png
-│ ├── darwin/
-│ └── windows/
-├── frontend/
-├── go.mod
-├── go.sum
-├── main.go
-└── wails.json
-```
-
-### プロジェクトの構造
-
-- `/main.go` - アプリのメインコード
-- `/frontend/` - フロントエンドのプロジェクトディレクトリ
-- `/build/` - ビルドディレクトリ
-- `/build/appicon.png` - アプリアイコン
-- `/build/darwin/` - Mac固有のプロジェクトディレクトリ
-- `/build/windows/` - Windows固有のプロジェクトディレクトリ
-- `/wails.json` - プロジェクト構成ファイル
-- `/go.mod` - Goモジュール定義ファイル
-- `/go.sum` - Goモジュールチェックサムファイル
-
-`frontend`ディレクトリ内は、Wailsで決まったファイル構成等は無く、お好きなフロントエンドプロジェクトを配置することができます。
-
-`build`ディレクトリは、アプリのビルド時に使用されます。 この中のファイルは、ビルドの挙動をカスタマイズするために、適宜ファイル内容を書き換えることができます。 buildディレクトリ内のファイルを削除すると、デフォルトのファイルが再生成されます。
-
-`go.mod`のモジュール名は、最初は"changeme"になっています。 このモジュール名は、あなたのプロジェクトに適切な名前に変更しましょう。
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/gettingstarted/installation.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/gettingstarted/installation.mdx
deleted file mode 100644
index 1317c1ec4..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/gettingstarted/installation.mdx
+++ /dev/null
@@ -1,79 +0,0 @@
----
-sidebar_position: 1
----
-
-# インストール
-
-## サポートされているプラットフォーム
-
-- Windows 10/11 AMD64/ARM64
-- MacOS 10.13+ AMD64
-- MacOS 11.0+ ARM64
-- Linux AMD64/ARM64
-
-## 依存関係
-
-Wailsをインストールする前に、下記のものを導入しておく必要があります。
-
-- Go 1.18+
-- NPM (Node 15+)
-
-### Go
-
-Download Go from the [Go Downloads Page](https://go.dev/dl/).
-
-公式の[Goインストール手順](https://go.dev/doc/install)に従って、Goをインストールしてください。 その際、`PATH`環境変数に`~/go/bin`ディレクトリへのパスが含まれていることも確認してください。 それらが終わったら、ターミナルを再起動し、以下の確認をしてください:
-
-- Goが正しくインストールされているかを確認する: `go version`
-- "~/go/bin"のディレクトリパスがPATH環境変数に含まれているか確認する: `echo $PATH | grep go/bin`
-
-### NPM
-
-[Nodeダウンロードページ](https://nodejs.org/ja/download/)からNPMをダウンロードしてください。 最新版を利用することをお勧めします。なぜなら、私たちは最新版に対してテストを実施しているためです。
-
-`npm --version`を実行して、インストールが完了しているかを確認してください。
-
-## プラットフォーム固有の依存関係
-
-開発作業を行うプラットフォームによって、必要な依存関係が存在します:
-
-```mdx-code-block
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-
-
-
- Wails requires that the xcode command line tools are installed. This can be
- done by running xcode-select --install.
-
-
- Wails requires that the WebView2 runtime is installed. Some Windows installations will already have this installed. You can check using the wails doctor command.
-
-
- Linux required the standard gcc build tools plus libgtk3 and libwebkit. Rather than list a ton of commands for different distros, Wails can try to determine what the installation commands are for your specific distribution. Run wails doctor after installation to be shown how to install the dependencies. If your distro/package manager is not supported, please consult the Add Linux Distro guide.
-
-
-```
-
-## 任意の依存関係
-
-- [UPX](https://upx.github.io/)を導入することで、構築したアプリを圧縮できます。
-
-## Wailsのインストール
-
-`go install github.com/wailsapp/wails/v2/cmd/wails@latest`を実行して、Wails CLIをインストールしてください。
-
-## システムチェック
-
-`wails doctor`を実行すると、必要な依存関係が正しくインストールされているかを確認することができます。 正しくインストールされていない場合は、その内容をあなたにお知らせして、どうすれば解決できるかを教えてくれます。
-
-## `wails`コマンドが見つからないのですが?
-
-`wails`コマンドが見つからないとシステムに怒られた場合は、Goが、公式のGoインストール手順に従って導入されているかを確認してください。 コマンドが見つからないほとんどの理由は、あなたのホームディレクトリ配下にある`go/bin`ディレクトリのパスが、`PATH`環境変数に含まれていないからです。 また、インストールによって行われた環境変更を反映させるために、もともと開いていたコマンドプロンプト(ターミナル)がある場合はそれらをいったん閉じて、再度開きなおしてください。
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/application-development.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/application-development.mdx
deleted file mode 100644
index a618076f1..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/application-development.mdx
+++ /dev/null
@@ -1,194 +0,0 @@
-# Application Development
-
-There are no hard and fast rules for developing applications with Wails, but there are some basic guidelines.
-
-## Application Setup
-
-The pattern used by the default templates are that `main.go` is used for configuring and running the application, whilst `app.go` is used for defining the application logic.
-
-The `app.go` file will define a struct that has 2 methods which act as hooks into the main application:
-
-```go title="app.go"
-type App struct {
- ctx context.Context
-}
-
-func NewApp() *App {
- return &App{}
-}
-
-func (a *App) startup(ctx context.Context) {
- a.ctx = ctx
-}
-
-func (a *App) shutdown(ctx context.Context) {
-}
-```
-
-- The startup method is called as soon as Wails allocates the resources it needs and is a good place for creating resources, setting up event listeners and anything else the application needs at startup. It is given a `context.Context` which is usually saved in a struct field. This context is needed for calling the [runtime](../reference/runtime/intro.mdx). If this method returns an error, the application will terminate. In dev mode, the error will be output to the console.
-
-- The shutdown method will be called by Wails right at the end of the shutdown process. This is a good place to deallocate memory and perform any shutdown tasks.
-
-The `main.go` file generally consists of a single call to `wails.Run()`, which accepts the application configuration. The pattern used by the templates is that before the call to `wails.Run()`, an instance of the struct we defined in `app.go` is created and saved in a variable called `app`. This configuration is where we add our callbacks:
-
-```go {3,9,10} title="main.go"
-func main() {
-
- app := NewApp()
-
- err := wails.Run(&options.App{
- Title: "My App",
- Width: 800,
- Height: 600,
- OnStartup: app.startup,
- OnShutdown: app.shutdown,
- })
- if err != nil {
- log.Fatal(err)
- }
-}
-
-```
-
-More information on application lifecycle hooks can be found [here](../howdoesitwork.mdx#application-lifecycle-callbacks).
-
-## Binding Methods
-
-It is likely that you will want to call Go methods from the frontend. This is normally done by adding public methods to the already defined struct in `app.go`:
-
-```go {16-18} title="app.go"
-type App struct {
- ctx context.Context
-}
-
-func NewApp() *App {
- return &App{}
-}
-
-func (a *App) startup(ctx context.Context) {
- a.ctx = ctx
-}
-
-func (a *App) shutdown(ctx context.Context) {
-}
-
-func (a *App) Greet(name string) string {
- return fmt.Sprintf("Hello %s!", name)
-}
-```
-
-In the main application configuration, the `Bind` key is where we can tell Wails what we want to bind:
-
-```go {11-13} title="main.go"
-func main() {
-
- app := NewApp()
-
- err := wails.Run(&options.App{
- Title: "My App",
- Width: 800,
- Height: 600,
- OnStartup: app.startup,
- OnShutdown: app.shutdown,
- Bind: []interface{}{
- app,
- },
- })
- if err != nil {
- log.Fatal(err)
- }
-}
-
-```
-
-This will bind all public methods in our `App` struct (it will never bind the startup and shutdown methods).
-
-### Dealing with context when binding multiple structs
-
-If you want to bind methods for multiple structs but want each struct to keep a reference to the context so that you can use the runtime functions, a good pattern is to pass the context from the `OnStartup` method to your struct instances :
-
-```go
-func main() {
-
- app := NewApp()
- otherStruct := NewOtherStruct()
-
- err := wails.Run(&options.App{
- Title: "My App",
- Width: 800,
- Height: 600,
- OnStartup: func(ctx context.Context){
- app.SetContext(ctx)
- otherStruct.SetContext(ctx)
- },
- OnShutdown: app.shutdown,
- Bind: []interface{}{
- app,
- otherStruct
- },
- })
- if err != nil {
- log.Fatal(err)
- }
-}
-```
-
-More information on Binding can be found [here](../howdoesitwork.mdx#method-binding).
-
-## Application Menu
-
-Wails supports adding a menu to your application. This is done by passing a [Menu](../reference/menus.mdx#menu) struct to application config. It's common to use a method that returns a Menu, and even more common for that to be a method on the `App` struct used for the lifecycle hooks.
-
-```go {11} title="main.go"
-func main() {
-
- app := NewApp()
-
- err := wails.Run(&options.App{
- Title: "My App",
- Width: 800,
- Height: 600,
- OnStartup: app.startup,
- OnShutdown: app.shutdown,
- Menu: app.menu(),
- Bind: []interface{}{
- app,
- },
- })
- if err != nil {
- log.Fatal(err)
- }
-}
-
-```
-
-## Assets
-
-The great thing about the way Wails v2 handles assets is that it doesn't! The only thing you need to give Wails is an `embed.FS`. How you get to that is entirely up to you. You can use vanilla html/css/js files like the vanilla template. You could have some complicated build system, it doesn't matter.
-
-When `wails build` is run, it will check the `wails.json` project file at the project root. There are 2 keys in the project file that are read:
-
-- "frontend:install"
-- "frontend:build"
-
-The first, if given, will be executed in the `frontend` directory to install the node modules. The second, if given, will be executed in the `frontend` directory to build the frontend project.
-
-If these 2 keys aren't given, then Wails does absolutely nothing with the frontend. It is only expecting that `embed.FS`.
-
-### AssetsHandler
-
-A Wails v2 app can optionally define a `http.Handler` in the `options.App`, which allows hooking into the AssetServer to create files on the fly or process POST/PUT requests. GET requests are always first handled by the `assets` FS. If the FS doesn't find the requested file the request will be forwarded to the `http.Handler` for serving. Any requests other than GET will be directly processed by the `AssetsHandler` if specified. It's also possible to only use the `AssetsHandler` by specifiy `nil` as the `Assets` option.
-
-## Built in Dev Server
-
-Running `wails dev` will start the built in dev server which will start a file watcher in your project directory. By default, if any file changes, wails checks if it was an application file (default: `.go`, configurable with `-e` flag). If it was, then it will rebuild your application and relaunch it. If the changed file was in the assets, it will issue a reload after a short amount of time.
-
-The dev server uses a technique called "debouncing" which means it doesn't reload straight away, as there may be multiple files changed in a short amount of time. When a trigger occurs, it waits for a set amount of time before issuing a reload. If another trigger happens, it resets to the wait time again. By default this value is `100ms`. If this value doesn't work for your project, it can be configured using the `-debounce` flag. If used, this value will be saved to your project config and become the default.
-
-## External Dev Server
-
-Some frameworks come with their own live-reloading server, however they will not be able to take advantage of the Wails Go bindings. In this scenario, it is best to run a watcher script that rebuilds the project into the build directory, which Wails will be watching. For an example, see the default svelte template that uses [rollup](https://rollupjs.org/guide/en/). For [create-react-app](https://create-react-app.dev/), it's possible to use [this script](https://gist.github.com/int128/e0cdec598c5b3db728ff35758abdbafd) to achieve a similar result.
-
-## Go Module
-
-The default Wails templates generate a `go.mod` file that contains the module name "changeme". You should change this to something more appropriate after project generation.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/bleeding-edge.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/bleeding-edge.mdx
deleted file mode 100644
index b81cc79dc..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/bleeding-edge.mdx
+++ /dev/null
@@ -1,55 +0,0 @@
-# Bleeding Edge
-
-## Overview
-
-Wails is in constant development and new releases are regularly "tagged". This usually happens when all the newer code on `master` has been tested and confirmed working. If you need a bugfix or feature that has not yet made it to a release, it's possible to use the latest "bleeding edge" version using the following steps:
-
-- `git clone https://github.com/wailsapp/wails`
-- `cd wails/v2/cmd/wails`
-- `go install`
-
-NOTE: The directory that you cloned the project into will now be called "clonedir".
-
-The Wails CLI will now be at the very latest version.
-
-### Updating your project
-
-To update projects to use the latest version of the Wails library, update the project's `go.mod` and ensure the following line is at the bottom of the file:
-
-`replace github.com/wailsapp/wails/v2 => `
-
-Example:
-
-On Windows: `replace github.com/wailsapp/wails/v2 => C:\Users\leaan\Documents\wails-v2-beta\wails\v2`
-
-On 'nix: `replace github.com/wailsapp/wails/v2 => /home/me/projects/wails/v2`
-
-To revert to a stable version, run:
-
-`go install github.com/wailsapp/wails/v2/cmd/wails@latest`
-
-## Testing a Branch
-
-If you want to test a branch, follow the instructions above, but ensure you switch the branch you want to test before installing:
-
-- `git clone https://github.com/wailsapp/wails`
-- `cd wails`
-- `git checkout -b branch-to-test --track origin/branch-to-test`
-- `cd v2/cmd/wails`
-- `go install`
-
-Make sure you [update your project](#updating-your-project) as described above.
-
-## Testing a PR
-
-If you want to test a PR, follow the instructions above, but ensure you fetch the PR and switch the branch before installing. Please replace `[IDofThePR]` with the ID of the PR shown on github.com:
-
-- `git clone https://github.com/wailsapp/wails`
-- `cd wails`
-- `git fetch -u origin pull/[IDofThePR]/head:test/pr-[IDofThePR]`
-- `git checkout test/pr-[IDofThePR]`
-- `git reset --hard HEAD`
-- `cd v2/cmd/wails`
-- `go install`
-
-Make sure you [update your project](#updating-your-project) as described above.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/dynamic-assets.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/dynamic-assets.mdx
deleted file mode 100644
index e4c199594..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/dynamic-assets.mdx
+++ /dev/null
@@ -1,134 +0,0 @@
-# Dynamic Assets
-
-If you want to load or generate assets for your frontend dynamically, you can achieve that using the [AssetsHandler](../reference/options#assetshandler) option. The AssetsHandler is a generic `http.Handler` which will be called for any non GET request on the assets server and for GET requests which can not be served from the bundled assets because the file is not found.
-
-By installing a custom AssetsHandler, you can serve your own assets using a custom asset server.
-
-## Example
-
-In our example project, we will create a simple assets handler which will load files off disk:
-
-```go title=main.go {16-35,49}
-package main
-
-import (
- "embed"
- "fmt"
- "github.com/wailsapp/wails/v2"
- "github.com/wailsapp/wails/v2/pkg/options"
- "net/http"
- "os"
- "strings"
-)
-
-//go:embed all:frontend/dist
-var assets embed.FS
-
-type FileLoader struct {
- http.Handler
-}
-
-func NewFileLoader() *FileLoader {
- return &FileLoader{}
-}
-
-func (h *FileLoader) ServeHTTP(res http.ResponseWriter, req *http.Request) {
- var err error
- requestedFilename := strings.TrimPrefix(req.URL.Path, "/")
- println("Requesting file:", requestedFilename)
- fileData, err := os.ReadFile(requestedFilename)
- if err != nil {
- res.WriteHeader(http.StatusBadRequest)
- res.Write([]byte(fmt.Sprintf("Could not load file %s", requestedFilename)))
- }
-
- res.Write(fileData)
-}
-
-func main() {
- // Create an instance of the app structure
- app := NewApp()
-
- // Create application with options
- err := wails.Run(&options.App{
- Title: "helloworld",
- Width: 1024,
- Height: 768,
- Assets: assets,
- BackgroundColour: &options.RGBA{R: 27, G: 38, B: 54, A: 255},
- OnStartup: app.startup,
- AssetsHandler: NewFileLoader(),
- Bind: []interface{}{
- app,
- },
- })
-
- if err != nil {
- println("Error:", err)
- }
-}
-```
-
-When we run the application in dev mode using `wails dev`, we will see the following output:
-
-```
-DEB | [ExternalAssetHandler] Loading 'http://localhost:3001/favicon.ico'
-DEB | [ExternalAssetHandler] Loading 'http://localhost:3001/favicon.ico' failed, using AssetHandler
-Requesting file: favicon.ico
-```
-
-As you can see, the assets handler is called when the default assets server is unable to serve the `favicon.ico` file.
-
-If you right click the main application and select "inspect" to bring up the devtools, you can test this feature out by typing the following into the console:
-
-```
-let response = await fetch('does-not-exist.txt');
-```
-
-This will generate an error in the devtools. We can see that the error is what we expect, returned by our custom assets handler:
-
-```mdx-code-block
-
-
-
-```
-
-However, if we request `go.mod`, we will see the following output:
-
-```mdx-code-block
-
-
-
-```
-
-This technique can be used to load images directly into the page. If we updated our default vanilla template and replaced the logo image:
-
-```html
-
-```
-
-with:
-
-```html
-
-```
-
-Then we would see the following:
-
-```mdx-code-block
-
-
-
-```
-
-:::warning
-
-
-Exposing your filesystem in this way is a security risk. It is recommended that you properly manage access to your filesystem.
-
-:::
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/frameless.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/frameless.mdx
deleted file mode 100644
index a9370f36f..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/frameless.mdx
+++ /dev/null
@@ -1,85 +0,0 @@
-# Frameless Applications
-
-Wails supports application that have no frames. This can be achieved by using the [frameless](../reference/options.mdx#frameless) field in [Application Options](../reference/options.mdx#application-options).
-
-Wails offers a simple solution for dragging the window: Any HTML element that has the CSS style `--wails-draggable:drag` will act as a "drag handle". This property applies to all child elements. If you need to indicate that a nested element should not drag, then use the attribute '--wails-draggable:no-drag' on that element.
-
-```html
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-```
-
-For some projects, using a CSS variable may not be possible due to dynamic styling. In this case, you can use the `CSSDragProperty` and `CSSDragValue` application options to define a property and value that will be used to indicate draggable regions:
-
-```go title=main.go
-package main
-
-import (
- "embed"
-
- "github.com/wailsapp/wails/v2"
- "github.com/wailsapp/wails/v2/pkg/options"
-)
-
-//go:embed all:frontend/dist
-var assets embed.FS
-
-func main() {
- // Create an instance of the app structure
- app := NewApp()
-
- // Create application with options
- err := wails.Run(&options.App{
- Title: "alwaysontop",
- Width: 1024,
- Height: 768,
- Assets: assets,
- Frameless: true,
- CSSDragProperty: "widows",
- CSSDragValue: "1",
- Bind: []interface{}{
- app,
- },
- })
-
- if err != nil {
- println("Error:", err)
- }
-}
-```
-
-```html title=index.html
-
-
-
-
-
- alwaysontop
-
-
-
-
-
-
-```
-
-:::info Fullscreen
-
-
-If you allow your application to go fullscreen, this drag functionality will be disabled.
-
-:::
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/frontend.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/frontend.mdx
deleted file mode 100644
index 29e442c5e..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/frontend.mdx
+++ /dev/null
@@ -1,75 +0,0 @@
-# Frontend
-
-## Script Injection
-
-When Wails serves your `index.html`, by default, it will inject 2 script entries into the `` tag to load `/wails/ipc.js` and `/wails/runtime.js`. These files install the bindings and runtime respectively.
-
-The code below shows where these are injected by default:
-
-```html
-
-
- injection example
-
-
-
-
-
-
-
-
Please enter your name below 👇
-
-
-
-
-
-
-
-
-
-```
-
-### Overriding Default Script Injection
-
-To provide more flexibility to developers, there is a meta tag that may be used to customise this behaviour:
-
-```html
-
-```
-
-The options are as follows:
-
-| 値 | Description |
-| ------------------- | ------------------------------------------------ |
-| noautoinjectruntime | Disable the autoinjection of `/wails/runtime.js` |
-| noautoinjectipc | Disable the autoinjection of `/wails/ipc.js` |
-| noautoinject | Disable all autoinjection of scripts |
-
-Multiple options may be used provided they are comma seperated.
-
-This code is perfectly valid and operates the same as the autoinjection version:
-
-```html
-
-
-
- injection example
-
-
-
-
-
-
-
Please enter your name below 👇
-
-
-
-
-
-
-
-
-
-
-
-```
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/ides.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/ides.mdx
deleted file mode 100644
index 7649030a2..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/ides.mdx
+++ /dev/null
@@ -1,128 +0,0 @@
-# IDEs
-
-Wails aims to provide a great development experience. To that aim, we now support generating IDE specific configuration to provide smoother project setup.
-
-Currently, we support [Visual Studio Code](https://code.visualstudio.com/) but aim to support other IDEs such as Goland.
-
-## Visual Studio Code
-
-```mdx-code-block
-
-
-
-```
-
-When generating a project using the `-ide vscode` flags, IDE files will be created alongside the other project files. These files are placed into the `.vscode` directory and provide the correct configuration for debugging your application.
-
-The 2 files generated are `tasks.json` and `launch.json`. Below are the files generated for the default vanilla project:
-
-```json title="tasks.json"
-{
- "version": "2.0.0",
- "tasks": [
- {
- "label": "build",
- "type": "shell",
- "options": {
- "cwd": "${workspaceFolder}"
- },
- "command": "go",
- "args": [
- "build",
- "-tags",
- "dev",
- "-gcflags",
- "all=-N -l",
- "-o",
- "build/bin/myproject.exe"
- ]
- }
- ]
-}
-```
-
-```json title="launch.json"
-{
- "version": "0.2.0",
- "configurations": [
- {
- "name": "Wails: Debug myproject",
- "type": "go",
- "request": "launch",
- "mode": "exec",
- "program": "${workspaceFolder}/build/bin/myproject.exe",
- "preLaunchTask": "build",
- "cwd": "${workspaceFolder}",
- "env": {}
- }
- ]
-}
-```
-
-### Configuring the install and build steps
-
-The `tasks.json` file is simple for the default project as there is no `npm install` or `npm run build` step needed. For projects that have a frontend build step, such as the svelte template, we would need to edit `tasks.json` to add the install and build steps:
-
-```json title="tasks.json"
-{
- "version": "2.0.0",
- "tasks": [
- {
- "label": "npm install",
- "type": "npm",
- "script": "install",
- "options": {
- "cwd": "${workspaceFolder}/frontend"
- },
- "presentation": {
- "clear": true,
- "panel": "shared",
- "showReuseMessage": false
- },
- "problemMatcher": []
- },
- {
- "label": "npm run build",
- "type": "npm",
- "script": "build",
- "options": {
- "cwd": "${workspaceFolder}/frontend"
- },
- "presentation": {
- "clear": true,
- "panel": "shared",
- "showReuseMessage": false
- },
- "problemMatcher": []
- },
- {
- "label": "build",
- "type": "shell",
- "options": {
- "cwd": "${workspaceFolder}"
- },
- "command": "go",
- "args": [
- "build",
- "-tags",
- "dev",
- "-gcflags",
- "all=-N -l",
- "-o",
- "build/bin/vscode.exe"
- ],
- "dependsOn": ["npm install", "npm run build"]
- }
- ]
-}
-```
-
-:::info Future Enhancement
-
-
-In the future, we hope to generate a `tasks.json` that includes the install and build steps automatically.
-
-:::
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/linux-distro-support.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/linux-distro-support.mdx
deleted file mode 100644
index 882f8d258..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/linux-distro-support.mdx
+++ /dev/null
@@ -1,104 +0,0 @@
-# Linux Distro Support
-
-## Overview
-
-Wails offers Linux support but providing installation instructions for all available distributions is an impossible task. Instead, Wails tries to determine if the packages you need to develop applications are available via your system's package manager. Currently, we support the following package managers:
-
-- apt
-- dnf
-- emerge
-- eopkg
-- nixpkgs
-- pacman
-- zypper
-
-## Adding package names
-
-There may be circumstances where your distro uses one of the supported package managers but the package name is different. For example, you may use an Ubuntu derivative, but the package name for gtk may be different. Wails attempts to find the correct package by iterating through a list of package names. The list of packages are stored in the packagemanager specific file in the `v2/internal/system/packagemanager` directory. In our example, this would be `v2/internal/system/packagemanager/apt.go`.
-
-In this file, the list of packages are defined by the `Packages()` method:
-
-```go
-func (a *Apt) Packages() packagemap {
- return packagemap{
- "libgtk-3": []*Package{
- {Name: "libgtk-3-dev", SystemPackage: true, Library: true},
- },
- "libwebkit": []*Package{
- {Name: "libwebkit2gtk-4.0-dev", SystemPackage: true, Library: true},
- },
- "gcc": []*Package{
- {Name: "build-essential", SystemPackage: true},
- },
- "pkg-config": []*Package{
- {Name: "pkg-config", SystemPackage: true},
- },
- "npm": []*Package{
- {Name: "npm", SystemPackage: true},
- },
- "docker": []*Package{
- {Name: "docker.io", SystemPackage: true, Optional: true},
- },
- }
-}
-```
-
-Let's assume that in our linux distro, `libgtk-3` is packaged under the name `lib-gtk3-dev`. We could add support for this by adding the following line:
-
-```go {5}
-func (a *Apt) Packages() packagemap {
- return packagemap{
- "libgtk-3": []*Package{
- {Name: "libgtk-3-dev", SystemPackage: true, Library: true},
- {Name: "lib-gtk3-dev", SystemPackage: true, Library: true},
- },
- "libwebkit": []*Package{
- {Name: "libwebkit2gtk-4.0-dev", SystemPackage: true, Library: true},
- },
- "gcc": []*Package{
- {Name: "build-essential", SystemPackage: true},
- },
- "pkg-config": []*Package{
- {Name: "pkg-config", SystemPackage: true},
- },
- "npm": []*Package{
- {Name: "npm", SystemPackage: true},
- },
- "docker": []*Package{
- {Name: "docker.io", SystemPackage: true, Optional: true},
- },
- }
-}
-```
-
-## Adding new package managers
-
-To add a new package manager, perform the following steps:
-
-- Create a new file in `v2/internal/system/packagemanager` called `.go`, where `` is the name of the package manager.
-- Define a struct that conforms to the package manager interface defined in `pm.go`:
-
-```go
-type PackageManager interface {
- Name() string
- Packages() packagemap
- PackageInstalled(*Package) (bool, error)
- PackageAvailable(*Package) (bool, error)
- InstallCommand(*Package) string
-}
-```
-
-- `Name()` should return the name of the package manager
-- `Packages()` should return a `packagemap`, that provides candidate filenames for dependencies
-- `PackageInstalled()` should return `true` if the given package is installed
-- `PackageAvailable()` should return `true` if the given package is not installed but available for installation
-- `InstallCommand()` should return the exact command to install the given package name
-
-Take a look at the other package managers code to get an idea how this works.
-
-:::info Remember
-
-
-If you add support for a new package manager, don't forget to also update this page!
-
-:::
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/linux.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/linux.mdx
deleted file mode 100644
index 229c282bf..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/linux.mdx
+++ /dev/null
@@ -1,18 +0,0 @@
-# Linux
-
-This page has miscellaneous guides related to developing Wails applications for Linux.
-
-## Video tag doesn't fire "ended" event
-
-When using a video tag, the "ended" event is not fired when the video is finished playing. This is a bug in WebkitGTK, however you can use the following workaround to fix it:
-
-```js
-videoTag.addEventListener("timeupdate", (event) => {
- if (event.target.duration - event.target.currentTime < 0.2) {
- let ended = new Event("ended");
- event.target.dispatchEvent(ended);
- }
-});
-```
-
-Source: [Lyimmi](https://github.com/Lyimmi) on the [discussions board](https://github.com/wailsapp/wails/issues/1729#issuecomment-1212291275)
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/migrating.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/migrating.mdx
deleted file mode 100644
index 55b791e61..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/migrating.mdx
+++ /dev/null
@@ -1,187 +0,0 @@
-# Migrating from v1
-
-## Overview
-
-Wails v2 is a significant change from v1. This document aims to highlight the changes and the steps in migrating an existing project.
-
-### Creating the Application
-
-In v1, the main application is created using `wails.CreateApp`, bindings are added with `app.Bind`, then the application is run using `app.Run()`.
-
-Example:
-
-```go title="v1"
- app := wails.CreateApp(&wails.AppConfig{
- Title: "MyApp",
- Width: 1024,
- Height: 768,
- JS: js,
- CSS: css,
- Colour: "#131313",
- })
- app.Bind(basic)
- app.Run()
-```
-
-In v2, there is just a single method, `wails.Run()`, that accepts [application options](../reference/options.mdx#application-options).
-
-```go title="v2"
- err := wails.Run(&options.App{
- Title: "MyApp",
- Width: 800,
- Height: 600,
- Assets: assets,
- Bind: []interface{}{
- basic,
- },
- })
-```
-
-### Binding
-
-In v1, it was possible to bind both arbitrary functions and structs. In v2, this has been simplified to only binding structs. The struct instances that were previously passed to the `Bind()` method in v1, are now specified in the `Bind` field of the [application options](../reference/options.mdx#application-options):
-
-```go title="v1"
- app := wails.CreateApp(/* options */)
- app.Bind(basic)
-```
-
-```go title="v2"
- err := wails.Run(&options.App{
- /* other options */
- Bind: []interface{}{
- basic,
- },
- })
-```
-
-In v1, bound methods were available to the frontend at `window.backend`. This has changed to `window.go`.``
-
-### Application Lifecycle
-
-In v1, there were 2 special methods in a bound struct: `WailsInit()` and `WailsShutdown()`. These have been replaced with 3 lifecycle hooks as part of the [application options](../reference/options.mdx#application-options):
-
-- [OnStartup](../reference/options.mdx#onstartup)
-- [OnShutdown](../reference/options.mdx#onshutdown)
-- [OnDomReady](../reference/options.mdx#ondomready)
-
-Note: [OnDomReady](../reference/options.mdx#ondomready) replaces the `wails:ready` system event in v1.
-
-These methods can be standard functions, but a common practice is to have them part of a struct:
-
-```go title="v2"
- basic := NewBasicApp()
- err := wails.Run(&options.App{
- /* Other Options */
- OnStartup: basic.startup,
- OnShutdown: basic.shutdown,
- OnDomReady: basic.domready,
- })
-...
-type Basic struct {
- ctx context.Context
-}
-func (b *Basic) startup(ctx context.Context) {
- b.ctx = ctx
-}
-...
-```
-
-### Runtime
-
-The runtime in v2 is much richer than v1 with support for menus, window manipulation and better dialogs. The signature of the methods has changed slightly - please refer the the [Runtime Reference](../reference/runtime/intro.mdx).
-
-In v1, the [runtime](../reference/runtime/intro.mdx) was available via a struct passed to `WailsInit()`. In v2, the runtime has been moved out to its own package. Each method in the runtime takes the `context.Context` that is passed to the [OnStartup](../reference/options.mdx#onstartup) method.
-
-```go title="Runtime Example"
-package main
-
-import "github.com/wailsapp/wails/v2/pkg/runtime"
-
-type Basic struct {
- ctx context.Context
-}
-
-// startup is called at application startup
-func (a *App) startup(ctx context.Context) {
- a.ctx = ctx
- runtime.LogInfo(ctx, "Application Startup called!")
-}
-
-```
-
-### Assets
-
-The _biggest_ change in v2 is how assets are handled.
-
-In v1, assets were passed via 2 application options:
-
-- `JS` - The application's Javascript
-- `CSS` - The application's CSS
-
-This meant that the responsibility of generating a single JS and CSS file was on the developer. This essentially required the use of complicated packers such as webpack.
-
-In v2, Wails makes no assumptions about your frontend assets, just like a webserver. All of your application assets are passed to the application options as an `embed.FS`.
-
-**This means there is no requirement to bundle your assets, encode images as Base64 or attempt the dark art of bundler configuration to use custom fonts**.
-
-At startup, Wails will scan the given `embed.FS` for `index.html` and use its location as the root path for all the other application assets - just like a webserver would.
-
-Example: An application has the following project layout. All final assets are placed in the `frontend/dist` directory:
-
-```shell
-.
-├── build/
-├── frontend/
-│ └── dist/
-│ ├── index.html
-│ ├── main.js
-│ ├── main.css
-│ └── logo.svg
-├── main.go
-└── wails.json
-```
-
-Those assets may be used by the application by simply creating an `embed.FS`:
-
-```go title="Assets Example"
-//go:embed all:frontend/dist
-var assets embed.FS
-
-func main() {
- err := wails.Run(&options.App{
- /* Other Options */
- Assets: assets,
- })
-}
-```
-
-Of course, bundlers can be used if you wish to. The only requirement is to pass the final application assets directory to Wails using an `embed.FS` in the `Assets` key of the [application options](../reference/options.mdx#application-options).
-
-### Project Configuration
-
-In v1, the project configuration was stored in the `project.json` file in the project root. In v2, the project configuration is stored in the `wails.json` file in the project root.
-
-The format of the file is slightly different. Here is a comparison:
-
-
-
-| v1 | v2 | Notes |
-| ------------------ | ---------------- | --------------------------------------------------- |
-| name | name | |
-| description | | Removed |
-| author / name | author / name | |
-| author / email | author / email | |
-| version | version | |
-| binaryname | outputfilename | Changed |
-| frontend / dir | | Removed |
-| frontend / install | frontend:install | Changed |
-| frontend / build | frontend:build | Changed |
-| frontend / bridge | | Removed |
-| frontend / serve | | Removed |
-| tags | | Removed |
-| | wailsjsdir | The directory to generate wailsjs modules |
-| | assetdir | The directory of the compiled frontend assets for `dev` mode. This is normally inferred and could be left empty. |
-| | reloaddirs | Comma separated list of additional directories to watch for changes and to trigger reloads in `dev` mode. This is only needed for some more advanced asset configurations. |
-
-
-```
-
-## Publishing Templates
-
-Publishing a template is simply pushing the files to GitHub. The following best practice is encouraged:
-
-- Remove any unwanted files and directories (such as `.git`) from your frontend directory
-- Ensure that `template.json` is complete, especially `helpurl`
-- Push the files to GitHub
-- Create a PR on the [Community Templates](../community/templates.mdx) page
-- Announce the template on the [Template Announcement](https://github.com/wailsapp/wails/discussions/825) discussion board
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/troubleshooting.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/troubleshooting.mdx
deleted file mode 100644
index c5d62774b..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/troubleshooting.mdx
+++ /dev/null
@@ -1,148 +0,0 @@
-# Troubleshooting
-
-An assortment of troubleshooting tips.
-
-## `wails`コマンドが見つからないのですが?
-
-`wails`コマンドが見つからないとシステムに怒られた場合は、Goが、公式のGoインストール手順に従って導入されているかを確認してください。 コマンドが見つからないほとんどの理由は、あなたのホームディレクトリ配下にある`go/bin`ディレクトリのパスが、`PATH`環境変数に含まれていないからです。 また、インストールによって行われた環境変更を反映させるために、もともと開いていたコマンドプロンプト(ターミナル)がある場合はそれらをいったん閉じて、再度開きなおしてください。
-
-## My application is displaying a white/blank screen
-
-Check that your application includes the assets from the correct directory. In your `main.go` file, you will have something similar to the following code:
-
-```go
-//go:embed all:frontend/dist
-var assets embed.FS
-```
-
-Check that `frontend/dist` contains your application assets.
-
-### Mac
-
-If this happens on Mac, try adding the following to your `Info.plist`:
-
-```xml
-NSAppTransportSecurity
-
- NSAllowsLocalNetworking
-
-
-```
-
-Reference: https://github.com/wailsapp/wails/issues/1504#issuecomment-1174317433
-
-## Mac application not valid
-
-If your built application looks like this in finder:
-
-```mdx-code-block
-
-
-
-```
-
-it's likely that your application's `info.plist` is invalid. Update the file in `build/.app/Contents/info.plist` and check if the data is valid, EG check the binary name is correct. To persist the changes, copy the file back to the `build/darwin` directory.
-
-## Cannot call backend method from frontend with variadic arguments
-
-If you have a backend method defined with variadic parameters, eg:
-
-```go
-func (a *App) TestFunc(msg string, args ...interface{}) error {
- // Code
-}
-```
-
-calling this method from the frontend like this will fail:
-
-```js
-var msg = "Hello: ";
-var args = ["Go", "JS"];
-window.go.main.App.TestFunc(msg, ...args)
- .then((result) => {
- //do things here
- })
- .catch((error) => {
- //handle error
- });
-```
-
-Workaround:
-
-```js
-var msg = "Hello ";
-var args = ["Go", "JS"];
-window.go.main.App.TestFunc(msg, args)
- .then((result) => {
- //without the 3 dots
- //do things here
- })
- .catch((error) => {
- //handle error
- });
-```
-
-Credit: https://github.com/wailsapp/wails/issues/1186
-
-## I'm having getting proxy errors when trying to install Wails
-
-If you are getting errors like this:
-
-```
-"https://proxy.golang.org/github.com/wailsapp/wails/cmd/wails/@v/list": dial tcp 172.217.163.49:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
-```
-
-it's probably because the official Go Proxy is being blocked (Users in China have reported this). The solution is to set up the proxy manually, eg:
-
-```
-go env -w GO111MODULE=on
-go env -w GOPROXY=https://goproxy.cn,direct
-```
-
-Source: https://github.com/wailsapp/wails/issues/1233
-
-## The generated Typescript doesn't have the correct types
-
-Sometimes the generated Typescript doesn't have the correct types. To mitigate this, it is possible to specify what types should be generated using the `ts_type` struct tag. For more details, please read [this](https://github.com/tkrajina/typescriptify-golang-structs#custom-types).
-
-## When I navigate away from `index.html`, I am unable to call methods on the frontend
-
-If you navigate away from `index.html` to a new html file, the context will be lost. This can be fixed by adding the following imports to the `` section of any new page you navigate to:
-
-```html
-
-
-
-
-```
-
-Source: https://github.com/wailsapp/wails/discussions/1512
-
-## I get `too many open files` errors on my Mac when I run `wails dev`
-
-By default, macOS will only allow you to open a maximum of 256 files. This can affect the `wails dev` command. This limit can be increased by running: `ulimit -n 1024` in the terminal.
-
-FSNotify is [looking to move to Apple's fsevents](https://github.com/fsnotify/fsnotify/issues/11) for Mac. If this isn't completed soon, we will create our own implementation, tracked [here](https://github.com/wailsapp/wails/issues/1733).
-
-## My Mac app gives me weird compilation errors
-
-A few users have reported seeing compilation errors such as the following:
-
-```shell
-# github.com/wailsapp/wails/v2/internal/frontend/desktop/darwin
-In file included from ../../pkg/mod/github.com/wailsapp/wails/v2@v2.0.0-beta.44.2/internal/frontend/desktop/darwin/callbacks.go:9:
-In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX12.1.sdk/System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:12:
-/Library/Developer/CommandLineTools/SDKs/MacOSX12.1.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSBundle.h:91:143: error: function does not return NSString
-- (NSAttributedString *)localizedAttributedStringForKey:(NSString *)key value:(nullable NSString *)value table:(nullable NSString *)tableName NS_FORMAT_ARGUMENT(1) NS_REFINED_FOR_SWIFT API_AVAILABLE(macos(12.0), ios(15.0), watchos(8.0), tvos(15.0));
- ~~~~~~~~~~~~~~ ^ ~
-/Library/Developer/CommandLineTools/SDKs/MacOSX12.1.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSObjCRuntime.h:103:48: note: expanded from macro 'NS_FORMAT_ARGUMENT'
- #define NS_FORMAT_ARGUMENT(A) __attribute__ ((format_arg(A)))
-```
-
-This is _normally_ due to a mismatch with the OS version you are running and the version of the XCode Command Line Tools installed. If you see an error like this, try upgrading your XCode Command Line Tools to the latest version.
-
-Source: https://github.com/wailsapp/wails/issues/1806
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/vscode.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/vscode.mdx
deleted file mode 100644
index ed258656d..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/vscode.mdx
+++ /dev/null
@@ -1,82 +0,0 @@
-
-# Visual Studio Code
-
-This page is for miscellaneous tips and tricks when using Visual Studio Code with Wails.
-
-## Vetur Configuration
-
-Many thanks to [@Lyimmi](https://github.com/Lyimmi) for this tip. Originally posted [here](https://github.com/wailsapp/wails/issues/1791#issuecomment-1228158349).
-
-Vetur is a popular plugin for Visual Studio Code that provides syntax highlighting and code completion for Vue projects. When loading a Wails project in VSCode, Vetur will throw an error as it is expecting to find the frontend project in the root directory. To fix this, you can do the following:
-
-Create a file named `vetur.config.js` in the project's root.
-
-```javascript
-// vetur.config.js
-/** @type {import('vls').VeturConfig} */
-module.exports = {
- // **optional** default: `{}`
- // override vscode settings
- // Notice: It only affects the settings used by Vetur.
- settings: {
- "vetur.useWorkspaceDependencies": true,
- "vetur.experimental.templateInterpolationService": true
- },
- // **optional** default: `[{ root: './' }]`
- // support monorepos
- projects: [
- {
- // **required**
- // Where is your project?
- // It is relative to `vetur.config.js`.
- // root: './packages/repo1',
- root: './frontend',
- // **optional** default: `'package.json'`
- // Where is `package.json` in the project?
- // We use it to determine the version of vue.
- // It is relative to root property.
- package: './package.json',
- // **optional**
- // Where is TypeScript config file in the project?
- // It is relative to root property.
- tsconfig: './tsconfig.json',
- // **optional** default: `'./.vscode/vetur/snippets'`
- // Where is vetur custom snippets folders?
- snippetFolder: './.vscode/vetur/snippets',
- // **optional** default: `[]`
- // Register globally Vue component glob.
- // If you set it, you can get completion by that components.
- // It is relative to root property.
- // Notice: It won't actually do it. You need to use `require.context` or `Vue.component`
- globalComponents: [
- './src/components/**/*.vue'
- ]
- }
- ]
-}
-```
-
-Next, configure `frontend/tsconfig.json`:
-
-```javascript
-{
- "compilerOptions": {
- "module": "system",
- "noImplicitAny": true,
- "removeComments": true,
- "preserveConstEnums": true,
- "sourceMap": true,
- "outFile": "../../built/local/tsc.js",
- "allowJs": true
- },
- "exclude": [
- "node_modules",
- "**/*.spec.ts"
- ],
- "include": [
- "src/**/*",
- "wailsjs/**/*.ts"
- ]
-}
-```
-This should enable you to now use Vetur as expected.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/howdoesitwork.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/howdoesitwork.mdx
deleted file mode 100644
index 11fe0ad9f..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/howdoesitwork.mdx
+++ /dev/null
@@ -1,365 +0,0 @@
----
-sidebar_position: 20
----
-
-# どうやって動いているの?
-
-Wailsは、webkitフロントエンドを備えた、何の変哲もないGoアプリです。 アプリ全体のうちGoの部分は、アプリのコードと、ウィンドウ制御などの便利な機能を提供するランタイムライブラリで構成されています。 フロントエンドはwebkitウィンドウであり、フロンドエンドアセットをウィンドウ上に表示します。 フロントエンドからも、Javascriptでランタイムライブラリを呼び出すことができます。 そして最終的に、Goのメソッドはフロントエンドにバインドされ、ローカルのJavascriptメソッドであるかのように、フロントエンドから呼び出すことができます。
-
-```mdx-code-block
-
-
-```
-
-When clicked, that will open an about message box:
-
-```mdx-code-block
-
-
-
-
-```
-
-### Linux
-
-[Linux固有のオプション](#linux)を定義します。
-
-名前: Linux データ型: `*linux.Options`
-
-#### Icon
-
-Sets up the icon representing the window. This icon is used when the window is minimized (also known as iconified).
-
-名前: Icon データ型: `[]byte`
-
-Some window managers or desktop environments may also place it in the window frame, or display it in other contexts. On others, the icon is not used at all, so your mileage may vary.
-
-NOTE: Gnome on Wayland at least does not display this icon. To have a application icon there, a `.desktop` file has to be used. On KDE it should work.
-
-The icon should be provided in whatever size it was naturally drawn; that is, don’t scale the image before passing it. Scaling is postponed until the last minute, when the desired final size is known, to allow best quality.
-
-#### WindowIsTranslucent
-
-Setting this to `true` will make the window background translucent. Some window managers may ignore it, or result in a black window.
-
-名前: WindowIsTranslucent データ型: `bool`
\ No newline at end of file
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/reference/project-config.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/reference/project-config.mdx
deleted file mode 100644
index cc9d01aa6..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/reference/project-config.mdx
+++ /dev/null
@@ -1,53 +0,0 @@
----
-sidebar_position: 5
----
-
-# Project Config
-
-The project config resides in the `wails.json` file in the project directory. The structure of the config is:
-
-```json
-{
- "name": "[The project name]",
- "assetdir": "[Relative path to the directory containing the compiled assets, this is normally inferred and could be left empty]",
- "reloaddirs": "[Additional directories to trigger reloads (comma separated), this is only used for some advanced asset configurations]",
- "frontend:install": "[The command to install node dependencies, run in the frontend directory - often `npm install`]",
- "frontend:build": "[The command to build the assets, run in the frontend directory - often `npm run build`]",
- "frontend:dev": "[This command has been replaced by frontend:dev:build. If frontend:dev:build is not specified will falls back to this command. \nIf this command is also not specified will falls back to frontend:build]",
- "frontend:dev:build": "[This command is the dev equivalent of frontend:build. If not specified falls back to frontend:dev]",
- "frontend:dev:install": "[This command is the dev equivalent of frontend:install. If not specified falls back to frontend:install]",
- "frontend:dev:watcher": "[This command is run in a separate process on `wails dev`. Useful for 3rd party watchers or starting 3d party dev servers]",
- "frontend:dev:serverUrl": "[URL to a 3rd party dev server to be used to serve assets, EG Vite. \nIf this is set to 'auto' then the devServerUrl will be inferred from the Vite output]",
- "wailsjsdir": "[Relative path to the directory that the auto-generated JS modules will be created]",
- "version": "[Project config version]",
- "outputfilename": "[The name of the binary]",
- "debounceMS": 100, // The default time the dev server waits to reload when it detects a change in assets
- "devServer": "[Address to bind the wails dev sever to. Default: localhost:34115]",
- "appargs": "[Arguments passed to the application in shell style when in dev mode]",
- "runNonNativeBuildHooks": false, // Defines if build hooks should be run though they are defined for an OS other than the host OS.
- "preBuildHooks": {
- "GOOS/GOARCH": "[The command that will be executed before a build of the specified GOOS/GOARCH: ${platform} is replaced with the "GOOS/GOARCH". The "GOOS/GOARCH" hook is executed before the "GOOS/*" and "*/*" hook.]",
- "GOOS/*": "[The command that will be executed before a build of the specified GOOS: ${platform} is replaced with the "GOOS/GOARCH". The "GOOS/*" hook is executed before the "*/*" hook.]",
- "*/*": "[The command that will be executed before every build: ${platform} is replaced with the "GOOS/GOARCH".]"
- },
- "postBuildHooks": {
- "GOOS/GOARCH": "[The command that will be executed after a build of the specified GOOS/GOARCH: ${platform} is replaced with the "GOOS/GOARCH" and ${bin} with the path to the compiled binary. The "GOOS/GOARCH" hook is executed before the "GOOS/*" and "*/*" hook.]",
- "GOOS/*": "[The command that will be executed after a build of the specified GOOS: ${platform} is replaced with the "GOOS/GOARCH" and ${bin} with the path to the compiled binary. The "GOOS/*" hook is executed before the "*/*" hook.]",
- "*/*": "[The command that will be executed after every build: ${platform} is replaced with the "GOOS/GOARCH" and ${bin} with the path to the compiled binary.]"
- },
- "info": { // Data used to populate manifests and version info.
- "companyName": "[The company name. Default: [The project name]]",
- "productName": "[The product name. Default: [The project name]]",
- "productVersion": "[The version of the product. Default: '1.0.0']",
- "copyright": "[The copyright of the product. Default: 'Copyright.........']",
- "comments": "[A short comment of the app. Default: 'Built using Wails (https://wails.app)']"
- },
- "nsisType": "['multiple': One installer per architecture. 'single': Single universal installer for all architectures being built. Default: 'multiple']",
- "obfuscated": "[Whether the app should be obfuscated. Default: false]",
- "garbleargs": "[The arguments to pass to the garble command when using the obfuscated flag]"
-}
-```
-
-This file is read by the Wails CLI when running `wails build` or `wails dev`.
-
-The `assetdir`, `reloaddirs`, `wailsjsdir`, `debounceMS`, `devserver` and `frontenddevserverurl` flags in `wails build/dev` will update the project config and thus become defaults for subsequent runs.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/reference/runtime/browser.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/reference/runtime/browser.mdx
deleted file mode 100644
index 39ae7e0a9..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/reference/runtime/browser.mdx
+++ /dev/null
@@ -1,13 +0,0 @@
----
-sidebar_position: 7
----
-
-# Browser
-
-これらは、システムブラウザに関連したメソッドです。
-
-### BrowserOpenURL
-
-指定されたURLをシステムブラウザで開きます。
-
-Go: `BrowserOpenURL(ctx context.Context, url string)` JS: `BrowserOpenURL(url string)`
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/reference/runtime/dialog.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/reference/runtime/dialog.mdx
deleted file mode 100644
index 28c91d225..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/reference/runtime/dialog.mdx
+++ /dev/null
@@ -1,304 +0,0 @@
----
-sidebar_position: 5
----
-
-# ダイアログ
-
-ランタイムでは、ファイルセレクターやメッセージボックスといったネイティブダイアログへのアクセスを提供しています。
-
-:::info Javascript
-
-
-現在、Javascriptランタイムではダイアログをサポートしていません。
-
-:::
-
-
-### OpenDirectoryDialog
-
-ユーザにディレクトリの選択を求めるダイアログを開きます。 [OpenDialogOptions](#opendialogoptions)を使用してカスタマイズできます。
-
-Go: `OpenDirectoryDialog(ctx context.Context, dialogOptions OpenDialogOptions) (string, error)`
-
-返り値: 選択されたディレクトリ(キャンセルされた場合は空) またはエラー
-
-### OpenFileDialog
-
-ユーザにファイルの選択を求めるダイアログを開きます。 [OpenDialogOptions](#opendialogoptions)を使用してカスタマイズできます。
-
-Go: `OpenFileDialog(ctx context.Context, dialogOptions OpenDialogOptions) (string, error)`
-
-返り値: 選択されたファイル(キャンセルされた場合は空) またはエラー
-
-### OpenMultipleFilesDialog
-
-ユーザに複数ファイルの選択を求めるダイアログを開きます。 [OpenDialogOptions](#opendialogoptions)を使用してカスタマイズできます。
-
-Go: `OpenMultipleFilesDialog(ctx context.Context, dialogOptions OpenDialogOptions) ([]string, error)`
-
-返り値: 選択された複数ファイル(キャンセルされた場合はnil) またはエラー
-
-### SaveFileDialog
-
-保存の目的でユーザにファイル名を入力選択させるダイアログを開きます。 [SaveDialogOptions](#savedialogoptions)を使用してカスタマイズできます。
-
-Go: `SaveFileDialog(ctx context.Context, dialogOptions SaveDialogOptions) (string, error)`
-
-返り値: 入力選択されたファイル(キャンセルされた場合は空) またはエラー
-
-### MessageDialog
-
-メッセージダイアログを使用してメッセージを表示します。 [MessageDialogOptions](#messagedialogoptions)を使用してカスタマイズできます。
-
-Go: `MessageDialog(ctx context.Context, dialogOptions MessageDialogOptions) (string, error)`
-
-返り値: 選択されたボタンのテキストまたはエラー
-
-## オプション
-
-### OpenDialogOptions
-
-```go
-type OpenDialogOptions struct {
- DefaultDirectory string
- DefaultFilename string
- Title string
- Filters []FileFilter
- ShowHiddenFiles bool
- CanCreateDirectories bool
- ResolvesAliases bool
- TreatPackagesAsDirectories bool
-}
-```
-
-| Field | Description | Win | Mac | Lin |
-| -------------------------- | ------------------------- | --- | --- | --- |
-| DefaultDirectory | ダイアログが開かれたときに初期表示するディレクトリ | ✅ | ✅ | ✅ |
-| DefaultFilename | デフォルトファイル名 | ✅ | ✅ | ✅ |
-| Title | ダイアログのタイトル | ✅ | ✅ | ✅ |
-| [Filters](#filefilter) | ファイルフィルタのリスト | ✅ | ✅ | ✅ |
-| ShowHiddenFiles | システムの隠しファイルを表示 | | ✅ | ✅ |
-| CanCreateDirectories | ユーザによるディレクトリの作成を許可する | | ✅ | |
-| ResolvesAliases | エイリアスではなくファイルパスを返す | | ✅ | |
-| TreatPackagesAsDirectories | パッケージへのナビゲーションを許可 | | ✅ | |
-
-### SaveDialogOptions
-
-```go
-type SaveDialogOptions struct {
- DefaultDirectory string
- DefaultFilename string
- Title string
- Filters []FileFilter
- ShowHiddenFiles bool
- CanCreateDirectories bool
- TreatPackagesAsDirectories bool
-}
-```
-
-| Field | Description | Win | Mac | Lin |
-| -------------------------- | ------------------------- | --- | --- | --- |
-| DefaultDirectory | ダイアログが開かれたときに初期表示するディレクトリ | ✅ | ✅ | ✅ |
-| DefaultFilename | デフォルトファイル名 | ✅ | ✅ | ✅ |
-| Title | ダイアログのタイトル | ✅ | ✅ | ✅ |
-| [Filters](#filefilter) | ファイルフィルタのリスト | ✅ | ✅ | ✅ |
-| ShowHiddenFiles | システムの隠しファイルを表示 | | ✅ | ✅ |
-| CanCreateDirectories | ユーザによるディレクトリの作成を許可する | | ✅ | |
-| TreatPackagesAsDirectories | パッケージへのナビゲーションを許可 | | ✅ | |
-
-### MessageDialogOptions
-
-```go
-type MessageDialogOptions struct {
- Type DialogType
- Title string
- Message string
- Buttons []string
- DefaultButton string
- CancelButton string
-}
-```
-
-| Field | Description | Win | Mac | Lin |
-| ------------- | ------------------------------------------------- | -------------- | --- | --- |
-| Type | メッセージダイアログの種類 (質問、情報など) | ✅ | ✅ | ✅ |
-| Title | ダイアログのタイトル | ✅ | ✅ | ✅ |
-| Message | ユーザに表示するメッセージ | ✅ | ✅ | ✅ |
-| Buttons | ボタンテキストのリスト | | ✅ | |
-| DefaultButton | 指定されたテキストのボタンをデフォルトボタンとして扱う。 Bound to `return`. | ✅[*](#windows) | ✅ | |
-| CancelButton | 指定されたテキストのボタンをキャンセルボタンとして扱う。 `escape`キーにバインドされます。 | | ✅ | |
-
-#### Windows
-
-Windowsでは、ボタンのカスタマイズができない標準ダイアログタイプがあります。 The value returned will be one of: "Ok", "Cancel", "Abort", "Retry", "Ignore", "Yes", "No", "Try Again" or "Continue".
-
-For Question dialogs, the default button is "Yes" and the cancel button is "No". This can be changed by setting the `DefaultButton` value to `"No"`.
-
-Example:
-```go
- result, err := runtime.MessageDialog(a.ctx, runtime.MessageDialogOptions{
- Type: runtime.QuestionDialog,
- Title: "Question",
- Message: "Do you want to continue?",
- DefaultButton: "No",
- })
-```
-
-#### Linux
-
-Linux has standard dialog types in which the buttons are not customisable. The value returned will be one of: "Ok", "Cancel", "Yes", "No"
-
-#### Mac
-
-A message dialog on Mac may specify up to 4 buttons. If no `DefaultButton` or `CancelButton` is given, the first button is considered default and is bound to the `return` key.
-
-For the following code:
-
-```go
-selection, err := runtime.MessageDialog(b.ctx, runtime.MessageDialogOptions{
- Title: "It's your turn!",
- Message: "Select a number",
- Buttons: []string{"one", "two", "three", "four"},
-})
-```
-
-1番目のボタンがデフォルトになります:
-
-```mdx-code-block
-
-
-
-
-```
-
-And if we specify `DefaultButton` to be "two":
-
-```go
-selection, err := runtime.MessageDialog(b.ctx, runtime.MessageDialogOptions{
- Title: "It's your turn!",
- Message: "Select a number",
- Buttons: []string{"one", "two", "three", "four"},
- DefaultButton: "two",
-})
-```
-
-the second button is shown as default. When `return` is pressed, the value "two" is returned.
-
-```mdx-code-block
-
-
-
-
-```
-
-If we now specify `CancelButton` to be "three":
-
-```go
-selection, err := runtime.MessageDialog(b.ctx, runtime.MessageDialogOptions{
- Title: "It's your turn!",
- Message: "Select a number",
- Buttons: []string{"one", "two", "three", "four"},
- DefaultButton: "two",
- CancelButton: "three",
-})
-```
-
-the button with "three" is shown at the bottom of the dialog. When `escape` is pressed, the value "three" is returned:
-
-```mdx-code-block
-
-
-
-
-
-
-```
-
-#### DialogType
-
-```go
-const (
- InfoDialog DialogType = "info"
- WarningDialog DialogType = "warning"
- ErrorDialog DialogType = "error"
- QuestionDialog DialogType = "question"
- )
-```
-
-### FileFilter
-
-```go
-type FileFilter struct {
- DisplayName string // Filter information EG: "Image Files (*.jpg, *.png)"
- Pattern string // semi-colon separated list of extensions, EG: "*.jpg;*.png"
-}
-```
-
-#### Windows
-
-Windows allows you to use multiple file filters in dialog boxes. Each FileFilter will show up as a separate entry in the dialog:
-
-```mdx-code-block
-
-
-
-
-
-
-```
-
-#### Linux
-
-Linux allows you to use multiple file filters in dialog boxes. Each FileFilter will show up as a separate entry in the dialog:
-
-```mdx-code-block
-
-
-
-
-
-
-```
-
-#### Mac
-
-Mac dialogs only have the concept of a single set of patterns to filter files. If multiple FileFilters are provided, Wails will use all the Patterns defined.
-
-Example:
-
-```go
- selection, err := runtime.OpenFileDialog(b.ctx, runtime.OpenDialogOptions{
- Title: "Select File",
- Filters: []runtime.FileFilter{
- {
- DisplayName: "Images (*.png;*.jpg)",
- Pattern: "*.png;*.jpg",
- }, {
- DisplayName: "Videos (*.mov;*.mp4)",
- Pattern: "*.mov;*.mp4",
- },
- },
- })
-```
-
-This will result in the Open File dialog using `*.png,*.jpg,*.mov,*.mp4` as a filter.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/reference/runtime/events.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/reference/runtime/events.mdx
deleted file mode 100644
index 48893b0b7..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/reference/runtime/events.mdx
+++ /dev/null
@@ -1,37 +0,0 @@
----
-sidebar_position: 2
----
-
-# イベント
-
-Wailsでは、GoまたはJavascriptによって発行および受信できる、一元化されたイベントシステムが用意されています。 必要に応じて、イベント発行時にデータを渡すことも可能です。 イベントリスナーは、そのデータをローカルデータ型で受け取ります。
-
-### EventsOn
-
-このメソッドは、指定されたイベント名のイベントリスナーを新たに設定します。 `eventName`という名前のイベントが[発行](#EventsEmit)されると、コールバックがトリガーされます。 イベント発行時にデータも付与されていた場合、そのデータはコールバックに渡されます。
-
-Go: `EventsOn(ctx context.Context, eventName string, callback func(optionalData ...interface{}))` JS: `EventsOn(eventName string, callback function(optionalData?: any))`
-
-### EventsOff
-
-このメソッドは、指定されたイベント名のイベントリスナー設定を解除します。引数の`additionalEventNames`を使用することで、複数のリスナーを一度に解除できます。
-
-Go: `EventsOff(ctx context.Context, eventName string, additionalEventNames ...string)` JS: `EventsOff(eventName string, ...additionalEventNames)`
-
-### EventsOnce
-
-このメソッドは、指定されたイベント名のイベントリスナーを新たに設定し、一度だけトリガーさせます。
-
-Go: `EventsOnce(ctx context.Context, eventName string, callback func(optionalData ...interface{}))` JS: `EventsOnce(eventName string, callback function(optionalData?: any))`
-
-### EventsOnMultiple
-
-このメソッドは、指定されたイベント名のイベントリスナーを新たに設定し、最大`counter`回だけトリガーします。
-
-Go: `EventsOnMultiple(ctx context.Context, eventName string, callback func(optionalData ...interface{}), counter int)` JS: `EventsOnMultiple(eventName string, callback function(optionalData?: any), counter int)`
-
-### EventsEmit
-
-このメソッドは、指定されたイベントを発行します。 必要に応じて、イベント発行時にデータを渡すこともできます。 このメソッドによって、任意のイベントリスナーをトリガーさせることができます。
-
-Go: `EventsEmit(ctx context.Context, eventName string, optionalData ...interface{})` JS: `EventsEmit(ctx context, optionalData function(optionalData?: any))`
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/reference/runtime/intro.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/reference/runtime/intro.mdx
deleted file mode 100644
index 855981f03..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/reference/runtime/intro.mdx
+++ /dev/null
@@ -1,90 +0,0 @@
----
-sidebar_position: 1
----
-
-# イントロダクション
-
-ランタイムは、アプリケーションにユーティリティメソッドを提供するライブラリです。 GoとJavascriptの両方にランタイムがあり、どちらにもほぼ同じメソッドが提供されています。
-
-ユーティリティメソッドには次のようなものがあります:
-
-- [ウィンドウ](window.mdx)
-- [Menu](menu.mdx)
-- [ダイアログ](dialog.mdx)
-- [イベント](events.mdx)
-- [Browser](browser.mdx)
-- [ログ](log.mdx)
-
-Goのランタイムは、`github.com/wailsapp/wails/v2/pkg/runtime`をインポートすることで利用できます。 このパッケージのすべてのメソッドは、1番目の引数でContextを渡す必要があります。 このContextは、[OnStartup](../options.mdx#onstartup)フック、または[OnDomReady](../options.mdx#ondomready)フックからあらかじめ取得しておいてください。
-
-:::info 備考
-
-
-[OnStartup](../options.mdx#onstartup)で提供されるContextは、ウィンドウが別のスレッドで初期化されているため、ランタイムが機能する保証がありません。 起動時にランタイムメソッドを呼び出したい場合は、[OnDomReady](../options.mdx#ondomready)を使用してください。
-
-:::
-
-
-Javascriptのランタイムは、`window.runtime`マップを介してフロントエンド上で利用できます。 `dev`モードでは、Typescript型定義を提供するランタイムパッケージが生成されます。 これらは、フロントエンドディレクトリの`wailsjs`ディレクトリに配置しておく必要があります。
-
-### 非表示
-
-Go: `Hide(ctx context.Context)` JS: `Hide()`
-
-アプリケーションを非表示にします。
-
-:::info 備考
-
-
-Macでこのメソッドを使用すると、標準のMacアプリケーションにおけるメニュー項目の`Hide`と同じ方法で、アプリケーションが非表示になります。 これはウィンドウの非表示とは異なりますが、アプリケーションはフォアグラウンドに残ったままになります。 WindowsおよびLinuxでは、`WindowHide`メソッドと同等です。
-
-:::
-
-
-### 表示
-
-アプリケーションを表示します。
-
-:::info 備考
-
-
-Macでこのメソッドを使用すると、アプリケーションがフォアグラウンドに戻ります。 WindowsおよびLinuxでは、`WindowShow`メソッドと同等です。
-
-:::
-
-
-Go: `Show(ctx context.Context)` JS: `Show()`
-
-### 終了
-
-アプリケーションを終了します。
-
-Go: `Quit(ctx context.Context)` JS: `Quit()`
-
-### 環境
-
-現在の環境の詳細情報を取得します。
-
-Go: `Environment(ctx context.Context) EnvironmentInfo` JS: `Environment(): Promise`
-
-#### EnvironmentInfo
-
-Go:
-
-```go
-type EnvironmentInfo struct {
- BuildType string
- Platform string
- Arch string
-}
-```
-
-JS:
-
-```ts
-interface EnvironmentInfo {
- buildType: string;
- platform: string;
- arch: string;
-}
-```
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/reference/runtime/log.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/reference/runtime/log.mdx
deleted file mode 100644
index 057aa802a..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/reference/runtime/log.mdx
+++ /dev/null
@@ -1,130 +0,0 @@
----
-sidebar_position: 3
----
-
-# ログ
-
-Wailsでは、GoまたはJavascriptから呼び出すことのできるロギングメカニズムを用意しています。 一般的なロガーと同じように、ログにはいくつかのログレベルがあります:
-
-- トレース
-- デバッグ
-- 情報
-- 警告
-- Error
-- 致命的
-
-ロガーは、設定されている出力ログレベル以上のログメッセージを出力します。 例えば、出力ログレベルを`Debug`に設定した場合、`Trace`以外のすべてのレベルのメッセージが出力されます。
-
-### LogPrint
-
-指定されたメッセージをRawメッセージとしてロギングします。
-
-Go: `LogPrint(ctx context.Context, message string)` JS: `LogPrint(message: string)`
-
-### LogPrintf
-
-指定されたメッセージをRawメッセージとしてロギングします。
-
-Go: `LogPrintf(ctx context.Context, format string, args ...interface{})`
-
-### LogTrace
-
-指定されたメッセージを`Trace`ログレベルでロギングします。
-
-Go: `LogTrace(ctx context.Context, message string)` JS: `LogTrace(message: string)`
-
-### LogTracef
-
-指定されたメッセージを`Trace`ログレベルでロギングします。
-
-Go: `LogTracef(ctx context.Context, format string, args ...interface{})`
-
-### LogDebug
-
-指定されたメッセージを`Debug`ログレベルでロギングします。
-
-Go: `LogDebug(ctx context.Context, message string)` JS: `LogDebug(message: string)`
-
-### LogDebugf
-
-指定されたメッセージを`Debug`ログレベルでロギングします。
-
-Go: `LogDebugf(ctx context.Context, format string, args ...interface{})`
-
-### LogInfo
-
-指定されたメッセージを`Info`ログレベルでロギングします。
-
-Go: `LogInfo(ctx context.Context, message string)` JS: `LogInfo(message: string)`
-
-### LogInfof
-
-指定されたメッセージを`Info`ログレベルでロギングします。
-
-Go: `LogInfof(ctx context.Context, format string, args ...interface{})`
-
-### LogWarning
-
-指定されたメッセージを`Warning`ログレベルでロギングします。
-
-Go: `LogWarning(ctx context.Context, message string)` JS: `LogWarning(message: string)`
-
-### LogWarningf
-
-指定されたメッセージを`Warning`ログレベルでロギングします。
-
-Go: `LogWarningf(ctx context.Context, format string, args ...interface{})`
-
-### LogError
-
-指定されたメッセージを`Error`ログレベルでロギングします。
-
-Go: `LogError(ctx context.Context, message string)` JS: `LogError(message: string)`
-
-### LogErrorf
-
-指定されたメッセージを`Error`ログレベルでロギングします。
-
-Go: `LogErrorf(ctx context.Context, format string, args ...interface{})`
-
-### LogFatal
-
-指定されたメッセージを`Fatal`ログレベルでロギングします。
-
-Go: `LogFatal(ctx context.Context, message string)` JS: `LogFatal(message: string)`
-
-### LogFatalf
-
-指定されたメッセージを`Fatal`ログレベルでロギングします。
-
-Go: `LogFatalf(ctx context.Context, format string, args ...interface{})`
-
-### LogSetLogLevel
-
-出力ログレベルを設定します。 Javascriptでは、数値が次のログレベルに対応しています:
-
-| 値 | ログレベル |
-| - | ----- |
-| 1 | トレース |
-| 2 | デバッグ |
-| 3 | 情報 |
-| 4 | 警告 |
-| 5 | Error |
-
-Go: `LogSetLogLevel(ctx context.Context, level logger.LogLevel)` JS: `LogSetLogLevel(level: number)`
-
-## カスタムロガーの使用
-
-カスタムロガーは、アプリケーションオプションの1つである[Logger](../options.mdx#logger)で指定してあげることで、使用することができます。 カスタムロガーを使用する際の唯一の要件は、`github.com/wailsapp/wails/v2/pkg/logger`で定義されている`logger.Logger`インターフェースを、ロガーに実装することです:
-
-```go title="logger.go"
-type Logger interface {
- Print(message string)
- Trace(message string)
- Debug(message string)
- Info(message string)
- Warning(message string)
- Error(message string)
- Fatal(message string)
-}
-```
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/reference/runtime/menu.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/reference/runtime/menu.mdx
deleted file mode 100644
index 0d2b40a7d..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/reference/runtime/menu.mdx
+++ /dev/null
@@ -1,27 +0,0 @@
----
-sidebar_position: 6
----
-
-# Menu
-
-これらは、アプリケーションメニューに関連したメソッドです。
-
-:::info Javascript
-
-
-現在、Javascriptランタイムではメニューをサポートしていません。
-
-:::
-
-
-### MenuSetApplicationMenu
-
-指定された[menu](../menus.mdx)をアプリケーションメニューとして設定します。
-
-Go: `MenuSetApplicationMenu(ctx context.Context, menu *menu.Menu)`
-
-### MenuUpdateApplicationMenu
-
-`MenuSetApplicationMenu`に渡されたメニューへの変更を検知し、アプリケーションメニューを更新します。
-
-Go: `MenuUpdateApplicationMenu(ctx context.Context)`
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/reference/runtime/window.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/reference/runtime/window.mdx
deleted file mode 100644
index daa3027fc..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/reference/runtime/window.mdx
+++ /dev/null
@@ -1,223 +0,0 @@
----
-sidebar_position: 4
----
-
-# ウィンドウ
-
-アプリケーションウィンドウを制御できるメソッド群です。
-
-### WindowSetTitle
-
-ウィンドウのタイトルバーにテキストを設定します。
-
-Go: `WindowSetTitle(ctx context.Context, title string)` JS: `WindowSetTitle(title: string)`
-
-### WindowFullscreen
-
-ウィンドウをフルスクリーンにします。
-
-Go: `WindowFullscreen(ctx context.Context)` JS: `WindowFullscreen()`
-
-### WindowUnfullscreen
-
-フルスクリーンにする前のウィンドウサイズおよび位置に戻します。
-
-Go: `WindowUnfullscreen(ctx context.Context)` JS: `WindowUnfullscreen()`
-
-### WindowIsFullscreen
-
-ウィンドウがフルスクリーンの場合は、trueを返します。
-
-Go: `WindowIsFullscreen(ctx context.Context) bool` JS: `WindowIsFullscreen() bool`
-
-### WindowCenter
-
-ウィンドウが現在表示されているモニターの中央に、ウィンドウを配置させます。
-
-Go: `WindowReload(ctx context.Context)` JS: `WindowReload()`
-
-### WindowExecJS
-
-Executes arbitrary JS code in the window.
-
-This method runs the code in the browser asynchronously and returns immediately. If the script causes any errors, they will only be available in the browser console.
-
-Go: `WindowExecJS(ctx context.Context, js string)`
-
-### WindowReload
-
-リロードします。(現在表示されているページをリロード)
-
-Go: `WindowReloadApp(ctx context.Context)` JS: `WindowReloadApp()`
-
-### WindowReloadApp
-
-アプリケーションフロントエンドをリロードします。
-
-Go: `WindowSetSystemDefaultTheme(ctx context.Context)` JS: `WindowSetSystemDefaultTheme()`
-
-### WindowSetSystemDefaultTheme
-
-Windowsのみ使用可能。
-
-Go: `WindowSetDarkTheme(ctx context.Context)` JS: `WindowSetDarkTheme()`
-
-ウィンドウのテーマをシステムデフォルト(ダーク/ライト) に設定します。
-
-### WindowSetLightTheme
-
-Windowsのみ使用可能。
-
-Go: `WindowSetLightTheme(ctx context.Context)` JS: `WindowSetLightTheme()`
-
-ウィンドウのテーマをライトに設定します。
-
-### WindowSetDarkTheme
-
-Windowsのみ使用可能。
-
-Go: `WindowShow(ctx context.Context)` JS: `WindowShow()`
-
-ウィンドウのテーマをダークに設定します。
-
-### WindowShow
-
-ウィンドウが非表示になっている場合は、表示させます。
-
-Go: `WindowHide(ctx context.Context)` JS: `WindowHide()`
-
-### WindowHide
-
-現在表示されているウィンドウを非表示にします。
-
-Go: `WindowSetSize(ctx context.Context, width int, height int)` JS: `WindowSetSize(size: Size)`
-
-### WindowIsNormal
-
-ウィンドウが最小化、最大化、またはフルスクリーンになっていない場合、trueを返します。
-
-Go: `WindowIsNormal(ctx context.Context) bool` JS: `WindowIsNormal() bool`
-
-### WindowSetSize
-
-ウィンドウの幅と高さを設定します。
-
-Go: `WindowSetMaxSize(ctx context.Context, width int, height int)` JS: `WindowSetMaxSize(size: Size)`
-
-### WindowGetSize
-
-ウィンドウの幅と高さを取得します。
-
-Go: `WindowGetSize(ctx context.Context) (width int, height int)` JS: `WindowGetSize() : Size`
-
-### WindowSetMinSize
-
-ウィンドウの最小サイズを設定します。 現在のウィンドウサイズが、指定された最小サイズよりも小さい場合、現在のウィンドウサイズは変更されます。
-
-サイズを`0,0`に設定すると、サイズの制約が無効化されます。
-
-Go: `WindowSetAlwaysOnTop(ctx context.Context, b bool)` JS: `WindowSetAlwaysOnTop(b: Boolen)`
-
-### WindowSetMaxSize
-
-ウィンドウの最大サイズを設定します。 現在のウィンドウサイズが、指定された最大サイズよりも大きい場合、現在のウィンドウサイズは変更されます。
-
-サイズを`0,0`に設定すると、サイズの制約が無効化されます。
-
-Go: `WindowSetPosition(ctx context.Context, x int, y int)` JS: `WindowSetPosition(position: Position)`
-
-### WindowSetAlwaysOnTop
-
-ウィンドウを常に最前面に表示するかを切り替えます。
-
-Go: `WindowSetAlwaysOnTop(ctx context.Context, b bool)` JS: `WindowSetAlwaysOnTop(b: Boolen)`
-
-### WindowSetPosition
-
-現在ウィンドウが表示されているモニターに対する、相対的なウィンドウ位置を設定します。
-
-Go: `WindowMaximise(ctx context.Context)` JS: `WindowMaximise()`
-
-### WindowGetPosition
-
-現在ウィンドウが表示されているモニターに対する、相対的なウィンドウ位置を取得します。
-
-Go: `WindowGetPosition(ctx context.Context) (x int, y int)` JS: `WindowGetPosition() : Position`
-
-### WindowMaximise
-
-ウィンドウを最大化します。
-
-Go: `WindowToggleMaximise(ctx context.Context)` JS: `WindowToggleMaximise()`
-
-### WindowUnmaximise
-
-ウィンドウの最大化を解除し、最大化する前のサイズおよび位置に戻します。
-
-Go: `WindowMinimise(ctx context.Context)` JS: `WindowMinimise()`
-
-### WindowIsMaximised
-
-ウィンドウが最大化している場合はtrueを返します。
-
-Go: `WindowIsMaximised(ctx context.Context) bool` JS: `WindowIsMaximised() bool`
-
-### WindowToggleMaximise
-
-最大化の状態を切り替えます。
-
-Go: `WindowToggleMaximise(ctx context.Context)` JS: `WindowToggleMaximise()`
-
-### WindowMinimise
-
-ウィンドウを最小化します。
-
-Go: `WindowSetBackgroundColour(ctx context.Context, R, G, B, A uint8)` JS: `WindowSetBackgroundColour(R, G, B, A)`
-
-### WindowUnminimise
-
-ウィンドウの最小化を解除し、最小化する前のサイズおよび位置に戻します。
-
-Go: `WindowUnminimise(ctx context.Context)` JS: `WindowUnminimise()`
-
-### WindowIsMinimised
-
-ウィンドウが最小化している場合はtrueを返します。
-
-Go: `WindowIsMinimised(ctx context.Context) bool` JS: `WindowIsMinimised() bool`
-
-### WindowSetBackgroundColour
-
-ウィンドウの背景色をRGBAカラー定義で設定します。 この色は、すべての透過ピクセルに対して表示されます。
-
-R、G、B、Aの有効な値の範囲は0~255です。
-
-:::info Windows
-
-
-Windowsの場合、0または255のアルファ値(A) のみがサポートされています。 0以外の値を指定すると、すべて255とみなされます。
-
-:::
-
-
-Go: `WindowSetBackgroundColour(ctx context.Context, R, G, B, A uint8)` JS: `WindowSetBackgroundColour(R, G, B, A)`
-
-## Typescript型定義
-
-### Position
-
-```ts
-interface Position {
- x: number;
- y: number;
-}
-```
-
-### Size
-
-```ts
-interface Size {
- w: number;
- h: number;
-}
-```
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/tutorials/helloworld.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/tutorials/helloworld.mdx
deleted file mode 100644
index 3e198f06b..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/tutorials/helloworld.mdx
+++ /dev/null
@@ -1,124 +0,0 @@
----
-sidebar_position: 10
----
-
-# Hello World
-
-The aim of this tutorial is to get you up and running with the most basic application using Wails. You will be able to:
-
-- Create a new Wails application
-- Build the application
-- Run the application
-
-:::note
-
-
-This tutorial uses Windows as the target platform. Output will vary slightly depending on your operating system.
-
-:::
-
-
-## Create a new Wails application
-
-To create a new Wails application using the default vanilla JS template, you need to run the following command:
-
-```bash
-wails init -n helloworld
-```
-
-You should see something similar to the following:
-
-```
-Wails CLI v2.0.0
-
-Initialising Project 'helloworld'
----------------------------------
-
-Project Name: helloworld
-Project Directory: C:\Users\leaan\tutorial\helloworld
-Project Template: vanilla
-Template Support: https://wails.io
-
-Initialised project 'helloworld' in 232ms.
-```
-
-This will create a new directory called `helloworld` in the current directory. In this directory, you will find a number of files:
-
-```
-build/ - Contains the build files + compiled application
-frontend/ - Contains the frontend files
-app.go - Contains the application code
-main.go - The main program with the application configuration
-wails.json - The project configuration file
-go.mod - The go module file
-go.sum - The go module checksum file
-```
-
-## Build the application
-
-To build the application, change to the new `helloworld` project directory and run the following command:
-
-```bash
-wails build
-```
-
-You should see something like the following:
-
-```
-Wails CLI v2.0.0
-
-App Type: desktop
-Platforms: windows/amd64
-Compiler: C:\Users\leaan\go\go1.18.3\bin\go.exe
-Build Mode: Production
-Skip Frontend: false
-Compress: false
-Package: true
-Clean Build Dir: false
-LDFlags: ""
-Tags: []
-Race Detector: false
-
-Building target: windows/amd64
-------------------------------
- - Installing frontend dependencies: Done.
- - Compiling frontend: Done.
- - Generating bundle assets: Done.
- - Compiling application: Done.
-Built 'C:\Users\leaan\tutorial\helloworld\build\bin\helloworld.exe' in 10.616s.
-```
-
-This has compiled the application and saved it in the `build/bin` directory.
-
-## Run the application
-
-If we view the `build/bin` directory in Windows Explorer, we should see our project binary:
-
-```mdx-code-block
-
-
-
-
-```
-
-We can run it by simply double-clicking the `helloworld.exe` file.
-
-On Mac, Wails generates a `helloworld.app` file which can be run by double-clicking it.
-
-On Linux, you can run the application using `./helloworld` from the `build/bin` directory.
-
-You should see the application working as expected:
-
-```mdx-code-block
-
-
-
-
-```
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/appendix/_category_.json b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/appendix/_category_.json
deleted file mode 100644
index 83af4ca28..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/appendix/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Appendix",
- "position": 70
-}
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/community/_category_.json b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/community/_category_.json
deleted file mode 100644
index 524986e1e..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/community/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Community",
- "position": 50
-}
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/community/links.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/community/links.mdx
deleted file mode 100644
index 4cd13bfa1..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/community/links.mdx
+++ /dev/null
@@ -1,25 +0,0 @@
----
-sidebar_position: 2
----
-
-# Links
-
-This page serves as a list for community related links. Please submit a PR (click `Edit this page` at the bottom) to submit links.
-
-## Awesome Wails
-
-The [definitive list](https://github.com/wailsapp/awesome-wails) of links related to Wails.
-
-## Support Channels
-
-- [Discord](https://discord.com/invite/JDdSxwjhGf)
-- [Github Issues](https://github.com/wailsapp/wails/issues)
-- [v2 Beta Discussion Board](https://github.com/wailsapp/wails/discussions/828)
-
-## Social Media
-
-- [Twitter](https://twitter.com/wailsapp)
-- [Wails Chinese Community QQ Group](https://qm.qq.com/cgi-bin/qm/qr?k=PmIURne5hFGNd7QWzW5qd6FV-INEjNJv&jump_from=webapi) - Group number: 1067173054
-
-## その他のチュートリアルや記事
-- [掲示板を作ってみる](https://blog.customct.com/building-bulletin-board)
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/_category_.json b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/_category_.json
deleted file mode 100644
index 276e283b7..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Showcase",
- "position": 1
-}
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/filehound.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/filehound.mdx
deleted file mode 100644
index 134365aaf..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/filehound.mdx
+++ /dev/null
@@ -1,16 +0,0 @@
-# FileHound Export Utility
-
-```mdx-code-block
-
-
-
-
-```
-
-[FileHound Export Utility](https://www.filehound.co.uk/) FileHound is a cloud document management platform made for secure file retention, business process automation and SmartCapture capabilities.
-
-The FileHound Export Utility allows FileHound Administrators the ability to run a secure document and data extraction tasks for alternative back-up and recovery purposes. This application will download all documents and/or meta data saved in FileHound based on the filters you choose. The metadata will be exported in both JSON and XML formats.
-
-Backend built with: Go 1.15 Wails 1.11.0 go-sqlite3 1.14.6 go-linq 3.2
-
-Frontend with: Vue 2.6.11 Vuex 3.4.0 Typescript Tailwind 1.9.6
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/community/templates.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/community/templates.mdx
deleted file mode 100644
index ee4349843..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/community/templates.mdx
+++ /dev/null
@@ -1,56 +0,0 @@
----
-sidebar_position: 1
----
-
-# テンプレート
-
-このページでは、コミュニティがサポートしているテンプレートを紹介しています。 このページに新たにテンプレートを含めたい場合は、このページの下側にある`このページを編集`をクリックして、プルリクエストを出してください。 独自テンプレートの作成方法については、[テンプレート](../guides/templates.mdx)ガイドをご覧ください。
-
-これらのテンプレートを使用するには、`wails init -n "プロジェクト名" -t [テンプレートのリンク[@バージョン]]`コマンドを実行してください。
-
-バージョンサフィックスが無い場合は、デフォルトで、メインブランチのコードテンプレートが使用されます。 バージョンサフィックスがある場合は、当該バージョンのタグに対応するコードテンプレートが使用されます。
-
-例: `wails init -n "プロジェクト名" -t https://github.com/misitebao/wails-template-vue`
-
-:::warning 注意
-
-**Wailsプロジェクトでは、サードパーティ製テンプレートのメンテナンスは行っておらず、責任も負いません!**
-
-テンプレートについてよく分からない場合は、`package.json`および`wails.json`を確認し、どのようなスクリプトが実行されるのかや、どのようなパッケージがインストールされるのかを調べてください。
-
-:::
-
-## Vue
-
-- [wails-template-vue](https://github.com/misitebao/wails-template-vue) - VueのエコシステムをベースにしたWailsテンプレート (TypeScript、ダークテーマ、i18n、シングルページルーティング、TailwindCSSを統合)
-- [wails-vite-vue-ts](https://github.com/codydbentley/wails-vite-vue-ts) - Viteを使用したVue 3 TypeScript (および機能を追加する手順)
-- [wails-vite-vue-the-works](https://github.com/codydbentley/wails-vite-vue-the-works) - Vite、Vuex、Vue Router、SaaS、ESLint + Prettier を使用した Vue 3 TypeScript
-- [wails-template-quasar-js](https://github.com/sgosiaco/wails-template-quasar-js) - A template using JavaScript + Quasar V2 (Vue 3, Vite, Sass, Pinia, ESLint, Prettier)
-- [wails-template-quasar-ts](https://github.com/sgosiaco/wails-template-quasar-ts) - A template using TypeScript + Quasar V2 (Vue 3, Vite, Sass, Pinia, ESLint, Prettier, Composition API with <script setup>)
-
-## Angular
-
-- [wails-angular-template](https://github.com/TAINCER/wails-angular-template) - TypeScript、Sass、ホットリロード、コード分割、i18n を使用した Angular
-
-## React
-
-- [wails-react-template](https://github.com/AlienRecall/wails-react-template) - reactjsを使用したテンプレート
-- [wails-react-template](https://github.com/flin7/wails-react-template) - ライブ開発をサポートしたReactの最小テンプレート
-- [wails-template-nextjs](https://github.com/LGiki/wails-template-nextjs) - Next.js、TypeScript を使用したテンプレート
-- [wails-vite-react-ts-tailwind-template](https://github.com/hotafrika/wails-vite-react-ts-tailwind-template) - React + TypeScript + Vite + TailwindCSSを使用したテンプレート
-
-## Svelte
-
-- [wails-svelte-template](https://github.com/raitonoberu/wails-svelte-template) - Svelteを使用したテンプレート
-- [wails-vite-svelte-template](https://github.com/BillBuilt/wails-vite-svelte-template) - SvelteおよびViteを使用したテンプレート
-- [wails-vite-svelte-tailwind-template](https://github.com/BillBuilt/wails-vite-svelte-tailwind-template) - TailwindCSS v3を含んだ、SvelteおよびViteを使用したテンプレート
-- [wails-sveltekit-template](https://github.com/h8gi/wails-sveltekit-template) - SvelteKitを使用したテンプレート
-
-## Elm
-
-- [wails-elm-template](https://github.com/benjamin-thomas/wails-elm-template) - 関数型プログラミングと**高速な**ホットリロードを使ったGUIアプリ開発 :tada: :rocket:
-- [wails-template-elm-tailwind](https://github.com/rnice01/wails-template-elm-tailwind) - Elm + Tailwind CSS + Wailsのパワー:muscle:を組み合わせたテンプレート (ホットリロードサポートあり)
-
-## ピュアJavaScript (バニラ)
-
-- [wails-pure-js-template](https://github.com/KiddoV/wails-pure-js-template) - 基本的なJavaScript、HTML、CSSのみを含むテンプレート
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/gettingstarted/_category_.json b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/gettingstarted/_category_.json
deleted file mode 100644
index 597b920df..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/gettingstarted/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Getting Started",
- "position": 10
-}
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/gettingstarted/building.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/gettingstarted/building.mdx
deleted file mode 100644
index dfab958b4..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/gettingstarted/building.mdx
+++ /dev/null
@@ -1,22 +0,0 @@
----
-sidebar_position: 6
----
-
-# プロジェクトのコンパイル
-
-プロジェクトディレクトリ上で、`wails build`コマンドを実行しましょう。 そうすることで、プロジェクトがコンパイルされ、`build/bin`ディレクトリ内に本番配布用のバイナリが出力されます。
-
-バイナリを起動すると、デフォルト仕様のアプリを確認することができます:
-
-```mdx-code-block
-
-
-
-
-```
-
-コンパイルオプションについて詳しくは、[CLIリファレンス](../reference/cli.mdx#build)をご覧ください。
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/gettingstarted/development.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/gettingstarted/development.mdx
deleted file mode 100644
index b26c3c546..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/gettingstarted/development.mdx
+++ /dev/null
@@ -1,16 +0,0 @@
----
-sidebar_position: 5
----
-
-# アプリの開発
-
-プロジェクトディレクトリのルート上で`wails dev`コマンドを実行すると、アプリを開発モードで起動することができます。 コマンドを実行すると下記の処理が実行されます:
-
-- アプリをビルドしたのち、起動する
-- Goのコードをフロントエンドにバインドし、Javascriptから呼び出せるようにする
-- Using the power of [Vite](https://vitejs.dev/), will watch for modifications in your Go files and rebuild/re-run on change
-- ブラウザからアプリを操作できるようにする[Webサーバ](http://localhost:34115)を立ち上げる。 これにより、任意のブラウザ拡張機能を利用できる。 JavascriptのコンソールからGoのコードを呼び出すこともできる
-
-アプリ開発を始めるときは、プロジェクトディレクトリ上で`wails dev`コマンドを実行しましょう。 詳しくは、[こちら](../reference/cli.mdx#dev)をご覧ください。
-
-近日中にチュートリアルを公開予定です。
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/gettingstarted/firstproject.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/gettingstarted/firstproject.mdx
deleted file mode 100644
index 8ce6453d7..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/gettingstarted/firstproject.mdx
+++ /dev/null
@@ -1,130 +0,0 @@
----
-sidebar_position: 2
----
-
-# プロジェクトの開始
-
-## プロジェクトの生成
-
-CLIのインストールが終わったら、`wails init`コマンドで新しいプロジェクトを生成しましょう。
-
-好きなフレームワークを選択してください:
-
-```mdx-code-block
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-
-
-
- Generate a Svelte project using Javascript with:
-
- wails init -n myproject -t svelte
-
-If you would rather use Typescript:
-
- wails init -n myproject -t svelte-ts
-
-
-
- Generate a React project using Javascript with:
-
- wails init -n myproject -t react
-
-If you would rather use Typescript:
-
- wails init -n myproject -t react-ts
-
-
-
- Generate a Vue project using Javascript with:
-
- wails init -n myproject -t vue
-
-If you would rather use Typescript:
-
- wails init -n myproject -t vue-ts
-
-
-
- Generate a Preact project using Javascript with:
-
- wails init -n myproject -t preact
-
-If you would rather use Typescript:
-
- wails init -n myproject -t preact-ts
-
-
-
- Generate a Lit project using Javascript with:
-
- wails init -n myproject -t lit
-
-If you would rather use Typescript:
-
- wails init -n myproject -t lit-ts
-
-
-
- Generate a Vanilla project using Javascript with:
-
- wails init -n myproject -t vanilla
-
-If you would rather use Typescript:
-
- wails init -n myproject -t vanilla-ts
-
-
-
-```
-
-
-
-様々な機能やフレームワークを提供する[コミュニティテンプレート](../community/templates.mdx)を利用することもできます。
-
-プロジェクト生成時に使用可能なオプションを確認するには、`wails init -help`を実行してください。 詳しくは、[CLIリファレンス](../reference/cli.mdx#init)を参照してください。
-
-## プロジェクトのディレクトリ構成
-
-Wailsのプロジェクトディレクトリの構成は次のとおりです:
-
-```
-.
-├── build/
-│ ├── appicon.png
-│ ├── darwin/
-│ └── windows/
-├── frontend/
-├── go.mod
-├── go.sum
-├── main.go
-└── wails.json
-```
-
-### プロジェクトの構造
-
-- `/main.go` - アプリのメインコード
-- `/frontend/` - フロントエンドのプロジェクトディレクトリ
-- `/build/` - ビルドディレクトリ
-- `/build/appicon.png` - アプリアイコン
-- `/build/darwin/` - Mac固有のプロジェクトディレクトリ
-- `/build/windows/` - Windows固有のプロジェクトディレクトリ
-- `/wails.json` - プロジェクト構成ファイル
-- `/go.mod` - Goモジュール定義ファイル
-- `/go.sum` - Goモジュールチェックサムファイル
-
-`frontend`ディレクトリ内は、Wailsで決まったファイル構成等は無く、お好きなフロントエンドプロジェクトを配置することができます。
-
-`build`ディレクトリは、アプリのビルド時に使用されます。 この中のファイルは、ビルドの挙動をカスタマイズするために、適宜ファイル内容を書き換えることができます。 buildディレクトリ内のファイルを削除すると、デフォルトのファイルが再生成されます。
-
-`go.mod`のモジュール名は、最初は"changeme"になっています。 このモジュール名は、あなたのプロジェクトに適切な名前に変更しましょう。
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/gettingstarted/installation.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/gettingstarted/installation.mdx
deleted file mode 100644
index c273f836d..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/gettingstarted/installation.mdx
+++ /dev/null
@@ -1,89 +0,0 @@
----
-sidebar_position: 1
----
-
-# インストール
-
-## サポートされているプラットフォーム
-
-- Windows 10/11 AMD64/ARM64
-- MacOS 10.13+ AMD64
-- MacOS 11.0+ ARM64
-- Linux AMD64/ARM64
-
-## 依存関係
-
-Wailsをインストールする前に、下記のものを導入しておく必要があります。
-
-- Go 1.18+
-- NPM (Node 15+)
-
-### Go
-
-Download Go from the [Go Downloads Page](https://go.dev/dl/).
-
-公式の[Goインストール手順](https://go.dev/doc/install)に従って、Goをインストールしてください。 その際、`PATH`環境変数に`~/go/bin`ディレクトリへのパスが含まれていることも確認してください。 それらが終わったら、ターミナルを再起動し、以下の確認をしてください:
-
-- Goが正しくインストールされているかを確認する: `go version`
-- "~/go/bin"のディレクトリパスがPATH環境変数に含まれているか確認する: `echo $PATH | grep go/bin`
-
-### NPM
-
-[Nodeダウンロードページ](https://nodejs.org/ja/download/)からNPMをダウンロードしてください。 最新版を利用することをお勧めします。なぜなら、私たちは最新版に対してテストを実施しているためです。
-
-`npm --version`を実行して、インストールが完了しているかを確認してください。
-
-## プラットフォーム固有の依存関係
-
-開発作業を行うプラットフォームによって、必要な依存関係が存在します:
-
-```mdx-code-block
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-
-
-
- Wails requires that the xcode command line tools are installed. This can be
- done by running xcode-select --install.
-
-
- Wails requires that the WebView2 runtime is installed. Some Windows installations will already have this installed. You can check using the wails doctor command.
-
-
- Linux required the standard gcc build tools plus libgtk3 and libwebkit. Rather than list a ton of commands for different distros, Wails can try to determine what the installation commands are for your specific distribution. Run wails doctor after installation to be shown how to install the dependencies. If your distro/package manager is not supported, please consult the Add Linux Distro guide.
-
-
-```
-
-## 任意の依存関係
-
-- [UPX](https://upx.github.io/)を導入することで、構築したアプリを圧縮できます。
-
-## Wailsのインストール
-
-`go install github.com/wailsapp/wails/v2/cmd/wails@latest`を実行して、Wails CLIをインストールしてください。
-
-Note: If you get an error similar to this:
-
-```shell
-....\Go\pkg\mod\github.com\wailsapp\wails\v2@v2.1.0\pkg\templates\templates.go:28:12: pattern all:ides/*: no matching files found
-```
-please check you have Go 1.18+ installed:
-```shell
-go version
-```
-
-## システムチェック
-
-`wails doctor`を実行すると、必要な依存関係が正しくインストールされているかを確認することができます。 正しくインストールされていない場合は、その内容をあなたにお知らせして、どうすれば解決できるかを教えてくれます。
-
-## `wails`コマンドが見つからないのですが?
-
-`wails`コマンドが見つからないとシステムに怒られた場合は、Goが、公式のGoインストール手順に従って導入されているかを確認してください。 コマンドが見つからないほとんどの理由は、あなたのホームディレクトリ配下にある`go/bin`ディレクトリのパスが、`PATH`環境変数に含まれていないからです。 また、インストールによって行われた環境変更を反映させるために、もともと開いていたコマンドプロンプト(ターミナル)がある場合はそれらをいったん閉じて、再度開きなおしてください。
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/_category_.json b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/_category_.json
deleted file mode 100644
index 5935dad93..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Guides",
- "position": 50
-}
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/application-development.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/application-development.mdx
deleted file mode 100644
index a618076f1..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/application-development.mdx
+++ /dev/null
@@ -1,194 +0,0 @@
-# Application Development
-
-There are no hard and fast rules for developing applications with Wails, but there are some basic guidelines.
-
-## Application Setup
-
-The pattern used by the default templates are that `main.go` is used for configuring and running the application, whilst `app.go` is used for defining the application logic.
-
-The `app.go` file will define a struct that has 2 methods which act as hooks into the main application:
-
-```go title="app.go"
-type App struct {
- ctx context.Context
-}
-
-func NewApp() *App {
- return &App{}
-}
-
-func (a *App) startup(ctx context.Context) {
- a.ctx = ctx
-}
-
-func (a *App) shutdown(ctx context.Context) {
-}
-```
-
-- The startup method is called as soon as Wails allocates the resources it needs and is a good place for creating resources, setting up event listeners and anything else the application needs at startup. It is given a `context.Context` which is usually saved in a struct field. This context is needed for calling the [runtime](../reference/runtime/intro.mdx). If this method returns an error, the application will terminate. In dev mode, the error will be output to the console.
-
-- The shutdown method will be called by Wails right at the end of the shutdown process. This is a good place to deallocate memory and perform any shutdown tasks.
-
-The `main.go` file generally consists of a single call to `wails.Run()`, which accepts the application configuration. The pattern used by the templates is that before the call to `wails.Run()`, an instance of the struct we defined in `app.go` is created and saved in a variable called `app`. This configuration is where we add our callbacks:
-
-```go {3,9,10} title="main.go"
-func main() {
-
- app := NewApp()
-
- err := wails.Run(&options.App{
- Title: "My App",
- Width: 800,
- Height: 600,
- OnStartup: app.startup,
- OnShutdown: app.shutdown,
- })
- if err != nil {
- log.Fatal(err)
- }
-}
-
-```
-
-More information on application lifecycle hooks can be found [here](../howdoesitwork.mdx#application-lifecycle-callbacks).
-
-## Binding Methods
-
-It is likely that you will want to call Go methods from the frontend. This is normally done by adding public methods to the already defined struct in `app.go`:
-
-```go {16-18} title="app.go"
-type App struct {
- ctx context.Context
-}
-
-func NewApp() *App {
- return &App{}
-}
-
-func (a *App) startup(ctx context.Context) {
- a.ctx = ctx
-}
-
-func (a *App) shutdown(ctx context.Context) {
-}
-
-func (a *App) Greet(name string) string {
- return fmt.Sprintf("Hello %s!", name)
-}
-```
-
-In the main application configuration, the `Bind` key is where we can tell Wails what we want to bind:
-
-```go {11-13} title="main.go"
-func main() {
-
- app := NewApp()
-
- err := wails.Run(&options.App{
- Title: "My App",
- Width: 800,
- Height: 600,
- OnStartup: app.startup,
- OnShutdown: app.shutdown,
- Bind: []interface{}{
- app,
- },
- })
- if err != nil {
- log.Fatal(err)
- }
-}
-
-```
-
-This will bind all public methods in our `App` struct (it will never bind the startup and shutdown methods).
-
-### Dealing with context when binding multiple structs
-
-If you want to bind methods for multiple structs but want each struct to keep a reference to the context so that you can use the runtime functions, a good pattern is to pass the context from the `OnStartup` method to your struct instances :
-
-```go
-func main() {
-
- app := NewApp()
- otherStruct := NewOtherStruct()
-
- err := wails.Run(&options.App{
- Title: "My App",
- Width: 800,
- Height: 600,
- OnStartup: func(ctx context.Context){
- app.SetContext(ctx)
- otherStruct.SetContext(ctx)
- },
- OnShutdown: app.shutdown,
- Bind: []interface{}{
- app,
- otherStruct
- },
- })
- if err != nil {
- log.Fatal(err)
- }
-}
-```
-
-More information on Binding can be found [here](../howdoesitwork.mdx#method-binding).
-
-## Application Menu
-
-Wails supports adding a menu to your application. This is done by passing a [Menu](../reference/menus.mdx#menu) struct to application config. It's common to use a method that returns a Menu, and even more common for that to be a method on the `App` struct used for the lifecycle hooks.
-
-```go {11} title="main.go"
-func main() {
-
- app := NewApp()
-
- err := wails.Run(&options.App{
- Title: "My App",
- Width: 800,
- Height: 600,
- OnStartup: app.startup,
- OnShutdown: app.shutdown,
- Menu: app.menu(),
- Bind: []interface{}{
- app,
- },
- })
- if err != nil {
- log.Fatal(err)
- }
-}
-
-```
-
-## Assets
-
-The great thing about the way Wails v2 handles assets is that it doesn't! The only thing you need to give Wails is an `embed.FS`. How you get to that is entirely up to you. You can use vanilla html/css/js files like the vanilla template. You could have some complicated build system, it doesn't matter.
-
-When `wails build` is run, it will check the `wails.json` project file at the project root. There are 2 keys in the project file that are read:
-
-- "frontend:install"
-- "frontend:build"
-
-The first, if given, will be executed in the `frontend` directory to install the node modules. The second, if given, will be executed in the `frontend` directory to build the frontend project.
-
-If these 2 keys aren't given, then Wails does absolutely nothing with the frontend. It is only expecting that `embed.FS`.
-
-### AssetsHandler
-
-A Wails v2 app can optionally define a `http.Handler` in the `options.App`, which allows hooking into the AssetServer to create files on the fly or process POST/PUT requests. GET requests are always first handled by the `assets` FS. If the FS doesn't find the requested file the request will be forwarded to the `http.Handler` for serving. Any requests other than GET will be directly processed by the `AssetsHandler` if specified. It's also possible to only use the `AssetsHandler` by specifiy `nil` as the `Assets` option.
-
-## Built in Dev Server
-
-Running `wails dev` will start the built in dev server which will start a file watcher in your project directory. By default, if any file changes, wails checks if it was an application file (default: `.go`, configurable with `-e` flag). If it was, then it will rebuild your application and relaunch it. If the changed file was in the assets, it will issue a reload after a short amount of time.
-
-The dev server uses a technique called "debouncing" which means it doesn't reload straight away, as there may be multiple files changed in a short amount of time. When a trigger occurs, it waits for a set amount of time before issuing a reload. If another trigger happens, it resets to the wait time again. By default this value is `100ms`. If this value doesn't work for your project, it can be configured using the `-debounce` flag. If used, this value will be saved to your project config and become the default.
-
-## External Dev Server
-
-Some frameworks come with their own live-reloading server, however they will not be able to take advantage of the Wails Go bindings. In this scenario, it is best to run a watcher script that rebuilds the project into the build directory, which Wails will be watching. For an example, see the default svelte template that uses [rollup](https://rollupjs.org/guide/en/). For [create-react-app](https://create-react-app.dev/), it's possible to use [this script](https://gist.github.com/int128/e0cdec598c5b3db728ff35758abdbafd) to achieve a similar result.
-
-## Go Module
-
-The default Wails templates generate a `go.mod` file that contains the module name "changeme". You should change this to something more appropriate after project generation.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/bleeding-edge.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/bleeding-edge.mdx
deleted file mode 100644
index b81cc79dc..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/bleeding-edge.mdx
+++ /dev/null
@@ -1,55 +0,0 @@
-# Bleeding Edge
-
-## Overview
-
-Wails is in constant development and new releases are regularly "tagged". This usually happens when all the newer code on `master` has been tested and confirmed working. If you need a bugfix or feature that has not yet made it to a release, it's possible to use the latest "bleeding edge" version using the following steps:
-
-- `git clone https://github.com/wailsapp/wails`
-- `cd wails/v2/cmd/wails`
-- `go install`
-
-NOTE: The directory that you cloned the project into will now be called "clonedir".
-
-The Wails CLI will now be at the very latest version.
-
-### Updating your project
-
-To update projects to use the latest version of the Wails library, update the project's `go.mod` and ensure the following line is at the bottom of the file:
-
-`replace github.com/wailsapp/wails/v2 => `
-
-Example:
-
-On Windows: `replace github.com/wailsapp/wails/v2 => C:\Users\leaan\Documents\wails-v2-beta\wails\v2`
-
-On 'nix: `replace github.com/wailsapp/wails/v2 => /home/me/projects/wails/v2`
-
-To revert to a stable version, run:
-
-`go install github.com/wailsapp/wails/v2/cmd/wails@latest`
-
-## Testing a Branch
-
-If you want to test a branch, follow the instructions above, but ensure you switch the branch you want to test before installing:
-
-- `git clone https://github.com/wailsapp/wails`
-- `cd wails`
-- `git checkout -b branch-to-test --track origin/branch-to-test`
-- `cd v2/cmd/wails`
-- `go install`
-
-Make sure you [update your project](#updating-your-project) as described above.
-
-## Testing a PR
-
-If you want to test a PR, follow the instructions above, but ensure you fetch the PR and switch the branch before installing. Please replace `[IDofThePR]` with the ID of the PR shown on github.com:
-
-- `git clone https://github.com/wailsapp/wails`
-- `cd wails`
-- `git fetch -u origin pull/[IDofThePR]/head:test/pr-[IDofThePR]`
-- `git checkout test/pr-[IDofThePR]`
-- `git reset --hard HEAD`
-- `cd v2/cmd/wails`
-- `go install`
-
-Make sure you [update your project](#updating-your-project) as described above.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/frontend.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/frontend.mdx
deleted file mode 100644
index 29e442c5e..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/frontend.mdx
+++ /dev/null
@@ -1,75 +0,0 @@
-# Frontend
-
-## Script Injection
-
-When Wails serves your `index.html`, by default, it will inject 2 script entries into the `` tag to load `/wails/ipc.js` and `/wails/runtime.js`. These files install the bindings and runtime respectively.
-
-The code below shows where these are injected by default:
-
-```html
-
-
- injection example
-
-
-
-
-
-
-
-
Please enter your name below 👇
-
-
-
-
-
-
-
-
-
-```
-
-### Overriding Default Script Injection
-
-To provide more flexibility to developers, there is a meta tag that may be used to customise this behaviour:
-
-```html
-
-```
-
-The options are as follows:
-
-| 値 | Description |
-| ------------------- | ------------------------------------------------ |
-| noautoinjectruntime | Disable the autoinjection of `/wails/runtime.js` |
-| noautoinjectipc | Disable the autoinjection of `/wails/ipc.js` |
-| noautoinject | Disable all autoinjection of scripts |
-
-Multiple options may be used provided they are comma seperated.
-
-This code is perfectly valid and operates the same as the autoinjection version:
-
-```html
-
-
-
- injection example
-
-
-
-
-
-
-
Please enter your name below 👇
-
-
-
-
-
-
-
-
-
-
-
-```
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/linux.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/linux.mdx
deleted file mode 100644
index 229c282bf..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/linux.mdx
+++ /dev/null
@@ -1,18 +0,0 @@
-# Linux
-
-This page has miscellaneous guides related to developing Wails applications for Linux.
-
-## Video tag doesn't fire "ended" event
-
-When using a video tag, the "ended" event is not fired when the video is finished playing. This is a bug in WebkitGTK, however you can use the following workaround to fix it:
-
-```js
-videoTag.addEventListener("timeupdate", (event) => {
- if (event.target.duration - event.target.currentTime < 0.2) {
- let ended = new Event("ended");
- event.target.dispatchEvent(ended);
- }
-});
-```
-
-Source: [Lyimmi](https://github.com/Lyimmi) on the [discussions board](https://github.com/wailsapp/wails/issues/1729#issuecomment-1212291275)
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/manual-builds.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/manual-builds.mdx
deleted file mode 100644
index dcf192d33..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/manual-builds.mdx
+++ /dev/null
@@ -1,95 +0,0 @@
-# Manual Builds
-
-The Wails CLI does a lot of heavy lifting for the project, but sometimes it's desirable to manually build your project. This document will discuss the different operations the CLI does and how this may be achieved in different ways.
-
-## Build Process
-
-When either `wails build` or `wails dev` are used, the Wails CLI performs a common build process:
-
- - Install frontend dependencies
- - Build frontend project
- - Generate build assets
- - Compile application
- - [optional] Compress application
-
-### Install frontend dependencies
-
-#### CLI Steps
-
-- If the `-s` flag is given, this step is skipped
-- Checks `wails.json` to see if there is an install command in the key `frontend:install`
-- If there isn't, it skips this step
-- If there is, it checks if `package.json` exists in the frontend directory. If it doesn't exist, it skips this step
-- An MD5 sum is generated from the `package.json` file contents
-- It checks for the existence of `package.json.md5` and if it exists, will compare the contents of it (an MD5 sum) with the one generated to see if the contents have changed. If they are the same, this step is skipped
-- If `package.json.md5` does not exist, it creates it using the generated MD5 sum
-- If a build is now required, or `node_modules` does not exist, or the `-f` flag is given, the install command is executed in the frontend directory
-
-#### Manual Steps
-
-This step could be done from the command line or a script with `npm install`.
-
-### Build frontend project
-
-#### Wails CLI
-
-- If the `-s` flag is given, this step is skipped
-- Checks `wails.json` to see if there is a build command in the key `frontend:build`
-- If there isn't, it skips this step
-- If there is, it is executed in the frontend directory
-
-#### Manual Steps
-
-This step could be done from the command line or a script with `npm run build` or whatever the frontend build script is.
-
-### Generate assets
-
-#### Wails CLI
-
-- If `-nopackage` flag is set, this stage is skipped
-- If the `build/appicon.png` file does not exist, a default one is created
-- For Windows, see [Bundling for Windows](#windows)
-- If `build/windows/icon.ico` does not exist, it will create it from the `build/appicon.png` image.
-
-##### Windows
-
-- If `build/windows/icon.ico` does not exist, it will create it from `build/appicon.png` using icon sizes of 256, 128, 64, 48, 32 and 16. This is done using [winicon](https://github.com/leaanthony/winicon).
-- If the `build/windows/.manifest` file does not exist, it creates it from a default version.
-- Compiles the application as a production build (above)
-- Uses [winres](https://github.com/tc-hib/winres) to bundle the icon and manifest into a `.syso` file ready for linking.
-
-#### Manual Steps
-
-- Create `icon.ico` using the [winicon](https://github.com/leaanthony/winicon) CLI tool (or any other tool).
-- Create / Update a `.manifest` file for your application
-- Use the [winres CLI](https://github.com/tc-hib/go-winres) to generate a `.syso` file.
-
-### Compile application
-
-#### Wails CLI
-
-- If the `-clean` flag is provided, the `build` directory is deleted and recreated
-- For `wails dev`, the following default Go flags are used: `-tags dev -gcflags "all=-N -l"`
-- For `wails build`, the following default Go flags are used: `-tags desktop,production -ldflags "-w -s"`
- - On Windows, `-ldflags "-w -h -H windowsgui"`
-- Additional tags passed to the CLI using `-tags` are added to the defaults
-- Additional ldflags passed to the CLI using `-ldflags` are added to the defaults
-- The `-o` flag is passed through
-- The Go compiler specified by `-compiler` will be used for compilation
-
-#### Manual steps
-
-- For dev build, the minimum command would be: `go build -tags dev -gcflags "all=-N -l"`
-- For production build, the minimum command would be: `go build -tags desktop,production -ldflags "-w -s -H windowsgui"`
-- Ensure that you compile in the same directory as the `.syso` file
-
-### Compress application
-
-#### Wails CLI
-
-- If the `-upx` flag has been given, the `upx` program will be run to compress the application with the default settings
-- If `-upxflags` is also passed, these flags are used instead of the default ones
-
-#### Manual steps
-
-- Run `upx [flags]` manually to compress the application.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/migrating.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/migrating.mdx
deleted file mode 100644
index f9b132127..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/migrating.mdx
+++ /dev/null
@@ -1,191 +0,0 @@
-# Migrating from v1
-
-## Overview
-
-Wails v2 is a significant change from v1. This document aims to highlight the changes and the steps in migrating an existing project.
-
-### Creating the Application
-
-In v1, the main application is created using `wails.CreateApp`, bindings are added with `app.Bind`, then the application is run using `app.Run()`.
-
-Example:
-
-```go title="v1"
- app := wails.CreateApp(&wails.AppConfig{
- Title: "MyApp",
- Width: 1024,
- Height: 768,
- JS: js,
- CSS: css,
- Colour: "#131313",
- })
- app.Bind(basic)
- app.Run()
-```
-
-In v2, there is just a single method, `wails.Run()`, that accepts [application options](../reference/options.mdx#application-options).
-
-```go title="v2"
- err := wails.Run(&options.App{
- Title: "MyApp",
- Width: 800,
- Height: 600,
- AssetServer: &assetserver.Options{
- Assets: assets,
- },
- Bind: []interface{}{
- basic,
- },
- })
-```
-
-### Binding
-
-In v1, it was possible to bind both arbitrary functions and structs. In v2, this has been simplified to only binding structs. The struct instances that were previously passed to the `Bind()` method in v1, are now specified in the `Bind` field of the [application options](../reference/options.mdx#application-options):
-
-```go title="v1"
- app := wails.CreateApp(/* options */)
- app.Bind(basic)
-```
-
-```go title="v2"
- err := wails.Run(&options.App{
- /* other options */
- Bind: []interface{}{
- basic,
- },
- })
-```
-
-In v1, bound methods were available to the frontend at `window.backend`. This has changed to `window.go`.``
-
-### Application Lifecycle
-
-In v1, there were 2 special methods in a bound struct: `WailsInit()` and `WailsShutdown()`. These have been replaced with 3 lifecycle hooks as part of the [application options](../reference/options.mdx#application-options):
-
-- [OnStartup](../reference/options.mdx#onstartup)
-- [OnShutdown](../reference/options.mdx#onshutdown)
-- [OnDomReady](../reference/options.mdx#ondomready)
-
-Note: [OnDomReady](../reference/options.mdx#ondomready) replaces the `wails:ready` system event in v1.
-
-These methods can be standard functions, but a common practice is to have them part of a struct:
-
-```go title="v2"
- basic := NewBasicApp()
- err := wails.Run(&options.App{
- /* Other Options */
- OnStartup: basic.startup,
- OnShutdown: basic.shutdown,
- OnDomReady: basic.domready,
- })
-...
-type Basic struct {
- ctx context.Context
-}
-func (b *Basic) startup(ctx context.Context) {
- b.ctx = ctx
-}
-...
-```
-
-### Runtime
-
-The runtime in v2 is much richer than v1 with support for menus, window manipulation and better dialogs. The signature of the methods has changed slightly - please refer the the [Runtime Reference](../reference/runtime/intro.mdx).
-
-In v1, the [runtime](../reference/runtime/intro.mdx) was available via a struct passed to `WailsInit()`. In v2, the runtime has been moved out to its own package. Each method in the runtime takes the `context.Context` that is passed to the [OnStartup](../reference/options.mdx#onstartup) method.
-
-```go title="Runtime Example"
-package main
-
-import "github.com/wailsapp/wails/v2/pkg/runtime"
-
-type Basic struct {
- ctx context.Context
-}
-
-// startup is called at application startup
-func (a *App) startup(ctx context.Context) {
- a.ctx = ctx
- runtime.LogInfo(ctx, "Application Startup called!")
-}
-
-```
-
-### Assets
-
-The _biggest_ change in v2 is how assets are handled.
-
-In v1, assets were passed via 2 application options:
-
-- `JS` - The application's Javascript
-- `CSS` - The application's CSS
-
-This meant that the responsibility of generating a single JS and CSS file was on the developer. This essentially required the use of complicated packers such as webpack.
-
-In v2, Wails makes no assumptions about your frontend assets, just like a webserver. All of your application assets are passed to the application options as an `embed.FS`.
-
-**This means there is no requirement to bundle your assets, encode images as Base64 or attempt the dark art of bundler configuration to use custom fonts**.
-
-At startup, Wails will scan the given `embed.FS` for `index.html` and use its location as the root path for all the other application assets - just like a webserver would.
-
-Example: An application has the following project layout. All final assets are placed in the `frontend/dist` directory:
-
-```shell
-.
-├── build/
-├── frontend/
-│ └── dist/
-│ ├── index.html
-│ ├── main.js
-│ ├── main.css
-│ └── logo.svg
-├── main.go
-└── wails.json
-```
-
-Those assets may be used by the application by simply creating an `embed.FS`:
-
-```go title="Assets Example"
-//go:embed all:frontend/dist
-var assets embed.FS
-
-func main() {
- err := wails.Run(&options.App{
- /* Other Options */
- AssetServer: &assetserver.Options{
- Assets: assets,
- },
- })
-}
-```
-
-Of course, bundlers can be used if you wish to. The only requirement is to pass the final application assets directory to Wails using an `embed.FS` in the `Assets` key of the [application options](../reference/options.mdx#application-options).
-
-### Project Configuration
-
-In v1, the project configuration was stored in the `project.json` file in the project root. In v2, the project configuration is stored in the `wails.json` file in the project root.
-
-The format of the file is slightly different. Here is a comparison:
-
-
-
-| v1 | v2 | Notes |
-| ------------------ | ---------------- | --------------------------------------------------- |
-| name | name | |
-| description | | Removed |
-| author / name | author / name | |
-| author / email | author / email | |
-| version | version | |
-| binaryname | outputfilename | Changed |
-| frontend / dir | | Removed |
-| frontend / install | frontend:install | Changed |
-| frontend / build | frontend:build | Changed |
-| frontend / bridge | | Removed |
-| frontend / serve | | Removed |
-| tags | | Removed |
-| | wailsjsdir | The directory to generate wailsjs modules |
-| | assetdir | The directory of the compiled frontend assets for `dev` mode. This is normally inferred and could be left empty. |
-| | reloaddirs | Comma separated list of additional directories to watch for changes and to trigger reloads in `dev` mode. This is only needed for some more advanced asset configurations. |
-
-
-```
-
-## Publishing Templates
-
-Publishing a template is simply pushing the files to GitHub. The following best practice is encouraged:
-
-- Remove any unwanted files and directories (such as `.git`) from your frontend directory
-- Ensure that `template.json` is complete, especially `helpurl`
-- Push the files to GitHub
-- Create a PR on the [Community Templates](../community/templates.mdx) page
-- Announce the template on the [Template Announcement](https://github.com/wailsapp/wails/discussions/825) discussion board
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/troubleshooting.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/troubleshooting.mdx
deleted file mode 100644
index 250e84e94..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/troubleshooting.mdx
+++ /dev/null
@@ -1,162 +0,0 @@
-# Troubleshooting
-
-An assortment of troubleshooting tips.
-
-## `wails`コマンドが見つからないのですが?
-
-`wails`コマンドが見つからないとシステムに怒られた場合は、Goが、公式のGoインストール手順に従って導入されているかを確認してください。 コマンドが見つからないほとんどの理由は、あなたのホームディレクトリ配下にある`go/bin`ディレクトリのパスが、`PATH`環境変数に含まれていないからです。 また、インストールによって行われた環境変更を反映させるために、もともと開いていたコマンドプロンプト(ターミナル)がある場合はそれらをいったん閉じて、再度開きなおしてください。
-
-## My application is displaying a white/blank screen
-
-Check that your application includes the assets from the correct directory. In your `main.go` file, you will have something similar to the following code:
-
-```go
-//go:embed all:frontend/dist
-var assets embed.FS
-```
-
-Check that `frontend/dist` contains your application assets.
-
-### Mac
-
-If this happens on Mac, try adding the following to your `Info.plist`:
-
-```xml
-NSAppTransportSecurity
-
- NSAllowsLocalNetworking
-
-
-```
-
-Reference: https://github.com/wailsapp/wails/issues/1504#issuecomment-1174317433
-
-## Mac application not valid
-
-If your built application looks like this in finder:
-
-```mdx-code-block
-
-
-
-```
-
-it's likely that your application's `info.plist` is invalid. Update the file in `build/.app/Contents/info.plist` and check if the data is valid, EG check the binary name is correct. To persist the changes, copy the file back to the `build/darwin` directory.
-
-## Cannot call backend method from frontend with variadic arguments
-
-If you have a backend method defined with variadic parameters, eg:
-
-```go
-func (a *App) TestFunc(msg string, args ...interface{}) error {
- // Code
-}
-```
-
-calling this method from the frontend like this will fail:
-
-```js
-var msg = "Hello: ";
-var args = ["Go", "JS"];
-window.go.main.App.TestFunc(msg, ...args)
- .then((result) => {
- //do things here
- })
- .catch((error) => {
- //handle error
- });
-```
-
-Workaround:
-
-```js
-var msg = "Hello ";
-var args = ["Go", "JS"];
-window.go.main.App.TestFunc(msg, args)
- .then((result) => {
- //without the 3 dots
- //do things here
- })
- .catch((error) => {
- //handle error
- });
-```
-
-Credit: https://github.com/wailsapp/wails/issues/1186
-
-## I'm having getting proxy errors when trying to install Wails
-
-If you are getting errors like this:
-
-```
-"https://proxy.golang.org/github.com/wailsapp/wails/cmd/wails/@v/list": dial tcp 172.217.163.49:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
-```
-
-it's probably because the official Go Proxy is being blocked (Users in China have reported this). The solution is to set up the proxy manually, eg:
-
-```
-go env -w GO111MODULE=on
-go env -w GOPROXY=https://goproxy.cn,direct
-```
-
-Source: https://github.com/wailsapp/wails/issues/1233
-
-## The generated Typescript doesn't have the correct types
-
-Sometimes the generated Typescript doesn't have the correct types. To mitigate this, it is possible to specify what types should be generated using the `ts_type` struct tag. For more details, please read [this](https://github.com/tkrajina/typescriptify-golang-structs#custom-types).
-
-## When I navigate away from `index.html`, I am unable to call methods on the frontend
-
-If you navigate away from `index.html` to a new html file, the context will be lost. This can be fixed by adding the following imports to the `` section of any new page you navigate to:
-
-```html
-
-
-
-
-```
-
-Source: https://github.com/wailsapp/wails/discussions/1512
-
-## I get `too many open files` errors on my Mac when I run `wails dev`
-
-By default, macOS will only allow you to open a maximum of 256 files. This can affect the `wails dev` command. This limit can be increased by running: `ulimit -n 1024` in the terminal.
-
-FSNotify is [looking to move to Apple's fsevents](https://github.com/fsnotify/fsnotify/issues/11) for Mac. If this isn't completed soon, we will create our own implementation, tracked [here](https://github.com/wailsapp/wails/issues/1733).
-
-## My Mac app gives me weird compilation errors
-
-A few users have reported seeing compilation errors such as the following:
-
-```shell
-# github.com/wailsapp/wails/v2/internal/frontend/desktop/darwin
-In file included from ../../pkg/mod/github.com/wailsapp/wails/v2@v2.0.0-beta.44.2/internal/frontend/desktop/darwin/callbacks.go:9:
-In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX12.1.sdk/System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:12:
-/Library/Developer/CommandLineTools/SDKs/MacOSX12.1.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSBundle.h:91:143: error: function does not return NSString
-- (NSAttributedString *)localizedAttributedStringForKey:(NSString *)key value:(nullable NSString *)value table:(nullable NSString *)tableName NS_FORMAT_ARGUMENT(1) NS_REFINED_FOR_SWIFT API_AVAILABLE(macos(12.0), ios(15.0), watchos(8.0), tvos(15.0));
- ~~~~~~~~~~~~~~ ^ ~
-/Library/Developer/CommandLineTools/SDKs/MacOSX12.1.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSObjCRuntime.h:103:48: note: expanded from macro 'NS_FORMAT_ARGUMENT'
- #define NS_FORMAT_ARGUMENT(A) __attribute__ ((format_arg(A)))
-```
-
-This is _normally_ due to a mismatch with the OS version you are running and the version of the XCode Command Line Tools installed. If you see an error like this, try upgrading your XCode Command Line Tools to the latest version.
-
-If reinstalling Xcode Command Tools still fails, you can check the path where the toolkit is located using:
-
-`xcode-select -p`
-
-If `/Applications/Xcode.app/Contents/Developer` is displayed, run `sudo xcode-select --switch /Library/Developer/CommandLineTools`
-
-Sources: https://github.com/wailsapp/wails/issues/1806 and https://github.com/wailsapp/wails/issues/1140#issuecomment-1290446496
-
---
-
-## Cannot start service: Host version "x.x.x does not match binary version "x.x.x"
-
-It's preferable to add `frontend/node_modules` and `frontend/package-lock.json` to your `.gitignore`. Otherwise when opening your repository on another machine that may have different versions of Node installed, you may not be able to run your application.
-
-If this does happen, simply delete `frontend/node_modules` and `frontend/package-lock.json` and run your `wails build` or `wails dev` command again.
\ No newline at end of file
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/vscode.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/vscode.mdx
deleted file mode 100644
index ed258656d..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/vscode.mdx
+++ /dev/null
@@ -1,82 +0,0 @@
-
-# Visual Studio Code
-
-This page is for miscellaneous tips and tricks when using Visual Studio Code with Wails.
-
-## Vetur Configuration
-
-Many thanks to [@Lyimmi](https://github.com/Lyimmi) for this tip. Originally posted [here](https://github.com/wailsapp/wails/issues/1791#issuecomment-1228158349).
-
-Vetur is a popular plugin for Visual Studio Code that provides syntax highlighting and code completion for Vue projects. When loading a Wails project in VSCode, Vetur will throw an error as it is expecting to find the frontend project in the root directory. To fix this, you can do the following:
-
-Create a file named `vetur.config.js` in the project's root.
-
-```javascript
-// vetur.config.js
-/** @type {import('vls').VeturConfig} */
-module.exports = {
- // **optional** default: `{}`
- // override vscode settings
- // Notice: It only affects the settings used by Vetur.
- settings: {
- "vetur.useWorkspaceDependencies": true,
- "vetur.experimental.templateInterpolationService": true
- },
- // **optional** default: `[{ root: './' }]`
- // support monorepos
- projects: [
- {
- // **required**
- // Where is your project?
- // It is relative to `vetur.config.js`.
- // root: './packages/repo1',
- root: './frontend',
- // **optional** default: `'package.json'`
- // Where is `package.json` in the project?
- // We use it to determine the version of vue.
- // It is relative to root property.
- package: './package.json',
- // **optional**
- // Where is TypeScript config file in the project?
- // It is relative to root property.
- tsconfig: './tsconfig.json',
- // **optional** default: `'./.vscode/vetur/snippets'`
- // Where is vetur custom snippets folders?
- snippetFolder: './.vscode/vetur/snippets',
- // **optional** default: `[]`
- // Register globally Vue component glob.
- // If you set it, you can get completion by that components.
- // It is relative to root property.
- // Notice: It won't actually do it. You need to use `require.context` or `Vue.component`
- globalComponents: [
- './src/components/**/*.vue'
- ]
- }
- ]
-}
-```
-
-Next, configure `frontend/tsconfig.json`:
-
-```javascript
-{
- "compilerOptions": {
- "module": "system",
- "noImplicitAny": true,
- "removeComments": true,
- "preserveConstEnums": true,
- "sourceMap": true,
- "outFile": "../../built/local/tsc.js",
- "allowJs": true
- },
- "exclude": [
- "node_modules",
- "**/*.spec.ts"
- ],
- "include": [
- "src/**/*",
- "wailsjs/**/*.ts"
- ]
-}
-```
-This should enable you to now use Vetur as expected.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/windows-installer.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/windows-installer.mdx
deleted file mode 100644
index 88a1698db..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/windows-installer.mdx
+++ /dev/null
@@ -1,58 +0,0 @@
-# NSIS installer
-
-```mdx-code-block
-
-
-
-
-```
-
-Wails supports generating Windows installers using the [NSIS installer](https://nsis.sourceforge.io/).
-
-## Installing NSIS
-
-### Windows
-
-The installer is available on the [NSIS Download](https://nsis.sourceforge.io/Download) page.
-
-If you use the chocolatey package manager, run the following script:
-
-```
-choco install nsis
-```
-
-If you install NSIS manually, you need to add the _Bin_ folder, which contains `makensis.exe`, in your NSIS installation to your path. [Here](https://www.architectryan.com/2018/03/17/add-to-the-path-on-windows-10/) is a good tutorial on how to add to path on Windows.
-
-### Linux
-
-The `nsis` package should be available through your distribution's package manager.
-
-### MacOS
-
-NSIS is available to install through homebrew: `brew install nsis`.
-
-## Generating the installer
-
-When a new project is created, Wails generates the NSIS configuration files in `build/windows/installer`. The config data is read from `installer/info.json` and that is configured to use the project's `wails.json` Info section:
-
-```json
-// ...
- "Info": {
- "companyName": "My Company Name",
- "productName": "Wails Vite",
- "productVersion": "1.0.0",
- "copyright": "Copyright.........",
- "comments": "Built using Wails (https://wails.io)"
- },
-```
-
-To generate an installer for your application, use the `-nsis` flag with `wails build`:
-
-```
-wails build -nsis
-```
-
-The installer will now be available in the `build/bin` directory.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/windows.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/windows.mdx
deleted file mode 100644
index 821808c0b..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/windows.mdx
+++ /dev/null
@@ -1,61 +0,0 @@
-# Windows
-
-This page has miscellaneous guides related to developing Wails applications for Windows.
-
-## Handling the WebView2 Runtime Dependency
-
-Wails applications built for Windows have a runtime requirement on the Microsoft [WebView2 Runtime](https://developer.microsoft.com/en-us/microsoft-edge/webview2/). Windows 11 will have this installed by default, but some machines won't. Wails offers an easy approach to dealing with this dependency.
-
-By using the `-webview2` flag when building, you can decide what your application will do when a suitable runtime is not detected (including if the installed runtime is too old). The four options are:
-
-1. Download
-2. Embed
-3. Browser
-4. Error
-
-### Download
-
-This option will prompt the user that no suitable runtime has been found and then offer to download and run the official bootstrapper from Microsoft's WebView2 site. If the user proceeds, the official bootstrapper will be downloaded and run.
-
-### Embed
-
-This option embeds the official bootstrapper within the application. If no suitable runtime has been found, the application will offer to run the bootstrapper. This adds ~150k to the binary size.
-
-### Browser
-
-This option will prompt the user that no suitable runtime has been found and then offer to open a browser to the official WebView2 page where the bootstrapper can be downloaded and installed. The application will then exit, leaving the installation up to the user.
-
-### Error
-
-If no suitable runtime is found, an error is given to the user and no further action taken.
-
-## Fixed version runtime
-
-Another way of dealing with webview2 dependency is shipping it yourself. You can download [fixed version runtime](https://developer.microsoft.com/microsoft-edge/webview2/#download-section) and bundle or download it with your application.
-
-Also, you should specify path to fixed version of webview2 runtime in the `windows.Options` structure when launching wails.
-
-```go
- wails.Run(&options.App{
- Windows: &windows.Options{
- WebviewBrowserPath: "",
- },
- })
-```
-
-Note: When `WebviewBrowserPath` is specified, `error` strategy will be forced in case of minimal required version mismatch or invalid path to a runtime.
-
-## Spawning other programs
-
-When spawning other programs, such as scripts, you will see the window appear on the screen. To hide the window, you can use the following code:
-
-```go
-cmd := exec.Command("your_script.exe")
-cmd.SysProcAttr = &syscall.SysProcAttr{
- HideWindow: true,
- CreationFlags: 0x08000000,
-}
-cmd.Start()
-```
-
-Solution provided by [sithembiso](https://github.com/sithembiso) on the [discussions board](https://github.com/wailsapp/wails/discussions/1734#discussioncomment-3386172).
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/howdoesitwork.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/howdoesitwork.mdx
deleted file mode 100644
index b9037aec2..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/howdoesitwork.mdx
+++ /dev/null
@@ -1,369 +0,0 @@
----
-sidebar_position: 20
----
-
-# どうやって動いているの?
-
-Wailsは、webkitフロントエンドを備えた、何の変哲もないGoアプリです。 アプリ全体のうちGoの部分は、アプリのコードと、ウィンドウ制御などの便利な機能を提供するランタイムライブラリで構成されています。 フロントエンドはwebkitウィンドウであり、フロンドエンドアセットをウィンドウ上に表示します。 フロントエンドからも、Javascriptでランタイムライブラリを呼び出すことができます。 そして最終的に、Goのメソッドはフロントエンドにバインドされ、ローカルのJavascriptメソッドであるかのように、フロントエンドから呼び出すことができます。
-
-```mdx-code-block
-
-
-```
-
-When clicked, that will open an about message box:
-
-```mdx-code-block
-
-
-
-
-```
-
-### Linux
-
-[Linux固有のオプション](#linux)を定義します。
-
-名前: Linux データ型: `*linux.Options`
-
-#### Icon
-
-Sets up the icon representing the window. This icon is used when the window is minimized (also known as iconified).
-
-名前: Icon データ型: `[]byte`
-
-Some window managers or desktop environments may also place it in the window frame, or display it in other contexts. On others, the icon is not used at all, so your mileage may vary.
-
-NOTE: Gnome on Wayland at least does not display this icon. To have a application icon there, a `.desktop` file has to be used. On KDE it should work.
-
-The icon should be provided in whatever size it was naturally drawn; that is, don’t scale the image before passing it. Scaling is postponed until the last minute, when the desired final size is known, to allow best quality.
-
-#### WindowIsTranslucent
-
-Setting this to `true` will make the window background translucent. Some window managers may ignore it, or result in a black window.
-
-名前: WindowIsTranslucent データ型: `bool`
\ No newline at end of file
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/reference/project-config.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/reference/project-config.mdx
deleted file mode 100644
index 6084f6682..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/reference/project-config.mdx
+++ /dev/null
@@ -1,55 +0,0 @@
----
-sidebar_position: 5
----
-
-# Project Config
-
-The project config resides in the `wails.json` file in the project directory. The structure of the config is:
-
-```json
-{
- "name": "[The project name]",
- "assetdir": "[Relative path to the directory containing the compiled assets, this is normally inferred and could be left empty]",
- "reloaddirs": "[Additional directories to trigger reloads (comma separated), this is only used for some advanced asset configurations]",
- "frontend:install": "[The command to install node dependencies, run in the frontend directory - often `npm install`]",
- "frontend:build": "[The command to build the assets, run in the frontend directory - often `npm run build`]",
- "frontend:dev": "[This command has been replaced by frontend:dev:build. If frontend:dev:build is not specified will falls back to this command. \nIf this command is also not specified will falls back to frontend:build]",
- "frontend:dev:build": "[This command is the dev equivalent of frontend:build. If not specified falls back to frontend:dev]",
- "frontend:dev:install": "[This command is the dev equivalent of frontend:install. If not specified falls back to frontend:install]",
- "frontend:dev:watcher": "[This command is run in a separate process on `wails dev`. Useful for 3rd party watchers or starting 3d party dev servers]",
- "frontend:dev:serverUrl": "[URL to a 3rd party dev server to be used to serve assets, EG Vite. \nIf this is set to 'auto' then the devServerUrl will be inferred from the Vite output]",
- "wailsjsdir": "[Relative path to the directory that the auto-generated JS modules will be created]",
- "version": "[Project config version]",
- "outputfilename": "[The name of the binary]",
- "debounceMS": 100, // The default time the dev server waits to reload when it detects a change in assets
- "devServer": "[Address to bind the wails dev sever to. Default: localhost:34115]",
- "appargs": "[Arguments passed to the application in shell style when in dev mode]",
- "runNonNativeBuildHooks": false, // Defines if build hooks should be run though they are defined for an OS other than the host OS.
- "preBuildHooks": {
- "GOOS/GOARCH": "[The command that will be executed before a build of the specified GOOS/GOARCH: ${platform} is replaced with the "GOOS/GOARCH". The "GOOS/GOARCH" hook is executed before the "GOOS/*" and "*/*" hook.]",
- "GOOS/*": "[The command that will be executed before a build of the specified GOOS: ${platform} is replaced with the "GOOS/GOARCH". The "GOOS/*" hook is executed before the "*/*" hook.]",
- "*/*": "[The command that will be executed before every build: ${platform} is replaced with the "GOOS/GOARCH".]"
- },
- "postBuildHooks": {
- "GOOS/GOARCH": "[The command that will be executed after a build of the specified GOOS/GOARCH: ${platform} is replaced with the "GOOS/GOARCH" and ${bin} with the path to the compiled binary. The "GOOS/GOARCH" hook is executed before the "GOOS/*" and "*/*" hook.]",
- "GOOS/*": "[The command that will be executed after a build of the specified GOOS: ${platform} is replaced with the "GOOS/GOARCH" and ${bin} with the path to the compiled binary. The "GOOS/*" hook is executed before the "*/*" hook.]",
- "*/*": "[The command that will be executed after every build: ${platform} is replaced with the "GOOS/GOARCH" and ${bin} with the path to the compiled binary.]"
- },
- "info": { // Data used to populate manifests and version info.
- "companyName": "[The company name. Default: [The project name]]",
- "productName": "[The product name. Default: [The project name]]",
- "productVersion": "[The version of the product. Default: '1.0.0']",
- "copyright": "[The copyright of the product. Default: 'Copyright.........']",
- "comments": "[A short comment of the app. Default: 'Built using Wails (https://wails.app)']"
- },
- "nsisType": "['multiple': One installer per architecture. 'single': Single universal installer for all architectures being built. Default: 'multiple']",
- "obfuscated": "[Whether the app should be obfuscated. Default: false]",
- "garbleargs": "[The arguments to pass to the garble command when using the obfuscated flag]"
-}
-```
-
-This file is read by the Wails CLI when running `wails build` or `wails dev`.
-
-The `assetdir`, `reloaddirs`, `wailsjsdir`, `debounceMS`, `devserver` and `frontenddevserverurl` flags in `wails build/dev` will update the project config and thus become defaults for subsequent runs.
-
-The JSON Schema for this file is located [here](https://wails.io/schemas/config.v2.json).
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/reference/runtime/_category_.json b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/reference/runtime/_category_.json
deleted file mode 100644
index ac6d55488..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/reference/runtime/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Runtime",
- "position": 1
-}
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/reference/runtime/browser.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/reference/runtime/browser.mdx
deleted file mode 100644
index 39ae7e0a9..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/reference/runtime/browser.mdx
+++ /dev/null
@@ -1,13 +0,0 @@
----
-sidebar_position: 7
----
-
-# Browser
-
-これらは、システムブラウザに関連したメソッドです。
-
-### BrowserOpenURL
-
-指定されたURLをシステムブラウザで開きます。
-
-Go: `BrowserOpenURL(ctx context.Context, url string)` JS: `BrowserOpenURL(url string)`
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/reference/runtime/dialog.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/reference/runtime/dialog.mdx
deleted file mode 100644
index 997acad0e..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/reference/runtime/dialog.mdx
+++ /dev/null
@@ -1,302 +0,0 @@
----
-sidebar_position: 5
----
-
-# ダイアログ
-
-ランタイムでは、ファイルセレクターやメッセージボックスといったネイティブダイアログへのアクセスを提供しています。
-
-:::info Javascript
-
-現在、Javascriptランタイムではダイアログをサポートしていません。
-
-:::
-
-### OpenDirectoryDialog
-
-ユーザにディレクトリの選択を求めるダイアログを開きます。 [OpenDialogOptions](#opendialogoptions)を使用してカスタマイズできます。
-
-Go: `OpenDirectoryDialog(ctx context.Context, dialogOptions OpenDialogOptions) (string, error)`
-
-返り値: 選択されたディレクトリ(キャンセルされた場合は空) またはエラー
-
-### OpenFileDialog
-
-ユーザにファイルの選択を求めるダイアログを開きます。 [OpenDialogOptions](#opendialogoptions)を使用してカスタマイズできます。
-
-Go: `OpenFileDialog(ctx context.Context, dialogOptions OpenDialogOptions) (string, error)`
-
-返り値: 選択されたファイル(キャンセルされた場合は空) またはエラー
-
-### OpenMultipleFilesDialog
-
-ユーザに複数ファイルの選択を求めるダイアログを開きます。 [OpenDialogOptions](#opendialogoptions)を使用してカスタマイズできます。
-
-Go: `OpenMultipleFilesDialog(ctx context.Context, dialogOptions OpenDialogOptions) ([]string, error)`
-
-返り値: 選択された複数ファイル(キャンセルされた場合はnil) またはエラー
-
-### SaveFileDialog
-
-保存の目的でユーザにファイル名を入力選択させるダイアログを開きます。 [SaveDialogOptions](#savedialogoptions)を使用してカスタマイズできます。
-
-Go: `SaveFileDialog(ctx context.Context, dialogOptions SaveDialogOptions) (string, error)`
-
-返り値: 入力選択されたファイル(キャンセルされた場合は空) またはエラー
-
-### MessageDialog
-
-メッセージダイアログを使用してメッセージを表示します。 [MessageDialogOptions](#messagedialogoptions)を使用してカスタマイズできます。
-
-Go: `MessageDialog(ctx context.Context, dialogOptions MessageDialogOptions) (string, error)`
-
-返り値: 選択されたボタンのテキストまたはエラー
-
-## オプション
-
-### OpenDialogOptions
-
-```go
-type OpenDialogOptions struct {
- DefaultDirectory string
- DefaultFilename string
- Title string
- Filters []FileFilter
- ShowHiddenFiles bool
- CanCreateDirectories bool
- ResolvesAliases bool
- TreatPackagesAsDirectories bool
-}
-```
-
-| Field | Description | Win | Mac | Lin |
-| -------------------------- | ------------------------- | --- | --- | --- |
-| DefaultDirectory | ダイアログが開かれたときに初期表示するディレクトリ | ✅ | ✅ | ✅ |
-| DefaultFilename | デフォルトファイル名 | ✅ | ✅ | ✅ |
-| Title | ダイアログのタイトル | ✅ | ✅ | ✅ |
-| [Filters](#filefilter) | ファイルフィルタのリスト | ✅ | ✅ | ✅ |
-| ShowHiddenFiles | システムの隠しファイルを表示 | | ✅ | ✅ |
-| CanCreateDirectories | ユーザによるディレクトリの作成を許可する | | ✅ | |
-| ResolvesAliases | エイリアスではなくファイルパスを返す | | ✅ | |
-| TreatPackagesAsDirectories | パッケージへのナビゲーションを許可 | | ✅ | |
-
-### SaveDialogOptions
-
-```go
-type SaveDialogOptions struct {
- DefaultDirectory string
- DefaultFilename string
- Title string
- Filters []FileFilter
- ShowHiddenFiles bool
- CanCreateDirectories bool
- TreatPackagesAsDirectories bool
-}
-```
-
-| Field | Description | Win | Mac | Lin |
-| -------------------------- | ------------------------- | --- | --- | --- |
-| DefaultDirectory | ダイアログが開かれたときに初期表示するディレクトリ | ✅ | ✅ | ✅ |
-| DefaultFilename | デフォルトファイル名 | ✅ | ✅ | ✅ |
-| Title | ダイアログのタイトル | ✅ | ✅ | ✅ |
-| [Filters](#filefilter) | ファイルフィルタのリスト | ✅ | ✅ | ✅ |
-| ShowHiddenFiles | システムの隠しファイルを表示 | | ✅ | ✅ |
-| CanCreateDirectories | ユーザによるディレクトリの作成を許可する | | ✅ | |
-| TreatPackagesAsDirectories | パッケージへのナビゲーションを許可 | | ✅ | |
-
-### MessageDialogOptions
-
-```go
-type MessageDialogOptions struct {
- Type DialogType
- Title string
- Message string
- Buttons []string
- DefaultButton string
- CancelButton string
-}
-```
-
-| Field | Description | Win | Mac | Lin |
-| ------------- | ------------------------------------------------- | -------------- | --- | --- |
-| Type | メッセージダイアログの種類 (質問、情報など) | ✅ | ✅ | ✅ |
-| Title | ダイアログのタイトル | ✅ | ✅ | ✅ |
-| Message | ユーザに表示するメッセージ | ✅ | ✅ | ✅ |
-| Buttons | ボタンテキストのリスト | | ✅ | |
-| DefaultButton | 指定されたテキストのボタンをデフォルトボタンとして扱う。 Bound to `return`. | ✅[*](#windows) | ✅ | |
-| CancelButton | 指定されたテキストのボタンをキャンセルボタンとして扱う。 `escape`キーにバインドされます。 | | ✅ | |
-
-#### Windows
-
-Windowsでは、ボタンのカスタマイズができない標準ダイアログタイプがあります。 The value returned will be one of: "Ok", "Cancel", "Abort", "Retry", "Ignore", "Yes", "No", "Try Again" or "Continue".
-
-For Question dialogs, the default button is "Yes" and the cancel button is "No". This can be changed by setting the `DefaultButton` value to `"No"`.
-
-Example:
-```go
- result, err := runtime.MessageDialog(a.ctx, runtime.MessageDialogOptions{
- Type: runtime.QuestionDialog,
- Title: "Question",
- Message: "Do you want to continue?",
- DefaultButton: "No",
- })
-```
-
-#### Linux
-
-Linux has standard dialog types in which the buttons are not customisable. The value returned will be one of: "Ok", "Cancel", "Yes", "No"
-
-#### Mac
-
-A message dialog on Mac may specify up to 4 buttons. If no `DefaultButton` or `CancelButton` is given, the first button is considered default and is bound to the `return` key.
-
-For the following code:
-
-```go
-selection, err := runtime.MessageDialog(b.ctx, runtime.MessageDialogOptions{
- Title: "It's your turn!",
- Message: "Select a number",
- Buttons: []string{"one", "two", "three", "four"},
-})
-```
-
-1番目のボタンがデフォルトになります:
-
-```mdx-code-block
-
-
-
-
-```
-
-And if we specify `DefaultButton` to be "two":
-
-```go
-selection, err := runtime.MessageDialog(b.ctx, runtime.MessageDialogOptions{
- Title: "It's your turn!",
- Message: "Select a number",
- Buttons: []string{"one", "two", "three", "four"},
- DefaultButton: "two",
-})
-```
-
-the second button is shown as default. When `return` is pressed, the value "two" is returned.
-
-```mdx-code-block
-
-
-
-
-```
-
-If we now specify `CancelButton` to be "three":
-
-```go
-selection, err := runtime.MessageDialog(b.ctx, runtime.MessageDialogOptions{
- Title: "It's your turn!",
- Message: "Select a number",
- Buttons: []string{"one", "two", "three", "four"},
- DefaultButton: "two",
- CancelButton: "three",
-})
-```
-
-the button with "three" is shown at the bottom of the dialog. When `escape` is pressed, the value "three" is returned:
-
-```mdx-code-block
-
-
-
-
-
-
-```
-
-#### DialogType
-
-```go
-const (
- InfoDialog DialogType = "info"
- WarningDialog DialogType = "warning"
- ErrorDialog DialogType = "error"
- QuestionDialog DialogType = "question"
- )
-```
-
-### FileFilter
-
-```go
-type FileFilter struct {
- DisplayName string // Filter information EG: "Image Files (*.jpg, *.png)"
- Pattern string // semi-colon separated list of extensions, EG: "*.jpg;*.png"
-}
-```
-
-#### Windows
-
-Windows allows you to use multiple file filters in dialog boxes. Each FileFilter will show up as a separate entry in the dialog:
-
-```mdx-code-block
-
-
-
-
-
-
-```
-
-#### Linux
-
-Linux allows you to use multiple file filters in dialog boxes. Each FileFilter will show up as a separate entry in the dialog:
-
-```mdx-code-block
-
-```
-
-**[EncryptEasy](https://www.encrypteasy.app) is a simple and easy to use PGP encryption tool, managing all your and your contacts keys. Encryption should be simple. Developed with Wails.**
-
-Encrypting messages using PGP is the industry standard. Everyone has a private and a public key. Your private key, well, needs to be kept private so only you can read messages. Your public key is distributed to anyone who wants to send you secret, encrypted messages. Managing keys, encrypting messages and decrypting messages should be a smooth experience. EncryptEasy is all about making it easy.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/minecraftupdater.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/minecraftupdater.mdx
deleted file mode 100644
index 2f6c7c72b..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/minecraftupdater.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
-# Minecraft Updater
-
-```mdx-code-block
-
-
-
-
-```
-
-[Minecraft Updater](https://github.com/Gurkengewuerz/MinecraftModUpdater) is a utility tool to update and synchronize Minecraft mods for your userbase. It’s built using Wails2 and React with [antd](https://ant.design/) as frontend framework.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/optimus.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/optimus.mdx
deleted file mode 100644
index 4f87479d6..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/optimus.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Optimus
-
-```mdx-code-block
-
-
-
-
-```
-
-[Optimus](https://github.com/splode/optimus) is a desktop image optimization application. It supports conversion and compression between WebP, JPEG, and PNG image formats.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/portfall.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/portfall.mdx
deleted file mode 100644
index 03e740f4c..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/portfall.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Portfall
-
-```mdx-code-block
-
-
-
-
-```
-
-[Portfall](https://github.com/rekon-oss/portfall) - A desktop k8s port-forwarding portal for easy access to all your cluster UIs
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/riftshare.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/riftshare.mdx
deleted file mode 100644
index 9928b4785..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/riftshare.mdx
+++ /dev/null
@@ -1,21 +0,0 @@
-# RiftShare
-
-```mdx-code-block
-
-
-
-
-```
-
-Easy, Secure, and Free file sharing for everyone. Learn more at [Riftshare.app](https://riftshare.app)
-
-## Features
-
-- Easy secure file sharing between computers both in the local network and through the internet
-- Supports sending files or directories securely through the [magic wormhole protocol](https://magic-wormhole.readthedocs.io/en/latest/)
-- Compatible with all other apps using magic wormhole (magic-wormhole or wormhole-william CLI, wormhole-gui, etc.)
-- Automatic zipping of multiple selected files to send at once
-- Full animations, progress bar, and cancellation support for sending and receiving
-- Native OS File Selection
-- Open files in one click once received
-- Auto Update - don't worry about having the latest release!
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/scriptbar.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/scriptbar.mdx
deleted file mode 100644
index 2ccb2acb4..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/scriptbar.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# ScriptBar
-
-```mdx-code-block
-
-
-
-
-```
-
-[ScriptBar](https://GitHub.com/raguay/ScriptBarApp) is a program to show the output of the embedded [Node-Red](https://nodered.org) server in the [EmailIt](https://GitHub.com/raguay/EmailIt) application. It also displays the output of scripts on your system. ScriptBar doesn't put them in the menubar, but has them all in a convient window for easy viewing. You can have multiple tabs to have many different things show. You can also keep the links to your most visited web sites.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/wombat.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/wombat.mdx
deleted file mode 100644
index f100c55e2..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/wombat.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Wombat
-
-```mdx-code-block
-
-
-```
-
-コンパイルオプションについて詳しくは、[CLIリファレンス](../reference/cli.mdx#build)をご覧ください。
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/_category_.json b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/_category_.json
deleted file mode 100644
index 5935dad93..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Guides",
- "position": 50
-}
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/angular.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/angular.mdx
deleted file mode 100644
index 2a049fd1e..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/angular.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
-# Angular
-
-Wailsでは、Angular向けのテンプレートは用意されていませんが、Angular自体を使用することはできます。
-
-## 開発モード
-
-Angularで開発モードを使用するには、`wails.json`で下記のように設定してください:
-
-```json
- "frontend:build": "npx ng build",
- "frontend:install": "npm install",
- "frontend:dev:watcher": "npx ng serve",
- "frontend:dev:serverUrl": "http://localhost:4200",
-```
\ No newline at end of file
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/manual-builds.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/manual-builds.mdx
deleted file mode 100644
index dcf192d33..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/manual-builds.mdx
+++ /dev/null
@@ -1,95 +0,0 @@
-# Manual Builds
-
-The Wails CLI does a lot of heavy lifting for the project, but sometimes it's desirable to manually build your project. This document will discuss the different operations the CLI does and how this may be achieved in different ways.
-
-## Build Process
-
-When either `wails build` or `wails dev` are used, the Wails CLI performs a common build process:
-
- - Install frontend dependencies
- - Build frontend project
- - Generate build assets
- - Compile application
- - [optional] Compress application
-
-### Install frontend dependencies
-
-#### CLI Steps
-
-- If the `-s` flag is given, this step is skipped
-- Checks `wails.json` to see if there is an install command in the key `frontend:install`
-- If there isn't, it skips this step
-- If there is, it checks if `package.json` exists in the frontend directory. If it doesn't exist, it skips this step
-- An MD5 sum is generated from the `package.json` file contents
-- It checks for the existence of `package.json.md5` and if it exists, will compare the contents of it (an MD5 sum) with the one generated to see if the contents have changed. If they are the same, this step is skipped
-- If `package.json.md5` does not exist, it creates it using the generated MD5 sum
-- If a build is now required, or `node_modules` does not exist, or the `-f` flag is given, the install command is executed in the frontend directory
-
-#### Manual Steps
-
-This step could be done from the command line or a script with `npm install`.
-
-### Build frontend project
-
-#### Wails CLI
-
-- If the `-s` flag is given, this step is skipped
-- Checks `wails.json` to see if there is a build command in the key `frontend:build`
-- If there isn't, it skips this step
-- If there is, it is executed in the frontend directory
-
-#### Manual Steps
-
-This step could be done from the command line or a script with `npm run build` or whatever the frontend build script is.
-
-### Generate assets
-
-#### Wails CLI
-
-- If `-nopackage` flag is set, this stage is skipped
-- If the `build/appicon.png` file does not exist, a default one is created
-- For Windows, see [Bundling for Windows](#windows)
-- If `build/windows/icon.ico` does not exist, it will create it from the `build/appicon.png` image.
-
-##### Windows
-
-- If `build/windows/icon.ico` does not exist, it will create it from `build/appicon.png` using icon sizes of 256, 128, 64, 48, 32 and 16. This is done using [winicon](https://github.com/leaanthony/winicon).
-- If the `build/windows/.manifest` file does not exist, it creates it from a default version.
-- Compiles the application as a production build (above)
-- Uses [winres](https://github.com/tc-hib/winres) to bundle the icon and manifest into a `.syso` file ready for linking.
-
-#### Manual Steps
-
-- Create `icon.ico` using the [winicon](https://github.com/leaanthony/winicon) CLI tool (or any other tool).
-- Create / Update a `.manifest` file for your application
-- Use the [winres CLI](https://github.com/tc-hib/go-winres) to generate a `.syso` file.
-
-### Compile application
-
-#### Wails CLI
-
-- If the `-clean` flag is provided, the `build` directory is deleted and recreated
-- For `wails dev`, the following default Go flags are used: `-tags dev -gcflags "all=-N -l"`
-- For `wails build`, the following default Go flags are used: `-tags desktop,production -ldflags "-w -s"`
- - On Windows, `-ldflags "-w -h -H windowsgui"`
-- Additional tags passed to the CLI using `-tags` are added to the defaults
-- Additional ldflags passed to the CLI using `-ldflags` are added to the defaults
-- The `-o` flag is passed through
-- The Go compiler specified by `-compiler` will be used for compilation
-
-#### Manual steps
-
-- For dev build, the minimum command would be: `go build -tags dev -gcflags "all=-N -l"`
-- For production build, the minimum command would be: `go build -tags desktop,production -ldflags "-w -s -H windowsgui"`
-- Ensure that you compile in the same directory as the `.syso` file
-
-### Compress application
-
-#### Wails CLI
-
-- If the `-upx` flag has been given, the `upx` program will be run to compress the application with the default settings
-- If `-upxflags` is also passed, these flags are used instead of the default ones
-
-#### Manual steps
-
-- Run `upx [flags]` manually to compress the application.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/overscroll.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/overscroll.mdx
deleted file mode 100644
index 9d1d772d0..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/overscroll.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Overscroll
-
-[Overscroll](https://developer.mozilla.org/en-US/docs/Web/CSS/overscroll-behavior) is the "bounce effect" you sometimes get when you scroll beyond a page's content boundaries. This is common in mobile apps. This can be disabled using CSS:
-
-```css
-html {
- height: 100%;
- overflow: hidden;
-}
-```
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/vscode.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/vscode.mdx
deleted file mode 100644
index ed258656d..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/vscode.mdx
+++ /dev/null
@@ -1,82 +0,0 @@
-
-# Visual Studio Code
-
-This page is for miscellaneous tips and tricks when using Visual Studio Code with Wails.
-
-## Vetur Configuration
-
-Many thanks to [@Lyimmi](https://github.com/Lyimmi) for this tip. Originally posted [here](https://github.com/wailsapp/wails/issues/1791#issuecomment-1228158349).
-
-Vetur is a popular plugin for Visual Studio Code that provides syntax highlighting and code completion for Vue projects. When loading a Wails project in VSCode, Vetur will throw an error as it is expecting to find the frontend project in the root directory. To fix this, you can do the following:
-
-Create a file named `vetur.config.js` in the project's root.
-
-```javascript
-// vetur.config.js
-/** @type {import('vls').VeturConfig} */
-module.exports = {
- // **optional** default: `{}`
- // override vscode settings
- // Notice: It only affects the settings used by Vetur.
- settings: {
- "vetur.useWorkspaceDependencies": true,
- "vetur.experimental.templateInterpolationService": true
- },
- // **optional** default: `[{ root: './' }]`
- // support monorepos
- projects: [
- {
- // **required**
- // Where is your project?
- // It is relative to `vetur.config.js`.
- // root: './packages/repo1',
- root: './frontend',
- // **optional** default: `'package.json'`
- // Where is `package.json` in the project?
- // We use it to determine the version of vue.
- // It is relative to root property.
- package: './package.json',
- // **optional**
- // Where is TypeScript config file in the project?
- // It is relative to root property.
- tsconfig: './tsconfig.json',
- // **optional** default: `'./.vscode/vetur/snippets'`
- // Where is vetur custom snippets folders?
- snippetFolder: './.vscode/vetur/snippets',
- // **optional** default: `[]`
- // Register globally Vue component glob.
- // If you set it, you can get completion by that components.
- // It is relative to root property.
- // Notice: It won't actually do it. You need to use `require.context` or `Vue.component`
- globalComponents: [
- './src/components/**/*.vue'
- ]
- }
- ]
-}
-```
-
-Next, configure `frontend/tsconfig.json`:
-
-```javascript
-{
- "compilerOptions": {
- "module": "system",
- "noImplicitAny": true,
- "removeComments": true,
- "preserveConstEnums": true,
- "sourceMap": true,
- "outFile": "../../built/local/tsc.js",
- "allowJs": true
- },
- "exclude": [
- "node_modules",
- "**/*.spec.ts"
- ],
- "include": [
- "src/**/*",
- "wailsjs/**/*.ts"
- ]
-}
-```
-This should enable you to now use Vetur as expected.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/windows-installer.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/windows-installer.mdx
deleted file mode 100644
index 88a1698db..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/windows-installer.mdx
+++ /dev/null
@@ -1,58 +0,0 @@
-# NSIS installer
-
-```mdx-code-block
-
-
-
-
-```
-
-Wails supports generating Windows installers using the [NSIS installer](https://nsis.sourceforge.io/).
-
-## Installing NSIS
-
-### Windows
-
-The installer is available on the [NSIS Download](https://nsis.sourceforge.io/Download) page.
-
-If you use the chocolatey package manager, run the following script:
-
-```
-choco install nsis
-```
-
-If you install NSIS manually, you need to add the _Bin_ folder, which contains `makensis.exe`, in your NSIS installation to your path. [Here](https://www.architectryan.com/2018/03/17/add-to-the-path-on-windows-10/) is a good tutorial on how to add to path on Windows.
-
-### Linux
-
-The `nsis` package should be available through your distribution's package manager.
-
-### MacOS
-
-NSIS is available to install through homebrew: `brew install nsis`.
-
-## Generating the installer
-
-When a new project is created, Wails generates the NSIS configuration files in `build/windows/installer`. The config data is read from `installer/info.json` and that is configured to use the project's `wails.json` Info section:
-
-```json
-// ...
- "Info": {
- "companyName": "My Company Name",
- "productName": "Wails Vite",
- "productVersion": "1.0.0",
- "copyright": "Copyright.........",
- "comments": "Built using Wails (https://wails.io)"
- },
-```
-
-To generate an installer for your application, use the `-nsis` flag with `wails build`:
-
-```
-wails build -nsis
-```
-
-The installer will now be available in the `build/bin` directory.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/windows.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/windows.mdx
deleted file mode 100644
index 821808c0b..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/windows.mdx
+++ /dev/null
@@ -1,61 +0,0 @@
-# Windows
-
-This page has miscellaneous guides related to developing Wails applications for Windows.
-
-## Handling the WebView2 Runtime Dependency
-
-Wails applications built for Windows have a runtime requirement on the Microsoft [WebView2 Runtime](https://developer.microsoft.com/en-us/microsoft-edge/webview2/). Windows 11 will have this installed by default, but some machines won't. Wails offers an easy approach to dealing with this dependency.
-
-By using the `-webview2` flag when building, you can decide what your application will do when a suitable runtime is not detected (including if the installed runtime is too old). The four options are:
-
-1. Download
-2. Embed
-3. Browser
-4. Error
-
-### Download
-
-This option will prompt the user that no suitable runtime has been found and then offer to download and run the official bootstrapper from Microsoft's WebView2 site. If the user proceeds, the official bootstrapper will be downloaded and run.
-
-### Embed
-
-This option embeds the official bootstrapper within the application. If no suitable runtime has been found, the application will offer to run the bootstrapper. This adds ~150k to the binary size.
-
-### Browser
-
-This option will prompt the user that no suitable runtime has been found and then offer to open a browser to the official WebView2 page where the bootstrapper can be downloaded and installed. The application will then exit, leaving the installation up to the user.
-
-### Error
-
-If no suitable runtime is found, an error is given to the user and no further action taken.
-
-## Fixed version runtime
-
-Another way of dealing with webview2 dependency is shipping it yourself. You can download [fixed version runtime](https://developer.microsoft.com/microsoft-edge/webview2/#download-section) and bundle or download it with your application.
-
-Also, you should specify path to fixed version of webview2 runtime in the `windows.Options` structure when launching wails.
-
-```go
- wails.Run(&options.App{
- Windows: &windows.Options{
- WebviewBrowserPath: "",
- },
- })
-```
-
-Note: When `WebviewBrowserPath` is specified, `error` strategy will be forced in case of minimal required version mismatch or invalid path to a runtime.
-
-## Spawning other programs
-
-When spawning other programs, such as scripts, you will see the window appear on the screen. To hide the window, you can use the following code:
-
-```go
-cmd := exec.Command("your_script.exe")
-cmd.SysProcAttr = &syscall.SysProcAttr{
- HideWindow: true,
- CreationFlags: 0x08000000,
-}
-cmd.Start()
-```
-
-Solution provided by [sithembiso](https://github.com/sithembiso) on the [discussions board](https://github.com/wailsapp/wails/discussions/1734#discussioncomment-3386172).
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/reference/_category_.json b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/reference/_category_.json
deleted file mode 100644
index ebb337b83..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/reference/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Reference",
- "position": 40
-}
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/_category_.json b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/_category_.json
deleted file mode 100644
index ac6d55488..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Runtime",
- "position": 1
-}
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/tutorials/_category_.json b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/tutorials/_category_.json
deleted file mode 100644
index dfac1d175..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/tutorials/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Tutorials",
- "position": 70
-}
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/tutorials/helloworld.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/tutorials/helloworld.mdx
deleted file mode 100644
index b783461da..000000000
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/tutorials/helloworld.mdx
+++ /dev/null
@@ -1,122 +0,0 @@
----
-sidebar_position: 10
----
-
-# Hello World
-
-The aim of this tutorial is to get you up and running with the most basic application using Wails. You will be able to:
-
-- Create a new Wails application
-- Build the application
-- Run the application
-
-:::note
-
-This tutorial uses Windows as the target platform. Output will vary slightly depending on your operating system.
-
-:::
-
-## Create a new Wails application
-
-To create a new Wails application using the default vanilla JS template, you need to run the following command:
-
-```bash
-wails init -n helloworld
-```
-
-You should see something similar to the following:
-
-```
-Wails CLI v2.0.0
-
-Initialising Project 'helloworld'
----------------------------------
-
-Project Name: helloworld
-Project Directory: C:\Users\leaan\tutorial\helloworld
-Project Template: vanilla
-Template Support: https://wails.io
-
-Initialised project 'helloworld' in 232ms.
-```
-
-This will create a new directory called `helloworld` in the current directory. In this directory, you will find a number of files:
-
-```
-build/ - Contains the build files + compiled application
-frontend/ - Contains the frontend files
-app.go - Contains the application code
-main.go - The main program with the application configuration
-wails.json - The project configuration file
-go.mod - The go module file
-go.sum - The go module checksum file
-```
-
-## Build the application
-
-To build the application, change to the new `helloworld` project directory and run the following command:
-
-```bash
-wails build
-```
-
-You should see something like the following:
-
-```
-Wails CLI v2.0.0
-
-App Type: desktop
-Platforms: windows/amd64
-Compiler: C:\Users\leaan\go\go1.18.3\bin\go.exe
-Build Mode: Production
-Skip Frontend: false
-Compress: false
-Package: true
-Clean Build Dir: false
-LDFlags: ""
-Tags: []
-Race Detector: false
-
-Building target: windows/amd64
-------------------------------
- - Installing frontend dependencies: Done.
- - Compiling frontend: Done.
- - Generating bundle assets: Done.
- - Compiling application: Done.
-Built 'C:\Users\leaan\tutorial\helloworld\build\bin\helloworld.exe' in 10.616s.
-```
-
-This has compiled the application and saved it in the `build/bin` directory.
-
-## Run the application
-
-If we view the `build/bin` directory in Windows Explorer, we should see our project binary:
-
-```mdx-code-block
-
-
-
-
-```
-
-We can run it by simply double-clicking the `helloworld.exe` file.
-
-On Mac, Wails generates a `helloworld.app` file which can be run by double-clicking it.
-
-On Linux, you can run the application using `./helloworld` from the `build/bin` directory.
-
-You should see the application working as expected:
-
-```mdx-code-block
-
-
-
-
-```
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/appendix/_category_.json b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/appendix/_category_.json
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/appendix/_category_.json
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/appendix/_category_.json
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/_category_.json b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/community/_category_.json
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/_category_.json
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/community/_category_.json
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/community/links.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/community/links.mdx
similarity index 86%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/community/links.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/community/links.mdx
index c9a5192df..6b180130b 100644
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/community/links.mdx
+++ b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/community/links.mdx
@@ -12,8 +12,7 @@ Wailsに関する[最高のリンク一覧](https://github.com/wailsapp/awesome-
## サポートチャネル
-- [Gophers Slack Channel](https://gophers.slack.com/messages/CJ4P9F7MZ/)
-- [Gophers Slack Channel Invite](https://invite.slack.golangbridge.org/)
+- [Discord](https://discord.com/invite/JDdSxwjhGf)
- [Github Issues](https://github.com/wailsapp/wails/issues)
- [v2ベータディスカッションボード](https://github.com/wailsapp/wails/discussions/828)
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/_category_.json b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/_category_.json
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/_category_.json
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/_category_.json
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/emailit.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/emailit.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/emailit.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/emailit.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/encrypteasy.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/encrypteasy.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/encrypteasy.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/encrypteasy.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/filehound.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/filehound.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/filehound.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/filehound.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/minecraftupdater.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/minecraftupdater.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/minecraftupdater.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/minecraftupdater.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/modalfilemanager.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/modalfilemanager.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/modalfilemanager.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/modalfilemanager.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/mollywallet.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/mollywallet.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/mollywallet.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/mollywallet.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/october.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/october.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/october.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/october.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/optimus.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/optimus.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/optimus.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/optimus.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/portfall.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/portfall.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/portfall.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/portfall.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/restic-browser.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/restic-browser.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/restic-browser.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/restic-browser.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/riftshare.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/riftshare.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/riftshare.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/riftshare.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/scriptbar.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/scriptbar.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/scriptbar.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/scriptbar.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/surge.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/surge.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/surge.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/surge.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/wally.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/wally.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/wally.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/wally.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/wombat.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/wombat.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/wombat.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/wombat.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/ytd.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/ytd.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/ytd.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/ytd.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/community/templates.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/community/templates.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/community/templates.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/community/templates.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/_category_.json b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/gettingstarted/_category_.json
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/_category_.json
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/gettingstarted/_category_.json
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/gettingstarted/building.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/gettingstarted/building.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/gettingstarted/building.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/gettingstarted/building.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/development.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/gettingstarted/development.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/development.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/gettingstarted/development.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/firstproject.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/gettingstarted/firstproject.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/firstproject.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/gettingstarted/firstproject.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/installation.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/gettingstarted/installation.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/installation.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/gettingstarted/installation.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/_category_.json b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/_category_.json
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/_category_.json
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/_category_.json
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/angular.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/angular.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/angular.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/angular.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/application-development.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/application-development.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/application-development.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/application-development.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/dynamic-assets.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/dynamic-assets.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/dynamic-assets.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/dynamic-assets.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/frameless.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/frameless.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/frameless.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/frameless.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/frontend.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/frontend.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/frontend.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/frontend.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/ides.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/ides.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/ides.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/ides.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/linux-distro-support.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/linux-distro-support.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/linux-distro-support.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/linux-distro-support.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/linux.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/linux.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/linux.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/linux.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/local-development.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/local-development.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/local-development.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/local-development.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/mac-appstore.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/mac-appstore.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/mac-appstore.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/mac-appstore.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/manual-builds.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/manual-builds.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/manual-builds.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/manual-builds.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/migrating.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/migrating.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/migrating.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/migrating.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/mouse-buttons.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/mouse-buttons.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/mouse-buttons.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/mouse-buttons.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/obfuscated.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/obfuscated.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/obfuscated.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/obfuscated.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/guides/overscroll.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/overscroll.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/guides/overscroll.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/overscroll.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/routing.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/routing.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/routing.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/routing.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/signing.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/signing.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/signing.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/signing.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/guides/templates.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/templates.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/guides/templates.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/templates.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/troubleshooting.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/troubleshooting.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/troubleshooting.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/troubleshooting.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/vscode.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/vscode.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/vscode.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/vscode.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/windows-installer.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/windows-installer.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/windows-installer.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/windows-installer.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/windows.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/windows.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/windows.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/guides/windows.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/howdoesitwork.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/howdoesitwork.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/howdoesitwork.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/howdoesitwork.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/introduction.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/introduction.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/introduction.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/introduction.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/_category_.json b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/reference/_category_.json
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/_category_.json
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/reference/_category_.json
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/reference/cli.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/reference/cli.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/reference/cli.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/reference/cli.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/reference/menus.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/reference/menus.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/reference/menus.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/reference/menus.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/reference/options.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/reference/options.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/reference/options.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/reference/options.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/reference/project-config.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/reference/project-config.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/reference/project-config.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/reference/project-config.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/_category_.json b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/_category_.json
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/_category_.json
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/_category_.json
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/browser.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/browser.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/browser.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/browser.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/dialog.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/dialog.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/dialog.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/dialog.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/events.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/events.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/events.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/events.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/intro.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/intro.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/intro.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/intro.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/log.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/log.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/log.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/log.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/menu.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/menu.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/menu.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/menu.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/window.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/window.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/window.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/window.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/tutorials/_category_.json b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/tutorials/_category_.json
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/tutorials/_category_.json
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/tutorials/_category_.json
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/tutorials/dogsapi.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/tutorials/dogsapi.mdx
similarity index 66%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/tutorials/dogsapi.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/tutorials/dogsapi.mdx
index 0910a4060..60e7ab094 100644
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/tutorials/dogsapi.mdx
+++ b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/tutorials/dogsapi.mdx
@@ -17,27 +17,25 @@ sidebar_position: 20
:::note
-
-This tutorial has been kindly provided by [@tatadan](https://twitter.com/tatadan) and forms part of their [Wails Examples Repository](https://github.com/tataDan/wails-v2-examples).
+このチュートリアルは[@tatadan](https://twitter.com/tatadan)の好意により提供されたもので、[Wails Examples Repository](https://github.com/tataDan/wails-v2-examples)の一部を構成しています。
:::
+このチュートリアルでは、Web上から犬の写真を取得し、表示するアプリケーションを開発します。
-In this tutorial we are going to develop an application that retrieves photos of dogs from the web and then displays them.
+### プロジェクトを作成する
-### Create the project
+では、アプリケーションを作成しましょう。ターミナルで次のコマンドを入力します: `wails init -n dogs-api -t svelte`
-Let's create the application. From a terminal enter: `wails init -n dogs-api -t svelte`
+注: IDEサポートを追加したい場合は、オプションでこのコマンドの最後に`-ide vscode`または`ide goland`を追加することができます。
-Note: We could optionally add `-ide vscode` or `-ide goland` to the end of this command if you wanted to add IDE support.
+では、cd `dogs-api`をして、プロジェクトファイルの編集を始めましょう。
-Now let's `cd dogs-api` and start editing the project files.
+### 未使用のコードを削除する
-### Remove unused code
+まず、使用しないことがわかっているいくつかの要素を削除することから始めます:
-We will start by removing some elements that we know we will not use:
-
-- Open `app.go` and remove the following lines:
+- `app.go`を開き、以下の行を削除してください:
```go
// Greet returns a greeting for the given name
@@ -46,14 +44,14 @@ func (a *App) Greet(name string) string {
}
```
-- Open `frontend/src/App.svelte` and delete all lines.
-- Delete the `frontend/src/assets/images/logo-universal.png` file
+- `frontend/src/App.svelte`を開き、すべての行を削除します。
+- `frontend/src/assets/images/logo-universal.png`ファイルを削除します。
-### Creating our application
+### アプリケーションの作成
-Now let's add our new Go code.
+では、新しいGoのコードを追加してみましょう。
-Add the following struct declarations to `app.go` before the function definitions:
+`app.go`の関数定義の前に、次の構造体宣言を追加します:
```go
type RandomImage struct {
@@ -72,7 +70,7 @@ type ImagesByBreed struct {
}
```
-Add the following functions to `app.go` (perhaps after the existing function definitions):
+以下の関数を`app.go`に追加します(既存の関数定義の後ろに追加するかもしれません):
```go
func (a *App) GetRandomImageUrl() string {
@@ -137,7 +135,7 @@ func (a *App) GetImageUrlsByBreed(breed string) []string {
}
```
-Modify the `import` section of `app.go` to look like this:
+`app.go`の`import`セクションを次のように変更します:
```go
import (
@@ -151,7 +149,9 @@ import (
)
```
-Add the following lines to `frontend/src/App.svelte`:
+以下の行を`frontend/src/App.svelte`に追加します:
+
+```html
```html
@@ -236,14 +236,12 @@ Add the following lines to `frontend/src/App.svelte`:
}
```
-
-
-### Testing the application
+### アプリケーションのテスト
-To generate the bindings and test the application, run `wails dev`.
+バインディングを生成し、アプリケーションをテストするには、`wails dev`を実行します。
-### Compiling the application
+### アプリケーションのコンパイル
-To compile the application to a single, production grade binary, run `wails build`.
+アプリケーションを単一の、本番用のバイナリにコンパイルするには、`wails build`を実行します。
\ No newline at end of file
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/tutorials/helloworld.mdx b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/tutorials/helloworld.mdx
similarity index 99%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/tutorials/helloworld.mdx
rename to website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/tutorials/helloworld.mdx
index b783461da..f9411527a 100644
--- a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/tutorials/helloworld.mdx
+++ b/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.4.0/tutorials/helloworld.mdx
@@ -119,4 +119,4 @@ You should see the application working as expected:
/>
-```
+```
\ No newline at end of file
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/appendix/_category_.json b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/appendix/_category_.json
deleted file mode 100644
index 83af4ca28..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/appendix/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Appendix",
- "position": 70
-}
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/_category_.json b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/_category_.json
deleted file mode 100644
index 524986e1e..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Community",
- "position": 50
-}
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/links.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/links.mdx
deleted file mode 100644
index 49cb7843b..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/links.mdx
+++ /dev/null
@@ -1,22 +0,0 @@
----
-sidebar_position: 2
----
-
-# Links
-
-This page serves as a list for community related links. Please submit a PR (click `Edit this page` at the bottom) to submit links.
-
-## Awesome Wails
-
-The [definitive list](https://github.com/wailsapp/awesome-wails) of links related to Wails.
-
-## Support Channels
-
-- [Discord](https://discord.com/invite/JDdSxwjhGf)
-- [Github Issues](https://github.com/wailsapp/wails/issues)
-- [v2 Beta Discussion Board](https://github.com/wailsapp/wails/discussions/828)
-
-## Social Media
-
-- [Twitter](https://twitter.com/wailsapp)
-- [Wails Chinese Community QQ Group](https://qm.qq.com/cgi-bin/qm/qr?k=PmIURne5hFGNd7QWzW5qd6FV-INEjNJv&jump_from=webapi) - Group number: 1067173054
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/_category_.json b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/_category_.json
deleted file mode 100644
index 276e283b7..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Showcase",
- "position": 1
-}
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/emailit.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/emailit.mdx
deleted file mode 100644
index 4a1ebe835..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/emailit.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
-# EmailIt
-
-
-
-
-
-
-[EmailIt](https://github.com/raguay/EmailIt/) is a Wails 2 program that is a markdown based email sender only with nine notepads, scripts to manipulate the text, and templates. It also has a builtin [Node-Red](https://nodered.org/) server, scripts terminal, and the [ScriptBar](https://github.com/raguay/ScriptBarApp) program for displaying results from Node-Red or a script on your system. Documentation is very scarce, but the programs works. It’s built using Wails2 and Svelte, and the download is a universal macOS application.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/encrypteasy.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/encrypteasy.mdx
deleted file mode 100644
index 13c2d8345..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/encrypteasy.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# EncryptEasy
-
-
-
-
-
-
-**[EncryptEasy](https://www.encrypteasy.app) is a simple and easy to use PGP encryption tool, managing all your and your contacts keys. Encryption should be simple. Developed with Wails.**
-
-Encrypting messages using PGP is the industry standard. Everyone has a private and a public key. Your private key, well, needs to be kept private so only you can read messages. Your public key is distributed to anyone who wants to send you secret, encrypted messages. Managing keys, encrypting messages and decrypting messages should be a smooth experience. EncryptEasy is all about making it easy.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/filehound.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/filehound.mdx
deleted file mode 100644
index 78cbfca86..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/filehound.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
-# FileHound Export Utility
-
-
-
-
-
-
-[FileHound Export Utility](https://www.filehound.co.uk/) FileHound is a cloud document management platform made for secure file retention, business process automation and SmartCapture capabilities.
-
-The FileHound Export Utility allows FileHound Administrators the ability to run a secure document and data extraction tasks for alternative back-up and recovery purposes. This application will download all documents and/or meta data saved in FileHound based on the filters you choose. The metadata will be exported in both JSON and XML formats.
-
-Backend built with: Go 1.15 Wails 1.11.0 go-sqlite3 1.14.6 go-linq 3.2
-
-Frontend with: Vue 2.6.11 Vuex 3.4.0 Typescript Tailwind 1.9.6
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/minecraftupdater.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/minecraftupdater.mdx
deleted file mode 100644
index 11247339d..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/minecraftupdater.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Minecraft Updater
-
-
-
-
-
-
-[Minecraft Updater](https://github.com/Gurkengewuerz/MinecraftModUpdater) is a utility tool to update and synchronize Minecraft mods for your userbase. It’s built using Wails2 and React with [antd](https://ant.design/) as frontend framework.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/modalfilemanager.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/modalfilemanager.mdx
deleted file mode 100644
index a7ae8c492..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/modalfilemanager.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
-# Modal File Manager
-
-
-
-
-
-
-[Modal File Manager](https://github.com/raguay/ModalFileManager) is a dual pane file manager using web technologies. My original design was based on NW.js and can be found [here](https://github.com/raguay/ModalFileManager-NWjs). This version uses the same Svelte based frontend code (but it has be greatly modified since the departure from NW.js), but the backend is a [Wails 2](https://wails.io/) implementation. By using this implementation, I no longer use command line `rm`, `cp`, etc. commands. It is fully coded using Go and runs much faster than the previous versions.
-
-This file manager is designed around the same principle as Vim: a state controlled keyboard actions. The number of states isn't fixed, but very programmable. Therefore, an infinite number of keyboard configurations can be created and used. This is the main difference from other file managers.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/mollywallet.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/mollywallet.mdx
deleted file mode 100644
index 534b097ca..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/mollywallet.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
-# Molley Wallet
-
-
-
-
-
-
-[Molly Wallet](https://github.com/grvlle/constellation_wallet/) the official $DAG wallet of the Constellation Network. It'll let users interact with the Hypergraph Network in various ways, not limited to producing $DAG transactions.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/october.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/october.mdx
deleted file mode 100644
index 889d2dd9e..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/october.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
-# October
-
-
-
-
-
-
-[October](https://october.utf9k.net) is a small Wails application that makes it really easy to extract highlights from [Kobo eReaders](https://en.wikipedia.org/wiki/Kobo_eReader) and then forward them to [Readwise](https://readwise.io).
-
-It has a relatively small scope with all platform versions weighing in under 10MB, and that's without enabling [UPX compression](https://upx.github.io/)!
-
-In contrast, the author's previous attempts with Electron quickly bloated to several hundred megabytes.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/optimus.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/optimus.mdx
deleted file mode 100644
index c3eb79507..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/optimus.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
-# Optimus
-
-
-
-
-
-
-[Optimus](https://github.com/splode/optimus) is a desktop image optimization application. It supports conversion and compression between WebP, JPEG, and PNG image formats.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/portfall.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/portfall.mdx
deleted file mode 100644
index 4cc2c63c9..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/portfall.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
-# Portfall
-
-
-
-
-
-
-[Portfall](https://github.com/rekon-oss/portfall) - A desktop k8s port-forwarding portal for easy access to all your cluster UIs
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/restic-browser.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/restic-browser.mdx
deleted file mode 100644
index 1505ce07a..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/restic-browser.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Restic Browser
-
-
-
-
-
-
-[Restic-Browser](https://github.com/emuell/restic-browser) - A simple, cross-platform [restic](https://github.com/restic/restic) backup GUI for browsing and restoring restic repositories.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/riftshare.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/riftshare.mdx
deleted file mode 100644
index 5223e88cf..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/riftshare.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
-# RiftShare
-
-
-
-
-
-
-Easy, Secure, and Free file sharing for everyone. Learn more at [Riftshare.app](https://riftshare.app)
-
-## Features
-
-- Easy secure file sharing between computers both in the local network and through the internet
-- Supports sending files or directories securely through the [magic wormhole protocol](https://magic-wormhole.readthedocs.io/en/latest/)
-- Compatible with all other apps using magic wormhole (magic-wormhole or wormhole-william CLI, wormhole-gui, etc.)
-- Automatic zipping of multiple selected files to send at once
-- Full animations, progress bar, and cancellation support for sending and receiving
-- Native OS File Selection
-- Open files in one click once received
-- Auto Update - don't worry about having the latest release!
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/scriptbar.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/scriptbar.mdx
deleted file mode 100644
index aaa556f92..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/scriptbar.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
-# ScriptBar
-
-
-
-
-
-
-[ScriptBar](https://GitHub.com/raguay/ScriptBarApp) is a program to show the output of the embedded [Node-Red](https://nodered.org) server in the [EmailIt](https://GitHub.com/raguay/EmailIt) application. It also displays the output of scripts on your system. ScriptBar doesn't put them in the menubar, but has them all in a convient window for easy viewing. You can have multiple tabs to have many different things show. You can also keep the links to your most visited web sites.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/surge.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/surge.mdx
deleted file mode 100644
index 2d895dc29..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/surge.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
-# Surge
-
-
-
-
-
-
-[Surge](https://getsurge.io/) is a p2p filesharing app designed to utilize blockchain technologies to enable 100% anonymous file transfers. Surge is end-to-end encrypted, decentralized and open source.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/wally.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/wally.mdx
deleted file mode 100644
index 2a2498f40..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/wally.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
-# Wally
-
-
-
-
-
-
-[Wally](https://ergodox-ez.com/pages/wally) is the official firmware flasher for [Ergodox](https://ergodox-ez.com/) keyboards. It looks great and is a fantastic example of what you can achieve with Wails: the ability to combine the power of Go and the rich graphical tools of the web development world.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/wombat.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/wombat.mdx
deleted file mode 100644
index 54cedacea..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/wombat.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
-# Wombat
-
-
-
-
-
-
-[Wombat](https://github.com/rogchap/wombat) is a cross platform gRPC client.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/ytd.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/ytd.mdx
deleted file mode 100644
index 178ff0529..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/ytd.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
-# Ytd
-
-
-
-
-
-
-[Ytd](https://github.com/marcio199226/ytd/tree/v2-wails) is an app for downloading tracks from youtube, creating offline playlists and share them with your friends, your friends will be able to playback your playlists or download them for offline listening, has an built-in player.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/templates.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/templates.mdx
deleted file mode 100644
index d9a29a6fa..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/templates.mdx
+++ /dev/null
@@ -1,52 +0,0 @@
----
-sidebar_position: 1
----
-
-# Templates
-
-This page serves as a list for community supported templates. Please submit a PR (click `Edit this page` at the bottom) to include your templates. To build your own template, please see the [Templates](../guides/templates.mdx) guide.
-
-To use these templates, run `wails init -n "Your Project Name" -t [the link below[@version]]`
-
-If there is no version suffix, the main branch code template is used by default. If there is a version suffix, the code template corresponding to the tag of this version is used.
-
-Example: `wails init -n "Your Project Name" -t https://github.com/misitebao/wails-template-vue`
-
-:::warning Attention
-
-**The Wails project does not maintain, is not responsible nor liable for 3rd party templates!**
-
-If you are unsure about a template, inspect `package.json` and `wails.json` for what scripts are run and what packages are installed.
-
-:::
-
-## Vue
-
-- [wails-template-vue](https://github.com/misitebao/wails-template-vue) - A template using Vite,Vue and Vue-Router(Support both JavaScript and TypeScript)
-- [wails-vite-vue-ts](https://github.com/codydbentley/wails-vite-vue-ts) - Vue 3 TypeScript with Vite (and instructions to add features)
-- [wails-vite-vue-the-works](https://github.com/codydbentley/wails-vite-vue-the-works) - Vue 3 TypeScript with Vite, Vuex, Vue Router, Sass, and ESLint + Prettier
-
-## Angular
-
-- [wails-angular-template](https://github.com/TAINCER/wails-angular-template) - Angular with TypeScript, Sass, Hot-Reload, Code-Splitting and i18n
-
-## React
-
-- [wails-react-template](https://github.com/AlienRecall/wails-react-template) - A template using reactjs
-- [wails-react-template](https://github.com/flin7/wails-react-template) - A minimal template for React that supports live development
-- [wails-template-nextjs](https://github.com/LGiki/wails-template-nextjs) - A template using Next.js and TypeScript
-
-## Svelte
-
-- [wails-svelte-template](https://github.com/raitonoberu/wails-svelte-template) - A template using Svelte
-- [wails-vite-svelte-template](https://github.com/BillBuilt/wails-vite-svelte-template) - A template using Svelte and Vite
-- [wails-vite-svelte-tailwind-template](https://github.com/BillBuilt/wails-vite-svelte-tailwind-template) - A template using Svelte and Vite with TailwindCSS v3
-- [wails-sveltekit-template](https://github.com/h8gi/wails-sveltekit-template) - A template using SvelteKit
-
-## Elm
-
-- [wails-elm-template](https://github.com/benjamin-thomas/wails-elm-template) - Develop your GUI app with functional programming and a **snappy** hot-reload setup :tada: :rocket:
-
-## Pure JavaScript (Vanilla)
-
-- [wails-pure-js-template](https://github.com/KiddoV/wails-pure-js-template) - A template with nothing but just basic JavaScript, HTML, and CSS
\ No newline at end of file
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/contributing/_category_.json b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/contributing/_category_.json
deleted file mode 100644
index fad21931a..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/contributing/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Contributing",
- "position": 99
-}
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/contributing/developing-new-features.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/contributing/developing-new-features.mdx
deleted file mode 100644
index 57c5b101b..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/contributing/developing-new-features.mdx
+++ /dev/null
@@ -1,29 +0,0 @@
----
-sidebar_position: 20
----
-
-# Developing New Features
-
-We are always keen to add features to Wails and expand on what the project can do. The process for adding new features are as follows:
-
-- Pick an enhancement ticket with the "TODO" label. It's preferable to select one from the current [Backlog](https://github.com/orgs/wailsapp/projects/1/views/1) but the choice is yours.
-- Before developing, check that the ticket includes the following information:
-- The purpose of the enhancement
-- What is out of scope for the enhancement
-- What platforms the enhancement targets (most features should be cross-platform unless there's a very specific reason)
-- If the ticket does not include this information, feel free to request the information from the person who opened the ticket. Sometimes placeholder tickets are created and require more details
-- Comment on the ticket stating you wish to develop the feature
-- Clone the repository and create a branch with the format `feature/_`
-- New features often require documentation so please ensure you have also added or updated the documentation as part of the changes
-- Once the feature is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested.
-- Once all the testing is completed, please update the status of the PR from draft and leave a message.
-
-:::note
-There is nothing stopping you from opening a ticket and working on it yourself, but please be aware that all
-enhancement requests are reviewed for good fit. Not all ideas will be selected so it's best to have discussion
-on the ticket first.
-:::
-
-:::warning
-Any PRs opened without a corresponding ticket may be rejected.
-:::
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/contributing/documenting.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/contributing/documenting.mdx
deleted file mode 100644
index 06f33914b..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/contributing/documenting.mdx
+++ /dev/null
@@ -1,34 +0,0 @@
----
-sidebar_position: 40
----
-
-# Documenting
-
-This website is also the main documentation site for the project. Sometimes this gets out of date and needs some slight adjustments. Some of the documentation isn't written to the best standards either. Developing documentation is hard and so any contribution to this is greatly appreciated. Features without documentation are unfinished so to the project, it's _as important_ as the code.
-
-We generally do not create tickets for updating documentation so if there is text you think should be updated or rephrased then feel free to submit a PR for that. This site is in the main repository under the `website` directory. We use [Docusaurus](https://docusaurus.io/) to create the site so there is plenty of existing documentation and tutorials around to get started.
-
-To set up a local documentation development environment, do the following:
-
-- [Install npm](https://docs.npmjs.com/cli/v8/configuring-npm/install)
-- `cd website`
-- `npm install`
-- `npm run start`
-
-After it has all installed and is running, you should see the site at [`http://localhost:3000`](http://localhost:3000). Any changes made to the site text will be immediately reflected in the browser.
-
-## Versioning
-
-We employ a versioning system where we have the "latest" documentation AKA "Next Version" which has all the changes that have occurred since the last release. We also keep the last release documentation as well as the version before that.
-
-There isn't usually a reason to update released documentation so we don't generally update the documents in the `versioned_docs` or `versioned_sidebars` directories.
-
-The "next version" docs are mainly in `website/docs` with some "version independent" documents in `src/pages`. Any updates should be made in the `website/docs` directory.
-
-## Languages
-
-The default documents of the Wails project are English documents. We use the "crowdin" tool to translate documents in other languages and synchronize them to the website. You can [join our project](https://crowdin.com/project/wails) and submit your translations to make contributions.
-
-### Add new language
-
-If you want to add a new language to the documentation, please follow the prompts to [fill in and submit an Issue](https://github.com/wailsapp/wails/issues/new?assignees=&labels=documentation&template=documentation.yml). After being confirmed by the maintainer, we will add the language to the "crowdin" and you will then be able to submit your translation.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/contributing/fixing-bugs.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/contributing/fixing-bugs.mdx
deleted file mode 100644
index 51bd90b74..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/contributing/fixing-bugs.mdx
+++ /dev/null
@@ -1,27 +0,0 @@
----
-sidebar_position: 30
----
-
-# Fixing Bugs
-
-The process for fixing bugs are as follows:
-
-- Check the current [Backlog](https://github.com/orgs/wailsapp/projects/1/views/1) and select a bug to fix
-- Before developing, check that the ticket includes the following information:
-- The scope of the issue including platforms affected
-- The steps to reproduce. Sometimes bugs are opened that are not Wails issues and the onus is on the reporter to prove that it is a Wails issue with a minimal reproducible example
-- The output of `wails doctor`
-- If the ticket does not include this information, feel free to request the information from the person who opened the ticket.
-- Comment on the ticket stating you wish to develop a fix
-- Clone the repository and create a branch with the format `bugfix/_`
-- Once the fix is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested.
-- Once all the testing is completed, please update the status of the PR from draft and leave a message.
-
-:::note
-There is nothing stopping you from opening a ticket and working on it yourself, but please be aware that all
-bugfixes should be discussed as the approach may have unintended side effects.
-:::
-
-:::warning
-Any PRs opened without a corresponding ticket may be rejected.
-:::
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/contributing/helping-others.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/contributing/helping-others.mdx
deleted file mode 100644
index dcfc6160b..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/contributing/helping-others.mdx
+++ /dev/null
@@ -1,13 +0,0 @@
----
-sidebar_position: 50
----
-
-# Helping Others
-
-A great way to contribute to the project is to help others who are experiencing difficulty. This is normally reported as a ticket or a message on the Wails slack channel. Even just clarifying the issue can really help out. Sometimes, when an issue is discussed and gets resolved, we create a guide out of it to help others who face the same issues.
-
-To join the Wails discord server, accept the invite [here](https://discord.com/invite/JDdSxwjhGf).
-
-:::note
-Work In Progress
-:::
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/contributing/setting-up-a-dev-environment.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/contributing/setting-up-a-dev-environment.mdx
deleted file mode 100644
index b933af9a6..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/contributing/setting-up-a-dev-environment.mdx
+++ /dev/null
@@ -1,30 +0,0 @@
----
-sidebar_position: 10
----
-
-# Setting up a Development Environment
-
-You can set up a development environment by doing the following:
-
-- Install the latest versions of Go and Git
-- `git clone https://github.com/wailsapp/wails`
-- `cd wails/v2/cmd/wails`
-- `go install`
-
-NOTE: The directory that you cloned the project into will now be called "clonedir".
-
-The Wails CLI will now be at the very latest version.
-
-To update projects to use the latest version, update the project's `go.mod` and ensure the following line is at the bottom of the file:
-
-`replace github.com/wailsapp/wails/v2 => `
-
-Example:
-
-On Windows: `replace github.com/wailsapp/wails/v2 => C:\Users\leaan\Documents\wails-v2-beta\wails\v2`
-
-On 'nix: `replace github.com/wailsapp/wails/v2 => /home/me/projects/wails/v2`
-
-To revert back to a stable version, run:
-
-`go install github.com/wailsapp/wails/v2/cmd/wails@latest`
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/contributing/testing.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/contributing/testing.mdx
deleted file mode 100644
index 284eec649..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/contributing/testing.mdx
+++ /dev/null
@@ -1,16 +0,0 @@
----
-sidebar_position: 35
----
-
-# Testing
-
-Testing is vitally important to ensure quality in the project. There are a couple of scenarios where testing can really help the project:
-
-- Testing if a bug is reproducible on your local system
-- Testing PRs to ensure that they work correctly
-
-If you chose to test if someone's bug report is reproducible on your local system, then feel free to add a comment on the ticket confirming this with the output of `wails doctor`.
-
-To test PRs, choose a PR to test and check if the PR description has the testing scenarios listed. If not, please ask the person who opened the PR to provide that list. Once you have determined a valid test scenario, please report your findings on the PR.
-
-If you ever need more clarity or help on testing, please ask a question in the [Contributing to Wails](https://github.com/wailsapp/wails/discussions/1520) discussion or on discord.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/contributing/ways-of-contributing.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/contributing/ways-of-contributing.mdx
deleted file mode 100644
index 6b76d99d9..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/contributing/ways-of-contributing.mdx
+++ /dev/null
@@ -1,18 +0,0 @@
----
-sidebar_position: 1
----
-
-# Ways of contributing
-
-Wails is an open source, community driven project. We welcome anyone to join us in contributing to the project. This documentation is aimed at anyone wishing to get familiar with the project and the development processes.
-
-There are many ways to contribute to the project:
-
-- Developing new features
-- Fixing bugs
-- Testing
-- Documenting features
-- Writing tutorials / guides
-- Helping others on the issues + discussions boards
-
-Guides for these have been created in their own sections. Before getting started, please introduce yourself in the [Contributing to Wails](https://github.com/wailsapp/wails/discussions/1520) discussion.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/_category_.json b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/_category_.json
deleted file mode 100644
index 597b920df..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Getting Started",
- "position": 10
-}
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/building.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/building.mdx
deleted file mode 100644
index a74c762d2..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/building.mdx
+++ /dev/null
@@ -1,21 +0,0 @@
----
-sidebar_position: 6
----
-
-# 프로젝트 컴파일
-
-프로젝트 디렉토리에서 `wails build`를 실행하세요. 이 작업은 프로젝트를 컴파일한 후 실행파일을 `build/bin` 디렉토리에 저장합니다.
-
-실행파일을 실행하면 아래와 같은 기본 애플리케이션을 볼 수 있습니다.
-
-
-
-
-
-
-
-컴파일 옵션에 대한 자세한 내용은 [CLI Reference](../reference/cli.mdx#build)를 참조하세요.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/development.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/development.mdx
deleted file mode 100644
index fc9387174..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/development.mdx
+++ /dev/null
@@ -1,16 +0,0 @@
----
-sidebar_position: 5
----
-
-# 애플리케이션 개발
-
-프로젝트 디렉토리에서 `wails dev`를 실행하여 개발 모드에서 애플리케이션을 실행할 수 있습니다. 이렇게 하면 다음과 같은 작업이 수행됩니다.
-
-- 애플리케이션 빌드 및 실행
-- Go 코드를 Javascript에서 호출할 수 있도록 프론트엔드에 바인딩
-- Using the power of [vite](https://vitejs.dev/), will watch for modifications in your Go files and rebuild/re-run on change
-- Sets up a [webserver](http://localhost:34115) that will serve your application over a browser. This allows you to use your favourite browser extensions. You can even call your Go code from the console
-
-시작하려면 프로젝트 디렉토리에서 `wails dev`를 실행하세요. 더 자세한 정보는 [여기](../reference/cli.mdx#dev)에서 찾을 수 있습니다.
-
-Coming soon: Tutorial
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/firstproject.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/firstproject.mdx
deleted file mode 100644
index 9348ea0a2..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/firstproject.mdx
+++ /dev/null
@@ -1,132 +0,0 @@
----
-sidebar_position: 2
----
-
-# Creating a Project
-
-## Project Generation
-
-Now that the CLI is installed, you can generate a new project by using the `wails init` command.
-
-Pick your favourite framework:
-
-
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-
-
-
- Generate a Svelte project using Javascript with:
-
- wails init -n myproject -t svelte
-
-If you would rather use Typescript:
-
- wails init -n myproject -t svelte-ts
-
-
-
- Generate a React project using Javascript with:
-
- wails init -n myproject -t react
-
-If you would rather use Typescript:
-
- wails init -n myproject -t react-ts
-
-
-
- Generate a Vue project using Javascript with:
-
- wails init -n myproject -t vue
-
-If you would rather use Typescript:
-
- wails init -n myproject -t vue-ts
-
-
-
- Generate a Preact project using Javascript with:
-
- wails init -n myproject -t preact
-
-If you would rather use Typescript:
-
- wails init -n myproject -t preact-ts
-
-
-
- Generate a Lit project using Javascript with:
-
- wails init -n myproject -t lit
-
-If you would rather use Typescript:
-
- wails init -n myproject -t lit-ts
-
-
-
- Generate a Vanilla project using Javascript with:
-
- wails init -n myproject -t vanilla
-
-If you would rather use Typescript:
-
- wails init -n myproject -t vanilla-ts
-
-
-
-
-
-
-
-
-There are also [community templates](../community/templates.mdx) available that offer different capabilities and frameworks.
-
-To see the other options available, you can run `wails init -help`. More details can be found in the [CLI Reference](../reference/cli.mdx#init).
-
-## Project Layout
-
-Wails projects have the following layout:
-
-```
-.
-├── build/
-│ ├── appicon.png
-│ ├── darwin/
-│ └── windows/
-├── frontend/
-├── go.mod
-├── go.sum
-├── main.go
-└── wails.json
-```
-
-### Project structure rundown
-
-- `/main.go` - The main application
-- `/frontend/` - Frontend project files
-- `/build/` - Project build directory
-- `/build/appicon.png` - The application icon
-- `/build/darwin/` - Mac specific project files
-- `/build/windows/` - Windows specific project files
-- `/wails.json` - The project configuration
-- `/go.mod` - Go module file
-- `/go.sum` - Go module checksum file
-
-The `frontend` directory has nothing specific to Wails and can be any frontend project of your choosing.
-
-The `build` directory is used during the build process. These files may be updated to customise your builds. If files are removed from the build directory, default versions will be regenerated.
-
-The default module name in `go.mod` is "changeme". You should change this to something more appropriate.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/installation.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/installation.mdx
deleted file mode 100644
index 1d702d6cc..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/installation.mdx
+++ /dev/null
@@ -1,95 +0,0 @@
----
-sidebar_position: 1
----
-
-# 설치하기
-
-## 지원되는 플랫폼
-
-- Windows 10/11 AMD64/ARM64
-- MacOS 10.13+ AMD64
-- MacOS 11.0+ ARM64
-- Linux AMD64/ARM64
-
-## 의존성
-
-Wails는 설치 전에 아래와 같은 몇 가지 공통적인 의존성이 필요합니다.
-
-- Go 1.17+
-- NPM (Node 15+)
-
-### Go
-
-[Go 다운로드 페이지](https://go.dev/doc/install)에서 Go를 다운로드 합니다.
-
-공식 [Go 설치 지침](https://go.dev/doc/install)에 따라 진행하세요. 또한 `PATH` 환경변수에 `~/go/bin` 디렉토리 경로가 포함되어 있는지 확인해야 합니다. 터미널을 다시 시작하고 아래 내용을 확인하세요.
-
-- Go 설치 확인: `go version`
-- PATH 변수에 "~/go/bin" 확인: `echo $PATH | grep go/bin`
-
-### NPM
-
-[Node 다운로드 페이지](https://nodejs.org/en/download/)에서 NPM을 다운로드 합니다. 우리는 일반적으로 최신 버전에서 테스트를 진행하기 때문에 최신 버전 사용을 권장합니다.
-
-정상적으로 설치된 것을 확인하기 위해 `npm --version`을 실행합니다.
-
-## 플랫폼에 따른 의존성
-
-아래와 같이 플랫폼별 의존성이 있습니다.
-
-
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-
-
-
- Wails를 사용하려면 xcode 명령어 라인 도구가 설치되어 있어야 합니다. This can be
- done by running:
- xcode-select --install
-
-
- Wails requires that the{" "}
-
- WebView2
- {" "}
- runtime is installed. Some Windows installations will already have this
- installed. You can check using the wails doctor command (see
- below).
-
-
- Linux required the standard gcc build tools plus{" "}
- libgtk3 and libwebkit. Rather than list a ton of
- commands for different distros, Wails can try to determine what the
- installation commands are for your specific distribution. Run{" "}
- wails doctor after installation to be shown how to install the
- dependencies. If your distro/package manager is not supported, please
- consult the{" "}
- Add Linux Distro guide.
-
-
-
-
-
-## 선택 설치
-
-- [UPX](https://upx.github.io/)는 어플리케이션 압축에 필요합니다.
-
-## Wails 설치
-
-`go install github.com/wailsapp/wails/v2/cmd/wails@latest`을 실행하여 Wails CLI를 설치합니다.
-
-## 시스템 점검
-
-`wails doctor`를 실행하면 의존성이 올바르게 설치되어 있는지 점검할 수 있습니다. 문제가 있는 의존성에 대해서는 문제 해결을 위한 도움을 줄 수 있습니다.
-
-## `wails` 명령어를 찾을 수 없나요?
-
-시스템에서 `wails` 명령어를 찾을 수 없는 경우 Go 설치 지침을 잘 따라했는지 확인해보세요. 대부분 사용자 홈 디렉토리에 있는 `go/bin` 디렉토리가 `PATH` 환경변수에 존재하지 않는 경우입니다. 또한 변경사항이 명령 프롬프트에 반영되도록 일반적으로 열려 있는 모든 명령 프롬프트를 닫았다가 다시 열어야 합니다.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/_category_.json b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/_category_.json
deleted file mode 100644
index 5935dad93..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Guides",
- "position": 50
-}
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/application-development.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/application-development.mdx
deleted file mode 100644
index a618076f1..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/application-development.mdx
+++ /dev/null
@@ -1,194 +0,0 @@
-# Application Development
-
-There are no hard and fast rules for developing applications with Wails, but there are some basic guidelines.
-
-## Application Setup
-
-The pattern used by the default templates are that `main.go` is used for configuring and running the application, whilst `app.go` is used for defining the application logic.
-
-The `app.go` file will define a struct that has 2 methods which act as hooks into the main application:
-
-```go title="app.go"
-type App struct {
- ctx context.Context
-}
-
-func NewApp() *App {
- return &App{}
-}
-
-func (a *App) startup(ctx context.Context) {
- a.ctx = ctx
-}
-
-func (a *App) shutdown(ctx context.Context) {
-}
-```
-
-- The startup method is called as soon as Wails allocates the resources it needs and is a good place for creating resources, setting up event listeners and anything else the application needs at startup. It is given a `context.Context` which is usually saved in a struct field. This context is needed for calling the [runtime](../reference/runtime/intro.mdx). If this method returns an error, the application will terminate. In dev mode, the error will be output to the console.
-
-- The shutdown method will be called by Wails right at the end of the shutdown process. This is a good place to deallocate memory and perform any shutdown tasks.
-
-The `main.go` file generally consists of a single call to `wails.Run()`, which accepts the application configuration. The pattern used by the templates is that before the call to `wails.Run()`, an instance of the struct we defined in `app.go` is created and saved in a variable called `app`. This configuration is where we add our callbacks:
-
-```go {3,9,10} title="main.go"
-func main() {
-
- app := NewApp()
-
- err := wails.Run(&options.App{
- Title: "My App",
- Width: 800,
- Height: 600,
- OnStartup: app.startup,
- OnShutdown: app.shutdown,
- })
- if err != nil {
- log.Fatal(err)
- }
-}
-
-```
-
-More information on application lifecycle hooks can be found [here](../howdoesitwork.mdx#application-lifecycle-callbacks).
-
-## Binding Methods
-
-It is likely that you will want to call Go methods from the frontend. This is normally done by adding public methods to the already defined struct in `app.go`:
-
-```go {16-18} title="app.go"
-type App struct {
- ctx context.Context
-}
-
-func NewApp() *App {
- return &App{}
-}
-
-func (a *App) startup(ctx context.Context) {
- a.ctx = ctx
-}
-
-func (a *App) shutdown(ctx context.Context) {
-}
-
-func (a *App) Greet(name string) string {
- return fmt.Sprintf("Hello %s!", name)
-}
-```
-
-In the main application configuration, the `Bind` key is where we can tell Wails what we want to bind:
-
-```go {11-13} title="main.go"
-func main() {
-
- app := NewApp()
-
- err := wails.Run(&options.App{
- Title: "My App",
- Width: 800,
- Height: 600,
- OnStartup: app.startup,
- OnShutdown: app.shutdown,
- Bind: []interface{}{
- app,
- },
- })
- if err != nil {
- log.Fatal(err)
- }
-}
-
-```
-
-This will bind all public methods in our `App` struct (it will never bind the startup and shutdown methods).
-
-### Dealing with context when binding multiple structs
-
-If you want to bind methods for multiple structs but want each struct to keep a reference to the context so that you can use the runtime functions, a good pattern is to pass the context from the `OnStartup` method to your struct instances :
-
-```go
-func main() {
-
- app := NewApp()
- otherStruct := NewOtherStruct()
-
- err := wails.Run(&options.App{
- Title: "My App",
- Width: 800,
- Height: 600,
- OnStartup: func(ctx context.Context){
- app.SetContext(ctx)
- otherStruct.SetContext(ctx)
- },
- OnShutdown: app.shutdown,
- Bind: []interface{}{
- app,
- otherStruct
- },
- })
- if err != nil {
- log.Fatal(err)
- }
-}
-```
-
-More information on Binding can be found [here](../howdoesitwork.mdx#method-binding).
-
-## Application Menu
-
-Wails supports adding a menu to your application. This is done by passing a [Menu](../reference/menus.mdx#menu) struct to application config. It's common to use a method that returns a Menu, and even more common for that to be a method on the `App` struct used for the lifecycle hooks.
-
-```go {11} title="main.go"
-func main() {
-
- app := NewApp()
-
- err := wails.Run(&options.App{
- Title: "My App",
- Width: 800,
- Height: 600,
- OnStartup: app.startup,
- OnShutdown: app.shutdown,
- Menu: app.menu(),
- Bind: []interface{}{
- app,
- },
- })
- if err != nil {
- log.Fatal(err)
- }
-}
-
-```
-
-## Assets
-
-The great thing about the way Wails v2 handles assets is that it doesn't! The only thing you need to give Wails is an `embed.FS`. How you get to that is entirely up to you. You can use vanilla html/css/js files like the vanilla template. You could have some complicated build system, it doesn't matter.
-
-When `wails build` is run, it will check the `wails.json` project file at the project root. There are 2 keys in the project file that are read:
-
-- "frontend:install"
-- "frontend:build"
-
-The first, if given, will be executed in the `frontend` directory to install the node modules. The second, if given, will be executed in the `frontend` directory to build the frontend project.
-
-If these 2 keys aren't given, then Wails does absolutely nothing with the frontend. It is only expecting that `embed.FS`.
-
-### AssetsHandler
-
-A Wails v2 app can optionally define a `http.Handler` in the `options.App`, which allows hooking into the AssetServer to create files on the fly or process POST/PUT requests. GET requests are always first handled by the `assets` FS. If the FS doesn't find the requested file the request will be forwarded to the `http.Handler` for serving. Any requests other than GET will be directly processed by the `AssetsHandler` if specified. It's also possible to only use the `AssetsHandler` by specifiy `nil` as the `Assets` option.
-
-## Built in Dev Server
-
-Running `wails dev` will start the built in dev server which will start a file watcher in your project directory. By default, if any file changes, wails checks if it was an application file (default: `.go`, configurable with `-e` flag). If it was, then it will rebuild your application and relaunch it. If the changed file was in the assets, it will issue a reload after a short amount of time.
-
-The dev server uses a technique called "debouncing" which means it doesn't reload straight away, as there may be multiple files changed in a short amount of time. When a trigger occurs, it waits for a set amount of time before issuing a reload. If another trigger happens, it resets to the wait time again. By default this value is `100ms`. If this value doesn't work for your project, it can be configured using the `-debounce` flag. If used, this value will be saved to your project config and become the default.
-
-## External Dev Server
-
-Some frameworks come with their own live-reloading server, however they will not be able to take advantage of the Wails Go bindings. In this scenario, it is best to run a watcher script that rebuilds the project into the build directory, which Wails will be watching. For an example, see the default svelte template that uses [rollup](https://rollupjs.org/guide/en/). For [create-react-app](https://create-react-app.dev/), it's possible to use [this script](https://gist.github.com/int128/e0cdec598c5b3db728ff35758abdbafd) to achieve a similar result.
-
-## Go Module
-
-The default Wails templates generate a `go.mod` file that contains the module name "changeme". You should change this to something more appropriate after project generation.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/bleeding-edge.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/bleeding-edge.mdx
deleted file mode 100644
index b81cc79dc..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/bleeding-edge.mdx
+++ /dev/null
@@ -1,55 +0,0 @@
-# Bleeding Edge
-
-## Overview
-
-Wails is in constant development and new releases are regularly "tagged". This usually happens when all the newer code on `master` has been tested and confirmed working. If you need a bugfix or feature that has not yet made it to a release, it's possible to use the latest "bleeding edge" version using the following steps:
-
-- `git clone https://github.com/wailsapp/wails`
-- `cd wails/v2/cmd/wails`
-- `go install`
-
-NOTE: The directory that you cloned the project into will now be called "clonedir".
-
-The Wails CLI will now be at the very latest version.
-
-### Updating your project
-
-To update projects to use the latest version of the Wails library, update the project's `go.mod` and ensure the following line is at the bottom of the file:
-
-`replace github.com/wailsapp/wails/v2 => `
-
-Example:
-
-On Windows: `replace github.com/wailsapp/wails/v2 => C:\Users\leaan\Documents\wails-v2-beta\wails\v2`
-
-On 'nix: `replace github.com/wailsapp/wails/v2 => /home/me/projects/wails/v2`
-
-To revert to a stable version, run:
-
-`go install github.com/wailsapp/wails/v2/cmd/wails@latest`
-
-## Testing a Branch
-
-If you want to test a branch, follow the instructions above, but ensure you switch the branch you want to test before installing:
-
-- `git clone https://github.com/wailsapp/wails`
-- `cd wails`
-- `git checkout -b branch-to-test --track origin/branch-to-test`
-- `cd v2/cmd/wails`
-- `go install`
-
-Make sure you [update your project](#updating-your-project) as described above.
-
-## Testing a PR
-
-If you want to test a PR, follow the instructions above, but ensure you fetch the PR and switch the branch before installing. Please replace `[IDofThePR]` with the ID of the PR shown on github.com:
-
-- `git clone https://github.com/wailsapp/wails`
-- `cd wails`
-- `git fetch -u origin pull/[IDofThePR]/head:test/pr-[IDofThePR]`
-- `git checkout test/pr-[IDofThePR]`
-- `git reset --hard HEAD`
-- `cd v2/cmd/wails`
-- `go install`
-
-Make sure you [update your project](#updating-your-project) as described above.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/dynamic-assets.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/dynamic-assets.mdx
deleted file mode 100644
index 4b68aef22..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/dynamic-assets.mdx
+++ /dev/null
@@ -1,126 +0,0 @@
-# Dynamic Assets
-
-If you want to load or generate assets for your frontend dynamically, you can achieve that using the [AssetsHandler](../reference/options#assetshandler) option. The AssetsHandler is a generic `http.Handler` which will be called for any non GET request on the assets server and for GET requests which can not be served from the bundled assets because the file is not found.
-
-By installing a custom AssetsHandler, you can serve your own assets using a custom asset server.
-
-## Example
-
-In our example project, we will create a simple assets handler which will load files off disk:
-
-```go title=main.go {16-35,49}
-package main
-
-import (
- "embed"
- "fmt"
- "github.com/wailsapp/wails/v2"
- "github.com/wailsapp/wails/v2/pkg/options"
- "net/http"
- "os"
- "strings"
-)
-
-//go:embed frontend/dist
-var assets embed.FS
-
-type FileLoader struct {
- http.Handler
-}
-
-func NewFileLoader() *FileLoader {
- return &FileLoader{}
-}
-
-func (h *FileLoader) ServeHTTP(res http.ResponseWriter, req *http.Request) {
- var err error
- requestedFilename := strings.TrimPrefix(req.URL.Path, "/")
- println("Requesting file:", requestedFilename)
- fileData, err := os.ReadFile(requestedFilename)
- if err != nil {
- res.WriteHeader(http.StatusBadRequest)
- res.Write([]byte(fmt.Sprintf("Could not load file %s", requestedFilename)))
- }
-
- res.Write(fileData)
-}
-
-func main() {
- // Create an instance of the app structure
- app := NewApp()
-
- // Create application with options
- err := wails.Run(&options.App{
- Title: "helloworld",
- Width: 1024,
- Height: 768,
- Assets: assets,
- BackgroundColour: &options.RGBA{R: 27, G: 38, B: 54, A: 255},
- OnStartup: app.startup,
- AssetsHandler: NewFileLoader(),
- Bind: []interface{}{
- app,
- },
- })
-
- if err != nil {
- println("Error:", err)
- }
-}
-```
-
-When we run the application in dev mode using `wails dev`, we will see the following output:
-
-```
-DEB | [ExternalAssetHandler] Loading 'http://localhost:3001/favicon.ico'
-DEB | [ExternalAssetHandler] Loading 'http://localhost:3001/favicon.ico' failed, using AssetHandler
-Requesting file: favicon.ico
-```
-
-As you can see, the assets handler is called when the default assets server is unable to serve the `favicon.ico` file.
-
-If you right click the main application and select "inspect" to bring up the devtools, you can test this feature out by typing the following into the console:
-
-```
-let response = await fetch('does-not-exist.txt');
-```
-
-This will generate an error in the devtools. We can see that the error is what we expect, returned by our custom assets handler:
-
-
-
-
-
-However, if we request `go.mod`, we will see the following output:
-
-
-
-
-
-This technique can be used to load images directly into the page. If we updated our default vanilla template and replaced the logo image:
-
-```html
-
-```
-
-with:
-
-```html
-
-```
-
-Then we would see the following:
-
-
-
-
-
-:::warning
-Exposing your filesystem in this way is a security risk. It is recommended that you properly manage access
-to your filesystem.
-:::
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/frameless.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/frameless.mdx
deleted file mode 100644
index 4ae507f03..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/frameless.mdx
+++ /dev/null
@@ -1,84 +0,0 @@
-# Frameless Applications
-
-Wails supports application that have no frames. This can be achieved by using the [frameless](../reference/options.mdx#frameless) field in [Application Options](../reference/options.mdx#application-options).
-
-Wails offers a simple solution for dragging the window: Any HTML element that has the CSS style `--wails-draggable:drag` will act as a "drag handle". This property applies to all child elements. If you need to indicate that a nested element should not drag, then use the attribute '--wails-draggable:no-drag' on that element.
-
-
-```html
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-```
-
-For some projects, using a CSS variable may not be possible due to dynamic styling. In this case, you can use the `CSSDragProperty` and `CSSDragValue` application options to define a property and value that will be used to indicate draggable regions:
-
-```go title=main.go
-package main
-
-import (
- "embed"
-
- "github.com/wailsapp/wails/v2"
- "github.com/wailsapp/wails/v2/pkg/options"
-)
-
-//go:embed frontend/dist
-var assets embed.FS
-
-func main() {
- // Create an instance of the app structure
- app := NewApp()
-
- // Create application with options
- err := wails.Run(&options.App{
- Title: "alwaysontop",
- Width: 1024,
- Height: 768,
- Assets: assets,
- Frameless: true,
- CSSDragProperty: "widows",
- CSSDragValue: "1",
- Bind: []interface{}{
- app,
- },
- })
-
- if err != nil {
- println("Error:", err)
- }
-}
-```
-
-```html title=index.html
-
-
-
-
-
- alwaysontop
-
-
-
-
-
-
-
-```
-
-:::info Fullscreen
-If you allow your application to go fullscreen, this drag functionality will be disabled.
-:::
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/ides.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/ides.mdx
deleted file mode 100644
index 5423ea495..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/ides.mdx
+++ /dev/null
@@ -1,125 +0,0 @@
-# IDEs
-
-Wails aims to provide a great development experience. To that aim, we now support generating IDE specific configuration to provide smoother project setup.
-
-Currently, we support [Visual Studio Code](https://code.visualstudio.com/) but aim to support other IDEs such as Goland.
-
-## Visual Studio Code
-
-
-
-
-
-When generating a project using the `-ide vscode` flags, IDE files will be created alongside the other project files. These files are placed into the `.vscode` directory and provide the correct configuration for debugging your application.
-
-The 2 files generated are `tasks.json` and `launch.json`. Below are the files generated for the default vanilla project:
-
-```json title="tasks.json"
-{
- "version": "2.0.0",
- "tasks": [
- {
- "label": "build",
- "type": "shell",
- "options": {
- "cwd": "${workspaceFolder}"
- },
- "command": "go",
- "args": [
- "build",
- "-tags",
- "dev",
- "-gcflags",
- "all=-N -l",
- "-o",
- "build/bin/myproject.exe"
- ]
- }
- ]
-}
-```
-
-```json title="launch.json"
-{
- "version": "0.2.0",
- "configurations": [
- {
- "name": "Wails: Debug myproject",
- "type": "go",
- "request": "launch",
- "mode": "exec",
- "program": "${workspaceFolder}/build/bin/myproject.exe",
- "preLaunchTask": "build",
- "cwd": "${workspaceFolder}",
- "env": {}
- }
- ]
-}
-```
-
-### Configuring the install and build steps
-
-The `tasks.json` file is simple for the default project as there is no `npm install` or `npm run build` step needed. For projects that have a frontend build step, such as the svelte template, we would need to edit `tasks.json` to add the install and build steps:
-
-```json title="tasks.json"
-{
- "version": "2.0.0",
- "tasks": [
- {
- "label": "npm install",
- "type": "npm",
- "script": "install",
- "options": {
- "cwd": "${workspaceFolder}/frontend"
- },
- "presentation": {
- "clear": true,
- "panel": "shared",
- "showReuseMessage": false
- },
- "problemMatcher": []
- },
- {
- "label": "npm run build",
- "type": "npm",
- "script": "build",
- "options": {
- "cwd": "${workspaceFolder}/frontend"
- },
- "presentation": {
- "clear": true,
- "panel": "shared",
- "showReuseMessage": false
- },
- "problemMatcher": []
- },
- {
- "label": "build",
- "type": "shell",
- "options": {
- "cwd": "${workspaceFolder}"
- },
- "command": "go",
- "args": [
- "build",
- "-tags",
- "dev",
- "-gcflags",
- "all=-N -l",
- "-o",
- "build/bin/vscode.exe"
- ],
- "dependsOn": ["npm install", "npm run build"]
- }
- ]
-}
-```
-
-:::info Future Enhancement
-
-In the future, we hope to generate a `tasks.json` that includes the install and build steps automatically.
-
-:::
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/linux-distro-support.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/linux-distro-support.mdx
deleted file mode 100644
index 28a224a26..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/linux-distro-support.mdx
+++ /dev/null
@@ -1,101 +0,0 @@
-# Linux Distro Support
-
-## Overview
-
-Wails offers Linux support but providing installation instructions for all available distributions is an impossible task. Instead, Wails tries to determine if the packages you need to develop applications are available via your system's package manager. Currently, we support the following package managers:
-
-- apt
-- dnf
-- emerge
-- eopkg
-- nixpkgs
-- pacman
-- zypper
-
-## Adding package names
-
-There may be circumstances where your distro uses one of the supported package managers but the package name is different. For example, you may use an Ubuntu derivative, but the package name for gtk may be different. Wails attempts to find the correct package by iterating through a list of package names. The list of packages are stored in the packagemanager specific file in the `v2/internal/system/packagemanager` directory. In our example, this would be `v2/internal/system/packagemanager/apt.go`.
-
-In this file, the list of packages are defined by the `Packages()` method:
-
-```go
-func (a *Apt) Packages() packagemap {
- return packagemap{
- "libgtk-3": []*Package{
- {Name: "libgtk-3-dev", SystemPackage: true, Library: true},
- },
- "libwebkit": []*Package{
- {Name: "libwebkit2gtk-4.0-dev", SystemPackage: true, Library: true},
- },
- "gcc": []*Package{
- {Name: "build-essential", SystemPackage: true},
- },
- "pkg-config": []*Package{
- {Name: "pkg-config", SystemPackage: true},
- },
- "npm": []*Package{
- {Name: "npm", SystemPackage: true},
- },
- "docker": []*Package{
- {Name: "docker.io", SystemPackage: true, Optional: true},
- },
- }
-}
-```
-
-Let's assume that in our linux distro, `libgtk-3` is packaged under the name `lib-gtk3-dev`. We could add support for this by adding the following line:
-
-```go {5}
-func (a *Apt) Packages() packagemap {
- return packagemap{
- "libgtk-3": []*Package{
- {Name: "libgtk-3-dev", SystemPackage: true, Library: true},
- {Name: "lib-gtk3-dev", SystemPackage: true, Library: true},
- },
- "libwebkit": []*Package{
- {Name: "libwebkit2gtk-4.0-dev", SystemPackage: true, Library: true},
- },
- "gcc": []*Package{
- {Name: "build-essential", SystemPackage: true},
- },
- "pkg-config": []*Package{
- {Name: "pkg-config", SystemPackage: true},
- },
- "npm": []*Package{
- {Name: "npm", SystemPackage: true},
- },
- "docker": []*Package{
- {Name: "docker.io", SystemPackage: true, Optional: true},
- },
- }
-}
-```
-
-## Adding new package managers
-
-To add a new package manager, perform the following steps:
-
-- Create a new file in `v2/internal/system/packagemanager` called `.go`, where `` is the name of the package manager.
-- Define a struct that conforms to the package manager interface defined in `pm.go`:
-
-```go
-type PackageManager interface {
- Name() string
- Packages() packagemap
- PackageInstalled(*Package) (bool, error)
- PackageAvailable(*Package) (bool, error)
- InstallCommand(*Package) string
-}
-```
-
-- `Name()` should return the name of the package manager
-- `Packages()` should return a `packagemap`, that provides candidate filenames for dependencies
-- `PackageInstalled()` should return `true` if the given package is installed
-- `PackageAvailable()` should return `true` if the given package is not installed but available for installation
-- `InstallCommand()` should return the exact command to install the given package name
-
-Take a look at the other package managers code to get an idea how this works.
-
-:::info Remember
-If you add support for a new package manager, don't forget to also update this page!
-:::
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/linux.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/linux.mdx
deleted file mode 100644
index 229c282bf..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/linux.mdx
+++ /dev/null
@@ -1,18 +0,0 @@
-# Linux
-
-This page has miscellaneous guides related to developing Wails applications for Linux.
-
-## Video tag doesn't fire "ended" event
-
-When using a video tag, the "ended" event is not fired when the video is finished playing. This is a bug in WebkitGTK, however you can use the following workaround to fix it:
-
-```js
-videoTag.addEventListener("timeupdate", (event) => {
- if (event.target.duration - event.target.currentTime < 0.2) {
- let ended = new Event("ended");
- event.target.dispatchEvent(ended);
- }
-});
-```
-
-Source: [Lyimmi](https://github.com/Lyimmi) on the [discussions board](https://github.com/wailsapp/wails/issues/1729#issuecomment-1212291275)
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/manual-builds.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/manual-builds.mdx
deleted file mode 100644
index dcf192d33..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/manual-builds.mdx
+++ /dev/null
@@ -1,95 +0,0 @@
-# Manual Builds
-
-The Wails CLI does a lot of heavy lifting for the project, but sometimes it's desirable to manually build your project. This document will discuss the different operations the CLI does and how this may be achieved in different ways.
-
-## Build Process
-
-When either `wails build` or `wails dev` are used, the Wails CLI performs a common build process:
-
- - Install frontend dependencies
- - Build frontend project
- - Generate build assets
- - Compile application
- - [optional] Compress application
-
-### Install frontend dependencies
-
-#### CLI Steps
-
-- If the `-s` flag is given, this step is skipped
-- Checks `wails.json` to see if there is an install command in the key `frontend:install`
-- If there isn't, it skips this step
-- If there is, it checks if `package.json` exists in the frontend directory. If it doesn't exist, it skips this step
-- An MD5 sum is generated from the `package.json` file contents
-- It checks for the existence of `package.json.md5` and if it exists, will compare the contents of it (an MD5 sum) with the one generated to see if the contents have changed. If they are the same, this step is skipped
-- If `package.json.md5` does not exist, it creates it using the generated MD5 sum
-- If a build is now required, or `node_modules` does not exist, or the `-f` flag is given, the install command is executed in the frontend directory
-
-#### Manual Steps
-
-This step could be done from the command line or a script with `npm install`.
-
-### Build frontend project
-
-#### Wails CLI
-
-- If the `-s` flag is given, this step is skipped
-- Checks `wails.json` to see if there is a build command in the key `frontend:build`
-- If there isn't, it skips this step
-- If there is, it is executed in the frontend directory
-
-#### Manual Steps
-
-This step could be done from the command line or a script with `npm run build` or whatever the frontend build script is.
-
-### Generate assets
-
-#### Wails CLI
-
-- If `-nopackage` flag is set, this stage is skipped
-- If the `build/appicon.png` file does not exist, a default one is created
-- For Windows, see [Bundling for Windows](#windows)
-- If `build/windows/icon.ico` does not exist, it will create it from the `build/appicon.png` image.
-
-##### Windows
-
-- If `build/windows/icon.ico` does not exist, it will create it from `build/appicon.png` using icon sizes of 256, 128, 64, 48, 32 and 16. This is done using [winicon](https://github.com/leaanthony/winicon).
-- If the `build/windows/.manifest` file does not exist, it creates it from a default version.
-- Compiles the application as a production build (above)
-- Uses [winres](https://github.com/tc-hib/winres) to bundle the icon and manifest into a `.syso` file ready for linking.
-
-#### Manual Steps
-
-- Create `icon.ico` using the [winicon](https://github.com/leaanthony/winicon) CLI tool (or any other tool).
-- Create / Update a `.manifest` file for your application
-- Use the [winres CLI](https://github.com/tc-hib/go-winres) to generate a `.syso` file.
-
-### Compile application
-
-#### Wails CLI
-
-- If the `-clean` flag is provided, the `build` directory is deleted and recreated
-- For `wails dev`, the following default Go flags are used: `-tags dev -gcflags "all=-N -l"`
-- For `wails build`, the following default Go flags are used: `-tags desktop,production -ldflags "-w -s"`
- - On Windows, `-ldflags "-w -h -H windowsgui"`
-- Additional tags passed to the CLI using `-tags` are added to the defaults
-- Additional ldflags passed to the CLI using `-ldflags` are added to the defaults
-- The `-o` flag is passed through
-- The Go compiler specified by `-compiler` will be used for compilation
-
-#### Manual steps
-
-- For dev build, the minimum command would be: `go build -tags dev -gcflags "all=-N -l"`
-- For production build, the minimum command would be: `go build -tags desktop,production -ldflags "-w -s -H windowsgui"`
-- Ensure that you compile in the same directory as the `.syso` file
-
-### Compress application
-
-#### Wails CLI
-
-- If the `-upx` flag has been given, the `upx` program will be run to compress the application with the default settings
-- If `-upxflags` is also passed, these flags are used instead of the default ones
-
-#### Manual steps
-
-- Run `upx [flags]` manually to compress the application.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/migrating.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/migrating.mdx
deleted file mode 100644
index a2f0c4a04..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/migrating.mdx
+++ /dev/null
@@ -1,187 +0,0 @@
-# Migrating from v1
-
-## Overview
-
-Wails v2 is a significant change from v1. This document aims to highlight the changes and the steps in migrating an existing project.
-
-### Creating the Application
-
-In v1, the main application is created using `wails.CreateApp`, bindings are added with `app.Bind`, then the application is run using `app.Run()`.
-
-Example:
-
-```go title="v1"
- app := wails.CreateApp(&wails.AppConfig{
- Title: "MyApp",
- Width: 1024,
- Height: 768,
- JS: js,
- CSS: css,
- Colour: "#131313",
- })
- app.Bind(basic)
- app.Run()
-```
-
-In v2, there is just a single method, `wails.Run()`, that accepts [application options](../reference/options.mdx#application-options).
-
-```go title="v2"
- err := wails.Run(&options.App{
- Title: "MyApp",
- Width: 800,
- Height: 600,
- Assets: assets,
- Bind: []interface{}{
- basic,
- },
- })
-```
-
-### Binding
-
-In v1, it was possible to bind both arbitrary functions and structs. In v2, this has been simplified to only binding structs. The struct instances that were previously passed to the `Bind()` method in v1, are now specified in the `Bind` field of the [application options](../reference/options.mdx#application-options):
-
-```go title="v1"
- app := wails.CreateApp(/* options */)
- app.Bind(basic)
-```
-
-```go title="v2"
- err := wails.Run(&options.App{
- /* other options */
- Bind: []interface{}{
- basic,
- },
- })
-```
-
-In v1, bound methods were available to the frontend at `window.backend`. This has changed to `window.go`.``
-
-### Application Lifecycle
-
-In v1, there were 2 special methods in a bound struct: `WailsInit()` and `WailsShutdown()`. These have been replaced with 3 lifecycle hooks as part of the [application options](../reference/options.mdx#application-options):
-
-- [OnStartup](../reference/options.mdx#onstartup)
-- [OnShutdown](../reference/options.mdx#onshutdown)
-- [OnDomReady](../reference/options.mdx#ondomready)
-
-Note: [OnDomReady](../reference/options.mdx#ondomready) replaces the `wails:ready` system event in v1.
-
-These methods can be standard functions, but a common practice is to have them part of a struct:
-
-```go title="v2"
- basic := NewBasicApp()
- err := wails.Run(&options.App{
- /* Other Options */
- OnStartup: basic.startup,
- OnShutdown: basic.shutdown,
- OnDomReady: basic.domready,
- })
-...
-type Basic struct {
- ctx context.Context
-}
-func (b *Basic) startup(ctx context.Context) {
- b.ctx = ctx
-}
-...
-```
-
-### Runtime
-
-The runtime in v2 is much richer than v1 with support for menus, window manipulation and better dialogs. The signature of the methods has changed slightly - please refer the the [Runtime Reference](../reference/runtime/intro.mdx).
-
-In v1, the [runtime](../reference/runtime/intro.mdx) was available via a struct passed to `WailsInit()`. In v2, the runtime has been moved out to its own package. Each method in the runtime takes the `context.Context` that is passed to the [OnStartup](../reference/options.mdx#onstartup) method.
-
-```go title="Runtime Example"
-package main
-
-import "github.com/wailsapp/wails/v2/pkg/runtime"
-
-type Basic struct {
- ctx context.Context
-}
-
-// startup is called at application startup
-func (a *App) startup(ctx context.Context) {
- a.ctx = ctx
- runtime.LogInfo(ctx, "Application Startup called!")
-}
-
-```
-
-### Assets
-
-The _biggest_ change in v2 is how assets are handled.
-
-In v1, assets were passed via 2 application options:
-
-- `JS` - The application's Javascript
-- `CSS` - The application's CSS
-
-This meant that the responsibility of generating a single JS and CSS file was on the developer. This essentially required the use of complicated packers such as webpack.
-
-In v2, Wails makes no assumptions about your frontend assets, just like a webserver. All of your application assets are passed to the application options as an `embed.FS`.
-
-**This means there is no requirement to bundle your assets, encode images as Base64 or attempt the dark art of bundler configuration to use custom fonts**.
-
-At startup, Wails will scan the given `embed.FS` for `index.html` and use its location as the root path for all the other application assets - just like a webserver would.
-
-Example: An application has the following project layout. All final assets are placed in the `frontend/dist` directory:
-
-```shell
-.
-├── build/
-├── frontend/
-│ └── dist/
-│ ├── index.html
-│ ├── main.js
-│ ├── main.css
-│ └── logo.svg
-├── main.go
-└── wails.json
-```
-
-Those assets may be used by the application by simply creating an `embed.FS`:
-
-```go title="Assets Example"
-//go:embed frontend/dist
-var assets embed.FS
-
-func main() {
- err := wails.Run(&options.App{
- /* Other Options */
- Assets: assets,
- })
-}
-```
-
-Of course, bundlers can be used if you wish to. The only requirement is to pass the final application assets directory to Wails using an `embed.FS` in the `Assets` key of the [application options](../reference/options.mdx#application-options).
-
-### Project Configuration
-
-In v1, the project configuration was stored in the `project.json` file in the project root. In v2, the project configuration is stored in the `wails.json` file in the project root.
-
-The format of the file is slightly different. Here is a comparison:
-
-
-
-| v1 | v2 | Notes |
-| ------------------ | ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| name | name | |
-| description | | Removed |
-| author / name | author / name | |
-| author / email | author / email | |
-| version | version | |
-| binaryname | outputfilename | Changed |
-| frontend / dir | | Removed |
-| frontend / install | frontend:install | Changed |
-| frontend / build | frontend:build | Changed |
-| frontend / bridge | | Removed |
-| frontend / serve | | Removed |
-| tags | | Removed |
-| | wailsjsdir | The directory to generate wailsjs modules |
-| | assetdir | The directory of the compiled frontend assets for `dev` mode. This is normally inferred and could be left empty. |
-| | reloaddirs | Comma separated list of additional directories to watch for changes and to trigger reloads in `dev` mode. This is only needed for some more advanced asset configurations. |
-
-
-
-## Publishing Templates
-
-Publishing a template is simply pushing the files to GitHub. The following best practice is encouraged:
-
-- Remove any unwanted files and directories (such as `.git`) from your frontend directory
-- Ensure that `template.json` is complete, especially `helpurl`
-- Push the files to GitHub
-- Create a PR on the [Community Templates](../community/templates.mdx) page
-- Announce the template on the [Template Announcement](https://github.com/wailsapp/wails/discussions/825) discussion board
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/troubleshooting.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/troubleshooting.mdx
deleted file mode 100644
index 4de561c08..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/troubleshooting.mdx
+++ /dev/null
@@ -1,142 +0,0 @@
-# Troubleshooting
-
-An assortment of troubleshooting tips.
-
-## The `wails` command appears to be missing?
-
-If your system is reporting that the `wails` command is missing, make sure you have followed the Go installation guide correctly. Normally, it means that the `go/bin` directory in your User's home directory is not in the `PATH` environment variable. You will also normally need to close and reopen any open command prompts so that changes to the environment made by the installer are reflected at the command prompt.
-
-## My application is displaying a white/blank screen
-
-Check that your application includes the assets from the correct directory. In your `main.go` file, you will have something similar to the following code:
-
-```go
-//go:embed frontend/dist
-var assets embed.FS
-```
-
-Check that `frontend/dist` contains your application assets.
-
-### Mac
-
-If this happens on Mac, try adding the following to your `Info.plist`:
-
-```xml
-NSAppTransportSecurity
-
- NSAllowsLocalNetworking
-
-
-```
-
-Reference: https://github.com/wailsapp/wails/issues/1504#issuecomment-1174317433
-
-## Mac application not valid
-
-If your built application looks like this in finder:
-
-
-
-
-
-it's likely that your application's `info.plist` is invalid. Update the file in `build/.app/Contents/info.plist` and check if the data is valid, EG check the binary name is correct. To persist the changes, copy the file back to the `build/darwin` directory.
-
-## Cannot call backend method from frontend with variadic arguments
-
-If you have a backend method defined with variadic parameters, eg:
-
-```go
-func (a *App) TestFunc(msg string, args ...interface{}) error {
- // Code
-}
-```
-
-calling this method from the frontend like this will fail:
-
-```js
-var msg = "Hello: ";
-var args = ["Go", "JS"];
-window.go.main.App.TestFunc(msg, ...args)
- .then((result) => {
- //do things here
- })
- .catch((error) => {
- //handle error
- });
-```
-
-Workaround:
-
-```js
-var msg = "Hello ";
-var args = ["Go", "JS"];
-window.go.main.App.TestFunc(msg, args)
- .then((result) => {
- //without the 3 dots
- //do things here
- })
- .catch((error) => {
- //handle error
- });
-```
-
-Credit: https://github.com/wailsapp/wails/issues/1186
-
-## I'm having getting proxy errors when trying to install Wails
-
-If you are getting errors like this:
-
-```
-"https://proxy.golang.org/github.com/wailsapp/wails/cmd/wails/@v/list": dial tcp 172.217.163.49:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
-```
-
-it's probably because the official Go Proxy is being blocked (Users in China have reported this). The solution is to set up the proxy manually, eg:
-
-```
-go env -w GO111MODULE=on
-go env -w GOPROXY=https://goproxy.cn,direct
-```
-
-Source: https://github.com/wailsapp/wails/issues/1233
-
-## The generated Typescript doesn't have the correct types
-
-Sometimes the generated Typescript doesn't have the correct types. To mitigate this, it is possible to specify what types should be generated using the `ts_type` struct tag. For more details, please read [this](https://github.com/tkrajina/typescriptify-golang-structs#custom-types).
-
-## When I navigate away from `index.html`, I am unable to call methods on the frontend
-
-If you navigate away from `index.html` to a new html file, the context will be lost. This can be fixed by adding the following imports to the `` section of any new page you navigate to:
-
-```html
-
-
-
-
-```
-
-Source: https://github.com/wailsapp/wails/discussions/1512
-
-## I get `too many open files` errors on my Mac when I run `wails dev`
-
-By default, macOS will only allow you to open a maximum of 256 files. This can affect the `wails dev` command. This limit can be increased by running: `ulimit -n 1024` in the terminal.
-
-FSNotify is [looking to move to Apple's fsevents](https://github.com/fsnotify/fsnotify/issues/11) for Mac. If this isn't completed soon, we will create our own implementation, tracked [here](https://github.com/wailsapp/wails/issues/1733).
-
-## My Mac app gives me weird compilation errors
-
-A few users have reported seeing compilation errors such as the following:
-
-```shell
-# github.com/wailsapp/wails/v2/internal/frontend/desktop/darwin
-In file included from ../../pkg/mod/github.com/wailsapp/wails/v2@v2.0.0-beta.44.2/internal/frontend/desktop/darwin/callbacks.go:9:
-In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX12.1.sdk/System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:12:
-/Library/Developer/CommandLineTools/SDKs/MacOSX12.1.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSBundle.h:91:143: error: function does not return NSString
-- (NSAttributedString *)localizedAttributedStringForKey:(NSString *)key value:(nullable NSString *)value table:(nullable NSString *)tableName NS_FORMAT_ARGUMENT(1) NS_REFINED_FOR_SWIFT API_AVAILABLE(macos(12.0), ios(15.0), watchos(8.0), tvos(15.0));
- ~~~~~~~~~~~~~~ ^ ~
-/Library/Developer/CommandLineTools/SDKs/MacOSX12.1.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSObjCRuntime.h:103:48: note: expanded from macro 'NS_FORMAT_ARGUMENT'
- #define NS_FORMAT_ARGUMENT(A) __attribute__ ((format_arg(A)))
-```
-
-This is *normally* due to a mismatch with the OS version you are running and the version of the XCode Command Line Tools installed. If you see an error like this, try upgrading your XCode Command Line Tools to the latest version.
-
-Source: https://github.com/wailsapp/wails/issues/1806
\ No newline at end of file
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/vscode.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/vscode.mdx
deleted file mode 100644
index ed258656d..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/vscode.mdx
+++ /dev/null
@@ -1,82 +0,0 @@
-
-# Visual Studio Code
-
-This page is for miscellaneous tips and tricks when using Visual Studio Code with Wails.
-
-## Vetur Configuration
-
-Many thanks to [@Lyimmi](https://github.com/Lyimmi) for this tip. Originally posted [here](https://github.com/wailsapp/wails/issues/1791#issuecomment-1228158349).
-
-Vetur is a popular plugin for Visual Studio Code that provides syntax highlighting and code completion for Vue projects. When loading a Wails project in VSCode, Vetur will throw an error as it is expecting to find the frontend project in the root directory. To fix this, you can do the following:
-
-Create a file named `vetur.config.js` in the project's root.
-
-```javascript
-// vetur.config.js
-/** @type {import('vls').VeturConfig} */
-module.exports = {
- // **optional** default: `{}`
- // override vscode settings
- // Notice: It only affects the settings used by Vetur.
- settings: {
- "vetur.useWorkspaceDependencies": true,
- "vetur.experimental.templateInterpolationService": true
- },
- // **optional** default: `[{ root: './' }]`
- // support monorepos
- projects: [
- {
- // **required**
- // Where is your project?
- // It is relative to `vetur.config.js`.
- // root: './packages/repo1',
- root: './frontend',
- // **optional** default: `'package.json'`
- // Where is `package.json` in the project?
- // We use it to determine the version of vue.
- // It is relative to root property.
- package: './package.json',
- // **optional**
- // Where is TypeScript config file in the project?
- // It is relative to root property.
- tsconfig: './tsconfig.json',
- // **optional** default: `'./.vscode/vetur/snippets'`
- // Where is vetur custom snippets folders?
- snippetFolder: './.vscode/vetur/snippets',
- // **optional** default: `[]`
- // Register globally Vue component glob.
- // If you set it, you can get completion by that components.
- // It is relative to root property.
- // Notice: It won't actually do it. You need to use `require.context` or `Vue.component`
- globalComponents: [
- './src/components/**/*.vue'
- ]
- }
- ]
-}
-```
-
-Next, configure `frontend/tsconfig.json`:
-
-```javascript
-{
- "compilerOptions": {
- "module": "system",
- "noImplicitAny": true,
- "removeComments": true,
- "preserveConstEnums": true,
- "sourceMap": true,
- "outFile": "../../built/local/tsc.js",
- "allowJs": true
- },
- "exclude": [
- "node_modules",
- "**/*.spec.ts"
- ],
- "include": [
- "src/**/*",
- "wailsjs/**/*.ts"
- ]
-}
-```
-This should enable you to now use Vetur as expected.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/windows-installer.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/windows-installer.mdx
deleted file mode 100644
index 21de9a408..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/windows-installer.mdx
+++ /dev/null
@@ -1,56 +0,0 @@
-# NSIS installer
-
-
-
-
-
-
-Wails supports generating Windows installers using the [NSIS installer](https://nsis.sourceforge.io/).
-
-## Installing NSIS
-
-### Windows
-
-The installer is available on the [NSIS Download](https://nsis.sourceforge.io/Download) page.
-
-If you use the chocolatey package manager, run the following script:
-
-```
-choco install nsis
-```
-
-If you install NSIS manually, you need to add the _Bin_ folder, which contains `makensis.exe`, in your NSIS installation to your path. [Here](https://www.architectryan.com/2018/03/17/add-to-the-path-on-windows-10/) is a good tutorial on how to add to path on Windows.
-
-### Linux
-
-The `nsis` package should be available through your distribution's package manager.
-
-### MacOS
-
-NSIS is available to install through homebrew: `brew install nsis`.
-
-## Generating the installer
-
-When a new project is created, Wails generates the NSIS configuration files in `build/windows/installer`. The config data is read from `installer/info.json` and that is configured to use the project's `wails.json` Info section:
-
-```json
-// ...
- "Info": {
- "companyName": "My Company Name",
- "productName": "Wails Vite",
- "productVersion": "1.0.0",
- "copyright": "Copyright.........",
- "comments": "Built using Wails (https://wails.io)"
- },
-```
-
-To generate an installer for your application, use the `-nsis` flag with `wails build`:
-
-```
-wails build -nsis
-```
-
-The installer will now be available in the `build/bin` directory.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/windows.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/windows.mdx
deleted file mode 100644
index 821808c0b..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/windows.mdx
+++ /dev/null
@@ -1,61 +0,0 @@
-# Windows
-
-This page has miscellaneous guides related to developing Wails applications for Windows.
-
-## Handling the WebView2 Runtime Dependency
-
-Wails applications built for Windows have a runtime requirement on the Microsoft [WebView2 Runtime](https://developer.microsoft.com/en-us/microsoft-edge/webview2/). Windows 11 will have this installed by default, but some machines won't. Wails offers an easy approach to dealing with this dependency.
-
-By using the `-webview2` flag when building, you can decide what your application will do when a suitable runtime is not detected (including if the installed runtime is too old). The four options are:
-
-1. Download
-2. Embed
-3. Browser
-4. Error
-
-### Download
-
-This option will prompt the user that no suitable runtime has been found and then offer to download and run the official bootstrapper from Microsoft's WebView2 site. If the user proceeds, the official bootstrapper will be downloaded and run.
-
-### Embed
-
-This option embeds the official bootstrapper within the application. If no suitable runtime has been found, the application will offer to run the bootstrapper. This adds ~150k to the binary size.
-
-### Browser
-
-This option will prompt the user that no suitable runtime has been found and then offer to open a browser to the official WebView2 page where the bootstrapper can be downloaded and installed. The application will then exit, leaving the installation up to the user.
-
-### Error
-
-If no suitable runtime is found, an error is given to the user and no further action taken.
-
-## Fixed version runtime
-
-Another way of dealing with webview2 dependency is shipping it yourself. You can download [fixed version runtime](https://developer.microsoft.com/microsoft-edge/webview2/#download-section) and bundle or download it with your application.
-
-Also, you should specify path to fixed version of webview2 runtime in the `windows.Options` structure when launching wails.
-
-```go
- wails.Run(&options.App{
- Windows: &windows.Options{
- WebviewBrowserPath: "",
- },
- })
-```
-
-Note: When `WebviewBrowserPath` is specified, `error` strategy will be forced in case of minimal required version mismatch or invalid path to a runtime.
-
-## Spawning other programs
-
-When spawning other programs, such as scripts, you will see the window appear on the screen. To hide the window, you can use the following code:
-
-```go
-cmd := exec.Command("your_script.exe")
-cmd.SysProcAttr = &syscall.SysProcAttr{
- HideWindow: true,
- CreationFlags: 0x08000000,
-}
-cmd.Start()
-```
-
-Solution provided by [sithembiso](https://github.com/sithembiso) on the [discussions board](https://github.com/wailsapp/wails/discussions/1734#discussioncomment-3386172).
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/howdoesitwork.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/howdoesitwork.mdx
deleted file mode 100644
index f59873eca..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/howdoesitwork.mdx
+++ /dev/null
@@ -1,355 +0,0 @@
----
-sidebar_position: 20
----
-
-# How does it work?
-
-A Wails application is a standard Go application, with a webkit frontend. The Go part of the application consists of the application code and a runtime library that provides a number of useful operations, like controlling the application window. The frontend is a webkit window that will display the frontend assets. Also available to the frontend is a Javascript version of the runtime library. Finally, it is possible to bind Go methods to the frontend, and these will appear as Javascript methods that can be called, just as if they were local Javascript methods.
-
-
-
-
-
-## The Main Application
-
-### Overview
-
-The main application consists of a single call to `wails.Run()`. It accepts the application configuration which describes the size of the application window, the window title, what assets to use, etc. A basic application might look like this:
-
-```go title="main.go"
-package main
-
-import (
- "embed"
- "log"
-
- "github.com/wailsapp/wails/v2"
- "github.com/wailsapp/wails/v2/pkg/options"
-)
-
-//go:embed frontend/dist
-var assets embed.FS
-
-func main() {
-
- app := &App{}
-
- err := wails.Run(&options.App{
- Title: "Basic Demo",
- Width: 1024,
- Height: 768,
- Assets: &assets,
- OnStartup: app.startup,
- OnShutdown: app.shutdown,
- Bind: []interface{}{
- app,
- },
- })
- if err != nil {
- log.Fatal(err)
- }
-}
-
-
-type App struct {
- ctx context.Context
-}
-
-func (b *App) startup(ctx context.Context) {
- b.ctx = ctx
-}
-
-func (b *App) shutdown(ctx context.Context) {}
-
-func (b *App) Greet(name string) string {
- return fmt.Sprintf("Hello %s!", name)
-}
-```
-
-### Options rundown
-
-This example has the following options set:
-
-- `Title` - The text that should appear in the window's title bar
-- `Width` & `Height` - The dimensions of the window
-- `Assets` - The application's frontend assets
-- `OnStartup` - A callback for when the window is created and is about to start loading the frontend assets
-- `OnShutdown` - A callback for when the application is about to quit
-- `Bind` - A slice of struct instances that we wish to expose to the frontend
-
-A full list of application options can be found in the [Options Reference](reference/options).
-
-#### Assets
-
-The `Assets` option is mandatory as you can't have a Wails application without frontend assets. Those assets can be any files you would expect to find in a web application - html, js, css, svg, png, etc. **There is no requirement to generate asset bundles** - plain files will do. When the application starts, it will attempt to load `index.html` from your assets and the frontend will essentially work as a browser from that point on. It is worth noting that there is no requirement on where in the `embed.FS` the files live. It is likely that the embed path uses a nested directory relative to your main application code, such as `frontend/dist`:
-
-```go title="main.go"
-//go:embed frontend/dist
-var assets embed.FS
-```
-
-At startup, Wails will iterate the embedded files looking for the directory containing `index.html`. All other assets will be loaded relative to this directory.
-
-As production binaries use the files contained in `embed.FS`, there are no external files required to be shipped with the application.
-
-When running in development mode using the `wails dev` command, the assets are loaded off disk, and any changes result in a "live reload". The location of the assets will be inferred from the `embed.FS`.
-
-More details can be found in the [Application Development Guide](guides/application-development.mdx).
-
-#### Application Lifecycle Callbacks
-
-Just before the frontend is about to load `index.html`, a callback is made to the function provided in [OnStartup](reference/options.mdx#onstartup). A standard Go context is passed to this method. This context is required when calling the runtime so a standard pattern is to save a reference to in this method. Just before the application shuts down, the [OnShutdown](reference/options.mdx#onshutdown) callback is called in the same way, again with the context. There is also an [OnDomReady](reference/options.mdx#ondomready) callback for when the frontend has completed loading all assets in `index.html` and is equivalent of the [`body onload`](https://www.w3schools.com/jsref/event_onload.asp) event in Javascript. It is also possible to hook into the window close (or application quit) event by setting the option [OnBeforeClose](reference/options.mdx#onbeforeclose).
-
-#### Method Binding
-
-The `Bind` option is one of the most important options in a Wails application. It specifies which struct methods to expose to the frontend. Think of structs like "controllers" in a traditional web application. When the application starts, it examines the struct instances listed in the `Bind` field in the options, determines which methods are public (starts with an uppercase letter) and will generate Javascript versions of those methods that can be called by the frontend code.
-
-:::info Note
-
-Wails requires that you pass in an _instance_ of the struct for it to bind it correctly
-
-:::
-
-In this example, we create a new `App` instance and then add this instance to the `Bind` option in `wails.Run`:
-
-```go {16,24} title="main.go"
-package main
-
-import (
- "embed"
- "log"
-
- "github.com/wailsapp/wails/v2"
- "github.com/wailsapp/wails/v2/pkg/options"
-)
-
-//go:embed frontend/dist
-var assets embed.FS
-
-func main() {
-
- app := &App{}
-
- err := wails.Run(&options.App{
- Title: "Basic Demo",
- Width: 1024,
- Height: 768,
- Assets: &assets,
- Bind: []interface{}{
- app,
- },
- })
- if err != nil {
- log.Fatal(err)
- }
-}
-
-
-type App struct {
- ctx context.Context
-}
-
-func (a *App) Greet(name string) string {
- return fmt.Sprintf("Hello %s!", name)
-}
-```
-
-You may bind as many structs as you like. Just make sure you create an instance of it and pass it in `Bind`:
-
-```go {8-10}
- //...
- err := wails.Run(&options.App{
- Title: "Basic Demo",
- Width: 1024,
- Height: 768,
- Assets: &assets,
- Bind: []interface{}{
- app,
- &mystruct1{},
- &mystruct2{},
- },
- })
-
-```
-
-When you run `wails dev` (or `wails generate module`), a frontend module will be generated containing the following:
-
-- Javascript bindings for all bound methods
-- Typescript declarations for all bound methods
-- Typescript definitions for all Go structs used as inputs or outputs by the bound methods
-
-This makes it incredibly simple to call Go code from the frontend, using the same strongly typed datastructures.
-
-## The Frontend
-
-### Overview
-
-The frontend is a collection of files rendered by webkit. It's like a browser and webserver in one. There is virtually[^1] no limit to which frameworks or libraries you can use. The main points of interaction between the frontend and your Go code are:
-
-- Calling bound Go methods
-- Calling runtime methods
-
-### Calling bound Go methods
-
-When you run your application with `wails dev`, it will automatically generate Javascript bindings for your structs in a directory called `wailsjs/go` (You can also do this by running `wails generate module`). The generated files mirror the package names in your application. In the example above, we bind `app`, which has one public method `Greet`. This will lead to the generation of the following files:
-
-```bash
-wailsjs
- └─go
- └─main
- ├─App.d.ts
- └─App.js
-```
-
-Here we can see that there is a `main` package that contains the Javascript bindings for the bound `App` struct, as well as the Typescript declaration file for those methods. To call `Greet` from our frontend, we simply import the method and call it like a regular Javascript function:
-
-```javascript
-// ...
-import { Greet } from "../wailsjs/go/main/App";
-
-function doGreeting(name) {
- Greet(name).then((result) => {
- // Do something with result
- });
-}
-```
-
-The Typescript declaration file gives you the correct types for the bound methods:
-
-```ts
-export function Greet(arg1: string): Promise;
-```
-
-The generated methods return a Promise. A successful call will result in the first return value from the Go call to be passed to the `resolve` handler. An unsuccessful call is when a Go method that has an error type as it's second return value, passes an error instance back to the caller. This is passed back via the `reject` handler. In the example above, `Greet` only returns a `string` so the Javascript call will never reject - unless invalid data is passed to it.
-
-All data types are correctly translated between Go and Javascript. Even structs. If you return a struct from a Go call, it will be returned to your frontend as a Javascript class. Note: If you wish to use structs, you **must** define `json` struct tags for your fields!
-
-:::info Note
-Anonymous nested structs are not supported at this time.
-:::
-
-It is possible to send structs back to Go. Any Javascript map/class passed as an argument that is expecting a struct, will be converted to that struct type. To make this process a lot easier, in `dev` mode, a TypeScript module is generated, defining all the struct types used in bound methods. Using this module, it's possible to construct and send native Javascript objects to the Go code.
-
-There is also support for Go methods that use structs in their signature. All Go structs specified by a bound method (either as parameters or return types) will have Typescript versions auto generated as part of the Go code wrapper module. Using these, it's possible to share the same data model between Go and Javascript.
-
-Example: We update our `Greet` method to accept a `Person` instead of a string:
-
-```go title="main.go"
-type Person struct {
- Name string `json:"name"`
- Age uint8 `json:"age"`
- Address *Address `json:"address"`
-}
-
-type Address struct {
- Street string `json:"street"`
- Postcode string `json:"postcode"`
-}
-
-func (a *App) Greet(p Person) string {
- return fmt.Sprintf("Hello %s (Age: %d)!", p.Name, p.Age)
-}
-```
-
-The `wailsjs/go/main/App.js` file will still have the following code:
-
-```js title="App.js"
-export function Greet(arg1) {
- return window["go"]["main"]["App"]["Greet"](arg1);
-}
-```
-
-But the `wailsjs/go/main/App.d.ts` file will be updated with the following code:
-
-```ts title="App.d.ts"
-import { main } from "../models";
-
-export function Greet(arg1: main.Person): Promise;
-```
-
-As we can see, the "main" namespace is imported from a new "models.ts" file. This file contains all the struct definitions used by our bound methods. In this example, this is a `Person` struct. If we look at `models.ts`, we can see how the models are defined:
-
-```ts title="models.ts"
-export namespace main {
- export class Address {
- street: string;
- postcode: string;
-
- static createFrom(source: any = {}) {
- return new Address(source);
- }
-
- constructor(source: any = {}) {
- if ("string" === typeof source) source = JSON.parse(source);
- this.street = source["street"];
- this.postcode = source["postcode"];
- }
- }
- export class Person {
- name: string;
- age: number;
- address?: Address;
-
- static createFrom(source: any = {}) {
- return new Person(source);
- }
-
- constructor(source: any = {}) {
- if ("string" === typeof source) source = JSON.parse(source);
- this.name = source["name"];
- this.age = source["age"];
- this.address = this.convertValues(source["address"], Address);
- }
-
- convertValues(a: any, classs: any, asMap: boolean = false): any {
- if (!a) {
- return a;
- }
- if (a.slice) {
- return (a as any[]).map((elem) => this.convertValues(elem, classs));
- } else if ("object" === typeof a) {
- if (asMap) {
- for (const key of Object.keys(a)) {
- a[key] = new classs(a[key]);
- }
- return a;
- }
- return new classs(a);
- }
- return a;
- }
- }
-}
-```
-
-So long as you have TypeScript as part of your frontend build configuration, you can use these models in the following way:
-
-```js title="mycode.js"
-import { Greet } from "../wailsjs/go/main/App";
-import { main } from "../wailsjs/go/models";
-
-function generate() {
- let person = new main.Person();
- person.name = "Peter";
- person.age = 27;
- Greet(person).then((result) => {
- console.log(result);
- });
-}
-```
-
-The combination of generated bindings and TypeScript models makes for a powerful development environment.
-
-More information on Binding can be found in the [Binding Methods](guides/application-development.mdx#binding-methods) section of the [Application Development Guide](guides/application-development.mdx).
-
-### Calling runtime methods
-
-The Javascript runtime is located at `window.runtime` and contains many methods to do various tasks such as emit an event or perform logging operations:
-
-```js title="mycode.js"
-window.runtime.EventsEmit("my-event", 1);
-```
-
-More details about the JS runtime can be found in the [Runtime Reference](reference/runtime/intro).
-
-[^1]: There is a very small subset of libraries that use features unsupported in WebViews. There are often alternatives and workarounds for such cases.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/introduction.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/introduction.mdx
deleted file mode 100644
index 4e65f932e..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/introduction.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-sidebar_position: 1
----
-
-# 소개
-
-Wails는 Go 및 웹 기술을 사용하여 데스크톱 앱을 작성할 수 있는 프로젝트입니다.
-
-Consider it a lightweight and fast Electron alternative for Go. You can easily build applications with the flexibility and power of Go, combined with a rich, modern frontend.
-
-### 기능
-
-- Native Menus, Dialogs, Theming and Translucency
-- Windows, macOS and linux support
-- Built in templates for Svelte, React, Preact, Vue, Lit and Vanilla JS
-- Easily call Go methods from Javascript
-- Automatic Go struct to Typescript model generation
-- No CGO or external DLLs required on Windows
-- Live development mode using the power of [Vite](https://vite.net/)
-- Powerful CLI to easily Create, Build and Package applications
-- A rich [runtime library](/docs/next/reference/runtime)
-- Applications built with Wails are Apple & Microsoft Store compliant
-
-
-[varly](https://varly.app)는 Wails를 사용하여 작성된 MacOS & Windows용 데스크톱 애플리케이션입니다. 보기 좋을 뿐만 아니라 최신 네이티브 앱에서 바라는 기본 메뉴 구성과 반투명도를 사용합니다.
-
-
-
-
-
-When clicked, that will open an about message box:
-
-
-
-
-
-
-
-## Linux Specific Options
-
-### Icon
-
-Sets up the icon representing the window. This icon is used when the window is minimized (also known as iconified).
-
-Type: `[]byte`
-
-Some window managers or desktop environments may also place it in the window frame, or display it in other contexts. On others, the icon is not used at all, so your mileage may vary.
-
-NOTE: Gnome on Wayland at least does not display this icon. To have a application icon there, a `.desktop` file has to be used. On KDE it should work.
-
-The icon should be provided in whatever size it was naturally drawn; that is, don’t scale the image before passing it. Scaling is postponed until the last minute, when the desired final size is known, to allow best quality.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/project-config.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/project-config.mdx
deleted file mode 100644
index 3dc1cf002..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/project-config.mdx
+++ /dev/null
@@ -1,51 +0,0 @@
----
-sidebar_position: 5
----
-
-# Project Config
-
-The project config resides in the `wails.json` file in the project directory. The structure of the config is:
-
-```json
-{
- "name": "[The project name]",
- "assetdir": "[Relative path to the directory containing the compiled assets, this is normally inferred and could be left empty]",
- "reloaddirs": "[Additional directories to trigger reloads (comma separated), this is only used for some advanced asset configurations]",
- "frontend:install": "[The command to install node dependencies, run in the frontend directory - often `npm install`]",
- "frontend:build": "[The command to build the assets, run in the frontend directory - often `npm run build`]",
- "frontend:dev": "[This command has been replaced by frontend:dev:build. If frontend:dev:build is not specified will falls back to this command. If this command is also not specified will falls back to frontend:build]",
- "frontend:dev:build": "[This command is the dev equivalent of frontend:build. If not specified falls back to frontend:dev]",
- "frontend:dev:install": "[This command is the dev equivalent of frontend:install. If not specified falls back to frontend:install]",
- "frontend:dev:watcher": "[This command is run in a separate process on `wails dev`. Useful for 3rd party watchers or starting 3d party dev servers]",
- "frontend:dev:serverUrl": "[URL to a 3rd party dev server to be used to serve assets, EG Vite. If this is set to 'auto' then the devServerUrl will be inferred from the Vite output]",
- "wailsjsdir": "[Relative path to the directory that the auto-generated JS modules will be created]",
- "version": "[Project config version]",
- "outputfilename": "[The name of the binary]",
- "debounceMS": 100, // The default time the dev server waits to reload when it detects a change in assets
- "devServer": "[Address to bind the wails dev sever to. Default: localhost:34115]",
- "appargs": "[Arguments passed to the application in shell style when in dev mode]",
- "runNonNativeBuildHooks": false, // Defines if build hooks should be run though they are defined for an OS other than the host OS.
- "preBuildHooks": {
- "GOOS/GOARCH": "[The command that will be executed before a build of the specified GOOS/GOARCH: ${platform} is replaced with the "GOOS/GOARCH". The "GOOS/GOARCH" hook is executed before the "GOOS/*" and "*/*" hook.]",
- "GOOS/*": "[The command that will be executed before a build of the specified GOOS: ${platform} is replaced with the "GOOS/GOARCH". The "GOOS/*" hook is executed before the "*/*" hook.]",
- "*/*": "[The command that will be executed before every build: ${platform} is replaced with the "GOOS/GOARCH".]"
- },
- "postBuildHooks": {
- "GOOS/GOARCH": "[The command that will be executed after a build of the specified GOOS/GOARCH: ${platform} is replaced with the "GOOS/GOARCH" and ${bin} with the path to the compiled binary. The "GOOS/GOARCH" hook is executed before the "GOOS/*" and "*/*" hook.]",
- "GOOS/*": "[The command that will be executed after a build of the specified GOOS: ${platform} is replaced with the "GOOS/GOARCH" and ${bin} with the path to the compiled binary. The "GOOS/*" hook is executed before the "*/*" hook.]",
- "*/*": "[The command that will be executed after every build: ${platform} is replaced with the "GOOS/GOARCH" and ${bin} with the path to the compiled binary.]"
- },
- "info": { // Data used to populate manifests and version info.
- "companyName": "[The company name. Default: [The project name]]",
- "productName": "[The product name. Default: [The project name]]",
- "productVersion": "[The version of the product. Default: '1.0.0']",
- "copyright": "[The copyright of the product. Default: 'Copyright.........']",
- "comments": "[A short comment of the app. Default: 'Built using Wails (https://wails.app)']"
- },
- "nsisType": "['multiple': One installer per architecture. 'single': Single universal installer for all architectures being built. Default: 'multiple']"
-}
-```
-
-This file is read by the Wails CLI when running `wails build` or `wails dev`.
-
-The `assetdir`, `reloaddirs`, `wailsjsdir`, `debounceMS`, `devserver` and `frontenddevserverurl` flags in `wails build/dev` will update the project config and thus become defaults for subsequent runs.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/_category_.json b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/_category_.json
deleted file mode 100644
index ac6d55488..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Runtime",
- "position": 1
-}
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/browser.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/browser.mdx
deleted file mode 100644
index 976ca1d80..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/browser.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
----
-sidebar_position: 7
----
-
-# Browser
-
-These methods are related to the system browser.
-
-### BrowserOpenURL
-
-Opens the given URL in the system browser.
-
-Go: `BrowserOpenURL(ctx context.Context, url string)` JS: `BrowserOpenURL(url string)`
-
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/dialog.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/dialog.mdx
deleted file mode 100644
index ad65257ee..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/dialog.mdx
+++ /dev/null
@@ -1,283 +0,0 @@
----
-sidebar_position: 5
----
-
-# Dialog
-
-This part of the runtime provides access to native dialogs, such as File Selectors and Message boxes.
-
-:::info Javascript
-Dialog is currently unsupported in the JS runtime.
-:::
-
-### OpenDirectoryDialog
-
-Opens a dialog that prompts the user to select a directory. Can be customised using [OpenDialogOptions](#opendialogoptions).
-
-Go: `OpenDirectoryDialog(ctx context.Context, dialogOptions OpenDialogOptions) (string, error)`
-
-Returns: Selected directory (blank if the user cancelled) or an error
-
-### OpenFileDialog
-
-Opens a dialog that prompts the user to select a file. Can be customised using [OpenDialogOptions](#opendialogoptions).
-
-Go: `OpenFileDialog(ctx context.Context, dialogOptions OpenDialogOptions) (string, error)`
-
-Returns: Selected file (blank if the user cancelled) or an error
-
-### OpenMultipleFilesDialog
-
-Opens a dialog that prompts the user to select multiple files. Can be customised using [OpenDialogOptions](#opendialogoptions).
-
-Go: `OpenMultipleFilesDialog(ctx context.Context, dialogOptions OpenDialogOptions) ([]string, error)`
-
-Returns: Selected files (nil if the user cancelled) or an error
-
-### SaveFileDialog
-
-Opens a dialog that prompts the user to select a filename for the purposes of saving. Can be customised using [SaveDialogOptions](#savedialogoptions).
-
-Go: `SaveFileDialog(ctx context.Context, dialogOptions SaveDialogOptions) (string, error)`
-
-Returns: The selected file (blank if the user cancelled) or an error
-
-### MessageDialog
-
-Displays a message using a message dialog. Can be customised using [MessageDialogOptions](#messagedialogoptions).
-
-Go: `MessageDialog(ctx context.Context, dialogOptions MessageDialogOptions) (string, error)`
-
-Returns: The text of the selected button or an error
-
-## Options
-
-### OpenDialogOptions
-
-```go
-type OpenDialogOptions struct {
- DefaultDirectory string
- DefaultFilename string
- Title string
- Filters []FileFilter
- ShowHiddenFiles bool
- CanCreateDirectories bool
- ResolvesAliases bool
- TreatPackagesAsDirectories bool
-}
-```
-
-| Field | Description | Win | Mac | Lin |
-| -------------------------- | ---------------------------------------------- | --- | --- | --- |
-| DefaultDirectory | The directory the dialog will show when opened | ✅ | ✅ | ✅ |
-| DefaultFilename | The default filename | ✅ | ✅ | ✅ |
-| Title | Title for the dialog | ✅ | ✅ | ✅ |
-| [Filters](#filefilter) | A list of file filters | ✅ | ✅ | ✅ |
-| ShowHiddenFiles | Show files hidden by the system | | ✅ | ✅ |
-| CanCreateDirectories | Allow user to create directories | | ✅ | |
-| ResolvesAliases | If true, returns the file not the alias | | ✅ | |
-| TreatPackagesAsDirectories | Allow navigating into packages | | ✅ | |
-
-### SaveDialogOptions
-
-```go
-type SaveDialogOptions struct {
- DefaultDirectory string
- DefaultFilename string
- Title string
- Filters []FileFilter
- ShowHiddenFiles bool
- CanCreateDirectories bool
- TreatPackagesAsDirectories bool
-}
-```
-
-| Field | Description | Win | Mac | Lin |
-| -------------------------- | ---------------------------------------------- | --- | --- | --- |
-| DefaultDirectory | The directory the dialog will show when opened | ✅ | ✅ | ✅ |
-| DefaultFilename | The default filename | ✅ | ✅ | ✅ |
-| Title | Title for the dialog | ✅ | ✅ | ✅ |
-| [Filters](#filefilter) | A list of file filters | ✅ | ✅ | ✅ |
-| ShowHiddenFiles | Show files hidden by the system | | ✅ | ✅ |
-| CanCreateDirectories | Allow user to create directories | | ✅ | |
-| TreatPackagesAsDirectories | Allow navigating into packages | | ✅ | |
-
-### MessageDialogOptions
-
-```go
-type MessageDialogOptions struct {
- Type DialogType
- Title string
- Message string
- Buttons []string
- DefaultButton string
- CancelButton string
-}
-```
-
-| Field | Description | Win | Mac | Lin |
-| ------------- | ------------------------------------------------------------------------- | --- | --- | --- |
-| Type | The type of message dialog, eg question, info... | ✅ | ✅ | ✅ |
-| Title | Title for the dialog | ✅ | ✅ | ✅ |
-| Message | The message to show the user | ✅ | ✅ | ✅ |
-| Buttons | A list of button titles | | ✅ | |
-| DefaultButton | The button with this text should be treated as default. Bound to `return` | | ✅ | |
-| CancelButton | The button with this text should be treated as cancel. Bound to `escape` | | ✅ | |
-
-#### Windows
-
-Windows has standard dialog types in which the buttons are not customisable. The value returned will be one of: "Ok", "Cancel", "Abort", "Retry", "Ignore", "Yes", "No", "Try Again" or "Continue"
-
-#### Linux
-
-Linux has standard dialog types in which the buttons are not customisable. The value returned will be one of: "Ok", "Cancel", "Yes", "No"
-
-#### Mac
-
-A message dialog on Mac may specify up to 4 buttons. If no `DefaultButton` or `CancelButton` is given, the first button is considered default and is bound to the `return` key.
-
-For the following code:
-
-```go
-selection, err := runtime.MessageDialog(b.ctx, runtime.MessageDialogOptions{
- Title: "It's your turn!",
- Message: "Select a number",
- Buttons: []string{"one", "two", "three", "four"},
-})
-```
-
-the first button is shown as default:
-
-
-
-
-
-
-
-And if we specify `DefaultButton` to be "two":
-
-```go
-selection, err := runtime.MessageDialog(b.ctx, runtime.MessageDialogOptions{
- Title: "It's your turn!",
- Message: "Select a number",
- Buttons: []string{"one", "two", "three", "four"},
- DefaultButton: "two",
-})
-```
-
-the second button is shown as default. When `return` is pressed, the value "two" is returned.
-
-
-
-
-
-
-
-If we now specify `CancelButton` to be "three":
-
-```go
-selection, err := runtime.MessageDialog(b.ctx, runtime.MessageDialogOptions{
- Title: "It's your turn!",
- Message: "Select a number",
- Buttons: []string{"one", "two", "three", "four"},
- DefaultButton: "two",
- CancelButton: "three",
-})
-```
-
-the button with "three" is shown at the bottom of the dialog. When `escape` is pressed, the value "three" is returned:
-
-
-
-
-
-
-
-
-
-#### DialogType
-
-```go
-const (
- InfoDialog DialogType = "info"
- WarningDialog DialogType = "warning"
- ErrorDialog DialogType = "error"
- QuestionDialog DialogType = "question"
- )
-```
-
-### FileFilter
-
-```go
-type FileFilter struct {
- DisplayName string // Filter information EG: "Image Files (*.jpg, *.png)"
- Pattern string // semi-colon separated list of extensions, EG: "*.jpg;*.png"
-}
-```
-
-#### Windows
-
-Windows allows you to use multiple file filters in dialog boxes. Each FileFilter will show up as a separate entry in the dialog:
-
-
-
-
-
-
-
-
-
-#### Linux
-
-Linux allows you to use multiple file filters in dialog boxes. Each FileFilter will show up as a separate entry in the dialog:
-
-
-
-
-
-
-
-
-
-#### Mac
-
-Mac dialogs only have the concept of a single set of patterns to filter files. If multiple FileFilters are provided, Wails will use all the Patterns defined.
-
-Example:
-
-```go
- selection, err := runtime.OpenFileDialog(b.ctx, runtime.OpenDialogOptions{
- Title: "Select File",
- Filters: []runtime.FileFilter{
- {
- DisplayName: "Images (*.png;*.jpg)",
- Pattern: "*.png;*.jpg",
- }, {
- DisplayName: "Videos (*.mov;*.mp4)",
- Pattern: "*.mov;*.mp4",
- },
- },
- })
-```
-
-This will result in the Open File dialog using `*.png,*.jpg,*.mov,*.mp4` as a filter.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/events.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/events.mdx
deleted file mode 100644
index 75e8b0a50..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/events.mdx
+++ /dev/null
@@ -1,38 +0,0 @@
----
-sidebar_position: 2
----
-
-# Events
-
-The Wails runtime provides a unified events system, where events can be emitted or received by either Go or Javascript. Optionally, data may be passed with the events. Listeners will receive the data in the local data types.
-
-### EventsOn
-
-This method sets up a listener for the given event name. When an event of type `eventName` is [emitted](#EventsEmit), the callback is triggered. Any additional data sent with the emitted event will be passed to the callback.
-
-Go: `EventsOn(ctx context.Context, eventName string, callback func(optionalData ...interface{}))` JS: `EventsOn(eventName string, callback function(optionalData?: any))`
-
-### EventsOff
-
-This method unregisters the listener for the given event name, optionally multiple listeneres can be unregistered via `additionalEventNames`.
-
-Go: `EventsOff(ctx context.Context, eventName string, additionalEventNames ...string)` JS: `EventsOff(eventName string, ...additionalEventNames)`
-
-### EventsOnce
-
-This method sets up a listener for the given event name, but will only trigger once.
-
-Go: `EventsOnce(ctx context.Context, eventName string, callback func(optionalData ...interface{}))` JS: `EventsOnce(eventName string, callback function(optionalData?: any))`
-
-### EventsOnMultiple
-
-This method sets up a listener for the given event name, but will only trigger a maximum of `counter` times.
-
-Go: `EventsOnMultiple(ctx context.Context, eventName string, callback func(optionalData ...interface{}), counter int)` JS: `EventsOnMultiple(eventName string, callback function(optionalData?: any), counter int)`
-
-### EventsEmit
-
-This method emits the given event. Optional data may be passed with the event. This will trigger any event listeners.
-
-Go: `EventsEmit(ctx context.Context, eventName string, optionalData ...interface{})` JS: `EventsEmit(ctx context, optionalData function(optionalData?: any))`
-
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/intro.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/intro.mdx
deleted file mode 100644
index 6c02c71cd..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/intro.mdx
+++ /dev/null
@@ -1,73 +0,0 @@
----
-sidebar_position: 1
----
-
-# Introduction
-
-The runtime is a library that provides utility methods for your application. There is both a Go and Javascript runtime and the aim is to try and keep them at parity where possible.
-
-It has utility methods for:
-
-- [Window](window.mdx)
-- [Menu](menu.mdx)
-- [Dialog](dialog.mdx)
-- [Events](events.mdx)
-- [Browser](browser.mdx)
-- [Log](log.mdx)
-
-The Go Runtime is available through importing `github.com/wailsapp/wails/v2/pkg/runtime`. All methods in this package take a context as the first parameter. This context should be obtained from the [OnStartup](../options.mdx#onstartup) or [OnDomReady](../options.mdx#ondomready) hooks.
-
-:::info Note
-
-Whilst the context will be provided to the [OnStartup](../options.mdx#onstartup) method, there's no guarantee the runtime will work in this method as the window is initialising in a different thread. If you wish to call runtime methods at startup, use [OnDomReady](../options.mdx#ondomready).
-
-:::
-
-The Javascript library is available to the frontend via the `window.runtime` map. There is a runtime package generated when using `dev` mode that provides Typescript declarations for the runtime. This should be located in the `wailsjs` directory in your frontend directory.
-
-### Hide
-
-Go: `Hide(ctx context.Context)` JS: `Hide()`
-
-Hides the application.
-
-:::info Note On Mac, this will hide the application in the same way as the `Hide` menu item in standard Mac applications. This is different to hiding the window, but the application still being in the foreground. For Windows and Linux, this is currently the same as `WindowHide`. :::
-
-### Show
-
-Shows the application.
-
-:::info Note On Mac, this will bring the application back into the foreground. For Windows and Linux, this is currently the same as `WindowShow`. :::
-
-Go: `Show(ctx context.Context)` JS: `Show()`
-
-### Quit
-
-Quits the application.
-
-Go: `Quit(ctx context.Context)` JS: `Quit()`
-
-### Environment
-
-Returns details of the current environment.
-
-Go: `Environment(ctx context.Context) EnvironmentInfo` JS: `Environment(): Promise`
-
-#### EnvironmentInfo
-
-Go:
-```go
-type EnvironmentInfo struct {
- BuildType string
- Platform string
- Arch string
-}
-```
-JS:
-```ts
-interface EnvironmentInfo {
- buildType: string;
- platform: string;
- arch: string;
-}
-```
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/log.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/log.mdx
deleted file mode 100644
index e5e6ea7ac..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/log.mdx
+++ /dev/null
@@ -1,130 +0,0 @@
----
-sidebar_position: 3
----
-
-# Log
-
-The Wails runtime provides a logging mechanism that may be called from Go or Javascript. Like most loggers, there are a number of log levels:
-
-- Trace
-- Debug
-- Info
-- Warning
-- Error
-- Fatal
-
-The logger will output any log message at the current, or higher, log level. Example: The `Debug` log level will output all messages except `Trace` messages.
-
-### LogPrint
-
-Logs the given message as a raw message.
-
-Go: `LogPrint(ctx context.Context, message string)` JS: `LogPrint(message: string)`
-
-### LogPrintf
-
-Logs the given message as a raw message.
-
-Go: `LogPrintf(ctx context.Context, format string, args ...interface{})`
-
-### LogTrace
-
-Logs the given message at the `Trace` log level.
-
-Go: `LogTrace(ctx context.Context, message string)` JS: `LogTrace(message: string)`
-
-### LogTracef
-
-Logs the given message at the `Trace` log level.
-
-Go: `LogTracef(ctx context.Context, format string, args ...interface{})`
-
-### LogDebug
-
-Logs the given message at the `Debug` log level.
-
-Go: `LogDebug(ctx context.Context, message string)` JS: `LogDebug(message: string)`
-
-### LogDebugf
-
-Logs the given message at the `Debug` log level.
-
-Go: `LogDebugf(ctx context.Context, format string, args ...interface{})`
-
-### LogInfo
-
-Logs the given message at the `Info` log level.
-
-Go: `LogInfo(ctx context.Context, message string)` JS: `LogInfo(message: string)`
-
-### LogInfof
-
-Logs the given message at the `Info` log level.
-
-Go: `LogInfof(ctx context.Context, format string, args ...interface{})`
-
-### LogWarning
-
-Logs the given message at the `Warning` log level.
-
-Go: `LogWarning(ctx context.Context, message string)` JS: `LogWarning(message: string)`
-
-### LogWarningf
-
-Logs the given message at the `Warning` log level.
-
-Go: `LogWarningf(ctx context.Context, format string, args ...interface{})`
-
-### LogError
-
-Logs the given message at the `Error` log level.
-
-Go: `LogError(ctx context.Context, message string)` JS: `LogError(message: string)`
-
-### LogErrorf
-
-Logs the given message at the `Error` log level.
-
-Go: `LogErrorf(ctx context.Context, format string, args ...interface{})`
-
-### LogFatal
-
-Logs the given message at the `Fatal` log level.
-
-Go: `LogFatal(ctx context.Context, message string)` JS: `LogFatal(message: string)`
-
-### LogFatalf
-
-Logs the given message at the `Fatal` log level.
-
-Go: `LogFatalf(ctx context.Context, format string, args ...interface{})`
-
-### LogSetLogLevel
-
-Sets the log level. In Javascript, the number relates to the following log levels:
-
-| Value | Log Level |
-| ----- | --------- |
-| 1 | Trace |
-| 2 | Debug |
-| 3 | Info |
-| 4 | Warning |
-| 5 | Error |
-
-Go: `LogSetLogLevel(ctx context.Context, level logger.LogLevel)` JS: `LogSetLogLevel(level: number)`
-
-## Using a Custom Logger
-
-A custom logger may be used by providing it using the [Logger](../options.mdx#logger) application option. The only requirement is that the logger implements the `logger.Logger` interface defined in `github.com/wailsapp/wails/v2/pkg/logger`:
-
-```go title="logger.go"
-type Logger interface {
- Print(message string)
- Trace(message string)
- Debug(message string)
- Info(message string)
- Warning(message string)
- Error(message string)
- Fatal(message string)
-}
-```
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/menu.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/menu.mdx
deleted file mode 100644
index 6a7e06cf9..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/menu.mdx
+++ /dev/null
@@ -1,23 +0,0 @@
----
-sidebar_position: 6
----
-
-# Menu
-
-These methods are related to the application menu.
-
-:::info Javascript
-Menu is currently unsupported in the JS runtime.
-:::
-
-### MenuSetApplicationMenu
-
-Sets the application menu to the given [menu](../menus.mdx).
-
-Go: `MenuSetApplicationMenu(ctx context.Context, menu *menu.Menu)`
-
-### MenuUpdateApplicationMenu
-
-Updates the application menu, picking up any changes to the menu passed to `MenuSetApplicationMenu`.
-
-Go: `MenuUpdateApplicationMenu(ctx context.Context)`
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/window.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/window.mdx
deleted file mode 100644
index d03143161..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/window.mdx
+++ /dev/null
@@ -1,211 +0,0 @@
----
-sidebar_position: 4
----
-
-# Window
-
-These methods give control of the application window.
-
-### WindowSetTitle
-
-Sets the text in the window title bar.
-
-Go: `WindowSetTitle(ctx context.Context, title string)` JS: `WindowSetTitle(title: string)`
-
-### WindowFullscreen
-
-Makes the window full screen.
-
-Go: `WindowFullscreen(ctx context.Context)` JS: `WindowFullscreen()`
-
-### WindowUnfullscreen
-
-Restores the previous window dimensions and position prior to full screen.
-
-Go: `WindowUnfullscreen(ctx context.Context)` JS: `WindowUnfullscreen()`
-
-### WindowIsFullscreen
-
-Returns true if the window is full screen.
-
-Go: `WindowCenter(ctx context.Context)` JS: `WindowCenter()`
-
-### WindowCenter
-
-Centers the window on the monitor the window is currently on.
-
-Go: `WindowReload(ctx context.Context)` JS: `WindowReload()`
-
-### WindowReload
-
-Performs a "reload" (Reloads current page).
-
-Go: `WindowReloadApp(ctx context.Context)` JS: `WindowReloadApp()`
-
-### WindowReloadApp
-
-Reloads the application frontend.
-
-Go: `WindowSetSystemDefaultTheme(ctx context.Context)` JS: `WindowSetSystemDefaultTheme()`
-
-### WindowSetSystemDefaultTheme
-
-Windows only.
-
-Go: `WindowSetDarkTheme(ctx context.Context)` JS: `WindowSetDarkTheme()`
-
-Sets window theme to system default (dark/light).
-
-### WindowSetLightTheme
-
-Windows only.
-
-Go: `WindowSetLightTheme(ctx context.Context)` JS: `WindowSetLightTheme()`
-
-Sets window theme to light.
-
-### WindowSetDarkTheme
-
-Windows only.
-
-Go: `WindowShow(ctx context.Context)` JS: `WindowShow()`
-
-Sets window theme to dark.
-
-### WindowShow
-
-Shows the window, if it is currently hidden.
-
-Go: `WindowHide(ctx context.Context)` JS: `WindowHide()`
-
-### WindowHide
-
-Hides the window, if it is currently visible.
-
-Go: `WindowSetSize(ctx context.Context, width int, height int)` JS: `WindowSetSize(size: Size)`
-
-### WindowIsNormal
-
-Returns true if the window not minimised, maximised or fullscreen.
-
-Go: `WindowGetSize(ctx context.Context) (width int, height int)` JS: `WindowGetSize() : Size`
-
-### WindowSetSize
-
-Sets the width and height of the window.
-
-Go: `WindowSetMaxSize(ctx context.Context, width int, height int)` JS: `WindowSetMaxSize(size: Size)`
-
-### WindowGetSize
-
-Gets the width and height of the window.
-
-Go: `WindowSetMinSize(ctx context.Context, width int, height int)` JS: `WindowSetMinSize(size: Size)`
-
-### WindowSetMinSize
-
-Sets the minimum window size. Will resize the window if the window is currently smaller than the given dimensions.
-
-Setting a size of `0,0` will disable this constraint.
-
-Go: `WindowSetAlwaysOnTop(ctx context.Context, b bool)` JS: `WindowSetAlwaysOnTop(b: Boolen)`
-
-### WindowSetMaxSize
-
-Sets the maximum window size. Will resize the window if the window is currently larger than the given dimensions.
-
-Setting a size of `0,0` will disable this constraint.
-
-Go: `WindowSetPosition(ctx context.Context, x int, y int)` JS: `WindowSetPosition(position: Position)`
-
-### WindowSetAlwaysOnTop
-
-Sets the window AlwaysOnTop or not on top.
-
-Go: `WindowGetPosition(ctx context.Context) (x int, y int)` JS: `WindowGetPosition() : Position`
-
-### WindowSetPosition
-
-Sets the window position relative to the monitor the window is currently on.
-
-Go: `WindowMaximise(ctx context.Context)` JS: `WindowMaximise()`
-
-### WindowGetPosition
-
-Gets the window position relative to the monitor the window is currently on.
-
-Go: `WindowUnmaximise(ctx context.Context)` JS: `WindowUnmaximise()`
-
-### WindowMaximise
-
-Maximises the window to fill the screen.
-
-Go: `WindowToggleMaximise(ctx context.Context)` JS: `WindowToggleMaximise()`
-
-### WindowUnmaximise
-
-Restores the window to the dimensions and position prior to maximising.
-
-Go: `WindowMinimise(ctx context.Context)` JS: `WindowMinimise()`
-
-### WindowIsMaximised
-
-Returns true if the window is maximised.
-
-Go: `WindowUnminimise(ctx context.Context)` JS: `WindowUnminimise()`
-
-### WindowToggleMaximise
-
-Toggles between Maximised and UnMaximised.
-
-Go: `WindowToggleMaximise(ctx context.Context)` JS: `WindowToggleMaximise()`
-
-### WindowMinimise
-
-Minimises the window.
-
-Go: `WindowSetBackgroundColour(ctx context.Context, R, G, B, A uint8)` JS: `WindowSetBackgroundColour(R, G, B, A)`
-
-### WindowUnminimise
-
-Restores the window to the dimensions and position prior to minimising.
-
-Go: `WindowUnminimise(ctx context.Context)` JS: `WindowUnminimise()`
-
-### WindowIsMinimised
-
-Returns true if the window is minimised.
-
-Go: `WindowIsMinimised(ctx context.Context) bool` JS: `WindowIsMinimised() bool`
-
-### WindowSetBackgroundColour
-
-Sets the background colour of the window to the given RGBA colour definition. This colour will show through for all transparent pixels.
-
-Valid values for R, G, B and A are 0-255.
-
-Any value that is not 0 will be considered 255. :::info Windows
-On Windows, only alpha values of 0 or 255 are supported.
-:::
-
-Go: `WindowSetBackgroundColour(ctx context.Context, R, G, B, A uint8)` JS: `WindowSetBackgroundColour(R, G, B, A)`
-
-## Typescript Object Definitions
-
-### Position
-
-```ts
-interface Position {
- x: number;
- y: number;
-}
-```
-
-### Size
-
-```ts
-interface Size {
- w: number;
- h: number;
-}
-```
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/tutorials/_category_.json b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/tutorials/_category_.json
deleted file mode 100644
index dfac1d175..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/tutorials/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Tutorials",
- "position": 70
-}
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/tutorials/dogsapi.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/tutorials/dogsapi.mdx
deleted file mode 100644
index f4845fdbe..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/tutorials/dogsapi.mdx
+++ /dev/null
@@ -1,243 +0,0 @@
----
-sidebar_position: 20
----
-
-# Dogs API
-
-
-
-
-
-
-
-:::note This tutorial has been kindly provided by [@tatadan](https://twitter.com/tatadan) and forms part of their [Wails Examples Repository](https://github.com/tataDan/wails-v2-examples). :::
-
-In this tutorial we are going to develop an application that retrieves photos of dogs from the web and then displays them.
-
-### Create the project
-
-Let's create the application. From a terminal enter: `wails init -n dogs-api -t svelte`
-
-Note: We could optionally add `-ide vscode` or `-ide goland` to the end of this command if you wanted to add IDE support.
-
-Now let's `cd dogs-api` and start editing the project files.
-
-### Remove unused code
-
-We will start by removing some elements that we know we will not use:
-
-- Open `app.go` and remove the following lines:
-
-```go
-// Greet returns a greeting for the given name
-func (a *App) Greet(name string) string {
- return fmt.Sprintf("Hello %s, It's show time!", name)
-}
-```
-
-- Open `frontend/src/App.svelte` and delete all lines.
-- Delete the `frontend/src/assets/images/logo-universal.png` file
-
-### Creating our application
-
-Now let's add our new Go code.
-
-Add the following struct declarations to `app.go` before the function definitions:
-
-```go
-type RandomImage struct {
- Message string
- Status string
-}
-
-type AllBreeds struct {
- Message map[string]map[string][]string
- Status string
-}
-
-type ImagesByBreed struct {
- Message []string
- Status string
-}
-```
-
-Add the following functions to `app.go` (perhaps after the existing function definitions):
-
-```go
-func (a *App) GetRandomImageUrl() string {
- response, err := http.Get("https://dog.ceo/api/breeds/image/random")
- if err != nil {
- log.Fatal(err)
- }
-
- responseData, err := ioutil.ReadAll(response.Body)
- if err != nil {
- log.Fatal(err)
- }
-
- var data RandomImage
- json.Unmarshal(responseData, &data)
-
- return data.Message
-}
-
-func (a *App) GetBreedList() []string {
- var breeds []string
-
- response, err := http.Get("https://dog.ceo/api/breeds/list/all")
- if err != nil {
- log.Fatal(err)
- }
-
- responseData, err := ioutil.ReadAll(response.Body)
- if err != nil {
- log.Fatal(err)
- }
-
- var data AllBreeds
- json.Unmarshal(responseData, &data)
-
- for k := range data.Message {
- breeds = append(breeds, k)
- }
-
- sort.Strings(breeds)
-
- return breeds
-}
-
-func (a *App) GetImageUrlsByBreed(breed string) []string {
-
- url := fmt.Sprintf("%s%s%s%s", "https://dog.ceo/api/", "breed/", breed, "/images")
- response, err := http.Get(url)
- if err != nil {
- log.Fatal(err)
- }
-
- responseData, err := ioutil.ReadAll(response.Body)
- if err != nil {
- log.Fatal(err)
- }
-
- var data ImagesByBreed
- json.Unmarshal(responseData, &data)
-
- return data.Message
-}
-```
-
-Modify the `import` section of `app.go` to look like this:
-
-```go
-import (
- "context"
- "fmt"
- "encoding/json"
- "io/ioutil"
- "log"
- "net/http"
- "sort"
-)
-```
-
-Add the following lines to `frontend/src/App.svelte`:
-
-```html
-
-
-
Dogs API
-
-
- Click on down arrow to select a breed
-
-
-
-
-{#if showRandomPhoto}
-
-{/if}
-{#if showBreedPhotos}
- {#each photos as photo}
-
- {/each}
-{/if}
-
-
-```
-
-### Testing the application
-
-To generate the bindings and test the application, run `wails dev`.
-
-### Compiling the application
-
-To compile the application to a single, production grade binary, run `wails build`.
-
-
-
-
-
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/tutorials/helloworld.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/tutorials/helloworld.mdx
deleted file mode 100644
index d1b8e9f98..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/tutorials/helloworld.mdx
+++ /dev/null
@@ -1,118 +0,0 @@
----
-sidebar_position: 10
----
-
-# Hello World
-
-The aim of this tutorial is to get you up and running with the most basic application using Wails. You will be able to:
-
-- Create a new Wails application
-- Build the application
-- Run the application
-
-:::note
-This tutorial uses Windows as the target platform. Output will vary slightly
-depending on your operating system.
-:::
-
-## Create a new Wails application
-
-To create a new Wails application using the default vanilla JS template, you need to run the following command:
-
-```bash
-wails init -n helloworld
-```
-
-You should see something similar to the following:
-
-```
-Wails CLI v2.0.0
-
-Initialising Project 'helloworld'
----------------------------------
-
-Project Name: helloworld
-Project Directory: C:\Users\leaan\tutorial\helloworld
-Project Template: vanilla
-Template Support: https://wails.io
-
-Initialised project 'helloworld' in 232ms.
-```
-
-This will create a new directory called `helloworld` in the current directory. In this directory, you will find a number of files:
-
-```
-build/ - Contains the build files + compiled application
-frontend/ - Contains the frontend files
-app.go - Contains the application code
-main.go - The main program with the application configuration
-wails.json - The project configuration file
-go.mod - The go module file
-go.sum - The go module checksum file
-```
-
-## Build the application
-
-To build the application, change to the new `helloworld` project directory and run the following command:
-
-```bash
-wails build
-```
-
-You should see something like the following:
-
-```
-Wails CLI v2.0.0
-
-App Type: desktop
-Platforms: windows/amd64
-Compiler: C:\Users\leaan\go\go1.18.3\bin\go.exe
-Build Mode: Production
-Skip Frontend: false
-Compress: false
-Package: true
-Clean Build Dir: false
-LDFlags: ""
-Tags: []
-Race Detector: false
-
-Building target: windows/amd64
-------------------------------
- - Installing frontend dependencies: Done.
- - Compiling frontend: Done.
- - Generating bundle assets: Done.
- - Compiling application: Done.
-Built 'C:\Users\leaan\tutorial\helloworld\build\bin\helloworld.exe' in 10.616s.
-```
-
-This has compiled the application and saved it in the `build/bin` directory.
-
-## Run the application
-
-If we view the `build/bin` directory in Windows Explorer, we should see our project binary:
-
-
-
-
-
-
-
-We can run it by simply double-clicking the `helloworld.exe` file.
-
-On Mac, Wails generates a `helloworld.app` file which can be run by double-clicking it.
-
-On Linux, you can run the application using `./helloworld` from the `build/bin` directory.
-
-You should see the application working as expected:
-
-
-
-
-
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/links.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/links.mdx
deleted file mode 100644
index 3f9ebf2fc..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/links.mdx
+++ /dev/null
@@ -1,26 +0,0 @@
----
-sidebar_position: 2
----
-
-# Links
-
-This page serves as a list for community related links. Please submit a PR (click `Edit this page` at the bottom) to submit links.
-
-## Awesome Wails
-
-The [definitive list](https://github.com/wailsapp/awesome-wails) of links related to Wails.
-
-## Support Channels
-
-- [Gophers Slack Channel](https://gophers.slack.com/messages/CJ4P9F7MZ/)
-- [Gophers Slack Channel Invite](https://invite.slack.golangbridge.org/)
-- [Github Issues](https://github.com/wailsapp/wails/issues)
-- [v2 Beta Discussion Board](https://github.com/wailsapp/wails/discussions/828)
-
-## Social Media
-
-- [Twitter](https://twitter.com/wailsapp)
-- [Wails Chinese Community QQ Group](https://qm.qq.com/cgi-bin/qm/qr?k=PmIURne5hFGNd7QWzW5qd6FV-INEjNJv&jump_from=webapi) - Group number: 1067173054
-
-## Other Tutorials and Articles
-- [Building of Bulletin Board](https://blog.customct.com/building-bulletin-board)
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/modalfilemanager.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/modalfilemanager.mdx
deleted file mode 100644
index f8e2bcd66..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/modalfilemanager.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
-# Modal File Manager
-
-```mdx-code-block
-
-
-
-
-```
-
-[Modal File Manager](https://github.com/raguay/ModalFileManager) is a dual pane file manager using web technologies. My original design was based on NW.js and can be found [here](https://github.com/raguay/ModalFileManager-NWjs). This version uses the same Svelte based frontend code (but it has be greatly modified since the departure from NW.js), but the backend is a [Wails 2](https://wails.io/) implementation. By using this implementation, I no longer use command line `rm`, `cp`, etc. commands. It is fully coded using Go and runs much faster than the previous versions.
-
-This file manager is designed around the same principle as Vim: a state controlled keyboard actions. The number of states isn't fixed, but very programmable. Therefore, an infinite number of keyboard configurations can be created and used. This is the main difference from other file managers.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/mollywallet.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/mollywallet.mdx
deleted file mode 100644
index 5d846d06d..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/mollywallet.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Molley Wallet
-
-```mdx-code-block
-
-
-
-
-```
-
-[Molly Wallet](https://github.com/grvlle/constellation_wallet/) the official $DAG wallet of the Constellation Network. It'll let users interact with the Hypergraph Network in various ways, not limited to producing $DAG transactions.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/october.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/october.mdx
deleted file mode 100644
index 66d634dc5..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/october.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
-# October
-
-```mdx-code-block
-
-
-
-
-```
-
-[October](https://october.utf9k.net) is a small Wails application that makes it really easy to extract highlights from [Kobo eReaders](https://en.wikipedia.org/wiki/Kobo_eReader) and then forward them to [Readwise](https://readwise.io).
-
-It has a relatively small scope with all platform versions weighing in under 10MB, and that's without enabling [UPX compression](https://upx.github.io/)!
-
-In contrast, the author's previous attempts with Electron quickly bloated to several hundred megabytes.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/restic-browser.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/restic-browser.mdx
deleted file mode 100644
index 3646384ec..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/restic-browser.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
-# Restic Browser
-
-```mdx-code-block
-
-
-
-
-```
-
-[Restic-Browser](https://github.com/emuell/restic-browser) - A simple, cross-platform [restic](https://github.com/restic/restic) backup GUI for browsing and restoring restic repositories.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/riftshare.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/riftshare.mdx
deleted file mode 100644
index 9928b4785..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/riftshare.mdx
+++ /dev/null
@@ -1,21 +0,0 @@
-# RiftShare
-
-```mdx-code-block
-
-
-
-
-```
-
-Easy, Secure, and Free file sharing for everyone. Learn more at [Riftshare.app](https://riftshare.app)
-
-## Features
-
-- Easy secure file sharing between computers both in the local network and through the internet
-- Supports sending files or directories securely through the [magic wormhole protocol](https://magic-wormhole.readthedocs.io/en/latest/)
-- Compatible with all other apps using magic wormhole (magic-wormhole or wormhole-william CLI, wormhole-gui, etc.)
-- Automatic zipping of multiple selected files to send at once
-- Full animations, progress bar, and cancellation support for sending and receiving
-- Native OS File Selection
-- Open files in one click once received
-- Auto Update - don't worry about having the latest release!
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/scriptbar.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/scriptbar.mdx
deleted file mode 100644
index 2ccb2acb4..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/scriptbar.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# ScriptBar
-
-```mdx-code-block
-
-
-
-
-```
-
-[ScriptBar](https://GitHub.com/raguay/ScriptBarApp) is a program to show the output of the embedded [Node-Red](https://nodered.org) server in the [EmailIt](https://GitHub.com/raguay/EmailIt) application. It also displays the output of scripts on your system. ScriptBar doesn't put them in the menubar, but has them all in a convient window for easy viewing. You can have multiple tabs to have many different things show. You can also keep the links to your most visited web sites.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/surge.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/surge.mdx
deleted file mode 100644
index c3b3fb4c0..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/surge.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Surge
-
-```mdx-code-block
-
-
-
-
-```
-
-[Surge](https://getsurge.io/) is a p2p filesharing app designed to utilize blockchain technologies to enable 100% anonymous file transfers. Surge is end-to-end encrypted, decentralized and open source.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/wally.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/wally.mdx
deleted file mode 100644
index 7408aa585..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/wally.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Wally
-
-```mdx-code-block
-
-
-
-
-```
-
-[Wally](https://ergodox-ez.com/pages/wally) is the official firmware flasher for [Ergodox](https://ergodox-ez.com/) keyboards. It looks great and is a fantastic example of what you can achieve with Wails: the ability to combine the power of Go and the rich graphical tools of the web development world.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/ytd.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/ytd.mdx
deleted file mode 100644
index 5db428f72..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/ytd.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Ytd
-
-```mdx-code-block
-
-
-
-
-```
-
-[Ytd](https://github.com/marcio199226/ytd/tree/v2-wails) is an app for downloading tracks from youtube, creating offline playlists and share them with your friends, your friends will be able to playback your playlists or download them for offline listening, has an built-in player.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/ides.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/ides.mdx
deleted file mode 100644
index f74282283..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/ides.mdx
+++ /dev/null
@@ -1,127 +0,0 @@
-# IDEs
-
-Wails aims to provide a great development experience. To that aim, we now support generating IDE specific configuration to provide smoother project setup.
-
-Currently, we support [Visual Studio Code](https://code.visualstudio.com/) but aim to support other IDEs such as Goland.
-
-## Visual Studio Code
-
-```mdx-code-block
-
-
-
-```
-
-When generating a project using the `-ide vscode` flags, IDE files will be created alongside the other project files. These files are placed into the `.vscode` directory and provide the correct configuration for debugging your application.
-
-The 2 files generated are `tasks.json` and `launch.json`. Below are the files generated for the default vanilla project:
-
-```json title="tasks.json"
-{
- "version": "2.0.0",
- "tasks": [
- {
- "label": "build",
- "type": "shell",
- "options": {
- "cwd": "${workspaceFolder}"
- },
- "command": "go",
- "args": [
- "build",
- "-tags",
- "dev",
- "-gcflags",
- "all=-N -l",
- "-o",
- "build/bin/myproject.exe"
- ]
- }
- ]
-}
-```
-
-```json title="launch.json"
-{
- "version": "0.2.0",
- "configurations": [
- {
- "name": "Wails: Debug myproject",
- "type": "go",
- "request": "launch",
- "mode": "exec",
- "program": "${workspaceFolder}/build/bin/myproject.exe",
- "preLaunchTask": "build",
- "cwd": "${workspaceFolder}",
- "env": {}
- }
- ]
-}
-```
-
-### Configuring the install and build steps
-
-The `tasks.json` file is simple for the default project as there is no `npm install` or `npm run build` step needed. For projects that have a frontend build step, such as the svelte template, we would need to edit `tasks.json` to add the install and build steps:
-
-```json title="tasks.json"
-{
- "version": "2.0.0",
- "tasks": [
- {
- "label": "npm install",
- "type": "npm",
- "script": "install",
- "options": {
- "cwd": "${workspaceFolder}/frontend"
- },
- "presentation": {
- "clear": true,
- "panel": "shared",
- "showReuseMessage": false
- },
- "problemMatcher": []
- },
- {
- "label": "npm run build",
- "type": "npm",
- "script": "build",
- "options": {
- "cwd": "${workspaceFolder}/frontend"
- },
- "presentation": {
- "clear": true,
- "panel": "shared",
- "showReuseMessage": false
- },
- "problemMatcher": []
- },
- {
- "label": "build",
- "type": "shell",
- "options": {
- "cwd": "${workspaceFolder}"
- },
- "command": "go",
- "args": [
- "build",
- "-tags",
- "dev",
- "-gcflags",
- "all=-N -l",
- "-o",
- "build/bin/vscode.exe"
- ],
- "dependsOn": ["npm install", "npm run build"]
- }
- ]
-}
-```
-
-:::info Future Enhancement
-
-In the future, we hope to generate a `tasks.json` that includes the install and build steps automatically.
-
-:::
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/linux-distro-support.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/linux-distro-support.mdx
deleted file mode 100644
index 8b25c1575..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/linux-distro-support.mdx
+++ /dev/null
@@ -1,103 +0,0 @@
-# Linux Distro Support
-
-## Overview
-
-Wails offers Linux support but providing installation instructions for all available distributions is an impossible task. Instead, Wails tries to determine if the packages you need to develop applications are available via your system's package manager. Currently, we support the following package managers:
-
-- apt
-- dnf
-- emerge
-- eopkg
-- nixpkgs
-- pacman
-- zypper
-
-## Adding package names
-
-There may be circumstances where your distro uses one of the supported package managers but the package name is different. For example, you may use an Ubuntu derivative, but the package name for gtk may be different. Wails attempts to find the correct package by iterating through a list of package names. The list of packages are stored in the packagemanager specific file in the `v2/internal/system/packagemanager` directory. In our example, this would be `v2/internal/system/packagemanager/apt.go`.
-
-In this file, the list of packages are defined by the `Packages()` method:
-
-```go
-func (a *Apt) Packages() packagemap {
- return packagemap{
- "libgtk-3": []*Package{
- {Name: "libgtk-3-dev", SystemPackage: true, Library: true},
- },
- "libwebkit": []*Package{
- {Name: "libwebkit2gtk-4.0-dev", SystemPackage: true, Library: true},
- },
- "gcc": []*Package{
- {Name: "build-essential", SystemPackage: true},
- },
- "pkg-config": []*Package{
- {Name: "pkg-config", SystemPackage: true},
- },
- "npm": []*Package{
- {Name: "npm", SystemPackage: true},
- },
- "docker": []*Package{
- {Name: "docker.io", SystemPackage: true, Optional: true},
- },
- }
-}
-```
-
-Let's assume that in our linux distro, `libgtk-3` is packaged under the name `lib-gtk3-dev`. We could add support for this by adding the following line:
-
-```go {5}
-func (a *Apt) Packages() packagemap {
- return packagemap{
- "libgtk-3": []*Package{
- {Name: "libgtk-3-dev", SystemPackage: true, Library: true},
- {Name: "lib-gtk3-dev", SystemPackage: true, Library: true},
- },
- "libwebkit": []*Package{
- {Name: "libwebkit2gtk-4.0-dev", SystemPackage: true, Library: true},
- },
- "gcc": []*Package{
- {Name: "build-essential", SystemPackage: true},
- },
- "pkg-config": []*Package{
- {Name: "pkg-config", SystemPackage: true},
- },
- "npm": []*Package{
- {Name: "npm", SystemPackage: true},
- },
- "docker": []*Package{
- {Name: "docker.io", SystemPackage: true, Optional: true},
- },
- }
-}
-```
-
-## Adding new package managers
-
-To add a new package manager, perform the following steps:
-
-- Create a new file in `v2/internal/system/packagemanager` called `.go`, where `` is the name of the package manager.
-- Define a struct that conforms to the package manager interface defined in `pm.go`:
-
-```go
-type PackageManager interface {
- Name() string
- Packages() packagemap
- PackageInstalled(*Package) (bool, error)
- PackageAvailable(*Package) (bool, error)
- InstallCommand(*Package) string
-}
-```
-
-- `Name()` should return the name of the package manager
-- `Packages()` should return a `packagemap`, that provides candidate filenames for dependencies
-- `PackageInstalled()` should return `true` if the given package is installed
-- `PackageAvailable()` should return `true` if the given package is not installed but available for installation
-- `InstallCommand()` should return the exact command to install the given package name
-
-Take a look at the other package managers code to get an idea how this works.
-
-:::info Remember
-
-If you add support for a new package manager, don't forget to also update this page!
-
-:::
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/linux.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/linux.mdx
deleted file mode 100644
index 229c282bf..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/linux.mdx
+++ /dev/null
@@ -1,18 +0,0 @@
-# Linux
-
-This page has miscellaneous guides related to developing Wails applications for Linux.
-
-## Video tag doesn't fire "ended" event
-
-When using a video tag, the "ended" event is not fired when the video is finished playing. This is a bug in WebkitGTK, however you can use the following workaround to fix it:
-
-```js
-videoTag.addEventListener("timeupdate", (event) => {
- if (event.target.duration - event.target.currentTime < 0.2) {
- let ended = new Event("ended");
- event.target.dispatchEvent(ended);
- }
-});
-```
-
-Source: [Lyimmi](https://github.com/Lyimmi) on the [discussions board](https://github.com/wailsapp/wails/issues/1729#issuecomment-1212291275)
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/manual-builds.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/manual-builds.mdx
deleted file mode 100644
index dcf192d33..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/manual-builds.mdx
+++ /dev/null
@@ -1,95 +0,0 @@
-# Manual Builds
-
-The Wails CLI does a lot of heavy lifting for the project, but sometimes it's desirable to manually build your project. This document will discuss the different operations the CLI does and how this may be achieved in different ways.
-
-## Build Process
-
-When either `wails build` or `wails dev` are used, the Wails CLI performs a common build process:
-
- - Install frontend dependencies
- - Build frontend project
- - Generate build assets
- - Compile application
- - [optional] Compress application
-
-### Install frontend dependencies
-
-#### CLI Steps
-
-- If the `-s` flag is given, this step is skipped
-- Checks `wails.json` to see if there is an install command in the key `frontend:install`
-- If there isn't, it skips this step
-- If there is, it checks if `package.json` exists in the frontend directory. If it doesn't exist, it skips this step
-- An MD5 sum is generated from the `package.json` file contents
-- It checks for the existence of `package.json.md5` and if it exists, will compare the contents of it (an MD5 sum) with the one generated to see if the contents have changed. If they are the same, this step is skipped
-- If `package.json.md5` does not exist, it creates it using the generated MD5 sum
-- If a build is now required, or `node_modules` does not exist, or the `-f` flag is given, the install command is executed in the frontend directory
-
-#### Manual Steps
-
-This step could be done from the command line or a script with `npm install`.
-
-### Build frontend project
-
-#### Wails CLI
-
-- If the `-s` flag is given, this step is skipped
-- Checks `wails.json` to see if there is a build command in the key `frontend:build`
-- If there isn't, it skips this step
-- If there is, it is executed in the frontend directory
-
-#### Manual Steps
-
-This step could be done from the command line or a script with `npm run build` or whatever the frontend build script is.
-
-### Generate assets
-
-#### Wails CLI
-
-- If `-nopackage` flag is set, this stage is skipped
-- If the `build/appicon.png` file does not exist, a default one is created
-- For Windows, see [Bundling for Windows](#windows)
-- If `build/windows/icon.ico` does not exist, it will create it from the `build/appicon.png` image.
-
-##### Windows
-
-- If `build/windows/icon.ico` does not exist, it will create it from `build/appicon.png` using icon sizes of 256, 128, 64, 48, 32 and 16. This is done using [winicon](https://github.com/leaanthony/winicon).
-- If the `build/windows/.manifest` file does not exist, it creates it from a default version.
-- Compiles the application as a production build (above)
-- Uses [winres](https://github.com/tc-hib/winres) to bundle the icon and manifest into a `.syso` file ready for linking.
-
-#### Manual Steps
-
-- Create `icon.ico` using the [winicon](https://github.com/leaanthony/winicon) CLI tool (or any other tool).
-- Create / Update a `.manifest` file for your application
-- Use the [winres CLI](https://github.com/tc-hib/go-winres) to generate a `.syso` file.
-
-### Compile application
-
-#### Wails CLI
-
-- If the `-clean` flag is provided, the `build` directory is deleted and recreated
-- For `wails dev`, the following default Go flags are used: `-tags dev -gcflags "all=-N -l"`
-- For `wails build`, the following default Go flags are used: `-tags desktop,production -ldflags "-w -s"`
- - On Windows, `-ldflags "-w -h -H windowsgui"`
-- Additional tags passed to the CLI using `-tags` are added to the defaults
-- Additional ldflags passed to the CLI using `-ldflags` are added to the defaults
-- The `-o` flag is passed through
-- The Go compiler specified by `-compiler` will be used for compilation
-
-#### Manual steps
-
-- For dev build, the minimum command would be: `go build -tags dev -gcflags "all=-N -l"`
-- For production build, the minimum command would be: `go build -tags desktop,production -ldflags "-w -s -H windowsgui"`
-- Ensure that you compile in the same directory as the `.syso` file
-
-### Compress application
-
-#### Wails CLI
-
-- If the `-upx` flag has been given, the `upx` program will be run to compress the application with the default settings
-- If `-upxflags` is also passed, these flags are used instead of the default ones
-
-#### Manual steps
-
-- Run `upx [flags]` manually to compress the application.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/vscode.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/vscode.mdx
deleted file mode 100644
index ed258656d..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/vscode.mdx
+++ /dev/null
@@ -1,82 +0,0 @@
-
-# Visual Studio Code
-
-This page is for miscellaneous tips and tricks when using Visual Studio Code with Wails.
-
-## Vetur Configuration
-
-Many thanks to [@Lyimmi](https://github.com/Lyimmi) for this tip. Originally posted [here](https://github.com/wailsapp/wails/issues/1791#issuecomment-1228158349).
-
-Vetur is a popular plugin for Visual Studio Code that provides syntax highlighting and code completion for Vue projects. When loading a Wails project in VSCode, Vetur will throw an error as it is expecting to find the frontend project in the root directory. To fix this, you can do the following:
-
-Create a file named `vetur.config.js` in the project's root.
-
-```javascript
-// vetur.config.js
-/** @type {import('vls').VeturConfig} */
-module.exports = {
- // **optional** default: `{}`
- // override vscode settings
- // Notice: It only affects the settings used by Vetur.
- settings: {
- "vetur.useWorkspaceDependencies": true,
- "vetur.experimental.templateInterpolationService": true
- },
- // **optional** default: `[{ root: './' }]`
- // support monorepos
- projects: [
- {
- // **required**
- // Where is your project?
- // It is relative to `vetur.config.js`.
- // root: './packages/repo1',
- root: './frontend',
- // **optional** default: `'package.json'`
- // Where is `package.json` in the project?
- // We use it to determine the version of vue.
- // It is relative to root property.
- package: './package.json',
- // **optional**
- // Where is TypeScript config file in the project?
- // It is relative to root property.
- tsconfig: './tsconfig.json',
- // **optional** default: `'./.vscode/vetur/snippets'`
- // Where is vetur custom snippets folders?
- snippetFolder: './.vscode/vetur/snippets',
- // **optional** default: `[]`
- // Register globally Vue component glob.
- // If you set it, you can get completion by that components.
- // It is relative to root property.
- // Notice: It won't actually do it. You need to use `require.context` or `Vue.component`
- globalComponents: [
- './src/components/**/*.vue'
- ]
- }
- ]
-}
-```
-
-Next, configure `frontend/tsconfig.json`:
-
-```javascript
-{
- "compilerOptions": {
- "module": "system",
- "noImplicitAny": true,
- "removeComments": true,
- "preserveConstEnums": true,
- "sourceMap": true,
- "outFile": "../../built/local/tsc.js",
- "allowJs": true
- },
- "exclude": [
- "node_modules",
- "**/*.spec.ts"
- ],
- "include": [
- "src/**/*",
- "wailsjs/**/*.ts"
- ]
-}
-```
-This should enable you to now use Vetur as expected.
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/windows.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/windows.mdx
deleted file mode 100644
index 821808c0b..000000000
--- a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/windows.mdx
+++ /dev/null
@@ -1,61 +0,0 @@
-# Windows
-
-This page has miscellaneous guides related to developing Wails applications for Windows.
-
-## Handling the WebView2 Runtime Dependency
-
-Wails applications built for Windows have a runtime requirement on the Microsoft [WebView2 Runtime](https://developer.microsoft.com/en-us/microsoft-edge/webview2/). Windows 11 will have this installed by default, but some machines won't. Wails offers an easy approach to dealing with this dependency.
-
-By using the `-webview2` flag when building, you can decide what your application will do when a suitable runtime is not detected (including if the installed runtime is too old). The four options are:
-
-1. Download
-2. Embed
-3. Browser
-4. Error
-
-### Download
-
-This option will prompt the user that no suitable runtime has been found and then offer to download and run the official bootstrapper from Microsoft's WebView2 site. If the user proceeds, the official bootstrapper will be downloaded and run.
-
-### Embed
-
-This option embeds the official bootstrapper within the application. If no suitable runtime has been found, the application will offer to run the bootstrapper. This adds ~150k to the binary size.
-
-### Browser
-
-This option will prompt the user that no suitable runtime has been found and then offer to open a browser to the official WebView2 page where the bootstrapper can be downloaded and installed. The application will then exit, leaving the installation up to the user.
-
-### Error
-
-If no suitable runtime is found, an error is given to the user and no further action taken.
-
-## Fixed version runtime
-
-Another way of dealing with webview2 dependency is shipping it yourself. You can download [fixed version runtime](https://developer.microsoft.com/microsoft-edge/webview2/#download-section) and bundle or download it with your application.
-
-Also, you should specify path to fixed version of webview2 runtime in the `windows.Options` structure when launching wails.
-
-```go
- wails.Run(&options.App{
- Windows: &windows.Options{
- WebviewBrowserPath: "",
- },
- })
-```
-
-Note: When `WebviewBrowserPath` is specified, `error` strategy will be forced in case of minimal required version mismatch or invalid path to a runtime.
-
-## Spawning other programs
-
-When spawning other programs, such as scripts, you will see the window appear on the screen. To hide the window, you can use the following code:
-
-```go
-cmd := exec.Command("your_script.exe")
-cmd.SysProcAttr = &syscall.SysProcAttr{
- HideWindow: true,
- CreationFlags: 0x08000000,
-}
-cmd.Start()
-```
-
-Solution provided by [sithembiso](https://github.com/sithembiso) on the [discussions board](https://github.com/wailsapp/wails/discussions/1734#discussioncomment-3386172).
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/community/links.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/community/links.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/community/links.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/community/links.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/emailit.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/emailit.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/emailit.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/emailit.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/encrypteasy.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/encrypteasy.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/encrypteasy.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/encrypteasy.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/filehound.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/filehound.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/filehound.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/filehound.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/minecraftupdater.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/minecraftupdater.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/minecraftupdater.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/minecraftupdater.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/modalfilemanager.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/modalfilemanager.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/modalfilemanager.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/modalfilemanager.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/mollywallet.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/mollywallet.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/mollywallet.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/mollywallet.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/october.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/october.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/october.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/october.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/optimus.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/optimus.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/optimus.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/optimus.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/portfall.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/portfall.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/portfall.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/portfall.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/restic-browser.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/restic-browser.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/restic-browser.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/restic-browser.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/riftshare.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/riftshare.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/riftshare.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/riftshare.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/scriptbar.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/scriptbar.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/scriptbar.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/scriptbar.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/surge.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/surge.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/surge.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/surge.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/wally.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/wally.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/wally.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/wally.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/wombat.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/wombat.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/wombat.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/wombat.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/ytd.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/ytd.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/ytd.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/ytd.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/templates.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/community/templates.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/community/templates.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/community/templates.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/building.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/gettingstarted/building.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/building.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/gettingstarted/building.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/development.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/gettingstarted/development.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/development.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/gettingstarted/development.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/firstproject.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/gettingstarted/firstproject.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/firstproject.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/gettingstarted/firstproject.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/installation.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/gettingstarted/installation.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/installation.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/gettingstarted/installation.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/angular.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/angular.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/angular.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/angular.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/application-development.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/application-development.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/application-development.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/application-development.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/dynamic-assets.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/dynamic-assets.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/dynamic-assets.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/dynamic-assets.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/frameless.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/frameless.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/frameless.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/frameless.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/frontend.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/frontend.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/frontend.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/frontend.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/ides.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/ides.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/ides.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/ides.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/linux-distro-support.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/linux-distro-support.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/guides/linux-distro-support.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/linux-distro-support.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/linux.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/linux.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/linux.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/linux.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/local-development.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/local-development.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/local-development.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/local-development.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/mac-appstore.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/mac-appstore.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/mac-appstore.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/mac-appstore.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/guides/manual-builds.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/manual-builds.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/guides/manual-builds.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/manual-builds.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/migrating.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/migrating.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/migrating.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/migrating.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/mouse-buttons.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/mouse-buttons.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/mouse-buttons.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/mouse-buttons.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/obfuscated.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/obfuscated.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/obfuscated.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/obfuscated.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/overscroll.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/overscroll.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/overscroll.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/overscroll.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/routing.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/routing.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/routing.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/routing.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/signing.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/signing.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/signing.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/signing.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/templates.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/templates.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/guides/templates.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/templates.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/troubleshooting.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/troubleshooting.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/troubleshooting.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/troubleshooting.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/guides/vscode.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/vscode.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/guides/vscode.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/vscode.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/windows-installer.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/windows-installer.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/windows-installer.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/windows-installer.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/guides/windows.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/windows.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/guides/windows.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/guides/windows.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/howdoesitwork.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/howdoesitwork.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/howdoesitwork.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/howdoesitwork.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/introduction.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/introduction.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/introduction.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/introduction.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/reference/cli.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/reference/cli.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/reference/cli.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/reference/cli.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/reference/menus.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/reference/menus.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/reference/menus.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/reference/menus.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/reference/options.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/reference/options.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/reference/options.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/reference/options.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/reference/project-config.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/reference/project-config.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/reference/project-config.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/reference/project-config.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/browser.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/browser.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/browser.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/browser.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/dialog.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/dialog.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/dialog.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/dialog.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/events.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/events.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/events.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/events.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/intro.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/intro.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/intro.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/intro.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/log.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/log.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/log.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/log.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/menu.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/menu.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/menu.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/menu.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/window.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/window.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/window.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/window.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/tutorials/dogsapi.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/tutorials/dogsapi.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/tutorials/dogsapi.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/tutorials/dogsapi.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/tutorials/helloworld.mdx b/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/tutorials/helloworld.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/tutorials/helloworld.mdx
rename to website/i18n/ko/docusaurus-plugin-content-docs/version-v2.4.0/tutorials/helloworld.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/emailit.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/emailit.mdx
deleted file mode 100644
index 04150ba28..000000000
--- a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/emailit.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# EmailIt
-
-```mdx-code-block
-
-
-
-
-```
-
-[EmailIt](https://github.com/raguay/EmailIt/) is a Wails 2 program that is a markdown based email sender only with nine notepads, scripts to manipulate the text, and templates. It also has a builtin [Node-Red](https://nodered.org/) server, scripts terminal, and the [ScriptBar](https://github.com/raguay/ScriptBarApp) program for displaying results from Node-Red or a script on your system. Documentation is very scarce, but the programs works. It’s built using Wails2 and Svelte, and the download is a universal macOS application.
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/dynamic-assets.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/dynamic-assets.mdx
deleted file mode 100644
index 73173e15b..000000000
--- a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/dynamic-assets.mdx
+++ /dev/null
@@ -1,136 +0,0 @@
-# Dynamic Assets
-
-If you want to load or generate assets for your frontend dynamically, you can achieve that using the [AssetsHandler](../reference/options#assetshandler) option. The AssetsHandler is a generic `http.Handler` which will be called for any non GET request on the assets server and for GET requests which can not be served from the bundled assets because the file is not found.
-
-By installing a custom AssetsHandler, you can serve your own assets using a custom asset server.
-
-## Example
-
-In our example project, we will create a simple assets handler which will load files off disk:
-
-```go title=main.go {16-35,49}
-package main
-
-import (
- "embed"
- "fmt"
- "github.com/wailsapp/wails/v2"
- "github.com/wailsapp/wails/v2/pkg/options"
- "github.com/wailsapp/wails/v2/pkg/options/assetserver"
- "net/http"
- "os"
- "strings"
-)
-
-//go:embed all:frontend/dist
-var assets embed.FS
-
-type FileLoader struct {
- http.Handler
-}
-
-func NewFileLoader() *FileLoader {
- return &FileLoader{}
-}
-
-func (h *FileLoader) ServeHTTP(res http.ResponseWriter, req *http.Request) {
- var err error
- requestedFilename := strings.TrimPrefix(req.URL.Path, "/")
- println("Requesting file:", requestedFilename)
- fileData, err := os.ReadFile(requestedFilename)
- if err != nil {
- res.WriteHeader(http.StatusBadRequest)
- res.Write([]byte(fmt.Sprintf("Could not load file %s", requestedFilename)))
- }
-
- res.Write(fileData)
-}
-
-func main() {
- // Create an instance of the app structure
- app := NewApp()
-
- // Create application with options
- err := wails.Run(&options.App{
- Title: "helloworld",
- Width: 1024,
- Height: 768,
- AssetServer: &assetserver.Options{
- Assets: assets,
- Handler: NewFileLoader(),
- },
- BackgroundColour: &options.RGBA{R: 27, G: 38, B: 54, A: 255},
- OnStartup: app.startup,
- Bind: []interface{}{
- app,
- },
- })
-
- if err != nil {
- println("Error:", err)
- }
-}
-```
-
-When we run the application in dev mode using `wails dev`, we will see the following output:
-
-```
-DEB | [ExternalAssetHandler] Loading 'http://localhost:3001/favicon.ico'
-DEB | [ExternalAssetHandler] Loading 'http://localhost:3001/favicon.ico' failed, using AssetHandler
-Requesting file: favicon.ico
-```
-
-As you can see, the assets handler is called when the default assets server is unable to serve the `favicon.ico` file.
-
-If you right click the main application and select "inspect" to bring up the devtools, you can test this feature out by typing the following into the console:
-
-```
-let response = await fetch('does-not-exist.txt');
-```
-
-This will generate an error in the devtools. We can see that the error is what we expect, returned by our custom assets handler:
-
-```mdx-code-block
-
-
-
-```
-
-However, if we request `go.mod`, we will see the following output:
-
-```mdx-code-block
-
-
-
-```
-
-This technique can be used to load images directly into the page. If we updated our default vanilla template and replaced the logo image:
-
-```html
-
-```
-
-with:
-
-```html
-
-```
-
-Then we would see the following:
-
-```mdx-code-block
-
-
-
-```
-
-:::warning
-
-Exposing your filesystem in this way is a security risk. It is recommended that you properly manage access to your filesystem.
-
-:::
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/mouse-buttons.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/mouse-buttons.mdx
deleted file mode 100644
index 4a3de2a61..000000000
--- a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/mouse-buttons.mdx
+++ /dev/null
@@ -1,25 +0,0 @@
-# Mouse Buttons
-
-The Wails runtime intercepts mouse clicks to determine whether a frameless window needs resizing or a window needs to be moved. It has been asked how to detect when a mouse click has occurred, because `window.onclick` doesn't report the mouse buttons correctly. The following code shows how to detect mouse clicks:
-
-```javascript
-window.addEventListener("mousedown", handleMouseButtonDown);
-
-function handleMouseButtonDown(event) {
- if (event.button === 0) {
- // left mouse button
- } else if (event.button === 1) {
- // middle mouse button
- } else if (event.button === 2) {
- // right mouse button
- } else if (event.button === 3) {
- // back mouse button
- } else if (event.button === 4) {
- // forward mouse button
- } else {
- // other mouse button
- }
-}
-```
-
-Reference: https://developer.mozilla.org/en-US/docs/Web/API/MouseEvent/button
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/obfuscated.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/obfuscated.mdx
deleted file mode 100644
index 21f7875e3..000000000
--- a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/obfuscated.mdx
+++ /dev/null
@@ -1,40 +0,0 @@
-# Obfuscated Builds
-
-Wails includes support for obfuscating your application using [garble](https://github.com/burrowers/garble).
-
-To produce an obfuscated build, you can use the `-obfuscate` flag with the `wails build` command:
-
-```bash
-wails build -obfuscated
-```
-
-To customise the obfuscation settings, you can use the `-garbleargs` flag:
-
-```bash
-wails build -obfuscated -garbleargs "-literals -tiny -seed=myrandomseed"
-```
-
-These settings may be persisted in your [project config](../reference/project-config).
-
-## How it works
-
-In a standard build, all bound methods are available in the frontend under the `window.go` variable. When these methods are called, the corresponding backend method is called using the fully qualified function name. When using an obfuscated build, methods are bound using an ID instead of a name. The bindings generated in the `wailsjs` directory use these IDs to call the backend functions.
-
-:::note
-
-To ensure that your application will work in obfuscated mode, you must use the generated bindings under the `wailsjs` directory in your application.
-
-:::
-
-## Example
-
-Importing the "Greet" method from the bindings like this:
-
-```js
-import { Greet } from "../../wailsjs/go/main/App";
-
-// snip
-Greet("World");
-```
-
-will ensure that the method will work correctly in obfuscated mode, as the bindings will be regenerated with IDs and the call mechanism updated.
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/overscroll.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/overscroll.mdx
deleted file mode 100644
index 9d1d772d0..000000000
--- a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/overscroll.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Overscroll
-
-[Overscroll](https://developer.mozilla.org/en-US/docs/Web/CSS/overscroll-behavior) is the "bounce effect" you sometimes get when you scroll beyond a page's content boundaries. This is common in mobile apps. This can be disabled using CSS:
-
-```css
-html {
- height: 100%;
- overflow: hidden;
-}
-```
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/templates.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/templates.mdx
deleted file mode 100644
index 790e3107f..000000000
--- a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/templates.mdx
+++ /dev/null
@@ -1,97 +0,0 @@
-# Templates
-
-Wails generates projects from pre-created templates. In v1, this was a difficult to maintain set of projects that were subject to going out of date. In v2, to empower the community, a couple of new features have been added for templates:
-
-- Ability to generate projects from [Remote Templates](../reference/cli.mdx#remote-templates)
-- Tooling to help create your own templates
-
-## Creating Templates
-
-To create a template, you can use the `wails generate template` command. To generate a default template, run:
-
-`wails generate template -name mytemplate`
-
-This creates the directory "mytemplate" with default files:
-
-```shell title=mytemplate/
-.
-|-- NEXTSTEPS.md
-|-- README.md
-|-- app.tmpl.go
-|-- frontend
-| `-- dist
-| |-- assets
-| | |-- fonts
-| | | |-- OFL.txt
-| | | `-- nunito-v16-latin-regular.woff2
-| | `-- images
-| | `-- logo-dark.svg
-| |-- index.html
-| |-- main.css
-| `-- main.js
-|-- go.mod.tmpl
-|-- main.tmpl.go
-|-- template.json
-`-- wails.tmpl.json
-```
-
-### Template Overview
-
-The default template consists of the following files and directories:
-
-| Filename / Dir | Description |
-| --------------- | -------------------------------------------- |
-| NEXTSTEPS.md | Instructions on how to complete the template |
-| README.md | The README published with the template |
-| app.tmpl.go | `app.go` template file |
-| frontend/ | The directory containing frontend assets |
-| go.mod.tmpl | `go.mod` template file |
-| main.tmpl.go | `main.go` template file |
-| template.json | The template metadata |
-| wails.tmpl.json | `wails.json` template file |
-
-At this point it is advisable to follow the steps in `NEXTSTEPS.md`.
-
-## Creating a Template from an Existing Project
-
-It's possible to create a template from an existing frontend project by passing the path to the project when generating the template. We will now walk through how to create a Vue 3 template:
-
-- Install the vue cli: `npm install -g @vue/cli`
-- Create the default project: `vue create vue3-base`
- - Select `Default (Vue 3) ([Vue 3] babel, eslint)`
-- After the project has been generated, run:
-
-```shell
-> wails generate template -name wails-vue3-template -frontend .\vue3-base\
-Extracting base template files...
-Migrating existing project files to frontend directory...
-Updating package.json data...
-Renaming package.json -> package.tmpl.json...
-Updating package-lock.json data...
-Renaming package-lock.json -> package-lock.tmpl.json...
-```
-
-- The template may now be customised as specified in the `NEXTSTEPS.md` file
-- Once the files are ready, it can be tested by running: `wails init -n my-vue3-project -t .\wails-vue3-template\`
-- To test the new project, run: `cd my-vue3-project` then `wails build`
-- Once the project has compiled, run it: `.\build\bin\my-vue3-project.exe`
-- You should have a fully functioning Vue3 application:
-
-```mdx-code-block
-
-
-
-```
-
-## Publishing Templates
-
-Publishing a template is simply pushing the files to GitHub. The following best practice is encouraged:
-
-- Remove any unwanted files and directories (such as `.git`) from your frontend directory
-- Ensure that `template.json` is complete, especially `helpurl`
-- Push the files to GitHub
-- Create a PR on the [Community Templates](../community/templates.mdx) page
-- Announce the template on the [Template Announcement](https://github.com/wailsapp/wails/discussions/825) discussion board
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/tutorials/dogsapi.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/tutorials/dogsapi.mdx
deleted file mode 100644
index 1af16f774..000000000
--- a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/tutorials/dogsapi.mdx
+++ /dev/null
@@ -1,245 +0,0 @@
----
-sidebar_position: 20
----
-
-# Dogs API
-
-```mdx-code-block
-
-
-
-
-```
-
-:::note
-
-This tutorial has been kindly provided by [@tatadan](https://twitter.com/tatadan) and forms part of their [Wails Examples Repository](https://github.com/tataDan/wails-v2-examples).
-
-:::
-
-In this tutorial we are going to develop an application that retrieves photos of dogs from the web and then displays them.
-
-### Create the project
-
-Let's create the application. From a terminal enter: `wails init -n dogs-api -t svelte`
-
-Note: We could optionally add `-ide vscode` or `-ide goland` to the end of this command if you wanted to add IDE support.
-
-Now let's `cd dogs-api` and start editing the project files.
-
-### Remove unused code
-
-We will start by removing some elements that we know we will not use:
-
-- Open `app.go` and remove the following lines:
-
-```go
-// Greet returns a greeting for the given name
-func (a *App) Greet(name string) string {
- return fmt.Sprintf("Hello %s, It's show time!", name)
-}
-```
-
-- Open `frontend/src/App.svelte` and delete all lines.
-- Delete the `frontend/src/assets/images/logo-universal.png` file
-
-### Creating our application
-
-Now let's add our new Go code.
-
-Add the following struct declarations to `app.go` before the function definitions:
-
-```go
-type RandomImage struct {
- Message string
- Status string
-}
-
-type AllBreeds struct {
- Message map[string]map[string][]string
- Status string
-}
-
-type ImagesByBreed struct {
- Message []string
- Status string
-}
-```
-
-Add the following functions to `app.go` (perhaps after the existing function definitions):
-
-```go
-func (a *App) GetRandomImageUrl() string {
- response, err := http.Get("https://dog.ceo/api/breeds/image/random")
- if err != nil {
- log.Fatal(err)
- }
-
- responseData, err := ioutil.ReadAll(response.Body)
- if err != nil {
- log.Fatal(err)
- }
-
- var data RandomImage
- json.Unmarshal(responseData, &data)
-
- return data.Message
-}
-
-func (a *App) GetBreedList() []string {
- var breeds []string
-
- response, err := http.Get("https://dog.ceo/api/breeds/list/all")
- if err != nil {
- log.Fatal(err)
- }
-
- responseData, err := ioutil.ReadAll(response.Body)
- if err != nil {
- log.Fatal(err)
- }
-
- var data AllBreeds
- json.Unmarshal(responseData, &data)
-
- for k := range data.Message {
- breeds = append(breeds, k)
- }
-
- sort.Strings(breeds)
-
- return breeds
-}
-
-func (a *App) GetImageUrlsByBreed(breed string) []string {
-
- url := fmt.Sprintf("%s%s%s%s", "https://dog.ceo/api/", "breed/", breed, "/images")
- response, err := http.Get(url)
- if err != nil {
- log.Fatal(err)
- }
-
- responseData, err := ioutil.ReadAll(response.Body)
- if err != nil {
- log.Fatal(err)
- }
-
- var data ImagesByBreed
- json.Unmarshal(responseData, &data)
-
- return data.Message
-}
-```
-
-Modify the `import` section of `app.go` to look like this:
-
-```go
-import (
- "context"
- "fmt"
- "encoding/json"
- "io/ioutil"
- "log"
- "net/http"
- "sort"
-)
-```
-
-Add the following lines to `frontend/src/App.svelte`:
-
-
-```html
-
-
-
Dogs API
-
-
- Click on down arrow to select a breed
-
-
-
-
-{#if showRandomPhoto}
-
-{/if}
-{#if showBreedPhotos}
- {#each photos as photo}
-
- {/each}
-{/if}
-
-
-```
-
-
-### Testing the application
-
-To generate the bindings and test the application, run `wails dev`.
-
-### Compiling the application
-
-To compile the application to a single, production grade binary, run `wails build`.
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/community/links.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/community/links.mdx
similarity index 84%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/community/links.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/community/links.mdx
index f3cbf4a91..d061c0ee0 100644
--- a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/community/links.mdx
+++ b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/community/links.mdx
@@ -12,8 +12,7 @@ A [lista definitiva](https://github.com/wailsapp/awesome-wails) dos links relaci
## Canais de Suporte
-- [Gophers Slack Channel](https://gophers.slack.com/messages/CJ4P9F7MZ/)
-- [Gophers Slack Channel Invite](https://invite.slack.golangbridge.org/)
+- [Discord](https://discord.com/invite/JDdSxwjhGf)
- [Github Issues](https://github.com/wailsapp/wails/issues)
- [v2 Beta Discussion Board](https://github.com/wailsapp/wails/discussions/828)
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/emailit.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/emailit.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/emailit.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/emailit.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/encrypteasy.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/encrypteasy.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/encrypteasy.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/encrypteasy.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/filehound.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/filehound.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/filehound.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/filehound.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/minecraftupdater.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/minecraftupdater.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/minecraftupdater.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/minecraftupdater.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/modalfilemanager.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/modalfilemanager.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/modalfilemanager.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/modalfilemanager.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/mollywallet.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/mollywallet.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/mollywallet.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/mollywallet.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/october.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/october.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/october.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/october.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/optimus.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/optimus.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/optimus.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/optimus.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/portfall.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/portfall.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/portfall.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/portfall.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/restic-browser.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/restic-browser.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/restic-browser.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/restic-browser.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/riftshare.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/riftshare.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/riftshare.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/riftshare.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/scriptbar.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/scriptbar.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/scriptbar.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/scriptbar.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/surge.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/surge.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/surge.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/surge.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/wally.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/wally.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/wally.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/wally.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/wombat.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/wombat.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/wombat.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/wombat.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/ytd.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/ytd.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/ytd.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/ytd.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/community/templates.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/community/templates.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/community/templates.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/community/templates.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/building.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/gettingstarted/building.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/building.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/gettingstarted/building.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/development.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/gettingstarted/development.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/development.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/gettingstarted/development.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/firstproject.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/gettingstarted/firstproject.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/firstproject.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/gettingstarted/firstproject.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/installation.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/gettingstarted/installation.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/installation.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/gettingstarted/installation.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/angular.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/angular.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/angular.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/angular.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/application-development.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/application-development.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/application-development.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/application-development.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/dynamic-assets.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/dynamic-assets.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/dynamic-assets.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/dynamic-assets.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/frameless.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/frameless.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/frameless.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/frameless.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/frontend.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/frontend.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/frontend.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/frontend.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/ides.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/ides.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/ides.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/ides.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/linux-distro-support.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/linux-distro-support.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/linux-distro-support.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/linux-distro-support.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/linux.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/linux.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/linux.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/linux.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/local-development.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/local-development.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/local-development.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/local-development.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/mac-appstore.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/mac-appstore.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/mac-appstore.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/mac-appstore.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/manual-builds.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/manual-builds.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/manual-builds.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/manual-builds.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/migrating.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/migrating.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/migrating.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/migrating.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/mouse-buttons.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/mouse-buttons.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/mouse-buttons.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/mouse-buttons.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/obfuscated.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/obfuscated.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/obfuscated.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/obfuscated.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/overscroll.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/overscroll.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/overscroll.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/overscroll.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/routing.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/routing.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/routing.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/routing.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/signing.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/signing.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/signing.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/signing.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/templates.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/templates.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/templates.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/templates.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/troubleshooting.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/troubleshooting.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/troubleshooting.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/troubleshooting.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/vscode.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/vscode.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/vscode.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/vscode.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/windows-installer.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/windows-installer.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/windows-installer.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/windows-installer.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/windows.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/windows.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/windows.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/guides/windows.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/howdoesitwork.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/howdoesitwork.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/howdoesitwork.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/howdoesitwork.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/introduction.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/introduction.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/introduction.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/introduction.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/reference/cli.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/reference/cli.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/reference/cli.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/reference/cli.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/reference/menus.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/reference/menus.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/reference/menus.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/reference/menus.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/reference/options.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/reference/options.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/reference/options.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/reference/options.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/reference/project-config.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/reference/project-config.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/reference/project-config.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/reference/project-config.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/browser.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/browser.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/browser.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/browser.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/dialog.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/dialog.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/dialog.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/dialog.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/events.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/events.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/events.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/events.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/intro.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/intro.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/intro.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/intro.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/log.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/log.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/log.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/log.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/menu.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/menu.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/menu.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/menu.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/window.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/window.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/window.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/window.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/tutorials/dogsapi.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/tutorials/dogsapi.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/tutorials/dogsapi.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/tutorials/dogsapi.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/tutorials/helloworld.mdx b/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/tutorials/helloworld.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/tutorials/helloworld.mdx
rename to website/i18n/pt/docusaurus-plugin-content-docs/version-v2.4.0/tutorials/helloworld.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/appendix/_category_.json b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/appendix/_category_.json
deleted file mode 100644
index 83af4ca28..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/appendix/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Appendix",
- "position": 70
-}
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/_category_.json b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/_category_.json
deleted file mode 100644
index 524986e1e..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Community",
- "position": 50
-}
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/links.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/links.mdx
deleted file mode 100644
index 4a3a89e87..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/links.mdx
+++ /dev/null
@@ -1,23 +0,0 @@
----
-sidebar_position: 2
----
-
-# Links
-
-This page serves as a list for community related links. Please submit a PR (click `Edit this page` at the bottom) to submit links.
-
-## Awesome Wails
-
-The [definitive list](https://github.com/wailsapp/awesome-wails) of links related to Wails.
-
-## Support Channels
-
-- [Gophers Slack Channel](https://gophers.slack.com/messages/CJ4P9F7MZ/)
-- [Gophers Slack Channel Invite](https://invite.slack.golangbridge.org/)
-- [Github Issues](https://github.com/wailsapp/wails/issues)
-- [v2 Beta Discussion Board](https://github.com/wailsapp/wails/discussions/828)
-
-## Social Media
-
-- [Twitter](https://twitter.com/wailsapp)
-- [Wails Chinese Community QQ Group](https://qm.qq.com/cgi-bin/qm/qr?k=PmIURne5hFGNd7QWzW5qd6FV-INEjNJv&jump_from=webapi) - Group number: 1067173054
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/_category_.json b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/_category_.json
deleted file mode 100644
index 276e283b7..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Showcase",
- "position": 1
-}
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/emailit.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/emailit.mdx
deleted file mode 100644
index 4a1ebe835..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/emailit.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
-# EmailIt
-
-
-
-
-
-
-[EmailIt](https://github.com/raguay/EmailIt/) is a Wails 2 program that is a markdown based email sender only with nine notepads, scripts to manipulate the text, and templates. It also has a builtin [Node-Red](https://nodered.org/) server, scripts terminal, and the [ScriptBar](https://github.com/raguay/ScriptBarApp) program for displaying results from Node-Red or a script on your system. Documentation is very scarce, but the programs works. It’s built using Wails2 and Svelte, and the download is a universal macOS application.
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/encrypteasy.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/encrypteasy.mdx
deleted file mode 100644
index 13c2d8345..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/encrypteasy.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# EncryptEasy
-
-
-
-
-
-
-**[EncryptEasy](https://www.encrypteasy.app) is a simple and easy to use PGP encryption tool, managing all your and your contacts keys. Encryption should be simple. Developed with Wails.**
-
-Encrypting messages using PGP is the industry standard. Everyone has a private and a public key. Your private key, well, needs to be kept private so only you can read messages. Your public key is distributed to anyone who wants to send you secret, encrypted messages. Managing keys, encrypting messages and decrypting messages should be a smooth experience. EncryptEasy is all about making it easy.
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/filehound.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/filehound.mdx
deleted file mode 100644
index 78cbfca86..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/filehound.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
-# FileHound Export Utility
-
-
-
-
-
-
-[FileHound Export Utility](https://www.filehound.co.uk/) FileHound is a cloud document management platform made for secure file retention, business process automation and SmartCapture capabilities.
-
-The FileHound Export Utility allows FileHound Administrators the ability to run a secure document and data extraction tasks for alternative back-up and recovery purposes. This application will download all documents and/or meta data saved in FileHound based on the filters you choose. The metadata will be exported in both JSON and XML formats.
-
-Backend built with: Go 1.15 Wails 1.11.0 go-sqlite3 1.14.6 go-linq 3.2
-
-Frontend with: Vue 2.6.11 Vuex 3.4.0 Typescript Tailwind 1.9.6
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/minecraftupdater.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/minecraftupdater.mdx
deleted file mode 100644
index 11247339d..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/minecraftupdater.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Minecraft Updater
-
-
-
-
-
-
-[Minecraft Updater](https://github.com/Gurkengewuerz/MinecraftModUpdater) is a utility tool to update and synchronize Minecraft mods for your userbase. It’s built using Wails2 and React with [antd](https://ant.design/) as frontend framework.
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/modalfilemanager.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/modalfilemanager.mdx
deleted file mode 100644
index a7ae8c492..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/modalfilemanager.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
-# Modal File Manager
-
-
-
-
-
-
-[Modal File Manager](https://github.com/raguay/ModalFileManager) is a dual pane file manager using web technologies. My original design was based on NW.js and can be found [here](https://github.com/raguay/ModalFileManager-NWjs). This version uses the same Svelte based frontend code (but it has be greatly modified since the departure from NW.js), but the backend is a [Wails 2](https://wails.io/) implementation. By using this implementation, I no longer use command line `rm`, `cp`, etc. commands. It is fully coded using Go and runs much faster than the previous versions.
-
-This file manager is designed around the same principle as Vim: a state controlled keyboard actions. The number of states isn't fixed, but very programmable. Therefore, an infinite number of keyboard configurations can be created and used. This is the main difference from other file managers.
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/mollywallet.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/mollywallet.mdx
deleted file mode 100644
index 534b097ca..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/mollywallet.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
-# Molley Wallet
-
-
-
-
-
-
-[Molly Wallet](https://github.com/grvlle/constellation_wallet/) the official $DAG wallet of the Constellation Network. It'll let users interact with the Hypergraph Network in various ways, not limited to producing $DAG transactions.
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/october.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/october.mdx
deleted file mode 100644
index 889d2dd9e..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/october.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
-# October
-
-
-
-
-
-
-[October](https://october.utf9k.net) is a small Wails application that makes it really easy to extract highlights from [Kobo eReaders](https://en.wikipedia.org/wiki/Kobo_eReader) and then forward them to [Readwise](https://readwise.io).
-
-It has a relatively small scope with all platform versions weighing in under 10MB, and that's without enabling [UPX compression](https://upx.github.io/)!
-
-In contrast, the author's previous attempts with Electron quickly bloated to several hundred megabytes.
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/optimus.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/optimus.mdx
deleted file mode 100644
index c3eb79507..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/optimus.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
-# Optimus
-
-
-
-
-
-
-[Optimus](https://github.com/splode/optimus) is a desktop image optimization application. It supports conversion and compression between WebP, JPEG, and PNG image formats.
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/portfall.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/portfall.mdx
deleted file mode 100644
index 4cc2c63c9..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/portfall.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
-# Portfall
-
-
-
-
-
-
-[Portfall](https://github.com/rekon-oss/portfall) - A desktop k8s port-forwarding portal for easy access to all your cluster UIs
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/restic-browser.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/restic-browser.mdx
deleted file mode 100644
index 1505ce07a..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/restic-browser.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Restic Browser
-
-
-
-
-
-
-[Restic-Browser](https://github.com/emuell/restic-browser) - A simple, cross-platform [restic](https://github.com/restic/restic) backup GUI for browsing and restoring restic repositories.
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/riftshare.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/riftshare.mdx
deleted file mode 100644
index 5223e88cf..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/riftshare.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
-# RiftShare
-
-
-
-
-
-
-Easy, Secure, and Free file sharing for everyone. Learn more at [Riftshare.app](https://riftshare.app)
-
-## Features
-
-- Easy secure file sharing between computers both in the local network and through the internet
-- Supports sending files or directories securely through the [magic wormhole protocol](https://magic-wormhole.readthedocs.io/en/latest/)
-- Compatible with all other apps using magic wormhole (magic-wormhole or wormhole-william CLI, wormhole-gui, etc.)
-- Automatic zipping of multiple selected files to send at once
-- Full animations, progress bar, and cancellation support for sending and receiving
-- Native OS File Selection
-- Open files in one click once received
-- Auto Update - don't worry about having the latest release!
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/scriptbar.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/scriptbar.mdx
deleted file mode 100644
index aaa556f92..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/scriptbar.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
-# ScriptBar
-
-
-
-
-
-
-[ScriptBar](https://GitHub.com/raguay/ScriptBarApp) is a program to show the output of the embedded [Node-Red](https://nodered.org) server in the [EmailIt](https://GitHub.com/raguay/EmailIt) application. It also displays the output of scripts on your system. ScriptBar doesn't put them in the menubar, but has them all in a convient window for easy viewing. You can have multiple tabs to have many different things show. You can also keep the links to your most visited web sites.
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/surge.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/surge.mdx
deleted file mode 100644
index 2d895dc29..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/surge.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
-# Surge
-
-
-
-
-
-
-[Surge](https://getsurge.io/) is a p2p filesharing app designed to utilize blockchain technologies to enable 100% anonymous file transfers. Surge is end-to-end encrypted, decentralized and open source.
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/wally.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/wally.mdx
deleted file mode 100644
index 2a2498f40..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/wally.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
-# Wally
-
-
-
-
-
-
-[Wally](https://ergodox-ez.com/pages/wally) is the official firmware flasher for [Ergodox](https://ergodox-ez.com/) keyboards. It looks great and is a fantastic example of what you can achieve with Wails: the ability to combine the power of Go and the rich graphical tools of the web development world.
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/wombat.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/wombat.mdx
deleted file mode 100644
index 54cedacea..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/wombat.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
-# Wombat
-
-
-
-
-
-
-[Wombat](https://github.com/rogchap/wombat) is a cross platform gRPC client.
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/ytd.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/ytd.mdx
deleted file mode 100644
index 178ff0529..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/ytd.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
-# Ytd
-
-
-
-
-
-
-[Ytd](https://github.com/marcio199226/ytd/tree/v2-wails) is an app for downloading tracks from youtube, creating offline playlists and share them with your friends, your friends will be able to playback your playlists or download them for offline listening, has an built-in player.
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/templates.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/templates.mdx
deleted file mode 100644
index d9a29a6fa..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/templates.mdx
+++ /dev/null
@@ -1,52 +0,0 @@
----
-sidebar_position: 1
----
-
-# Templates
-
-This page serves as a list for community supported templates. Please submit a PR (click `Edit this page` at the bottom) to include your templates. To build your own template, please see the [Templates](../guides/templates.mdx) guide.
-
-To use these templates, run `wails init -n "Your Project Name" -t [the link below[@version]]`
-
-If there is no version suffix, the main branch code template is used by default. If there is a version suffix, the code template corresponding to the tag of this version is used.
-
-Example: `wails init -n "Your Project Name" -t https://github.com/misitebao/wails-template-vue`
-
-:::warning Attention
-
-**The Wails project does not maintain, is not responsible nor liable for 3rd party templates!**
-
-If you are unsure about a template, inspect `package.json` and `wails.json` for what scripts are run and what packages are installed.
-
-:::
-
-## Vue
-
-- [wails-template-vue](https://github.com/misitebao/wails-template-vue) - A template using Vite,Vue and Vue-Router(Support both JavaScript and TypeScript)
-- [wails-vite-vue-ts](https://github.com/codydbentley/wails-vite-vue-ts) - Vue 3 TypeScript with Vite (and instructions to add features)
-- [wails-vite-vue-the-works](https://github.com/codydbentley/wails-vite-vue-the-works) - Vue 3 TypeScript with Vite, Vuex, Vue Router, Sass, and ESLint + Prettier
-
-## Angular
-
-- [wails-angular-template](https://github.com/TAINCER/wails-angular-template) - Angular with TypeScript, Sass, Hot-Reload, Code-Splitting and i18n
-
-## React
-
-- [wails-react-template](https://github.com/AlienRecall/wails-react-template) - A template using reactjs
-- [wails-react-template](https://github.com/flin7/wails-react-template) - A minimal template for React that supports live development
-- [wails-template-nextjs](https://github.com/LGiki/wails-template-nextjs) - A template using Next.js and TypeScript
-
-## Svelte
-
-- [wails-svelte-template](https://github.com/raitonoberu/wails-svelte-template) - A template using Svelte
-- [wails-vite-svelte-template](https://github.com/BillBuilt/wails-vite-svelte-template) - A template using Svelte and Vite
-- [wails-vite-svelte-tailwind-template](https://github.com/BillBuilt/wails-vite-svelte-tailwind-template) - A template using Svelte and Vite with TailwindCSS v3
-- [wails-sveltekit-template](https://github.com/h8gi/wails-sveltekit-template) - A template using SvelteKit
-
-## Elm
-
-- [wails-elm-template](https://github.com/benjamin-thomas/wails-elm-template) - Develop your GUI app with functional programming and a **snappy** hot-reload setup :tada: :rocket:
-
-## Pure JavaScript (Vanilla)
-
-- [wails-pure-js-template](https://github.com/KiddoV/wails-pure-js-template) - A template with nothing but just basic JavaScript, HTML, and CSS
\ No newline at end of file
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/_category_.json b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/_category_.json
deleted file mode 100644
index 597b920df..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Getting Started",
- "position": 10
-}
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/building.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/building.mdx
deleted file mode 100644
index 3e0df3b68..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/building.mdx
+++ /dev/null
@@ -1,21 +0,0 @@
----
-sidebar_position: 6
----
-
-# Compiling your Project
-
-From the project directory, run `wails build`. This will compile your project and save the production-ready binary in the `build/bin` directory.
-
-If you run the binary, you should see the default application:
-
-
-
-
-
-
-
-For more details on compilation options, please refer to the [CLI Reference](../reference/cli.mdx#build).
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/development.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/development.mdx
deleted file mode 100644
index 54dda5faa..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/development.mdx
+++ /dev/null
@@ -1,16 +0,0 @@
----
-sidebar_position: 5
----
-
-# Developing your Application
-
-You can run your application in development mode by running `wails dev` from your project directory. This will do the following things:
-
-- Build your application and run it
-- Bind your Go code to the frontend so it can be called from Javascript
-- Using the power of [vite](https://vitejs.dev/), will watch for modifications in your Go files and rebuild/re-run on change
-- Sets up a [webserver](http://localhost:34115) that will serve your application over a browser. This allows you to use your favourite browser extensions. You can even call your Go code from the console
-
-To get started, run `wails dev` in the project directory. More information on this can be found [here](../reference/cli.mdx#dev).
-
-Coming soon: Tutorial
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/firstproject.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/firstproject.mdx
deleted file mode 100644
index 94e330c47..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/firstproject.mdx
+++ /dev/null
@@ -1,130 +0,0 @@
----
-sidebar_position: 2
----
-
-# Creating a Project
-
-## Project Generation
-
-Now that the CLI is installed, you can generate a new project by using the `wails init` command.
-
-Pick your favourite framework:
-
-
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-
-
-
- Generate a Svelte project using Javascript with:
-
- wails init -n myproject -t svelte
-If you would rather use Typescript:
-
- wails init -n myproject -t svelte-ts
-
-
-
- Generate a React project using Javascript with:
-
- wails init -n myproject -t react
-If you would rather use Typescript:
-
- wails init -n myproject -t react-ts
-
-
-
- Generate a Vue project using Javascript with:
-
- wails init -n myproject -t vue
-
-If you would rather use Typescript:
-
- wails init -n myproject -t vue-ts
-
-
-
- Generate a Preact project using Javascript with:
-
- wails init -n myproject -t preact
-
-If you would rather use Typescript:
-
- wails init -n myproject -t preact-ts
-
-
-
- Generate a Lit project using Javascript with:
-
- wails init -n myproject -t lit
-
-If you would rather use Typescript:
-
- wails init -n myproject -t lit-ts
-
-
-
- Generate a Vanilla project using Javascript with:
-
- wails init -n myproject -t vanilla
-
-If you would rather use Typescript:
-
- wails init -n myproject -t vanilla-ts
-
-
-
-
-
-
-
-
-There are also [community templates](../community/templates.mdx) available that offer different capabilities and frameworks.
-
-To see the other options available, you can run `wails init -help`. More details can be found in the [CLI Reference](../reference/cli.mdx#init).
-
-## Project Layout
-
-Wails projects have the following layout:
-
-```
-.
-├── build/
-│ ├── appicon.png
-│ ├── darwin/
-│ └── windows/
-├── frontend/
-├── go.mod
-├── go.sum
-├── main.go
-└── wails.json
-```
-
-### Project structure rundown
-
-- `/main.go` - The main application
-- `/frontend/` - Frontend project files
-- `/build/` - Project build directory
-- `/build/appicon.png` - The application icon
-- `/build/darwin/` - Mac specific project files
-- `/build/windows/` - Windows specific project files
-- `/wails.json` - The project configuration
-- `/go.mod` - Go module file
-- `/go.sum` - Go module checksum file
-
-The `frontend` directory has nothing specific to Wails and can be any frontend project of your choosing.
-
-The `build` directory is used during the build process. These files may be updated to customise your builds. If files are removed from the build directory, default versions will be regenerated.
-
-The default module name in `go.mod` is "changeme". You should change this to something more appropriate.
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/installation.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/installation.mdx
deleted file mode 100644
index 5c37d84ff..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/installation.mdx
+++ /dev/null
@@ -1,90 +0,0 @@
----
-sidebar_position: 1
----
-
-# Installation
-
-## Supported Platforms
-
-- Windows 10/11 AMD64/ARM64
-- MacOS 10.13+ AMD64
-- MacOS 11.0+ ARM64
-- Linux AMD64/ARM64
-
-## Dependencies
-
-Wails has a number of common dependencies that are required before installation:
-
-- Go 1.17+
-- NPM (Node 15+)
-
-### Go
-
-Download Go from the [Go Downloads Page](https://go.dev/doc/install).
-
-Ensure that you follow the official [Go installation instructions](https://go.dev/doc/install). You will also need to ensure that your `PATH` environment variable also includes the path to your `~/go/bin` directory. Restart your terminal and do the following checks:
-
-- Check Go is installed correctly: `go version`
-- Check "~/go/bin" is in your PATH variable: `echo $PATH | grep go/bin`
-
-### NPM
-
-Download NPM from the [Node Downloads Page](https://nodejs.org/en/download/). It is best to use the latest release as that is what we generally test against.
-
-Run `npm --version` to verify.
-
-## Platform Specific Dependencies
-
-You will also need to install platform specific dependencies:
-
-
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-
-
-
- Wails requires that the xcode command line tools are installed. This can be done by running:
- xcode-select --install
-
-
- Wails requires that the WebView2{" "}
- runtime is installed. Some Windows installations will already have this installed. You can check using
- the{" "}
- wails doctor command (see below).
-
-
- Linux required the standard gcc build tools
- plus libgtk3 and libwebkit. Rather than list a ton of commands for different distros, Wails can try to determine
- what the installation commands are for your specific distribution. Run wails doctor after
- installation
- to be shown how to install the dependencies. If your distro/package manager is not supported, please consult the {" "}
- Add Linux Distro guide.
-
-
-
-
-
-## Optional Dependencies
-
-- [UPX](https://upx.github.io/) for compressing your applications.
-
-## Installing Wails
-
-Run `go install github.com/wailsapp/wails/v2/cmd/wails@latest` to install the Wails CLI.
-
-## System Check
-
-Running `wails doctor` will check if you have the correct dependencies installed. If not, it will advise on what is missing and help on how to rectify any problems.
-
-## The `wails` command appears to be missing?
-
-If your system is reporting that the `wails` command is missing, make sure you have followed the Go installation guide correctly. Normally, it means that the `go/bin` directory in your User's home directory is not in the `PATH` environment variable. You will also normally need to close and reopen any open command prompts so that changes to the environment made by the installer are reflected at the command prompt.
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/_category_.json b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/_category_.json
deleted file mode 100644
index 5935dad93..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Guides",
- "position": 50
-}
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/application-development.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/application-development.mdx
deleted file mode 100644
index a618076f1..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/application-development.mdx
+++ /dev/null
@@ -1,194 +0,0 @@
-# Application Development
-
-There are no hard and fast rules for developing applications with Wails, but there are some basic guidelines.
-
-## Application Setup
-
-The pattern used by the default templates are that `main.go` is used for configuring and running the application, whilst `app.go` is used for defining the application logic.
-
-The `app.go` file will define a struct that has 2 methods which act as hooks into the main application:
-
-```go title="app.go"
-type App struct {
- ctx context.Context
-}
-
-func NewApp() *App {
- return &App{}
-}
-
-func (a *App) startup(ctx context.Context) {
- a.ctx = ctx
-}
-
-func (a *App) shutdown(ctx context.Context) {
-}
-```
-
-- The startup method is called as soon as Wails allocates the resources it needs and is a good place for creating resources, setting up event listeners and anything else the application needs at startup. It is given a `context.Context` which is usually saved in a struct field. This context is needed for calling the [runtime](../reference/runtime/intro.mdx). If this method returns an error, the application will terminate. In dev mode, the error will be output to the console.
-
-- The shutdown method will be called by Wails right at the end of the shutdown process. This is a good place to deallocate memory and perform any shutdown tasks.
-
-The `main.go` file generally consists of a single call to `wails.Run()`, which accepts the application configuration. The pattern used by the templates is that before the call to `wails.Run()`, an instance of the struct we defined in `app.go` is created and saved in a variable called `app`. This configuration is where we add our callbacks:
-
-```go {3,9,10} title="main.go"
-func main() {
-
- app := NewApp()
-
- err := wails.Run(&options.App{
- Title: "My App",
- Width: 800,
- Height: 600,
- OnStartup: app.startup,
- OnShutdown: app.shutdown,
- })
- if err != nil {
- log.Fatal(err)
- }
-}
-
-```
-
-More information on application lifecycle hooks can be found [here](../howdoesitwork.mdx#application-lifecycle-callbacks).
-
-## Binding Methods
-
-It is likely that you will want to call Go methods from the frontend. This is normally done by adding public methods to the already defined struct in `app.go`:
-
-```go {16-18} title="app.go"
-type App struct {
- ctx context.Context
-}
-
-func NewApp() *App {
- return &App{}
-}
-
-func (a *App) startup(ctx context.Context) {
- a.ctx = ctx
-}
-
-func (a *App) shutdown(ctx context.Context) {
-}
-
-func (a *App) Greet(name string) string {
- return fmt.Sprintf("Hello %s!", name)
-}
-```
-
-In the main application configuration, the `Bind` key is where we can tell Wails what we want to bind:
-
-```go {11-13} title="main.go"
-func main() {
-
- app := NewApp()
-
- err := wails.Run(&options.App{
- Title: "My App",
- Width: 800,
- Height: 600,
- OnStartup: app.startup,
- OnShutdown: app.shutdown,
- Bind: []interface{}{
- app,
- },
- })
- if err != nil {
- log.Fatal(err)
- }
-}
-
-```
-
-This will bind all public methods in our `App` struct (it will never bind the startup and shutdown methods).
-
-### Dealing with context when binding multiple structs
-
-If you want to bind methods for multiple structs but want each struct to keep a reference to the context so that you can use the runtime functions, a good pattern is to pass the context from the `OnStartup` method to your struct instances :
-
-```go
-func main() {
-
- app := NewApp()
- otherStruct := NewOtherStruct()
-
- err := wails.Run(&options.App{
- Title: "My App",
- Width: 800,
- Height: 600,
- OnStartup: func(ctx context.Context){
- app.SetContext(ctx)
- otherStruct.SetContext(ctx)
- },
- OnShutdown: app.shutdown,
- Bind: []interface{}{
- app,
- otherStruct
- },
- })
- if err != nil {
- log.Fatal(err)
- }
-}
-```
-
-More information on Binding can be found [here](../howdoesitwork.mdx#method-binding).
-
-## Application Menu
-
-Wails supports adding a menu to your application. This is done by passing a [Menu](../reference/menus.mdx#menu) struct to application config. It's common to use a method that returns a Menu, and even more common for that to be a method on the `App` struct used for the lifecycle hooks.
-
-```go {11} title="main.go"
-func main() {
-
- app := NewApp()
-
- err := wails.Run(&options.App{
- Title: "My App",
- Width: 800,
- Height: 600,
- OnStartup: app.startup,
- OnShutdown: app.shutdown,
- Menu: app.menu(),
- Bind: []interface{}{
- app,
- },
- })
- if err != nil {
- log.Fatal(err)
- }
-}
-
-```
-
-## Assets
-
-The great thing about the way Wails v2 handles assets is that it doesn't! The only thing you need to give Wails is an `embed.FS`. How you get to that is entirely up to you. You can use vanilla html/css/js files like the vanilla template. You could have some complicated build system, it doesn't matter.
-
-When `wails build` is run, it will check the `wails.json` project file at the project root. There are 2 keys in the project file that are read:
-
-- "frontend:install"
-- "frontend:build"
-
-The first, if given, will be executed in the `frontend` directory to install the node modules. The second, if given, will be executed in the `frontend` directory to build the frontend project.
-
-If these 2 keys aren't given, then Wails does absolutely nothing with the frontend. It is only expecting that `embed.FS`.
-
-### AssetsHandler
-
-A Wails v2 app can optionally define a `http.Handler` in the `options.App`, which allows hooking into the AssetServer to create files on the fly or process POST/PUT requests. GET requests are always first handled by the `assets` FS. If the FS doesn't find the requested file the request will be forwarded to the `http.Handler` for serving. Any requests other than GET will be directly processed by the `AssetsHandler` if specified. It's also possible to only use the `AssetsHandler` by specifiy `nil` as the `Assets` option.
-
-## Built in Dev Server
-
-Running `wails dev` will start the built in dev server which will start a file watcher in your project directory. By default, if any file changes, wails checks if it was an application file (default: `.go`, configurable with `-e` flag). If it was, then it will rebuild your application and relaunch it. If the changed file was in the assets, it will issue a reload after a short amount of time.
-
-The dev server uses a technique called "debouncing" which means it doesn't reload straight away, as there may be multiple files changed in a short amount of time. When a trigger occurs, it waits for a set amount of time before issuing a reload. If another trigger happens, it resets to the wait time again. By default this value is `100ms`. If this value doesn't work for your project, it can be configured using the `-debounce` flag. If used, this value will be saved to your project config and become the default.
-
-## External Dev Server
-
-Some frameworks come with their own live-reloading server, however they will not be able to take advantage of the Wails Go bindings. In this scenario, it is best to run a watcher script that rebuilds the project into the build directory, which Wails will be watching. For an example, see the default svelte template that uses [rollup](https://rollupjs.org/guide/en/). For [create-react-app](https://create-react-app.dev/), it's possible to use [this script](https://gist.github.com/int128/e0cdec598c5b3db728ff35758abdbafd) to achieve a similar result.
-
-## Go Module
-
-The default Wails templates generate a `go.mod` file that contains the module name "changeme". You should change this to something more appropriate after project generation.
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/bleeding-edge.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/bleeding-edge.mdx
deleted file mode 100644
index b81cc79dc..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/bleeding-edge.mdx
+++ /dev/null
@@ -1,55 +0,0 @@
-# Bleeding Edge
-
-## Overview
-
-Wails is in constant development and new releases are regularly "tagged". This usually happens when all the newer code on `master` has been tested and confirmed working. If you need a bugfix or feature that has not yet made it to a release, it's possible to use the latest "bleeding edge" version using the following steps:
-
-- `git clone https://github.com/wailsapp/wails`
-- `cd wails/v2/cmd/wails`
-- `go install`
-
-NOTE: The directory that you cloned the project into will now be called "clonedir".
-
-The Wails CLI will now be at the very latest version.
-
-### Updating your project
-
-To update projects to use the latest version of the Wails library, update the project's `go.mod` and ensure the following line is at the bottom of the file:
-
-`replace github.com/wailsapp/wails/v2 => `
-
-Example:
-
-On Windows: `replace github.com/wailsapp/wails/v2 => C:\Users\leaan\Documents\wails-v2-beta\wails\v2`
-
-On 'nix: `replace github.com/wailsapp/wails/v2 => /home/me/projects/wails/v2`
-
-To revert to a stable version, run:
-
-`go install github.com/wailsapp/wails/v2/cmd/wails@latest`
-
-## Testing a Branch
-
-If you want to test a branch, follow the instructions above, but ensure you switch the branch you want to test before installing:
-
-- `git clone https://github.com/wailsapp/wails`
-- `cd wails`
-- `git checkout -b branch-to-test --track origin/branch-to-test`
-- `cd v2/cmd/wails`
-- `go install`
-
-Make sure you [update your project](#updating-your-project) as described above.
-
-## Testing a PR
-
-If you want to test a PR, follow the instructions above, but ensure you fetch the PR and switch the branch before installing. Please replace `[IDofThePR]` with the ID of the PR shown on github.com:
-
-- `git clone https://github.com/wailsapp/wails`
-- `cd wails`
-- `git fetch -u origin pull/[IDofThePR]/head:test/pr-[IDofThePR]`
-- `git checkout test/pr-[IDofThePR]`
-- `git reset --hard HEAD`
-- `cd v2/cmd/wails`
-- `go install`
-
-Make sure you [update your project](#updating-your-project) as described above.
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/dynamic-assets.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/dynamic-assets.mdx
deleted file mode 100644
index 77ad6d09e..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/dynamic-assets.mdx
+++ /dev/null
@@ -1,126 +0,0 @@
-# Dynamic Assets
-
-If you want to load or generate assets for your frontend dynamically, you can achieve that using the [AssetsHandler](../reference/options#assetshandler) option. The AssetsHandler is a generic `http.Handler` which will be called for any non GET request on the assets server and for GET requests which can not be served from the bundled assets because the file is not found.
-
-By installing a custom AssetsHandler, you can serve your own assets using a custom asset server.
-
-## Example
-
-In our example project, we will create a simple assets handler which will load files off disk:
-
-```go title=main.go {16-35,49}
-package main
-
-import (
- "embed"
- "fmt"
- "github.com/wailsapp/wails/v2"
- "github.com/wailsapp/wails/v2/pkg/options"
- "net/http"
- "os"
- "strings"
-)
-
-//go:embed frontend/dist
-var assets embed.FS
-
-type FileLoader struct {
- http.Handler
-}
-
-func NewFileLoader() *FileLoader {
- return &FileLoader{}
-}
-
-func (h *FileLoader) ServeHTTP(res http.ResponseWriter, req *http.Request) {
- var err error
- requestedFilename := strings.TrimPrefix(req.URL.Path, "/")
- println("Requesting file:", requestedFilename)
- fileData, err := os.ReadFile(requestedFilename)
- if err != nil {
- res.WriteHeader(http.StatusBadRequest)
- res.Write([]byte(fmt.Sprintf("Could not load file %s", requestedFilename)))
- }
-
- res.Write(fileData)
-}
-
-func main() {
- // Create an instance of the app structure
- app := NewApp()
-
- // Create application with options
- err := wails.Run(&options.App{
- Title: "helloworld",
- Width: 1024,
- Height: 768,
- Assets: assets,
- BackgroundColour: &options.RGBA{R: 27, G: 38, B: 54, A: 255},
- OnStartup: app.startup,
- AssetsHandler: NewFileLoader(),
- Bind: []interface{}{
- app,
- },
- })
-
- if err != nil {
- println("Error:", err)
- }
-}
-```
-
-When we run the application in dev mode using `wails dev`, we will see the following output:
-
-```
-DEB | [ExternalAssetHandler] Loading 'http://localhost:3001/favicon.ico'
-DEB | [ExternalAssetHandler] Loading 'http://localhost:3001/favicon.ico' failed, using AssetHandler
-Requesting file: favicon.ico
-```
-
-As you can see, the assets handler is called when the default assets server is unable to serve the `favicon.ico` file.
-
-If you right click the main application and select "inspect" to bring up the devtools, you can test this feature out by typing the following into the console:
-
-```
-let response = await fetch('does-not-exist.txt');
-```
-
-This will generate an error in the devtools. We can see that the error is what we expect, returned by our custom assets handler:
-
-
-
-
-
-However, if we request `go.mod`, we will see the following output:
-
-
-
-
-
-This technique can be used to load images directly into the page. If we updated our default vanilla template and replaced the logo image:
-
-```html
-
-```
-
-with:
-
-```html
-
-```
-
-Then we would see the following:
-
-
-
-
-
-:::warning
-Exposing your filesystem in this way is a security risk. It is recommended that you properly manage access
-to your filesystem.
-:::
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/frameless.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/frameless.mdx
deleted file mode 100644
index c7ca5f6c3..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/frameless.mdx
+++ /dev/null
@@ -1,84 +0,0 @@
-# Frameless Applications
-
-Wails supports application that have no frames. This can be achieved by using the [frameless](../reference/options.mdx#frameless) field in [Application Options](../reference/options.mdx#application-options).
-
-Wails offers a simple solution for dragging the window: Any HTML element that has the CSS style `--wails-draggable:drag` will act as a "drag handle". This property applies to all child elements. If you need to indicate that a nested element should not drag, then use the attribute '--wails-draggable:no-drag' on that element.
-
-
-```html
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-```
-
-For some projects, using a CSS variable may not be possible due to dynamic styling. In this case, you can use the `CSSDragProperty` and `CSSDragValue` application options to define a property and value that will be used to indicate draggable regions:
-
-```go title=main.go
-package main
-
-import (
- "embed"
-
- "github.com/wailsapp/wails/v2"
- "github.com/wailsapp/wails/v2/pkg/options"
-)
-
-//go:embed frontend/dist
-var assets embed.FS
-
-func main() {
- // Create an instance of the app structure
- app := NewApp()
-
- // Create application with options
- err := wails.Run(&options.App{
- Title: "alwaysontop",
- Width: 1024,
- Height: 768,
- Assets: assets,
- Frameless: true,
- CSSDragProperty: "widows",
- CSSDragValue: "1",
- Bind: []interface{}{
- app,
- },
- })
-
- if err != nil {
- println("Error:", err)
- }
-}
-```
-
-```html title=index.html
-
-
-
-
-
- alwaysontop
-
-
-
-
-
-
-
-```
-
-:::info Fullscreen
- If you allow your application to go fullscreen, this drag functionality will be disabled.
-:::
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/frontend.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/frontend.mdx
deleted file mode 100644
index 4b192c557..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/frontend.mdx
+++ /dev/null
@@ -1,75 +0,0 @@
-# Frontend
-
-## Script Injection
-
-When Wails serves your `index.html`, by default, it will inject 2 script entries into the `` tag to load `/wails/ipc.js` and `/wails/runtime.js`. These files install the bindings and runtime respectively.
-
-The code below shows where these are injected by default:
-
-```html
-
-
- injection example
-
-
-
-
-
-
-
-
Please enter your name below 👇
-
-
-
-
-
-
-
-
-
-```
-
-### Overriding Default Script Injection
-
-To provide more flexibility to developers, there is a meta tag that may be used to customise this behaviour:
-
-```html
-
-```
-
-The options are as follows:
-
-| Value | Description |
-| ------------------- | ------------------------------------------------ |
-| noautoinjectruntime | Disable the autoinjection of `/wails/runtime.js` |
-| noautoinjectipc | Disable the autoinjection of `/wails/ipc.js` |
-| noautoinject | Disable all autoinjection of scripts |
-
-Multiple options may be used provided they are comma seperated.
-
-This code is perfectly valid and operates the same as the autoinjection version:
-
-```html
-
-
-
- injection example
-
-
-
-
-
-
-
Please enter your name below 👇
-
-
-
-
-
-
-
-
-
-
-
-```
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/ides.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/ides.mdx
deleted file mode 100644
index a20ae4131..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/ides.mdx
+++ /dev/null
@@ -1,113 +0,0 @@
-# IDEs
-
-Wails aims to provide a great development experience. To that aim, we now support generating IDE specific configuration to provide smoother project setup.
-
-Currently, we support [Visual Studio Code](https://code.visualstudio.com/) but aim to support other IDEs such as Goland.
-
-## Visual Studio Code
-
-
-
-
-
-When generating a project using the `-ide vscode` flags, IDE files will be created alongside the other project files. These files are placed into the `.vscode` directory and provide the correct configuration for debugging your application.
-
-The 2 files generated are `tasks.json` and `launch.json`. Below are the files generated for the default vanilla project:
-
-```json title="tasks.json"
-{
- "version": "2.0.0",
- "tasks": [
- {
- "label": "build",
- "type": "shell",
- "options": {
- "cwd": "${workspaceFolder}"
- },
- "command": "go",
- "args": ["build", "-tags", "dev", "-gcflags", "all=-N -l", "-o", "build/bin/myproject.exe"]
- },
- ]
-}
-```
-
-```json title="launch.json"
-{
- "version": "0.2.0",
- "configurations": [
- {
- "name": "Wails: Debug myproject",
- "type": "go",
- "request": "launch",
- "mode": "exec",
- "program": "${workspaceFolder}/build/bin/myproject.exe",
- "preLaunchTask": "build",
- "cwd": "${workspaceFolder}",
- "env": {}
- },
- ]
-}
-```
-
-### Configuring the install and build steps
-
-The `tasks.json` file is simple for the default project as there is no `npm install` or `npm run build` step needed. For projects that have a frontend build step, such as the svelte template, we would need to edit `tasks.json` to add the install and build steps:
-
-```json title="tasks.json"
-{
- "version": "2.0.0",
- "tasks": [
- {
- "label": "npm install",
- "type": "npm",
- "script": "install",
- "options": {
- "cwd": "${workspaceFolder}/frontend"
- },
- "presentation": {
- "clear": true,
- "panel": "shared",
- "showReuseMessage": false
- },
- "problemMatcher": []
- },
- {
- "label": "npm run build",
- "type": "npm",
- "script": "build",
- "options": {
- "cwd": "${workspaceFolder}/frontend"
- },
- "presentation": {
- "clear": true,
- "panel": "shared",
- "showReuseMessage": false
- },
- "problemMatcher": []
- },
- {
- "label": "build",
- "type": "shell",
- "options": {
- "cwd": "${workspaceFolder}"
- },
- "command": "go",
- "args": ["build", "-tags", "dev", "-gcflags", "all=-N -l", "-o", "build/bin/vscode.exe"],
- "dependsOn":[
- "npm install",
- "npm run build"
- ]
-
- },
- ]
-}
-```
-
-:::info Future Enhancement
-
-In the future, we hope to generate a `tasks.json` that includes the install and build steps automatically.
-
-:::
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/linux-distro-support.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/linux-distro-support.mdx
deleted file mode 100644
index 28a224a26..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/linux-distro-support.mdx
+++ /dev/null
@@ -1,101 +0,0 @@
-# Linux Distro Support
-
-## Overview
-
-Wails offers Linux support but providing installation instructions for all available distributions is an impossible task. Instead, Wails tries to determine if the packages you need to develop applications are available via your system's package manager. Currently, we support the following package managers:
-
-- apt
-- dnf
-- emerge
-- eopkg
-- nixpkgs
-- pacman
-- zypper
-
-## Adding package names
-
-There may be circumstances where your distro uses one of the supported package managers but the package name is different. For example, you may use an Ubuntu derivative, but the package name for gtk may be different. Wails attempts to find the correct package by iterating through a list of package names. The list of packages are stored in the packagemanager specific file in the `v2/internal/system/packagemanager` directory. In our example, this would be `v2/internal/system/packagemanager/apt.go`.
-
-In this file, the list of packages are defined by the `Packages()` method:
-
-```go
-func (a *Apt) Packages() packagemap {
- return packagemap{
- "libgtk-3": []*Package{
- {Name: "libgtk-3-dev", SystemPackage: true, Library: true},
- },
- "libwebkit": []*Package{
- {Name: "libwebkit2gtk-4.0-dev", SystemPackage: true, Library: true},
- },
- "gcc": []*Package{
- {Name: "build-essential", SystemPackage: true},
- },
- "pkg-config": []*Package{
- {Name: "pkg-config", SystemPackage: true},
- },
- "npm": []*Package{
- {Name: "npm", SystemPackage: true},
- },
- "docker": []*Package{
- {Name: "docker.io", SystemPackage: true, Optional: true},
- },
- }
-}
-```
-
-Let's assume that in our linux distro, `libgtk-3` is packaged under the name `lib-gtk3-dev`. We could add support for this by adding the following line:
-
-```go {5}
-func (a *Apt) Packages() packagemap {
- return packagemap{
- "libgtk-3": []*Package{
- {Name: "libgtk-3-dev", SystemPackage: true, Library: true},
- {Name: "lib-gtk3-dev", SystemPackage: true, Library: true},
- },
- "libwebkit": []*Package{
- {Name: "libwebkit2gtk-4.0-dev", SystemPackage: true, Library: true},
- },
- "gcc": []*Package{
- {Name: "build-essential", SystemPackage: true},
- },
- "pkg-config": []*Package{
- {Name: "pkg-config", SystemPackage: true},
- },
- "npm": []*Package{
- {Name: "npm", SystemPackage: true},
- },
- "docker": []*Package{
- {Name: "docker.io", SystemPackage: true, Optional: true},
- },
- }
-}
-```
-
-## Adding new package managers
-
-To add a new package manager, perform the following steps:
-
-- Create a new file in `v2/internal/system/packagemanager` called `.go`, where `` is the name of the package manager.
-- Define a struct that conforms to the package manager interface defined in `pm.go`:
-
-```go
-type PackageManager interface {
- Name() string
- Packages() packagemap
- PackageInstalled(*Package) (bool, error)
- PackageAvailable(*Package) (bool, error)
- InstallCommand(*Package) string
-}
-```
-
-- `Name()` should return the name of the package manager
-- `Packages()` should return a `packagemap`, that provides candidate filenames for dependencies
-- `PackageInstalled()` should return `true` if the given package is installed
-- `PackageAvailable()` should return `true` if the given package is not installed but available for installation
-- `InstallCommand()` should return the exact command to install the given package name
-
-Take a look at the other package managers code to get an idea how this works.
-
-:::info Remember
-If you add support for a new package manager, don't forget to also update this page!
-:::
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/linux.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/linux.mdx
deleted file mode 100644
index 229c282bf..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/linux.mdx
+++ /dev/null
@@ -1,18 +0,0 @@
-# Linux
-
-This page has miscellaneous guides related to developing Wails applications for Linux.
-
-## Video tag doesn't fire "ended" event
-
-When using a video tag, the "ended" event is not fired when the video is finished playing. This is a bug in WebkitGTK, however you can use the following workaround to fix it:
-
-```js
-videoTag.addEventListener("timeupdate", (event) => {
- if (event.target.duration - event.target.currentTime < 0.2) {
- let ended = new Event("ended");
- event.target.dispatchEvent(ended);
- }
-});
-```
-
-Source: [Lyimmi](https://github.com/Lyimmi) on the [discussions board](https://github.com/wailsapp/wails/issues/1729#issuecomment-1212291275)
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/manual-builds.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/manual-builds.mdx
deleted file mode 100644
index dcf192d33..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/manual-builds.mdx
+++ /dev/null
@@ -1,95 +0,0 @@
-# Manual Builds
-
-The Wails CLI does a lot of heavy lifting for the project, but sometimes it's desirable to manually build your project. This document will discuss the different operations the CLI does and how this may be achieved in different ways.
-
-## Build Process
-
-When either `wails build` or `wails dev` are used, the Wails CLI performs a common build process:
-
- - Install frontend dependencies
- - Build frontend project
- - Generate build assets
- - Compile application
- - [optional] Compress application
-
-### Install frontend dependencies
-
-#### CLI Steps
-
-- If the `-s` flag is given, this step is skipped
-- Checks `wails.json` to see if there is an install command in the key `frontend:install`
-- If there isn't, it skips this step
-- If there is, it checks if `package.json` exists in the frontend directory. If it doesn't exist, it skips this step
-- An MD5 sum is generated from the `package.json` file contents
-- It checks for the existence of `package.json.md5` and if it exists, will compare the contents of it (an MD5 sum) with the one generated to see if the contents have changed. If they are the same, this step is skipped
-- If `package.json.md5` does not exist, it creates it using the generated MD5 sum
-- If a build is now required, or `node_modules` does not exist, or the `-f` flag is given, the install command is executed in the frontend directory
-
-#### Manual Steps
-
-This step could be done from the command line or a script with `npm install`.
-
-### Build frontend project
-
-#### Wails CLI
-
-- If the `-s` flag is given, this step is skipped
-- Checks `wails.json` to see if there is a build command in the key `frontend:build`
-- If there isn't, it skips this step
-- If there is, it is executed in the frontend directory
-
-#### Manual Steps
-
-This step could be done from the command line or a script with `npm run build` or whatever the frontend build script is.
-
-### Generate assets
-
-#### Wails CLI
-
-- If `-nopackage` flag is set, this stage is skipped
-- If the `build/appicon.png` file does not exist, a default one is created
-- For Windows, see [Bundling for Windows](#windows)
-- If `build/windows/icon.ico` does not exist, it will create it from the `build/appicon.png` image.
-
-##### Windows
-
-- If `build/windows/icon.ico` does not exist, it will create it from `build/appicon.png` using icon sizes of 256, 128, 64, 48, 32 and 16. This is done using [winicon](https://github.com/leaanthony/winicon).
-- If the `build/windows/.manifest` file does not exist, it creates it from a default version.
-- Compiles the application as a production build (above)
-- Uses [winres](https://github.com/tc-hib/winres) to bundle the icon and manifest into a `.syso` file ready for linking.
-
-#### Manual Steps
-
-- Create `icon.ico` using the [winicon](https://github.com/leaanthony/winicon) CLI tool (or any other tool).
-- Create / Update a `.manifest` file for your application
-- Use the [winres CLI](https://github.com/tc-hib/go-winres) to generate a `.syso` file.
-
-### Compile application
-
-#### Wails CLI
-
-- If the `-clean` flag is provided, the `build` directory is deleted and recreated
-- For `wails dev`, the following default Go flags are used: `-tags dev -gcflags "all=-N -l"`
-- For `wails build`, the following default Go flags are used: `-tags desktop,production -ldflags "-w -s"`
- - On Windows, `-ldflags "-w -h -H windowsgui"`
-- Additional tags passed to the CLI using `-tags` are added to the defaults
-- Additional ldflags passed to the CLI using `-ldflags` are added to the defaults
-- The `-o` flag is passed through
-- The Go compiler specified by `-compiler` will be used for compilation
-
-#### Manual steps
-
-- For dev build, the minimum command would be: `go build -tags dev -gcflags "all=-N -l"`
-- For production build, the minimum command would be: `go build -tags desktop,production -ldflags "-w -s -H windowsgui"`
-- Ensure that you compile in the same directory as the `.syso` file
-
-### Compress application
-
-#### Wails CLI
-
-- If the `-upx` flag has been given, the `upx` program will be run to compress the application with the default settings
-- If `-upxflags` is also passed, these flags are used instead of the default ones
-
-#### Manual steps
-
-- Run `upx [flags]` manually to compress the application.
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/migrating.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/migrating.mdx
deleted file mode 100644
index 2dff1a91b..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/migrating.mdx
+++ /dev/null
@@ -1,189 +0,0 @@
-# Migrating from v1
-
-## Overview
-
-Wails v2 is a significant change from v1. This document aims to highlight the changes and the steps in migrating an existing project.
-
-### Creating the Application
-
-In v1, the main application is created using `wails.CreateApp`, bindings are added with `app.Bind`, then the application is run using `app.Run()`.
-
-Example:
-
-```go title="v1"
- app := wails.CreateApp(&wails.AppConfig{
- Title: "MyApp",
- Width: 1024,
- Height: 768,
- JS: js,
- CSS: css,
- Colour: "#131313",
- })
- app.Bind(basic)
- app.Run()
-```
-
-In v2, there is just a single method, `wails.Run()`, that accepts [application options](../reference/options.mdx#application-options).
-
-```go title="v2"
- err := wails.Run(&options.App{
- Title: "MyApp",
- Width: 800,
- Height: 600,
- Assets: assets,
- Bind: []interface{}{
- basic,
- },
- })
-```
-
-### Binding
-
-In v1, it was possible to bind both arbitrary functions and structs. In v2, this has been simplified to only binding structs. The struct instances that were previously passed to the `Bind()` method in v1, are now specified in the `Bind` field of the [application options](../reference/options.mdx#application-options):
-
-```go title="v1"
- app := wails.CreateApp(/* options */)
- app.Bind(basic)
-```
-
-```go title="v2"
- err := wails.Run(&options.App{
- /* other options */
- Bind: []interface{}{
- basic,
- },
- })
-```
-
-In v1, bound methods were available to the frontend at `window.backend`. This has changed to `window.go`.``
-
-### Application Lifecycle
-
-In v1, there were 2 special methods in a bound struct: `WailsInit()` and `WailsShutdown()`. These have been replaced with 3 lifecycle hooks as part of the [application options](../reference/options.mdx#application-options):
-
-- [OnStartup](../reference/options.mdx#onstartup)
-- [OnShutdown](../reference/options.mdx#onshutdown)
-- [OnDomReady](../reference/options.mdx#ondomready)
-
-Note: [OnDomReady](../reference/options.mdx#ondomready) replaces the `wails:ready` system event in v1.
-
-These methods can be standard functions, but a common practice is to have them part of a struct:
-
-```go title="v2"
- basic := NewBasicApp()
- err := wails.Run(&options.App{
- /* Other Options */
- OnStartup: basic.startup,
- OnShutdown: basic.shutdown,
- OnDomReady: basic.domready,
- })
-...
-type Basic struct {
- ctx context.Context
-}
-func (b *Basic) startup(ctx context.Context) {
- b.ctx = ctx
-}
-...
-```
-
-### Runtime
-
-The runtime in v2 is much richer than v1 with support for menus, window manipulation and better dialogs. The signature of the methods has changed slightly - please refer the the [Runtime Reference](../reference/runtime/intro.mdx).
-
-In v1, the [runtime](../reference/runtime/intro.mdx) was available via a struct passed to `WailsInit()`. In v2, the runtime has been moved out to its own package. Each method in the runtime takes the `context.Context` that is passed to the [OnStartup](../reference/options.mdx#onstartup) method.
-
-```go title="Runtime Example"
-package main
-
-import "github.com/wailsapp/wails/v2/pkg/runtime"
-
-type Basic struct {
- ctx context.Context
-}
-
-// startup is called at application startup
-func (a *App) startup(ctx context.Context) {
- a.ctx = ctx
- runtime.LogInfo(ctx, "Application Startup called!")
-}
-}
-}
-
-```
-
-### Assets
-
-The _biggest_ change in v2 is how assets are handled.
-
-In v1, assets were passed via 2 application options:
-
-- `JS` - The application's Javascript
-- `CSS` - The application's CSS
-
-This meant that the responsibility of generating a single JS and CSS file was on the developer. This essentially required the use of complicated packers such as webpack.
-
-In v2, Wails makes no assumptions about your frontend assets, just like a webserver. All of your application assets are passed to the application options as an `embed.FS`.
-
-**This means there is no requirement to bundle your assets, encode images as Base64 or attempt the dark art of bundler configuration to use custom fonts**.
-
-At startup, Wails will scan the given `embed.FS` for `index.html` and use its location as the root path for all the other application assets - just like a webserver would.
-
-Example: An application has the following project layout. All final assets are placed in the `frontend/dist` directory:
-
-```shell
-.
-├── build/
-├── frontend/
-│ └── dist/
-│ ├── index.html
-│ ├── main.js
-│ ├── main.css
-│ └── logo.svg
-├── main.go
-└── wails.json
-```
-
-Those assets may be used by the application by simply creating an `embed.FS`:
-
-```go title="Assets Example"
-//go:embed frontend/dist
-var assets embed.FS
-
-func main() {
- err := wails.Run(&options.App{
- /* Other Options */
- Assets: assets,
- })
-}
-```
-
-Of course, bundlers can be used if you wish to. The only requirement is to pass the final application assets directory to Wails using an `embed.FS` in the `Assets` key of the [application options](../reference/options.mdx#application-options).
-
-### Project Configuration
-
-In v1, the project configuration was stored in the `project.json` file in the project root. In v2, the project configuration is stored in the `wails.json` file in the project root.
-
-The format of the file is slightly different. Here is a comparison:
-
-
-
-| v1 | v2 | Notes |
-| ------------------ | ---------------- | --------------------------------------------------- |
-| name | name | |
-| description | | Removed |
-| author / name | author / name | |
-| author / email | author / email | |
-| version | version | |
-| binaryname | outputfilename | Changed |
-| frontend / dir | | Removed |
-| frontend / install | frontend:install | Changed |
-| frontend / build | frontend:build | Changed |
-| frontend / bridge | | Removed |
-| frontend / serve | | Removed |
-| tags | | Removed |
-| | wailsjsdir | The directory to generate wailsjs modules |
-| | assetdir | The directory of the compiled frontend assets for `dev` mode. This is normally inferred and could be left empty. |
-| | reloaddirs | Comma separated list of additional directories to watch for changes and to trigger reloads in `dev` mode. This is only needed for some more advanced asset configurations. |
-
-
-
-## Publishing Templates
-
-Publishing a template is simply pushing the files to GitHub. The following best practice is encouraged:
-
-- Remove any unwanted files and directories (such as `.git`) from your frontend directory
-- Ensure that `template.json` is complete, especially `helpurl`
-- Push the files to GitHub
-- Create a PR on the [Community Templates](../community/templates.mdx) page
-- Announce the template on the [Template Announcement](https://github.com/wailsapp/wails/discussions/825) discussion board
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/troubleshooting.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/troubleshooting.mdx
deleted file mode 100644
index b6a73efa5..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/troubleshooting.mdx
+++ /dev/null
@@ -1,137 +0,0 @@
-# Troubleshooting
-
-An assortment of troubleshooting tips.
-
-## The `wails` command appears to be missing?
-
-If your system is reporting that the `wails` command is missing, make sure you have followed the Go installation guide correctly. Normally, it means that the `go/bin` directory in your User's home directory is not in the `PATH` environment variable. You will also normally need to close and reopen any open command prompts so that changes to the environment made by the installer are reflected at the command prompt.
-
-## My application is displaying a white/blank screen
-
-Check that your application includes the assets from the correct directory. In your `main.go` file, you will have something similar to the following code:
-
-```go
-//go:embed frontend/dist
-var assets embed.FS
-```
-
-Check that `frontend/dist` contains your application assets.
-
-### Mac
-
-If this happens on Mac, try adding the following to your `Info.plist`:
-
-```xml
-NSAppTransportSecurity
-
- NSAllowsLocalNetworking
-
-
-```
-
-Reference: https://github.com/wailsapp/wails/issues/1504#issuecomment-1174317433
-
-## Mac application not valid
-
-If your built application looks like this in finder:
-
-
-
-
-
-it's likely that your application's `info.plist` is invalid. Update the file in `build/.app/Contents/info.plist` and check if the data is valid, EG check the binary name is correct. To persist the changes, copy the file back to the `build/darwin` directory.
-
-## Cannot call backend method from frontend with variadic arguments
-
-If you have a backend method defined with variadic parameters, eg:
-
-```go
-func (a *App) TestFunc(msg string, args ...interface{}) error {
- // Code
-}
-```
-
-calling this method from the frontend like this will fail:
-
-```js
-var msg = "Hello: "
-var args = ["Go", "JS"]
-window.go.main.App.TestFunc(msg, ...args).then((result) => {
- //do things here
-}).catch((error) => {
- //handle error
-});
-```
-
-Workaround:
-
-```js
-var msg = "Hello "
-var args = ["Go", "JS"]
-window.go.main.App.TestFunc(msg, args).then((result) => { //without the 3 dots
- //do things here
-}).catch((error) => {
- //handle error
-});
-```
-
-Credit: https://github.com/wailsapp/wails/issues/1186
-
-## I'm having getting proxy errors when trying to install Wails
-
-If you are getting errors like this:
-
-```
-"https://proxy.golang.org/github.com/wailsapp/wails/cmd/wails/@v/list": dial tcp 172.217.163.49:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
-```
-
-it's probably because the official Go Proxy is being blocked (Users in China have reported this). The solution is to set up the proxy manually, eg:
-
-```
-go env -w GO111MODULE=on
-go env -w GOPROXY=https://goproxy.cn,direct
-```
-
-Source: https://github.com/wailsapp/wails/issues/1233
-
-## The generated Typescript doesn't have the correct types
-
-Sometimes the generated Typescript doesn't have the correct types. To mitigate this, it is possible to specify what types should be generated using the `ts_type` struct tag. For more details, please read [this](https://github.com/tkrajina/typescriptify-golang-structs#custom-types).
-
-## When I navigate away from `index.html`, I am unable to call methods on the frontend
-
-If you navigate away from `index.html` to a new html file, the context will be lost. This can be fixed by adding the following imports to the `` section of any new page you navigate to:
-
-```html
-
-
-
-
-```
-
-Source: https://github.com/wailsapp/wails/discussions/1512
-
-## I get `too many open files` errors on my Mac when I run `wails dev`
-
-By default, macOS will only allow you to open a maximum of 256 files. This can affect the `wails dev` command. This limit can be increased by running: `ulimit -n 1024` in the terminal.
-
-FSNotify is [looking to move to Apple's fsevents](https://github.com/fsnotify/fsnotify/issues/11) for Mac. If this isn't completed soon, we will create our own implementation, tracked [here](https://github.com/wailsapp/wails/issues/1733).
-
-## My Mac app gives me weird compilation errors
-
-A few users have reported seeing compilation errors such as the following:
-
-```shell
-# github.com/wailsapp/wails/v2/internal/frontend/desktop/darwin
-In file included from ../../pkg/mod/github.com/wailsapp/wails/v2@v2.0.0-beta.44.2/internal/frontend/desktop/darwin/callbacks.go:9:
-In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX12.1.sdk/System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:12:
-/Library/Developer/CommandLineTools/SDKs/MacOSX12.1.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSBundle.h:91:143: error: function does not return NSString
-- (NSAttributedString *)localizedAttributedStringForKey:(NSString *)key value:(nullable NSString *)value table:(nullable NSString *)tableName NS_FORMAT_ARGUMENT(1) NS_REFINED_FOR_SWIFT API_AVAILABLE(macos(12.0), ios(15.0), watchos(8.0), tvos(15.0));
- ~~~~~~~~~~~~~~ ^ ~
-/Library/Developer/CommandLineTools/SDKs/MacOSX12.1.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSObjCRuntime.h:103:48: note: expanded from macro 'NS_FORMAT_ARGUMENT'
- #define NS_FORMAT_ARGUMENT(A) __attribute__ ((format_arg(A)))
-```
-
-This is *normally* due to a mismatch with the OS version you are running and the version of the XCode Command Line Tools installed. If you see an error like this, try upgrading your XCode Command Line Tools to the latest version.
-
-Source: https://github.com/wailsapp/wails/issues/1806
\ No newline at end of file
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/vscode.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/vscode.mdx
deleted file mode 100644
index ed258656d..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/vscode.mdx
+++ /dev/null
@@ -1,82 +0,0 @@
-
-# Visual Studio Code
-
-This page is for miscellaneous tips and tricks when using Visual Studio Code with Wails.
-
-## Vetur Configuration
-
-Many thanks to [@Lyimmi](https://github.com/Lyimmi) for this tip. Originally posted [here](https://github.com/wailsapp/wails/issues/1791#issuecomment-1228158349).
-
-Vetur is a popular plugin for Visual Studio Code that provides syntax highlighting and code completion for Vue projects. When loading a Wails project in VSCode, Vetur will throw an error as it is expecting to find the frontend project in the root directory. To fix this, you can do the following:
-
-Create a file named `vetur.config.js` in the project's root.
-
-```javascript
-// vetur.config.js
-/** @type {import('vls').VeturConfig} */
-module.exports = {
- // **optional** default: `{}`
- // override vscode settings
- // Notice: It only affects the settings used by Vetur.
- settings: {
- "vetur.useWorkspaceDependencies": true,
- "vetur.experimental.templateInterpolationService": true
- },
- // **optional** default: `[{ root: './' }]`
- // support monorepos
- projects: [
- {
- // **required**
- // Where is your project?
- // It is relative to `vetur.config.js`.
- // root: './packages/repo1',
- root: './frontend',
- // **optional** default: `'package.json'`
- // Where is `package.json` in the project?
- // We use it to determine the version of vue.
- // It is relative to root property.
- package: './package.json',
- // **optional**
- // Where is TypeScript config file in the project?
- // It is relative to root property.
- tsconfig: './tsconfig.json',
- // **optional** default: `'./.vscode/vetur/snippets'`
- // Where is vetur custom snippets folders?
- snippetFolder: './.vscode/vetur/snippets',
- // **optional** default: `[]`
- // Register globally Vue component glob.
- // If you set it, you can get completion by that components.
- // It is relative to root property.
- // Notice: It won't actually do it. You need to use `require.context` or `Vue.component`
- globalComponents: [
- './src/components/**/*.vue'
- ]
- }
- ]
-}
-```
-
-Next, configure `frontend/tsconfig.json`:
-
-```javascript
-{
- "compilerOptions": {
- "module": "system",
- "noImplicitAny": true,
- "removeComments": true,
- "preserveConstEnums": true,
- "sourceMap": true,
- "outFile": "../../built/local/tsc.js",
- "allowJs": true
- },
- "exclude": [
- "node_modules",
- "**/*.spec.ts"
- ],
- "include": [
- "src/**/*",
- "wailsjs/**/*.ts"
- ]
-}
-```
-This should enable you to now use Vetur as expected.
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/windows-installer.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/windows-installer.mdx
deleted file mode 100644
index 249ec5527..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/windows-installer.mdx
+++ /dev/null
@@ -1,56 +0,0 @@
-# NSIS installer
-
-
-
-
-
-
-Wails supports generating Windows installers using the [NSIS installer](https://nsis.sourceforge.io/).
-
-## Installing NSIS
-
-### Windows
-
-The installer is available on the [NSIS Download](https://nsis.sourceforge.io/Download) page.
-
-If you use the chocolatey package manager, run the following script:
-
-```
-choco install nsis
-```
-
-If you install NSIS manually, you need to add the *Bin* folder, which contains `makensis.exe`, in your NSIS installation to your path. [Here](https://www.architectryan.com/2018/03/17/add-to-the-path-on-windows-10/) is a good tutorial on how to add to path on Windows.
-
-### Linux
-
-The `nsis` package should be available through your distribution's package manager.
-
-### MacOS
-
-NSIS is available to install through homebrew: `brew install nsis`.
-
-## Generating the installer
-
-When a new project is created, Wails generates the NSIS configuration files in `build/windows/installer`. The config data is read from `installer/info.json` and that is configured to use the project's `wails.json` Info section:
-
-```json
-// ...
- "Info": {
- "companyName": "My Company Name",
- "productName": "Wails Vite",
- "productVersion": "1.0.0",
- "copyright": "Copyright.........",
- "comments": "Built using Wails (https://wails.io)"
- },
-```
-
-To generate an installer for your application, use the `-nsis` flag with `wails build`:
-
-```
-wails build -nsis
-```
-
-The installer will now be available in the `build/bin` directory.
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/windows.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/windows.mdx
deleted file mode 100644
index 821808c0b..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/windows.mdx
+++ /dev/null
@@ -1,61 +0,0 @@
-# Windows
-
-This page has miscellaneous guides related to developing Wails applications for Windows.
-
-## Handling the WebView2 Runtime Dependency
-
-Wails applications built for Windows have a runtime requirement on the Microsoft [WebView2 Runtime](https://developer.microsoft.com/en-us/microsoft-edge/webview2/). Windows 11 will have this installed by default, but some machines won't. Wails offers an easy approach to dealing with this dependency.
-
-By using the `-webview2` flag when building, you can decide what your application will do when a suitable runtime is not detected (including if the installed runtime is too old). The four options are:
-
-1. Download
-2. Embed
-3. Browser
-4. Error
-
-### Download
-
-This option will prompt the user that no suitable runtime has been found and then offer to download and run the official bootstrapper from Microsoft's WebView2 site. If the user proceeds, the official bootstrapper will be downloaded and run.
-
-### Embed
-
-This option embeds the official bootstrapper within the application. If no suitable runtime has been found, the application will offer to run the bootstrapper. This adds ~150k to the binary size.
-
-### Browser
-
-This option will prompt the user that no suitable runtime has been found and then offer to open a browser to the official WebView2 page where the bootstrapper can be downloaded and installed. The application will then exit, leaving the installation up to the user.
-
-### Error
-
-If no suitable runtime is found, an error is given to the user and no further action taken.
-
-## Fixed version runtime
-
-Another way of dealing with webview2 dependency is shipping it yourself. You can download [fixed version runtime](https://developer.microsoft.com/microsoft-edge/webview2/#download-section) and bundle or download it with your application.
-
-Also, you should specify path to fixed version of webview2 runtime in the `windows.Options` structure when launching wails.
-
-```go
- wails.Run(&options.App{
- Windows: &windows.Options{
- WebviewBrowserPath: "",
- },
- })
-```
-
-Note: When `WebviewBrowserPath` is specified, `error` strategy will be forced in case of minimal required version mismatch or invalid path to a runtime.
-
-## Spawning other programs
-
-When spawning other programs, such as scripts, you will see the window appear on the screen. To hide the window, you can use the following code:
-
-```go
-cmd := exec.Command("your_script.exe")
-cmd.SysProcAttr = &syscall.SysProcAttr{
- HideWindow: true,
- CreationFlags: 0x08000000,
-}
-cmd.Start()
-```
-
-Solution provided by [sithembiso](https://github.com/sithembiso) on the [discussions board](https://github.com/wailsapp/wails/discussions/1734#discussioncomment-3386172).
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/howdoesitwork.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/howdoesitwork.mdx
deleted file mode 100644
index 0063b47a6..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/howdoesitwork.mdx
+++ /dev/null
@@ -1,356 +0,0 @@
----
-sidebar_position: 20
----
-
-# How does it work?
-
-A Wails application is a standard Go application, with a webkit frontend. The Go part of the application consists of the application code and a runtime library that provides a number of useful operations, like controlling the application window. The frontend is a webkit window that will display the frontend assets. Also available to the frontend is a Javascript version of the runtime library. Finally, it is possible to bind Go methods to the frontend, and these will appear as Javascript methods that can be called, just as if they were local Javascript methods.
-
-
-
-
-
-## The Main Application
-
-### Overview
-
-The main application consists of a single call to `wails.Run()`. It accepts the application configuration which describes the size of the application window, the window title, what assets to use, etc. A basic application might look like this:
-
-```go title="main.go"
-package main
-
-import (
- "embed"
- "log"
-
- "github.com/wailsapp/wails/v2"
- "github.com/wailsapp/wails/v2/pkg/options"
-)
-
-//go:embed frontend/dist
-var assets embed.FS
-
-func main() {
-
- app := &App{}
-
- err := wails.Run(&options.App{
- Title: "Basic Demo",
- Width: 1024,
- Height: 768,
- Assets: &assets,
- OnStartup: app.startup,
- OnShutdown: app.shutdown,
- Bind: []interface{}{
- app,
- },
- })
- if err != nil {
- log.Fatal(err)
- }
-}
-
-
-type App struct {
- ctx context.Context
-}
-
-func (b *App) startup(ctx context.Context) {
- b.ctx = ctx
-}
-
-func (b *App) shutdown(ctx context.Context) {}
-
-func (b *App) Greet(name string) string {
- return fmt.Sprintf("Hello %s!", name)
-}
-```
-
-### Options rundown
-
-This example has the following options set:
-
-- `Title` - The text that should appear in the window's title bar
-- `Width` & `Height` - The dimensions of the window
-- `Assets` - The application's frontend assets
-- `OnStartup` - A callback for when the window is created and is about to start loading the frontend assets
-- `OnShutdown` - A callback for when the application is about to quit
-- `Bind` - A slice of struct instances that we wish to expose to the frontend
-
-A full list of application options can be found in the [Options Reference](reference/options).
-
-#### Assets
-
-The `Assets` option is mandatory as you can't have a Wails application without frontend assets. Those assets can be any files you would expect to find in a web application - html, js, css, svg, png, etc. **There is no requirement to generate asset bundles** - plain files will do. When the application starts, it will attempt to load `index.html` from your assets and the frontend will essentially work as a browser from that point on. It is worth noting that there is no requirement on where in the `embed.FS` the files live. It is likely that the embed path uses a nested directory relative to your main application code, such as `frontend/dist`:
-
-```go title="main.go"
-//go:embed frontend/dist
-var assets embed.FS
-```
-
-At startup, Wails will iterate the embedded files looking for the directory containing `index.html`. All other assets will be loaded relative to this directory.
-
-As production binaries use the files contained in `embed.FS`, there are no external files required to be shipped with the application.
-
-When running in development mode using the `wails dev` command, the assets are loaded off disk, and any changes result in a "live reload". The location of the assets will be inferred from the `embed.FS`.
-
-More details can be found in the [Application Development Guide](guides/application-development.mdx).
-
-#### Application Lifecycle Callbacks
-
-Just before the frontend is about to load `index.html`, a callback is made to the function provided in [OnStartup](reference/options.mdx#onstartup). A standard Go context is passed to this method. This context is required when calling the runtime so a standard pattern is to save a reference to in this method. Just before the application shuts down, the [OnShutdown](reference/options.mdx#onshutdown) callback is called in the same way, again with the context. There is also an [OnDomReady](reference/options.mdx#ondomready) callback for when the frontend has completed loading all assets in `index.html` and is equivalent of the [`body onload`](https://www.w3schools.com/jsref/event_onload.asp) event in Javascript. It is also possible to hook into the window close (or application quit) event by setting the option [OnBeforeClose](reference/options.mdx#onbeforeclose).
-
-#### Method Binding
-
-The `Bind` option is one of the most important options in a Wails application. It specifies which struct methods to expose to the frontend. Think of structs like "controllers" in a traditional web application. When the application starts, it examines the struct instances listed in the `Bind` field in the options, determines which methods are public (starts with an uppercase letter) and will generate Javascript versions of those methods that can be called by the frontend code.
-
-:::info Note
-
-Wails requires that you pass in an *instance* of the struct for it to bind it correctly
-
-:::
-
-In this example, we create a new `App` instance and then add this instance to the `Bind` option in `wails.Run`:
-
-```go {16,24} title="main.go"
-package main
-
-import (
- "embed"
- "log"
-
- "github.com/wailsapp/wails/v2"
- "github.com/wailsapp/wails/v2/pkg/options"
-)
-
-//go:embed frontend/dist
-var assets embed.FS
-
-func main() {
-
- app := &App{}
-
- err := wails.Run(&options.App{
- Title: "Basic Demo",
- Width: 1024,
- Height: 768,
- Assets: &assets,
- Bind: []interface{}{
- app,
- },
- })
- if err != nil {
- log.Fatal(err)
- }
-}
-
-
-type App struct {
- ctx context.Context
-}
-
-func (a *App) Greet(name string) string {
- return fmt.Sprintf("Hello %s!", name)
-}
-```
-
-You may bind as many structs as you like. Just make sure you create an instance of it and pass it in `Bind`:
-
-```go {8-10}
- //...
- err := wails.Run(&options.App{
- Title: "Basic Demo",
- Width: 1024,
- Height: 768,
- Assets: &assets,
- Bind: []interface{}{
- app,
- &mystruct1{},
- &mystruct2{},
- },
- })
-
-```
-
-When you run `wails dev` (or `wails generate module`), a frontend module will be generated containing the following:
-
-- Javascript bindings for all bound methods
-- Typescript declarations for all bound methods
-- Typescript definitions for all Go structs used as inputs or outputs by the bound methods
-
-This makes it incredibly simple to call Go code from the frontend, using the same strongly typed datastructures.
-
-## The Frontend
-
-### Overview
-
-The frontend is a collection of files rendered by webkit. It's like a browser and webserver in one. There is virtually[^1] no limit to which frameworks or libraries you can use. The main points of interaction between the frontend and your Go code are:
-
-- Calling bound Go methods
-- Calling runtime methods
-
-### Calling bound Go methods
-
-When you run your application with `wails dev`, it will automatically generate Javascript bindings for your structs in a directory called `wailsjs/go` (You can also do this by running `wails generate module`). The generated files mirror the package names in your application. In the example above, we bind `app`, which has one public method `Greet`. This will lead to the generation of the following files:
-
-```bash
-wailsjs
- └─go
- └─main
- ├─App.d.ts
- └─App.js
-```
-
-Here we can see that there is a `main` package that contains the Javascript bindings for the bound `App` struct, as well as the Typescript declaration file for those methods. To call `Greet` from our frontend, we simply import the method and call it like a regular Javascript function:
-
-```javascript
-// ...
-import {Greet} from '../wailsjs/go/main/App'
-
- function doGreeting(name) {
- Greet(name).then((result) => {
- // Do something with result
- })
- }
-```
-
-The Typescript declaration file gives you the correct types for the bound methods:
-
-```ts
-export function Greet(arg1:string):Promise;
-```
-
-The generated methods return a Promise. A successful call will result in the first return value from the Go call to be passed to the `resolve` handler. An unsuccessful call is when a Go method that has an error type as it's second return value, passes an error instance back to the caller. This is passed back via the `reject` handler. In the example above, `Greet` only returns a `string` so the Javascript call will never reject - unless invalid data is passed to it.
-
-All data types are correctly translated between Go and Javascript. Even structs. If you return a struct from a Go call, it will be returned to your frontend as a Javascript class. Note: If you wish to use structs, you **must** define `json` struct tags for your fields!
-
-:::info Note
-Anonymous nested structs are not supported at this time.
-:::
-
-It is possible to send structs back to Go. Any Javascript map/class passed as an argument that is expecting a struct, will be converted to that struct type. To make this process a lot easier, in `dev` mode, a TypeScript module is generated, defining all the struct types used in bound methods. Using this module, it's possible to construct and send native Javascript objects to the Go code.
-
-There is also support for Go methods that use structs in their signature. All Go structs specified by a bound method (either as parameters or return types) will have Typescript versions auto generated as part of the Go code wrapper module. Using these, it's possible to share the same data model between Go and Javascript.
-
-Example: We update our `Greet` method to accept a `Person` instead of a string:
-
-```go title="main.go"
-type Person struct {
- Name string `json:"name"`
- Age uint8 `json:"age"`
- Address *Address `json:"address"`
-}
-
-type Address struct {
- Street string `json:"street"`
- Postcode string `json:"postcode"`
-}
-
-func (a *App) Greet(p Person) string {
- return fmt.Sprintf("Hello %s (Age: %d)!", p.Name, p.Age)
-}
-```
-
-The `wailsjs/go/main/App.js` file will still have the following code:
-
-```js title="App.js"
-export function Greet(arg1) {
- return window['go']['main']['App']['Greet'](arg1);
-}
-```
-
-But the `wailsjs/go/main/App.d.ts` file will be updated with the following code:
-
-```ts title="App.d.ts"
-import {main} from '../models';
-
-export function Greet(arg1:main.Person):Promise;
-```
-
-As we can see, the "main" namespace is imported from a new "models.ts" file. This file contains all the struct definitions used by our bound methods. In this example, this is a `Person` struct. If we look at `models.ts`, we can see how the models are defined:
-
-```ts title="models.ts"
-export namespace main {
-
- export class Address {
- street: string;
- postcode: string;
-
- static createFrom(source: any = {}) {
- return new Address(source);
- }
-
- constructor(source: any = {}) {
- if ('string' === typeof source) source = JSON.parse(source);
- this.street = source["street"];
- this.postcode = source["postcode"];
- }
- }
- export class Person {
- name: string;
- age: number;
- address?: Address;
-
- static createFrom(source: any = {}) {
- return new Person(source);
- }
-
- constructor(source: any = {}) {
- if ('string' === typeof source) source = JSON.parse(source);
- this.name = source["name"];
- this.age = source["age"];
- this.address = this.convertValues(source["address"], Address);
- }
-
- convertValues(a: any, classs: any, asMap: boolean = false): any {
- if (!a) {
- return a;
- }
- if (a.slice) {
- return (a as any[]).map(elem => this.convertValues(elem, classs));
- } else if ("object" === typeof a) {
- if (asMap) {
- for (const key of Object.keys(a)) {
- a[key] = new classs(a[key]);
- }
- return a;
- }
- return new classs(a);
- }
- return a;
- }
- }
-}
-```
-
-So long as you have TypeScript as part of your frontend build configuration, you can use these models in the following way:
-
-```js title="mycode.js"
-import {Greet} from '../wailsjs/go/main/App'
- import {main} from '../wailsjs/go/models'
-
- function generate() {
- let person = new main.Person()
- person.name = "Peter"
- person.age = 27
- Greet(person).then((result) => {
- console.log(result)
- })
- }
-```
-
-The combination of generated bindings and TypeScript models makes for a powerful development environment.
-
-More information on Binding can be found in the [Binding Methods](guides/application-development.mdx#binding-methods) section of the [Application Development Guide](guides/application-development.mdx).
-
-### Calling runtime methods
-
-The Javascript runtime is located at `window.runtime` and contains many methods to do various tasks such as emit an event or perform logging operations:
-
-```js title="mycode.js"
-window.runtime.EventsEmit("my-event", 1);
-```
-
-More details about the JS runtime can be found in the [Runtime Reference](reference/runtime/intro).
-
-[^1]: There is a very small subset of libraries that use features unsupported in WebViews. There are often alternatives and workarounds for such cases.
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/introduction.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/introduction.mdx
deleted file mode 100644
index 5a832a69e..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/introduction.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-sidebar_position: 1
----
-
-# Введение
-
-Wails - это проект, позволяющий писать настольные приложения с использованием Go и web технологий.
-
-Считайте, что это легкая и быстрая альтернатива Electron для Go. Вы можете легко создавать приложения с гибкостью и мощностью Go, в сочетании с богатым современным фронтендом.
-
-### Features
-
-- Native Menus, Dialogs, Theming and Translucency
-- Windows, macOS and linux support
-- Built in templates for Svelte, React, Preact, Vue, Lit and Vanilla JS
-- Easily call Go methods from Javascript
-- Automatic Go struct to Typescript model generation
-- No CGO or external DLLs required on Windows
-- Live development mode using the power of [Vite](https://vite.net/)
-- Powerful CLI to easily Create, Build and Package applications
-- A rich [runtime library](/docs/next/reference/runtime)
-- Applications built with Wails are Apple & Microsoft Store compliant
-
-
-Например, [varly](https://varly.app) - настольное приложение для MacOS & Windows, написанное с помощью Wails. Оно не только великолепно выглядит, но и использует системные меню и полупрозрачность - все, что можно ожидать от современного нативного приложения.
-
-
-
-
-
-When clicked, that will open an about message box:
-
-
-
-
-
-
-
-## Linux Specific Options
-
-### Icon
-
-Sets up the icon representing the window. This icon is used when the window is minimized (also known as iconified).
-
-Type: []byte
-
-Some window managers or desktop environments may also place it in the window frame, or display it in other contexts. On others, the icon is not used at all, so your mileage may vary.
-
-NOTE: Gnome on Wayland at least does not display this icon. To have a application icon there, a `.desktop` file has to be used. On KDE it should work.
-
-The icon should be provided in whatever size it was naturally drawn; that is, don’t scale the image before passing it. Scaling is postponed until the last minute, when the desired final size is known, to allow best quality.
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/project-config.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/project-config.mdx
deleted file mode 100644
index 3dc1cf002..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/project-config.mdx
+++ /dev/null
@@ -1,51 +0,0 @@
----
-sidebar_position: 5
----
-
-# Project Config
-
-The project config resides in the `wails.json` file in the project directory. The structure of the config is:
-
-```json
-{
- "name": "[The project name]",
- "assetdir": "[Relative path to the directory containing the compiled assets, this is normally inferred and could be left empty]",
- "reloaddirs": "[Additional directories to trigger reloads (comma separated), this is only used for some advanced asset configurations]",
- "frontend:install": "[The command to install node dependencies, run in the frontend directory - often `npm install`]",
- "frontend:build": "[The command to build the assets, run in the frontend directory - often `npm run build`]",
- "frontend:dev": "[This command has been replaced by frontend:dev:build. If frontend:dev:build is not specified will falls back to this command. If this command is also not specified will falls back to frontend:build]",
- "frontend:dev:build": "[This command is the dev equivalent of frontend:build. If not specified falls back to frontend:dev]",
- "frontend:dev:install": "[This command is the dev equivalent of frontend:install. If not specified falls back to frontend:install]",
- "frontend:dev:watcher": "[This command is run in a separate process on `wails dev`. Useful for 3rd party watchers or starting 3d party dev servers]",
- "frontend:dev:serverUrl": "[URL to a 3rd party dev server to be used to serve assets, EG Vite. If this is set to 'auto' then the devServerUrl will be inferred from the Vite output]",
- "wailsjsdir": "[Relative path to the directory that the auto-generated JS modules will be created]",
- "version": "[Project config version]",
- "outputfilename": "[The name of the binary]",
- "debounceMS": 100, // The default time the dev server waits to reload when it detects a change in assets
- "devServer": "[Address to bind the wails dev sever to. Default: localhost:34115]",
- "appargs": "[Arguments passed to the application in shell style when in dev mode]",
- "runNonNativeBuildHooks": false, // Defines if build hooks should be run though they are defined for an OS other than the host OS.
- "preBuildHooks": {
- "GOOS/GOARCH": "[The command that will be executed before a build of the specified GOOS/GOARCH: ${platform} is replaced with the "GOOS/GOARCH". The "GOOS/GOARCH" hook is executed before the "GOOS/*" and "*/*" hook.]",
- "GOOS/*": "[The command that will be executed before a build of the specified GOOS: ${platform} is replaced with the "GOOS/GOARCH". The "GOOS/*" hook is executed before the "*/*" hook.]",
- "*/*": "[The command that will be executed before every build: ${platform} is replaced with the "GOOS/GOARCH".]"
- },
- "postBuildHooks": {
- "GOOS/GOARCH": "[The command that will be executed after a build of the specified GOOS/GOARCH: ${platform} is replaced with the "GOOS/GOARCH" and ${bin} with the path to the compiled binary. The "GOOS/GOARCH" hook is executed before the "GOOS/*" and "*/*" hook.]",
- "GOOS/*": "[The command that will be executed after a build of the specified GOOS: ${platform} is replaced with the "GOOS/GOARCH" and ${bin} with the path to the compiled binary. The "GOOS/*" hook is executed before the "*/*" hook.]",
- "*/*": "[The command that will be executed after every build: ${platform} is replaced with the "GOOS/GOARCH" and ${bin} with the path to the compiled binary.]"
- },
- "info": { // Data used to populate manifests and version info.
- "companyName": "[The company name. Default: [The project name]]",
- "productName": "[The product name. Default: [The project name]]",
- "productVersion": "[The version of the product. Default: '1.0.0']",
- "copyright": "[The copyright of the product. Default: 'Copyright.........']",
- "comments": "[A short comment of the app. Default: 'Built using Wails (https://wails.app)']"
- },
- "nsisType": "['multiple': One installer per architecture. 'single': Single universal installer for all architectures being built. Default: 'multiple']"
-}
-```
-
-This file is read by the Wails CLI when running `wails build` or `wails dev`.
-
-The `assetdir`, `reloaddirs`, `wailsjsdir`, `debounceMS`, `devserver` and `frontenddevserverurl` flags in `wails build/dev` will update the project config and thus become defaults for subsequent runs.
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/_category_.json b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/_category_.json
deleted file mode 100644
index ac6d55488..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Runtime",
- "position": 1
-}
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/browser.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/browser.mdx
deleted file mode 100644
index 976ca1d80..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/browser.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
----
-sidebar_position: 7
----
-
-# Browser
-
-These methods are related to the system browser.
-
-### BrowserOpenURL
-
-Opens the given URL in the system browser.
-
-Go: `BrowserOpenURL(ctx context.Context, url string)` JS: `BrowserOpenURL(url string)`
-
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/dialog.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/dialog.mdx
deleted file mode 100644
index bf1dd7246..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/dialog.mdx
+++ /dev/null
@@ -1,283 +0,0 @@
----
-sidebar_position: 5
----
-
-# Dialog
-
-This part of the runtime provides access to native dialogs, such as File Selectors and Message boxes.
-
-:::info Javascript
- Dialog is currently unsupported in the JS runtime.
-:::
-
-### OpenDirectoryDialog
-
-Opens a dialog that prompts the user to select a directory. Can be customised using [OpenDialogOptions](#opendialogoptions).
-
-Go: `OpenDirectoryDialog(ctx context.Context, dialogOptions OpenDialogOptions) (string, error)`
-
-Returns: Selected directory (blank if the user cancelled) or an error
-
-### OpenFileDialog
-
-Opens a dialog that prompts the user to select a file. Can be customised using [OpenDialogOptions](#opendialogoptions).
-
-Go: `OpenFileDialog(ctx context.Context, dialogOptions OpenDialogOptions) (string, error)`
-
-Returns: Selected file (blank if the user cancelled) or an error
-
-### OpenMultipleFilesDialog
-
-Opens a dialog that prompts the user to select multiple files. Can be customised using [OpenDialogOptions](#opendialogoptions).
-
-Go: `OpenMultipleFilesDialog(ctx context.Context, dialogOptions OpenDialogOptions) ([]string, error)`
-
-Returns: Selected files (nil if the user cancelled) or an error
-
-### SaveFileDialog
-
-Opens a dialog that prompts the user to select a filename for the purposes of saving. Can be customised using [SaveDialogOptions](#savedialogoptions).
-
-Go: `SaveFileDialog(ctx context.Context, dialogOptions SaveDialogOptions) (string, error)`
-
-Returns: The selected file (blank if the user cancelled) or an error
-
-### MessageDialog
-
-Displays a message using a message dialog. Can be customised using [MessageDialogOptions](#messagedialogoptions).
-
-Go: `MessageDialog(ctx context.Context, dialogOptions MessageDialogOptions) (string, error)`
-
-Returns: The text of the selected button or an error
-
-## Options
-
-### OpenDialogOptions
-
-```go
-type OpenDialogOptions struct {
- DefaultDirectory string
- DefaultFilename string
- Title string
- Filters []FileFilter
- ShowHiddenFiles bool
- CanCreateDirectories bool
- ResolvesAliases bool
- TreatPackagesAsDirectories bool
-}
-```
-
-| Field | Description | Win | Mac | Lin |
-| -------------------------- | ---------------------------------------------- | --- | --- | --- |
-| DefaultDirectory | The directory the dialog will show when opened | ✅ | ✅ | ✅ |
-| DefaultFilename | The default filename | ✅ | ✅ | ✅ |
-| Title | Title for the dialog | ✅ | ✅ | ✅ |
-| [Filters](#filefilter) | A list of file filters | ✅ | ✅ | ✅ |
-| ShowHiddenFiles | Show files hidden by the system | | ✅ | ✅ |
-| CanCreateDirectories | Allow user to create directories | | ✅ | |
-| ResolvesAliases | If true, returns the file not the alias | | ✅ | |
-| TreatPackagesAsDirectories | Allow navigating into packages | | ✅ | |
-
-### SaveDialogOptions
-
-```go
-type SaveDialogOptions struct {
- DefaultDirectory string
- DefaultFilename string
- Title string
- Filters []FileFilter
- ShowHiddenFiles bool
- CanCreateDirectories bool
- TreatPackagesAsDirectories bool
-}
-```
-
-| Field | Description | Win | Mac | Lin |
-| -------------------------- | ---------------------------------------------- | --- | --- | --- |
-| DefaultDirectory | The directory the dialog will show when opened | ✅ | ✅ | ✅ |
-| DefaultFilename | The default filename | ✅ | ✅ | ✅ |
-| Title | Title for the dialog | ✅ | ✅ | ✅ |
-| [Filters](#filefilter) | A list of file filters | ✅ | ✅ | ✅ |
-| ShowHiddenFiles | Show files hidden by the system | | ✅ | ✅ |
-| CanCreateDirectories | Allow user to create directories | | ✅ | |
-| TreatPackagesAsDirectories | Allow navigating into packages | | ✅ | |
-
-### MessageDialogOptions
-
-```go
-type MessageDialogOptions struct {
- Type DialogType
- Title string
- Message string
- Buttons []string
- DefaultButton string
- CancelButton string
-}
-```
-
-| Field | Description | Win | Mac | Lin |
-| ------------- | ------------------------------------------------------------------------- | --- | --- | --- |
-| Type | The type of message dialog, eg question, info... | ✅ | ✅ | ✅ |
-| Title | Title for the dialog | ✅ | ✅ | ✅ |
-| Message | The message to show the user | ✅ | ✅ | ✅ |
-| Buttons | A list of button titles | | ✅ | |
-| DefaultButton | The button with this text should be treated as default. Bound to `return` | | ✅ | |
-| CancelButton | The button with this text should be treated as cancel. Bound to `escape` | | ✅ | |
-
-#### Windows
-
-Windows has standard dialog types in which the buttons are not customisable. The value returned will be one of: "Ok", "Cancel", "Abort", "Retry", "Ignore", "Yes", "No", "Try Again" or "Continue"
-
-#### Linux
-
-Linux has standard dialog types in which the buttons are not customisable. The value returned will be one of: "Ok", "Cancel", "Yes", "No"
-
-#### Mac
-
-A message dialog on Mac may specify up to 4 buttons. If no `DefaultButton` or `CancelButton` is given, the first button is considered default and is bound to the `return` key.
-
-For the following code:
-
-```go
-selection, err := runtime.MessageDialog(b.ctx, runtime.MessageDialogOptions{
- Title: "It's your turn!",
- Message: "Select a number",
- Buttons: []string{"one", "two", "three", "four"},
-})
-```
-
-the first button is shown as default:
-
-
-
-
-
-
-
-And if we specify `DefaultButton` to be "two":
-
-```go
-selection, err := runtime.MessageDialog(b.ctx, runtime.MessageDialogOptions{
- Title: "It's your turn!",
- Message: "Select a number",
- Buttons: []string{"one", "two", "three", "four"},
- DefaultButton: "two",
-})
-```
-
-the second button is shown as default. When `return` is pressed, the value "two" is returned.
-
-
-
-
-
-
-
-If we now specify `CancelButton` to be "three":
-
-```go
-selection, err := runtime.MessageDialog(b.ctx, runtime.MessageDialogOptions{
- Title: "It's your turn!",
- Message: "Select a number",
- Buttons: []string{"one", "two", "three", "four"},
- DefaultButton: "two",
- CancelButton: "three",
-})
-```
-
-the button with "three" is shown at the bottom of the dialog. When `escape` is pressed, the value "three" is returned:
-
-
-
-
-
-
-
-
-
-#### DialogType
-
-```go
-const (
- InfoDialog DialogType = "info"
- WarningDialog DialogType = "warning"
- ErrorDialog DialogType = "error"
- QuestionDialog DialogType = "question"
- )
-```
-
-### FileFilter
-
-```go
-type FileFilter struct {
- DisplayName string // Filter information EG: "Image Files (*.jpg, *.png)"
- Pattern string // semi-colon separated list of extensions, EG: "*.jpg;*.png"
-}
-```
-
-#### Windows
-
-Windows allows you to use multiple file filters in dialog boxes. Each FileFilter will show up as a separate entry in the dialog:
-
-
-
-
-
-
-
-
-
-#### Linux
-
-Linux allows you to use multiple file filters in dialog boxes. Each FileFilter will show up as a separate entry in the dialog:
-
-
-
-
-
-
-
-
-
-#### Mac
-
-Mac dialogs only have the concept of a single set of patterns to filter files. If multiple FileFilters are provided, Wails will use all the Patterns defined.
-
-Example:
-
-```go
- selection, err := runtime.OpenFileDialog(b.ctx, runtime.OpenDialogOptions{
- Title: "Select File",
- Filters: []runtime.FileFilter{
- {
- DisplayName: "Images (*.png;*.jpg)",
- Pattern: "*.png;*.jpg",
- }, {
- DisplayName: "Videos (*.mov;*.mp4)",
- Pattern: "*.mov;*.mp4",
- },
- },
- })
-```
-
-This will result in the Open File dialog using `*.png,*.jpg,*.mov,*.mp4` as a filter.
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/events.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/events.mdx
deleted file mode 100644
index 75e8b0a50..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/events.mdx
+++ /dev/null
@@ -1,38 +0,0 @@
----
-sidebar_position: 2
----
-
-# Events
-
-The Wails runtime provides a unified events system, where events can be emitted or received by either Go or Javascript. Optionally, data may be passed with the events. Listeners will receive the data in the local data types.
-
-### EventsOn
-
-This method sets up a listener for the given event name. When an event of type `eventName` is [emitted](#EventsEmit), the callback is triggered. Any additional data sent with the emitted event will be passed to the callback.
-
-Go: `EventsOn(ctx context.Context, eventName string, callback func(optionalData ...interface{}))` JS: `EventsOn(eventName string, callback function(optionalData?: any))`
-
-### EventsOff
-
-This method unregisters the listener for the given event name, optionally multiple listeneres can be unregistered via `additionalEventNames`.
-
-Go: `EventsOff(ctx context.Context, eventName string, additionalEventNames ...string)` JS: `EventsOff(eventName string, ...additionalEventNames)`
-
-### EventsOnce
-
-This method sets up a listener for the given event name, but will only trigger once.
-
-Go: `EventsOnce(ctx context.Context, eventName string, callback func(optionalData ...interface{}))` JS: `EventsOnce(eventName string, callback function(optionalData?: any))`
-
-### EventsOnMultiple
-
-This method sets up a listener for the given event name, but will only trigger a maximum of `counter` times.
-
-Go: `EventsOnMultiple(ctx context.Context, eventName string, callback func(optionalData ...interface{}), counter int)` JS: `EventsOnMultiple(eventName string, callback function(optionalData?: any), counter int)`
-
-### EventsEmit
-
-This method emits the given event. Optional data may be passed with the event. This will trigger any event listeners.
-
-Go: `EventsEmit(ctx context.Context, eventName string, optionalData ...interface{})` JS: `EventsEmit(ctx context, optionalData function(optionalData?: any))`
-
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/intro.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/intro.mdx
deleted file mode 100644
index 6c02c71cd..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/intro.mdx
+++ /dev/null
@@ -1,73 +0,0 @@
----
-sidebar_position: 1
----
-
-# Introduction
-
-The runtime is a library that provides utility methods for your application. There is both a Go and Javascript runtime and the aim is to try and keep them at parity where possible.
-
-It has utility methods for:
-
-- [Window](window.mdx)
-- [Menu](menu.mdx)
-- [Dialog](dialog.mdx)
-- [Events](events.mdx)
-- [Browser](browser.mdx)
-- [Log](log.mdx)
-
-The Go Runtime is available through importing `github.com/wailsapp/wails/v2/pkg/runtime`. All methods in this package take a context as the first parameter. This context should be obtained from the [OnStartup](../options.mdx#onstartup) or [OnDomReady](../options.mdx#ondomready) hooks.
-
-:::info Note
-
-Whilst the context will be provided to the [OnStartup](../options.mdx#onstartup) method, there's no guarantee the runtime will work in this method as the window is initialising in a different thread. If you wish to call runtime methods at startup, use [OnDomReady](../options.mdx#ondomready).
-
-:::
-
-The Javascript library is available to the frontend via the `window.runtime` map. There is a runtime package generated when using `dev` mode that provides Typescript declarations for the runtime. This should be located in the `wailsjs` directory in your frontend directory.
-
-### Hide
-
-Go: `Hide(ctx context.Context)` JS: `Hide()`
-
-Hides the application.
-
-:::info Note On Mac, this will hide the application in the same way as the `Hide` menu item in standard Mac applications. This is different to hiding the window, but the application still being in the foreground. For Windows and Linux, this is currently the same as `WindowHide`. :::
-
-### Show
-
-Shows the application.
-
-:::info Note On Mac, this will bring the application back into the foreground. For Windows and Linux, this is currently the same as `WindowShow`. :::
-
-Go: `Show(ctx context.Context)` JS: `Show()`
-
-### Quit
-
-Quits the application.
-
-Go: `Quit(ctx context.Context)` JS: `Quit()`
-
-### Environment
-
-Returns details of the current environment.
-
-Go: `Environment(ctx context.Context) EnvironmentInfo` JS: `Environment(): Promise`
-
-#### EnvironmentInfo
-
-Go:
-```go
-type EnvironmentInfo struct {
- BuildType string
- Platform string
- Arch string
-}
-```
-JS:
-```ts
-interface EnvironmentInfo {
- buildType: string;
- platform: string;
- arch: string;
-}
-```
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/log.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/log.mdx
deleted file mode 100644
index e5e6ea7ac..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/log.mdx
+++ /dev/null
@@ -1,130 +0,0 @@
----
-sidebar_position: 3
----
-
-# Log
-
-The Wails runtime provides a logging mechanism that may be called from Go or Javascript. Like most loggers, there are a number of log levels:
-
-- Trace
-- Debug
-- Info
-- Warning
-- Error
-- Fatal
-
-The logger will output any log message at the current, or higher, log level. Example: The `Debug` log level will output all messages except `Trace` messages.
-
-### LogPrint
-
-Logs the given message as a raw message.
-
-Go: `LogPrint(ctx context.Context, message string)` JS: `LogPrint(message: string)`
-
-### LogPrintf
-
-Logs the given message as a raw message.
-
-Go: `LogPrintf(ctx context.Context, format string, args ...interface{})`
-
-### LogTrace
-
-Logs the given message at the `Trace` log level.
-
-Go: `LogTrace(ctx context.Context, message string)` JS: `LogTrace(message: string)`
-
-### LogTracef
-
-Logs the given message at the `Trace` log level.
-
-Go: `LogTracef(ctx context.Context, format string, args ...interface{})`
-
-### LogDebug
-
-Logs the given message at the `Debug` log level.
-
-Go: `LogDebug(ctx context.Context, message string)` JS: `LogDebug(message: string)`
-
-### LogDebugf
-
-Logs the given message at the `Debug` log level.
-
-Go: `LogDebugf(ctx context.Context, format string, args ...interface{})`
-
-### LogInfo
-
-Logs the given message at the `Info` log level.
-
-Go: `LogInfo(ctx context.Context, message string)` JS: `LogInfo(message: string)`
-
-### LogInfof
-
-Logs the given message at the `Info` log level.
-
-Go: `LogInfof(ctx context.Context, format string, args ...interface{})`
-
-### LogWarning
-
-Logs the given message at the `Warning` log level.
-
-Go: `LogWarning(ctx context.Context, message string)` JS: `LogWarning(message: string)`
-
-### LogWarningf
-
-Logs the given message at the `Warning` log level.
-
-Go: `LogWarningf(ctx context.Context, format string, args ...interface{})`
-
-### LogError
-
-Logs the given message at the `Error` log level.
-
-Go: `LogError(ctx context.Context, message string)` JS: `LogError(message: string)`
-
-### LogErrorf
-
-Logs the given message at the `Error` log level.
-
-Go: `LogErrorf(ctx context.Context, format string, args ...interface{})`
-
-### LogFatal
-
-Logs the given message at the `Fatal` log level.
-
-Go: `LogFatal(ctx context.Context, message string)` JS: `LogFatal(message: string)`
-
-### LogFatalf
-
-Logs the given message at the `Fatal` log level.
-
-Go: `LogFatalf(ctx context.Context, format string, args ...interface{})`
-
-### LogSetLogLevel
-
-Sets the log level. In Javascript, the number relates to the following log levels:
-
-| Value | Log Level |
-| ----- | --------- |
-| 1 | Trace |
-| 2 | Debug |
-| 3 | Info |
-| 4 | Warning |
-| 5 | Error |
-
-Go: `LogSetLogLevel(ctx context.Context, level logger.LogLevel)` JS: `LogSetLogLevel(level: number)`
-
-## Using a Custom Logger
-
-A custom logger may be used by providing it using the [Logger](../options.mdx#logger) application option. The only requirement is that the logger implements the `logger.Logger` interface defined in `github.com/wailsapp/wails/v2/pkg/logger`:
-
-```go title="logger.go"
-type Logger interface {
- Print(message string)
- Trace(message string)
- Debug(message string)
- Info(message string)
- Warning(message string)
- Error(message string)
- Fatal(message string)
-}
-```
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/menu.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/menu.mdx
deleted file mode 100644
index 226ff2c68..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/menu.mdx
+++ /dev/null
@@ -1,23 +0,0 @@
----
-sidebar_position: 6
----
-
-# Menu
-
-These methods are related to the application menu.
-
-:::info Javascript
- Menu is currently unsupported in the JS runtime.
-:::
-
-### MenuSetApplicationMenu
-
-Sets the application menu to the given [menu](../menus.mdx).
-
-Go: `MenuSetApplicationMenu(ctx context.Context, menu *menu.Menu)`
-
-### MenuUpdateApplicationMenu
-
-Updates the application menu, picking up any changes to the menu passed to `MenuSetApplicationMenu`.
-
-Go: `MenuUpdateApplicationMenu(ctx context.Context)`
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/window.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/window.mdx
deleted file mode 100644
index 3316a45f9..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/window.mdx
+++ /dev/null
@@ -1,211 +0,0 @@
----
-sidebar_position: 4
----
-
-# Window
-
-These methods give control of the application window.
-
-### WindowSetTitle
-
-Sets the text in the window title bar.
-
-Go: `WindowSetTitle(ctx context.Context, title string)` JS: `WindowSetTitle(title: string)`
-
-### WindowFullscreen
-
-Makes the window full screen.
-
-Go: `WindowFullscreen(ctx context.Context)` JS: `WindowFullscreen()`
-
-### WindowUnfullscreen
-
-Restores the previous window dimensions and position prior to full screen.
-
-Go: `WindowUnfullscreen(ctx context.Context)` JS: `WindowUnfullscreen()`
-
-### WindowIsFullscreen
-
-Returns true if the window is full screen.
-
-Go: `WindowCenter(ctx context.Context)` JS: `WindowCenter()`
-
-### WindowCenter
-
-Centers the window on the monitor the window is currently on.
-
-Go: `WindowReload(ctx context.Context)` JS: `WindowReload()`
-
-### WindowReload
-
-Performs a "reload" (Reloads current page).
-
-Go: `WindowReloadApp(ctx context.Context)` JS: `WindowReloadApp()`
-
-### WindowReloadApp
-
-Reloads the application frontend.
-
-Go: `WindowSetSystemDefaultTheme(ctx context.Context)` JS: `WindowSetSystemDefaultTheme()`
-
-### WindowSetSystemDefaultTheme
-
-Windows only.
-
-Go: `WindowSetDarkTheme(ctx context.Context)` JS: `WindowSetDarkTheme()`
-
-Sets window theme to system default (dark/light).
-
-### WindowSetLightTheme
-
-Windows only.
-
-Go: `WindowSetLightTheme(ctx context.Context)` JS: `WindowSetLightTheme()`
-
-Sets window theme to light.
-
-### WindowSetDarkTheme
-
-Windows only.
-
-Go: `WindowShow(ctx context.Context)` JS: `WindowShow()`
-
-Sets window theme to dark.
-
-### WindowShow
-
-Shows the window, if it is currently hidden.
-
-Go: `WindowHide(ctx context.Context)` JS: `WindowHide()`
-
-### WindowHide
-
-Hides the window, if it is currently visible.
-
-Go: `WindowSetSize(ctx context.Context, width int, height int)` JS: `WindowSetSize(size: Size)`
-
-### WindowIsNormal
-
-Returns true if the window not minimised, maximised or fullscreen.
-
-Go: `WindowGetSize(ctx context.Context) (width int, height int)` JS: `WindowGetSize() : Size`
-
-### WindowSetSize
-
-Sets the width and height of the window.
-
-Go: `WindowSetMaxSize(ctx context.Context, width int, height int)` JS: `WindowSetMaxSize(size: Size)`
-
-### WindowGetSize
-
-Gets the width and height of the window.
-
-Go: `WindowSetMinSize(ctx context.Context, width int, height int)` JS: `WindowSetMinSize(size: Size)`
-
-### WindowSetMinSize
-
-Sets the minimum window size. Will resize the window if the window is currently smaller than the given dimensions.
-
-Setting a size of `0,0` will disable this constraint.
-
-Go: `WindowSetAlwaysOnTop(ctx context.Context, b bool)` JS: `WindowSetAlwaysOnTop(b: Boolen)`
-
-### WindowSetMaxSize
-
-Sets the maximum window size. Will resize the window if the window is currently larger than the given dimensions.
-
-Setting a size of `0,0` will disable this constraint.
-
-Go: `WindowSetPosition(ctx context.Context, x int, y int)` JS: `WindowSetPosition(position: Position)`
-
-### WindowSetAlwaysOnTop
-
-Sets the window AlwaysOnTop or not on top.
-
-Go: `WindowGetPosition(ctx context.Context) (x int, y int)` JS: `WindowGetPosition() : Position`
-
-### WindowSetPosition
-
-Sets the window position relative to the monitor the window is currently on.
-
-Go: `WindowMaximise(ctx context.Context)` JS: `WindowMaximise()`
-
-### WindowGetPosition
-
-Gets the window position relative to the monitor the window is currently on.
-
-Go: `WindowUnmaximise(ctx context.Context)` JS: `WindowUnmaximise()`
-
-### WindowMaximise
-
-Maximises the window to fill the screen.
-
-Go: `WindowToggleMaximise(ctx context.Context)` JS: `WindowToggleMaximise()`
-
-### WindowUnmaximise
-
-Restores the window to the dimensions and position prior to maximising.
-
-Go: `WindowMinimise(ctx context.Context)` JS: `WindowMinimise()`
-
-### WindowIsMaximised
-
-Returns true if the window is maximised.
-
-Go: `WindowUnminimise(ctx context.Context)` JS: `WindowUnminimise()`
-
-### WindowToggleMaximise
-
-Toggles between Maximised and UnMaximised.
-
-Go: `WindowToggleMaximise(ctx context.Context)` JS: `WindowToggleMaximise()`
-
-### WindowMinimise
-
-Minimises the window.
-
-Go: `WindowSetBackgroundColour(ctx context.Context, R, G, B, A uint8)` JS: `WindowSetBackgroundColour(R, G, B, A)`
-
-### WindowUnminimise
-
-Restores the window to the dimensions and position prior to minimising.
-
-Go: `WindowUnminimise(ctx context.Context)` JS: `WindowUnminimise()`
-
-### WindowIsMinimised
-
-Returns true if the window is minimised.
-
-Go: `WindowIsMinimised(ctx context.Context) bool` JS: `WindowIsMinimised() bool`
-
-### WindowSetBackgroundColour
-
-Sets the background colour of the window to the given RGBA colour definition. This colour will show through for all transparent pixels.
-
-Valid values for R, G, B and A are 0-255.
-
-Any value that is not 0 will be considered 255. :::info Windows
-On Windows, only alpha values of 0 or 255 are supported.
-:::
-
-Go: `WindowSetBackgroundColour(ctx context.Context, R, G, B, A uint8)` JS: `WindowSetBackgroundColour(R, G, B, A)`
-
-## Typescript Object Definitions
-
-### Position
-
-```ts
-interface Position {
- x: number;
- y: number;
-}
-```
-
-### Size
-
-```ts
-interface Size {
- w: number;
- h: number;
-}
-```
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/tutorials/_category_.json b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/tutorials/_category_.json
deleted file mode 100644
index dfac1d175..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/tutorials/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Tutorials",
- "position": 70
-}
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/tutorials/dogsapi.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/tutorials/dogsapi.mdx
deleted file mode 100644
index f4845fdbe..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/tutorials/dogsapi.mdx
+++ /dev/null
@@ -1,243 +0,0 @@
----
-sidebar_position: 20
----
-
-# Dogs API
-
-
-
-
-
-
-
-:::note This tutorial has been kindly provided by [@tatadan](https://twitter.com/tatadan) and forms part of their [Wails Examples Repository](https://github.com/tataDan/wails-v2-examples). :::
-
-In this tutorial we are going to develop an application that retrieves photos of dogs from the web and then displays them.
-
-### Create the project
-
-Let's create the application. From a terminal enter: `wails init -n dogs-api -t svelte`
-
-Note: We could optionally add `-ide vscode` or `-ide goland` to the end of this command if you wanted to add IDE support.
-
-Now let's `cd dogs-api` and start editing the project files.
-
-### Remove unused code
-
-We will start by removing some elements that we know we will not use:
-
-- Open `app.go` and remove the following lines:
-
-```go
-// Greet returns a greeting for the given name
-func (a *App) Greet(name string) string {
- return fmt.Sprintf("Hello %s, It's show time!", name)
-}
-```
-
-- Open `frontend/src/App.svelte` and delete all lines.
-- Delete the `frontend/src/assets/images/logo-universal.png` file
-
-### Creating our application
-
-Now let's add our new Go code.
-
-Add the following struct declarations to `app.go` before the function definitions:
-
-```go
-type RandomImage struct {
- Message string
- Status string
-}
-
-type AllBreeds struct {
- Message map[string]map[string][]string
- Status string
-}
-
-type ImagesByBreed struct {
- Message []string
- Status string
-}
-```
-
-Add the following functions to `app.go` (perhaps after the existing function definitions):
-
-```go
-func (a *App) GetRandomImageUrl() string {
- response, err := http.Get("https://dog.ceo/api/breeds/image/random")
- if err != nil {
- log.Fatal(err)
- }
-
- responseData, err := ioutil.ReadAll(response.Body)
- if err != nil {
- log.Fatal(err)
- }
-
- var data RandomImage
- json.Unmarshal(responseData, &data)
-
- return data.Message
-}
-
-func (a *App) GetBreedList() []string {
- var breeds []string
-
- response, err := http.Get("https://dog.ceo/api/breeds/list/all")
- if err != nil {
- log.Fatal(err)
- }
-
- responseData, err := ioutil.ReadAll(response.Body)
- if err != nil {
- log.Fatal(err)
- }
-
- var data AllBreeds
- json.Unmarshal(responseData, &data)
-
- for k := range data.Message {
- breeds = append(breeds, k)
- }
-
- sort.Strings(breeds)
-
- return breeds
-}
-
-func (a *App) GetImageUrlsByBreed(breed string) []string {
-
- url := fmt.Sprintf("%s%s%s%s", "https://dog.ceo/api/", "breed/", breed, "/images")
- response, err := http.Get(url)
- if err != nil {
- log.Fatal(err)
- }
-
- responseData, err := ioutil.ReadAll(response.Body)
- if err != nil {
- log.Fatal(err)
- }
-
- var data ImagesByBreed
- json.Unmarshal(responseData, &data)
-
- return data.Message
-}
-```
-
-Modify the `import` section of `app.go` to look like this:
-
-```go
-import (
- "context"
- "fmt"
- "encoding/json"
- "io/ioutil"
- "log"
- "net/http"
- "sort"
-)
-```
-
-Add the following lines to `frontend/src/App.svelte`:
-
-```html
-
-
-
Dogs API
-
-
- Click on down arrow to select a breed
-
-
-
-
-{#if showRandomPhoto}
-
-{/if}
-{#if showBreedPhotos}
- {#each photos as photo}
-
- {/each}
-{/if}
-
-
-```
-
-### Testing the application
-
-To generate the bindings and test the application, run `wails dev`.
-
-### Compiling the application
-
-To compile the application to a single, production grade binary, run `wails build`.
-
-
-
-
-
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/tutorials/helloworld.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/tutorials/helloworld.mdx
deleted file mode 100644
index ee2814292..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/tutorials/helloworld.mdx
+++ /dev/null
@@ -1,118 +0,0 @@
----
-sidebar_position: 10
----
-
-# Hello World
-
-Цель этого урока — запустить наиболее базовое приложение, использующее Wails. Вы сможете:
-
-- Создавать новое Wails приложение
-- Собирать приложение
-- Запускать приложение
-
-:::note
-В этом уроке в качестве целевой платформы используется Windows. Вывод будет варьироваться в
-зависимости от вашей операционной системы.
-:::
-
-## Создавать новое Wails приложение
-
-Чтобы создать новое Wails приложение, использующее стандартный шаблон JS, вам нужно выполнить следующую команду:
-
-```bash
-wails init -n helloworld
-```
-
-Вы должны увидеть что-то похожее на следующее:
-
-```
-Wails CLI v2.0.0
-
-Initialising Project 'helloworld'
----------------------------------
-
-Project Name: helloworld
-Project Directory: C:\Users\leaan\tutorial\helloworld
-Project Template: vanilla
-Template Support: https://wails.io
-
-Initialised project 'helloworld' in 232ms.
-```
-
-Это создаст новый каталог под названием `helloworld` в текущей директории. В этом каталоге вы найдете несколько файлов:
-
-```
-build/ - Содержит файлы сборки + собранное приложение
-frontend/ - Содержит файлы интерфейса
-app.go - Содержит код приложения
-main.go - Основная программа с настройками приложения
-wails.json - Файл настройки проекта
-go.mod - Файл модуля Go
-go.sum - Файл контрольной суммы модуля Go
-```
-
-## Собирать приложение
-
-Чтобы собрать приложение, перейдите в новую директорию `helloworld` и запустите следующую команду:
-
-```bash
-wails build
-```
-
-Вы должны увидеть что-то похожее на следующее:
-
-```
-Wails CLI v2.0.0
-
-App Type: desktop
-Platforms: windows/amd64
-Compiler: C:\Users\leaan\go\go1.18.3\bin\go.exe
-Build Mode: Production
-Skip Frontend: false
-Compress: false
-Package: true
-Clean Build Dir: false
-LDFlags: ""
-Tags: []
-Race Detector: false
-
-Building target: windows/amd64
-------------------------------
- - Installing frontend dependencies: Done.
- - Compiling frontend: Done.
- - Generating bundle assets: Done.
- - Compiling application: Done.
-Built 'C:\Users\leaan\tutorial\helloworld\build\bin\helloworld.exe' in 10.616s.
-```
-
-Приложение собрано и сохранено в папке `build/bin`.
-
-## Запускать приложение
-
-Если мы откроем папку `build/bin` в Проводнике, то увидим исполняемый файл проекта:
-
-
-
-
-
-
-
-Мы можем запустить его, просто дважды щелкнув по файлу `helloworld.exe`.
-
-На Mac, Wails генерирует файл `helloworld.app` который может быть запущен двойным щелчком.
-
-На Linux вы можете запустить приложение с помощью файла `./helloworld` из папки `build/bin`.
-
-Вы должны видеть приложение, работающее так, как ожидалось:
-
-
-```
-
-[EmailIt](https://github.com/raguay/EmailIt/) is a Wails 2 program that is a markdown based email sender only with nine notepads, scripts to manipulate the text, and templates. It also has a builtin [Node-Red](https://nodered.org/) server, scripts terminal, and the [ScriptBar](https://github.com/raguay/ScriptBarApp) program for displaying results from Node-Red or a script on your system. Documentation is very scarce, but the programs works. It’s built using Wails2 and Svelte, and the download is a universal macOS application.
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/frameless.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/frameless.mdx
deleted file mode 100644
index 3845736f4..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/frameless.mdx
+++ /dev/null
@@ -1,87 +0,0 @@
-# Frameless Applications
-
-Wails supports application that have no frames. This can be achieved by using the [frameless](../reference/options.mdx#frameless) field in [Application Options](../reference/options.mdx#application-options).
-
-Wails offers a simple solution for dragging the window: Any HTML element that has the CSS style `--wails-draggable:drag` will act as a "drag handle". This property applies to all child elements. If you need to indicate that a nested element should not drag, then use the attribute '--wails-draggable:no-drag' on that element.
-
-```html
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-```
-
-For some projects, using a CSS variable may not be possible due to dynamic styling. In this case, you can use the `CSSDragProperty` and `CSSDragValue` application options to define a property and value that will be used to indicate draggable regions:
-
-```go title=main.go
-package main
-
-import (
- "embed"
-
- "github.com/wailsapp/wails/v2"
- "github.com/wailsapp/wails/v2/pkg/options"
- "github.com/wailsapp/wails/v2/pkg/options/assetserver"
-)
-
-//go:embed all:frontend/dist
-var assets embed.FS
-
-func main() {
- // Create an instance of the app structure
- app := NewApp()
-
- // Create application with options
- err := wails.Run(&options.App{
- Title: "alwaysontop",
- Width: 1024,
- Height: 768,
- AssetServer: &assetserver.Options{
- Assets: assets,
- },
- Frameless: true,
- CSSDragProperty: "widows",
- CSSDragValue: "1",
- Bind: []interface{}{
- app,
- },
- })
-
- if err != nil {
- println("Error:", err)
- }
-}
-```
-
-```html title=index.html
-
-
-
-
-
- alwaysontop
-
-
-
-
-
-
-```
-
-:::info Fullscreen
-
-If you allow your application to go fullscreen, this drag functionality will be disabled.
-
-:::
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/frontend.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/frontend.mdx
deleted file mode 100644
index ac087ee45..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/frontend.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
-# Frontend
-
-## Script Injection
-
-When Wails serves your `index.html`, by default, it will inject 2 script entries into the `` tag to load `/wails/ipc.js` and `/wails/runtime.js`. These files install the bindings and runtime respectively.
-
-The code below shows where these are injected by default:
-
-```html
-
-
- injection example
-
-
-
-
-
-
-
-
Please enter your name below 👇
-
-
-
-
-
-
-
-
-```
-
-### Overriding Default Script Injection
-
-To provide more flexibility to developers, there is a meta tag that may be used to customise this behaviour:
-
-```html
-
-```
-
-The options are as follows:
-
-| Value | Description |
-| ------------------- | ------------------------------------------------ |
-| noautoinjectruntime | Disable the autoinjection of `/wails/runtime.js` |
-| noautoinjectipc | Disable the autoinjection of `/wails/ipc.js` |
-| noautoinject | Disable all autoinjection of scripts |
-
-Multiple options may be used provided they are comma seperated.
-
-This code is perfectly valid and operates the same as the autoinjection version:
-
-```html
-
-
- injection example
-
-
-
-
-
-
-
Please enter your name below 👇
-
-
-
-
-
-
-
-
-
-
-```
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/linux.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/linux.mdx
deleted file mode 100644
index 229c282bf..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/linux.mdx
+++ /dev/null
@@ -1,18 +0,0 @@
-# Linux
-
-This page has miscellaneous guides related to developing Wails applications for Linux.
-
-## Video tag doesn't fire "ended" event
-
-When using a video tag, the "ended" event is not fired when the video is finished playing. This is a bug in WebkitGTK, however you can use the following workaround to fix it:
-
-```js
-videoTag.addEventListener("timeupdate", (event) => {
- if (event.target.duration - event.target.currentTime < 0.2) {
- let ended = new Event("ended");
- event.target.dispatchEvent(ended);
- }
-});
-```
-
-Source: [Lyimmi](https://github.com/Lyimmi) on the [discussions board](https://github.com/wailsapp/wails/issues/1729#issuecomment-1212291275)
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/manual-builds.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/manual-builds.mdx
deleted file mode 100644
index dcf192d33..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/manual-builds.mdx
+++ /dev/null
@@ -1,95 +0,0 @@
-# Manual Builds
-
-The Wails CLI does a lot of heavy lifting for the project, but sometimes it's desirable to manually build your project. This document will discuss the different operations the CLI does and how this may be achieved in different ways.
-
-## Build Process
-
-When either `wails build` or `wails dev` are used, the Wails CLI performs a common build process:
-
- - Install frontend dependencies
- - Build frontend project
- - Generate build assets
- - Compile application
- - [optional] Compress application
-
-### Install frontend dependencies
-
-#### CLI Steps
-
-- If the `-s` flag is given, this step is skipped
-- Checks `wails.json` to see if there is an install command in the key `frontend:install`
-- If there isn't, it skips this step
-- If there is, it checks if `package.json` exists in the frontend directory. If it doesn't exist, it skips this step
-- An MD5 sum is generated from the `package.json` file contents
-- It checks for the existence of `package.json.md5` and if it exists, will compare the contents of it (an MD5 sum) with the one generated to see if the contents have changed. If they are the same, this step is skipped
-- If `package.json.md5` does not exist, it creates it using the generated MD5 sum
-- If a build is now required, or `node_modules` does not exist, or the `-f` flag is given, the install command is executed in the frontend directory
-
-#### Manual Steps
-
-This step could be done from the command line or a script with `npm install`.
-
-### Build frontend project
-
-#### Wails CLI
-
-- If the `-s` flag is given, this step is skipped
-- Checks `wails.json` to see if there is a build command in the key `frontend:build`
-- If there isn't, it skips this step
-- If there is, it is executed in the frontend directory
-
-#### Manual Steps
-
-This step could be done from the command line or a script with `npm run build` or whatever the frontend build script is.
-
-### Generate assets
-
-#### Wails CLI
-
-- If `-nopackage` flag is set, this stage is skipped
-- If the `build/appicon.png` file does not exist, a default one is created
-- For Windows, see [Bundling for Windows](#windows)
-- If `build/windows/icon.ico` does not exist, it will create it from the `build/appicon.png` image.
-
-##### Windows
-
-- If `build/windows/icon.ico` does not exist, it will create it from `build/appicon.png` using icon sizes of 256, 128, 64, 48, 32 and 16. This is done using [winicon](https://github.com/leaanthony/winicon).
-- If the `build/windows/.manifest` file does not exist, it creates it from a default version.
-- Compiles the application as a production build (above)
-- Uses [winres](https://github.com/tc-hib/winres) to bundle the icon and manifest into a `.syso` file ready for linking.
-
-#### Manual Steps
-
-- Create `icon.ico` using the [winicon](https://github.com/leaanthony/winicon) CLI tool (or any other tool).
-- Create / Update a `.manifest` file for your application
-- Use the [winres CLI](https://github.com/tc-hib/go-winres) to generate a `.syso` file.
-
-### Compile application
-
-#### Wails CLI
-
-- If the `-clean` flag is provided, the `build` directory is deleted and recreated
-- For `wails dev`, the following default Go flags are used: `-tags dev -gcflags "all=-N -l"`
-- For `wails build`, the following default Go flags are used: `-tags desktop,production -ldflags "-w -s"`
- - On Windows, `-ldflags "-w -h -H windowsgui"`
-- Additional tags passed to the CLI using `-tags` are added to the defaults
-- Additional ldflags passed to the CLI using `-ldflags` are added to the defaults
-- The `-o` flag is passed through
-- The Go compiler specified by `-compiler` will be used for compilation
-
-#### Manual steps
-
-- For dev build, the minimum command would be: `go build -tags dev -gcflags "all=-N -l"`
-- For production build, the minimum command would be: `go build -tags desktop,production -ldflags "-w -s -H windowsgui"`
-- Ensure that you compile in the same directory as the `.syso` file
-
-### Compress application
-
-#### Wails CLI
-
-- If the `-upx` flag has been given, the `upx` program will be run to compress the application with the default settings
-- If `-upxflags` is also passed, these flags are used instead of the default ones
-
-#### Manual steps
-
-- Run `upx [flags]` manually to compress the application.
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/windows.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/windows.mdx
deleted file mode 100644
index 821808c0b..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/windows.mdx
+++ /dev/null
@@ -1,61 +0,0 @@
-# Windows
-
-This page has miscellaneous guides related to developing Wails applications for Windows.
-
-## Handling the WebView2 Runtime Dependency
-
-Wails applications built for Windows have a runtime requirement on the Microsoft [WebView2 Runtime](https://developer.microsoft.com/en-us/microsoft-edge/webview2/). Windows 11 will have this installed by default, but some machines won't. Wails offers an easy approach to dealing with this dependency.
-
-By using the `-webview2` flag when building, you can decide what your application will do when a suitable runtime is not detected (including if the installed runtime is too old). The four options are:
-
-1. Download
-2. Embed
-3. Browser
-4. Error
-
-### Download
-
-This option will prompt the user that no suitable runtime has been found and then offer to download and run the official bootstrapper from Microsoft's WebView2 site. If the user proceeds, the official bootstrapper will be downloaded and run.
-
-### Embed
-
-This option embeds the official bootstrapper within the application. If no suitable runtime has been found, the application will offer to run the bootstrapper. This adds ~150k to the binary size.
-
-### Browser
-
-This option will prompt the user that no suitable runtime has been found and then offer to open a browser to the official WebView2 page where the bootstrapper can be downloaded and installed. The application will then exit, leaving the installation up to the user.
-
-### Error
-
-If no suitable runtime is found, an error is given to the user and no further action taken.
-
-## Fixed version runtime
-
-Another way of dealing with webview2 dependency is shipping it yourself. You can download [fixed version runtime](https://developer.microsoft.com/microsoft-edge/webview2/#download-section) and bundle or download it with your application.
-
-Also, you should specify path to fixed version of webview2 runtime in the `windows.Options` structure when launching wails.
-
-```go
- wails.Run(&options.App{
- Windows: &windows.Options{
- WebviewBrowserPath: "",
- },
- })
-```
-
-Note: When `WebviewBrowserPath` is specified, `error` strategy will be forced in case of minimal required version mismatch or invalid path to a runtime.
-
-## Spawning other programs
-
-When spawning other programs, such as scripts, you will see the window appear on the screen. To hide the window, you can use the following code:
-
-```go
-cmd := exec.Command("your_script.exe")
-cmd.SysProcAttr = &syscall.SysProcAttr{
- HideWindow: true,
- CreationFlags: 0x08000000,
-}
-cmd.Start()
-```
-
-Solution provided by [sithembiso](https://github.com/sithembiso) on the [discussions board](https://github.com/wailsapp/wails/discussions/1734#discussioncomment-3386172).
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/tutorials/dogsapi.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/tutorials/dogsapi.mdx
deleted file mode 100644
index 1af16f774..000000000
--- a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/tutorials/dogsapi.mdx
+++ /dev/null
@@ -1,245 +0,0 @@
----
-sidebar_position: 20
----
-
-# Dogs API
-
-```mdx-code-block
-
-
-
-
-```
-
-:::note
-
-This tutorial has been kindly provided by [@tatadan](https://twitter.com/tatadan) and forms part of their [Wails Examples Repository](https://github.com/tataDan/wails-v2-examples).
-
-:::
-
-In this tutorial we are going to develop an application that retrieves photos of dogs from the web and then displays them.
-
-### Create the project
-
-Let's create the application. From a terminal enter: `wails init -n dogs-api -t svelte`
-
-Note: We could optionally add `-ide vscode` or `-ide goland` to the end of this command if you wanted to add IDE support.
-
-Now let's `cd dogs-api` and start editing the project files.
-
-### Remove unused code
-
-We will start by removing some elements that we know we will not use:
-
-- Open `app.go` and remove the following lines:
-
-```go
-// Greet returns a greeting for the given name
-func (a *App) Greet(name string) string {
- return fmt.Sprintf("Hello %s, It's show time!", name)
-}
-```
-
-- Open `frontend/src/App.svelte` and delete all lines.
-- Delete the `frontend/src/assets/images/logo-universal.png` file
-
-### Creating our application
-
-Now let's add our new Go code.
-
-Add the following struct declarations to `app.go` before the function definitions:
-
-```go
-type RandomImage struct {
- Message string
- Status string
-}
-
-type AllBreeds struct {
- Message map[string]map[string][]string
- Status string
-}
-
-type ImagesByBreed struct {
- Message []string
- Status string
-}
-```
-
-Add the following functions to `app.go` (perhaps after the existing function definitions):
-
-```go
-func (a *App) GetRandomImageUrl() string {
- response, err := http.Get("https://dog.ceo/api/breeds/image/random")
- if err != nil {
- log.Fatal(err)
- }
-
- responseData, err := ioutil.ReadAll(response.Body)
- if err != nil {
- log.Fatal(err)
- }
-
- var data RandomImage
- json.Unmarshal(responseData, &data)
-
- return data.Message
-}
-
-func (a *App) GetBreedList() []string {
- var breeds []string
-
- response, err := http.Get("https://dog.ceo/api/breeds/list/all")
- if err != nil {
- log.Fatal(err)
- }
-
- responseData, err := ioutil.ReadAll(response.Body)
- if err != nil {
- log.Fatal(err)
- }
-
- var data AllBreeds
- json.Unmarshal(responseData, &data)
-
- for k := range data.Message {
- breeds = append(breeds, k)
- }
-
- sort.Strings(breeds)
-
- return breeds
-}
-
-func (a *App) GetImageUrlsByBreed(breed string) []string {
-
- url := fmt.Sprintf("%s%s%s%s", "https://dog.ceo/api/", "breed/", breed, "/images")
- response, err := http.Get(url)
- if err != nil {
- log.Fatal(err)
- }
-
- responseData, err := ioutil.ReadAll(response.Body)
- if err != nil {
- log.Fatal(err)
- }
-
- var data ImagesByBreed
- json.Unmarshal(responseData, &data)
-
- return data.Message
-}
-```
-
-Modify the `import` section of `app.go` to look like this:
-
-```go
-import (
- "context"
- "fmt"
- "encoding/json"
- "io/ioutil"
- "log"
- "net/http"
- "sort"
-)
-```
-
-Add the following lines to `frontend/src/App.svelte`:
-
-
-```html
-
-
-
Dogs API
-
-
- Click on down arrow to select a breed
-
-
-
-
-{#if showRandomPhoto}
-
-{/if}
-{#if showBreedPhotos}
- {#each photos as photo}
-
- {/each}
-{/if}
-
-
-```
-
-
-### Testing the application
-
-To generate the bindings and test the application, run `wails dev`.
-
-### Compiling the application
-
-To compile the application to a single, production grade binary, run `wails build`.
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/community/links.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/community/links.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/community/links.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/community/links.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/emailit.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/emailit.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/emailit.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/emailit.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/encrypteasy.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/encrypteasy.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/encrypteasy.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/encrypteasy.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/filehound.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/filehound.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/filehound.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/filehound.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/minecraftupdater.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/minecraftupdater.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/minecraftupdater.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/minecraftupdater.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/modalfilemanager.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/modalfilemanager.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/modalfilemanager.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/modalfilemanager.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/mollywallet.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/mollywallet.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/mollywallet.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/mollywallet.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/october.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/october.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/october.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/october.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/optimus.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/optimus.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/optimus.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/optimus.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/portfall.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/portfall.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/portfall.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/portfall.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/restic-browser.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/restic-browser.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/restic-browser.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/restic-browser.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/riftshare.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/riftshare.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/riftshare.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/riftshare.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/scriptbar.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/scriptbar.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/scriptbar.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/scriptbar.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/surge.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/surge.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/surge.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/surge.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/wally.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/wally.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/wally.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/wally.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/wombat.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/wombat.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/wombat.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/wombat.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/ytd.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/ytd.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/ytd.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/community/showcase/ytd.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/community/templates.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/community/templates.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/community/templates.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/community/templates.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/building.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/gettingstarted/building.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/building.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/gettingstarted/building.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/development.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/gettingstarted/development.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/development.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/gettingstarted/development.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/firstproject.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/gettingstarted/firstproject.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/firstproject.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/gettingstarted/firstproject.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/installation.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/gettingstarted/installation.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/installation.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/gettingstarted/installation.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/angular.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/angular.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/angular.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/angular.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/application-development.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/application-development.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/application-development.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/application-development.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/dynamic-assets.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/dynamic-assets.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/dynamic-assets.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/dynamic-assets.mdx
diff --git a/website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/frameless.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/frameless.mdx
similarity index 100%
rename from website/i18n/pt/docusaurus-plugin-content-docs/version-v2.3.0/guides/frameless.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/frameless.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/frontend.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/frontend.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/frontend.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/frontend.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/ides.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/ides.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/ides.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/ides.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/linux-distro-support.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/linux-distro-support.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/linux-distro-support.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/linux-distro-support.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/guides/linux.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/linux.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/guides/linux.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/linux.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/local-development.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/local-development.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/local-development.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/local-development.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/mac-appstore.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/mac-appstore.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/mac-appstore.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/mac-appstore.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/manual-builds.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/manual-builds.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/manual-builds.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/manual-builds.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/migrating.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/migrating.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/migrating.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/migrating.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/mouse-buttons.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/mouse-buttons.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/mouse-buttons.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/mouse-buttons.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/obfuscated.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/obfuscated.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/obfuscated.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/obfuscated.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/overscroll.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/overscroll.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/overscroll.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/overscroll.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/routing.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/routing.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/routing.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/routing.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/signing.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/signing.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/signing.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/signing.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/templates.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/templates.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/templates.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/templates.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/troubleshooting.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/troubleshooting.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/troubleshooting.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/troubleshooting.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/vscode.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/vscode.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/vscode.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/vscode.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/windows-installer.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/windows-installer.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/guides/windows-installer.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/windows-installer.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/windows.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/windows.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/windows.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/guides/windows.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/howdoesitwork.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/howdoesitwork.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/howdoesitwork.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/howdoesitwork.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/introduction.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/introduction.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/introduction.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/introduction.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/reference/cli.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/reference/cli.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/reference/cli.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/reference/cli.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/reference/menus.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/reference/menus.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/reference/menus.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/reference/menus.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/reference/options.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/reference/options.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/reference/options.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/reference/options.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/reference/project-config.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/reference/project-config.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/reference/project-config.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/reference/project-config.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/browser.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/browser.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/browser.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/browser.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/dialog.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/dialog.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/dialog.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/dialog.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/events.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/events.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/events.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/events.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/intro.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/intro.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/intro.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/intro.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/log.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/log.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/log.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/log.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/menu.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/menu.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/menu.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/menu.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/window.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/window.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/reference/runtime/window.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/reference/runtime/window.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/tutorials/dogsapi.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/tutorials/dogsapi.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/tutorials/dogsapi.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/tutorials/dogsapi.mdx
diff --git a/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/tutorials/helloworld.mdx b/website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/tutorials/helloworld.mdx
similarity index 100%
rename from website/i18n/ru/docusaurus-plugin-content-docs/version-v2.3.0/tutorials/helloworld.mdx
rename to website/i18n/ru/docusaurus-plugin-content-docs/version-v2.4.0/tutorials/helloworld.mdx
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/links.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/links.mdx
deleted file mode 100644
index 90c365a3d..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/links.mdx
+++ /dev/null
@@ -1,23 +0,0 @@
----
-sidebar_position: 2
----
-
-# 链接
-
-此页面用于列出社区相关的链接。 请提交 PR(点击页面底部的`编辑此页`)增加链接。
-
-## 了不起的 Wails
-
-Wails 相关的[优秀列表](https://github.com/wailsapp/awesome-wails)。
-
-## 支持的通道
-
-- [Gophers Slack Channel](https://gophers.slack.com/messages/CJ4P9F7MZ/)
-- [Gophers Slack Channel Invite](https://invite.slack.golangbridge.org/)
-- [Github Issues](https://github.com/wailsapp/wails/issues)
-- [v2 测试版讨论板](https://github.com/wailsapp/wails/discussions/828)
-
-## 社交媒体
-
-- [Twitter](https://twitter.com/wailsapp)
-- [Wails 中文社区 QQ 群](https://qm.qq.com/cgi-bin/qm/qr?k=PmIURne5hFGNd7QWzW5qd6FV-INEjNJv&jump_from=webapi) - 群号:1067173054
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/_category_.json b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/_category_.json
deleted file mode 100644
index 276e283b7..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Showcase",
- "position": 1
-}
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/emailit.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/emailit.mdx
deleted file mode 100644
index 4a1ebe835..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/emailit.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
-# EmailIt
-
-
-
-
-
-
-[EmailIt](https://github.com/raguay/EmailIt/) is a Wails 2 program that is a markdown based email sender only with nine notepads, scripts to manipulate the text, and templates. It also has a builtin [Node-Red](https://nodered.org/) server, scripts terminal, and the [ScriptBar](https://github.com/raguay/ScriptBarApp) program for displaying results from Node-Red or a script on your system. Documentation is very scarce, but the programs works. It’s built using Wails2 and Svelte, and the download is a universal macOS application.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/encrypteasy.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/encrypteasy.mdx
deleted file mode 100644
index 9b2e5f8ac..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/encrypteasy.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# EncryptEasy
-
-
-
-
-
-
-**[cryptEasy](https://www.encrypteasy.app) 是一个管理您和您所有的联系人密钥的简单易用的 PGP 加密工具。 加密应该是简单的。 使用Wails开发。**
-
-Encrypting messages using PGP is the industry standard. Everyone has a private and a public key. Your private key, well, needs to be kept private so only you can read messages. Your public key is distributed to anyone who wants to send you secret, encrypted messages. Managing keys, encrypting messages and decrypting messages should be a smooth experience. EncryptEasy is all about making it easy.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/filehound.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/filehound.mdx
deleted file mode 100644
index 78cbfca86..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/filehound.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
-# FileHound Export Utility
-
-
-
-
-
-
-[FileHound Export Utility](https://www.filehound.co.uk/) FileHound is a cloud document management platform made for secure file retention, business process automation and SmartCapture capabilities.
-
-The FileHound Export Utility allows FileHound Administrators the ability to run a secure document and data extraction tasks for alternative back-up and recovery purposes. This application will download all documents and/or meta data saved in FileHound based on the filters you choose. The metadata will be exported in both JSON and XML formats.
-
-Backend built with: Go 1.15 Wails 1.11.0 go-sqlite3 1.14.6 go-linq 3.2
-
-Frontend with: Vue 2.6.11 Vuex 3.4.0 Typescript Tailwind 1.9.6
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/minecraftupdater.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/minecraftupdater.mdx
deleted file mode 100644
index 11247339d..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/minecraftupdater.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Minecraft Updater
-
-
-
-
-
-
-[Minecraft Updater](https://github.com/Gurkengewuerz/MinecraftModUpdater) is a utility tool to update and synchronize Minecraft mods for your userbase. It’s built using Wails2 and React with [antd](https://ant.design/) as frontend framework.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/modalfilemanager.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/modalfilemanager.mdx
deleted file mode 100644
index a7ae8c492..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/modalfilemanager.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
-# Modal File Manager
-
-
-
-
-
-
-[Modal File Manager](https://github.com/raguay/ModalFileManager) is a dual pane file manager using web technologies. My original design was based on NW.js and can be found [here](https://github.com/raguay/ModalFileManager-NWjs). This version uses the same Svelte based frontend code (but it has be greatly modified since the departure from NW.js), but the backend is a [Wails 2](https://wails.io/) implementation. By using this implementation, I no longer use command line `rm`, `cp`, etc. commands. It is fully coded using Go and runs much faster than the previous versions.
-
-This file manager is designed around the same principle as Vim: a state controlled keyboard actions. The number of states isn't fixed, but very programmable. Therefore, an infinite number of keyboard configurations can be created and used. This is the main difference from other file managers.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/mollywallet.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/mollywallet.mdx
deleted file mode 100644
index 534b097ca..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/mollywallet.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
-# Molley Wallet
-
-
-
-
-
-
-[Molly Wallet](https://github.com/grvlle/constellation_wallet/) the official $DAG wallet of the Constellation Network. It'll let users interact with the Hypergraph Network in various ways, not limited to producing $DAG transactions.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/october.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/october.mdx
deleted file mode 100644
index 889d2dd9e..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/october.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
-# October
-
-
-
-
-
-
-[October](https://october.utf9k.net) is a small Wails application that makes it really easy to extract highlights from [Kobo eReaders](https://en.wikipedia.org/wiki/Kobo_eReader) and then forward them to [Readwise](https://readwise.io).
-
-It has a relatively small scope with all platform versions weighing in under 10MB, and that's without enabling [UPX compression](https://upx.github.io/)!
-
-In contrast, the author's previous attempts with Electron quickly bloated to several hundred megabytes.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/optimus.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/optimus.mdx
deleted file mode 100644
index c3eb79507..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/optimus.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
-# Optimus
-
-
-
-
-
-
-[Optimus](https://github.com/splode/optimus) is a desktop image optimization application. It supports conversion and compression between WebP, JPEG, and PNG image formats.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/portfall.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/portfall.mdx
deleted file mode 100644
index 4cc2c63c9..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/portfall.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
-# Portfall
-
-
-
-
-
-
-[Portfall](https://github.com/rekon-oss/portfall) - A desktop k8s port-forwarding portal for easy access to all your cluster UIs
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/restic-browser.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/restic-browser.mdx
deleted file mode 100644
index 1505ce07a..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/restic-browser.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Restic Browser
-
-
-
-
-
-
-[Restic-Browser](https://github.com/emuell/restic-browser) - A simple, cross-platform [restic](https://github.com/restic/restic) backup GUI for browsing and restoring restic repositories.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/riftshare.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/riftshare.mdx
deleted file mode 100644
index 5223e88cf..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/riftshare.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
-# RiftShare
-
-
-
-
-
-
-Easy, Secure, and Free file sharing for everyone. Learn more at [Riftshare.app](https://riftshare.app)
-
-## Features
-
-- Easy secure file sharing between computers both in the local network and through the internet
-- Supports sending files or directories securely through the [magic wormhole protocol](https://magic-wormhole.readthedocs.io/en/latest/)
-- Compatible with all other apps using magic wormhole (magic-wormhole or wormhole-william CLI, wormhole-gui, etc.)
-- Automatic zipping of multiple selected files to send at once
-- Full animations, progress bar, and cancellation support for sending and receiving
-- Native OS File Selection
-- Open files in one click once received
-- Auto Update - don't worry about having the latest release!
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/scriptbar.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/scriptbar.mdx
deleted file mode 100644
index aaa556f92..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/scriptbar.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
-# ScriptBar
-
-
-
-
-
-
-[ScriptBar](https://GitHub.com/raguay/ScriptBarApp) is a program to show the output of the embedded [Node-Red](https://nodered.org) server in the [EmailIt](https://GitHub.com/raguay/EmailIt) application. It also displays the output of scripts on your system. ScriptBar doesn't put them in the menubar, but has them all in a convient window for easy viewing. You can have multiple tabs to have many different things show. You can also keep the links to your most visited web sites.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/surge.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/surge.mdx
deleted file mode 100644
index 2d895dc29..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/surge.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
-# Surge
-
-
-
-
-
-
-[Surge](https://getsurge.io/) is a p2p filesharing app designed to utilize blockchain technologies to enable 100% anonymous file transfers. Surge is end-to-end encrypted, decentralized and open source.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/wally.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/wally.mdx
deleted file mode 100644
index 2a2498f40..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/wally.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
-# Wally
-
-
-
-
-
-
-[Wally](https://ergodox-ez.com/pages/wally) is the official firmware flasher for [Ergodox](https://ergodox-ez.com/) keyboards. It looks great and is a fantastic example of what you can achieve with Wails: the ability to combine the power of Go and the rich graphical tools of the web development world.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/wombat.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/wombat.mdx
deleted file mode 100644
index 54cedacea..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/wombat.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
-# Wombat
-
-
-
-
-
-
-[Wombat](https://github.com/rogchap/wombat) is a cross platform gRPC client.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/ytd.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/ytd.mdx
deleted file mode 100644
index 178ff0529..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/showcase/ytd.mdx
+++ /dev/null
@@ -1,8 +0,0 @@
-# Ytd
-
-
-
-
-
-
-[Ytd](https://github.com/marcio199226/ytd/tree/v2-wails) is an app for downloading tracks from youtube, creating offline playlists and share them with your friends, your friends will be able to playback your playlists or download them for offline listening, has an built-in player.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/templates.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/templates.mdx
deleted file mode 100644
index 8b98f7115..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/community/templates.mdx
+++ /dev/null
@@ -1,52 +0,0 @@
----
-sidebar_position: 1
----
-
-# 模板
-
-此页面用作社区支持的模板列表。 请提交一个包含您的模板的 PR(点击页面底部的`编辑此页`)。 要构建您自己的模板,请参考[模板](../guides/templates)指南。
-
-要使用这些模板,请运行 `wails init -n "您的项目名" -t [下面的链接[@版本]]`
-
-如果不带版本后缀,默认使用的是主分支代码模板,如果带有版本后缀,则使用该版本对应标签的代码模板。 If there is a version suffix, the code template corresponding to the tag of this version is used.
-
-示例:`wails init -n "Your Project Name" -t https://github.com/misitebao/wails-template-vue@v2.0.0-beta.3`
-
-:::warning 注意
-
-**Wails 项目不维护也不对第 3 方模板负责**
-
-如果您不确定某个模板,请检查 `package.json`和`wails.json` 中安装的模块和运行的脚本。
-
-:::
-
-## Vue
-
-- [wails-template-vue](https://github.com/misitebao/wails-template-vue) - 基于 Vite、Vue 和 Vue-Router 的 Wails 模板(同时支持 JavaScript 和 TypeScript)
-- [wails-vite-vue-ts](https://github.com/codydbentley/wails-vite-vue-ts) - 使用 Vite 的 Vue 3 TypeScript(以及添加功能的说明)
-- [wails-vite-vue-the-works](https://github.com/codydbentley/wails-vite-vue-the-works) - 使用 Vite, Vuex, Vue Router, Sass, 和 ESLint + Prettier 的 Vue 3 TypeScript
-
-## Angular
-
-- [wails-angular-template](https://github.com/TAINCER/wails-angular-template) - 带有 TypeScript, Sass, 热重载, 代码拆分和 i18n 的 Angular
-
-## React
-
-- [wails-react-template](https://github.com/AlienRecall/wails-react-template) - 基于 reactjs 的模板
-- [wails-react-template](https://github.com/flin7/wails-react-template) - 基于 React 并支持实时开发模式的轻量级模板
-- [wails-vite-react-ts](https://github.com/lontten/wails-vite-react-ts) - 基于 Vite + React + TypeScript 的模板
-
-## Svelte
-
-- [wails-svelte-template](https://github.com/raitonoberu/wails-svelte-template) - 基于 Svelte 的模板
-- [wails-vite-svelte-template](https://github.com/BillBuilt/wails-vite-svelte-template) - 使用 Svelte 和 Vite 的模板
-- [wails-vite-svelte-tailwind-template](https://github.com/BillBuilt/wails-vite-svelte-tailwind-template) - 使用 Svelte 和 Vite 和 TailwindCSS v3 的模板
-- [wails-template-nextjs](https://github.com/LGiki/wails-template-nextjs) - 基于 Next.js + TypeScript 的模板
-
-## Elm
-
-- [wails-elm-template](https://github.com/benjamin-thomas/wails-elm-template) - Develop your GUI app with functional programming and a **snappy** hot-reload setup :tada: :rocket:
-
-## Pure JavaScript (Vanilla)
-
-- [wails-pure-js-template](https://github.com/KiddoV/wails-pure-js-template) - A template with nothing but just basic JavaScript, HTML, and CSS
\ No newline at end of file
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/_category_.json b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/_category_.json
deleted file mode 100644
index 597b920df..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Getting Started",
- "position": 10
-}
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/building.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/building.mdx
deleted file mode 100644
index 38bf5d47d..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/building.mdx
+++ /dev/null
@@ -1,21 +0,0 @@
----
-sidebar_position: 6
----
-
-# 编译您的项目
-
-从项目目录,运行`wails build`。 这将编译您的项目并将构建的可用于生产的二进制文件保存在 `build/bin` 目录中。
-
-如果您运行二进制文件,您应该会看到默认应用程序:
-
-
-
-
-
-
-
-有关编译选项的更多详细信息,请参阅[构建命令](../reference/cli#构建)。
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/development.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/development.mdx
deleted file mode 100644
index a9e165543..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/development.mdx
+++ /dev/null
@@ -1,16 +0,0 @@
----
-sidebar_position: 5
----
-
-# 开发您的应用程序
-
-您可以通过运行`wails dev`从项目目录在开发模式下运行您的应用程序。 这将执行以下操作:
-
-- 构建您的应用程序并运行它
-- 监听 Go 文件中的修改并在更改时重新构建/重新运行
-- Using the power of [vite](https://vitejs.dev/), will watch for modifications in your Go files and rebuild/re-run on change
-- 设置将通过浏览器为您的应用程序提供服务的[网络服务器](http://localhost:34115)。 这允许您使用您喜欢的浏览器扩展。 您甚至可以从控制台调用 Go 代码。
-
-首先,在项目目录中运行`wails dev`。 可以在[此处](../reference/cli#开发)找到有关这方面的更多信息。
-
-即将提供:教程
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/firstproject.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/firstproject.mdx
deleted file mode 100644
index e43d5f7d1..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/firstproject.mdx
+++ /dev/null
@@ -1,132 +0,0 @@
----
-sidebar_position: 2
----
-
-# 创建项目
-
-## 项目生成
-
-现在 CLI 已安装,您可以使用`wails init`命令生成一个新项目。
-
-选择您最喜欢的框架:
-
-
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-
-
-
- Generate a Svelte project using Javascript with:
-
- wails init -n myproject -t svelte
-If you would rather use Typescript:
-
- wails init -n myproject -t svelte-ts
-
-
-
- Generate a React project using Javascript with:
-
- wails init -n myproject -t react
-If you would rather use Typescript:
-
- wails init -n myproject -t react-ts
-
-
-
- Generate a Vue project using Javascript with:
-
- wails init -n myproject -t vue
-
-If you would rather use Typescript:
-
- wails init -n myproject -t vue-ts
-
-
-
- Generate a Preact project using Javascript with:
-
- wails init -n myproject -t preact
-
-If you would rather use Typescript:
-
- wails init -n myproject -t preact-ts
-
-
-
- Generate a Lit project using Javascript with:
-
- wails init -n myproject -t lit
-
-If you would rather use Typescript:
-
- wails init -n myproject -t lit-ts
-
-
-
- Generate a Vanilla project using Javascript with:
-
- wails init -n myproject -t vanilla
-
-If you would rather use Typescript:
-
- wails init -n myproject -t vanilla-ts
-
-
-
-
-
-
-
-
-Wails 项目具有以下布局:
-
-要查看其他可用选项,您可以运行 `wails init -help`。 更多详细信息可以在 [初始化命令](../reference/cli#初始化)中找到。
-
-## 项目布局
-
-Wails 项目有以下布局:
-
-```
-.
-.
-.
-├── build/
-│ ├── appicon.png
-│ ├── darwin/
-│ └── windows/
-├── frontend/
-├── go.mod
-├── go.sum
-├── main.go
-└── wails.json
-```
-
-### 项目结构概要
-
-- `/main.go` - 主应用
-- `/frontend/` - 前端项目文件
-- `/build/` - 项目构建目录
-- `/wails.json` - 项目配置
-- `/go.mod` - Go mod 文件
-- `/go.sum` - Go mod 校验文件
-- `/build/windows/` - Windows 特定的项目文件
-- `/go.mod` - Go module file
-- `/go.sum` - Go module checksum file
-
-`frontend`目录没有特定于 Wails 的内容,可以是您选择的任何前端项目。
-
-`build`目录在构建过程中使用。 这些文件可以修改以自定义您的构建。 如果文件从构建目录中删除,将重新生成默认版本。
-
-`go.mod`中的默认模块名称是“changeme”。 您应该将其更改为更合适的内容。
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/installation.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/installation.mdx
deleted file mode 100644
index bbef43c3c..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/gettingstarted/installation.mdx
+++ /dev/null
@@ -1,109 +0,0 @@
----
-sidebar_position: 1
----
-
-# 安装
-
-## 支持的平台
-
-- Windows 10/11 AMD64/ARM64
-- MacOS 10.13+ AMD64
-- MacOS 11.0+ ARM64
-- Linux AMD64/ARM64
-
-## 依赖
-
-Wails 有许多安装前需要的常见依赖项:
-
-- Go 1.17+
-- NPM (Node 15+)
-
-### Go
-
-从[Go 下载页面](https://golang.org/dl/)下载 Go。
-
-确保您遵守官方的[Go 安装说明](https://golang.org/doc/install#install)。 您还需要确保您的 `PATH` 环境变量包含您的 `~/go/bin` 目录路径。 重启终端并执行以下命令检查:
-
-- 检查 Go 是否安装正确: `go version`
-- 检查 "~/go/bin" 是否在您的 PATH 变量中: `echo $PATH | grep go/bin`
-
-### NPM
-
-从[Node 下载页面](https://nodejs.org/en/download/)下载 NPM。 最好使用最新版本,因为这是我们通常会测试的版本。
-
-运行 `npm --version` 进行验证。
-
-## 平台指定依赖关系
-
-您还需要安装指定平台的依赖项:
-
-
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-
-
-
- Wails 需要安装 xcode 命令行工具。 This can be
- done by running:
- xcode-select --install
-
-
- Wails requires that the WebView2{" "}
- runtime is installed. Some Windows installations will already have this installed. You can check using
- the{" "}
- wails doctor command (see below). Some Windows installations will already have this installed. You can check using
- the{" "}
- wails doctor command (see below). Some Windows installations will already have this
- installed. You can check using the wails doctor command (see
- below).
-
-
- Linux required the standard gcc build tools
- plus libgtk3 and libwebkit.
- Rather than list a ton of commands for different distros, Wails can try to determine
- what the installation commands are for your specific distribution. Run wails doctor after
- installation
- to be shown how to install the dependencies.
- If your distro/package manager is not supported, please consult the {" "}
- Add Linux Distro guide.
- Rather than list a ton of commands for different distros, Wails can try to determine
- what the installation commands are for your specific distribution. Run wails doctor after
- installation
- to be shown how to install the dependencies.
- If your distro/package manager is not supported, please consult the {" "}
- Add Linux Distro guide. Rather than list a ton of
- commands for different distros, Wails can try to determine what the
- installation commands are for your specific distribution. Run{" "}
- wails doctor after installation to be shown how to install the
- dependencies. If your distro/package manager is not supported, please
- consult the{" "}
- Add Linux Distro guide.
-
-
-
-
-
-## 可选依赖
-
-- [UPX](https://upx.github.io/) 用于压缩您的应用程序。
-
-## 安装 Wails
-
-运行 `go install github.com/wailsapp/wails/v2/cmd/wails@latest` 安装 Wails CLI。
-
-## 系统检查
-
-运行 `wails doctor` 将检查您是否安装了正确的依赖项。 如果没有,它会就缺少的内容提供建议以帮助纠正问题。
-
-## The `wails` command appears to be missing?
-
-If your system is reporting that the `wails` command is missing, make sure you have followed the Go installation guide correctly. Normally, it means that the `go/bin` directory in your User's home directory is not in the `PATH` environment variable. You will also normally need to close and reopen any open command prompts so that changes to the environment made by the installer are reflected at the command prompt.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/_category_.json b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/_category_.json
deleted file mode 100644
index 5935dad93..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Guides",
- "position": 50
-}
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/application-development.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/application-development.mdx
deleted file mode 100644
index 76e93b17a..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/application-development.mdx
+++ /dev/null
@@ -1,194 +0,0 @@
-# 应用开发
-
-使用 Wails 开发应用程序没有硬性规定,但有一些基本准则。
-
-## 应用程序设置
-
-默认模板使用 `main.go` 配置和运行应用程序, 同时`app.go`用于定义应用程序逻辑.
-
-`app.go`文件将定义一个结构体,该结构体有 2 个方法作为主应用程序的回调:
-
-```go title="app.go"
-type App struct {
- ctx context.Context
-}
-
-func NewApp() *App {
- return &App{}
-}
-
-func (a *App) startup(ctx context.Context) {
- a.ctx = ctx
-}
-
-func (a *App) shutdown(ctx context.Context) {
-}
-```
-
-- `startup`方法会在 Wails 分配它需要的资源后立即调用,这是创建资源、设置事件侦听器以及应用程序在启动时需要的任何其他内容的好地方。 它提供了一个`context.Context`, 通常保存在结构字段中。 调用[运行时](../reference/runtime/intro)需要此`context.Context`。 如果此方法返回错误,则应用程序将终止。 在开发模式下,错误会输出到控制台。
-
-- The shutdown method will be called by Wails right at the end of the shutdown process. This is a good place to deallocate memory and perform any shutdown tasks. This is a good place to deallocate memory and perform any shutdown tasks.
-
-`main.go`文件通常由对`wails.Run()`的单个调用组成,它接受应用程序配置。 模板使用的模式是,在调用`wails.Run()`之前, 我们创建并保存一个在`app.go`中定义的结构体的实例在名`app`的变量中。 这个配置是我们添加回调的地方:
-
-```go {3,9,10} title="main.go"
-func main() {
-
- app := NewApp()
-
- err := wails.Run(&options.App{
- Title: "My App",
- Width: 800,
- Height: 600,
- OnStartup: app.startup,
- OnShutdown: app.shutdown,
- })
- if err != nil {
- log.Fatal(err)
- }
-}
-
-```
-
-可以在[此处](../howdoesitwork#应用程序生命周期回调)找到有关应用程序生命周期回调的更多信息。
-
-## 绑定方法
-
-您可能希望从前端调用 Go 方法。 这通常是通过向`app.go`中已经定义的结构体中添加公共方法来实现的:
-
-```go {16-18} title="app.go"
-type App struct {
- ctx context.Context
-}
-
-func NewApp() *App {
- return &App{}
-}
-
-func (a *App) startup(ctx context.Context) {
- a.ctx = ctx
-}
-
-func (a *App) shutdown(ctx context.Context) {
-}
-
-func (a *App) Greet(name string) string {
- return fmt.Printf("Hello %s!", name)
-}
-```
-
-在主应用程序中,`Bind`字段告诉我们 Wails 想要绑定什么:
-
-```go {11-13} title="main.go"
-func main() {
-
- app := NewApp()
-
- err := wails.Run(&options.App{
- Title: "My App",
- Width: 800,
- Height: 600,
- OnStartup: app.startup,
- OnShutdown: app.shutdown,
- Bind: []interface{}{
- app,
- },
- })
- if err != nil {
- log.Fatal(err)
- }
-}
-
-```
-
-这将绑定`App`结构中的所有公共方法(它永远不会绑定 startup 和 shutdown 方法)。
-
-### Dealing with context when binding multiple structs
-
-可以在[此处](../howdoesitwork#方法绑定)找到有关绑定的更多信息。
-
-```go
-func main() {
-
- app := NewApp()
- otherStruct := NewOtherStruct()
-
- err := wails.Run(&options.App{
- Title: "My App",
- Width: 800,
- Height: 600,
- OnStartup: func(ctx context.Context){
- app.SetContext(ctx)
- otherStruct.SetContext(ctx)
- },
- OnShutdown: app.shutdown,
- Bind: []interface{}{
- app,
- otherStruct
- },
- })
- if err != nil {
- log.Fatal(err)
- }
-}
-```
-
-More information on Binding can be found [here](../howdoesitwork.mdx#method-binding).
-
-## 应用程序菜单
-
-Wails 支持向您的应用程序添加菜单。 这是通过将 [菜单](../reference/menus#菜单) 结构体传递给应用程序配置来完成的。 常见做法是使用一个返回菜单的方法,更常见的是用作生命周期回调的 `App` 结构体上的方法。
-
-```go {11} title="main.go"
-func main() {
-
- app := NewApp()
-
- err := wails.Run(&options.App{
- Title: "My App",
- Width: 800,
- Height: 600,
- OnStartup: app.startup,
- OnShutdown: app.shutdown,
- Menu: app.menu(),
- Bind: []interface{}{
- app,
- },
- })
- if err != nil {
- log.Fatal(err)
- }
-}
-
-```
-
-## 资源
-
-Wails v2 处理资源的方式的伟大之处在于它没有! 您唯一需要给 Wails 的是一个 `embed.FS`, 如何做到这一点完全取决于您。 How you get to that is entirely up to you. 您可以像 vanilla 模板一样使用 vanilla html/css/js 文件。 您可能有一些复杂的构建系统,但这并不影响。
-
-当运行`wails build`时,它会检查项目根目录的`wails.json`文件。 文件中有 2 个字段会被读取:
-
-- "frontend:install"
-- "frontend:build"
-
-第一个,如果有给定,将在`frontend`目录中执行以安装 node 模块。 第二个,如果有给定,将在`frontend`目录中执行以构建前端项目。
-
-如果没有给出这两个字段,那么 Wails 不会对前端做任何操作。 它仅仅被用作`embed.FS`。
-
-### AssetsHandler
-
-A Wails v2 app can optionally define a `http.Handler` in the `options.App`, which allows hooking into the AssetServer to create files on the fly or process POST/PUT requests. GET requests are always first handled by the `assets` FS. If the FS doesn't find the requested file the request will be forwarded to the `http.Handler` for serving. Any requests other than GET will be directly processed by the `AssetsHandler` if specified. It's also possible to only use the `AssetsHandler` by specifiy `nil` as the `Assets` option. GET requests are always first handled by the `assets` FS. If the FS doesn't find the requested file the request will be forwarded to the `http.Handler` for serving. Any requests other than GET will be directly processed by the `AssetsHandler` if specified. It's also possible to only use the `AssetsHandler` by specifiy `nil` as the `Assets` option.
-
-## 内置开发服务器
-
-运行`wails dev`将启动内置的开发服务器,它将在您的项目目录中启动一个文件监听器。 默认情况下,如果有任何文件更改,wails 会检查它是否是应用程序文件(默认:.go,可使用`-e`标志配置)。 如果是,那么它将重新构建您的应用程序并重新启动它。 如果更改的文件在`assetdir`目录中,它会在很短的时间后重新加载。
-
-开发服务器使用一种称为“防抖”的技术,这意味着它不会立即重新加载,因为可能会在短时间内更改多个文件。 当触发发生时,它会在发出重新加载之前等待一定的时间。 如果发生另一个触发,它会再次重置为等待时间。 默认情况下,此值为 100ms。 如果此值不适用于您的项目,则可以使用`-debounce`标志进行配置。 如果使用,此值将保存到您的项目配置中并成为默认值。
-
-## 外部开发服务器
-
-一些框架带有自己的实时重新加载服务器,但是它们将无法利用 Wails Go 绑定。 在这种情况下,最好运行一个监听脚本,将项目重新构建到构建目录中,Wails 将监视该目录。 有关示例,请参阅使用[rollup](https://rollupjs.org/guide/en/)的默认 svelte 模板。 对于[create-react-app](https://create-react-app.dev/),可以使用[此脚本](https://gist.github.com/int128/e0cdec598c5b3db728ff35758abdbafd)来实现类似的结果。
-
-## Go 模块
-
-默认的 Wails 模板会生成一个包含模块名称“changeme”的`go.mod`文件。 您应该在项目生成后将其更改为更合适的内容。
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/bleeding-edge.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/bleeding-edge.mdx
deleted file mode 100644
index 8fad99fde..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/bleeding-edge.mdx
+++ /dev/null
@@ -1,55 +0,0 @@
-# 前沿风险技术
-
-## 概述
-
-Wails 一直在开发中,新版本会定期“标记”。 这通常发生在`master`分支上所有较新的代码都经过测试并确认有效时。 如果您需要尚未发布的错误修复或功能,可以通过以下步骤使用最新的“前沿风险”版本:
-
-- `git clone https://github.com/wailsapp/wails`
-- `cd wails/v2/cmd/wails`
-- `go install`
-
-注意:您将项目克隆到的目录现在将被称为“clonedir”。
-
-Wails CLI 现在将是最新版本。
-
-### Updating your project
-
-To update projects to use the latest version of the Wails library, update the project's `go.mod` and ensure the following line is at the bottom of the file:
-
-`replace github.com/wailsapp/wails/v2 => `
-
-示例:
-
-在 Windows 上: `replace github.com/wailsapp/wails/v2 => C:\Users\leaan\Documents\wails-v2-beta\wails\v2`
-
-在'nix 上: `replace github.com/wailsapp/wails/v2 => /home/me/projects/wails/v2`
-
-To revert to a stable version, run:
-
-`go install github.com/wailsapp/wails/v2/cmd/wails@latest`
-
-## 测试一个分支
-
-如果要测试一个分支,请按照上面的说明进行操作,但请确保在安装之前切换要测试的分支:
-
-- `git clone https://github.com/wailsapp/wails`
-- `cd wails`
-- `git checkout -b branch-to-test --track origin/branch-to-test`
-- `cd v2/cmd/wails`
-- `go install`
-
-Make sure you [update your project](#updating-your-project) as described above.
-
-## Testing a PR
-
-If you want to test a PR, follow the instructions above, but ensure you fetch the PR and switch the branch before installing. Please replace `[IDofThePR]` with the ID of the PR shown on github.com: If you want to test a PR, follow the instructions above, but ensure you fetch the PR and switch the branch before installing. Please replace `[IDofThePR]` with the ID of the PR shown on github.com: Please replace `[IDofThePR]` with the ID of the PR shown on github.com:
-
-- `git clone https://github.com/wailsapp/wails`
-- `cd wails`
-- `git fetch -u origin pull/[IDofThePR]/head:test/pr-[IDofThePR]`
-- `git checkout test/pr-[IDofThePR]`
-- `git reset --hard HEAD`
-- `cd v2/cmd/wails`
-- `go install`
-
-Make sure you [update your project](#updating-your-project) as described above.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/dynamic-assets.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/dynamic-assets.mdx
deleted file mode 100644
index c28d70e9d..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/dynamic-assets.mdx
+++ /dev/null
@@ -1,130 +0,0 @@
-# 动态资源
-
-If you want to load or generate assets for your frontend dynamically, you can achieve that using the [AssetsHandler](../reference/options#assetshandler) option. The AssetsHandler is a generic `http.Handler` which will be called for any non GET request on the assets server and for GET requests which can not be served from the bundled assets because the file is not found. The AssetsHandler is a generic `http.Handler` which will be called for any non GET request on the assets server and for GET requests which can not be served from the bundled assets because the file is not found. The AssetsHandler is a generic `http.Handler` which will be called for any non GET request on the assets server and for GET requests which can not be served from the bundled assets because the file is not found.
-
-By installing a custom AssetsHandler, you can serve your own assets using a custom asset server.
-
-## Example
-
-In our example project, we will create a simple assets handler which will load files off disk:
-
-```go title=main.go {16-35,49}
-package main
-
-import (
- "embed"
- "fmt"
- "github.com/wailsapp/wails/v2"
- "github.com/wailsapp/wails/v2/pkg/options"
- "net/http"
- "os"
- "strings"
-)
-
-//go:embed frontend/dist
-var assets embed.FS
-
-type FileLoader struct {
- http.Handler
-}
-
-func NewFileLoader() *FileLoader {
- return &FileLoader{}
-}
-
-func (h *FileLoader) ServeHTTP(res http.ResponseWriter, req *http.Request) {
- var err error
- requestedFilename := strings.TrimPrefix(req.URL.Path, "/")
- println("Requesting file:", requestedFilename)
- fileData, err := os.ReadFile(requestedFilename)
- if err != nil {
- res.WriteHeader(http.StatusBadRequest)
- res.Write([]byte(fmt.Sprintf("Could not load file %s", requestedFilename)))
- }
-
- res.Write(fileData)
-}
-
-func main() {
- // Create an instance of the app structure
- app := NewApp()
-
- // Create application with options
- err := wails.Run(&options.App{
- Title: "helloworld",
- Width: 1024,
- Height: 768,
- Assets: assets,
- BackgroundColour: &options.RGBA{R: 27, G: 38, B: 54, A: 255},
- OnStartup: app.startup,
- AssetsHandler: NewFileLoader(),
- Bind: []interface{}{
- app,
- },
- })
-
- if err != nil {
- println("Error:", err)
- }
-}
-```
-
-When we run the application in dev mode using `wails dev`, we will see the following output:
-
-```
-DEB | [ExternalAssetHandler] Loading 'http://localhost:3001/favicon.ico'
-DEB | [ExternalAssetHandler] Loading 'http://localhost:3001/favicon.ico' failed, using AssetHandler
-Requesting file: favicon.ico
-```
-
-As you can see, the assets handler is called when the default assets server is unable to serve the `favicon.ico` file.
-
-If you right click the main application and select "inspect" to bring up the devtools, you can test this feature out by typing the following into the console:
-
-```
-let response = await fetch('does-not-exist.txt');
-```
-
-This will generate an error in the devtools. This will generate an error in the devtools. This will generate an error in the devtools. We can see that the error is what we expect, returned by our custom assets handler:
-
-
-
-
-
-However, if we request `go.mod`, we will see the following output:
-
-
-
-
-
-This technique can be used to load images directly into the page. This technique can be used to load images directly into the page. If we updated our default vanilla template and replaced the logo image: This technique can be used to load images directly into the page. This technique can be used to load images directly into the page. If we updated our default vanilla template and replaced the logo image: This technique can be used to load images directly into the page. If we updated our default vanilla template and replaced the logo image:
-
-```html
-
-```
-
-with:
-
-```html
-
-```
-
-Then we would see the following:
-
-
-
-
-
-:::warning
-Exposing your filesystem in this way is a security risk. It is recommended that you properly manage access
-to your filesystem.
-::: It is recommended that you properly manage access
-to your filesystem.
-::: It is recommended that you properly manage access
-to your filesystem.
-:::
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/frameless.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/frameless.mdx
deleted file mode 100644
index 126a36c38..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/frameless.mdx
+++ /dev/null
@@ -1,84 +0,0 @@
-# 无边框应用
-
-Wails supports application that have no frames. 这可以通过使用[应用程序参数选项](../reference/options#应用程序参数选项)中的[无边框](../reference/options#无边框)字段来实现。
-
-Wails offers a simple solution for dragging the window: Any HTML element that has the CSS style `--wails-draggable:drag` will act as a "drag handle". This property applies to all child elements. If you need to indicate that a nested element should not drag, then use the attribute '--wails-draggable:no-drag' on that element.
-
-
-```html
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-```
-
-For some projects, using a CSS variable may not be possible due to dynamic styling. In this case, you can use the `CSSDragProperty` and `CSSDragValue` application options to define a property and value that will be used to indicate draggable regions:
-
-```go title=main.go
-package main
-
-import (
- "embed"
-
- "github.com/wailsapp/wails/v2"
- "github.com/wailsapp/wails/v2/pkg/options"
-)
-
-//go:embed frontend/dist
-var assets embed.FS
-
-func main() {
- // Create an instance of the app structure
- app := NewApp()
-
- // Create application with options
- err := wails.Run(&options.App{
- Title: "alwaysontop",
- Width: 1024,
- Height: 768,
- Assets: assets,
- Frameless: true,
- CSSDragProperty: "widows",
- CSSDragValue: "1",
- Bind: []interface{}{
- app,
- },
- })
-
- if err != nil {
- println("Error:", err)
- }
-}
-```
-
-```html title=index.html
-
-
-
-
-
- alwaysontop
-
-
-
-
-
-
-
-```
-
-:::info 全屏
-如果您允许应用程序全屏显示,则此拖动功能将被禁用。
-:::
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/frontend.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/frontend.mdx
deleted file mode 100644
index 789e834b8..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/frontend.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
-# 前端
-
-## 脚本注入
-
-当 Wails 为您的`index.html`提供服务时,默认情况下,它会将 2 个脚本注入``标签以加载`/wails/ipc.js`和`/wails/runtime.js`。 这些文件分别安装绑定和运行时。
-
-下面的代码显示了这些默认注入的位置:
-
-```html
-
-
- injection example
-
-
-
-
-
-
-
-
-
-## 发布模板
-
-发布模板只是将文件推送到 GitHub。 鼓励以下最佳实践:
-
-- 从前端目录中删除任何不需要的文件和目录(例如:.git)
-- 确保`template.json`完整,尤其是`helpurl`
-- 将文件推送到 GitHub
-- 在[社区模板](../community/templates)页面上创建 PR
-- 在[模板公告](https://github.com/wailsapp/wails/discussions/825)讨论板上发布模板
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/troubleshooting.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/troubleshooting.mdx
deleted file mode 100644
index bf338f32f..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/troubleshooting.mdx
+++ /dev/null
@@ -1,142 +0,0 @@
-# Troubleshooting
-
-An assortment of troubleshooting tips.
-
-## The `wails` command appears to be missing?
-
-If your system is reporting that the `wails` command is missing, make sure you have followed the Go installation guide correctly. Normally, it means that the `go/bin` directory in your User's home directory is not in the `PATH` environment variable. You will also normally need to close and reopen any open command prompts so that changes to the environment made by the installer are reflected at the command prompt.
-
-## My application is displaying a white/blank screen
-
-检查您的应用程序是否在正确目录中包含资源。 Check that your application includes the assets from the correct directory. In your `main.go` file, you will have something similar to the following code:
-
-```go
-//go:embed frontend/dist
-var assets embed.FS
-```
-
-Check that `frontend/dist` contains your application assets.
-
-### Mac
-
-If this happens on Mac, try adding the following to your `Info.plist`:
-
-```xml
-NSAppTransportSecurity
-
- NSAllowsLocalNetworking
-
-
-```
-
-Reference: https://github.com/wailsapp/wails/issues/1504#issuecomment-1174317433
-
-## Mac application not valid
-
-If your built application looks like this in finder:
-
-
-
-
-
-It's likely that your application's `info.plist` is invalid. Update the file in `build/.app/Contents/info.plist` and check if the data is valid, EG check the binary name is correct. To persist the changes, copy the file back to the `build/darwin` directory.
-
-## Cannot call backend method from frontend with variadic arguments
-
-If you have a backend method defined with variadic parameters, eg:
-
-```go
-func (a *App) TestFunc(msg string, args ...interface{}) error {
- // Code
-}
-```
-
-calling this method from the frontend like this will fail:
-
-```js
-var msg = "Hello: ";
-var args = ["Go", "JS"];
-window.go.main.App.TestFunc(msg, ...args)
- .then((result) => {
- //do things here
- })
- .catch((error) => {
- //handle error
- });
-```
-
-Workaround:
-
-```js
-var msg = "Hello ";
-var args = ["Go", "JS"];
-window.go.main.App.TestFunc(msg, args)
- .then((result) => {
- //without the 3 dots
- //do things here
- })
- .catch((error) => {
- //handle error
- });
-```
-
-Credit: https://github.com/wailsapp/wails/issues/1186
-
-## I'm having getting proxy errors when trying to install Wails
-
-If you are getting errors like this:
-
-```
-"https://proxy.golang.org/github.com/wailsapp/wails/cmd/wails/@v/list": dial tcp 172.217.163.49:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
-```
-
-it's probably because the official Go Proxy is being blocked (Users in China have reported this). The solution is to set up the proxy manually, eg: 解决方案是手动设置代理,例如:
-
-```
-go env -w GO111MODULE=on
-go env -w GOPROXY=https://goproxy.cn,direct
-```
-
-Source: https://github.com/wailsapp/wails/issues/1233
-
-## The generated Typescript doesn't have the correct types
-
-Sometimes the generated Typescript doesn't have the correct types. Sometimes the generated Typescript doesn't have the correct types. To mitigate this, it is possible to specify what types should be generated using the `ts_type` struct tag. For more details, please read [this](https://github.com/tkrajina/typescriptify-golang-structs#custom-types). For more details, please read [this](https://github.com/tkrajina/typescriptify-golang-structs#custom-types).
-
-## When I navigate away from `index.html`, I am unable to call methods on the frontend
-
-If you navigate away from `index.html` to a new html file, the context will be lost. If you navigate away from `index.html` to a new html file, the context will be lost. This can be fixed by adding the following imports to the `` section of any new page you navigate to:
-
-```html
-
-
-
-
-```
-
-Source: https://github.com/wailsapp/wails/discussions/1512
-
-## I get `too many open files` errors on my Mac when I run `wails dev`
-
-By default, macOS will only allow you to open a maximum of 256 files. This can affect the `wails dev` command. This limit can be increased by running: `ulimit -n 1024` in the terminal. This can affect the `wails dev` command. This limit can be increased by running: `ulimit -n 1024` in the terminal.
-
-FSNotify is [looking to move to Apple's fsevents](https://github.com/fsnotify/fsnotify/issues/11) for Mac. If this isn't completed soon, we will create our own implementation, tracked [here](https://github.com/wailsapp/wails/issues/1733). If this isn't completed soon, we will create our own implementation, tracked [here](https://github.com/wailsapp/wails/issues/1733).
-
-## My Mac app gives me weird compilation errors
-
-A few users have reported seeing compilation errors such as the following:
-
-```shell
-# github.com/wailsapp/wails/v2/internal/frontend/desktop/darwin
-In file included from ../../pkg/mod/github.com/wailsapp/wails/v2@v2.0.0-beta.44.2/internal/frontend/desktop/darwin/callbacks.go:9:
-In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX12.1.sdk/System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:12:
-/Library/Developer/CommandLineTools/SDKs/MacOSX12.1.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSBundle.h:91:143: error: function does not return NSString
-- (NSAttributedString *)localizedAttributedStringForKey:(NSString *)key value:(nullable NSString *)value table:(nullable NSString *)tableName NS_FORMAT_ARGUMENT(1) NS_REFINED_FOR_SWIFT API_AVAILABLE(macos(12.0), ios(15.0), watchos(8.0), tvos(15.0));
- ~~~~~~~~~~~~~~ ^ ~
-/Library/Developer/CommandLineTools/SDKs/MacOSX12.1.sdk/System/Library/Frameworks/Foundation.framework/Headers/NSObjCRuntime.h:103:48: note: expanded from macro 'NS_FORMAT_ARGUMENT'
- #define NS_FORMAT_ARGUMENT(A) __attribute__ ((format_arg(A)))
-```
-
-This is *normally* due to a mismatch with the OS version you are running and the version of the XCode Command Line Tools installed. If you see an error like this, try upgrading your XCode Command Line Tools to the latest version.
-
-Source: https://github.com/wailsapp/wails/issues/1806
\ No newline at end of file
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/vscode.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/vscode.mdx
deleted file mode 100644
index 9911a286c..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/vscode.mdx
+++ /dev/null
@@ -1,118 +0,0 @@
-
-# Visual Studio Code
-
-This page is for miscellaneous tips and tricks when using Visual Studio Code with Wails.
-
-## Vetur Configuration
-
-Many thanks to [@Lyimmi](https://github.com/Lyimmi) for this tip. Many thanks to [@Lyimmi](https://github.com/Lyimmi) for this tip. Originally posted [here](https://github.com/wailsapp/wails/issues/1791#issuecomment-1228158349).
-
-Vetur is a popular plugin for Visual Studio Code that provides syntax highlighting and code completion for Vue projects. Vetur is a popular plugin for Visual Studio Code that provides syntax highlighting and code completion for Vue projects. When loading a Wails project in VSCode, Vetur will throw an error as it is expecting to find the frontend project in the root directory. To fix this, you can do the following: To fix this, you can do the following:
-
-Create a file named `vetur.config.js` in the project's root.
-
-```javascript
-// vetur.config.js
-/** @type {import('vls').VeturConfig} */
-module.exports = {
- // **optional** default: `{}`
- // override vscode settings
- // Notice: It only affects the settings used by Vetur.
- settings: {
- "vetur.useWorkspaceDependencies": true,
- "vetur.experimental.templateInterpolationService": true
- },
- // **optional** default: `[{ root: './' }]`
- // support monorepos
- projects: [
- {
- // **required**
- // Where is your project?
- // It is relative to `vetur.config.js`.
- // root: './packages/repo1',
- root: './frontend',
- // **optional** default: `'package.json'`
- // Where is `package.json` in the project?
- // We use it to determine the version of vue.
- // It is relative to root property.
- package: './package.json',
- // **optional**
- // Where is TypeScript config file in the project?
- // It is relative to root property.
- tsconfig: './tsconfig.json',
- // **optional** default: `'./.vscode/vetur/snippets'`
- // Where is vetur custom snippets folders?
- snippetFolder: './.vscode/vetur/snippets',
- // **optional** default: `[]`
- // Register globally Vue component glob.
- // If you set it, you can get completion by that components.
- // It is relative to root property.
- // Notice: It won't actually do it. You need to use `require.context` or `Vue.component`
- globalComponents: [
- './src/components/**/*.vue'
- ]
- }
- ]
-}
- settings: {
- "vetur.useWorkspaceDependencies": true,
- "vetur.experimental.templateInterpolationService": true
- },
- // **optional** default: `[{ root: './' }]`
- // support monorepos
- projects: [
- {
- // **required**
- // Where is your project?
- // It is relative to `vetur.config.js`.
- // root: './packages/repo1',
- root: './frontend',
- // **optional** default: `'package.json'`
- // Where is `package.json` in the project?
- // We use it to determine the version of vue.
- // It is relative to root property.
- package: './package.json',
- // **optional**
- // Where is TypeScript config file in the project?
- // It is relative to root property.
- tsconfig: './tsconfig.json',
- // **optional** default: `'./.vscode/vetur/snippets'`
- // Where is vetur custom snippets folders?
- snippetFolder: './.vscode/vetur/snippets',
- // **optional** default: `[]`
- // Register globally Vue component glob.
- // If you set it, you can get completion by that components.
- // It is relative to root property.
- // Notice: It won't actually do it. You need to use `require.context` or `Vue.component`
- globalComponents: [
- './src/components/**/*.vue'
- ]
- }
- ]
-}
-```
-
-Next, configure `frontend/tsconfig.json`:
-
-```javascript
-{
- "compilerOptions": {
- "module": "system",
- "noImplicitAny": true,
- "removeComments": true,
- "preserveConstEnums": true,
- "sourceMap": true,
- "outFile": "../../built/local/tsc.js",
- "allowJs": true
- },
- "exclude": [
- "node_modules",
- "**/*.spec.ts"
- ],
- "include": [
- "src/**/*",
- "wailsjs/**/*.ts"
- ]
-}
-```
-This should enable you to now use Vetur as expected.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/windows-installer.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/windows-installer.mdx
deleted file mode 100644
index 5eb5b7d1f..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/windows-installer.mdx
+++ /dev/null
@@ -1,56 +0,0 @@
-# NSIS 安装程序
-
-
-
-
-
-
-Wails 支持使用[NSIS 安装程序](https://nsis.sourceforge.io/)生成 Windows 安装程序。
-
-## 安装 NSIS
-
-### Windows
-
-安装程序可在[NSIS 下载页面](https://nsis.sourceforge.io/Download)上找到。
-
-如果您使用 chocolatey 包管理器,请运行以下脚本:
-
-```
-choco install nsis
-```
-
-如果手动安装 NSIS,则需要将 NSIS 安装目录中包含`makensis.exe`的*Bin*目录添加到 PATH 中。 [这是](https://www.architectryan.com/2018/03/17/add-to-the-path-on-windows-10/) 一个关于如何在 Windows 上添加到 PATH 的好教程。
-
-### Linux
-
-应该可以通过您的发行版的软件包管理器获得`nsis`包。
-
-### MacOS
-
-NSIS 可通 homebrew 安装:`brew install nsis`。
-
-## 生成安装程序
-
-创建新项目时,Wails 从`installer/info.json`中读取配置数据并使用项目的`wails.json`的 Info 部分,在`build/windows/installer`中生成 NSIS 配置文件: 创建新项目时,Wails 从`installer/info.json`中读取配置数据并使用项目的`wails.json`的 Info 部分,在`build/windows/installer`中生成 NSIS 配置文件: The config data is read from `installer/info.json` and that is configured to use the project's `wails.json` Info section: 创建新项目时,Wails 从`installer/info.json`中读取配置数据并使用项目的`wails.json`的 Info 部分,在`build/windows/installer`中生成 NSIS 配置文件: The config data is read from `installer/info.json` and that is configured to use the project's `wails.json` Info section:
-
-```json
- // ...
- "Info": {
- "companyName": "My Company Name",
- "productName": "Wails Vite",
- "productVersion": "1.0.0",
- "copyright": "Copyright.........",
- "comments": "Built using Wails (https://wails.io)"
- },
-```
-
-要为您的应用程序生成安装程序,请使用`wails build`的`-nsis`标志:
-
-```
-wails build -nsis
-```
-
-现在可用安装程序将生成在`build/bin`目录中。
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/windows.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/windows.mdx
deleted file mode 100644
index 93f89b44c..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/guides/windows.mdx
+++ /dev/null
@@ -1,61 +0,0 @@
-# Windows 系统
-
-此页面包含了在 Windows 上开发 Wails 应用程序相关的其他指南。
-
-## 处理 WebView2 运行时依赖
-
-为 Windows 构建 Wails 应用程序时对 Microsoft [WebView2 运行时](https://developer.microsoft.com/en-us/microsoft-edge/webview2/)有要求。 默认情况下,Windows 11 会安装它,但有些机器不会。 Wails 提供了一种简单的方法来处理这种依赖关系。
-
-通过在构建时使用`-webview2`标志,您可以决定在未检测到合适的运行时的时候(包括安装的运行时是否太旧)应用程序将执行的操作。 四个选项是:
-
-1. Download(下载)
-2. Embed(内嵌)
-3. Browser(浏览器)
-4. Error(错误)
-
-### Download(下载)
-
-此选项将提示用户在未找到合适的运行时时,提供从 Microsoft 的 WebView2 官方站点下载并运行引导程序。 如果用户继续,官方引导程序将被下载并运行。
-
-### Embed(内嵌)
-
-此选项将官方引导程序嵌入到应用程序中。 如果没有找到合适的运行时,应用程序将提供并运行引导程序。 这将使二进制大小增加约 150k。
-
-### Browser(浏览器)
-
-此选项将提示用户没有找到合适的运行时时,提供打开浏览器到 WebView2 官方页面,可以下载和安装引导程序。 然后应用程序将会退出,安装的操作留给用户。
-
-### Error(错误)
-
-如果未找到合适的运行时间,则会向用户显示错误并且不采取进一步措施。
-
-## Fixed version runtime
-
-Another way of dealing with webview2 dependency is shipping it yourself. Another way of dealing with webview2 dependency is shipping it yourself. You can download [fixed version runtime](https://developer.microsoft.com/ru-ru/microsoft-edge/webview2/#download-section) and bundle or download it with your application. Another way of dealing with webview2 dependency is shipping it yourself. You can download [fixed version runtime](https://developer.microsoft.com/microsoft-edge/webview2/#download-section) and bundle or download it with your application.
-
-Also, you should specify path to fixed version of webview2 runtime in the `windows.Options` structure when launching wails.
-
-```go
- wails.Run(&options.App{
- Windows: &windows.Options{
- WebviewBrowserPath: "",
- },
- })
-```
-
-Note: When `WebviewBrowserPath` is specified, `error` strategy will be forced in case of minimal required version mismatch or invalid path to a runtime.
-
-## Spawning other programs
-
-When spawning other programs, such as scripts, you will see the window appear on the screen. To hide the window, you can use the following code:
-
-```go
-cmd := exec.Command("your_script.exe")
-cmd.SysProcAttr = &syscall.SysProcAttr{
- HideWindow: true,
- CreationFlags: 0x08000000,
-}
-cmd.Start()
-```
-
-Solution provided by [sithembiso](https://github.com/sithembiso) on the [discussions board](https://github.com/wailsapp/wails/discussions/1734#discussioncomment-3386172).
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/howdoesitwork.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/howdoesitwork.mdx
deleted file mode 100644
index 297b4087b..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/howdoesitwork.mdx
+++ /dev/null
@@ -1,435 +0,0 @@
----
-sidebar_position: 20
----
-
-# 它是如何工作的?
-
-Wails 应用程序是一个带有一个 webkit 前端的标准的 Go 应用程序。 应用程序的 Go 部分由应用程序代码和一个运行时库组成, 该库提供了许多有用的操作,例如控制应用程序窗口。 前端是一个 webkit 窗口,将显示前端资源。 前端还可以使用运行时库的 Javascript 版本。 最后,可以将 Go 方法绑定到前端,这些将显示为可以调用的 Javascript 方法,就像它们是原生 Javascript 方法一样。
-
-
-
-
-
-## 主应用程序
-
-### 概述
-
-主应用程序由对`wails.Run()`的调用组成。 它接受描述应用程序窗口大小、窗口标题、要使用的资源等应用程序配置。 基本应用程序可能如下所示:
-
-```go title="main.go"
-package main
-
-import (
- "embed"
- "log"
-
- "github.com/wailsapp/wails/v2"
- "github.com/wailsapp/wails/v2/pkg/options"
-)
-
-//go:embed frontend/dist
-var assets embed.FS
-
-func main() {
-
- app := &App{}
-
- err := wails.Run(&options.App{
- Title: "Basic Demo",
- Width: 1024,
- Height: 768,
- Assets: &assets,
- OnStartup: app.startup,
- OnShutdown: app.shutdown,
- Bind: []interface{}{
- app,
- },
- })
- if err != nil {
- log.Fatal(err)
- }
-}
-
-
-type App struct {
- ctx context.Context
-}
-
-func (b *App) startup(ctx context.Context) {
- b.ctx = ctx
-}
-
-func (b *App) shutdown(ctx context.Context) {}
-
-func (b *App) Greet(name string) string {
- return fmt.Sprintf("Hello %s!", name)
-}
-```
-
-### 选项概要
-
-此示例设置了以下选项:
-
-- `Title` - 应该出现在窗口标题栏中的文本
-- `Width&Height`- 窗口的尺寸
-- `Assets` - 应用程序的前端资源
-- `OnStartup` - 创建窗口并即将开始加载前端资源时的回调
-- `OnShutdown` - 应用程序即将退出时的回调
-- `Bind` - 我们希望向前端暴露的一部分结构体实例
-
-完整的应用程序参数选项列表可以在[参数选项](./reference/options)中找到。
-
-#### 资产
-
-`Assets` 选项是必须的,因为您不能拥有没有前端资源的 Wails 应用程序。 这些资源可以是您希望在 Web 应用程序中找到的任何文件 - html、js、css、svg、png 等。 **不需要生成资源包** - 纯文件即可。 当应用程序启动时,它将尝试从您的资源中加载`index.html`,并且那时起前端基本上将作为浏览器工作。 值得注意的是`embed.FS`对文件所在的位置没有要求。 嵌入路径很可能使用了相对于您的主应用程序代码的嵌套目录,例如 `frontend/dist`:
-
-```go title="main.go"
-//go:embed frontend/dist
-var assets embed.FS
-```
-
-启动时,Wails 将遍历嵌入的文件,寻找包含的`index.html`。 所有其他资源将相对于该目录加载。
-
-由于可用于生产的二进制文件使用包含在`embed.FS`中的文件,因此应用程序不需要附带任何外部文件。
-
-当使用`wails dev`命令在“开发”模式下,资源从磁盘加载,任何更改都会导致“实时重新加载”。 资产的位置将从 `embed.FS` 推断。
-
-更多细节可以在[应用程序开发指南](./guides/application-development)中找到。
-
-#### 应用程序生命周期回调
-
-在即将加载前端`index.html`之前,对 [应用启动回调](./reference/options#应用启动回调) 中提供的函数进行调用。 一个标准的 Go 上下文被传递给这个方法。 调用运行时需要此上下文,因此标准方式是保存此时对它的引用。 在应用程序关闭之前,再次使用上下文以同样的方式调用 [应用退出回调](./reference/options#应用退出回调)。 当前端完成加载`index.html`中所有资源时,还有一个 [前端 Dom 加载完成回调](./reference/options#前端-dom-加载完成回调) ,相当于 Javascript 中的`body onload`事件。 还可以通过设置 [关闭应用程序之前回调](./reference/options#关闭应用程序之前回调) 选项来控制窗口关闭(或应用程序退出)事件。
-
-#### 方法绑定
-
-`Bind`选项是 Wails 应用程序中最重要的参数选项之一。 它指定向前端暴露哪些结构方法。 想到传统的 web 应用程序中的 "Controllers" 。 当应用程序启动时,它会检查 `Bind` 中列出的结构实例, 确定哪些方法是公开的(以大写字母开头),并将生成前端可以调用的那些方法的 Javascript 版本。
-
-:::info 注意
-
-Wails 要求您传入结构的 _实例_ 才能正确绑定它
-
-:::
-
-在此示例中,我们创建一个新`App`实例,然后将此实例添加到`wails.Run`中的`Bind`选项:
-
-```go {16,24} title="main.go"
-package main
-
-import (
- "embed"
- "log"
-
- "github.com/wailsapp/wails/v2"
- "github.com/wailsapp/wails/v2/pkg/options"
-)
-
-//go:embed frontend/dist
-var assets embed.FS
-
-func main() {
-
- app := &App{}
-
- err := wails.Run(&options.App{
- Title: "Basic Demo",
- Width: 1024,
- Height: 768,
- Assets: &assets,
- Bind: []interface{}{
- app,
- },
- })
- if err != nil {
- log.Fatal(err)
- }
-}
-
-
-type App struct {
- ctx context.Context
-}
-
-func (a *App) Greet(name string) string {
- return fmt.Sprintf("Hello %s!", name)
-}
-```
-
-您可以绑定任意数量的结构体。 只需确保创建它的一个实例并将其传递给 `Bind`:
-
-```go {8-10}
- //...
- //...
- ...
- err := wails.Run(&options.App{
- Title: "Basic Demo",
- Width: 1024,
- Height: 768,
- Assets: &assets,
- OnStartup: app.startup,
- OnShutdown: app.shutdown,
- Bind: []interface{}{
- app,
- &mystruct1{},
- &mystruct2{},
- },
- })
-...
-
-```
-
-When you run `wails dev` (or `wails generate module`), a frontend module will be generated containing the following:
-
-- 调用绑定的 Go 方法
-- 调用运行时方法
-- Typescript definitions for all Go structs used as inputs or outputs by the bound methods
-
-This makes it incredibly simple to call Go code from the frontend, using the same strongly typed datastructures.
-
-## 前端
-
-### 概述
-
-前端是由 webkit 渲染的文件集合。 这就像浏览器和网络服务器合二为一。 您可以使用的框架或库[^1]几乎没有限制。 前端和 Go 代码之间的主要交互点是:
-
-- 调用绑定的 Go 方法
-- 调用运行时方法
-
-### 调用绑定的 Go 方法
-
-在`wails dev`模式下运行应用程序时,会生成一个 javascript 模块,该模块用 JSDoc 注释包装这些方法。 这确实有助于开发,尤其是因为大多数 IDE 将处理 JSDoc 以提供代码完成和类型提示。 该模块名为`go` 并在`wailsjsdir`标志指定的目录中生成。 The generated files mirror the package names in your application. 在上面的例子中,我们绑定 `app`,它有一个公开方法 `Greet`。 在上面的例子中,我们绑定 `app`,它有一个公开方法 `Greet`。 This will lead to the generation of the following files:
-
-```bash
-window.go.main.App.Greet("Bill").then((result) => {
- console.log("The greeting is: " + result);
- })
-```
-
-Here we can see that there is a `main` package that contains the Javascript bindings for the bound `App` struct, as well as the Typescript declaration file for those methods. To call `Greet` from our frontend, we simply import the method and call it like a regular Javascript function: 要从我们的前端调用 `Greet`,我们只需导入该方法并像普通的 Javascript 函数一样调用它:
-
-```javascript
-// ...
-// ...
-// ...
- // ...
- import {Greet} from '../wailsjs/go/main/App'
-
- function doGreeting(name) {
- Greet(name).then((result) => {
- // Do something with result
- })
- }
-```
-
-The Typescript declaration file gives you the correct types for the bound methods:
-
-```ts
-const go = {
- main: {
- App: {
- /**
- * Greet
- * @param {Person} arg1 - Go Type: string
- * @returns {Promise} - Go Type: string
- */
- Greet: (arg1) => {
- return window.go.main.App.Greet(arg1);
- },
- },
- },
-};
-export default go;
-```
-
-这些方法返回一个 Promise。 成功的调用将导致 Go 调用的第一个返回值被传递给 `resolve` 处理程序。 一个不成功的调用是将一个 Go 方法的第二个错误类型返回值通过`reject`传递回调用者。 这通过 `reject` 处理程序传回。 This is passed back via the `reject` handler. 在上面的例子中,Greet 只返回一个字符串,所以 `Javascript` 调用永远不会`reject` - 除非将无效数据传递给它。
-
-所有数据类型都在 Go 和 Javascript 之间正确转换。 包括结构体。 如果您从 Go 调用返回一个结构体,它将作为 `Javascript` Map 返回到您的前端。 注意:如果您想使用结构体,您必须为您的结构体字段定义`json` 标签!
-
-:::info 注意
-目前不支持嵌套匿名结构体。
-:::
-
-也可以将结构体发送回 Go。 任何作为期望结构的参数传递的 Javascript Map 都将转换为该结构类型。 为了使这个过程更容易,在 `开发`模式下,会生成一个 TypeScript 模块,定义绑定方法中使用的所有结构类型。 使用此模块,可以构建原生 Javascript 对象并将其发送到 Go 代码。
-
-还额外支持在其签名中使用结构的 Go 方法。 所有由绑定方法指定的 Go 结构体(作为参数或返回类型)都将自动生成 Typescript 版本作为 Go 代码包装器模块的一部分。 使用这些,可以在 Go 和 Javascript 之间共享相同的数据模型。
-
-此外`bindings.js`,还有一个名为`models.ts`的文件. 这包含我们 Go 结构体的 TypeScript 形式:
-
-```go title="main.go"
-type Person struct {
- Name string `json:"name"`
- Age uint8 `json:"age"`
- Address *Address `json:"address"`
-}
-
-type Address struct {
- Street string `json:"street"`
- Postcode string `json:"postcode"`
-}
-
-func (a *App) Greet(p Person) string {
- return fmt.Sprintf("Hello %s (Age: %d)!", p.Name, p.Age)
-}
-```
-
-只要您将 TypeScript 作为前端构建配置的一部分,您就可以通过以下方式使用这些模型:
-
-```js title="App.js"
-export class Address {
- street: string;
- postcode: string;
-
- static createFrom(source: any = {}) {
- return new Address(source);
- }
-
- constructor(source: any = {}) {
- if ("string" === typeof source) source = JSON.parse(source);
- this.street = source["street"];
- this.postcode = source["postcode"];
- }
-}
-export class Person {
- name: string;
- age: number;
- address?: Address;
-
- static createFrom(source: any = {}) {
- return new Person(source);
- }
-
- constructor(source: any = {}) {
- if ("string" === typeof source) source = JSON.parse(source);
- this.name = source["name"];
- this.age = source["age"];
- this.address = this.convertValues(source["address"], Address);
- }
-
- convertValues(a: any, classs: any, asMap: boolean = false): any {
- if (!a) {
- return a;
- }
- if (a.slice) {
- return (a as any[]).map((elem) => this.convertValues(elem, classs));
- } else if ("object" === typeof a) {
- if (asMap) {
- for (const key of Object.keys(a)) {
- a[key] = new classs(a[key]);
- }
- return a;
- }
- return new classs(a);
- }
- return a;
- }
-}
-```
-
-JSDoc 和 TypeScript 生成模型的组合构成了一个强大的开发环境。
-
-```ts title="App.d.ts"
-import go from "./wailsjs/go/bindings";
-import { Person } from "./wailsjs/go/models";
-
-let name = "";
-
-function greet(name) {
- let p = new Person();
- p.name = name;
- p.age = 42;
- go.main.App.Greet(p).then((result) => {
- console.log(result);
- });
-}
-```
-
-As we can see, the "main" namespace is imported from a new "models.ts" file. This file contains all the struct definitions used by our bound methods. In this example, this is a `Person` struct. If we look at `models.ts`, we can see how the models are defined: 该文件包含我们绑定方法使用的所有结构定义。 在这个示例中,这是一个 `Person` 结构体。 如果我们查看 `models.ts`,我们可以看到模型是如何定义的:
-
-```ts title="models.ts"
-export namespace main {
-
- export class Address {
- street: string;
- postcode: string;
-
- static createFrom(source: any = {}) {
- return new Address(source);
- }
-
- constructor(source: any = {}) {
- if ('string' === typeof source) source = JSON.parse(source);
- this.street = source["street"];
- this.postcode = source["postcode"];
- }
- }
- export class Person {
- name: string;
- age: number;
- address?: Address;
-
- static createFrom(source: any = {}) {
- return new Person(source);
- }
-
- constructor(source: any = {}) {
- if ('string' === typeof source) source = JSON.parse(source);
- this.name = source["name"];
- this.age = source["age"];
- this.address = this.convertValues(source["address"], Address);
- }
-
- convertValues(a: any, classs: any, asMap: boolean = false): any {
- if (!a) {
- return a;
- }
- if (a.slice) {
- return (a as any[]).map(elem => this.convertValues(elem, classs));
- } else if ("object" === typeof a) {
- if (asMap) {
- for (const key of Object.keys(a)) {
- a[key] = new classs(a[key]);
- }
- return a;
- }
- return new classs(a);
- }
- return a;
- }
- }
-}
-```
-
-可以在[运行时参考](./reference/runtime/intro)中找到有关 JS 运行时的更多详细信息。
-
-```js title="mycode.js"
-const go = {
- main: {
- App: {
- /**
- * Greet
- * @param {Person} arg1 - Go Type: main.Person
- * @returns {Promise} - Go Type: string
- */
- Greet: (arg1) => {
- return window.go.main.App.Greet(arg1);
- },
- },
- },
-};
-export default go;
-```
-
-The combination of generated bindings and TypeScript models makes for a powerful development environment.
-
-关于绑定的更多信息可以在[应用程序开发指南](./guides/application-development)的[绑定方法](./guides/application-development#绑定方法)一节中找到。
-
-### 调用运行时方法
-
-Javascript 运行时位于`window.runtime`并包含许多方法来执行各种任务,例如发出事件或执行日志记录操作:
-
-```js title="mycode.js"
-window.runtime.EventsEmit("my-event", 1);
-```
-
-More details about the JS runtime can be found in the [Runtime Reference](reference/runtime/intro).
-
-[^1]: 有一小部分库使用了 WebView 中不支持的功能。 对于这种情况,通常有替代方案和解决方法。
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/introduction.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/introduction.mdx
deleted file mode 100644
index 8c191a7aa..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/introduction.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-sidebar_position: 1
----
-
-# 简介
-
-Wails 是一个可让您使用 Go 和 Web 技术编写桌面应用的项目。
-
-将它看作为 Go 的快并且轻量的 Electron 替代品。 您可以使用 Go 的灵活性和强大功能,结合丰富的现代前端,轻松的构建应用程序。
-
-### 功能
-
-- 原生菜单、对话框、主题和半透明
-- Windows、macOS 和 linux 支持
-- 内置 Svelte、React 、Preact 、Vue、Lit 和 Vanilla JS 的模板
-- 从 Javascript 轻松调用 Go 方法
-- 自动将Go结构体转换为TypeScript模块
-- Windows 上不需要 CGO 或外部 DLL
-- 使用 [Vite ](https://vite.net/) 的实时开发模式
-- 可以轻松创建、构建和打包应用的强大命令行工具
-- 丰富的 [运行时库](/docs/next/reference/runtime)
-- Applications built with Wails are Apple & Microsoft Store compliant
-
-
-这是 [varly](https://varly.app) - 一个使用 Wails 编写的 MacOS 和 Windows 桌面应用。 它不仅看起来很强,它使用原生菜单和半透明 - 你希望从现代原生应用中得到的一切
-
-
-
-
-
-
-
-#### Mac
-
-Mac 对话框只有一组模式来过滤文件的概念。 如果提供了多个 FileFilters,Wails 将使用所有定义的模式。
-
-示例:
-
-```go
- selection, err := runtime.OpenFileDialog(b.ctx, runtime.OpenDialogOptions{
- Title: "Select File",
- Filters: []runtime.FileFilter{
- {
- DisplayName: "Images (*.png;*.jpg)",
- Pattern: "*.png;*.jpg",
- }, {
- DisplayName: "Videos (*.mov;*.mp4)",
- Pattern: "*.mov;*.mp4",
- },
- },
- })
-```
-
-这将导致使用`*.png,*.jpg,*.mov,*.mp4`作为过滤器打开文件对话框。
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/events.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/events.mdx
deleted file mode 100644
index 8d21f7bee..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/events.mdx
+++ /dev/null
@@ -1,38 +0,0 @@
----
-sidebar_position: 2
----
-
-# 事件
-
-Wails 运行时提供了一个统一的事件系统,其中事件可以由 Go 或 Javascript 发出或接收。 可选地,数据可以与事件一起传递。 侦听器将接收本地数据类型中的数据。
-
-### 添加事件侦听器
-
-此方法为给定的事件名称设置一个侦听器。 当一个`eventName`类型的事件被[触发指定事件](#触发指定事件)时,回调被触发。 与触发事件一起发送的任何其他数据都将传递给回调。
-
-Go: `EventsOn(ctx context.Context, eventName string, callback func(optionalData ...interface{}))` JS: `EventsOn(eventName string, callback function(optionalData?: any))`
-
-### 移除事件侦听器
-
-This method unregisters the listener for the given event name, optionally multiple listeneres can be unregistered via `additionalEventNames`.
-
-Go: `EventsOff(ctx context.Context, eventName string, additionalEventNames ...string)` JS: `EventsOff(eventName string, ...additionalEventNames)`
-
-### 添加只触发一次的事件侦听器
-
-此方法为给定的事件名称设置一个侦听器,但只会触发一次。
-
-Go: `EventsOnce(ctx context.Context, eventName string, callback func(optionalData ...interface{}))` JS: `EventsOnce(eventName string, callback function(optionalData?: any))`
-
-### 添加指定对多触发次数的事件侦听器
-
-此方法为给定的事件名称设置一个侦听器,但最多只能触发`counter`次。
-
-Go: `EventsOnMultiple(ctx context.Context, eventName string, callback func(optionalData ...interface{}), counter int)` JS: `EventsOnMultiple(eventName string, callback function(optionalData?: any), counter int)`
-
-### 触发指定事件
-
-此方法触发指定的事件。 可选数据可以与事件一起传递。 这将触发任何事件侦听器。
-
-Go: `EventsEmit(ctx context.Context, eventName string, optionalData ...interface{})` JS: `EventsEmit(ctx context, optionalData function(optionalData?: any))`
-
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/intro.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/intro.mdx
deleted file mode 100644
index 24f60593f..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/intro.mdx
+++ /dev/null
@@ -1,73 +0,0 @@
----
-sidebar_position: 1
----
-
-# 介绍
-
-运行时是一个为应用程序提供实用方法的库。 有 Go 和 Javascript 运行时,目的是在可能的情况下尝试使它们保持一致。
-
-It has utility methods for:
-
-- [Window](window.mdx)
-- [Menu](menu.mdx)
-- [Dialog](dialog.mdx)
-- [Events](events.mdx)
-- [Browser](browser.mdx)
-- [Log](log.mdx)
-
-Go 运行时可通过导入`github.com/wailsapp/wails/v2/pkg/runtime`。 此包中的所有方法都将 context 作为第一个参数。 此 context 应该从 [应用启动回调](../options.mdx#onstartup) 或 [前端 Dom 加载完成回调](../options.mdx#ondomready) 钩子获得。
-
-:::info 注意
-
-虽然上下文将提供给[应用启动回调](../../reference/options#应用启动回调)方法,但不能保证运行时将在此方法中工作,因为窗口正在不同的线程中初始化。 如果您希望在启动时调用运行时方法,请使用[前端 Dom 加载完成回调](../../reference/options#前端-dom-加载完成回调)方法。
-
-:::
-
-Javascript 库可通过`window.runtime`提供给前端。 使用 `开发` 模式时会生成一个运行时包,该包为运行时提供 Typescript 声明。 这应该位于您的前端目录中的`wailsjs`目录中。
-
-### 隐藏
-
-Go: `Hide(ctx context.Context)` JS: `Hide()`
-
-隐藏应用程序。
-
-:::info Note On Mac, this will hide the application in the same way as the `Hide` menu item in standard Mac applications. This is different to hiding the window, but the application still being in the foreground. For Windows and Linux, this is currently the same as `WindowHide`. ::: This is different to hiding the window, but the application still being in the foreground. For Windows and Linux, this is currently the same as `WindowHide`. :::
-
-### 环境
-
-Shows the application.
-
-:::info Note On Mac, this will bring the application back into the foreground. For Windows and Linux, this is currently the same as `WindowShow`. ::: :::info Note On Mac, this will bring the application back into the foreground. For Windows and Linux, this is currently the same as `WindowShow`. ::: For Windows and Linux, this is currently the same as `WindowShow`. ::: :::
-
-Go: `Show(ctx context.Context)` JS: `Show()`
-
-### Quit
-
-Quits the application.
-
-Go: `Quit(ctx context.Context)` JS: `Quit()`
-
-### Environment
-
-Returns details of the current environment.
-
-Go: `Environment(ctx context.Context) EnvironmentInfo` JS: `Environment(): Promise`
-
-#### 环境信息
-
-Go:
-```go
-type EnvironmentInfo struct {
- BuildType string
- Platform string
- Arch string
-}
-```
-JS:
-```ts
-interface EnvironmentInfo {
- buildType: string;
- platform: string;
- arch: string;
-}
-```
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/log.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/log.mdx
deleted file mode 100644
index 2b717aa52..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/log.mdx
+++ /dev/null
@@ -1,130 +0,0 @@
----
-sidebar_position: 3
----
-
-# 日志
-
-Wails 运行时提供了一种可以从 Go 或 Javascript 调用的日志记录机制。 像大多数记录器一样,有许多日志级别:
-
-- Trace
-- Debug
-- Info
-- Warning
-- Error
-- Fatal
-
-记录器将输出当前或更高日志级别的任何日志消息。 示例:`Debug`日志级别将输出除`Trace`消息之外的所有消息。
-
-### 打印日志
-
-将给定的消息记录为原始消息。
-
-Go: `LogPrint(ctx context.Context, message string)` JS: `LogPrint(message: string)`
-
-### 格式化打印日志
-
-将给定的消息记录为原始消息。
-
-Go: `LogPrintf(ctx context.Context, format string, args ...interface{})`
-
-### Trace 日志
-
-在`Trace`日志级别记录给定的消息。
-
-Go: `LogTrace(ctx context.Context, message string)` JS: `LogTrace(message: string)`
-
-### 格式化 Trace 日志
-
-在`Trace`日志级别记录给定的消息。
-
-Go: `LogTracef(ctx context.Context, format string, args ...interface{})`
-
-### Debug 日志
-
-在`Debug`日志级别记录给定的消息。
-
-Go: `LogDebug(ctx context.Context, message string)` JS: `LogDebug(message: string)`
-
-### 格式化 Debug 日志
-
-在`Debug`日志级别记录给定的消息。
-
-Go: `LogDebugf(ctx context.Context, format string, args ...interface{})`
-
-### Info 日志
-
-在`Info`日志级别记录给定的消息。
-
-Go: `LogInfo(ctx context.Context, message string)` JS: `LogInfo(message: string)`
-
-### 格式化 Info 日志
-
-在`Info`日志级别记录给定的消息。
-
-Go: `LogInfof(ctx context.Context, format string, args ...interface{})`
-
-### Warning 日志
-
-在`Warning`日志级别记录给定的消息。
-
-Go: `LogWarning(ctx context.Context, message string)` JS: `LogWarning(message: string)`
-
-### 格式化 Warning 日志
-
-在`Warning`日志级别记录给定的消息。
-
-Go: `LogWarningf(ctx context.Context, format string, args ...interface{})`
-
-### Error 日志
-
-在`Error`日志级别记录给定的消息。
-
-Go: `LogError(ctx context.Context, message string)` JS: `LogError(message: string)`
-
-### 格式化 Error 日志
-
-在`Error`日志级别记录给定的消息。
-
-Go: `LogErrorf(ctx context.Context, format string, args ...interface{})`
-
-### Fatal 日志
-
-在`Fatal`日志级别记录给定的消息。
-
-Go: `LogFatal(ctx context.Context, message string)` JS: `LogFatal(message: string)`
-
-### 格式化 Fatal 日志
-
-在`Fatal`日志级别记录给定的消息。
-
-Go: `LogFatalf(ctx context.Context, format string, args ...interface{})`
-
-### 设置日志级别
-
-设置日志级别。 在 Javascript 中,该数字与以下日志级别有关:
-
-| 值 | 日志等级 |
-| - | ------- |
-| 1 | Trace |
-| 2 | Debug |
-| 3 | Info |
-| 4 | Warning |
-| 5 | Error |
-
-Go: `LogSetLogLevel(ctx context.Context, level logger.LogLevel)` JS: `LogSetLogLevel(level: number)`
-
-## 使用自定义日志
-
-可以通过使用应用程序参数选项 [日志](../../reference/options#日志) 提供自定义记录器来使用它。 唯一的要求是记录器实现了在`github.com/wailsapp/wails/v2/pkg/logger`里`logger.Logger`定义的接口:
-
-```go title="logger.go"
-type Logger interface {
- Print(message string)
- Trace(message string)
- Debug(message string)
- Info(message string)
- Warning(message string)
- Error(message string)
- Fatal(message string)
-}
-```
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/menu.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/menu.mdx
deleted file mode 100644
index 4ce2b368e..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/menu.mdx
+++ /dev/null
@@ -1,24 +0,0 @@
----
-sidebar_position: 6
----
-
-# 菜单
-
-这些方法与应用程序菜单相关。
-
-:::info Javascript
- Menu is currently unsupported in the JS runtime.
-::: :::
-::: :::
-
-### 设置应用程序菜单
-
-Sets the application menu to the given [menu](../menus.mdx).
-
-Go: `MenuSetApplicationMenu(ctx context.Context, menu *menu.Menu)`
-
-### 更新应用程序菜单
-
-将应用程序菜单设置为给定的[应用菜单](../../reference/menus)。
-
-Go: `MenuUpdateApplicationMenu(ctx context.Context)`
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/window.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/window.mdx
deleted file mode 100644
index e26776d0c..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/reference/runtime/window.mdx
+++ /dev/null
@@ -1,213 +0,0 @@
----
-sidebar_position: 4
----
-
-# 窗口
-
-这些方法可以控制应用程序窗口。
-
-### 窗口标题
-
-设置窗口标题栏中的文本。
-
-Go: `WindowSetTitle(ctx context.Context, title string)` JS: `WindowSetTitle(title: string)`
-
-### 窗口全屏
-
-使窗口全屏。
-
-Go: `WindowFullscreen(ctx context.Context)` JS: `WindowFullscreen()`
-
-### 窗口取消全屏
-
-在全屏之前恢复先前的窗口尺寸和位置。
-
-Go: `WindowUnfullscreen(ctx context.Context)` JS: `WindowUnfullscreen()`
-
-### 窗口居中
-
-使窗口在当前窗口所在的监视器上居中。
-
-Go: `WindowCenter(ctx context.Context)` JS: `WindowCenter()`
-
-### 窗口居中
-
-使窗口在当前窗口所在的监视器上居中。
-
-Go: `WindowReload(ctx context.Context)` JS: `WindowReload()`
-
-### 窗口重新加载
-
-执行“重新加载”(重新加载 index.html)
-
-Go: `WindowReloadApp(ctx context.Context)` JS: `WindowReloadApp()`
-
-### 窗口设置系统默认主题
-
-仅限 Windows。
-
-Go: `WindowSetSystemDefaultTheme(ctx context.Context)` JS: `WindowSetSystemDefaultTheme()`
-
-### 窗口设置深色主题
-
-JS 方法签名: `WindowSetLightTheme()`
-
-JS 方法签名: `WindowSetLightTheme()`
-
-仅限 Windows。
-
-### 显示窗口
-
-JS 方法签名: `WindowSetLightTheme()`
-
-JS 方法签名: `WindowSetLightTheme()`
-
-仅限 Windows。
-
-### 隐藏窗口
-
-JS 方法签名: `WindowSetLightTheme()`
-
-隐藏窗口(如果当前可见)。
-
-如果窗口当前处于隐藏状态,则显示该窗口。
-
-### 设置窗口尺寸
-
-隐藏窗口(如果当前可见)。
-
-Go: `WindowHide(ctx context.Context)` JS: `WindowHide()`
-
-### 获取窗口尺寸
-
-设置窗口的宽度和高度。
-
-Go: `WindowSetSize(ctx context.Context, width int, height int)` JS: `WindowSetSize(size: Size)`
-
-### 设置窗口最大尺寸
-
-Returns true if the window not minimised, maximised or fullscreen.
-
-Go: `WindowGetSize(ctx context.Context) (width int, height int)` JS: `WindowGetSize() : Size`
-
-### 设置窗口最小尺寸
-
-获取窗口的宽度和高度。
-
-Go: `WindowSetMinSize(ctx context.Context, width int, height int)` JS: `WindowSetMinSize(size: Size)`
-
-### 设置窗口最大尺寸
-
-Gets the width and height of the window.
-
-Go: `WindowSetAlwaysOnTop(ctx context.Context, b bool)` JS: `WindowSetAlwaysOnTop(b: Boolen)`
-
-### 设置窗口位置
-
-设置最小窗口大小。 如果窗口当前小于给定尺寸,将调整窗口大小。
-
-Setting a size of `0,0` will disable this constraint.
-
-获取相对于窗口当前所在显示器的窗口位置。
-
-### 获取窗口位置
-
-设置最大窗口大小。 如果窗口当前大于给定尺寸,将调整窗口大小。
-
-Setting a size of `0,0` will disable this constraint.
-
-Go: `WindowSetPosition(ctx context.Context, x int, y int)` JS: `WindowSetPosition(position: Position)`
-
-### 窗口最大化
-
-获取相对于窗口当前所在显示器的窗口位置。
-
-Go: `WindowGetPosition(ctx context.Context) (x int, y int)` JS: `WindowGetPosition() : Position`
-
-### 窗口取消最大化
-
-最大化窗口以填满屏幕。
-
-Go: `WindowMaximise(ctx context.Context)` JS: `WindowMaximise()`
-
-### 窗口最大化切换
-
-将窗口恢复到最大化之前的尺寸和位置。
-
-Go: `WindowUnmaximise(ctx context.Context)` JS: `WindowUnmaximise()`
-
-### 窗口最小化
-
-在最大化和最大化之间切换。
-
-Go: `WindowToggleMaximise(ctx context.Context)` JS: `WindowToggleMaximise()`
-
-### 窗口取消最小化
-
-最小化窗口。
-
-Go: `WindowMinimise(ctx context.Context)` JS: `WindowMinimise()`
-
-### 尺寸
-
-Returns true if the window is maximised.
-
-Go: `WindowUnminimise(ctx context.Context)` JS: `WindowUnminimise()`
-
-### 窗口设置 RGBA
-
-将窗口恢复到最小化之前的尺寸和位置。
-
-Go: `WindowToggleMaximise(ctx context.Context)` JS: `WindowToggleMaximise()`
-
-### 位置
-
-窗口
-
-Go: `WindowSetBackgroundColour(ctx context.Context, R, G, B, A uint8)` JS: `WindowSetBackgroundColour(R, G, B, A)`
-
-### 尺寸
-
-Restores the window to the dimensions and position prior to minimising.
-
-Go: `WindowUnminimise(ctx context.Context)` JS: `WindowUnminimise()`
-
-### WindowIsMinimised
-
-Returns true if the window is minimised.
-
-Go: `WindowIsMinimised(ctx context.Context) bool` JS: `WindowIsMinimised() bool`
-
-### WindowSetBackgroundColour
-
-将窗口的背景颜色设置为给定的 RGBA 颜色定义。 此颜色将显示所有透明像素。
-
-Valid values for R, G, B and A are 0-255.
-
-:::info Windows
-On Windows, only alpha values of 0 or 255 are supported.
-任何不为 0 的值都将被视为 255。
-任何不为 0 的值都将被视为 255。
-:::
-
-Go: `WindowSetBackgroundColour(ctx context.Context, R, G, B, A uint8)` JS: `WindowSetBackgroundColour(R, G, B, A)`
-
-## Typescript 对象定义
-
-### Position
-
-```ts
-interface Position {
- x: number;
- y: number;
-}
-```
-
-### Size
-
-```ts
-interface Size {
- w: number;
- h: number;
-}
-```
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/tutorials/_category_.json b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/tutorials/_category_.json
deleted file mode 100644
index dfac1d175..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/tutorials/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Tutorials",
- "position": 70
-}
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/tutorials/dogsapi.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/tutorials/dogsapi.mdx
deleted file mode 100644
index f4845fdbe..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/tutorials/dogsapi.mdx
+++ /dev/null
@@ -1,243 +0,0 @@
----
-sidebar_position: 20
----
-
-# Dogs API
-
-
-
-
-
-
-
-:::note This tutorial has been kindly provided by [@tatadan](https://twitter.com/tatadan) and forms part of their [Wails Examples Repository](https://github.com/tataDan/wails-v2-examples). :::
-
-In this tutorial we are going to develop an application that retrieves photos of dogs from the web and then displays them.
-
-### Create the project
-
-Let's create the application. From a terminal enter: `wails init -n dogs-api -t svelte`
-
-Note: We could optionally add `-ide vscode` or `-ide goland` to the end of this command if you wanted to add IDE support.
-
-Now let's `cd dogs-api` and start editing the project files.
-
-### Remove unused code
-
-We will start by removing some elements that we know we will not use:
-
-- Open `app.go` and remove the following lines:
-
-```go
-// Greet returns a greeting for the given name
-func (a *App) Greet(name string) string {
- return fmt.Sprintf("Hello %s, It's show time!", name)
-}
-```
-
-- Open `frontend/src/App.svelte` and delete all lines.
-- Delete the `frontend/src/assets/images/logo-universal.png` file
-
-### Creating our application
-
-Now let's add our new Go code.
-
-Add the following struct declarations to `app.go` before the function definitions:
-
-```go
-type RandomImage struct {
- Message string
- Status string
-}
-
-type AllBreeds struct {
- Message map[string]map[string][]string
- Status string
-}
-
-type ImagesByBreed struct {
- Message []string
- Status string
-}
-```
-
-Add the following functions to `app.go` (perhaps after the existing function definitions):
-
-```go
-func (a *App) GetRandomImageUrl() string {
- response, err := http.Get("https://dog.ceo/api/breeds/image/random")
- if err != nil {
- log.Fatal(err)
- }
-
- responseData, err := ioutil.ReadAll(response.Body)
- if err != nil {
- log.Fatal(err)
- }
-
- var data RandomImage
- json.Unmarshal(responseData, &data)
-
- return data.Message
-}
-
-func (a *App) GetBreedList() []string {
- var breeds []string
-
- response, err := http.Get("https://dog.ceo/api/breeds/list/all")
- if err != nil {
- log.Fatal(err)
- }
-
- responseData, err := ioutil.ReadAll(response.Body)
- if err != nil {
- log.Fatal(err)
- }
-
- var data AllBreeds
- json.Unmarshal(responseData, &data)
-
- for k := range data.Message {
- breeds = append(breeds, k)
- }
-
- sort.Strings(breeds)
-
- return breeds
-}
-
-func (a *App) GetImageUrlsByBreed(breed string) []string {
-
- url := fmt.Sprintf("%s%s%s%s", "https://dog.ceo/api/", "breed/", breed, "/images")
- response, err := http.Get(url)
- if err != nil {
- log.Fatal(err)
- }
-
- responseData, err := ioutil.ReadAll(response.Body)
- if err != nil {
- log.Fatal(err)
- }
-
- var data ImagesByBreed
- json.Unmarshal(responseData, &data)
-
- return data.Message
-}
-```
-
-Modify the `import` section of `app.go` to look like this:
-
-```go
-import (
- "context"
- "fmt"
- "encoding/json"
- "io/ioutil"
- "log"
- "net/http"
- "sort"
-)
-```
-
-Add the following lines to `frontend/src/App.svelte`:
-
-```html
-
-
-
Dogs API
-
-
- Click on down arrow to select a breed
-
-
-
-
-{#if showRandomPhoto}
-
-{/if}
-{#if showBreedPhotos}
- {#each photos as photo}
-
- {/each}
-{/if}
-
-
-```
-
-### Testing the application
-
-To generate the bindings and test the application, run `wails dev`.
-
-### Compiling the application
-
-To compile the application to a single, production grade binary, run `wails build`.
-
-
-
-
-
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/tutorials/helloworld.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/tutorials/helloworld.mdx
deleted file mode 100644
index 034c44fd6..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0-rc.1/tutorials/helloworld.mdx
+++ /dev/null
@@ -1,117 +0,0 @@
----
-sidebar_position: 10
----
-
-# 你好世界
-
-本教程的目的是让你使用最基本的 软件来运行和使用Wails。 你将可以:
-
-- 创建一个新的Wails应用
-- 构建应用
-- 运行应用
-
-:::note
-本教程使用 Windows 作为目标平台。 根据您的操作系统,输出会略有不同。
-:::
-
-## 创建一个新Wails应用
-
-使用默认的vanilla JS模板创建新的Wails程序, 您需要运行这个指令:
-
-```bash
-wails init -n helloworld
-```
-
-您应该会看到如下输出:
-
-```
-Wails CLI v2.0.0
-
-Initialising Project 'helloworld'
----------------------------------
-
-Project Name: helloworld
-Project Directory: C:\Users\leaan\tutorial\helloworld
-Project Template: vanilla
-Template Support: https://wails.io
-
-Initialised project 'helloworld' in 232ms.
-```
-
-这将在当前目录中创建一个名为 `helloworld` 的新目录。 在这个目录中,您会找到一些文件:
-
-```
-build/ - Contains the build files + compiled application
-frontend/ - Contains the frontend files
-app.go - Contains the application code
-main.go - The main program with the application configuration
-wails.json - The project configuration file
-go.mod - The go module file
-go.sum - The go module checksum file
-```
-
-## 构建应用
-
-要构建应用程序,请切换到新的 `helloword` 项目目录并运行以下命令:
-
-```bash
-wails build
-```
-
-您应该会看到如下输出:
-
-```
-Wails CLI v2.0.0
-
-App Type: desktop
-Platforms: windows/amd64
-Compiler: C:\Users\leaan\go\go1.18.3\bin\go.exe
-Build Mode: Production
-Skip Frontend: false
-Compress: false
-Package: true
-Clean Build Dir: false
-LDFlags: ""
-Tags: []
-Race Detector: false
-
-Building target: windows/amd64
-------------------------------
- - Installing frontend dependencies: Done.
- - Compiling frontend: Done.
- - Generating bundle assets: Done.
- - Compiling application: Done.
-Built 'C:\Users\leaan\tutorial\helloworld\build\bin\helloworld.exe' in 10.616s.
-```
-
-这有一个已经编译了的应用程序保存在 `build/bin` 目录中。
-
-## 运行应用
-
-如果我们在 Windows 文件管理器中查看 `build/bin` 目录,我们应该看到我们的项目二进制文件:
-
-
-```
-
-[EmailIt](https://github.com/raguay/EmailIt/) is a Wails 2 program that is a markdown based email sender only with nine notepads, scripts to manipulate the text, and templates. It also has a builtin [Node-Red](https://nodered.org/) server, scripts terminal, and the [ScriptBar](https://github.com/raguay/ScriptBarApp) program for displaying results from Node-Red or a script on your system. Documentation is very scarce, but the programs works. It’s built using Wails2 and Svelte, and the download is a universal macOS application.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/encrypteasy.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/encrypteasy.mdx
deleted file mode 100644
index 7504950ea..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/encrypteasy.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
-# EncryptEasy
-
-```mdx-code-block
-
-
-
-
-```
-
-**[EncryptEasy](https://www.encrypteasy.app) is a simple and easy to use PGP encryption tool, managing all your and your contacts keys. Encryption should be simple. Developed with Wails.**
-
-Encrypting messages using PGP is the industry standard. Everyone has a private and a public key. Your private key, well, needs to be kept private so only you can read messages. Your public key is distributed to anyone who wants to send you secret, encrypted messages. Managing keys, encrypting messages and decrypting messages should be a smooth experience. EncryptEasy is all about making it easy.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/filehound.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/filehound.mdx
deleted file mode 100644
index 134365aaf..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/filehound.mdx
+++ /dev/null
@@ -1,16 +0,0 @@
-# FileHound Export Utility
-
-```mdx-code-block
-
-
-
-
-```
-
-[FileHound Export Utility](https://www.filehound.co.uk/) FileHound is a cloud document management platform made for secure file retention, business process automation and SmartCapture capabilities.
-
-The FileHound Export Utility allows FileHound Administrators the ability to run a secure document and data extraction tasks for alternative back-up and recovery purposes. This application will download all documents and/or meta data saved in FileHound based on the filters you choose. The metadata will be exported in both JSON and XML formats.
-
-Backend built with: Go 1.15 Wails 1.11.0 go-sqlite3 1.14.6 go-linq 3.2
-
-Frontend with: Vue 2.6.11 Vuex 3.4.0 Typescript Tailwind 1.9.6
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/minecraftupdater.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/minecraftupdater.mdx
deleted file mode 100644
index 2f6c7c72b..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/minecraftupdater.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
-# Minecraft Updater
-
-```mdx-code-block
-
-
-
-
-```
-
-[Minecraft Updater](https://github.com/Gurkengewuerz/MinecraftModUpdater) is a utility tool to update and synchronize Minecraft mods for your userbase. It’s built using Wails2 and React with [antd](https://ant.design/) as frontend framework.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/modalfilemanager.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/modalfilemanager.mdx
deleted file mode 100644
index f8e2bcd66..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/modalfilemanager.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
-# Modal File Manager
-
-```mdx-code-block
-
-
-
-
-```
-
-[Modal File Manager](https://github.com/raguay/ModalFileManager) is a dual pane file manager using web technologies. My original design was based on NW.js and can be found [here](https://github.com/raguay/ModalFileManager-NWjs). This version uses the same Svelte based frontend code (but it has be greatly modified since the departure from NW.js), but the backend is a [Wails 2](https://wails.io/) implementation. By using this implementation, I no longer use command line `rm`, `cp`, etc. commands. It is fully coded using Go and runs much faster than the previous versions.
-
-This file manager is designed around the same principle as Vim: a state controlled keyboard actions. The number of states isn't fixed, but very programmable. Therefore, an infinite number of keyboard configurations can be created and used. This is the main difference from other file managers.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/mollywallet.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/mollywallet.mdx
deleted file mode 100644
index 5d846d06d..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/mollywallet.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Molley Wallet
-
-```mdx-code-block
-
-
-
-
-```
-
-[Molly Wallet](https://github.com/grvlle/constellation_wallet/) the official $DAG wallet of the Constellation Network. It'll let users interact with the Hypergraph Network in various ways, not limited to producing $DAG transactions.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/october.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/october.mdx
deleted file mode 100644
index 66d634dc5..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/october.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
-# October
-
-```mdx-code-block
-
-
-
-
-```
-
-[October](https://october.utf9k.net) is a small Wails application that makes it really easy to extract highlights from [Kobo eReaders](https://en.wikipedia.org/wiki/Kobo_eReader) and then forward them to [Readwise](https://readwise.io).
-
-It has a relatively small scope with all platform versions weighing in under 10MB, and that's without enabling [UPX compression](https://upx.github.io/)!
-
-In contrast, the author's previous attempts with Electron quickly bloated to several hundred megabytes.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/optimus.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/optimus.mdx
deleted file mode 100644
index 4f87479d6..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/optimus.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Optimus
-
-```mdx-code-block
-
-
-
-
-```
-
-[Optimus](https://github.com/splode/optimus) is a desktop image optimization application. It supports conversion and compression between WebP, JPEG, and PNG image formats.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/portfall.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/portfall.mdx
deleted file mode 100644
index 03e740f4c..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/portfall.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Portfall
-
-```mdx-code-block
-
-
-
-
-```
-
-[Portfall](https://github.com/rekon-oss/portfall) - A desktop k8s port-forwarding portal for easy access to all your cluster UIs
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/restic-browser.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/restic-browser.mdx
deleted file mode 100644
index 3646384ec..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/restic-browser.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
-# Restic Browser
-
-```mdx-code-block
-
-
-
-
-```
-
-[Restic-Browser](https://github.com/emuell/restic-browser) - A simple, cross-platform [restic](https://github.com/restic/restic) backup GUI for browsing and restoring restic repositories.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/scriptbar.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/scriptbar.mdx
deleted file mode 100644
index 2ccb2acb4..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/scriptbar.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# ScriptBar
-
-```mdx-code-block
-
-
-
-
-```
-
-[ScriptBar](https://GitHub.com/raguay/ScriptBarApp) is a program to show the output of the embedded [Node-Red](https://nodered.org) server in the [EmailIt](https://GitHub.com/raguay/EmailIt) application. It also displays the output of scripts on your system. ScriptBar doesn't put them in the menubar, but has them all in a convient window for easy viewing. You can have multiple tabs to have many different things show. You can also keep the links to your most visited web sites.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/surge.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/surge.mdx
deleted file mode 100644
index c3b3fb4c0..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/surge.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Surge
-
-```mdx-code-block
-
-
-
-
-```
-
-[Surge](https://getsurge.io/) is a p2p filesharing app designed to utilize blockchain technologies to enable 100% anonymous file transfers. Surge is end-to-end encrypted, decentralized and open source.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/wally.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/wally.mdx
deleted file mode 100644
index 7408aa585..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/wally.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Wally
-
-```mdx-code-block
-
-
-
-
-```
-
-[Wally](https://ergodox-ez.com/pages/wally) is the official firmware flasher for [Ergodox](https://ergodox-ez.com/) keyboards. It looks great and is a fantastic example of what you can achieve with Wails: the ability to combine the power of Go and the rich graphical tools of the web development world.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/wombat.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/wombat.mdx
deleted file mode 100644
index f100c55e2..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/community/showcase/wombat.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Wombat
-
-```mdx-code-block
-
-```
-
-[Ytd](https://github.com/marcio199226/ytd/tree/v2-wails) is an app for downloading tracks from youtube, creating offline playlists and share them with your friends, your friends will be able to playback your playlists or download them for offline listening, has an built-in player.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/community/templates.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/community/templates.mdx
deleted file mode 100644
index 133fc48b9..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/community/templates.mdx
+++ /dev/null
@@ -1,54 +0,0 @@
----
-sidebar_position: 1
----
-
-# 模板
-
-此页面用作社区支持的模板列表。 请提交一个包含您的模板的 PR(点击页面底部的 `编辑此页`)。 要构建您自己的模板,请参考 [模板](../guides/templates) 指南。
-
-要使用这些模板,请运行 `wails init -n "您的项目名" -t [下面的链接[@版本]]`
-
-如果不带版本后缀,默认使用的是主分支代码模板。 如果带有版本后缀,则使用该版本对应标签的代码模板。
-
-示例:`wails init -n "Your Project Name" -t https://github.com/misitebao/wails-template-vue`
-
-:::warning 注意
-
-
-**Wails 项目不维护也不对第 3 方模板负责**
-
-如果您不确定某个模板,请检查 `package.json` 和 `wails.json` 中安装的模块和运行的脚本。
-
-:::
-
-
-## Vue
-
-- [wails-template-vue](https://github.com/misitebao/wails-template-vue) - 基于 Vite、Vue 和 Vue-Router 的 Wails 模板(同时支持 JavaScript 和 TypeScript)
-- [wails-vite-vue-ts](https://github.com/codydbentley/wails-vite-vue-ts) - 使用 Vite 的 Vue 3 TypeScript(以及添加功能的说明)
-- [wails-vite-vue-the-works](https://github.com/codydbentley/wails-vite-vue-the-works) - 使用 Vite, Vuex, Vue Router, Sass, 和 ESLint + Prettier 的 Vue 3 TypeScript
-
-## Angular
-
-- [wails-angular-template](https://github.com/TAINCER/wails-angular-template) - 带有 TypeScript, Sass, 热重载, 代码拆分和 i18n 的 Angular
-
-## React
-
-- [wails-react-template](https://github.com/AlienRecall/wails-react-template) - 基于 reactjs 的模板
-- [wails-react-template](https://github.com/flin7/wails-react-template) - 基于 React 并支持实时开发模式的轻量级模板
-- [wails-vite-react-ts](https://github.com/lontten/wails-vite-react-ts) - 基于 Vite + React + TypeScript 的模板
-
-## Svelte
-
-- [wails-svelte-template](https://github.com/raitonoberu/wails-svelte-template) - 基于 Svelte 的模板
-- [wails-vite-svelte-template](https://github.com/BillBuilt/wails-vite-svelte-template) - 使用 Svelte 和 Vite 的模板
-- [wails-vite-svelte-tailwind-template](https://github.com/BillBuilt/wails-vite-svelte-tailwind-template) - 使用 Svelte 和 Vite 和 TailwindCSS v3 的模板
-- [wails-template-nextjs](https://github.com/LGiki/wails-template-nextjs) - 基于 Next.js + TypeScript 的模板
-
-## Elm
-
-- [wails-elm-template](https://github.com/benjamin-thomas/wails-elm-template) - 使用函数式编程和 **快速** 的热重载设置开发您的 GUI 应用程序 :tada: :rocket:
-
-## Pure JavaScript (Vanilla)
-
-- [wails-pure-js-template](https://github.com/KiddoV/wails-pure-js-template) - 一个只有基本 JavaScript、HTML 和 CSS 的模板
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/contributing/developing-new-features.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/contributing/developing-new-features.mdx
deleted file mode 100644
index 9fc9025bd..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/contributing/developing-new-features.mdx
+++ /dev/null
@@ -1,34 +0,0 @@
----
-sidebar_position: 20
----
-
-# 开发新功能
-
-We are always keen to add features to Wails and expand on what the project can do. The process for adding new features are as follows: The process for adding new features are as follows: We are always keen to add features to Wails and expand on what the project can do. The process for adding new features are as follows: The process for adding new features are as follows: The process for adding new features are as follows:
-
-- Pick an enhancement ticket with the "TODO" label. Pick an enhancement ticket with the "TODO" label. Pick an enhancement ticket with the "TODO" label. It's preferable to select one from the current [Backlog](https://github.com/orgs/wailsapp/projects/1/views/1) but the choice is yours.
-- Before developing, check that the ticket includes the following information:
-- The purpose of the enhancement
-- What is out of scope for the enhancement
-- What platforms the enhancement targets (most features should be cross-platform unless there's a very specific reason)
-- If the ticket does not include this information, feel free to request the information from the person who opened the ticket. Sometimes placeholder tickets are created and require more details Sometimes placeholder tickets are created and require more details Sometimes placeholder tickets are created and require more details
-- Comment on the ticket stating you wish to develop the feature
-- Clone the repository and create a branch with the format `feature/_`
-- New features often require documentation so please ensure you have also added or updated the documentation as part of the changes
-- Once the feature is ready for testing, create a draft PR. Once the feature is ready for testing, create a draft PR. Once the feature is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested. Once the feature is ready for testing, create a draft PR. Once the feature is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested. Once the feature is ready for testing, create a draft PR. Once the feature is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested.
-- Once all the testing is completed, please update the status of the PR from draft and leave a message.
-
-:::note
-There is nothing stopping you from opening a ticket and working on it yourself, but please be aware that all
-enhancement requests are reviewed for good fit. Not all ideas will be selected so it's best to have discussion
-on the ticket first.
-::: Not all ideas will be selected so it's best to have discussion
-on the ticket first.
-::: Not all ideas will be selected so it's best to have discussion
-on the ticket first.
-:::
-
-:::warning
-Any PRs opened without a corresponding ticket may be rejected.
-::: :::
-:::
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/contributing/documenting.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/contributing/documenting.mdx
deleted file mode 100644
index 84e472903..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/contributing/documenting.mdx
+++ /dev/null
@@ -1,34 +0,0 @@
----
-sidebar_position: 40
----
-
-# 文档
-
-This website is also the main documentation site for the project. Sometimes this gets out of date and needs some slight adjustments. Some of the documentation isn't written to the best standards either. Developing documentation is hard and so any contribution to this is greatly appreciated. Features without documentation are unfinished so to the project, it's _as important_ as the code.
-
-We generally do not create tickets for updating documentation so if there is text you think should be updated or rephrased then feel free to submit a PR for that. This site is in the main repository under the `website` directory. We use [Docusaurus](https://docusaurus.io/) to create the site so there is plenty of existing documentation and tutorials around to get started. This site is in the main repository under the `website` directory. We use [Docusaurus](https://docusaurus.io/) to create the site so there is plenty of existing documentation and tutorials around to get started. This site is in the main repository under the `website` directory. We use [Docusaurus](https://docusaurus.io/) to create the site so there is plenty of existing documentation and tutorials around to get started.
-
-To set up a local documentation development environment, do the following:
-
-- [Install npm](https://docs.npmjs.com/cli/v8/configuring-npm/install)
-- `cd website`
-- `npm install`
-- `npm run start`
-
-After it has all installed and is running, you should see the site at [`http://localhost:3000`](http://localhost:3000). Any changes made to the site text will be immediately reflected in the browser. Any changes made to the site text will be immediately reflected in the browser. Any changes made to the site text will be immediately reflected in the browser.
-
-## Versioning
-
-We employ a versioning system where we have the "latest" documentation AKA "Next Version" which has all the changes that have occurred since the last release. We also keep the last release documentation as well as the version before that. We also keep the last release documentation as well as the version before that. We also keep the last release documentation as well as the version before that.
-
-There isn't usually a reason to update released documentation so we don't generally update the documents in the `versioned_docs` or `versioned_sidebars` directories.
-
-The "next version" docs are mainly in `website/docs` with some "version independent" documents in `src/pages`. Any updates should be made in the `website/docs` directory. Any updates should be made in the `website/docs` directory. Any updates should be made in the `website/docs` directory.
-
-## Languages
-
-The default documents of the Wails project are English documents. We use the "crowdin" tool to translate documents in other languages and synchronize them to the website. You can [join our project](https://crowdin.com/project/wails) and submit your translations to make contributions.
-
-### Add new language
-
-If you want to add a new language to the documentation, please follow the prompts to [fill in and submit an Issue](https://github.com/wailsapp/wails/issues/new?assignees=&labels=documentation&template=documentation.yml). After being confirmed by the maintainer, we will add the language to the "crowdin" and you will then be able to submit your translation.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/contributing/fixing-bugs.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/contributing/fixing-bugs.mdx
deleted file mode 100644
index 01eceeccd..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/contributing/fixing-bugs.mdx
+++ /dev/null
@@ -1,29 +0,0 @@
----
-sidebar_position: 30
----
-
-# 修复漏洞
-
-The process for fixing bugs are as follows:
-
-- Check the current [Backlog](https://github.com/orgs/wailsapp/projects/1/views/1) and select a bug to fix
-- Before developing, check that the ticket includes the following information:
-- The scope of the issue including platforms affected
-- The steps to reproduce. The steps to reproduce. The steps to reproduce. Sometimes bugs are opened that are not Wails issues and the onus is on the reporter to prove that it is a Wails issue with a minimal reproducible example
-- The output of `wails doctor`
-- If the ticket does not include this information, feel free to request the information from the person who opened the ticket.
-- Comment on the ticket stating you wish to develop a fix
-- Clone the repository and create a branch with the format `bugfix/_`
-- Once the fix is ready for testing, create a draft PR. Once the fix is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested. Once the fix is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested.
-- Once all the testing is completed, please update the status of the PR from draft and leave a message.
-
-:::note
-There is nothing stopping you from opening a ticket and working on it yourself, but please be aware that all
-bugfixes should be discussed as the approach may have unintended side effects.
-::: :::
-:::
-
-:::warning
-Any PRs opened without a corresponding ticket may be rejected.
-::: :::
-:::
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/contributing/setting-up-a-dev-environment.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/contributing/setting-up-a-dev-environment.mdx
deleted file mode 100644
index 1133e275d..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/contributing/setting-up-a-dev-environment.mdx
+++ /dev/null
@@ -1,30 +0,0 @@
----
-sidebar_position: 10
----
-
-# 设置开发环境
-
-You can set up a development environment by doing the following:
-
-- Install the latest versions of Go and Git
-- `git clone https://github.com/wailsapp/wails`
-- `cd wails/v2/cmd/wails`
-- `go install`
-
-NOTE: The directory that you cloned the project into will now be called "clonedir".
-
-The Wails CLI will now be at the very latest version.
-
-To update projects to use the latest version, update the project's `go.mod` and ensure the following line is at the bottom of the file:
-
-`replace github.com/wailsapp/wails/v2 => `
-
-Example:
-
-On Windows: `replace github.com/wailsapp/wails/v2 => C:\Users\leaan\Documents\wails-v2-beta\wails\v2`
-
-On 'nix: `replace github.com/wailsapp/wails/v2 => /home/me/projects/wails/v2`
-
-To revert back to a stable version, run:
-
-`go install github.com/wailsapp/wails/v2/cmd/wails@latest`
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/contributing/ways-of-contributing.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/contributing/ways-of-contributing.mdx
deleted file mode 100644
index 3bbe9a889..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/contributing/ways-of-contributing.mdx
+++ /dev/null
@@ -1,18 +0,0 @@
----
-sidebar_position: 1
----
-
-# 贡献方式
-
-Wails is an open source, community driven project. We welcome anyone to join us in contributing to the project. This documentation is aimed at anyone wishing to get familiar with the project and the development processes. We welcome anyone to join us in contributing to the project. This documentation is aimed at anyone wishing to get familiar with the project and the development processes.
-
-There are many ways to contribute to the project:
-
-- Developing new features
-- Fixing bugs
-- Testing
-- Documenting features
-- Writing tutorials / guides
-- Helping others on the issues + discussions boards
-
-Guides for these have been created in their own sections. Guides for these have been created in their own sections. Guides for these have been created in their own sections. Before getting started, please introduce yourself in the [Contributing to Wails](https://github.com/wailsapp/wails/discussions/1520) discussion.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/gettingstarted/_category_.json b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/gettingstarted/_category_.json
deleted file mode 100644
index 597b920df..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/gettingstarted/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Getting Started",
- "position": 10
-}
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/gettingstarted/development.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/gettingstarted/development.mdx
deleted file mode 100644
index 1343a8a89..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/gettingstarted/development.mdx
+++ /dev/null
@@ -1,16 +0,0 @@
----
-sidebar_position: 5
----
-
-# 开发您的应用程序
-
-您可以通过从项目目录运行 `wails dev` 在开发模式下运行您的应用程序。 这将执行以下操作:
-
-- 构建您的应用程序并运行它
-- 将您的 Go 代码绑定到前端,以便可以从 Javascript 调用它
-- 使用 [Vite](https://vitejs.dev/) 的强大功能,将监视您的 Go 文件中的修改并在更改时重新构建/重新运行
-- 启动一个 [网络服务器](http://localhost:34115) 通过浏览器为您的应用程序提供服务。 这使您可以使用自己喜欢的浏览器扩展。你甚至可以从控制台调用你的 Go 代码。 您甚至可以从控制台调用 Go 代码。
-
-首先,在项目目录中运行 `wails dev`。 可以在 [此处](../reference/cli#开发) 找到有关这方面的更多信息。
-
-即将提供:教程
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/gettingstarted/firstproject.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/gettingstarted/firstproject.mdx
deleted file mode 100644
index e789438b0..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/gettingstarted/firstproject.mdx
+++ /dev/null
@@ -1,130 +0,0 @@
----
-sidebar_position: 2
----
-
-# 创建项目
-
-## 项目生成
-
-现在 CLI 已安装,您可以使用 `wails init` 命令生成一个新项目。
-
-选择您最喜欢的框架:
-
-```mdx-code-block
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-
-
-
- 使用 Javascript 生成一个 Svelte 项目:
-
-```
-
-### Linux
-
-这定义了 [Linux 特定的选项](#linux)。
-
-名称:Linux 类型:`*linux.Options`
-
-#### 图标
-
-设置代表窗口的图标。 当窗口最小化(也称为图标化)时使用此图标。
-
-名称:Icon 类型:`[]byte`
-
-一些窗口管理器或桌面环境也可能将其放置在窗口框架中,或在其他上下文中显示。 在其他情况下,根本不使用该图标,因此您的预计情况可能会有所不同。
-
-注意:Wayland 上的 Gnome 至少不显示此图标。 要在那里有一个应用程序图标,必须使用一个`.desktop`文件。 在 KDE 上它应该可以工作。
-
-图标应该以自然绘制的任何尺寸提供;也就是说,在传递图像之前不要缩放图像。 缩放将延迟到当所需的最终尺寸已知的最后一刻,以获得最佳质量。
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/reference/project-config.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/reference/project-config.mdx
deleted file mode 100644
index a21d26b5d..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/reference/project-config.mdx
+++ /dev/null
@@ -1,53 +0,0 @@
----
-sidebar_position: 5
----
-
-# 项目配置
-
-项目配置在项目目录中的 `wails.json` 文件中。 配置的结构是:
-
-```json
-{
- "name": "[The project name]",
- "assetdir": "[Relative path to the directory containing the compiled assets, this is normally inferred and could be left empty]",
- "reloaddirs": "[Additional directories to trigger reloads (comma separated), this is only used for some advanced asset configurations]",
- "frontend:install": "[The command to install node dependencies, run in the frontend directory - often `npm install`]",
- "frontend:build": "[The command to build the assets, run in the frontend directory - often `npm run build`]",
- "frontend:dev": "[This command has been replaced by frontend:dev:build. If frontend:dev:build is not specified will falls back to this command. \nIf this command is also not specified will falls back to frontend:build]",
- "frontend:dev:build": "[This command is the dev equivalent of frontend:build. If not specified falls back to frontend:dev]",
- "frontend:dev:install": "[This command is the dev equivalent of frontend:install. If not specified falls back to frontend:install]",
- "frontend:dev:watcher": "[This command is run in a separate process on `wails dev`. Useful for 3rd party watchers or starting 3d party dev servers]",
- "frontend:dev:serverUrl": "[URL to a 3rd party dev server to be used to serve assets, EG Vite. \nIf this is set to 'auto' then the devServerUrl will be inferred from the Vite output]",
- "wailsjsdir": "[Relative path to the directory that the auto-generated JS modules will be created]",
- "version": "[Project config version]",
- "outputfilename": "[The name of the binary]",
- "debounceMS": 100, // The default time the dev server waits to reload when it detects a change in assets
- "devServer": "[Address to bind the wails dev sever to. Default: localhost:34115]",
- "appargs": "[Arguments passed to the application in shell style when in dev mode]",
- "runNonNativeBuildHooks": false, // Defines if build hooks should be run though they are defined for an OS other than the host OS.
- "preBuildHooks": {
- "GOOS/GOARCH": "[The command that will be executed before a build of the specified GOOS/GOARCH: ${platform} is replaced with the "GOOS/GOARCH". The "GOOS/GOARCH" hook is executed before the "GOOS/*" and "*/*" hook.]",
- "GOOS/*": "[The command that will be executed before a build of the specified GOOS: ${platform} is replaced with the "GOOS/GOARCH". The "GOOS/*" hook is executed before the "*/*" hook.]",
- "*/*": "[The command that will be executed before every build: ${platform} is replaced with the "GOOS/GOARCH".]"
- },
- "postBuildHooks": {
- "GOOS/GOARCH": "[The command that will be executed after a build of the specified GOOS/GOARCH: ${platform} is replaced with the "GOOS/GOARCH" and ${bin} with the path to the compiled binary. The "GOOS/GOARCH" hook is executed before the "GOOS/*" and "*/*" hook.]",
- "GOOS/*": "[The command that will be executed after a build of the specified GOOS: ${platform} is replaced with the "GOOS/GOARCH" and ${bin} with the path to the compiled binary. The "GOOS/*" hook is executed before the "*/*" hook.]",
- "*/*": "[The command that will be executed after every build: ${platform} is replaced with the "GOOS/GOARCH" and ${bin} with the path to the compiled binary.]"
- },
- "info": { // Data used to populate manifests and version info.
- "companyName": "[The company name. Default: [The project name]]",
- "productName": "[The product name. Default: [The project name]]",
- "productVersion": "[The version of the product. Default: '1.0.0']",
- "copyright": "[The copyright of the product. Default: 'Copyright.........']",
- "comments": "[A short comment of the app. Default: 'Built using Wails (https://wails.app)']"
- },
- "nsisType": "['multiple': One installer per architecture. 'single': Single universal installer for all architectures being built. Default: 'multiple']",
- "obfuscated": "[Whether the app should be obfuscated. Default: false]",
- "garbleargs": "[The arguments to pass to the garble command when using the obfuscated flag]"
-}
-```
-
-该文件将在运行 `wails build` 或 `wails dev` 时,由 Wails CLI 读取。
-
-`wails build/dev` 命令中的 `assetdir`、`reloaddirs`、`wailsjsdir`、`debounceMS`、`devserver` 和 `frontenddevserverurl` 标志将覆盖项目配置并作为后续运行的默认值。
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/reference/runtime/_category_.json b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/reference/runtime/_category_.json
deleted file mode 100644
index ac6d55488..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/reference/runtime/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Runtime",
- "position": 1
-}
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/reference/runtime/dialog.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/reference/runtime/dialog.mdx
deleted file mode 100644
index e99d6d50d..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.0.0/reference/runtime/dialog.mdx
+++ /dev/null
@@ -1,292 +0,0 @@
----
-sidebar_position: 5
----
-
-# 对话框
-
-运行时的这一部分提供对原生对话框的调用,例如文件选择器和消息框。
-
-:::info Javascript
-
-
-JS 运行时当前不支持对话框。
-
-:::
-
-
-### 打开选择目录对话框
-
-打开一个对话框,提示用户选择目录。 可以使用 [ 打开选择文件对话框参数选项](#打开选择文件对话框参数选项) 进行自定义。
-
-Go: `OpenDirectoryDialog(ctx context.Context, dialogOptions OpenDialogOptions) (string, error)`
-
-返回值: 所选目录(如果用户取消则为空白)或错误
-
-### 打开选择文件对话框
-
-打开一个对话框,提示用户选择文件。 可以使用 [ 打开选择文件对话框参数选项](#打开选择文件对话框参数选项) 进行自定义。
-
-Go: `OpenFileDialog(ctx context.Context, dialogOptions OpenDialogOptions) (string, error)`
-
-返回值: 所选文件(如果用户取消则为空白)或错误
-
-### 打开选择多文件对话框
-
-打开一个对话框,提示用户选择多个文件。 可以使用 [ 打开选择文件对话框参数选项](#打开选择文件对话框参数选项) 进行自定义。
-
-Go: `OpenMultipleFilesDialog(ctx context.Context, dialogOptions OpenDialogOptions) ([]string, error)`
-
-返回值: 选定的文件(如果用户取消则为 nil)或错误
-
-### 保存文件对话框
-
-打开一个对话框,提示用户选择文件名以进行保存。 可以使用 [保存文件对话框参数选项](#保存文件对话框参数选项) 自定义。
-
-Go: `SaveFileDialog(ctx context.Context, dialogOptions SaveDialogOptions) (string, error)`
-
-返回值: 所选文件(如果用户取消则为空白)或错误
-
-### 消息对话框
-
-使用消息对话框显示消息。 可以使用 [消息对话框参数选项](#消息对话框参数选项) 进行自定义。
-
-Go: `MessageDialog(ctx context.Context, dialogOptions MessageDialogOptions) (string, error)`
-
-返回值: 所选按钮的文本或错误
-
-## 参数选项
-
-### 打开选择文件对话框参数选项
-
-```go
-type OpenDialogOptions struct {
- DefaultDirectory string
- DefaultFilename string
- Title string
- Filters []FileFilter
- ShowHiddenFiles bool
- CanCreateDirectories bool
- ResolvesAliases bool
- TreatPackagesAsDirectories bool
-}
-```
-
-| 字段 | 描述 | Win | Mac | Lin |
-| -------------------------- | ------------------- | --- | --- | --- |
-| DefaultDirectory | 对话框打开时显示的目录 | ✅ | ✅ | ✅ |
-| DefaultFilename | 默认文件名 | ✅ | ✅ | ✅ |
-| Title | 对话框的标题 | ✅ | ✅ | ✅ |
-| [Filters](#filefilter) | 文件过滤器列表 | ✅ | ✅ | ✅ |
-| ShowHiddenFiles | 显示系统隐藏的文件 | | ✅ | ✅ |
-| CanCreateDirectories | 允许用户创建目录 | | ✅ | |
-| ResolvesAliases | 如果为 true,则返回文件而不是别名 | | ✅ | |
-| TreatPackagesAsDirectories | 允许导航到包 | | ✅ | |
-
-### 保存文件对话框参数选项
-
-```go
-type SaveDialogOptions struct {
- DefaultDirectory string
- DefaultFilename string
- Title string
- Filters []FileFilter
- ShowHiddenFiles bool
- CanCreateDirectories bool
- TreatPackagesAsDirectories bool
-}
-```
-
-| 字段 | 描述 | Win | Mac | Lin |
-| -------------------------- | ----------- | --- | --- | --- |
-| DefaultDirectory | 对话框打开时显示的目录 | ✅ | ✅ | ✅ |
-| DefaultFilename | 默认文件名 | ✅ | ✅ | ✅ |
-| Title | 对话框的标题 | ✅ | ✅ | ✅ |
-| [Filters](#filefilter) | 文件过滤器列表 | ✅ | ✅ | ✅ |
-| ShowHiddenFiles | 显示系统隐藏的文件 | | ✅ | ✅ |
-| CanCreateDirectories | 允许用户创建目录 | | ✅ | |
-| TreatPackagesAsDirectories | 允许导航到包 | | ✅ | |
-
-### 消息对话框参数选项
-
-```go
-type MessageDialogOptions struct {
- Type DialogType
- Title string
- Message string
- Buttons []string
- DefaultButton string
- CancelButton string
-}
-```
-
-| 字段 | 描述 | Win | Mac | Lin |
-| ------------- | ------------------------------ | --- | --- | --- |
-| 类型 | 消息对话框的类型,例如问题、信息... | ✅ | ✅ | ✅ |
-| Title | 对话框的标题 | ✅ | ✅ | ✅ |
-| Message | 向用户显示的消息 | ✅ | ✅ | ✅ |
-| Buttons | 按钮标题列表 | | ✅ | |
-| DefaultButton | 带有此文本的按钮应被视为默认按钮。 绑定到 `return` | | ✅ | |
-| CancelButton | 带有此文本的按钮应被视为取消。 绑定到 `escape` | | ✅ | |
-
-#### Windows
-
-Windows 具有标准对话框类型,其中的按钮不可自定义。 返回的值将是以下之一:"Ok"、"Cancel"、"Abort"、"Retry"、"Ignore"、"Yes"、"No"、"Try Again"或"Continue"
-
-#### Linux
-
-Linux 有标准的对话框类型,其中的按钮是不可定制的。 返回的值将是以下之一:“Ok”、“Cancel”、“Yes”、“No”
-
-#### Mac
-
-Mac 上的消息对话框最多可以指定 4 个按钮。 如果没有 `DefaultButton` 或 `CancelButton` 给出,第一个按钮被认为是默认的并绑定到 `return` 键。
-
-对于以下代码:
-
-```go
-selection, err := runtime.MessageDialog(b.ctx, runtime.MessageDialogOptions{
- Title: "It's your turn!",
- Message: "Select a number",
- Buttons: []string{"one", "two", "three", "four"},
-})
-```
-
-第一个按钮显示为默认值:
-
-```mdx-code-block
-
-```
-
-[EmailIt](https://github.com/raguay/EmailIt/) is a Wails 2 program that is a markdown based email sender only with nine notepads, scripts to manipulate the text, and templates. It also has a builtin [Node-Red](https://nodered.org/) server, scripts terminal, and the [ScriptBar](https://github.com/raguay/ScriptBarApp) program for displaying results from Node-Red or a script on your system. Documentation is very scarce, but the programs works. It’s built using Wails2 and Svelte, and the download is a universal macOS application.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/encrypteasy.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/encrypteasy.mdx
deleted file mode 100644
index 7504950ea..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/encrypteasy.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
-# EncryptEasy
-
-```mdx-code-block
-
-
-
-
-```
-
-**[EncryptEasy](https://www.encrypteasy.app) is a simple and easy to use PGP encryption tool, managing all your and your contacts keys. Encryption should be simple. Developed with Wails.**
-
-Encrypting messages using PGP is the industry standard. Everyone has a private and a public key. Your private key, well, needs to be kept private so only you can read messages. Your public key is distributed to anyone who wants to send you secret, encrypted messages. Managing keys, encrypting messages and decrypting messages should be a smooth experience. EncryptEasy is all about making it easy.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/filehound.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/filehound.mdx
deleted file mode 100644
index 134365aaf..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/filehound.mdx
+++ /dev/null
@@ -1,16 +0,0 @@
-# FileHound Export Utility
-
-```mdx-code-block
-
-
-
-
-```
-
-[FileHound Export Utility](https://www.filehound.co.uk/) FileHound is a cloud document management platform made for secure file retention, business process automation and SmartCapture capabilities.
-
-The FileHound Export Utility allows FileHound Administrators the ability to run a secure document and data extraction tasks for alternative back-up and recovery purposes. This application will download all documents and/or meta data saved in FileHound based on the filters you choose. The metadata will be exported in both JSON and XML formats.
-
-Backend built with: Go 1.15 Wails 1.11.0 go-sqlite3 1.14.6 go-linq 3.2
-
-Frontend with: Vue 2.6.11 Vuex 3.4.0 Typescript Tailwind 1.9.6
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/minecraftupdater.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/minecraftupdater.mdx
deleted file mode 100644
index 2f6c7c72b..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/minecraftupdater.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
-# Minecraft Updater
-
-```mdx-code-block
-
-
-
-
-```
-
-[Minecraft Updater](https://github.com/Gurkengewuerz/MinecraftModUpdater) is a utility tool to update and synchronize Minecraft mods for your userbase. It’s built using Wails2 and React with [antd](https://ant.design/) as frontend framework.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/modalfilemanager.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/modalfilemanager.mdx
deleted file mode 100644
index f8e2bcd66..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/modalfilemanager.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
-# Modal File Manager
-
-```mdx-code-block
-
-
-
-
-```
-
-[Modal File Manager](https://github.com/raguay/ModalFileManager) is a dual pane file manager using web technologies. My original design was based on NW.js and can be found [here](https://github.com/raguay/ModalFileManager-NWjs). This version uses the same Svelte based frontend code (but it has be greatly modified since the departure from NW.js), but the backend is a [Wails 2](https://wails.io/) implementation. By using this implementation, I no longer use command line `rm`, `cp`, etc. commands. It is fully coded using Go and runs much faster than the previous versions.
-
-This file manager is designed around the same principle as Vim: a state controlled keyboard actions. The number of states isn't fixed, but very programmable. Therefore, an infinite number of keyboard configurations can be created and used. This is the main difference from other file managers.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/mollywallet.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/mollywallet.mdx
deleted file mode 100644
index 5d846d06d..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/mollywallet.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Molley Wallet
-
-```mdx-code-block
-
-
-
-
-```
-
-[Molly Wallet](https://github.com/grvlle/constellation_wallet/) the official $DAG wallet of the Constellation Network. It'll let users interact with the Hypergraph Network in various ways, not limited to producing $DAG transactions.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/october.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/october.mdx
deleted file mode 100644
index 66d634dc5..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/october.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
-# October
-
-```mdx-code-block
-
-
-
-
-```
-
-[October](https://october.utf9k.net) is a small Wails application that makes it really easy to extract highlights from [Kobo eReaders](https://en.wikipedia.org/wiki/Kobo_eReader) and then forward them to [Readwise](https://readwise.io).
-
-It has a relatively small scope with all platform versions weighing in under 10MB, and that's without enabling [UPX compression](https://upx.github.io/)!
-
-In contrast, the author's previous attempts with Electron quickly bloated to several hundred megabytes.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/optimus.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/optimus.mdx
deleted file mode 100644
index 4f87479d6..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/optimus.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Optimus
-
-```mdx-code-block
-
-
-
-
-```
-
-[Optimus](https://github.com/splode/optimus) is a desktop image optimization application. It supports conversion and compression between WebP, JPEG, and PNG image formats.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/portfall.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/portfall.mdx
deleted file mode 100644
index 03e740f4c..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/portfall.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Portfall
-
-```mdx-code-block
-
-
-
-
-```
-
-[Portfall](https://github.com/rekon-oss/portfall) - A desktop k8s port-forwarding portal for easy access to all your cluster UIs
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/restic-browser.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/restic-browser.mdx
deleted file mode 100644
index 3646384ec..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/restic-browser.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
-# Restic Browser
-
-```mdx-code-block
-
-
-
-
-```
-
-[Restic-Browser](https://github.com/emuell/restic-browser) - A simple, cross-platform [restic](https://github.com/restic/restic) backup GUI for browsing and restoring restic repositories.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/riftshare.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/riftshare.mdx
deleted file mode 100644
index 6224bbf89..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/riftshare.mdx
+++ /dev/null
@@ -1,21 +0,0 @@
-# RiftShare
-
-```mdx-code-block
-
-
-
-
-```
-
-Easy, Secure, and Free file sharing for everyone. Learn more at [Riftshare.app](https://riftshare.app)
-
-## 功能
-
-- Easy secure file sharing between computers both in the local network and through the internet
-- Supports sending files or directories securely through the [magic wormhole protocol](https://magic-wormhole.readthedocs.io/en/latest/)
-- Compatible with all other apps using magic wormhole (magic-wormhole or wormhole-william CLI, wormhole-gui, etc.)
-- Automatic zipping of multiple selected files to send at once
-- Full animations, progress bar, and cancellation support for sending and receiving
-- Native OS File Selection
-- Open files in one click once received
-- Auto Update - don't worry about having the latest release!
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/scriptbar.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/scriptbar.mdx
deleted file mode 100644
index 2ccb2acb4..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/scriptbar.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# ScriptBar
-
-```mdx-code-block
-
-
-
-
-```
-
-[ScriptBar](https://GitHub.com/raguay/ScriptBarApp) is a program to show the output of the embedded [Node-Red](https://nodered.org) server in the [EmailIt](https://GitHub.com/raguay/EmailIt) application. It also displays the output of scripts on your system. ScriptBar doesn't put them in the menubar, but has them all in a convient window for easy viewing. You can have multiple tabs to have many different things show. You can also keep the links to your most visited web sites.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/surge.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/surge.mdx
deleted file mode 100644
index c3b3fb4c0..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/surge.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Surge
-
-```mdx-code-block
-
-
-
-
-```
-
-[Surge](https://getsurge.io/) is a p2p filesharing app designed to utilize blockchain technologies to enable 100% anonymous file transfers. Surge is end-to-end encrypted, decentralized and open source.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/wally.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/wally.mdx
deleted file mode 100644
index 7408aa585..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/wally.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Wally
-
-```mdx-code-block
-
-
-
-
-```
-
-[Wally](https://ergodox-ez.com/pages/wally) is the official firmware flasher for [Ergodox](https://ergodox-ez.com/) keyboards. It looks great and is a fantastic example of what you can achieve with Wails: the ability to combine the power of Go and the rich graphical tools of the web development world.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/wombat.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/wombat.mdx
deleted file mode 100644
index f100c55e2..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/wombat.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Wombat
-
-```mdx-code-block
-
-```
-
-[Ytd](https://github.com/marcio199226/ytd/tree/v2-wails) is an app for downloading tracks from youtube, creating offline playlists and share them with your friends, your friends will be able to playback your playlists or download them for offline listening, has an built-in player.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/templates.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/templates.mdx
deleted file mode 100644
index 8e9f51284..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/community/templates.mdx
+++ /dev/null
@@ -1,56 +0,0 @@
----
-sidebar_position: 1
----
-
-# 模板
-
-此页面用作社区支持的模板列表。 请提交一个包含您的模板的 PR(点击页面底部的 `编辑此页`)。 要构建您自己的模板,请参考 [模板](../guides/templates) 指南。
-
-要使用这些模板,请运行 `wails init -n "您的项目名" -t [下面的链接[@版本]]`
-
-如果不带版本后缀,默认使用的是主分支代码模板。 如果带有版本后缀,则使用该版本对应标签的代码模板。
-
-示例:`wails init -n "Your Project Name" -t https://github.com/misitebao/wails-template-vue`
-
-:::warning 注意
-
-
-**Wails 项目不维护也不对第 3 方模板负责**
-
-如果您不确定某个模板,请检查 `package.json` 和 `wails.json` 中安装的模块和运行的脚本。
-
-:::
-
-
-## Vue
-
-- [wails-template-vue](https://github.com/misitebao/wails-template-vue) - 基于 Vue 生态的 Wails 模板(集成 TypeScript、黑暗主题、国际化、单页路由、TailwindCSS)
-- [wails-vite-vue-ts](https://github.com/codydbentley/wails-vite-vue-ts) - 使用 Vite 的 Vue 3 TypeScript(以及添加功能的说明)
-- [wails-vite-vue-the-works](https://github.com/codydbentley/wails-vite-vue-the-works) - 使用 Vite, Vuex, Vue Router, Sass, 和 ESLint + Prettier 的 Vue 3 TypeScript
-
-## Angular
-
-- [wails-angular-template](https://github.com/TAINCER/wails-angular-template) - 带有 TypeScript, Sass, 热重载, 代码拆分和 i18n 的 Angular
-
-## React
-
-- [wails-react-template](https://github.com/AlienRecall/wails-react-template) - 基于 reactjs 的模板
-- [wails-react-template](https://github.com/flin7/wails-react-template) - 基于 React 并支持实时开发模式的轻量级模板
-- [wails-vite-react-ts](https://github.com/lontten/wails-vite-react-ts) - 基于 Vite + React + TypeScript 的模板
-- [wails-vite-react-ts-tailwind-template](https://github.com/hotafrika/wails-vite-react-ts-tailwind-template) - 一个 React + TypeScript + Vite + TailwindCSS 模板
-
-## Svelte
-
-- [wails-svelte-template](https://github.com/raitonoberu/wails-svelte-template) - 基于 Svelte 的模板
-- [wails-vite-svelte-template](https://github.com/BillBuilt/wails-vite-svelte-template) - 使用 Svelte 和 Vite 的模板
-- [wails-vite-svelte-tailwind-template](https://github.com/BillBuilt/wails-vite-svelte-tailwind-template) - 使用 Svelte 和 Vite 和 TailwindCSS v3 的模板
-- [wails-template-nextjs](https://github.com/LGiki/wails-template-nextjs) - 基于 Next.js + TypeScript 的模板
-
-## Elm
-
-- [wails-elm-template](https://github.com/benjamin-thomas/wails-elm-template) - 使用函数式编程和 **快速** 的热重载设置开发您的 GUI 应用程序 :tada: :rocket:
-- [wails-template-elm-tailwind](https://github.com/rnice01/wails-template-elm-tailwind) - 结合 Elm + Tailwind CSS + Wails 的力量 :muscle: ! 支持热重载。
-
-## 纯 JavaScript (Vanilla)
-
-- [wails-pure-js-template](https://github.com/KiddoV/wails-pure-js-template) - 一个只有基本 JavaScript、HTML 和 CSS 的模板
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/contributing/developing-new-features.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/contributing/developing-new-features.mdx
deleted file mode 100644
index 9fc9025bd..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/contributing/developing-new-features.mdx
+++ /dev/null
@@ -1,34 +0,0 @@
----
-sidebar_position: 20
----
-
-# 开发新功能
-
-We are always keen to add features to Wails and expand on what the project can do. The process for adding new features are as follows: The process for adding new features are as follows: We are always keen to add features to Wails and expand on what the project can do. The process for adding new features are as follows: The process for adding new features are as follows: The process for adding new features are as follows:
-
-- Pick an enhancement ticket with the "TODO" label. Pick an enhancement ticket with the "TODO" label. Pick an enhancement ticket with the "TODO" label. It's preferable to select one from the current [Backlog](https://github.com/orgs/wailsapp/projects/1/views/1) but the choice is yours.
-- Before developing, check that the ticket includes the following information:
-- The purpose of the enhancement
-- What is out of scope for the enhancement
-- What platforms the enhancement targets (most features should be cross-platform unless there's a very specific reason)
-- If the ticket does not include this information, feel free to request the information from the person who opened the ticket. Sometimes placeholder tickets are created and require more details Sometimes placeholder tickets are created and require more details Sometimes placeholder tickets are created and require more details
-- Comment on the ticket stating you wish to develop the feature
-- Clone the repository and create a branch with the format `feature/_`
-- New features often require documentation so please ensure you have also added or updated the documentation as part of the changes
-- Once the feature is ready for testing, create a draft PR. Once the feature is ready for testing, create a draft PR. Once the feature is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested. Once the feature is ready for testing, create a draft PR. Once the feature is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested. Once the feature is ready for testing, create a draft PR. Once the feature is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested.
-- Once all the testing is completed, please update the status of the PR from draft and leave a message.
-
-:::note
-There is nothing stopping you from opening a ticket and working on it yourself, but please be aware that all
-enhancement requests are reviewed for good fit. Not all ideas will be selected so it's best to have discussion
-on the ticket first.
-::: Not all ideas will be selected so it's best to have discussion
-on the ticket first.
-::: Not all ideas will be selected so it's best to have discussion
-on the ticket first.
-:::
-
-:::warning
-Any PRs opened without a corresponding ticket may be rejected.
-::: :::
-:::
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/contributing/documenting.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/contributing/documenting.mdx
deleted file mode 100644
index 84e472903..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/contributing/documenting.mdx
+++ /dev/null
@@ -1,34 +0,0 @@
----
-sidebar_position: 40
----
-
-# 文档
-
-This website is also the main documentation site for the project. Sometimes this gets out of date and needs some slight adjustments. Some of the documentation isn't written to the best standards either. Developing documentation is hard and so any contribution to this is greatly appreciated. Features without documentation are unfinished so to the project, it's _as important_ as the code.
-
-We generally do not create tickets for updating documentation so if there is text you think should be updated or rephrased then feel free to submit a PR for that. This site is in the main repository under the `website` directory. We use [Docusaurus](https://docusaurus.io/) to create the site so there is plenty of existing documentation and tutorials around to get started. This site is in the main repository under the `website` directory. We use [Docusaurus](https://docusaurus.io/) to create the site so there is plenty of existing documentation and tutorials around to get started. This site is in the main repository under the `website` directory. We use [Docusaurus](https://docusaurus.io/) to create the site so there is plenty of existing documentation and tutorials around to get started.
-
-To set up a local documentation development environment, do the following:
-
-- [Install npm](https://docs.npmjs.com/cli/v8/configuring-npm/install)
-- `cd website`
-- `npm install`
-- `npm run start`
-
-After it has all installed and is running, you should see the site at [`http://localhost:3000`](http://localhost:3000). Any changes made to the site text will be immediately reflected in the browser. Any changes made to the site text will be immediately reflected in the browser. Any changes made to the site text will be immediately reflected in the browser.
-
-## Versioning
-
-We employ a versioning system where we have the "latest" documentation AKA "Next Version" which has all the changes that have occurred since the last release. We also keep the last release documentation as well as the version before that. We also keep the last release documentation as well as the version before that. We also keep the last release documentation as well as the version before that.
-
-There isn't usually a reason to update released documentation so we don't generally update the documents in the `versioned_docs` or `versioned_sidebars` directories.
-
-The "next version" docs are mainly in `website/docs` with some "version independent" documents in `src/pages`. Any updates should be made in the `website/docs` directory. Any updates should be made in the `website/docs` directory. Any updates should be made in the `website/docs` directory.
-
-## Languages
-
-The default documents of the Wails project are English documents. We use the "crowdin" tool to translate documents in other languages and synchronize them to the website. You can [join our project](https://crowdin.com/project/wails) and submit your translations to make contributions.
-
-### Add new language
-
-If you want to add a new language to the documentation, please follow the prompts to [fill in and submit an Issue](https://github.com/wailsapp/wails/issues/new?assignees=&labels=documentation&template=documentation.yml). After being confirmed by the maintainer, we will add the language to the "crowdin" and you will then be able to submit your translation.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/contributing/fixing-bugs.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/contributing/fixing-bugs.mdx
deleted file mode 100644
index 01eceeccd..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/contributing/fixing-bugs.mdx
+++ /dev/null
@@ -1,29 +0,0 @@
----
-sidebar_position: 30
----
-
-# 修复漏洞
-
-The process for fixing bugs are as follows:
-
-- Check the current [Backlog](https://github.com/orgs/wailsapp/projects/1/views/1) and select a bug to fix
-- Before developing, check that the ticket includes the following information:
-- The scope of the issue including platforms affected
-- The steps to reproduce. The steps to reproduce. The steps to reproduce. Sometimes bugs are opened that are not Wails issues and the onus is on the reporter to prove that it is a Wails issue with a minimal reproducible example
-- The output of `wails doctor`
-- If the ticket does not include this information, feel free to request the information from the person who opened the ticket.
-- Comment on the ticket stating you wish to develop a fix
-- Clone the repository and create a branch with the format `bugfix/_`
-- Once the fix is ready for testing, create a draft PR. Once the fix is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested. Once the fix is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested.
-- Once all the testing is completed, please update the status of the PR from draft and leave a message.
-
-:::note
-There is nothing stopping you from opening a ticket and working on it yourself, but please be aware that all
-bugfixes should be discussed as the approach may have unintended side effects.
-::: :::
-:::
-
-:::warning
-Any PRs opened without a corresponding ticket may be rejected.
-::: :::
-:::
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/contributing/setting-up-a-dev-environment.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/contributing/setting-up-a-dev-environment.mdx
deleted file mode 100644
index 1133e275d..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/contributing/setting-up-a-dev-environment.mdx
+++ /dev/null
@@ -1,30 +0,0 @@
----
-sidebar_position: 10
----
-
-# 设置开发环境
-
-You can set up a development environment by doing the following:
-
-- Install the latest versions of Go and Git
-- `git clone https://github.com/wailsapp/wails`
-- `cd wails/v2/cmd/wails`
-- `go install`
-
-NOTE: The directory that you cloned the project into will now be called "clonedir".
-
-The Wails CLI will now be at the very latest version.
-
-To update projects to use the latest version, update the project's `go.mod` and ensure the following line is at the bottom of the file:
-
-`replace github.com/wailsapp/wails/v2 => `
-
-Example:
-
-On Windows: `replace github.com/wailsapp/wails/v2 => C:\Users\leaan\Documents\wails-v2-beta\wails\v2`
-
-On 'nix: `replace github.com/wailsapp/wails/v2 => /home/me/projects/wails/v2`
-
-To revert back to a stable version, run:
-
-`go install github.com/wailsapp/wails/v2/cmd/wails@latest`
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/contributing/ways-of-contributing.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/contributing/ways-of-contributing.mdx
deleted file mode 100644
index 3bbe9a889..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/contributing/ways-of-contributing.mdx
+++ /dev/null
@@ -1,18 +0,0 @@
----
-sidebar_position: 1
----
-
-# 贡献方式
-
-Wails is an open source, community driven project. We welcome anyone to join us in contributing to the project. This documentation is aimed at anyone wishing to get familiar with the project and the development processes. We welcome anyone to join us in contributing to the project. This documentation is aimed at anyone wishing to get familiar with the project and the development processes.
-
-There are many ways to contribute to the project:
-
-- Developing new features
-- Fixing bugs
-- Testing
-- Documenting features
-- Writing tutorials / guides
-- Helping others on the issues + discussions boards
-
-Guides for these have been created in their own sections. Guides for these have been created in their own sections. Guides for these have been created in their own sections. Before getting started, please introduce yourself in the [Contributing to Wails](https://github.com/wailsapp/wails/discussions/1520) discussion.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/gettingstarted/_category_.json b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/gettingstarted/_category_.json
deleted file mode 100644
index 597b920df..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/gettingstarted/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Getting Started",
- "position": 10
-}
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/gettingstarted/building.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/gettingstarted/building.mdx
deleted file mode 100644
index c4fe879bc..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/gettingstarted/building.mdx
+++ /dev/null
@@ -1,22 +0,0 @@
----
-sidebar_position: 6
----
-
-# 编译您的项目
-
-从项目目录,运行 `wails build`。 这将编译您的项目并将构建的可用于生产的二进制文件保存在 `build/bin` 目录中。
-
-如果您运行二进制文件,您应该会看到默认应用程序:
-
-```mdx-code-block
-
-
-```
-
-### Linux
-
-这定义了 [Linux 特定的选项](#linux)。
-
-名称:Linux 类型:`*linux.Options`
-
-#### 图标
-
-设置代表窗口的图标。 当窗口最小化(也称为图标化)时使用此图标。
-
-名称:Icon 类型:`[]byte`
-
-一些窗口管理器或桌面环境也可能将其放置在窗口框架中,或在其他上下文中显示。 在其他情况下,根本不使用该图标,因此您的预计情况可能会有所不同。
-
-注意:Wayland 上的 Gnome 至少不显示此图标。 要在那里有一个应用程序图标,必须使用一个`.desktop`文件。 在 KDE 上它应该可以工作。
-
-图标应该以自然绘制的任何尺寸提供;也就是说,在传递图像之前不要缩放图像。 缩放将延迟到当所需的最终尺寸已知的最后一刻,以获得最佳质量。
-
-#### 窗口半透明
-
-将此设置为 `true` 将使窗口半透明。 某些窗口管理员可能忽略它,或导致黑窗口。
-
-名称:WindowIsTranslucent 类型:`bool`
\ No newline at end of file
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/reference/project-config.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/reference/project-config.mdx
deleted file mode 100644
index a21d26b5d..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/reference/project-config.mdx
+++ /dev/null
@@ -1,53 +0,0 @@
----
-sidebar_position: 5
----
-
-# 项目配置
-
-项目配置在项目目录中的 `wails.json` 文件中。 配置的结构是:
-
-```json
-{
- "name": "[The project name]",
- "assetdir": "[Relative path to the directory containing the compiled assets, this is normally inferred and could be left empty]",
- "reloaddirs": "[Additional directories to trigger reloads (comma separated), this is only used for some advanced asset configurations]",
- "frontend:install": "[The command to install node dependencies, run in the frontend directory - often `npm install`]",
- "frontend:build": "[The command to build the assets, run in the frontend directory - often `npm run build`]",
- "frontend:dev": "[This command has been replaced by frontend:dev:build. If frontend:dev:build is not specified will falls back to this command. \nIf this command is also not specified will falls back to frontend:build]",
- "frontend:dev:build": "[This command is the dev equivalent of frontend:build. If not specified falls back to frontend:dev]",
- "frontend:dev:install": "[This command is the dev equivalent of frontend:install. If not specified falls back to frontend:install]",
- "frontend:dev:watcher": "[This command is run in a separate process on `wails dev`. Useful for 3rd party watchers or starting 3d party dev servers]",
- "frontend:dev:serverUrl": "[URL to a 3rd party dev server to be used to serve assets, EG Vite. \nIf this is set to 'auto' then the devServerUrl will be inferred from the Vite output]",
- "wailsjsdir": "[Relative path to the directory that the auto-generated JS modules will be created]",
- "version": "[Project config version]",
- "outputfilename": "[The name of the binary]",
- "debounceMS": 100, // The default time the dev server waits to reload when it detects a change in assets
- "devServer": "[Address to bind the wails dev sever to. Default: localhost:34115]",
- "appargs": "[Arguments passed to the application in shell style when in dev mode]",
- "runNonNativeBuildHooks": false, // Defines if build hooks should be run though they are defined for an OS other than the host OS.
- "preBuildHooks": {
- "GOOS/GOARCH": "[The command that will be executed before a build of the specified GOOS/GOARCH: ${platform} is replaced with the "GOOS/GOARCH". The "GOOS/GOARCH" hook is executed before the "GOOS/*" and "*/*" hook.]",
- "GOOS/*": "[The command that will be executed before a build of the specified GOOS: ${platform} is replaced with the "GOOS/GOARCH". The "GOOS/*" hook is executed before the "*/*" hook.]",
- "*/*": "[The command that will be executed before every build: ${platform} is replaced with the "GOOS/GOARCH".]"
- },
- "postBuildHooks": {
- "GOOS/GOARCH": "[The command that will be executed after a build of the specified GOOS/GOARCH: ${platform} is replaced with the "GOOS/GOARCH" and ${bin} with the path to the compiled binary. The "GOOS/GOARCH" hook is executed before the "GOOS/*" and "*/*" hook.]",
- "GOOS/*": "[The command that will be executed after a build of the specified GOOS: ${platform} is replaced with the "GOOS/GOARCH" and ${bin} with the path to the compiled binary. The "GOOS/*" hook is executed before the "*/*" hook.]",
- "*/*": "[The command that will be executed after every build: ${platform} is replaced with the "GOOS/GOARCH" and ${bin} with the path to the compiled binary.]"
- },
- "info": { // Data used to populate manifests and version info.
- "companyName": "[The company name. Default: [The project name]]",
- "productName": "[The product name. Default: [The project name]]",
- "productVersion": "[The version of the product. Default: '1.0.0']",
- "copyright": "[The copyright of the product. Default: 'Copyright.........']",
- "comments": "[A short comment of the app. Default: 'Built using Wails (https://wails.app)']"
- },
- "nsisType": "['multiple': One installer per architecture. 'single': Single universal installer for all architectures being built. Default: 'multiple']",
- "obfuscated": "[Whether the app should be obfuscated. Default: false]",
- "garbleargs": "[The arguments to pass to the garble command when using the obfuscated flag]"
-}
-```
-
-该文件将在运行 `wails build` 或 `wails dev` 时,由 Wails CLI 读取。
-
-`wails build/dev` 命令中的 `assetdir`、`reloaddirs`、`wailsjsdir`、`debounceMS`、`devserver` 和 `frontenddevserverurl` 标志将覆盖项目配置并作为后续运行的默认值。
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/reference/runtime/_category_.json b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/reference/runtime/_category_.json
deleted file mode 100644
index ac6d55488..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/reference/runtime/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Runtime",
- "position": 1
-}
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/reference/runtime/browser.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/reference/runtime/browser.mdx
deleted file mode 100644
index 26b81b958..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/reference/runtime/browser.mdx
+++ /dev/null
@@ -1,13 +0,0 @@
----
-sidebar_position: 7
----
-
-# 浏览器
-
-这些方法与系统浏览器相关。
-
-### 浏览器打开 URL
-
-使用系统默认浏览器打开给定的 URL。
-
-Go: `BrowserOpenURL(ctx context.Context, url string)` JS: `BrowserOpenURL(url string)`
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/reference/runtime/dialog.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/reference/runtime/dialog.mdx
deleted file mode 100644
index 169a288f2..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.1.0/reference/runtime/dialog.mdx
+++ /dev/null
@@ -1,304 +0,0 @@
----
-sidebar_position: 5
----
-
-# 对话框
-
-运行时的这一部分提供对原生对话框的调用,例如文件选择器和消息框。
-
-:::info Javascript
-
-
-JS 运行时当前不支持对话框。
-
-:::
-
-
-### 打开选择目录对话框
-
-打开一个对话框,提示用户选择目录。 可以使用 [ 打开选择文件对话框参数选项](#打开选择文件对话框参数选项) 进行自定义。
-
-Go: `OpenDirectoryDialog(ctx context.Context, dialogOptions OpenDialogOptions) (string, error)`
-
-返回值: 所选目录(如果用户取消则为空白)或错误
-
-### 打开选择文件对话框
-
-打开一个对话框,提示用户选择文件。 可以使用 [ 打开选择文件对话框参数选项](#打开选择文件对话框参数选项) 进行自定义。
-
-Go: `OpenFileDialog(ctx context.Context, dialogOptions OpenDialogOptions) (string, error)`
-
-返回值: 所选文件(如果用户取消则为空白)或错误
-
-### 打开选择多文件对话框
-
-打开一个对话框,提示用户选择多个文件。 可以使用 [ 打开选择文件对话框参数选项](#打开选择文件对话框参数选项) 进行自定义。
-
-Go: `OpenMultipleFilesDialog(ctx context.Context, dialogOptions OpenDialogOptions) ([]string, error)`
-
-返回值: 选定的文件(如果用户取消则为 nil)或错误
-
-### 保存文件对话框
-
-打开一个对话框,提示用户选择文件名以进行保存。 可以使用 [保存文件对话框参数选项](#保存文件对话框参数选项) 自定义。
-
-Go: `SaveFileDialog(ctx context.Context, dialogOptions SaveDialogOptions) (string, error)`
-
-返回值: 所选文件(如果用户取消则为空白)或错误
-
-### 消息对话框
-
-使用消息对话框显示消息。 可以使用 [消息对话框参数选项](#消息对话框参数选项) 进行自定义。
-
-Go: `MessageDialog(ctx context.Context, dialogOptions MessageDialogOptions) (string, error)`
-
-返回值: 所选按钮的文本或错误
-
-## 参数选项
-
-### 打开选择文件对话框参数选项
-
-```go
-type OpenDialogOptions struct {
- DefaultDirectory string
- DefaultFilename string
- Title string
- Filters []FileFilter
- ShowHiddenFiles bool
- CanCreateDirectories bool
- ResolvesAliases bool
- TreatPackagesAsDirectories bool
-}
-```
-
-| 字段 | 描述 | Win | Mac | Lin |
-| -------------------------- | ------------------- | --- | --- | --- |
-| DefaultDirectory | 对话框打开时显示的目录 | ✅ | ✅ | ✅ |
-| DefaultFilename | 默认文件名 | ✅ | ✅ | ✅ |
-| Title | 对话框的标题 | ✅ | ✅ | ✅ |
-| [Filters](#filefilter) | 文件过滤器列表 | ✅ | ✅ | ✅ |
-| ShowHiddenFiles | 显示系统隐藏的文件 | | ✅ | ✅ |
-| CanCreateDirectories | 允许用户创建目录 | | ✅ | |
-| ResolvesAliases | 如果为 true,则返回文件而不是别名 | | ✅ | |
-| TreatPackagesAsDirectories | 允许导航到包 | | ✅ | |
-
-### 保存文件对话框参数选项
-
-```go
-type SaveDialogOptions struct {
- DefaultDirectory string
- DefaultFilename string
- Title string
- Filters []FileFilter
- ShowHiddenFiles bool
- CanCreateDirectories bool
- TreatPackagesAsDirectories bool
-}
-```
-
-| 字段 | 描述 | Win | Mac | Lin |
-| -------------------------- | ----------- | --- | --- | --- |
-| DefaultDirectory | 对话框打开时显示的目录 | ✅ | ✅ | ✅ |
-| DefaultFilename | 默认文件名 | ✅ | ✅ | ✅ |
-| Title | 对话框的标题 | ✅ | ✅ | ✅ |
-| [Filters](#filefilter) | 文件过滤器列表 | ✅ | ✅ | ✅ |
-| ShowHiddenFiles | 显示系统隐藏的文件 | | ✅ | ✅ |
-| CanCreateDirectories | 允许用户创建目录 | | ✅ | |
-| TreatPackagesAsDirectories | 允许导航到包 | | ✅ | |
-
-### 消息对话框参数选项
-
-```go
-type MessageDialogOptions struct {
- Type DialogType
- Title string
- Message string
- Buttons []string
- DefaultButton string
- CancelButton string
-}
-```
-
-| 字段 | 描述 | Win | Mac | Lin |
-| ------------- | ------------------------------ | -------------- | --- | --- |
-| 类型 | 消息对话框的类型,例如问题、信息... | ✅ | ✅ | ✅ |
-| Title | 对话框的标题 | ✅ | ✅ | ✅ |
-| Message | 向用户显示的消息 | ✅ | ✅ | ✅ |
-| Buttons | 按钮标题列表 | | ✅ | |
-| DefaultButton | 带有此文本的按钮应被视为默认按钮。 必定 `return`。 | ✅[*](#windows) | ✅ | |
-| CancelButton | 带有此文本的按钮应被视为取消。 必定 `escape` | | ✅ | |
-
-#### Windows
-
-Windows 具有标准对话框类型,其中的按钮不可自定义。 返回的值将是以下之一:"Ok"、"Cancel"、"Abort"、"Retry"、"Ignore"、"Yes"、"No"、"Try Again"或"Continue"。
-
-对于问题对话框,默认按钮是 “是”,取消按钮是 “否”。 可以通过将 `默认按钮` 值设置为 `"否"` 来改变这一点。
-
-示例:
-```go
- result, err := runtime.MessageDialog(a.ctx, runtime.MessageDialogOptions{
- Type: runtime.QuestionDialog,
- Title: "Question",
- Message: "Do you want to continue?",
- DefaultButton: "No",
- })
-```
-
-#### Linux
-
-Linux 有标准的对话框类型,其中的按钮是不可定制的。 返回的值将是以下之一:“Ok”、“Cancel”、“Yes”、“No”
-
-#### Mac
-
-Mac 上的消息对话框最多可以指定 4 个按钮。 如果没有 `DefaultButton` 或 `CancelButton` 给出,第一个按钮被认为是默认的并绑定到 `return` 键。
-
-对于以下代码:
-
-```go
-selection, err := runtime.MessageDialog(b.ctx, runtime.MessageDialogOptions{
- Title: "It's your turn!",
- Message: "Select a number",
- Buttons: []string{"one", "two", "three", "four"},
-})
-```
-
-第一个按钮显示为默认值:
-
-```mdx-code-block
-
-```
-
-[EmailIt](https://github.com/raguay/EmailIt/) is a Wails 2 program that is a markdown based email sender only with nine notepads, scripts to manipulate the text, and templates. It also has a builtin [Node-Red](https://nodered.org/) server, scripts terminal, and the [ScriptBar](https://github.com/raguay/ScriptBarApp) program for displaying results from Node-Red or a script on your system. Documentation is very scarce, but the programs works. It’s built using Wails2 and Svelte, and the download is a universal macOS application.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/encrypteasy.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/encrypteasy.mdx
deleted file mode 100644
index 7504950ea..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/encrypteasy.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
-# EncryptEasy
-
-```mdx-code-block
-
-
-
-
-```
-
-**[EncryptEasy](https://www.encrypteasy.app) is a simple and easy to use PGP encryption tool, managing all your and your contacts keys. Encryption should be simple. Developed with Wails.**
-
-Encrypting messages using PGP is the industry standard. Everyone has a private and a public key. Your private key, well, needs to be kept private so only you can read messages. Your public key is distributed to anyone who wants to send you secret, encrypted messages. Managing keys, encrypting messages and decrypting messages should be a smooth experience. EncryptEasy is all about making it easy.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/filehound.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/filehound.mdx
deleted file mode 100644
index 134365aaf..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/filehound.mdx
+++ /dev/null
@@ -1,16 +0,0 @@
-# FileHound Export Utility
-
-```mdx-code-block
-
-
-
-
-```
-
-[FileHound Export Utility](https://www.filehound.co.uk/) FileHound is a cloud document management platform made for secure file retention, business process automation and SmartCapture capabilities.
-
-The FileHound Export Utility allows FileHound Administrators the ability to run a secure document and data extraction tasks for alternative back-up and recovery purposes. This application will download all documents and/or meta data saved in FileHound based on the filters you choose. The metadata will be exported in both JSON and XML formats.
-
-Backend built with: Go 1.15 Wails 1.11.0 go-sqlite3 1.14.6 go-linq 3.2
-
-Frontend with: Vue 2.6.11 Vuex 3.4.0 Typescript Tailwind 1.9.6
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/minecraftupdater.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/minecraftupdater.mdx
deleted file mode 100644
index 2f6c7c72b..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/minecraftupdater.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
-# Minecraft Updater
-
-```mdx-code-block
-
-
-
-
-```
-
-[Minecraft Updater](https://github.com/Gurkengewuerz/MinecraftModUpdater) is a utility tool to update and synchronize Minecraft mods for your userbase. It’s built using Wails2 and React with [antd](https://ant.design/) as frontend framework.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/modalfilemanager.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/modalfilemanager.mdx
deleted file mode 100644
index f8e2bcd66..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/modalfilemanager.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
-# Modal File Manager
-
-```mdx-code-block
-
-
-
-
-```
-
-[Modal File Manager](https://github.com/raguay/ModalFileManager) is a dual pane file manager using web technologies. My original design was based on NW.js and can be found [here](https://github.com/raguay/ModalFileManager-NWjs). This version uses the same Svelte based frontend code (but it has be greatly modified since the departure from NW.js), but the backend is a [Wails 2](https://wails.io/) implementation. By using this implementation, I no longer use command line `rm`, `cp`, etc. commands. It is fully coded using Go and runs much faster than the previous versions.
-
-This file manager is designed around the same principle as Vim: a state controlled keyboard actions. The number of states isn't fixed, but very programmable. Therefore, an infinite number of keyboard configurations can be created and used. This is the main difference from other file managers.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/mollywallet.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/mollywallet.mdx
deleted file mode 100644
index 5d846d06d..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/mollywallet.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Molley Wallet
-
-```mdx-code-block
-
-
-
-
-```
-
-[Molly Wallet](https://github.com/grvlle/constellation_wallet/) the official $DAG wallet of the Constellation Network. It'll let users interact with the Hypergraph Network in various ways, not limited to producing $DAG transactions.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/october.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/october.mdx
deleted file mode 100644
index 66d634dc5..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/october.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
-# October
-
-```mdx-code-block
-
-
-
-
-```
-
-[October](https://october.utf9k.net) is a small Wails application that makes it really easy to extract highlights from [Kobo eReaders](https://en.wikipedia.org/wiki/Kobo_eReader) and then forward them to [Readwise](https://readwise.io).
-
-It has a relatively small scope with all platform versions weighing in under 10MB, and that's without enabling [UPX compression](https://upx.github.io/)!
-
-In contrast, the author's previous attempts with Electron quickly bloated to several hundred megabytes.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/optimus.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/optimus.mdx
deleted file mode 100644
index 4f87479d6..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/optimus.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Optimus
-
-```mdx-code-block
-
-
-
-
-```
-
-[Optimus](https://github.com/splode/optimus) is a desktop image optimization application. It supports conversion and compression between WebP, JPEG, and PNG image formats.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/portfall.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/portfall.mdx
deleted file mode 100644
index 03e740f4c..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/portfall.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Portfall
-
-```mdx-code-block
-
-
-
-
-```
-
-[Portfall](https://github.com/rekon-oss/portfall) - A desktop k8s port-forwarding portal for easy access to all your cluster UIs
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/restic-browser.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/restic-browser.mdx
deleted file mode 100644
index 3646384ec..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/restic-browser.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
-# Restic Browser
-
-```mdx-code-block
-
-
-
-
-```
-
-[Restic-Browser](https://github.com/emuell/restic-browser) - A simple, cross-platform [restic](https://github.com/restic/restic) backup GUI for browsing and restoring restic repositories.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/riftshare.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/riftshare.mdx
deleted file mode 100644
index 6224bbf89..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/riftshare.mdx
+++ /dev/null
@@ -1,21 +0,0 @@
-# RiftShare
-
-```mdx-code-block
-
-
-
-
-```
-
-Easy, Secure, and Free file sharing for everyone. Learn more at [Riftshare.app](https://riftshare.app)
-
-## 功能
-
-- Easy secure file sharing between computers both in the local network and through the internet
-- Supports sending files or directories securely through the [magic wormhole protocol](https://magic-wormhole.readthedocs.io/en/latest/)
-- Compatible with all other apps using magic wormhole (magic-wormhole or wormhole-william CLI, wormhole-gui, etc.)
-- Automatic zipping of multiple selected files to send at once
-- Full animations, progress bar, and cancellation support for sending and receiving
-- Native OS File Selection
-- Open files in one click once received
-- Auto Update - don't worry about having the latest release!
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/scriptbar.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/scriptbar.mdx
deleted file mode 100644
index 2ccb2acb4..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/scriptbar.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# ScriptBar
-
-```mdx-code-block
-
-
-
-
-```
-
-[ScriptBar](https://GitHub.com/raguay/ScriptBarApp) is a program to show the output of the embedded [Node-Red](https://nodered.org) server in the [EmailIt](https://GitHub.com/raguay/EmailIt) application. It also displays the output of scripts on your system. ScriptBar doesn't put them in the menubar, but has them all in a convient window for easy viewing. You can have multiple tabs to have many different things show. You can also keep the links to your most visited web sites.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/surge.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/surge.mdx
deleted file mode 100644
index c3b3fb4c0..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/surge.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Surge
-
-```mdx-code-block
-
-
-
-
-```
-
-[Surge](https://getsurge.io/) is a p2p filesharing app designed to utilize blockchain technologies to enable 100% anonymous file transfers. Surge is end-to-end encrypted, decentralized and open source.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/wally.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/wally.mdx
deleted file mode 100644
index 7408aa585..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/wally.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Wally
-
-```mdx-code-block
-
-
-
-
-```
-
-[Wally](https://ergodox-ez.com/pages/wally) is the official firmware flasher for [Ergodox](https://ergodox-ez.com/) keyboards. It looks great and is a fantastic example of what you can achieve with Wails: the ability to combine the power of Go and the rich graphical tools of the web development world.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/wombat.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/wombat.mdx
deleted file mode 100644
index f100c55e2..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/wombat.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Wombat
-
-```mdx-code-block
-
-```
-
-[Ytd](https://github.com/marcio199226/ytd/tree/v2-wails) is an app for downloading tracks from youtube, creating offline playlists and share them with your friends, your friends will be able to playback your playlists or download them for offline listening, has an built-in player.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/templates.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/templates.mdx
deleted file mode 100644
index c3d10598e..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/community/templates.mdx
+++ /dev/null
@@ -1,61 +0,0 @@
----
-sidebar_position: 1
----
-
-# 模板
-
-此页面用作社区支持的模板列表。 请提交一个包含您的模板的 PR(点击页面底部的 `编辑此页`)。 要构建您自己的模板,请参考 [模板](../guides/templates) 指南。
-
-要使用这些模板,请运行 `wails init -n "您的项目名" -t [下面的链接[@版本]]`
-
-如果不带版本后缀,默认使用的是主分支代码模板。 如果带有版本后缀,则使用该版本对应标签的代码模板。
-
-示例:`wails init -n "Your Project Name" -t https://github.com/misitebao/wails-template-vue`
-
-:::warning 注意
-
-**Wails 项目不维护也不对第 3 方模板负责**
-
-如果您不确定某个模板,请检查 `package.json` 和 `wails.json` 中安装的模块和运行的脚本。
-
-:::
-
-## Vue
-
-- [wails-template-vue](https://github.com/misitebao/wails-template-vue) - 基于 Vue 生态的 Wails 模板(集成 TypeScript、黑暗主题、国际化、单页路由、TailwindCSS)
-- [wails-vite-vue-ts](https://github.com/codydbentley/wails-vite-vue-ts) - 使用 Vite 的 Vue 3 TypeScript(以及添加功能的说明)
-- [wails-vite-vue-the-works](https://github.com/codydbentley/wails-vite-vue-the-works) - 使用 Vite, Vuex, Vue Router, Sass, 和 ESLint + Prettier 的 Vue 3 TypeScript
-- [wails-template-quasar-js](https://github.com/sgosiaco/wails-template-quasar-js) - 使用 JavaScript + Quasar V2(Vue 3, Vite, Sass, Pinia, ESLint, Prettier)的模板
-- [wails-template-quasar-ts](https://github.com/sgosiaco/wails-template-quasar-ts) - 使用 TypeScript + Quasar V2(Vue 3、Vite、Sass、Pinia、ESLint、Prettier、带 <script setup> 的Composition API)的模板
-
-## Angular
-
-- [wails-angular-template](https://github.com/TAINCER/wails-angular-template) - 带有 TypeScript, Sass, 热重载, 代码拆分和 i18n 的 Angular
-
-## React
-
-- [wails-react-template](https://github.com/AlienRecall/wails-react-template) - 基于 reactjs 的模板
-- [wails-react-template](https://github.com/flin7/wails-react-template) - 基于 React 并支持实时开发模式的轻量级模板
-- [wails-vite-react-ts](https://github.com/lontten/wails-vite-react-ts) - 基于 Vite + React + TypeScript 的模板
-- [wails-vite-react-ts-tailwind-template](https://github.com/hotafrika/wails-vite-react-ts-tailwind-template) - 一个 React + TypeScript + Vite + TailwindCSS 模板
-
-## Svelte
-
-- [wails-svelte-template](https://github.com/raitonoberu/wails-svelte-template) - 基于 Svelte 的模板
-- [wails-vite-svelte-template](https://github.com/BillBuilt/wails-vite-svelte-template) - 使用 Svelte 和 Vite 的模板
-- [wails-vite-svelte-tailwind-template](https://github.com/BillBuilt/wails-vite-svelte-tailwind-template) - 使用 Svelte 和 Vite 和 TailwindCSS v3 的模板
-- [wails-template-nextjs](https://github.com/LGiki/wails-template-nextjs) - 基于 Next.js + TypeScript 的模板
-
-## Solid
-
-- [wails-template-vite-solid-js](https://github.com/xijaja/wails-template-solid-js) - 基于 Solid + Js + Vite 的模版
-- [wails-template-vite-solid-ts](https://github.com/xijaja/wails-template-solid-ts) - 基于 Solid + Ts + Vite 的模版
-
-## Elm
-
-- [wails-elm-template](https://github.com/benjamin-thomas/wails-elm-template) - 使用函数式编程和 **快速** 的热重载设置开发您的 GUI 应用程序 :tada: :rocket:
-- [wails-template-elm-tailwind](https://github.com/rnice01/wails-template-elm-tailwind) - 结合 Elm + Tailwind CSS + Wails 的力量 :muscle: ! 支持热重载。
-
-## 纯 JavaScript (Vanilla)
-
-- [wails-pure-js-template](https://github.com/KiddoV/wails-pure-js-template) - 一个只有基本 JavaScript、HTML 和 CSS 的模板
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/contributing/developing-new-features.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/contributing/developing-new-features.mdx
deleted file mode 100644
index 9fc9025bd..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/contributing/developing-new-features.mdx
+++ /dev/null
@@ -1,34 +0,0 @@
----
-sidebar_position: 20
----
-
-# 开发新功能
-
-We are always keen to add features to Wails and expand on what the project can do. The process for adding new features are as follows: The process for adding new features are as follows: We are always keen to add features to Wails and expand on what the project can do. The process for adding new features are as follows: The process for adding new features are as follows: The process for adding new features are as follows:
-
-- Pick an enhancement ticket with the "TODO" label. Pick an enhancement ticket with the "TODO" label. Pick an enhancement ticket with the "TODO" label. It's preferable to select one from the current [Backlog](https://github.com/orgs/wailsapp/projects/1/views/1) but the choice is yours.
-- Before developing, check that the ticket includes the following information:
-- The purpose of the enhancement
-- What is out of scope for the enhancement
-- What platforms the enhancement targets (most features should be cross-platform unless there's a very specific reason)
-- If the ticket does not include this information, feel free to request the information from the person who opened the ticket. Sometimes placeholder tickets are created and require more details Sometimes placeholder tickets are created and require more details Sometimes placeholder tickets are created and require more details
-- Comment on the ticket stating you wish to develop the feature
-- Clone the repository and create a branch with the format `feature/_`
-- New features often require documentation so please ensure you have also added or updated the documentation as part of the changes
-- Once the feature is ready for testing, create a draft PR. Once the feature is ready for testing, create a draft PR. Once the feature is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested. Once the feature is ready for testing, create a draft PR. Once the feature is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested. Once the feature is ready for testing, create a draft PR. Once the feature is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested.
-- Once all the testing is completed, please update the status of the PR from draft and leave a message.
-
-:::note
-There is nothing stopping you from opening a ticket and working on it yourself, but please be aware that all
-enhancement requests are reviewed for good fit. Not all ideas will be selected so it's best to have discussion
-on the ticket first.
-::: Not all ideas will be selected so it's best to have discussion
-on the ticket first.
-::: Not all ideas will be selected so it's best to have discussion
-on the ticket first.
-:::
-
-:::warning
-Any PRs opened without a corresponding ticket may be rejected.
-::: :::
-:::
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/contributing/documenting.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/contributing/documenting.mdx
deleted file mode 100644
index 84e472903..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/contributing/documenting.mdx
+++ /dev/null
@@ -1,34 +0,0 @@
----
-sidebar_position: 40
----
-
-# 文档
-
-This website is also the main documentation site for the project. Sometimes this gets out of date and needs some slight adjustments. Some of the documentation isn't written to the best standards either. Developing documentation is hard and so any contribution to this is greatly appreciated. Features without documentation are unfinished so to the project, it's _as important_ as the code.
-
-We generally do not create tickets for updating documentation so if there is text you think should be updated or rephrased then feel free to submit a PR for that. This site is in the main repository under the `website` directory. We use [Docusaurus](https://docusaurus.io/) to create the site so there is plenty of existing documentation and tutorials around to get started. This site is in the main repository under the `website` directory. We use [Docusaurus](https://docusaurus.io/) to create the site so there is plenty of existing documentation and tutorials around to get started. This site is in the main repository under the `website` directory. We use [Docusaurus](https://docusaurus.io/) to create the site so there is plenty of existing documentation and tutorials around to get started.
-
-To set up a local documentation development environment, do the following:
-
-- [Install npm](https://docs.npmjs.com/cli/v8/configuring-npm/install)
-- `cd website`
-- `npm install`
-- `npm run start`
-
-After it has all installed and is running, you should see the site at [`http://localhost:3000`](http://localhost:3000). Any changes made to the site text will be immediately reflected in the browser. Any changes made to the site text will be immediately reflected in the browser. Any changes made to the site text will be immediately reflected in the browser.
-
-## Versioning
-
-We employ a versioning system where we have the "latest" documentation AKA "Next Version" which has all the changes that have occurred since the last release. We also keep the last release documentation as well as the version before that. We also keep the last release documentation as well as the version before that. We also keep the last release documentation as well as the version before that.
-
-There isn't usually a reason to update released documentation so we don't generally update the documents in the `versioned_docs` or `versioned_sidebars` directories.
-
-The "next version" docs are mainly in `website/docs` with some "version independent" documents in `src/pages`. Any updates should be made in the `website/docs` directory. Any updates should be made in the `website/docs` directory. Any updates should be made in the `website/docs` directory.
-
-## Languages
-
-The default documents of the Wails project are English documents. We use the "crowdin" tool to translate documents in other languages and synchronize them to the website. You can [join our project](https://crowdin.com/project/wails) and submit your translations to make contributions.
-
-### Add new language
-
-If you want to add a new language to the documentation, please follow the prompts to [fill in and submit an Issue](https://github.com/wailsapp/wails/issues/new?assignees=&labels=documentation&template=documentation.yml). After being confirmed by the maintainer, we will add the language to the "crowdin" and you will then be able to submit your translation.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/contributing/fixing-bugs.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/contributing/fixing-bugs.mdx
deleted file mode 100644
index 01eceeccd..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/contributing/fixing-bugs.mdx
+++ /dev/null
@@ -1,29 +0,0 @@
----
-sidebar_position: 30
----
-
-# 修复漏洞
-
-The process for fixing bugs are as follows:
-
-- Check the current [Backlog](https://github.com/orgs/wailsapp/projects/1/views/1) and select a bug to fix
-- Before developing, check that the ticket includes the following information:
-- The scope of the issue including platforms affected
-- The steps to reproduce. The steps to reproduce. The steps to reproduce. Sometimes bugs are opened that are not Wails issues and the onus is on the reporter to prove that it is a Wails issue with a minimal reproducible example
-- The output of `wails doctor`
-- If the ticket does not include this information, feel free to request the information from the person who opened the ticket.
-- Comment on the ticket stating you wish to develop a fix
-- Clone the repository and create a branch with the format `bugfix/_`
-- Once the fix is ready for testing, create a draft PR. Once the fix is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested. Once the fix is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested.
-- Once all the testing is completed, please update the status of the PR from draft and leave a message.
-
-:::note
-There is nothing stopping you from opening a ticket and working on it yourself, but please be aware that all
-bugfixes should be discussed as the approach may have unintended side effects.
-::: :::
-:::
-
-:::warning
-Any PRs opened without a corresponding ticket may be rejected.
-::: :::
-:::
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/contributing/setting-up-a-dev-environment.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/contributing/setting-up-a-dev-environment.mdx
deleted file mode 100644
index 1133e275d..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/contributing/setting-up-a-dev-environment.mdx
+++ /dev/null
@@ -1,30 +0,0 @@
----
-sidebar_position: 10
----
-
-# 设置开发环境
-
-You can set up a development environment by doing the following:
-
-- Install the latest versions of Go and Git
-- `git clone https://github.com/wailsapp/wails`
-- `cd wails/v2/cmd/wails`
-- `go install`
-
-NOTE: The directory that you cloned the project into will now be called "clonedir".
-
-The Wails CLI will now be at the very latest version.
-
-To update projects to use the latest version, update the project's `go.mod` and ensure the following line is at the bottom of the file:
-
-`replace github.com/wailsapp/wails/v2 => `
-
-Example:
-
-On Windows: `replace github.com/wailsapp/wails/v2 => C:\Users\leaan\Documents\wails-v2-beta\wails\v2`
-
-On 'nix: `replace github.com/wailsapp/wails/v2 => /home/me/projects/wails/v2`
-
-To revert back to a stable version, run:
-
-`go install github.com/wailsapp/wails/v2/cmd/wails@latest`
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/contributing/ways-of-contributing.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/contributing/ways-of-contributing.mdx
deleted file mode 100644
index 3bbe9a889..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/contributing/ways-of-contributing.mdx
+++ /dev/null
@@ -1,18 +0,0 @@
----
-sidebar_position: 1
----
-
-# 贡献方式
-
-Wails is an open source, community driven project. We welcome anyone to join us in contributing to the project. This documentation is aimed at anyone wishing to get familiar with the project and the development processes. We welcome anyone to join us in contributing to the project. This documentation is aimed at anyone wishing to get familiar with the project and the development processes.
-
-There are many ways to contribute to the project:
-
-- Developing new features
-- Fixing bugs
-- Testing
-- Documenting features
-- Writing tutorials / guides
-- Helping others on the issues + discussions boards
-
-Guides for these have been created in their own sections. Guides for these have been created in their own sections. Guides for these have been created in their own sections. Before getting started, please introduce yourself in the [Contributing to Wails](https://github.com/wailsapp/wails/discussions/1520) discussion.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/gettingstarted/_category_.json b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/gettingstarted/_category_.json
deleted file mode 100644
index 597b920df..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/gettingstarted/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Getting Started",
- "position": 10
-}
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/gettingstarted/building.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/gettingstarted/building.mdx
deleted file mode 100644
index c4fe879bc..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/gettingstarted/building.mdx
+++ /dev/null
@@ -1,22 +0,0 @@
----
-sidebar_position: 6
----
-
-# 编译您的项目
-
-从项目目录,运行 `wails build`。 这将编译您的项目并将构建的可用于生产的二进制文件保存在 `build/bin` 目录中。
-
-如果您运行二进制文件,您应该会看到默认应用程序:
-
-```mdx-code-block
-
-
-```
-
-### Linux
-
-这定义了 [Linux 特定的选项](#linux)。
-
-名称:Linux 类型:`*linux.Options`
-
-#### 图标
-
-设置代表窗口的图标。 当窗口最小化(也称为图标化)时使用此图标。
-
-名称:Icon 类型:`[]byte`
-
-一些窗口管理器或桌面环境也可能将其放置在窗口框架中,或在其他上下文中显示。 在其他情况下,根本不使用该图标,因此您的预计情况可能会有所不同。
-
-注意:Wayland 上的 Gnome 至少不显示此图标。 要在那里有一个应用程序图标,必须使用一个`.desktop`文件。 在 KDE 上它应该可以工作。
-
-图标应该以自然绘制的任何尺寸提供;也就是说,在传递图像之前不要缩放图像。 缩放将延迟到当所需的最终尺寸已知的最后一刻,以获得最佳质量。
-
-#### 窗口半透明
-
-将此设置为 `true` 将使窗口半透明。 某些窗口管理员可能忽略它,或导致黑窗口。
-
-名称:WindowIsTranslucent 类型:`bool`
\ No newline at end of file
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/reference/project-config.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/reference/project-config.mdx
deleted file mode 100644
index 092988431..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/reference/project-config.mdx
+++ /dev/null
@@ -1,55 +0,0 @@
----
-sidebar_position: 5
----
-
-# 项目配置
-
-项目配置在项目目录中的 `wails.json` 文件中。 配置的结构是:
-
-```json
-{
- "name": "[The project name]",
- "assetdir": "[Relative path to the directory containing the compiled assets, this is normally inferred and could be left empty]",
- "reloaddirs": "[Additional directories to trigger reloads (comma separated), this is only used for some advanced asset configurations]",
- "frontend:install": "[The command to install node dependencies, run in the frontend directory - often `npm install`]",
- "frontend:build": "[The command to build the assets, run in the frontend directory - often `npm run build`]",
- "frontend:dev": "[This command has been replaced by frontend:dev:build. If frontend:dev:build is not specified will falls back to this command. \nIf this command is also not specified will falls back to frontend:build]",
- "frontend:dev:build": "[This command is the dev equivalent of frontend:build. If not specified falls back to frontend:dev]",
- "frontend:dev:install": "[This command is the dev equivalent of frontend:install. If not specified falls back to frontend:install]",
- "frontend:dev:watcher": "[This command is run in a separate process on `wails dev`. Useful for 3rd party watchers or starting 3d party dev servers]",
- "frontend:dev:serverUrl": "[URL to a 3rd party dev server to be used to serve assets, EG Vite. \nIf this is set to 'auto' then the devServerUrl will be inferred from the Vite output]",
- "wailsjsdir": "[Relative path to the directory that the auto-generated JS modules will be created]",
- "version": "[Project config version]",
- "outputfilename": "[The name of the binary]",
- "debounceMS": 100, // The default time the dev server waits to reload when it detects a change in assets
- "devServer": "[Address to bind the wails dev sever to. Default: localhost:34115]",
- "appargs": "[Arguments passed to the application in shell style when in dev mode]",
- "runNonNativeBuildHooks": false, // Defines if build hooks should be run though they are defined for an OS other than the host OS.
- "preBuildHooks": {
- "GOOS/GOARCH": "[The command that will be executed before a build of the specified GOOS/GOARCH: ${platform} is replaced with the "GOOS/GOARCH". The "GOOS/GOARCH" hook is executed before the "GOOS/*" and "*/*" hook.]",
- "GOOS/*": "[The command that will be executed before a build of the specified GOOS: ${platform} is replaced with the "GOOS/GOARCH". The "GOOS/*" hook is executed before the "*/*" hook.]",
- "*/*": "[The command that will be executed before every build: ${platform} is replaced with the "GOOS/GOARCH".]"
- },
- "postBuildHooks": {
- "GOOS/GOARCH": "[The command that will be executed after a build of the specified GOOS/GOARCH: ${platform} is replaced with the "GOOS/GOARCH" and ${bin} with the path to the compiled binary. The "GOOS/GOARCH" hook is executed before the "GOOS/*" and "*/*" hook.]",
- "GOOS/*": "[The command that will be executed after a build of the specified GOOS: ${platform} is replaced with the "GOOS/GOARCH" and ${bin} with the path to the compiled binary. The "GOOS/*" hook is executed before the "*/*" hook.]",
- "*/*": "[The command that will be executed after every build: ${platform} is replaced with the "GOOS/GOARCH" and ${bin} with the path to the compiled binary.]"
- },
- "info": { // Data used to populate manifests and version info.
- "companyName": "[The company name. Default: [The project name]]",
- "productName": "[The product name. Default: [The project name]]",
- "productVersion": "[The version of the product. Default: '1.0.0']",
- "copyright": "[The copyright of the product. Default: 'Copyright.........']",
- "comments": "[A short comment of the app. Default: 'Built using Wails (https://wails.app)']"
- },
- "nsisType": "['multiple': One installer per architecture. 'single': Single universal installer for all architectures being built. Default: 'multiple']",
- "obfuscated": "[Whether the app should be obfuscated. Default: false]",
- "garbleargs": "[The arguments to pass to the garble command when using the obfuscated flag]"
-}
-```
-
-该文件将在运行 `wails build` 或 `wails dev` 时,由 Wails CLI 读取。
-
-`wails build/dev` 命令中的 `assetdir`、`reloaddirs`、`wailsjsdir`、`debounceMS`、`devserver` 和 `frontenddevserverurl` 标志将覆盖项目配置并作为后续运行的默认值。
-
-此文件的 JSON 模型位于 [此处](https://wails.io/schemas/config.v2.json)。
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/reference/runtime/_category_.json b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/reference/runtime/_category_.json
deleted file mode 100644
index ac6d55488..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/reference/runtime/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Runtime",
- "position": 1
-}
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/reference/runtime/browser.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/reference/runtime/browser.mdx
deleted file mode 100644
index 26b81b958..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/reference/runtime/browser.mdx
+++ /dev/null
@@ -1,13 +0,0 @@
----
-sidebar_position: 7
----
-
-# 浏览器
-
-这些方法与系统浏览器相关。
-
-### 浏览器打开 URL
-
-使用系统默认浏览器打开给定的 URL。
-
-Go: `BrowserOpenURL(ctx context.Context, url string)` JS: `BrowserOpenURL(url string)`
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/reference/runtime/dialog.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/reference/runtime/dialog.mdx
deleted file mode 100644
index 11c03cdd4..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.2.0/reference/runtime/dialog.mdx
+++ /dev/null
@@ -1,302 +0,0 @@
----
-sidebar_position: 5
----
-
-# 对话框
-
-运行时的这一部分提供对原生对话框的调用,例如文件选择器和消息框。
-
-:::info Javascript
-
-JS 运行时当前不支持对话框。
-
-:::
-
-### 打开选择目录对话框
-
-打开一个对话框,提示用户选择目录。 可以使用 [ 打开选择文件对话框参数选项](#打开选择文件对话框参数选项) 进行自定义。
-
-Go: `OpenDirectoryDialog(ctx context.Context, dialogOptions OpenDialogOptions) (string, error)`
-
-返回值: 所选目录(如果用户取消则为空白)或错误
-
-### 打开选择文件对话框
-
-打开一个对话框,提示用户选择文件。 可以使用 [ 打开选择文件对话框参数选项](#打开选择文件对话框参数选项) 进行自定义。
-
-Go: `OpenFileDialog(ctx context.Context, dialogOptions OpenDialogOptions) (string, error)`
-
-返回值: 所选文件(如果用户取消则为空白)或错误
-
-### 打开选择多文件对话框
-
-打开一个对话框,提示用户选择多个文件。 可以使用 [ 打开选择文件对话框参数选项](#打开选择文件对话框参数选项) 进行自定义。
-
-Go: `OpenMultipleFilesDialog(ctx context.Context, dialogOptions OpenDialogOptions) ([]string, error)`
-
-返回值: 选定的文件(如果用户取消则为 nil)或错误
-
-### 保存文件对话框
-
-打开一个对话框,提示用户选择文件名以进行保存。 可以使用 [保存文件对话框参数选项](#保存文件对话框参数选项) 自定义。
-
-Go: `SaveFileDialog(ctx context.Context, dialogOptions SaveDialogOptions) (string, error)`
-
-返回值: 所选文件(如果用户取消则为空白)或错误
-
-### 消息对话框
-
-使用消息对话框显示消息。 可以使用 [消息对话框参数选项](#消息对话框参数选项) 进行自定义。
-
-Go: `MessageDialog(ctx context.Context, dialogOptions MessageDialogOptions) (string, error)`
-
-返回值: 所选按钮的文本或错误
-
-## 参数选项
-
-### 打开选择文件对话框参数选项
-
-```go
-type OpenDialogOptions struct {
- DefaultDirectory string
- DefaultFilename string
- Title string
- Filters []FileFilter
- ShowHiddenFiles bool
- CanCreateDirectories bool
- ResolvesAliases bool
- TreatPackagesAsDirectories bool
-}
-```
-
-| 字段 | 描述 | Win | Mac | Lin |
-| -------------------------- | ------------------- | --- | --- | --- |
-| DefaultDirectory | 对话框打开时显示的目录 | ✅ | ✅ | ✅ |
-| DefaultFilename | 默认文件名 | ✅ | ✅ | ✅ |
-| Title | 对话框的标题 | ✅ | ✅ | ✅ |
-| [Filters](#filefilter) | 文件过滤器列表 | ✅ | ✅ | ✅ |
-| ShowHiddenFiles | 显示系统隐藏的文件 | | ✅ | ✅ |
-| CanCreateDirectories | 允许用户创建目录 | | ✅ | |
-| ResolvesAliases | 如果为 true,则返回文件而不是别名 | | ✅ | |
-| TreatPackagesAsDirectories | 允许导航到包 | | ✅ | |
-
-### 保存文件对话框参数选项
-
-```go
-type SaveDialogOptions struct {
- DefaultDirectory string
- DefaultFilename string
- Title string
- Filters []FileFilter
- ShowHiddenFiles bool
- CanCreateDirectories bool
- TreatPackagesAsDirectories bool
-}
-```
-
-| 字段 | 描述 | Win | Mac | Lin |
-| -------------------------- | ----------- | --- | --- | --- |
-| DefaultDirectory | 对话框打开时显示的目录 | ✅ | ✅ | ✅ |
-| DefaultFilename | 默认文件名 | ✅ | ✅ | ✅ |
-| Title | 对话框的标题 | ✅ | ✅ | ✅ |
-| [Filters](#filefilter) | 文件过滤器列表 | ✅ | ✅ | ✅ |
-| ShowHiddenFiles | 显示系统隐藏的文件 | | ✅ | ✅ |
-| CanCreateDirectories | 允许用户创建目录 | | ✅ | |
-| TreatPackagesAsDirectories | 允许导航到包 | | ✅ | |
-
-### 消息对话框参数选项
-
-```go
-type MessageDialogOptions struct {
- Type DialogType
- Title string
- Message string
- Buttons []string
- DefaultButton string
- CancelButton string
-}
-```
-
-| 字段 | 描述 | Win | Mac | Lin |
-| ------------- | ------------------------------ | -------------- | --- | --- |
-| 类型 | 消息对话框的类型,例如问题、信息... | ✅ | ✅ | ✅ |
-| Title | 对话框的标题 | ✅ | ✅ | ✅ |
-| Message | 向用户显示的消息 | ✅ | ✅ | ✅ |
-| Buttons | 按钮标题列表 | | ✅ | |
-| DefaultButton | 带有此文本的按钮应被视为默认按钮。 必定 `return`。 | ✅[*](#windows) | ✅ | |
-| CancelButton | 带有此文本的按钮应被视为取消。 必定 `escape` | | ✅ | |
-
-#### Windows
-
-Windows 具有标准对话框类型,其中的按钮不可自定义。 返回的值将是以下之一:"Ok"、"Cancel"、"Abort"、"Retry"、"Ignore"、"Yes"、"No"、"Try Again"或"Continue"。
-
-对于问题对话框,默认按钮是 “是”,取消按钮是 “否”。 可以通过将 `默认按钮` 值设置为 `"否"` 来改变这一点。
-
-示例:
-```go
- result, err := runtime.MessageDialog(a.ctx, runtime.MessageDialogOptions{
- Type: runtime.QuestionDialog,
- Title: "Question",
- Message: "Do you want to continue?",
- DefaultButton: "No",
- })
-```
-
-#### Linux
-
-Linux 有标准的对话框类型,其中的按钮是不可定制的。 返回的值将是以下之一:“Ok”、“Cancel”、“Yes”、“No”
-
-#### Mac
-
-Mac 上的消息对话框最多可以指定 4 个按钮。 如果没有 `DefaultButton` 或 `CancelButton` 给出,第一个按钮被认为是默认的并绑定到 `return` 键。
-
-对于以下代码:
-
-```go
-selection, err := runtime.MessageDialog(b.ctx, runtime.MessageDialogOptions{
- Title: "It's your turn!",
- Message: "Select a number",
- Buttons: []string{"one", "two", "three", "four"},
-})
-```
-
-第一个按钮显示为默认值:
-
-```mdx-code-block
-
-```
-
-[EmailIt](https://github.com/raguay/EmailIt/) is a Wails 2 program that is a markdown based email sender only with nine notepads, scripts to manipulate the text, and templates. It also has a builtin [Node-Red](https://nodered.org/) server, scripts terminal, and the [ScriptBar](https://github.com/raguay/ScriptBarApp) program for displaying results from Node-Red or a script on your system. Documentation is very scarce, but the programs works. It’s built using Wails2 and Svelte, and the download is a universal macOS application.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/encrypteasy.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/encrypteasy.mdx
deleted file mode 100644
index 7504950ea..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/encrypteasy.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
-# EncryptEasy
-
-```mdx-code-block
-
-
-
-
-```
-
-**[EncryptEasy](https://www.encrypteasy.app) is a simple and easy to use PGP encryption tool, managing all your and your contacts keys. Encryption should be simple. Developed with Wails.**
-
-Encrypting messages using PGP is the industry standard. Everyone has a private and a public key. Your private key, well, needs to be kept private so only you can read messages. Your public key is distributed to anyone who wants to send you secret, encrypted messages. Managing keys, encrypting messages and decrypting messages should be a smooth experience. EncryptEasy is all about making it easy.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/minecraftupdater.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/minecraftupdater.mdx
deleted file mode 100644
index 2f6c7c72b..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/minecraftupdater.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
-# Minecraft Updater
-
-```mdx-code-block
-
-
-
-
-```
-
-[Minecraft Updater](https://github.com/Gurkengewuerz/MinecraftModUpdater) is a utility tool to update and synchronize Minecraft mods for your userbase. It’s built using Wails2 and React with [antd](https://ant.design/) as frontend framework.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/modalfilemanager.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/modalfilemanager.mdx
deleted file mode 100644
index f8e2bcd66..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/modalfilemanager.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
-# Modal File Manager
-
-```mdx-code-block
-
-
-
-
-```
-
-[Modal File Manager](https://github.com/raguay/ModalFileManager) is a dual pane file manager using web technologies. My original design was based on NW.js and can be found [here](https://github.com/raguay/ModalFileManager-NWjs). This version uses the same Svelte based frontend code (but it has be greatly modified since the departure from NW.js), but the backend is a [Wails 2](https://wails.io/) implementation. By using this implementation, I no longer use command line `rm`, `cp`, etc. commands. It is fully coded using Go and runs much faster than the previous versions.
-
-This file manager is designed around the same principle as Vim: a state controlled keyboard actions. The number of states isn't fixed, but very programmable. Therefore, an infinite number of keyboard configurations can be created and used. This is the main difference from other file managers.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/mollywallet.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/mollywallet.mdx
deleted file mode 100644
index 5d846d06d..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/mollywallet.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Molley Wallet
-
-```mdx-code-block
-
-
-
-
-```
-
-[Molly Wallet](https://github.com/grvlle/constellation_wallet/) the official $DAG wallet of the Constellation Network. It'll let users interact with the Hypergraph Network in various ways, not limited to producing $DAG transactions.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/october.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/october.mdx
deleted file mode 100644
index 66d634dc5..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/october.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
-# October
-
-```mdx-code-block
-
-
-
-
-```
-
-[October](https://october.utf9k.net) is a small Wails application that makes it really easy to extract highlights from [Kobo eReaders](https://en.wikipedia.org/wiki/Kobo_eReader) and then forward them to [Readwise](https://readwise.io).
-
-It has a relatively small scope with all platform versions weighing in under 10MB, and that's without enabling [UPX compression](https://upx.github.io/)!
-
-In contrast, the author's previous attempts with Electron quickly bloated to several hundred megabytes.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/optimus.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/optimus.mdx
deleted file mode 100644
index 4f87479d6..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/optimus.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Optimus
-
-```mdx-code-block
-
-
-
-
-```
-
-[Optimus](https://github.com/splode/optimus) is a desktop image optimization application. It supports conversion and compression between WebP, JPEG, and PNG image formats.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/portfall.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/portfall.mdx
deleted file mode 100644
index 03e740f4c..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/portfall.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Portfall
-
-```mdx-code-block
-
-
-
-
-```
-
-[Portfall](https://github.com/rekon-oss/portfall) - A desktop k8s port-forwarding portal for easy access to all your cluster UIs
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/restic-browser.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/restic-browser.mdx
deleted file mode 100644
index 3646384ec..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/restic-browser.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
-# Restic Browser
-
-```mdx-code-block
-
-
-
-
-```
-
-[Restic-Browser](https://github.com/emuell/restic-browser) - A simple, cross-platform [restic](https://github.com/restic/restic) backup GUI for browsing and restoring restic repositories.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/riftshare.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/riftshare.mdx
deleted file mode 100644
index 6224bbf89..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/riftshare.mdx
+++ /dev/null
@@ -1,21 +0,0 @@
-# RiftShare
-
-```mdx-code-block
-
-
-
-
-```
-
-Easy, Secure, and Free file sharing for everyone. Learn more at [Riftshare.app](https://riftshare.app)
-
-## 功能
-
-- Easy secure file sharing between computers both in the local network and through the internet
-- Supports sending files or directories securely through the [magic wormhole protocol](https://magic-wormhole.readthedocs.io/en/latest/)
-- Compatible with all other apps using magic wormhole (magic-wormhole or wormhole-william CLI, wormhole-gui, etc.)
-- Automatic zipping of multiple selected files to send at once
-- Full animations, progress bar, and cancellation support for sending and receiving
-- Native OS File Selection
-- Open files in one click once received
-- Auto Update - don't worry about having the latest release!
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/scriptbar.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/scriptbar.mdx
deleted file mode 100644
index 2ccb2acb4..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/scriptbar.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# ScriptBar
-
-```mdx-code-block
-
-
-
-
-```
-
-[ScriptBar](https://GitHub.com/raguay/ScriptBarApp) is a program to show the output of the embedded [Node-Red](https://nodered.org) server in the [EmailIt](https://GitHub.com/raguay/EmailIt) application. It also displays the output of scripts on your system. ScriptBar doesn't put them in the menubar, but has them all in a convient window for easy viewing. You can have multiple tabs to have many different things show. You can also keep the links to your most visited web sites.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/surge.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/surge.mdx
deleted file mode 100644
index c3b3fb4c0..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/surge.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Surge
-
-```mdx-code-block
-
-
-
-
-```
-
-[Surge](https://getsurge.io/) is a p2p filesharing app designed to utilize blockchain technologies to enable 100% anonymous file transfers. Surge is end-to-end encrypted, decentralized and open source.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/wally.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/wally.mdx
deleted file mode 100644
index 7408aa585..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/wally.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Wally
-
-```mdx-code-block
-
-
-
-
-```
-
-[Wally](https://ergodox-ez.com/pages/wally) is the official firmware flasher for [Ergodox](https://ergodox-ez.com/) keyboards. It looks great and is a fantastic example of what you can achieve with Wails: the ability to combine the power of Go and the rich graphical tools of the web development world.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/wombat.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/wombat.mdx
deleted file mode 100644
index f100c55e2..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/wombat.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Wombat
-
-```mdx-code-block
-
-```
-
-[Ytd](https://github.com/marcio199226/ytd/tree/v2-wails) is an app for downloading tracks from youtube, creating offline playlists and share them with your friends, your friends will be able to playback your playlists or download them for offline listening, has an built-in player.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/contributing/developing-new-features.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/contributing/developing-new-features.mdx
deleted file mode 100644
index 9fc9025bd..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/contributing/developing-new-features.mdx
+++ /dev/null
@@ -1,34 +0,0 @@
----
-sidebar_position: 20
----
-
-# 开发新功能
-
-We are always keen to add features to Wails and expand on what the project can do. The process for adding new features are as follows: The process for adding new features are as follows: We are always keen to add features to Wails and expand on what the project can do. The process for adding new features are as follows: The process for adding new features are as follows: The process for adding new features are as follows:
-
-- Pick an enhancement ticket with the "TODO" label. Pick an enhancement ticket with the "TODO" label. Pick an enhancement ticket with the "TODO" label. It's preferable to select one from the current [Backlog](https://github.com/orgs/wailsapp/projects/1/views/1) but the choice is yours.
-- Before developing, check that the ticket includes the following information:
-- The purpose of the enhancement
-- What is out of scope for the enhancement
-- What platforms the enhancement targets (most features should be cross-platform unless there's a very specific reason)
-- If the ticket does not include this information, feel free to request the information from the person who opened the ticket. Sometimes placeholder tickets are created and require more details Sometimes placeholder tickets are created and require more details Sometimes placeholder tickets are created and require more details
-- Comment on the ticket stating you wish to develop the feature
-- Clone the repository and create a branch with the format `feature/_`
-- New features often require documentation so please ensure you have also added or updated the documentation as part of the changes
-- Once the feature is ready for testing, create a draft PR. Once the feature is ready for testing, create a draft PR. Once the feature is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested. Once the feature is ready for testing, create a draft PR. Once the feature is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested. Once the feature is ready for testing, create a draft PR. Once the feature is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested.
-- Once all the testing is completed, please update the status of the PR from draft and leave a message.
-
-:::note
-There is nothing stopping you from opening a ticket and working on it yourself, but please be aware that all
-enhancement requests are reviewed for good fit. Not all ideas will be selected so it's best to have discussion
-on the ticket first.
-::: Not all ideas will be selected so it's best to have discussion
-on the ticket first.
-::: Not all ideas will be selected so it's best to have discussion
-on the ticket first.
-:::
-
-:::warning
-Any PRs opened without a corresponding ticket may be rejected.
-::: :::
-:::
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/contributing/documenting.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/contributing/documenting.mdx
deleted file mode 100644
index 84e472903..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/contributing/documenting.mdx
+++ /dev/null
@@ -1,34 +0,0 @@
----
-sidebar_position: 40
----
-
-# 文档
-
-This website is also the main documentation site for the project. Sometimes this gets out of date and needs some slight adjustments. Some of the documentation isn't written to the best standards either. Developing documentation is hard and so any contribution to this is greatly appreciated. Features without documentation are unfinished so to the project, it's _as important_ as the code.
-
-We generally do not create tickets for updating documentation so if there is text you think should be updated or rephrased then feel free to submit a PR for that. This site is in the main repository under the `website` directory. We use [Docusaurus](https://docusaurus.io/) to create the site so there is plenty of existing documentation and tutorials around to get started. This site is in the main repository under the `website` directory. We use [Docusaurus](https://docusaurus.io/) to create the site so there is plenty of existing documentation and tutorials around to get started. This site is in the main repository under the `website` directory. We use [Docusaurus](https://docusaurus.io/) to create the site so there is plenty of existing documentation and tutorials around to get started.
-
-To set up a local documentation development environment, do the following:
-
-- [Install npm](https://docs.npmjs.com/cli/v8/configuring-npm/install)
-- `cd website`
-- `npm install`
-- `npm run start`
-
-After it has all installed and is running, you should see the site at [`http://localhost:3000`](http://localhost:3000). Any changes made to the site text will be immediately reflected in the browser. Any changes made to the site text will be immediately reflected in the browser. Any changes made to the site text will be immediately reflected in the browser.
-
-## Versioning
-
-We employ a versioning system where we have the "latest" documentation AKA "Next Version" which has all the changes that have occurred since the last release. We also keep the last release documentation as well as the version before that. We also keep the last release documentation as well as the version before that. We also keep the last release documentation as well as the version before that.
-
-There isn't usually a reason to update released documentation so we don't generally update the documents in the `versioned_docs` or `versioned_sidebars` directories.
-
-The "next version" docs are mainly in `website/docs` with some "version independent" documents in `src/pages`. Any updates should be made in the `website/docs` directory. Any updates should be made in the `website/docs` directory. Any updates should be made in the `website/docs` directory.
-
-## Languages
-
-The default documents of the Wails project are English documents. We use the "crowdin" tool to translate documents in other languages and synchronize them to the website. You can [join our project](https://crowdin.com/project/wails) and submit your translations to make contributions.
-
-### Add new language
-
-If you want to add a new language to the documentation, please follow the prompts to [fill in and submit an Issue](https://github.com/wailsapp/wails/issues/new?assignees=&labels=documentation&template=documentation.yml). After being confirmed by the maintainer, we will add the language to the "crowdin" and you will then be able to submit your translation.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/contributing/fixing-bugs.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/contributing/fixing-bugs.mdx
deleted file mode 100644
index 01eceeccd..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/contributing/fixing-bugs.mdx
+++ /dev/null
@@ -1,29 +0,0 @@
----
-sidebar_position: 30
----
-
-# 修复漏洞
-
-The process for fixing bugs are as follows:
-
-- Check the current [Backlog](https://github.com/orgs/wailsapp/projects/1/views/1) and select a bug to fix
-- Before developing, check that the ticket includes the following information:
-- The scope of the issue including platforms affected
-- The steps to reproduce. The steps to reproduce. The steps to reproduce. Sometimes bugs are opened that are not Wails issues and the onus is on the reporter to prove that it is a Wails issue with a minimal reproducible example
-- The output of `wails doctor`
-- If the ticket does not include this information, feel free to request the information from the person who opened the ticket.
-- Comment on the ticket stating you wish to develop a fix
-- Clone the repository and create a branch with the format `bugfix/_`
-- Once the fix is ready for testing, create a draft PR. Once the fix is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested. Once the fix is ready for testing, create a draft PR. Please ensure the PR description has the test scenarios and test cases listed with checkmarks, so that others can know what still needs to be tested.
-- Once all the testing is completed, please update the status of the PR from draft and leave a message.
-
-:::note
-There is nothing stopping you from opening a ticket and working on it yourself, but please be aware that all
-bugfixes should be discussed as the approach may have unintended side effects.
-::: :::
-:::
-
-:::warning
-Any PRs opened without a corresponding ticket may be rejected.
-::: :::
-:::
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/contributing/setting-up-a-dev-environment.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/contributing/setting-up-a-dev-environment.mdx
deleted file mode 100644
index 1133e275d..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/contributing/setting-up-a-dev-environment.mdx
+++ /dev/null
@@ -1,30 +0,0 @@
----
-sidebar_position: 10
----
-
-# 设置开发环境
-
-You can set up a development environment by doing the following:
-
-- Install the latest versions of Go and Git
-- `git clone https://github.com/wailsapp/wails`
-- `cd wails/v2/cmd/wails`
-- `go install`
-
-NOTE: The directory that you cloned the project into will now be called "clonedir".
-
-The Wails CLI will now be at the very latest version.
-
-To update projects to use the latest version, update the project's `go.mod` and ensure the following line is at the bottom of the file:
-
-`replace github.com/wailsapp/wails/v2 => `
-
-Example:
-
-On Windows: `replace github.com/wailsapp/wails/v2 => C:\Users\leaan\Documents\wails-v2-beta\wails\v2`
-
-On 'nix: `replace github.com/wailsapp/wails/v2 => /home/me/projects/wails/v2`
-
-To revert back to a stable version, run:
-
-`go install github.com/wailsapp/wails/v2/cmd/wails@latest`
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/contributing/ways-of-contributing.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/contributing/ways-of-contributing.mdx
deleted file mode 100644
index 3bbe9a889..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/contributing/ways-of-contributing.mdx
+++ /dev/null
@@ -1,18 +0,0 @@
----
-sidebar_position: 1
----
-
-# 贡献方式
-
-Wails is an open source, community driven project. We welcome anyone to join us in contributing to the project. This documentation is aimed at anyone wishing to get familiar with the project and the development processes. We welcome anyone to join us in contributing to the project. This documentation is aimed at anyone wishing to get familiar with the project and the development processes.
-
-There are many ways to contribute to the project:
-
-- Developing new features
-- Fixing bugs
-- Testing
-- Documenting features
-- Writing tutorials / guides
-- Helping others on the issues + discussions boards
-
-Guides for these have been created in their own sections. Guides for these have been created in their own sections. Guides for these have been created in their own sections. Before getting started, please introduce yourself in the [Contributing to Wails](https://github.com/wailsapp/wails/discussions/1520) discussion.
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/_category_.json b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/_category_.json
deleted file mode 100644
index 597b920df..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Getting Started",
- "position": 10
-}
diff --git a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/building.mdx b/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/building.mdx
deleted file mode 100644
index c4fe879bc..000000000
--- a/website/i18n/zh-Hans/docusaurus-plugin-content-docs/version-v2.3.0/gettingstarted/building.mdx
+++ /dev/null
@@ -1,22 +0,0 @@
----
-sidebar_position: 6
----
-
-# 编译您的项目
-
-从项目目录,运行 `wails build`。 这将编译您的项目并将构建的可用于生产的二进制文件保存在 `build/bin` 目录中。
-
-如果您运行二进制文件,您应该会看到默认应用程序:
-
-```mdx-code-block
-
@@ -194,6 +267,7 @@
[go-winloader](https://github.com/jchv/go-winloader) have made the Windows version possible.
- [Tad Vizbaras](https://github.com/tadvi) - His winc project was the first step down the path to a pure Go Wails.
- [Mat Ryer](https://github.com/matryer) - For advice, support and bants.
+- [Byron Chris](https://github.com/bh90210) - For his long term contributions to this project.
- [Dustin Krysak](https://wiki.ubuntu.com/bashfulrobot) - His support and feedback has been invaluable.
- [Justen Walker](https://github.com/justenwalker/) - For helping wrangle COM issues which got v2 over the line.
- [Wang, Chi](https://github.com/patr0nus/) - The DeskGap project was a huge influence on the direction of Wails v2.
diff --git a/website/versioned_docs/version-v2.3.0/appendix/_category_.json b/website/versioned_docs/version-v2.3.0/appendix/_category_.json
deleted file mode 100644
index 83af4ca28..000000000
--- a/website/versioned_docs/version-v2.3.0/appendix/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Appendix",
- "position": 70
-}
diff --git a/website/versioned_docs/version-v2.3.0/community/_category_.json b/website/versioned_docs/version-v2.3.0/community/_category_.json
deleted file mode 100644
index 524986e1e..000000000
--- a/website/versioned_docs/version-v2.3.0/community/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Community",
- "position": 50
-}
diff --git a/website/versioned_docs/version-v2.3.0/community/showcase/_category_.json b/website/versioned_docs/version-v2.3.0/community/showcase/_category_.json
deleted file mode 100644
index 276e283b7..000000000
--- a/website/versioned_docs/version-v2.3.0/community/showcase/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Showcase",
- "position": 1
-}
diff --git a/website/versioned_docs/version-v2.3.0/community/showcase/emailit.mdx b/website/versioned_docs/version-v2.3.0/community/showcase/emailit.mdx
deleted file mode 100644
index 04150ba28..000000000
--- a/website/versioned_docs/version-v2.3.0/community/showcase/emailit.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# EmailIt
-
-```mdx-code-block
-
-
-
-
-```
-
-[EmailIt](https://github.com/raguay/EmailIt/) is a Wails 2 program that is a markdown based email sender only with nine notepads, scripts to manipulate the text, and templates. It also has a builtin [Node-Red](https://nodered.org/) server, scripts terminal, and the [ScriptBar](https://github.com/raguay/ScriptBarApp) program for displaying results from Node-Red or a script on your system. Documentation is very scarce, but the programs works. It’s built using Wails2 and Svelte, and the download is a universal macOS application.
diff --git a/website/versioned_docs/version-v2.3.0/community/showcase/encrypteasy.mdx b/website/versioned_docs/version-v2.3.0/community/showcase/encrypteasy.mdx
deleted file mode 100644
index 7504950ea..000000000
--- a/website/versioned_docs/version-v2.3.0/community/showcase/encrypteasy.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
-# EncryptEasy
-
-```mdx-code-block
-
-
-
-
-```
-
-**[EncryptEasy](https://www.encrypteasy.app) is a simple and easy to use PGP encryption tool, managing all your and your contacts keys. Encryption should be simple. Developed with Wails.**
-
-Encrypting messages using PGP is the industry standard. Everyone has a private and a public key. Your private key, well, needs to be kept private so only you can read messages. Your public key is distributed to anyone who wants to send you secret, encrypted messages. Managing keys, encrypting messages and decrypting messages should be a smooth experience. EncryptEasy is all about making it easy.
diff --git a/website/versioned_docs/version-v2.3.0/community/showcase/minecraftupdater.mdx b/website/versioned_docs/version-v2.3.0/community/showcase/minecraftupdater.mdx
deleted file mode 100644
index 2f6c7c72b..000000000
--- a/website/versioned_docs/version-v2.3.0/community/showcase/minecraftupdater.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
-# Minecraft Updater
-
-```mdx-code-block
-
-
-
-
-```
-
-[Minecraft Updater](https://github.com/Gurkengewuerz/MinecraftModUpdater) is a utility tool to update and synchronize Minecraft mods for your userbase. It’s built using Wails2 and React with [antd](https://ant.design/) as frontend framework.
diff --git a/website/versioned_docs/version-v2.3.0/community/showcase/modalfilemanager.mdx b/website/versioned_docs/version-v2.3.0/community/showcase/modalfilemanager.mdx
deleted file mode 100644
index f8e2bcd66..000000000
--- a/website/versioned_docs/version-v2.3.0/community/showcase/modalfilemanager.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
-# Modal File Manager
-
-```mdx-code-block
-
-
-
-
-```
-
-[Modal File Manager](https://github.com/raguay/ModalFileManager) is a dual pane file manager using web technologies. My original design was based on NW.js and can be found [here](https://github.com/raguay/ModalFileManager-NWjs). This version uses the same Svelte based frontend code (but it has be greatly modified since the departure from NW.js), but the backend is a [Wails 2](https://wails.io/) implementation. By using this implementation, I no longer use command line `rm`, `cp`, etc. commands. It is fully coded using Go and runs much faster than the previous versions.
-
-This file manager is designed around the same principle as Vim: a state controlled keyboard actions. The number of states isn't fixed, but very programmable. Therefore, an infinite number of keyboard configurations can be created and used. This is the main difference from other file managers.
diff --git a/website/versioned_docs/version-v2.3.0/community/showcase/mollywallet.mdx b/website/versioned_docs/version-v2.3.0/community/showcase/mollywallet.mdx
deleted file mode 100644
index 5d846d06d..000000000
--- a/website/versioned_docs/version-v2.3.0/community/showcase/mollywallet.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Molley Wallet
-
-```mdx-code-block
-
-
-
-
-```
-
-[Molly Wallet](https://github.com/grvlle/constellation_wallet/) the official $DAG wallet of the Constellation Network. It'll let users interact with the Hypergraph Network in various ways, not limited to producing $DAG transactions.
diff --git a/website/versioned_docs/version-v2.3.0/community/showcase/october.mdx b/website/versioned_docs/version-v2.3.0/community/showcase/october.mdx
deleted file mode 100644
index 66d634dc5..000000000
--- a/website/versioned_docs/version-v2.3.0/community/showcase/october.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
-# October
-
-```mdx-code-block
-
-
-
-
-```
-
-[October](https://october.utf9k.net) is a small Wails application that makes it really easy to extract highlights from [Kobo eReaders](https://en.wikipedia.org/wiki/Kobo_eReader) and then forward them to [Readwise](https://readwise.io).
-
-It has a relatively small scope with all platform versions weighing in under 10MB, and that's without enabling [UPX compression](https://upx.github.io/)!
-
-In contrast, the author's previous attempts with Electron quickly bloated to several hundred megabytes.
diff --git a/website/versioned_docs/version-v2.3.0/community/showcase/optimus.mdx b/website/versioned_docs/version-v2.3.0/community/showcase/optimus.mdx
deleted file mode 100644
index 4f87479d6..000000000
--- a/website/versioned_docs/version-v2.3.0/community/showcase/optimus.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Optimus
-
-```mdx-code-block
-
-
-
-
-```
-
-[Optimus](https://github.com/splode/optimus) is a desktop image optimization application. It supports conversion and compression between WebP, JPEG, and PNG image formats.
diff --git a/website/versioned_docs/version-v2.3.0/community/showcase/portfall.mdx b/website/versioned_docs/version-v2.3.0/community/showcase/portfall.mdx
deleted file mode 100644
index 03e740f4c..000000000
--- a/website/versioned_docs/version-v2.3.0/community/showcase/portfall.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Portfall
-
-```mdx-code-block
-
-
-
-
-```
-
-[Portfall](https://github.com/rekon-oss/portfall) - A desktop k8s port-forwarding portal for easy access to all your cluster UIs
diff --git a/website/versioned_docs/version-v2.3.0/community/showcase/restic-browser.mdx b/website/versioned_docs/version-v2.3.0/community/showcase/restic-browser.mdx
deleted file mode 100644
index 3646384ec..000000000
--- a/website/versioned_docs/version-v2.3.0/community/showcase/restic-browser.mdx
+++ /dev/null
@@ -1,12 +0,0 @@
-# Restic Browser
-
-```mdx-code-block
-
-
-
-
-```
-
-[Restic-Browser](https://github.com/emuell/restic-browser) - A simple, cross-platform [restic](https://github.com/restic/restic) backup GUI for browsing and restoring restic repositories.
diff --git a/website/versioned_docs/version-v2.3.0/community/showcase/riftshare.mdx b/website/versioned_docs/version-v2.3.0/community/showcase/riftshare.mdx
deleted file mode 100644
index 9928b4785..000000000
--- a/website/versioned_docs/version-v2.3.0/community/showcase/riftshare.mdx
+++ /dev/null
@@ -1,21 +0,0 @@
-# RiftShare
-
-```mdx-code-block
-
-
-
-
-```
-
-Easy, Secure, and Free file sharing for everyone. Learn more at [Riftshare.app](https://riftshare.app)
-
-## Features
-
-- Easy secure file sharing between computers both in the local network and through the internet
-- Supports sending files or directories securely through the [magic wormhole protocol](https://magic-wormhole.readthedocs.io/en/latest/)
-- Compatible with all other apps using magic wormhole (magic-wormhole or wormhole-william CLI, wormhole-gui, etc.)
-- Automatic zipping of multiple selected files to send at once
-- Full animations, progress bar, and cancellation support for sending and receiving
-- Native OS File Selection
-- Open files in one click once received
-- Auto Update - don't worry about having the latest release!
diff --git a/website/versioned_docs/version-v2.3.0/community/showcase/scriptbar.mdx b/website/versioned_docs/version-v2.3.0/community/showcase/scriptbar.mdx
deleted file mode 100644
index 2ccb2acb4..000000000
--- a/website/versioned_docs/version-v2.3.0/community/showcase/scriptbar.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# ScriptBar
-
-```mdx-code-block
-
-
-
-
-```
-
-[ScriptBar](https://GitHub.com/raguay/ScriptBarApp) is a program to show the output of the embedded [Node-Red](https://nodered.org) server in the [EmailIt](https://GitHub.com/raguay/EmailIt) application. It also displays the output of scripts on your system. ScriptBar doesn't put them in the menubar, but has them all in a convient window for easy viewing. You can have multiple tabs to have many different things show. You can also keep the links to your most visited web sites.
diff --git a/website/versioned_docs/version-v2.3.0/community/showcase/surge.mdx b/website/versioned_docs/version-v2.3.0/community/showcase/surge.mdx
deleted file mode 100644
index c3b3fb4c0..000000000
--- a/website/versioned_docs/version-v2.3.0/community/showcase/surge.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Surge
-
-```mdx-code-block
-
-
-
-
-```
-
-[Surge](https://getsurge.io/) is a p2p filesharing app designed to utilize blockchain technologies to enable 100% anonymous file transfers. Surge is end-to-end encrypted, decentralized and open source.
diff --git a/website/versioned_docs/version-v2.3.0/community/showcase/wally.mdx b/website/versioned_docs/version-v2.3.0/community/showcase/wally.mdx
deleted file mode 100644
index 7408aa585..000000000
--- a/website/versioned_docs/version-v2.3.0/community/showcase/wally.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Wally
-
-```mdx-code-block
-
-
-
-
-```
-
-[Wally](https://ergodox-ez.com/pages/wally) is the official firmware flasher for [Ergodox](https://ergodox-ez.com/) keyboards. It looks great and is a fantastic example of what you can achieve with Wails: the ability to combine the power of Go and the rich graphical tools of the web development world.
diff --git a/website/versioned_docs/version-v2.3.0/community/showcase/wombat.mdx b/website/versioned_docs/version-v2.3.0/community/showcase/wombat.mdx
deleted file mode 100644
index f100c55e2..000000000
--- a/website/versioned_docs/version-v2.3.0/community/showcase/wombat.mdx
+++ /dev/null
@@ -1,10 +0,0 @@
-# Wombat
-
-```mdx-code-block
-
-```
-
-[Ytd](https://github.com/marcio199226/ytd/tree/v2-wails) is an app for downloading tracks from youtube, creating offline playlists and share them with your friends, your friends will be able to playback your playlists or download them for offline listening, has an built-in player.
diff --git a/website/versioned_docs/version-v2.3.0/gettingstarted/_category_.json b/website/versioned_docs/version-v2.3.0/gettingstarted/_category_.json
deleted file mode 100644
index 597b920df..000000000
--- a/website/versioned_docs/version-v2.3.0/gettingstarted/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Getting Started",
- "position": 10
-}
diff --git a/website/versioned_docs/version-v2.3.0/guides/_category_.json b/website/versioned_docs/version-v2.3.0/guides/_category_.json
deleted file mode 100644
index 5935dad93..000000000
--- a/website/versioned_docs/version-v2.3.0/guides/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Guides",
- "position": 50
-}
diff --git a/website/versioned_docs/version-v2.3.0/guides/routing.mdx b/website/versioned_docs/version-v2.3.0/guides/routing.mdx
deleted file mode 100644
index c35cc1c8a..000000000
--- a/website/versioned_docs/version-v2.3.0/guides/routing.mdx
+++ /dev/null
@@ -1,47 +0,0 @@
-# Routing
-
-Routing is a popular way to switch views in an application. This page offers some guidance around how to do that.
-
-## Vue
-
-The recommended approach for routing in Vue is [Hash Mode](https://next.router.vuejs.org/guide/essentials/history-mode.html#hash-mode):
-
-```js
-import { createRouter, createWebHashHistory } from "vue-router";
-
-const router = createRouter({
- history: createWebHashHistory(),
- routes: [
- //...
- ],
-});
-```
-
-## Angular
-
-The recommended approach for routing in Angular is [HashLocationStrategy](https://codecraft.tv/courses/angular/routing/routing-strategies#_hashlocationstrategy):
-
-```ts
-RouterModule.forRoot(routes, { useHash: true });
-```
-
-## React
-
-The recommended approach for routing in React is [HashRouter](https://reactrouter.com/docs/en/v6/routers/hash-router):
-
-```jsx
-import { HashRouter } from "react-router-dom";
-
-ReactDOM.render(
-
- {/* The rest of your app goes here */}
-
- } exact />
- } />
- } />
- {/* more... */}
-
- ,
- root
-);
-```
diff --git a/website/versioned_docs/version-v2.3.0/reference/_category_.json b/website/versioned_docs/version-v2.3.0/reference/_category_.json
deleted file mode 100644
index ebb337b83..000000000
--- a/website/versioned_docs/version-v2.3.0/reference/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Reference",
- "position": 40
-}
diff --git a/website/versioned_docs/version-v2.3.0/reference/runtime/_category_.json b/website/versioned_docs/version-v2.3.0/reference/runtime/_category_.json
deleted file mode 100644
index ac6d55488..000000000
--- a/website/versioned_docs/version-v2.3.0/reference/runtime/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Runtime",
- "position": 1
-}
diff --git a/website/versioned_docs/version-v2.3.0/tutorials/_category_.json b/website/versioned_docs/version-v2.3.0/tutorials/_category_.json
deleted file mode 100644
index dfac1d175..000000000
--- a/website/versioned_docs/version-v2.3.0/tutorials/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Tutorials",
- "position": 70
-}
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/appendix/_category_.json b/website/versioned_docs/version-v2.4.0/appendix/_category_.json
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/appendix/_category_.json
rename to website/versioned_docs/version-v2.4.0/appendix/_category_.json
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/community/_category_.json b/website/versioned_docs/version-v2.4.0/community/_category_.json
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.0.0/community/_category_.json
rename to website/versioned_docs/version-v2.4.0/community/_category_.json
diff --git a/website/versioned_docs/version-v2.3.0/community/links.mdx b/website/versioned_docs/version-v2.4.0/community/links.mdx
similarity index 83%
rename from website/versioned_docs/version-v2.3.0/community/links.mdx
rename to website/versioned_docs/version-v2.4.0/community/links.mdx
index 23a4b8cf6..fe8b51dd0 100644
--- a/website/versioned_docs/version-v2.3.0/community/links.mdx
+++ b/website/versioned_docs/version-v2.4.0/community/links.mdx
@@ -13,8 +13,7 @@ The [definitive list](https://github.com/wailsapp/awesome-wails) of links relate
## Support Channels
-- [Gophers Slack Channel](https://gophers.slack.com/messages/CJ4P9F7MZ/)
-- [Gophers Slack Channel Invite](https://invite.slack.golangbridge.org/)
+- [Wails Discord Server](https://discord.gg/JDdSxwjhGf)
- [Github Issues](https://github.com/wailsapp/wails/issues)
- [v2 Beta Discussion Board](https://github.com/wailsapp/wails/discussions/828)
@@ -24,4 +23,5 @@ The [definitive list](https://github.com/wailsapp/awesome-wails) of links relate
- [Wails Chinese Community QQ Group](https://qm.qq.com/cgi-bin/qm/qr?k=PmIURne5hFGNd7QWzW5qd6FV-INEjNJv&jump_from=webapi) - Group number: 1067173054
## Other Tutorials and Articles
+
- [Building of Bulletin Board](https://blog.customct.com/building-bulletin-board)
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/_category_.json b/website/versioned_docs/version-v2.4.0/community/showcase/_category_.json
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/community/showcase/_category_.json
rename to website/versioned_docs/version-v2.4.0/community/showcase/_category_.json
diff --git a/website/versioned_docs/version-v2.4.0/community/showcase/bulletinboard.mdx b/website/versioned_docs/version-v2.4.0/community/showcase/bulletinboard.mdx
new file mode 100644
index 000000000..37be75135
--- /dev/null
+++ b/website/versioned_docs/version-v2.4.0/community/showcase/bulletinboard.mdx
@@ -0,0 +1,10 @@
+# BulletinBoard
+
+```mdx-code-block
+
+
+
+
+```
+
+The [BulletinBoard](https://github.com/raguay/BulletinBoard) application is a versital message board for static messages or dialogs to get information from the user for a script. It has a TUI for creating new dialogs that can latter be used to get information from the user. It's design is to stay running on your system and show the information as needed and then hide away. I have a process for watching a file on my system and sending the contents to BulletinBoard when changed. It works great with my workflows. There is also an [Alfred workflow](https://github.com/raguay/MyAlfred/blob/master/Alfred%205/EmailIt.alfredworkflow) for sending information to the program. The workflow is also for working with [EmailIt](https://github.com/raguay/EmailIt).
diff --git a/website/versioned_docs/version-v2.4.0/community/showcase/emailit.mdx b/website/versioned_docs/version-v2.4.0/community/showcase/emailit.mdx
new file mode 100644
index 000000000..c1817b70f
--- /dev/null
+++ b/website/versioned_docs/version-v2.4.0/community/showcase/emailit.mdx
@@ -0,0 +1,10 @@
+# EmailIt
+
+```mdx-code-block
+
+
+
+
+```
+
+[EmailIt](https://github.com/raguay/EmailIt/) is a Wails 2 program that is a markdown based email sender only with nine notepads, scripts to manipulate the text, and templates. It also has a scripts terminal to run scripts in EmailIt on files in your system. The scripts and templates can be used from the commandline itself or with the Alfred, Keyboard Maestro, Dropzone, or PopClip extensions. It also supports scripts and themes downloaded form GitHub. Documentation is not complete, but the programs works. It’s built using Wails2 and Svelte, and the download is a universal macOS application.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/encrypteasy.mdx b/website/versioned_docs/version-v2.4.0/community/showcase/encrypteasy.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/encrypteasy.mdx
rename to website/versioned_docs/version-v2.4.0/community/showcase/encrypteasy.mdx
diff --git a/website/versioned_docs/version-v2.3.0/community/showcase/filehound.mdx b/website/versioned_docs/version-v2.4.0/community/showcase/filehound.mdx
similarity index 100%
rename from website/versioned_docs/version-v2.3.0/community/showcase/filehound.mdx
rename to website/versioned_docs/version-v2.4.0/community/showcase/filehound.mdx
diff --git a/website/versioned_docs/version-v2.4.0/community/showcase/hiposter.mdx b/website/versioned_docs/version-v2.4.0/community/showcase/hiposter.mdx
new file mode 100644
index 000000000..c0f9052c3
--- /dev/null
+++ b/website/versioned_docs/version-v2.4.0/community/showcase/hiposter.mdx
@@ -0,0 +1,10 @@
+# hiposter
+
+```mdx-code-block
+
+
+
+
+```
+
+[hiposter](https://github.com/obity/hiposter) is a simple and efficient http API testing client tool. Based on Wails, Go and sveltejs.
\ No newline at end of file
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/minecraftupdater.mdx b/website/versioned_docs/version-v2.4.0/community/showcase/minecraftupdater.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/minecraftupdater.mdx
rename to website/versioned_docs/version-v2.4.0/community/showcase/minecraftupdater.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/modalfilemanager.mdx b/website/versioned_docs/version-v2.4.0/community/showcase/modalfilemanager.mdx
similarity index 74%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/modalfilemanager.mdx
rename to website/versioned_docs/version-v2.4.0/community/showcase/modalfilemanager.mdx
index f8e2bcd66..bcd212396 100644
--- a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/modalfilemanager.mdx
+++ b/website/versioned_docs/version-v2.4.0/community/showcase/modalfilemanager.mdx
@@ -9,6 +9,6 @@
```
-[Modal File Manager](https://github.com/raguay/ModalFileManager) is a dual pane file manager using web technologies. My original design was based on NW.js and can be found [here](https://github.com/raguay/ModalFileManager-NWjs). This version uses the same Svelte based frontend code (but it has be greatly modified since the departure from NW.js), but the backend is a [Wails 2](https://wails.io/) implementation. By using this implementation, I no longer use command line `rm`, `cp`, etc. commands. It is fully coded using Go and runs much faster than the previous versions.
+[Modal File Manager](https://github.com/raguay/ModalFileManager) is a dual pane file manager using web technologies. My original design was based on NW.js and can be found [here](https://github.com/raguay/ModalFileManager-NWjs). This version uses the same Svelte based frontend code (but it has be greatly modified since the departure from NW.js), but the backend is a [Wails 2](https://wails.io/) implementation. By using this implementation, I no longer use command line `rm`, `cp`, etc. commands, but a git install has to be on the system to download themes and extensions. It is fully coded using Go and runs much faster than the previous versions.
-This file manager is designed around the same principle as Vim: a state controlled keyboard actions. The number of states isn't fixed, but very programmable. Therefore, an infinite number of keyboard configurations can be created and used. This is the main difference from other file managers.
+This file manager is designed around the same principle as Vim: a state controlled keyboard actions. The number of states isn't fixed, but very programmable. Therefore, an infinite number of keyboard configurations can be created and used. This is the main difference from other file managers. There are themes and extensions available to download from GitHub.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/mollywallet.mdx b/website/versioned_docs/version-v2.4.0/community/showcase/mollywallet.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/mollywallet.mdx
rename to website/versioned_docs/version-v2.4.0/community/showcase/mollywallet.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/october.mdx b/website/versioned_docs/version-v2.4.0/community/showcase/october.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/october.mdx
rename to website/versioned_docs/version-v2.4.0/community/showcase/october.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/optimus.mdx b/website/versioned_docs/version-v2.4.0/community/showcase/optimus.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/optimus.mdx
rename to website/versioned_docs/version-v2.4.0/community/showcase/optimus.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/portfall.mdx b/website/versioned_docs/version-v2.4.0/community/showcase/portfall.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/portfall.mdx
rename to website/versioned_docs/version-v2.4.0/community/showcase/portfall.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/restic-browser.mdx b/website/versioned_docs/version-v2.4.0/community/showcase/restic-browser.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/restic-browser.mdx
rename to website/versioned_docs/version-v2.4.0/community/showcase/restic-browser.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/riftshare.mdx b/website/versioned_docs/version-v2.4.0/community/showcase/riftshare.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/riftshare.mdx
rename to website/versioned_docs/version-v2.4.0/community/showcase/riftshare.mdx
diff --git a/website/versioned_docs/version-v2.4.0/community/showcase/scriptbar.mdx b/website/versioned_docs/version-v2.4.0/community/showcase/scriptbar.mdx
new file mode 100644
index 000000000..3e41eb32a
--- /dev/null
+++ b/website/versioned_docs/version-v2.4.0/community/showcase/scriptbar.mdx
@@ -0,0 +1,10 @@
+# ScriptBar
+
+```mdx-code-block
+
+
+
+
+```
+
+[ScriptBar](https://GitHub.com/raguay/ScriptBarApp) is a program to show the output of scripts or [Node-Red](https://nodered.org) server. It runs scripts defined in EmailIt program and shows the output. Scripts from xBar or TextBar can be used, but currently on the TextBar scripts work well. It also displays the output of scripts on your system. ScriptBar doesn't put them in the menubar, but has them all in a convient window for easy viewing. You can have multiple tabs to have many different things show. You can also keep the links to your most visited web sites.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/surge.mdx b/website/versioned_docs/version-v2.4.0/community/showcase/surge.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/surge.mdx
rename to website/versioned_docs/version-v2.4.0/community/showcase/surge.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/wally.mdx b/website/versioned_docs/version-v2.4.0/community/showcase/wally.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/wally.mdx
rename to website/versioned_docs/version-v2.4.0/community/showcase/wally.mdx
diff --git a/website/versioned_docs/version-v2.4.0/community/showcase/warmine.mdx b/website/versioned_docs/version-v2.4.0/community/showcase/warmine.mdx
new file mode 100644
index 000000000..46b10b5b1
--- /dev/null
+++ b/website/versioned_docs/version-v2.4.0/community/showcase/warmine.mdx
@@ -0,0 +1,19 @@
+# Minecraft launcher for WarMine
+
+```mdx-code-block
+
+
+
+
+
+```
+
+[Minecraft launcher for WarMine](https://warmine.ru/) is a Wails application, that allows you to easily join modded game servers and manage your game accounts.
+
+The Launcher downloads the game files, checks their integrity and launches the game with a wide range of customization options for the launch arguments from the backend.
+
+Frontend is written in Svelte, whole launcher fits in 9MB and supports Windows 7-11.
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/wombat.mdx b/website/versioned_docs/version-v2.4.0/community/showcase/wombat.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.2.0/community/showcase/wombat.mdx
rename to website/versioned_docs/version-v2.4.0/community/showcase/wombat.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/ytd.mdx b/website/versioned_docs/version-v2.4.0/community/showcase/ytd.mdx
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.3.0/community/showcase/ytd.mdx
rename to website/versioned_docs/version-v2.4.0/community/showcase/ytd.mdx
diff --git a/website/versioned_docs/version-v2.3.0/community/templates.mdx b/website/versioned_docs/version-v2.4.0/community/templates.mdx
similarity index 100%
rename from website/versioned_docs/version-v2.3.0/community/templates.mdx
rename to website/versioned_docs/version-v2.4.0/community/templates.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/gettingstarted/_category_.json b/website/versioned_docs/version-v2.4.0/gettingstarted/_category_.json
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/gettingstarted/_category_.json
rename to website/versioned_docs/version-v2.4.0/gettingstarted/_category_.json
diff --git a/website/versioned_docs/version-v2.3.0/gettingstarted/building.mdx b/website/versioned_docs/version-v2.4.0/gettingstarted/building.mdx
similarity index 100%
rename from website/versioned_docs/version-v2.3.0/gettingstarted/building.mdx
rename to website/versioned_docs/version-v2.4.0/gettingstarted/building.mdx
diff --git a/website/versioned_docs/version-v2.3.0/gettingstarted/development.mdx b/website/versioned_docs/version-v2.4.0/gettingstarted/development.mdx
similarity index 100%
rename from website/versioned_docs/version-v2.3.0/gettingstarted/development.mdx
rename to website/versioned_docs/version-v2.4.0/gettingstarted/development.mdx
diff --git a/website/versioned_docs/version-v2.3.0/gettingstarted/firstproject.mdx b/website/versioned_docs/version-v2.4.0/gettingstarted/firstproject.mdx
similarity index 100%
rename from website/versioned_docs/version-v2.3.0/gettingstarted/firstproject.mdx
rename to website/versioned_docs/version-v2.4.0/gettingstarted/firstproject.mdx
diff --git a/website/versioned_docs/version-v2.3.0/gettingstarted/installation.mdx b/website/versioned_docs/version-v2.4.0/gettingstarted/installation.mdx
similarity index 98%
rename from website/versioned_docs/version-v2.3.0/gettingstarted/installation.mdx
rename to website/versioned_docs/version-v2.4.0/gettingstarted/installation.mdx
index 0e4bd0a50..331ca5062 100644
--- a/website/versioned_docs/version-v2.3.0/gettingstarted/installation.mdx
+++ b/website/versioned_docs/version-v2.4.0/gettingstarted/installation.mdx
@@ -57,7 +57,7 @@ import TabItem from "@theme/TabItem";
Wails requires that the WebView2 runtime is installed. Some Windows installations will already have this installed. You can check using the wails doctor command.
- Linux required the standard gcc build tools plus libgtk3 and libwebkit. Rather than list a ton of commands for different distros, Wails can try to determine what the installation commands are for your specific distribution. Run wails doctor after installation to be shown how to install the dependencies. If your distro/package manager is not supported, please consult the Add Linux Distro guide.
+ Linux requires the standard gcc build tools plus libgtk3 and libwebkit. Rather than list a ton of commands for different distros, Wails can try to determine what the installation commands are for your specific distribution. Run wails doctor after installation to be shown how to install the dependencies. If your distro/package manager is not supported, please consult the Add Linux Distro guide.
```
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/_category_.json b/website/versioned_docs/version-v2.4.0/guides/_category_.json
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/guides/_category_.json
rename to website/versioned_docs/version-v2.4.0/guides/_category_.json
diff --git a/website/versioned_docs/version-v2.3.0/guides/angular.mdx b/website/versioned_docs/version-v2.4.0/guides/angular.mdx
similarity index 100%
rename from website/versioned_docs/version-v2.3.0/guides/angular.mdx
rename to website/versioned_docs/version-v2.4.0/guides/angular.mdx
diff --git a/website/versioned_docs/version-v2.3.0/guides/application-development.mdx b/website/versioned_docs/version-v2.4.0/guides/application-development.mdx
similarity index 100%
rename from website/versioned_docs/version-v2.3.0/guides/application-development.mdx
rename to website/versioned_docs/version-v2.4.0/guides/application-development.mdx
diff --git a/website/versioned_docs/version-v2.3.0/guides/dynamic-assets.mdx b/website/versioned_docs/version-v2.4.0/guides/dynamic-assets.mdx
similarity index 99%
rename from website/versioned_docs/version-v2.3.0/guides/dynamic-assets.mdx
rename to website/versioned_docs/version-v2.4.0/guides/dynamic-assets.mdx
index 806accf18..0516fb729 100644
--- a/website/versioned_docs/version-v2.3.0/guides/dynamic-assets.mdx
+++ b/website/versioned_docs/version-v2.4.0/guides/dynamic-assets.mdx
@@ -11,7 +11,7 @@ By installing a custom AssetsHandler, you can serve your own assets using a cust
In our example project, we will create a simple assets handler which will load files off disk:
-```go title=main.go {16-35,49}
+```go title=main.go {17-36,49}
package main
import (
diff --git a/website/versioned_docs/version-v2.3.0/guides/frameless.mdx b/website/versioned_docs/version-v2.4.0/guides/frameless.mdx
similarity index 100%
rename from website/versioned_docs/version-v2.3.0/guides/frameless.mdx
rename to website/versioned_docs/version-v2.4.0/guides/frameless.mdx
diff --git a/website/versioned_docs/version-v2.3.0/guides/frontend.mdx b/website/versioned_docs/version-v2.4.0/guides/frontend.mdx
similarity index 100%
rename from website/versioned_docs/version-v2.3.0/guides/frontend.mdx
rename to website/versioned_docs/version-v2.4.0/guides/frontend.mdx
diff --git a/website/versioned_docs/version-v2.3.0/guides/ides.mdx b/website/versioned_docs/version-v2.4.0/guides/ides.mdx
similarity index 100%
rename from website/versioned_docs/version-v2.3.0/guides/ides.mdx
rename to website/versioned_docs/version-v2.4.0/guides/ides.mdx
diff --git a/website/versioned_docs/version-v2.3.0/guides/linux-distro-support.mdx b/website/versioned_docs/version-v2.4.0/guides/linux-distro-support.mdx
similarity index 100%
rename from website/versioned_docs/version-v2.3.0/guides/linux-distro-support.mdx
rename to website/versioned_docs/version-v2.4.0/guides/linux-distro-support.mdx
diff --git a/website/versioned_docs/version-v2.3.0/guides/linux.mdx b/website/versioned_docs/version-v2.4.0/guides/linux.mdx
similarity index 100%
rename from website/versioned_docs/version-v2.3.0/guides/linux.mdx
rename to website/versioned_docs/version-v2.4.0/guides/linux.mdx
diff --git a/website/versioned_docs/version-v2.3.0/guides/local-development.mdx b/website/versioned_docs/version-v2.4.0/guides/local-development.mdx
similarity index 100%
rename from website/versioned_docs/version-v2.3.0/guides/local-development.mdx
rename to website/versioned_docs/version-v2.4.0/guides/local-development.mdx
diff --git a/website/versioned_docs/version-v2.3.0/guides/mac-appstore.mdx b/website/versioned_docs/version-v2.4.0/guides/mac-appstore.mdx
similarity index 81%
rename from website/versioned_docs/version-v2.3.0/guides/mac-appstore.mdx
rename to website/versioned_docs/version-v2.4.0/guides/mac-appstore.mdx
index 271464730..d2c3a9458 100644
--- a/website/versioned_docs/version-v2.3.0/guides/mac-appstore.mdx
+++ b/website/versioned_docs/version-v2.4.0/guides/mac-appstore.mdx
@@ -21,6 +21,12 @@ This page gives a brief overview of how to submit your Wails App to the Mac App
3. Populate your app with the correct screen shots, descriptions, etc. as required by Apple
4. Create a new version of your app
+#### Create Provisioning Profile
+1. Go to the [Apple Developer Profiles](https://developer.apple.com/account/resources/profiles/list) page
+2. Add a new provisioning profile for Mac App Store Distribution
+3. Set the Profile Type as Mac and select the App ID for the application created above
+4. Select the Mac App Distribution certificate
+5. Name the Provisioning Profile embedded and download the created profile.
## Mac App Store Process
@@ -30,7 +36,7 @@ Apps submitted to the Mac App Store must run under Apple's [App Sandbox](https:/
**Example Entitlements File**
-This is an example entitlements file from the [RiftShare](https://github.com/achhabra2/riftshare) app. For reference please put in the entitlements your app requires. Refer to [this site](https://developer.apple.com/documentation/bundleresources/entitlements) for more information.
+This is an example entitlements file from the [RiftShare](https://github.com/achhabra2/riftshare) app. For reference please put in the entitlements your app requires. Refer to [this site](https://developer.apple.com/documentation/bundleresources/entitlements) for more information. You will need to replace the Team ID and Application Name with the ones you registered above.
```xml title="entitlements.plist"
@@ -47,10 +53,17 @@ This is an example entitlements file from the [RiftShare](https://github.com/ach
com.apple.security.files.downloads.read-write
+ com.apple.application-identifier
+ TEAM_ID.APP_NAME
+ com.apple.developer.team-identifier
+ TEAM_ID
```
+**Add the Embedded Provisioning Profile**
+The Provisioning Profile created above needs to be added to the root of the applicaton. It needs to be named embedded.provisionprofile.
+
#### Build and Sign the App Package
The following is an example script for building and signing your app for Mac App Store submission. It assumes you are running the script from your root project directory.
@@ -66,6 +79,8 @@ APP_NAME="YourApp"
wails build -platform darwin/universal -clean
+cp ./embedded.provisionprofile "./build/bin/$APP_NAME.app/Contents"
+
codesign --timestamp --options=runtime -s "$APP_CERTIFICATE" -v --entitlements ./build/darwin/entitlements.plist ./build/bin/$APP_NAME.app
productbuild --sign "$PKG_CERTIFICATE" --component ./build/bin/$APP_NAME.app /Applications ./$APP_NAME.pkg
@@ -80,4 +95,4 @@ You will need to upload the generated package file and associate it to your Appl
3. Click the + sign and select the `APP_NAME.pkg` file that you generated in the previous step. Upload it
4. Go back to the [App Store Connect](https://appstoreconnect.apple.com/apps) site and navigate back into your app submission. Select the version that you are ready to make available on the App Store. Under `Build` select the package that you uploaded via Transporter.
-That's it! You can now use the site to submit your App for review. After a few business days if all goes well you should see your App live on the Mac App Store.
\ No newline at end of file
+That's it! You can now use the site to submit your App for review. After a few business days if all goes well you should see your App live on the Mac App Store.
diff --git a/website/versioned_docs/version-v2.3.0/guides/manual-builds.mdx b/website/versioned_docs/version-v2.4.0/guides/manual-builds.mdx
similarity index 100%
rename from website/versioned_docs/version-v2.3.0/guides/manual-builds.mdx
rename to website/versioned_docs/version-v2.4.0/guides/manual-builds.mdx
diff --git a/website/versioned_docs/version-v2.3.0/guides/migrating.mdx b/website/versioned_docs/version-v2.4.0/guides/migrating.mdx
similarity index 100%
rename from website/versioned_docs/version-v2.3.0/guides/migrating.mdx
rename to website/versioned_docs/version-v2.4.0/guides/migrating.mdx
diff --git a/website/versioned_docs/version-v2.3.0/guides/mouse-buttons.mdx b/website/versioned_docs/version-v2.4.0/guides/mouse-buttons.mdx
similarity index 100%
rename from website/versioned_docs/version-v2.3.0/guides/mouse-buttons.mdx
rename to website/versioned_docs/version-v2.4.0/guides/mouse-buttons.mdx
diff --git a/website/versioned_docs/version-v2.3.0/guides/obfuscated.mdx b/website/versioned_docs/version-v2.4.0/guides/obfuscated.mdx
similarity index 100%
rename from website/versioned_docs/version-v2.3.0/guides/obfuscated.mdx
rename to website/versioned_docs/version-v2.4.0/guides/obfuscated.mdx
diff --git a/website/versioned_docs/version-v2.3.0/guides/overscroll.mdx b/website/versioned_docs/version-v2.4.0/guides/overscroll.mdx
similarity index 100%
rename from website/versioned_docs/version-v2.3.0/guides/overscroll.mdx
rename to website/versioned_docs/version-v2.4.0/guides/overscroll.mdx
diff --git a/website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/routing.mdx b/website/versioned_docs/version-v2.4.0/guides/routing.mdx
similarity index 100%
rename from website/i18n/ko/docusaurus-plugin-content-docs/version-v2.3.0/guides/routing.mdx
rename to website/versioned_docs/version-v2.4.0/guides/routing.mdx
diff --git a/website/versioned_docs/version-v2.3.0/guides/signing.mdx b/website/versioned_docs/version-v2.4.0/guides/signing.mdx
similarity index 100%
rename from website/versioned_docs/version-v2.3.0/guides/signing.mdx
rename to website/versioned_docs/version-v2.4.0/guides/signing.mdx
diff --git a/website/versioned_docs/version-v2.3.0/guides/templates.mdx b/website/versioned_docs/version-v2.4.0/guides/templates.mdx
similarity index 100%
rename from website/versioned_docs/version-v2.3.0/guides/templates.mdx
rename to website/versioned_docs/version-v2.4.0/guides/templates.mdx
diff --git a/website/versioned_docs/version-v2.3.0/guides/troubleshooting.mdx b/website/versioned_docs/version-v2.4.0/guides/troubleshooting.mdx
similarity index 99%
rename from website/versioned_docs/version-v2.3.0/guides/troubleshooting.mdx
rename to website/versioned_docs/version-v2.4.0/guides/troubleshooting.mdx
index 37a6d3e79..9a68610c3 100644
--- a/website/versioned_docs/version-v2.3.0/guides/troubleshooting.mdx
+++ b/website/versioned_docs/version-v2.4.0/guides/troubleshooting.mdx
@@ -173,7 +173,7 @@ Sources: https://github.com/wailsapp/wails/issues/1806 and https://github.com/wa
It's preferable to add `frontend/node_modules` and `frontend/package-lock.json` to your `.gitignore`. Otherwise when opening your repository on another machine
that may have different versions of Node installed, you may not be able to run your application.
-If this does happen, simply delete `frontend/node_modules` and `frontend/package-lock.json` and run your `wails build` or `wails dev` command again.
+If this does happen, simply delete `frontend/node_modules` and `frontend/package-lock.json` and run your `wails build` or `wails dev` command again.
## Build process stuck on "Generating bindings"
diff --git a/website/versioned_docs/version-v2.3.0/guides/vscode.mdx b/website/versioned_docs/version-v2.4.0/guides/vscode.mdx
similarity index 100%
rename from website/versioned_docs/version-v2.3.0/guides/vscode.mdx
rename to website/versioned_docs/version-v2.4.0/guides/vscode.mdx
diff --git a/website/versioned_docs/version-v2.3.0/guides/windows-installer.mdx b/website/versioned_docs/version-v2.4.0/guides/windows-installer.mdx
similarity index 100%
rename from website/versioned_docs/version-v2.3.0/guides/windows-installer.mdx
rename to website/versioned_docs/version-v2.4.0/guides/windows-installer.mdx
diff --git a/website/versioned_docs/version-v2.3.0/guides/windows.mdx b/website/versioned_docs/version-v2.4.0/guides/windows.mdx
similarity index 100%
rename from website/versioned_docs/version-v2.3.0/guides/windows.mdx
rename to website/versioned_docs/version-v2.4.0/guides/windows.mdx
diff --git a/website/versioned_docs/version-v2.3.0/howdoesitwork.mdx b/website/versioned_docs/version-v2.4.0/howdoesitwork.mdx
similarity index 99%
rename from website/versioned_docs/version-v2.3.0/howdoesitwork.mdx
rename to website/versioned_docs/version-v2.4.0/howdoesitwork.mdx
index 2db56daa5..e9f2c6e3d 100644
--- a/website/versioned_docs/version-v2.3.0/howdoesitwork.mdx
+++ b/website/versioned_docs/version-v2.4.0/howdoesitwork.mdx
@@ -141,7 +141,7 @@ Wails requires that you pass in an _instance_ of the struct for it to bind it co
In this example, we create a new `App` instance and then add this instance to the `Bind` option in `wails.Run`:
-```go {16,24} title="main.go"
+```go {17,27} title="main.go"
package main
import (
@@ -188,7 +188,7 @@ func (a *App) Greet(name string) string {
You may bind as many structs as you like. Just make sure you create an instance of it and pass it in `Bind`:
-```go {8-10}
+```go {10-12}
//...
err := wails.Run(&options.App{
Title: "Basic Demo",
@@ -276,7 +276,7 @@ it will be returned to your frontend as a JavaScript class.
:::info Note
-Struct fields *must* have a valid `json` tag to be included in the generated TypeScript.
+Struct fields _must_ have a valid `json` tag to be included in the generated TypeScript.
Anonymous nested structs are not supported at this time.
diff --git a/website/versioned_docs/version-v2.3.0/introduction.mdx b/website/versioned_docs/version-v2.4.0/introduction.mdx
similarity index 100%
rename from website/versioned_docs/version-v2.3.0/introduction.mdx
rename to website/versioned_docs/version-v2.4.0/introduction.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/reference/_category_.json b/website/versioned_docs/version-v2.4.0/reference/_category_.json
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/reference/_category_.json
rename to website/versioned_docs/version-v2.4.0/reference/_category_.json
diff --git a/website/versioned_docs/version-v2.3.0/reference/cli.mdx b/website/versioned_docs/version-v2.4.0/reference/cli.mdx
similarity index 99%
rename from website/versioned_docs/version-v2.3.0/reference/cli.mdx
rename to website/versioned_docs/version-v2.4.0/reference/cli.mdx
index 4a73292ae..c76baaadd 100644
--- a/website/versioned_docs/version-v2.3.0/reference/cli.mdx
+++ b/website/versioned_docs/version-v2.4.0/reference/cli.mdx
@@ -85,8 +85,10 @@ Example:
`wails build -clean -o myproject.exe`
-:::Info
+:::info
+
On Mac, the application will be bundled with `Info.plist`, not `Info.dev.plist`.
+
:::
:::info UPX on Apple Silicon
diff --git a/website/versioned_docs/version-v2.3.0/reference/menus.mdx b/website/versioned_docs/version-v2.4.0/reference/menus.mdx
similarity index 100%
rename from website/versioned_docs/version-v2.3.0/reference/menus.mdx
rename to website/versioned_docs/version-v2.4.0/reference/menus.mdx
diff --git a/website/versioned_docs/version-v2.3.0/reference/options.mdx b/website/versioned_docs/version-v2.4.0/reference/options.mdx
similarity index 95%
rename from website/versioned_docs/version-v2.3.0/reference/options.mdx
rename to website/versioned_docs/version-v2.4.0/reference/options.mdx
index 1e7af4c19..878512d25 100644
--- a/website/versioned_docs/version-v2.3.0/reference/options.mdx
+++ b/website/versioned_docs/version-v2.4.0/reference/options.mdx
@@ -51,6 +51,7 @@ func main() {
OnBeforeClose: app.beforeClose,
CSSDragProperty: "--wails-draggable",
CSSDragValue: "drag",
+ EnableFraudulentWebsiteDetection: false,
ZoomFactor: 1.0,
IsZoomControlEnabled: false,
Bind: []interface{}{
@@ -78,7 +79,8 @@ func main() {
// OnSuspend is called when Windows enters low power mode
OnSuspend func()
// OnResume is called when Windows resumes from low power mode
- OnResume func()
+ OnResume func(),
+ WebviewGpuDisabled: false,
},
Mac: &mac.Options{
TitleBar: &mac.TitleBar{
@@ -101,6 +103,7 @@ func main() {
Linux: &linux.Options{
Icon: icon,
WindowIsTranslucent: false,
+ WebviewGpuPolicy: linux.WebviewGpuPolicyAlways,
},
Debug: options.Debug{
OpenInspectorOnStartup: false,
@@ -413,6 +416,15 @@ Indicates what value the `CSSDragProperty` style should have to drag the window.
Name: CSSDragValue
Type: `string`
+### EnableFraudulentWebsiteDetection
+
+EnableFraudulentWebsiteDetection enables scan services for fraudulent content, such as malware or phishing attempts.
+These services might send information from your app like URLs navigated to and possibly other content to cloud
+services of Apple and Microsoft.
+
+Name: EnableFraudulentWebsiteDetection
+Type: `bool`
+
### ZoomFactor
Name: ZoomFactor
@@ -628,6 +640,13 @@ If set, this function will be called when Windows resumes from low power mode (s
Name: OnResume
Type: `func()`
+#### WebviewGpuIsDisabled
+
+Setting this to `true` will disable GPU hardware acceleration for the webview.
+
+Name: WebviewGpuIsDisabled
+Type: `bool`
+
### Mac
This defines [Mac specific options](#mac).
@@ -824,6 +843,22 @@ Setting this to `true` will make the window background translucent. Some window
Name: WindowIsTranslucent
Type: `bool`
+#### WebviewGpuPolicy
+
+This option is used for determining the webview's hardware acceleration policy.
+
+Name: WebviewGpuPolicy
+Type: [`options.WebviewGpuPolicy`](#webviewgpupolicy-type)
+Default: `WebviewGpuPolicyAlways`
+
+##### WebviewGpuPolicy type
+
+| Value | Description |
+| -------------------------| ----------- |
+| WebviewGpuPolicyAlways | Hardware acceleration is always enabled|
+| WebviewGpuPolicyOnDemand | Hardware acceleration is enabled/disabled as request by web contents|
+| WebviewGpuPolicyNever | Hardware acceleration is always disabled |
+
### Debug
This defines [Debug specific options](#Debug) that apply to debug builds.
diff --git a/website/versioned_docs/version-v2.3.0/reference/project-config.mdx b/website/versioned_docs/version-v2.4.0/reference/project-config.mdx
similarity index 100%
rename from website/versioned_docs/version-v2.3.0/reference/project-config.mdx
rename to website/versioned_docs/version-v2.4.0/reference/project-config.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/reference/runtime/_category_.json b/website/versioned_docs/version-v2.4.0/reference/runtime/_category_.json
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/reference/runtime/_category_.json
rename to website/versioned_docs/version-v2.4.0/reference/runtime/_category_.json
diff --git a/website/versioned_docs/version-v2.3.0/reference/runtime/browser.mdx b/website/versioned_docs/version-v2.4.0/reference/runtime/browser.mdx
similarity index 100%
rename from website/versioned_docs/version-v2.3.0/reference/runtime/browser.mdx
rename to website/versioned_docs/version-v2.4.0/reference/runtime/browser.mdx
diff --git a/website/versioned_docs/version-v2.4.0/reference/runtime/clipboard.mdx b/website/versioned_docs/version-v2.4.0/reference/runtime/clipboard.mdx
new file mode 100644
index 000000000..306cfcb44
--- /dev/null
+++ b/website/versioned_docs/version-v2.4.0/reference/runtime/clipboard.mdx
@@ -0,0 +1,28 @@
+---
+sidebar_position: 8
+---
+
+# Clipboard
+
+This part of the runtime provides access to the operating system's clipboard.
+The current implementation only handles text.
+
+### ClipboardGetText
+
+This method reads the currently stored text from the clipboard.
+
+Go: `ClipboardGetText(ctx context.Context) (string, error)`
+Returns: a string (if the clipboard is empty an empty string will be returned) or an error.
+
+JS: `ClipboardGetText(): Promise`
+Returns: a promise with a string result (if the clipboard is empty an empty string will be returned).
+
+### ClipboardSetText
+
+This method writes a text to the clipboard.
+
+Go: `ClipboardSetText(ctx context.Context, text string) error`
+Returns: an error if there is any.
+
+JS: `ClipboardSetText(text: string): Promise`
+Returns: a promise with true result if the text was successfully set on the clipboard, false otherwise.
diff --git a/website/versioned_docs/version-v2.3.0/reference/runtime/dialog.mdx b/website/versioned_docs/version-v2.4.0/reference/runtime/dialog.mdx
similarity index 100%
rename from website/versioned_docs/version-v2.3.0/reference/runtime/dialog.mdx
rename to website/versioned_docs/version-v2.4.0/reference/runtime/dialog.mdx
diff --git a/website/versioned_docs/version-v2.3.0/reference/runtime/events.mdx b/website/versioned_docs/version-v2.4.0/reference/runtime/events.mdx
similarity index 96%
rename from website/versioned_docs/version-v2.3.0/reference/runtime/events.mdx
rename to website/versioned_docs/version-v2.4.0/reference/runtime/events.mdx
index 354a68f4c..138e03d73 100644
--- a/website/versioned_docs/version-v2.3.0/reference/runtime/events.mdx
+++ b/website/versioned_docs/version-v2.4.0/reference/runtime/events.mdx
@@ -44,4 +44,4 @@ JS: `EventsOnMultiple(eventName string, callback function(optionalData?: any), c
This method emits the given event. Optional data may be passed with the event. This will trigger any event listeners.
Go: `EventsEmit(ctx context.Context, eventName string, optionalData ...interface{})`
-JS: `EventsEmit(ctx context, optionalData function(optionalData?: any))`
+JS: `EventsEmit(eventName: string, ...optionalData: any)`
diff --git a/website/versioned_docs/version-v2.3.0/reference/runtime/intro.mdx b/website/versioned_docs/version-v2.4.0/reference/runtime/intro.mdx
similarity index 98%
rename from website/versioned_docs/version-v2.3.0/reference/runtime/intro.mdx
rename to website/versioned_docs/version-v2.4.0/reference/runtime/intro.mdx
index 13a50edfb..3c491ecf0 100644
--- a/website/versioned_docs/version-v2.3.0/reference/runtime/intro.mdx
+++ b/website/versioned_docs/version-v2.4.0/reference/runtime/intro.mdx
@@ -15,6 +15,7 @@ It has utility methods for:
- [Events](events.mdx)
- [Browser](browser.mdx)
- [Log](log.mdx)
+- [Clipboard](clipboard.mdx)
The Go Runtime is available through importing `github.com/wailsapp/wails/v2/pkg/runtime`. All methods in this package
take a context as the first parameter. This context should be obtained from the [OnStartup](../options.mdx#onstartup)
diff --git a/website/versioned_docs/version-v2.3.0/reference/runtime/log.mdx b/website/versioned_docs/version-v2.4.0/reference/runtime/log.mdx
similarity index 100%
rename from website/versioned_docs/version-v2.3.0/reference/runtime/log.mdx
rename to website/versioned_docs/version-v2.4.0/reference/runtime/log.mdx
diff --git a/website/versioned_docs/version-v2.3.0/reference/runtime/menu.mdx b/website/versioned_docs/version-v2.4.0/reference/runtime/menu.mdx
similarity index 100%
rename from website/versioned_docs/version-v2.3.0/reference/runtime/menu.mdx
rename to website/versioned_docs/version-v2.4.0/reference/runtime/menu.mdx
diff --git a/website/versioned_docs/version-v2.3.0/reference/runtime/window.mdx b/website/versioned_docs/version-v2.4.0/reference/runtime/window.mdx
similarity index 100%
rename from website/versioned_docs/version-v2.3.0/reference/runtime/window.mdx
rename to website/versioned_docs/version-v2.4.0/reference/runtime/window.mdx
diff --git a/website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/tutorials/_category_.json b/website/versioned_docs/version-v2.4.0/tutorials/_category_.json
similarity index 100%
rename from website/i18n/ja/docusaurus-plugin-content-docs/version-v2.1.0/tutorials/_category_.json
rename to website/versioned_docs/version-v2.4.0/tutorials/_category_.json
diff --git a/website/versioned_docs/version-v2.3.0/tutorials/dogsapi.mdx b/website/versioned_docs/version-v2.4.0/tutorials/dogsapi.mdx
similarity index 100%
rename from website/versioned_docs/version-v2.3.0/tutorials/dogsapi.mdx
rename to website/versioned_docs/version-v2.4.0/tutorials/dogsapi.mdx
diff --git a/website/versioned_docs/version-v2.3.0/tutorials/helloworld.mdx b/website/versioned_docs/version-v2.4.0/tutorials/helloworld.mdx
similarity index 100%
rename from website/versioned_docs/version-v2.3.0/tutorials/helloworld.mdx
rename to website/versioned_docs/version-v2.4.0/tutorials/helloworld.mdx
diff --git a/website/versioned_sidebars/version-v2.3.0-sidebars.json b/website/versioned_sidebars/version-v2.4.0-sidebars.json
similarity index 100%
rename from website/versioned_sidebars/version-v2.3.0-sidebars.json
rename to website/versioned_sidebars/version-v2.4.0-sidebars.json
diff --git a/website/versions.json b/website/versions.json
index 55f999c0a..a3ee08918 100644
--- a/website/versions.json
+++ b/website/versions.json
@@ -1 +1 @@
-["v2.3.1","v2.3.0"]
\ No newline at end of file
+["v2.4.0","v2.3.1"]
\ No newline at end of file