yesamer commented on code in PR #56:
URL:
https://github.com/apache/incubator-kie-website/pull/56#discussion_r3404456042
##########
blog/2026-06-09-new-generation-editors-kie-10-2.md:
##########
@@ -0,0 +1,147 @@
+---
+slug: new-generation-editors-kie-10-2
+title: "The Dawn of a New Era: Next-Generation Editors in Apache KIE 10.2"
+authors: [bento, bowers]
+tags: [apache, kie, editors, bpmn, dmn, scesim, modernization, tooling]
+---
+
+# The Dawn of a New Era: Next-Generation Editors in Apache KIE 10.2
+
+Apache KIE has been undergoing a significant transformation with the
introduction of next-generation editors for BPMN, DMN, and Test Scenario
(SceSim) modeling. Built from the ground up with modern web technologies, these
new editors deliver substantial improvements in performance, user experience,
and long-term maintainability. With the latest release, the new BPMN Editor
completes this modernization journey, setting the foundation for future
innovations across the entire tooling ecosystem.
+
+## The End of an Era: Saying Goodbye to GWT
+
+Let's be honest: the classic BPMN and DMN editors served us well for many
years. Built on Google Web Toolkit (GWT), they were powerful tools that enabled
thousands of developers and business analysts to model complex processes and
decisions. But technology moves forward, and what was cutting-edge a decade ago
can become a maintenance burden today.
+
+
+*The classic GWT-based BPMN Editor - showing the old interface with its
characteristic styling and layout*
+
+The GWT-based editors had their strengths:
+- Robust functionality that powered enterprise applications
+- Familiar interface for long-time users
+- Comprehensive feature sets built over years of development
+
+However, they also came with significant challenges:
+- **Performance bottlenecks** with large, complex models
+- **Limited responsiveness** on modern devices and screen sizes
+- **Maintenance complexity** as GWT itself moved toward end-of-life
+- **Integration friction** with contemporary web technologies and frameworks
+- **Accessibility concerns** that didn't meet modern standards
+
+As we committed to Apache KIE's graduation from incubation, it became clear:
we needed to modernize our tooling to align with Apache guidelines and
contemporary development practices.
+
+## The New Generation: Built for the Modern Web
+
+The new BPMN Editor in Apache KIE 10.2.0 isn't just a facelift; it's a
complete reimagining of what a process modeling tool should be in 2026. Built
from the ground up using modern web technologies, this editor represents the
culmination of extensive research, community feedback, and engineering
excellence.
+
+
+*The new BPMN Editor - showcasing the modern, clean interface with improved UX*
+
+### What Makes the New Editors Stand Out?
+
+#### 1. **Modern Technology Stack**
+
+The new editors leverage contemporary web technologies that ensure longevity
and maintainability:
+- **React-based architecture** for component reusability and performance
+- **TypeScript** for type safety and better developer experience
+- **PatternFly v5** for consistent, accessible UI components
+- **Modern build tooling** for faster development cycles
+
+This isn't just about using trendy frameworks - it's about building on stable,
well-supported technologies with thriving ecosystems and long-term viability.
+
+#### 2. **Performance That Scales**
+
+One of the most dramatic improvements is performance. The new editor handles
large, complex process models with ease:
+- **Instant loading** even for models with hundreds of nodes
+- **Smooth panning and zooming** without lag or stuttering
+- **Real-time validation** that doesn't slow down your workflow
+- **Optimized rendering** that uses modern browser capabilities
+
+#### 3. **Enhanced User Experience**
+
+Every interaction has been thoughtfully designed:
+- **Intuitive drag-and-drop** with smart snapping and alignment
+- **Context-aware property panels** that show exactly what you need
+- **Visual feedback** that guides you through complex operations
+
+<div style={{display: 'flex', gap: '20px', alignItems: 'flex-start'}}>
+ <div style={{flex: 1}}>
+ <img src="/img/blogs/old-bpmn-properties.png" alt="Old BPMN Properties
Panel" />
+ <p style={{textAlign: 'center', fontStyle: 'italic'}}>Classic properties
panel</p>
+ </div>
+ <div style={{flex: 1}}>
+ <img src="/img/blogs/new-bpmn-properties.png" alt="New BPMN Properties
Panel" />
+ <p style={{textAlign: 'center', fontStyle: 'italic'}}>New properties panel
with improved organization</p>
+ </div>
+</div>
+
+### DMN 1.6 Support: Staying Current with Standards
+
+While we're talking about modernization, it's worth highlighting that both the
new editor and the Drools engine now support **DMN 1.6**, the latest
specification from the Object Management Group (OMG). This ensures you're
working with current standards and can leverage the newest decision modeling
capabilities.
+
+## The Deprecation Journey: A Necessary Step Forward
+
+Change is never easy, especially when it involves tools that teams have relied
on for years. The deprecation of the classic editors didn't happen overnight;
it was a carefully planned transition:
+
+- **10.0.0 (December 2024)**: Classic editors marked as deprecated, warnings
added
+- **10.1.0 (July 2025)**: New Test Scenario Editor introduced
Review Comment:
@kbowers-ibm When we introduced the new DMN Editor? I would mention that.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
