Updated wiki to match core update

Author: Tigerpanzer02

.github/workflows/deploy.yml

@@ -0,0 +1,40 @@
+name: Deploy to GitHub Pages
+
+on:
+  push:
+    branches:
+    #  - source
+    # Review gh actions docs if you want to further define triggers, paths, etc
+    # https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#on
+
+jobs:
+  deploy:
+    name: Deploy to GitHub Pages
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+      - uses: actions/setup-node@v3
+        with:
+          node-version: 18
+          cache: yarn
+
+      - name: Install dependencies
+        run: yarn install --frozen-lockfile
+      - name: Build website
+        run: yarn build
+
+      # Popular action to deploy to GitHub Pages:
+      # Docs: https://github.com/peaceiris/actions-gh-pages#%EF%B8%8F-docusaurus
+      - name: Deploy to GitHub Pages
+        uses: peaceiris/actions-gh-pages@v3
+        with:
+          github_token: ${{ secrets.GITHUB_TOKEN }}
+          # Build output to publish to the `gh-pages` branch:
+          publish_dir: ./build
+          # The following lines assign commit authorship to the official
+          # GH-Actions bot for deploys to `gh-pages` branch:
+          # https://github.com/actions/checkout/issues/13#issuecomment-724415212
+          # The GH actions bot is used by default if you didn't specify the two fields.
+          # You can swap them out with your own user credentials.
+          user_name: github-actions[bot]
+          user_email: 41898282+github-actions[bot]@users.noreply.github.com

.github/workflows/documentation.yml

@@ -0,0 +1,27 @@
+name: Test deployment
+
+on:
+  pull_request:
+    branches:
+      - source
+  push:
+    branches:
+      - source
+    # Review gh actions docs if you want to further define triggers, paths, etc
+    # https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#on
+
+jobs:
+  test-deploy:
+    name: Test deployment
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+      - uses: actions/setup-node@v3
+        with:
+          node-version: 18
+          cache: yarn
+
+      - name: Install dependencies
+        run: yarn install --frozen-lockfile
+      - name: Test build website
+        run: yarn build

.github/workflows/test-deploy.yml

@@ -18,4 +18,3 @@
 npm-debug.log*
 yarn-debug.log*
 yarn-error.log*
-

.gitignore

@@ -1,37 +1,41 @@
-# Plugily Projects Page
-
-This repository represents https://wiki.plugily.xyz
-
 # Website
 
-This website is built using [Docusaurus 2](https://v2.docusaurus.io/), a modern static website generator.
+This website is built using [Docusaurus 2](https://docusaurus.io/), a modern static website generator.
 
-## Installation
+### Installation
 
-```console
-yarn install
+```
+$ yarn
 ```
 
-## Local Development
+### Local Development
 
-```console
-yarn start
+```
+$ yarn start
 ```
 
-This command starts a local development server and open up a browser window. Most changes are reflected live without having to restart the server.
+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
+### Build
 
-```console
-yarn build
+```
+$ yarn build
 ```
 
 This command generates static content into the `build` directory and can be served using any static contents hosting service.
 
-## Deployment
+### Deployment
+
+Using SSH:
 
-```console
-GIT_USER=<Your GitHub username> USE_SSH=true yarn deploy
+```
+$ USE_SSH=true yarn deploy
+```
+
+Not using SSH:
+
+```
+$ GIT_USER=<Your GitHub username> 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.

README.md

@@ -1,10 +1,7 @@
 ---
 slug: new-wiki
 title: Introducing our new Wiki
-author: Tigerpanzer_02
-author_title: Manager of Plugily Projects
-author_url: https://github.com/Tigerpanzer02
-author_image_url: https://avatars.githubusercontent.com/u/37453987?s=460&v=4
+authors: [tigerpanzer_02]
 tags: [welcome, plugily projects, new wiki]
 ---
 

blog/2021-02-28-new-wiki.md

@@ -1,10 +1,7 @@
 ---
 slug: summerbreak2021
 title: Summerbreak 21
-author: Tigerpanzer_02
-author_title: Manager of Plugily Projects
-author_url: https://github.com/Tigerpanzer02
-author_image_url: https://avatars.githubusercontent.com/u/37453987?s=460&v=4
+authors: [tigerpanzer_02]
 hide_table_of_contents: false
 tags: [summerbreak, plugily projects, plugily, news, betatester, planned]
 ---

blog/2021-08-20-summerbreak2021.mdx

@@ -0,0 +1,102 @@
+---
+slug: next-generation
+title: Next Generation - Minigame Core
+authors: [tigerpanzer_02]
+tags: [minigame core, 1.20 update, 1.19 update, 1.18 update, plugily projects, plugily, news, betatester, planned]
+---
+:::info Minecraft version compatibility
+The core update introduces 1.18 to 1.20 added support while maintaining our legacy versions still. Our plugins supports 1.8.8+ and java8!
+
+We strongly recommend to update your minecraft and java versions shortly as we are (like the spigot community) dropping support requests for 1.18 and lower versions. They will still remain but may not work in the future! May you would need a spigot fork to be compatible with a more recent version of java!
+
+It won't take long and java 17 will be a requirement!
+:::
+
+:::danger Plugin Updating - New arena configuration needed
+On updating your plugins with the new core update you should make sure to take a **backup**! Our plugin tries to save all old configurations to a new folder, but you need to manually set it up again (**especially the arena setup!**).
+
+**WE STRONGLY *RECOMMEND* TO HANDLE THE PLUGIN UPDATES AS YOU WOULD INSTALL A NEW PLUGIN!**
+:::
+
+:::danger CORE UPDATE ROLLOUT - FULL ROLLOUT UNTIL AUGUST!
+We published Release Candidates to SPIGOTMC which will be there until tutorial videos, wiki and patreon addons gets fully updated.
+:::
+
+**Throwback**
+
+We started 2021 with the transformation to the core. At the end its a one man development why it takes so long. (You want to help, Write me fast, Now). Its free-time basis which sometimes in life got limited due to obvious reasons happen in life such as uni, illness, whatever you know better than me ;).
+
+**Minigame Core**
+
+As you have already seen above, we implemented the core finally! yeah. Its now way more easier to maintain and update all of our minigame plugins!
+
+
+**Planned**
+:::note In short
+Currently we want to enhance the experience with our plugins by adding new stuff to them and make the user experience easier.
+:::
+
+import Tabs from '@theme/Tabs';
+
+import TabItem from '@theme/TabItem';
+
+:::tip We got several stuff on our todo
+
+<Tabs
+defaultValue="feedbacky"
+values={[
+{label: 'Feedbacky - Plugin Updates', value: 'feedbacky'},
+{label: 'New Beta Programm', value: 'beta'},
+{label: 'Tails v3', value: 'tails'},
+{label: 'Websites', value: 'web'},
+]}>
+<TabItem value="feedbacky">
+Goal: Convert your posted ideas into actual code!
+
+How: Next updates will be focused on user requests provided from you by feedbacky.
+</TabItem>
+<TabItem value="beta">
+The beta program is now going (again) into **summer break.** We thank you for all the help over the last years! Currently we don't like the beta program anymore. It does not meet our quality standards anymore. We are thinking deeply and will start with a completely new system in the future. This new system will improve the contact between testers and plugily. It will optimize processes and the usefulness of a beta release.
+
+*Current process:*
+1 A beta is released
+2 Almost no feedback
+
+*Use at the moment:*
+- Almost none for both sides
+
+**Future flow:**
+
+1 Different roles of testers (currently there are internal and beta testers - future: DEV TESTERS and BETA TESTERS)
+
+2a DEV TESTERS will work hand in hand with Plugily in direct contact (more effort)
+
+2b BETA TESTERS will work in close contact with Plugily (less effort)
+
+3 Feedback will be collected through one point of contact
+
+4 Feedback will be evaluated or assessed
+
+5 Feedback will be implemented
+
+**Future benefit:**
+- mutual commitment to a common goal
+- Feedback flows directly into development
+
+
+**Will I be a beta tester in the future?**
+- Currently the new system is still in the thinking phase, so we plan that all beta testers can also be a beta tester in the new system.
+- There will be a choice of roles in the new system, so it will be your own interest
+- It will be extensively documented, from which you can deduce if you want to be a beta tester in the new system.
+
+
+**How can I help atm until new platform get released?**
+- You can always try a automatically generated SNAPSHOT version and tell us if the feature for the SNAPSHOT version works or not on the correct discord channel
+- SNAPSHOT versions can be downloaded (soon) by using latest channel on https://download.plugily.xyz
+
+</TabItem>
+<TabItem value="tails">Currently our Bot Tails is at his 2. Generation. We will try to start the 3. Generation of Tails with a lot of new and additional stuff that was never seen anywhere before. It doesn't only contain ticket improvements and a working verification system. It also includes some currency module to earn points with activity that can be used to claim one patreon addon as prize.</TabItem>
+<TabItem value="web">We are creating and redesigning all our web pages to be more simple and modern. There will be a lot of internal and external new platforms that will help with the communication beetween you and us</TabItem>
+</Tabs>
+
+:::

blog/2023-06-21-Next Generation - Minigame Core.mdx

@@ -0,0 +1,5 @@
+tigerpanzer_02:
+  name: Tigerpanzer_02
+  title: Manager of Plugily Projects
+  url: https://github.com/Tigerpanzer02
+  image_url: https://avatars.githubusercontent.com/u/37453987?s=460&v=4