Extending SolidX
Reference for extending SolidX through generated code, frontend customization, and backend customization.
Mental Model
Extending SolidX is primarily about choosing the correct layer for customization and preserving the distinction between metadata-driven behavior and project-specific implementation.
Generated codeprovides the baseline structure and default runtime composition.Frontend customizationtargets user-facing workflows, layout behavior, widgets, routes, and UI extensions.Backend customizationtargets domain logic, integrations, runtime policies, and non-declarative behavior.
This section documents where customization belongs so implementation stays aligned with framework conventions rather than bypassing them.
This section outlines how to extend SolidX to build your own functional modules, such as a school-fees-portal.
SolidX provides a code-generation workflow that scaffolds the baseline structure for new modules so you can focus directly on business logic rather than foundational setup.
In addition to scaffolding, SolidX supports customization across both frontend and backend layers. You can tailor UI components, adjust generated behavior, or introduce project-specific runtime logic where the default platform behavior is not enough.
Extension Areas
SolidX provides the following extension areas:
Code Generation
Generate the baseline structure for new modules and models, including controllers, services, entities, DTOs, repositories, and default frontend layout metadata.
Frontend Customization
Customize generated UI behavior through layouts, widgets, buttons, routes, custom pages, event handlers, and other module-specific frontend extensions.
Backend Customization
Extend the NestJS backend with services, controllers, providers, middleware, integrations, subscribers, scheduled jobs, and business-specific runtime behavior.
Built-in Reference
Review the built-in providers, widgets, primitives, and extension surfaces that already ship with SolidX before implementing custom versions.