Your craft.
A foundation worth reusing.
Build distinctive client experiences on shared content and business capabilities. Choose your frontend, extend the platform, and keep each client’s instance in focus.
Room to grow.
Built differently.
Go further.
A different client.
A considered starting point.
Reuse the structure and integration work that deserves to be reused. Give every client an experience shaped around their brand, content, and business.
Repeat the good decisions.
Keep the identity individual.
Use blueprint components and content types as a dependable approach to page composition. Your frontend controls the visual language, so a reusable content foundation can support three very different brands.
- Model a small library of useful page components
- Adapt the frontend to each client’s design system
- Keep each client’s tenant instance in focus
Room to grow.
Built differently.
Go further.
Build in the stack
your team already knows.
Choose official TypeScript or PHP SDKs, or packages for Next.js and Laravel. The Next.js storefront starter gives commerce projects an available source foundation to inspect and adapt.
- Use official language and framework packages
- Keep privileged credentials in server configuration
- Adapt the available storefront source to the brief
npm add @ominity/api-typescriptcomposer require ominity/ominity-api-phpnpm add @ominity/nextcomposer require ominity/laravel-ominityA client’s business
rarely fits one generic field.
Extend product, customer, or other business records with typed custom fields. When the workflow needs its own capabilities, a self-contained extension can own the domain instead of pushing all that behavior into frontend code.
- Add the data fields the client actually needs
- Choose response and update behavior deliberately
- Keep project-specific operations in an extension
Hand over a system
people understand.
Give contributors clear models and appropriate administrator permissions. A good handover shows where information belongs, how translations inherit their source, and which operations a person can perform.
- Define understandable fields and relationships
- Separate editing and administration permissions
- Show default-language inheritance during handover
Connect the other systems.
Keep the outcome visible.
An extension can connect the client’s own services and business operations. Actions and outboxes keep the internal change connected to any external delivery, including the attempts that follow when delivery needs a retry.
- Express business changes as deliberate actions
- Link external work to its originating execution
- Inspect failures without losing the request context
Internal completion does not mean external delivery has finished.
Explore the details.
The capabilities, examples, and integration choices behind this solution.
Bring your next brief.
Build the right foundation.
Discuss the client’s content, commerce, and application needs, then choose the capabilities that belong in the project.