Add wiki

[AxenoDev]

No description provided.

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds a VitePress documentation site under docs/: a site config (docs/.vitepress/config.mts), a theme extension (docs/.vitepress/theme/index.ts), theme components (CachedImage.vue, KikoHero.vue, KikoFeature.vue), and multiple style sheets. Adds documentation pages (docs/pages/index.md, markdown-examples.md, api-examples.md). Updates .gitignore at repo root and docs/.gitignore to ignore runtime, build, Bun-specific, tooling, and cache artifacts. Adds a root package.json with dev dependencies and scripts for docs:dev, docs:build, and docs:preview.

🚥 Pre-merge checks | ✅ 1 | ❌ 3

❌ Failed checks (1 warning, 2 inconclusive)

Check name	Status	Explanation	Resolution
Merge Conflict Detection	⚠️ Warning	❌ Merge conflicts detected (12 files): ⚔️ .editorconfig (content) ⚔️ .gitignore (content) ⚔️ build.gradle.kts (content) ⚔️ gradle.properties (content) ⚔️ src/main/java/fr/kikoplugins/kikoapi/KikoAPI.java (content) ⚔️ src/main/java/fr/kikoplugins/kikoapi/KikoAPILoader.java (content) ⚔️ src/main/java/fr/kikoplugins/kikoapi/updatechecker/UpdateChecker.java (content) ⚔️ src/main/java/fr/kikoplugins/kikoapi/updatechecker/UpdateCheckerListener.java (content) ⚔️ src/main/java/fr/kikoplugins/kikoapi/utils/StringUtils.java (content) ⚔️ src/main/java/fr/kikoplugins/kikoapi/utils/Task.java (content) ⚔️ src/main/resources/config.yml (content) ⚔️ src/main/resources/paper-plugin.yml (content) These conflicts must be resolved before merging into master.	Resolve conflicts locally and push changes to this branch.
Title check	❓ Inconclusive	The title 'Add wiki' is vague and generic; it does not clearly describe what specific wiki additions or documentation changes are being made.	Use a more descriptive title that specifies the changes, such as 'Add VitePress documentation site with theme components and configuration' or 'Initialize wiki documentation with VitePress setup'.
Description check	❓ Inconclusive	No description was provided by the author; without any content, it is impossible to assess relevance to the changeset.	Add a pull request description explaining the purpose, scope, and key components of the documentation site setup.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 18

[PuppyTransGirl]

I've put some messages on the CodeRabbit reviews that might need to be looked into

[coderabbitai]

Actionable comments posted: 6

[coderabbitai]

Actionable comments posted: 2

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[coderabbitai]

Actionable comments posted: 1