📄docs: add wiki to docs/

docs/Extensions.md

@@ -0,0 +1,13 @@
+# 4.1.alpha.2
+
+The new prerelease adds simple extensions, so you definitively want to know how it works. Just to note that this version is not deployed.
+For first, you will need to open the source code in a text editor that can run codes. 
+
+### How to add something to the menubar?
+Open the `extension_menubar.py` file. In the `main()`function, write the code to add something to the menubar. **You might not need to import the libraries separately in that file.**
+
+### How to add code straight to the `TextEditor` class?
+Open the `extension_mainclass.py` file. In the `main()`function, write the code to add something to the main class. **You might not need to import the libraries separately in that file.**
+
+### How to add code straight to the `main` function?
+Open the `extension_mainfn.py` file. In the `main()`function, write the code to add something to the main function. **You might not need to import the libraries separately in that file.**

docs/Github-Notifications.md

@@ -0,0 +1,29 @@
+Here, you will learn how to use the Github Integration feature.
+
+## Configuration
+To start, open the `repo.ghicfg` file. If you do not have one, create one.
+Set the value to:
+```
+user/repo:seconds_between reload
+```
+`user` - The owner of the repo<br>
+`repo` - The name of the repo<br>
+`seconds_between reload` - How much seconds between fetching repo data again<br>
+
+**Please set `seconds_between reload` to at least 600, or you will probably reach the API usage limits.**<br>
+**You can set as many repos as you want.**
+
+If you want to use your Github API Token, _you might reach API rate limits_, run:
+```cmd
+# Widnows
+setx GITHUB_TOKEN "your_token"
+```
+```bash
+# Linux / Unix / macOS
+export GITHUB_TOKEN=value
+source ~/.bashrc
+```
+
+## Disclaimer
+* I'm not responsible for you reaching API limits.
+* If you reach an API rate limit on your API key, I'm not responsible for anything happening.

docs/Home.md

@@ -0,0 +1,4 @@
+### Welcome to the XediX Docs
+Here, you can find tutorials for XediX.
+
+

docs/How--to-use-XediX.md

@@ -0,0 +1,58 @@
+# Installation
+## Windows, v4.1.alpha.5+
+Basically the same as alpha.5, but there is not a file put in there by mistake :).
+
+## Windows, v4.1.alpha.5
+This release contains a zipfile with all the files, but do NOT use the xedixSetup.exe file. Use the main.exe file instead.
+
+## Windows 11
+
+**If there is not a setup file provided, there is probably a portable version instead.**
+
+To install XediX on Windows 11, follow these steps:
+
+### 1. Download the Latest Version
+- Go to the [XediX GitHub Releases](https://github.com/mostypc123/XediX/releases) page.
+- Download the latest setup file for Windows 11.
+- If the release is a pre-release, you can still take it as a stable version, it is just not complete.
+
+### 2. Run the Setup File
+- Once the download is complete, run the setup file to begin the installation process.
+- Follow the on-screen instructions to install XediX on your computer.
+
+### 3. Start Using XediX
+- After installation, you can open XediX directly from the start menu or your application folder, depending on your operating system.
+
+That’s it! You’re ready to start coding in Python with XediX.
+
+# Using XediX
+_For not using outdated info, this was writenn throught the beatiful day of 15.11.24_
+
+To start using XediX, download it with the installer.
+
+When you will download it, you will see this:
+![image](https://github.com/user-attachments/assets/57556268-09b6-4e6c-8c97-f6ed5059c0e4)
+
+Now the title screen actually says what you should do: Open a file.
+If you do not have a file to open, press New File.
+
+Enter the filename **without the file extension** and press next.
+
+Enter the file extension **without the dot** and press next.
+
+Now, you have a file created.
+You can:
+***
+**Run the code**: File > Run code
+
+**Run pylint**: File > Run pylint
+
+**Basic editing shortcuts**: Edit > Copy/Paste/Cut
+
+**Find/Replace**: Edit > Find/Replace
+
+**Run Tools**: Tools > Run Tools
+
+In the tools, you can run the Markdown/JSON preview/visualization, and the Map of Marks.
+
+

docs/Project-Initialization.md

@@ -0,0 +1,6 @@
+This is a very important thing if you want to make bigger projects in XediX. Because we all know you will not be working in the directory of XediX :).
+
+## How
+Go to Menu > Project > Init Project to start a new project in your directory. I also recommend running the other options (Git & Python Init).
+## Why
+XediX would not work if you do not init at least XediX.

docs/Theming.md

@@ -0,0 +1,15 @@
+## Theming
+Edit the theme.xcfg file to change your theme.
+You can set the theme to any of the following:
+### Obsidian
+![image](https://github.com/user-attachments/assets/99e3fa28-3726-411a-8618-81523ea4c888)
+
+### Dark (default)
+![image](https://github.com/user-attachments/assets/1376d058-5d2f-40ab-b5ea-8cd2faa2922c)
+
+### Light
+For the native UI guys. This theme will be improved for readable text :).
+![image](https://github.com/user-attachments/assets/9c2628b2-4d4c-4f44-8bf2-70cbc93afb90)
+
+### Night
+![image](https://github.com/user-attachments/assets/f2099e94-8d2a-434f-9867-0d4c1b22129d)

docs/_Footer.md

@@ -0,0 +1 @@
+For feedback, contact us at Discussions.