Update blog

This reverts commit f587457e7e.

.github/workflows/check_docs.yml

@@ -1,23 +0,0 @@
-name: Check Docs
-on:
-  pull_request:
-    branches: [ 'feature/*' ]
-
-jobs:
-  docs:
-    name: Website Updated
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v2
-
-      - name: Verify Changed files
-        uses: tj-actions/verify-changed-files@v11.1
-        id: verify-changed-files
-        with:
-          files: |
-            v2/website/*.mdx
-
-      - name: Run step only when files change.
-        if: steps.verify-changed-files.outputs.files_changed != 'true'
-        run: |
-          echo "Feature branch does not contain any changes to the website."

.github/workflows/pr.yml

@@ -1,40 +0,0 @@
-name: PR Checks
-on:
-  pull_request:
-
-jobs:
-  check_branch_name:
-    runs-on: ubuntu-latest
-    name: Check branch name
-    steps:
-      - run: |
-          if ! [[ "$(echo ${GITHUB_HEAD_REF} | cut -d "/" -f1)" =~ (feature|bugfix|release|chore) ]]; then
-            echo "PRs are only accepted for branches starting with: feature/, bugfix/, chore/ or release/"
-            exit 1
-          fi
-        shell: bash
-
-  test:
-    name: Run Go Tests
-    runs-on: ${{ matrix.os }}
-    needs: check_branch_name
-    strategy:
-      matrix:
-        os: [ ubuntu-latest, windows-latest, macos-latest ]
-        go-version: [ 1.18, 1.19 ]
-
-    steps:
-      - name: Checkout code
-        uses: actions/checkout@v2
-
-      - name: Install linux dependencies
-        if: matrix.os == 'ubuntu-latest'
-        run: sudo apt-get update -y && sudo apt-get install -y libgtk-3-dev libwebkit2gtk-4.0-dev build-essential pkg-config
-
-      - name: Set up Go 1.18
-        uses: actions/setup-go@v3
-        with:
-          go-version: ${{ matrix.go-version }}
-
-      - name: Run tests
-        run: go test -v ./...

website/blog/2022-09-22-v2-release-notes.mdx

@@ -10,6 +10,7 @@ tags: [wails, v2]
   <img
     src={require("@site/static/img/blog/montage.png").default}
     width="75%"
+    class="screenshot"
   />
 </div>
 <br />

website/i18n/ja/docusaurus-plugin-content-blog/2022-09-18-v2-release-notes.mdx

@@ -13,6 +13,7 @@ tags:
   <img
     src={require("@site/static/img/blog/montage.png").default}
     width="75%"
+    class="screenshot"
   />
 </div>
 <br />

website/i18n/zh-Hans/docusaurus-plugin-content-blog/2022-09-18-v2-release-notes.mdx

@@ -13,6 +13,7 @@ tags:
   <img
     src={require("@site/static/img/blog/montage.png").default}
     width="75%"
+    class="screenshot"
   />
 </div>
 <br />

website/src/pages/community-guide.mdx

@@ -56,8 +56,8 @@ The process for adding new features are as follows:
   person who opened the ticket. Sometimes placeholder tickets are created and require more details
 - Comment on the ticket stating if you wish to develop the feature
 - Clone the repository and create a branch with the format `feature/<ticket_number>_<ticket_title>`
-- New features will require documentation so please ensure you have also added or updated the documentation as part of
-  the changes. Feature PRs without changes to the documentation will not be accepted.
+- 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.
@@ -99,23 +99,6 @@ bugfixes should be discussed as the approach may have unintended side effects.
 Any PRs opened without a corresponding ticket may be rejected.
 :::
 
-### Chores
-
-Chores are tasks that need to be done but are not directly related to the codebase. Examples
-include:
-
-- Updating documentation
-- Writing tutorials / guides
-- Updating GitHub templates or actions
-- Adding scripts to help with development
-
-If you wish to work on a chore, please open a ticket and comment on it stating you wish to do so. 
-Chores are not assigned to anyone and are open to anyone who wishes to work on them. If you have
-any questions, please ask in the [Contributing to Wails](https://github.com/wailsapp/wails/discussions/1520)
-discussion or on slack.
-
-PRs for chores should be done from a `chore/<ticket_number>_<ticket_title>` branch.
-
 ### Testing
 
 Testing is vitally important to ensure quality in the project. There are a couple of