BluKavantUI Community 1.2.0 for OutSystems 11
Install the library OAP first, then the optional demo OAP. In Service Studio, use Manage Dependencies to add only the BluKavantUi_Community producer blocks used by your application. Refresh existing consumers after upgrading and validate them before publishing. Keep a backup of your current application.
The library provides 85 public native blocks, including 12 motion foundation blocks. Start with the demo’s Base animations and Animation integration pages: each example shows the effect, its controls, and the corresponding CSS classes or block inputs. Effects use a 750 ms default and support System, Reduced and Off motion modes. Respect reduced-motion preferences and keep essential information available without animation.
Use the component playgrounds for Button, form inputs, menus, overlays, layouts and data controls. The Fieldwork portfolio screen template demonstrates title, container and image effects in a complete screen. Copy the template into your own app and replace its sample content.
Documentation and component API examples: https://blukavantui.blutekmedia.com/components?platform=outsystems
Animation classes and examples: https://blukavantui.blutekmedia.com/foundations/animations
Release notes and upgrade guidance: https://blukavantui.blutekmedia.com/releases/1.2.0
Community is distributed under the existing BluKavantUI Community licence. Pro components require a separate licence and download; they are not included in this Forge package.
Install and upgrade
Install BluKavantUI Community 1.1.0 from this listing before installing its separate demo. In an existing consumer, open Manage Dependencies, refresh the Community references, resolve any application-specific validation messages and test before publishing your consumer. Keep your existing module exports as a rollback.
Choose the Community producer that contains the component. Reference its public Block and the exact Structures and events documented in the component API. Inherit the shared Community theme in your application theme. Do not mix similarly named types from the Community and Pro producers. The library and matching Community demo do not require OutSystems UI or Pro.
Forms
Bind Value or Checked to application state and handle the documented change event to update that state. Your application owns business validation, authorization and saving. Provide a meaningful label and help/error text. For text boxes with images visible in Service Studio, use InputGroup with actual Image widgets in Leading or Trailing and TextInput in Control. Keep the accessible label on the TextInput. Runtime image URL inputs resolve when the application runs.
Layouts and Table
Two Columns, Three Columns and Four Columns expose content slots, responsive proportions and EqualHeight. Use the fixed-proportion helpers when the design canvas needs to show the proportions directly. Table consumes your supplied records and exposes sorting, paging and row-action events; it does not supply a database or authorization layer.
Explore the matching demo
New components are marked v1.1.0 in the sidebar. Playground controls update the component, Examples shows rendered scenarios, and API, Implementation and Accessibility provide the native contracts and integration guidance. Use Try in playground to load an example configuration.
Full setup and theme guidance: https://blukavantui.blutekmedia.com/integration
Component catalogue and API documentation: https://blukavantui.blutekmedia.com/components?platform=outsystems-community
Live Community demo: https://personal-6kr71auc.outsystemscloud.com/BluKavantUi_Community_Demo/
Support: https://blukavantui.blutekmedia.com/contact
Community is free for personal, internal and commercial end-user applications under the included Community Free Use, Official Distribution Licence 1.2. Private modification is permitted; redistribution of the reusable library is restricted. Third-party licences remain applicable.
BluKavantUI Community provides 55 reusable UI components for OutSystems 11 Reactive Web, including layout, navigation, forms, feedback, media and a read-only Basic Grid.
No BluKavantUI account, subscription or license key is required to use Community.
Install BluKavantUI Community from Forge using Service Studio.
Allow Service Studio to install the included libraries and resolve their dependencies:
BluKavantUi_Community_Core
BluKavantUi_Community_Layout
BluKavantUi_Community_Inputs
BluKavantUi_Community_Feedback
BluKavantUi_Community_Data
BluKavantUi_Community_Content
BluKavantUi_Community_Grid
Open your Reactive Web application and select Manage Dependencies.
Add BluUICommunityTheme from BluKavantUi_Community_Core, together with the public Blocks and Structures required by your screens.
BluUICommunityTheme
Set your application theme’s Base Theme to BluUICommunityTheme.
Community uses its own theme and components. It does not require OutSystems UI, OutSystems Charts, OutSystems Maps or BluKavantUI Pro. When changing the base theme of an existing application, review its existing screens and custom styles before publishing.
Full installation and module guide
Find a component in the Community catalogue.
Open its documentation and select OutSystems.
Use the Implementation tab for Service Studio setup, data binding and event-handling instructions.
Use the API tab for the native producer, input parameters, public Structures and event payloads.
Add the documented Block to your screen.
Bind its inputs to screen variables, expressions or application data.
Create Client Action handlers for the events your application needs, and connect them to your application logic.
Use the native OutSystems Blocks and their documented contracts. The Web/TypeScript examples describe a separate integration and should not be pasted into native Block parameters.
Your application owns its business data and persistence. Components display and interact with the data supplied to them; they do not automatically save changes to your database.
Where applicable:
Populate inputs using Aggregates, Data Actions or screen variables.
Handle component events to validate input, update state or call Server Actions.
Supply your own upload endpoints and external services.
Configure any AI services used by chat components in your application.
Basic Grid supports client-side sorting, filtering, pagination, column sizing and single-row selection. For advanced Grid capabilities, consult the edition comparison and component documentation.
The Community UI Demo is a separate, optional application. It is not required by the reusable libraries.
Open the Community UI Demo
To inspect its implementation, install the separate demo package after the Community libraries, then open its screens in Service Studio. The demo references the Community libraries and the platform’s Users application.
After updating the libraries, open Manage Dependencies in your consuming modules and refresh changed public elements. Resolve validation messages, review your bindings and test affected screens before publishing.
If a component appears unstyled, check its producer references and the BluUICommunityTheme base-theme configuration. For data or event issues, compare your bindings with the component’s OutSystems Implementation and API guides.
Version 1.0.1 was validated on Platform Server 11.42.1.47790
Accessibility guidance and review results
Contact support — include your platform version, component name, reproduction steps and any error message.