Releases: o2sdev/openselfservice
@o2s/blocks.quick-links@1.0.1
@o2s/blocks.category-list@1.0.1
docs-v1.2.4
docs: LP ui fixes
docs-v1.2.3
docs: dxp LP ui fixes
docs-v1.2.2
Update overview.md
DXP 1.0.0 release
We're excited to announce an initial release of our new Digital Experience Platform Frontend Starter Kit built on top of O2S! Kick-start your modern, composable digital platform with our Next.js based starter and built-in CMS integration.
What is DXP Starter Kit?
The Digital Experience Starter is a frontend starter based on our composable framework architecture, developed within the Open Self Service project. It provides a solid foundation for building large-scale solutions, and it is easy to extend and customize, solutions from simple portals to full-fledged digital platforms.
What makes this kit unique is its flexibility. It allows teams to start quickly with a clean, well-structured frontend and evolve over time, adapting the architecture to meet growing business needs and integrating with additional services as needed.
Although it can be used in many contexts, the Starter Kit is particularly well-suited for solutions that involve customer interaction and service enablement. Thanks to its modular, headless, and API-first architecture, it’s easy to evolve the solution toward rich, customer-facing experiences - without rebuilding from scratch.
In fact, our long-term development focus is on use cases around customer support and self-service.
That’s where the flexibility and composability of the Starter can deliver the most value — enabling fast, scalable, and future-proof digital platforms.
The framework and this starter reflect everything we’ve learned during real projects. We’ve packaged our best practices into an open-source solution that we’re proud to share with the world today.
Architecture
The DXP Starter Kit relies on exactly the same architecture that is already utilized in the Open Self Service, with:
- a decoupled Frontend app,
- an intermediate Harmonization server for data aggregation, orchestration and normalization,
- and a UI component library.
This new starter also is built on top of the recently released new approach to blocks so you can already start with a more modular way of working.
Features
The DXP Frontend Starter is designed for building knowledge bases, marketing portals, and Digital Experience Platforms (DXP) of any size. It provides a foundation for content-rich applications that can evolve into comprehensive digital experience solutions. Its features can be extended with Blocks or integrations O2S provides or your own.
To get a quick overview about what kind of blocks DXP Starter supports, you can now view our newly released Storybook and also a demo app that showcases what can be built using our components.
Take a look at our DXP Frontend Starter chapter to learn more about what's included in this starter.
Get started now!
To get started, you can use our NPM script to create a new project:
npx create-dxp-app@latest my-dxp-portalwhich, just like in O2S, will create a pre-configured template with all the necessary components, integrations, and best practices to accelerate your development and is ready for your own customizations.
For more information about installation and requirements, see the Getting started chapter in our docs.
1.2.0
We're excited to announce Release 1.2.0 of Open Self Service, featuring a major architectural improvement in how we handle blocks. This release focuses on making the platform more modular, maintainable, and developer-friendly. Let's explore what's new!
New features
Modular approach to blocks
We've completely reworked our approach to blocks by separating all block-related code from the api-harmonization and frontend apps into independent packages. This architectural change brings several significant benefits:
- Independent versioning: Each block can now be versioned separately, allowing for more granular updates
- Simplified maintenance: Blocks can be developed, tested, and deployed independently
- Easier integration: Adding blocks to your projects is now as simple as installing an NPM package
- Better developer experience: Clear separation of concerns makes the codebase more maintainable
Each block is now a standalone NPM package with three main components:
- API Harmonization Module: Handles data aggregation and normalization
- Frontend Components: React-based implementations for UI rendering
- SDK Methods: Simplified access to the block's API
With our new approach to blocks, integrating blocks into your application is more straightforward than ever:
npm install @o2s/blocks.block-name --workspace=@o2s/api-harmonization --workspace=@o2s/frontendOnce installed, blocks can be easily imported and used in both the API Harmonization server and Frontend app with minimal configuration.
Need to customize a block beyond its basic configuration? Our new architecture makes it easy to "eject" a block and take full ownership of its source code:
npm run eject-blockThis gives you complete control over the block's implementation while still maintaining compatibility with the rest of your application.
For more information and guides, see the Blocks chapter in our documentation.
Other changes
Storybook integration
We've added Storybook to Open Self Service, providing a powerful development environment for UI components. Storybook is now available:
- Locally: Run
npm run storybookin your project to launch it - Publicly: Access our always-up-to-date version at https://storybook-o2s.openselfservice.com/
Storybook serves as both a development tool and living documentation, making it easier for teams to collaborate on UI components and maintain design consistency throughout the application.
At the moment our Storybook includes only blocks - stay tuned for upcoming updated, where we will also include the components from our UI Library.
Updated documentation
We've made significant improvements to our documentation that should improve its readability and make it easier to find what you need:
New Customization chapter
We've added a dedicated Customization chapter that provides quick links to important sections for extending both starters and the framework itself. This centralized resource makes it easier to find guides for:
- Using generators for blocks and UI
- Adding and customizing existing blocks
- UI theme customization
- Extending integrations
App Starters documentation
We've added new pages for app starters in our documentation, providing information about different starter templates to help you bootstrap your frontend applications:
- O2S Customer Portal starter: Our default starter for customer self-service portals
- DXP Frontend Starter: A new starter for knowledge and marketing portals evolving to Digital Experience Platforms (DXP)
Stay tuned for more updates on the DXP starter as we continue to enhance its capabilities and documentation!
Bugfixing and security updates
As always, we're committed to maintaining a stable and secure platform. This release includes various bug fixes and security updates to ensure your Open Self Service implementation remains reliable and up-to-date.
@o2s/integrations.mocked@1.11.1
Patch Changes
- 9c62515: removed Polish characters from mocked URLs for servivces
create-o2s-app@1.1.2
Patch Changes
- c25f982: updated script to remove unneeded files
create-o2s-app@1.1.1
Patch Changes
- ebadc3f: updated script to remove blocks and updated telemetry version