[v2] Docs update

website/.github/deploy-to-wails.top-mirror.yml

@@ -0,0 +1,34 @@
+name: Deploy mirror | 部署镜像
+
+on:
+  push:
+    branches: [ main ]
+  pull_request:
+    branches: [ main ]
+
+jobs:
+  build-and-deploy:
+    name: Automatic deployment | 自动部署
+    runs-on: ubuntu-latest
+    if: github.repository == 'misitebao/wails-docs'
+
+    steps:
+      - name: Checkout | 切换到部署分支
+        uses: actions/checkout@v2
+        with:
+          ref: "main"
+          submodules: true
+          fetch-depth: 0
+
+      - name: Build Site | 构建网站
+        run: |
+          npm install && npm run build
+
+      # - name: Deploy to Server | 部署到服务器
+      #   uses: hengkx/ssh-deploy@v1.0.1
+      #   with:
+      #     HOST: ${{ secrets.DEPLOY_HOST }}
+      #     USERNAME: ${{ secrets.DEPLOY_HOST_USER }}
+      #     PASSWORD: ${{ secrets.DEPLOY_HOST_PASSWORD }}
+      #     SOURCE: "build"
+      #     TARGET: "/www/wwwroot/beta.wails.top"

website/.gitignore

@@ -0,0 +1,20 @@
+# Dependencies
+/node_modules
+
+# Production
+/build
+
+# Generated files
+.docusaurus
+.cache-loader
+
+# Misc
+.DS_Store
+.env.local
+.env.development.local
+.env.test.local
+.env.production.local
+
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*

website/README.md

@@ -0,0 +1,36 @@
+# Website
+
+This website is built using [Docusaurus 2](https://docusaurus.io/), a modern static website generator.
+
+### Installation
+
+```
+$ yarn
+```
+
+### Local Development
+
+```
+$ yarn start
+```
+
+This command starts a local development server and opens up a browser window. Most changes are reflected live without
+having to restart the server.
+
+### Build
+
+```
+$ yarn build
+```
+
+This command generates static content into the `build` directory and can be served using any static contents hosting
+service.
+
+### Deployment
+
+```
+$ GIT_USER=<Your GitHub username> USE_SSH=true yarn deploy
+```
+
+If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to
+the `gh-pages` branch.

website/babel.config.js

@@ -0,0 +1,3 @@
+module.exports = {
+    presets: [require.resolve('@docusaurus/core/lib/babel/preset')],
+};

website/blog/2021-09-27-v2-beta1-release-notes.mdx

@@ -0,0 +1,182 @@
+---
+slug: wails-v2-beta-for-windows
+title: Wails v2 Beta for Windows
+authors: [leaanthony]
+tags: [wails, v2]
+---
+
+
+<div class="text--center">
+    <img src="/img/wails.png" width="40%" style={{"box-shadow": "rgb(255 255 255 / 20%) 0px 4px 8px 0px, rgb(104 104 104) 0px 6px 20px 0px"}}/>
+</div>
+<br/>
+
+
+When I first announced Wails on Reddit, just over 2 years ago from a train in Sydney, I did not expect it to get much 
+attention. A few days later, a prolific tech vlogger released a tutorial video, gave it a positive review and from that 
+point on, interest in the project has skyrocketed.
+
+It was clear that people were excited about adding web frontends to their Go projects, and almost immediately pushed the 
+project beyond the proof of concept that I had created.
+At the time, Wails used the [webview](https://github.com/webview/webview) project to handle the frontend, and the only 
+option for Windows was the IE11 renderer. Many bug reports were rooted in this limitation: poor JavaScript/CSS support 
+and no dev tools to debug it. This was a frustrating development experience but there wasn't much that could have been 
+done to rectify it.
+
+For a long time, I'd firmly believed that Microsoft would eventually have to sort out their browser situation. 
+The world was moving on, frontend development was booming and IE wasn't cutting it. 
+When Microsoft announced the move to using Chromium as the basis for their new browser direction, I knew it was only a 
+matter of time until Wails could use it, and move the Windows developer experience to the next level.
+
+Today, I am pleased to announce: **Wails v2 Beta for Windows**! There's a huge amount to unpack in this release, so 
+grab a drink, take a seat and we'll begin...
+
+### No CGO Dependency!
+
+No, I'm not joking: *No* *CGO* *dependency* 🤯! The thing about Windows is that, unlike MacOS and Linux, it doesn't 
+come with a default compiler. In addition, CGO requires a mingw compiler and there's a ton of different installation
+options. Removing the CGO requirement has massively simplified setup, as well as making debugging an awful lot easier. 
+Whilst I have put a fair bit of effort in getting this working, the majority of the 
+credit should go to [John Chadwick](https://github.com/jchv) for not only starting a couple of projects to make this
+possible, but also being open to someone taking those projects and building on them. Credit also to 
+[Tad Vizbaras](https://github.com/tadvi) whose [winc](https://github.com/tadvi/winc) project started me down this path.
+
+### WebView2 Chromium Renderer
+
+<div class="text--center">
+    <img src="/img/devtools.png" width="75%" style={{"box-shadow": "rgb(255 255 255 / 20%) 0px 4px 8px 0px, rgb(104 104 104) 0px 6px 20px 0px"}}/>
+</div>
+<br/>
+
+Finally, Windows developers get a first class rendering engine for their applications! Gone are the days of contorting
+your frontend code to work on Windows. On top of that, you get a first-class developer tools experience!
+
+The WebView2 component does, however, have a requirement to have the `WebView2Loader.dll` sitting alongside the binary.
+This makes distribution just that little bit more painful than we gophers are used to. All solutions and libraries 
+(that I know of) that use WebView2 have this dependency. 
+
+However, I'm really excited to announce that Wails applications *have no such requirement*! Thanks to the wizardry of 
+[John Chadwick](https://github.com/jchv), we are able to bundle this dll inside the binary and get Windows to load it
+as if it were present on disk. 
+
+Gophers rejoice! The single binary dream lives on!
+
+### New Features
+
+<div class="text--center">
+    <img src="/img/wails-menus.png" width="60%" style={{"box-shadow": "rgb(255 255 255 / 20%) 0px 4px 8px 0px, rgb(104 104 104) 0px 6px 20px 0px"}}/>
+</div>
+<br/>
+
+There were a lot of requests for native menu support. Wails has finally got you covered. Application menus are now available
+and include support for most native menu features. This includes standard menu items, checkboxes, radio groups, submenus 
+and separators.
+
+There were a huge number of requests in v1 for the ability to have greater control of the window itself. 
+I'm happy to announce that there's new runtime APIs specifically for this. 
+It's feature-rich and supports multi-monitor configurations. There is also an improved dialogs API: Now, you can have modern, native 
+dialogs with rich configuration to cater for all your dialog needs.
+
+There is now the option to generate IDE configuration along with your project. This means that if you open your project
+in a supported IDE, it will already be configured for building and debugging your application. Currently VSCode is supported
+but we hope to support other IDEs such as Goland soon.
+
+<div class="text--center">
+    <img src="/img/vscode.png" width="100%" style={{"box-shadow": "rgb(255 255 255 / 20%) 0px 4px 8px 0px, rgb(104 104 104) 0px 6px 20px 0px"}}/>
+</div>
+<br/>
+
+### No requirement to bundle assets  
+
+A huge pain-point of v1 was the need to condense your entire application down to single JS & CSS files. I'm happy to 
+announce that for v2, there is no requirement to bundle assets, in any way, shape or form. Want to load a local image? Use an 
+`<img>` tag with a local src path. Want to use a cool font? Copy it in and add the path to it in your CSS. 
+
+> Wow, that sounds like a webserver...
+
+Yes, it works just like a webserver, except it isn't. 
+
+> So how do I include my assets?
+
+You just pass a single `embed.FS` that contains all your assets into your application configuration. 
+They don't even need to be in the top directory - Wails will just work it out for you. 
+
+### New Development Experience
+
+<div class="text--center">
+    <img src="/img/browser.png" width="60%" style={{"box-shadow": "rgb(255 255 255 / 20%) 0px 4px 8px 0px, rgb(104 104 104) 0px 6px 20px 0px"}}/>
+</div>
+<br/>
+
+
+Now that assets don't need to be bundled, it's enabled a whole new development experience. The new `wails dev`
+command will build and run your application, but instead of using the assets in the `embed.FS`, it loads them directly
+from disk.
+
+It also provides the additional features:
+
+  - Hot reload - Any changes to frontend assets will trigger and auto reload of the application frontend
+  - Auto rebuild - Any changes to your Go code will rebuild and relaunch your application
+
+In addition to this, a webserver will start on port 34115. This will serve your application to any browser that 
+connects to it. All connected web browsers will respond to system events like hot reload on asset change.
+
+In Go, we are used to dealing with structs in our applications. It's often useful to send structs to our frontend
+and use them as state in our application. In v1, this was a very manual process and a bit of a burden on the 
+developer. I'm happy to announce that in v2, any application run in dev mode will automatically generate Typescript
+models for all structs that are input or output parameters to bound methods. This enables seamless interchange of data
+models between the two worlds.
+
+In addition to this, another JS module is dynamically generated wrapping all your bound methods. This provides 
+JSDoc for your methods, providing code completion and hinting in your IDE. It's really cool when you get data models 
+auto-imported when hitting tab in an auto-generated module wrapping your Go code!
+
+### Remote Templates
+
+<div class="text--center">
+    <img src="/img/remote.png" width="60%" style={{"box-shadow": "rgb(255 255 255 / 20%) 0px 4px 8px 0px, rgb(104 104 104) 0px 6px 20px 0px"}}/>
+</div>
+<br/>
+
+Getting an application up and running quickly was always a key goal for the Wails project. When we launched, we tried
+to cover a lot of the modern frameworks at the time: react, vue and angular. The world of frontend development is very
+opinionated, fast moving and hard to keep on top of! As a result, we found our base templates getting out of date pretty 
+quickly and this caused a maintenance headache. It also meant that we didn't have cool modern templates for the latest
+and greatest tech stacks.
+
+With v2, I wanted to empower the community by giving you the ability to create and host templates yourselves, rather
+than rely on the Wails project. So now you can create projects using community supported templates! I hope this will 
+inspire developers to create a vibrant ecosystem of project templates. I'm really quite excited about what our developer 
+community can create!
+
+### In Conclusion
+
+Wails v2 represents a new foundation for the project. 
+The aim of this release is to get feedback on the new approach, and to iron out any bugs before a full release. 
+Your input would be most welcome. Please direct any feedback to the [v2 Beta](https://github.com/wailsapp/wails/discussions) 
+discussion board.
+
+There were many twists and turns, pivots and u-turns to get to this point. This was due partly to early technical decisions 
+that needed changing, and partly because some core problems we had spent time building workarounds for were fixed upstream: 
+Go’s embed feature is a good example. Fortunately, everything came together at the right time, and today we have the 
+very best solution that we can have. I believe the wait has been worth it - this would not have been possible even 2 
+months ago.
+
+I also need to give a huge thank you :pray: to the following people because without them, this release just wouldn't exist:
+
+- [Misitebao](https://github.com/misitebao) - An absolute workhorse on the Chinese translations and an incredible bug finder. 
+- [John Chadwick](https://github.com/jchv) - His amazing work on [go-webview2](https://github.com/jchv/go-webview2) and
+  [go-winloader](https://github.com/jchv/go-winloader) have made the Windows version we have today possible.
+- [Tad Vizbaras](https://github.com/tadvi) - Experimenting with his [winc](https://github.com/tadvi/winc) project was the first step down the path to a pure Go Wails.
+- [Mat Ryer](https://github.com/matryer) - His support, encouragement and feedback has really helped drive the project forward.
+
+And finally, I'd like to give a special thank you to all the [project sponsors](/docs/credits#sponsors), including [JetBrains](https://www.jetbrains.com?from=Wails), 
+whose support drive the project in many ways behind the scenes.
+
+I look forward to seeing what people build with Wails in this next exciting phase of the project! 
+
+Lea.
+
+PS: MacOS and Linux users need not feel left out - porting to this new foundation is actively under way and most of the hard work has already been done. Hang in there!
+
+PPS: If you or your company find Wails useful, please consider [sponsoring the project](https://github.com/sponsors/leaanthony). Thanks!

website/blog/authors.yml

@@ -0,0 +1,11 @@
+leaanthony:
+  name: Lea Anthony
+  title: Maintainer of Wails
+  url: https://github.com/leaanthony
+  image_url: https://github.com/leaanthony.png
+
+misitebao:
+  name: Misitebao
+  title: Front-End Architect
+  url: https://github.com/misitebao
+  image_url: https://cdn.jsdelivr.net/gh/misitebao/CDN@main/gravatar.gif

website/docs/about.md

@@ -0,0 +1,70 @@
+---
+sidebar_position: 1
+---
+
+# About
+
+## Overview
+
+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.
+
+Wails doesn't hold back with the eye candy either! This is [xbar](https://xbarapp.com) - a desktop application for MacOS
+written using Wails. It has menus, supports light and dark desktop themes, and the main window uses translucency that
+gives it that 'frosty' effect of a native app.
+
+<p class="text--center">
+<a href="https://xbarapp.com"><img src="/img/xbar-app-preview-2.png" width="75%"/></a>
+</p>
+
+## Native Elements
+
+Wails uses a purpose built library for handling native elements such as Window, Menus, Dialogs, etc, so you can build
+good-looking, feature rich desktop applications.
+
+**It does not embed a browser**, so it is resource efficient. Instead, it uses the native rendering engine for the
+platform. On Windows, this is the new Microsoft Webview2 library, built on Chromium.
+
+## Go & Javascript Interoperability
+
+Wails automatically makes your Go methods available to Javascript, so you can call them by name from your frontend!
+It even generates Typescript versions of the structs used by your Go methods, so you can pass the same data structures
+between Go and Javascript.
+
+## Runtime Library
+
+Wails provides a runtime library, for both Go and Javascript, that handles a lot of the things modern applications need,
+like Eventing, Logging, Dialogs, etc.
+
+## Live Development Experience
+
+### Automatic Rebuilds
+
+When you run your application in "dev" mode, Wails will build your application as a native desktop application, but will
+read your assets from disk. It will detect any changes to your Go code and automatically rebuild and relaunch your
+application.
+
+### Automatic Reloads
+
+When changes to your application assets are detected, your running application will "reload", reflecting your changes
+almost immediately.
+
+### Develop your application in a Browser
+
+If you prefer to debug and develop in a browser then Wails has you covered. The running application also has a webserver
+that will run your application in any browser that connects to it. It will even refresh when your assets change on disk.
+
+## Production-ready Native Binaries
+
+When you're ready to do the final build of your application, the CLI will compile it down to a single executable, with
+all the assets bundled into it. On Windows and MacOS, it is possible to create a native package for distribution. The
+assets used in packaging (icon, info.plist, manifest file, etc) are part of your project and may be customised, giving
+you total control over how your applications are built.
+
+## Tooling
+
+The Wails CLI provides a hassle-free way to generate, build and bundle your applications. It will do the heavy lifting
+of creating icons, compiling your application with optimal settings and delivering a distributable, production ready
+binary. Choose from a number of starter templates to get up and running quickly!

website/docs/community/_category_.json

@@ -0,0 +1,4 @@
+{
+  "label": "Community",
+  "position": 50
+}

website/docs/community/links.mdx

@@ -0,0 +1,19 @@
+---
+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.
+
+## 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)
+
+## Social Media
+
+ - [Twitter](https://twitter.com/wailsapp)

website/docs/community/showcase/_category_.json

@@ -0,0 +1,4 @@
+{
+  "label": "Showcase",
+  "position": 1
+}

website/docs/community/showcase/encrypteasy.mdx

@@ -0,0 +1,10 @@
+
+# EncryptEasy
+
+<p style={{"text-align": "center"}}>
+   <img src="encrypteasy.jpg"></img><br/>
+</p>
+
+**[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.

website/docs/community/showcase/filehound.mdx

@@ -0,0 +1,23 @@
+
+# FileHound Export Utility
+
+<p style={{"text-align": "center"}}>
+   <img src="filehound.jpg"></img><br/>
+</p>
+
+
+[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

website/docs/community/showcase/mollywallet.mdx

@@ -0,0 +1,9 @@
+
+# Molley Wallet
+
+<p style={{"text-align": "center"}}>
+   <img src="mollywallet.png"></img><br/>
+</p>
+
+[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.
+

website/docs/community/showcase/optimus.mdx

@@ -0,0 +1,9 @@
+
+# Optimus
+
+<p style={{"text-align": "center"}}>
+   <img src="optimus.png"></img><br/>
+</p>
+
+[Optimus](https://github.com/splode/optimus) is a desktop image optimization application. It supports conversion and compression between WebP, JPEG, and PNG image formats.
+

website/docs/community/showcase/portfall.mdx

@@ -0,0 +1,9 @@
+
+# Portfall
+
+<p style={{"text-align": "center"}}>
+   <img src="portfall.gif"></img><br/>
+</p>
+
+[Portfall](https://github.com/rekon-oss/portfall) - A desktop k8s port-forwarding portal for easy access to all your cluster UIs
+