DocsGuides
Extending Trentarev
Principles for contributing and extending functionality within the ecosystem.
When building new functionality or contributing to the desktop or server ecosystems, our number one rule is simplicity and restraint.
Server Guidelines
- Domain Separation: Never mix Market and Product domain logic in the same router namespace.
- Error Handling: All HTTP responses must return strictly valid JSON. Avoid stack traces printing in a production runtime environment.
- Migrations: Do not use migration frameworks. Schema schemas are initialized linearly on server start if tables don't exist.
Client Guidelines
- Simplicity: Build exclusively within established Shadcn-style components.
- Animations: Limit Framer Motion to deliberate state changes, not decoration.