Start your journey here
Author:
Fluent Commerce
Changed on:
29 Oct 2024
Overview
To guide you through your journey of understanding and learning the Fluent Commerce OMS platform, the documentation is modeled according to the internal building blocks of the system, like 🔀Workflow or ⚙️Settings, with other top-level content types, such as 💡Essential Knowledge and 🧭How-to Guides layered on top of it. Dive right into it by starting here.
Key points
- Navigating through the content structure will help you better understand the platform's inner workings, dependencies, and components.
- Leverage the extensive tagging system to narrow your search for the right article.
- Feedback wherever you want to highlight areas of improvement.
Fluent Commerce OMS
At its core, Fluent Commerce OMS is an event-driven system with three main components. The user interface, the event orchestration, and the extensibility layer:
- The front-end user interface is the responsibility of the User Interface Framework (UX Framework, codename Mystique).
- The workflow framework (workflow engine, codename Rubix) drives the event orchestration.
- The extensibility layer consists of APIs and SDKs, helping to shorten development time.
Fluent-specific JSON application manifests are used to make these layers work together. Application manifests are commonly used to drive web application behavior.
User Interface Framework
React UI components drive the User Interface (UI) Framework. Users can change the application behavior by adjusting Settings in the application's UI.
Workflow Framework
The workflow framework is used to specify application behavior via a Workflow definition in a JSON manifest. Workflows execute a ruleset, which is a chain of Rules.
Extensibility layer
Almost every part of the platform can be extended. These extension points correspond to the above layers, with the Component SDK for extending the User Interface Framework, the Connect SDK to connect to third-party systems, and the Rules SDK to extend the workflow framework.
A GraphQL endpoint with standard mutation operations support provides direct access to the application data, and batch operations can be executed with the REST API.
Interface contracts explained through Interface contract flows are used to connect different pieces of the app together to have a transparent way of interacting with individual application parts.
Flexible deployment
Application packages (modules) are used to help with repeatable deployments. Those are distributable ZIP packages containing all the artifacts mentioned in this article. You can deploy these manually or with a CLI interface.
Given the above, you can see how powerful the extensibility model of Fluent Commerce OMS is. Guiding you in understanding this flexible platform is this documentation portal reflecting individual parts of this platform with platform-specific content types.
Browsing the documentation
Discover higher-level content to understand the essentials and head to Essential Knowledge.
If you are curious about Features, Topics, or How-to guides, browse the content By type.
Ready to dive deep? Head to Building Blocks to discover the core building blocks of the platform, such as Workflows, Settings, Rules, Interface contracts, or UI Components.
Check other ways to experience the documentation as a Developer or Partner, or start here if you are Exploring the Fluent Commerce platform in general.
