docs(readme): update README for clarity and consistency

- Translated sections from German to English for better accessibility.
- Enhanced the structure by clearly defining the workspace relationship and local development instructions.
- Improved descriptions for Docker setup and deployment processes to ensure users understand the requirements and context.
- Updated links and formatting for consistency throughout the document.

This commit aims to improve the overall clarity and usability of the README documentation.
This commit is contained in:
Marvin
2026-04-10 02:12:06 +02:00
parent 66b8446d19
commit 8d8fda49c4
227 changed files with 498 additions and 2496 deletions

View File

@@ -1,13 +1,13 @@
---
title: FFI, hooks & Lua
sidebar_label: FFI, hooks & Lua (hub)
description: FFI, hook lists, naming — bridge between framework and legacy wiki.
description: FFI, hook lists, naming — curated reference for mod and plugin authors.
---
# FFI, hooks & Lua
- [FMF hooks catalog](/wiki/reference/fmf-hooks-catalog) (generated)
- [FMF hook naming](/wiki/reference/fmf-hook-naming)
- Imported: [HOOKS](/wiki/legacy/wiki-import/HOOKS), [Hook naming convention](/wiki/legacy/wiki-import/HOOK-NAMING-CONVENTION)
- Imported: [FFI bridge reference](/wiki/legacy/wiki-import/FFI-Bridge-Reference), [Lua FFI start](/wiki/legacy/wiki-import/Lua-FFI-Start-Developing)
- Imported: [Mod developer debug](/wiki/legacy/wiki-import/Mod-Developer-Debug)
- [FMF hooks](/wiki/framework/fmf-hooks) generated hook surface
- [FMF hooks catalog](/wiki/reference/fmf-hooks-catalog) — strings from core sources
- [FMF hook naming](/wiki/reference/fmf-hook-naming) — `FMF.*` vs legacy `FFM.*`
- [Framework architecture](/wiki/framework/architecture) — bridges (including Rust) and runtime layout
- [Modding language requirement](/wiki/reference/modding-language-requirement) — C# policy for mods/plugins