How koster/cms works
Project type and purpose
• This is a Unity Package (“test-package” / “CMS”) delivered via the Unity Package Manager (manifest.json & package.json).
• It provides a Content Management System (CMS) as a runtime library (Runtime/CMS) plus Unity Editor extensions (Runtime/Editor).
File structure
• Top-level:
• manifest.json & package.json – Unity Package metadata
• Runtime/ – contains all Unity-compatible code
• Runtime/CMS/ – the core CMS runtime assembly (CMS.asmdef)
• CMS.cs – main entry point
• Common/ – data structures & utilities (tags, reflection helpers, SFX definitions)
• CMS.asmdef / CMS.asmdef.meta – defines a Unity assembly for runtime code
• Runtime/Editor/ – editor-only code (no asmdef, but built into the Editor when package is installed)
• CMSMenuItems.cs – menu commands exposing CMS features in the Unity Editor
• README.md – minimal description; no internal architecture doc
Key architecture insights from structure
• Two main assemblies:
a. Runtime Assembly (“CMS”) – compiled into game builds
b. Editor Assembly – runs only inside Unity Editor, depends on Runtime Assembly
• Common utilities (tags, reflection) are shared by both Editor and Runtime code
• Separation enforced by asmdef files and Unity Package Manager
Elements
• Package Manager → Assembly loading
• Editor Assembly → Runtime API calls
• Game Scripts → Runtime API calls