You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@kie.apache.org by ti...@apache.org on 2026/08/17 15:37:40 UTC
(incubator-kie-website) 01/01: Revert website to the state of d3e9133
This is an automated email from the ASF dual-hosted git repository.
tiagobento pushed a commit to branch revert-to-d3e9133
in repository https://gitbox.apache.org/repos/asf/incubator-kie-website.git
commit f62cbc54462dba8e68b4fc3468f40aebbf5a0e22
Author: Tiago Bento <ti...@gmail.com>
AuthorDate: Mon Aug 17 11:37:09 2026 -0400
Revert website to the state of d3e9133
Reverts the following commits, restoring the tree exactly as it was at
d3e9133 ("Home page, navbar, footer, and site-wide styling refresh (#58)"):
1529ca8 Add DRL chapter, correct jBPM pages, and rework component taglines
57836e8 Polish overview pages: drop Learn more sections, link components, prefer JDK 21
0b7cd6c Give Tools its own docs section and retire /components
7c341d5 Give SonataFlow its own docs section at /sonataflow
74fce52 Give Kogito its own docs section at /kogito
702652c Give jBPM its own docs section at /jbpm
bcd9e3f Give OptaPlanner its own docs section at /optaplanner
c79965a Give Drools its own docs section at /drools
1d4fc3f Show an Apache KIE / <component> lockup in the navbar
Co-Authored-By: Claude Opus 5 (1M context) <no...@anthropic.com>
---
docs/about/components.md | 20 +-
docs/components/drools/_category_.json | 6 +
docs/components/drools/books.mdx | 74 +++++++
...Business-Rule-Engines-for-Excel-Power-Users.jpg | Bin
.../drools/books/DroolsTechnicalGuide.png | Bin
.../drools/books/Mastering-JBOSS-Drools-6.png | Bin
docs/components/drools/dmn.mdx | 52 +++++
.../img => docs/components}/drools/dmn/DMNBPMN.png | Bin
.../components}/drools/dmn/DMNBoxed.png | Bin
.../img => docs/components}/drools/dmn/DMNDRG.png | Bin
.../img => docs/components}/drools/dmn/DMNDT.png | Bin
.../img => docs/components}/drools/dmn/DMNTCK.png | Bin
.../drools-dmn-engine-historical-milestones.png | Bin 0 -> 150731 bytes
docs/components/drools/drools.md | 9 +
docs/components/drools/papers.mdx | 228 ++++++++++++++++++++
.../drools/upgrade_recipe.mdx} | 10 +-
docs/components/drools/videos.mdx | 40 ++++
docs/components/jbpm/_category_.json | 6 +
.../jbpm/efficient_business_process_management.png | Bin
.../jbpm/getting_started/getting_started.md | 97 +++++++++
docs/components/jbpm/jbpm.md | 73 +++++++
.../components}/jbpm/jbpm5_developer_guide.png | Bin
.../components}/jbpm/jbpm6_developer_guide.png | Bin
.../components}/jbpm/mastering_jbpm6.png | Bin
docs/components/kogito/_category_.json | 6 +
docs/components/kogito/kogito.md | 30 +++
docs/components/optaplanner/_category_.json | 6 +
docs/components/optaplanner/optaplanner.md | 92 ++++++++
docs/components/sonataflow/_category_.json | 6 +
.../sonataflow/sonataflow.md} | 13 +-
docs/components/tools/_category_.json | 6 +
docs/components/tools/tools.md | 17 ++
docs/drools/books.md | 46 ----
docs/drools/dmn.mdx | 83 --------
docs/drools/drl.mdx | 187 ----------------
docs/drools/drools.mdx | 37 ----
docs/drools/get-started.md | 33 ---
docs/drools/papers.md | 237 ---------------------
docs/drools/videos.md | 44 ----
docs/jbpm/books.md | 44 ----
docs/jbpm/get-started.md | 36 ----
docs/jbpm/jbpm.mdx | 44 ----
docs/jbpm/what-is-jbpm.md | 44 ----
docs/kogito/get-started.md | 30 ---
docs/kogito/guides.md | 101 ---------
docs/kogito/kogito.mdx | 19 --
docs/optaplanner/code-example.md | 24 ---
docs/optaplanner/compatibility.md | 24 ---
docs/optaplanner/get-started.md | 27 ---
docs/optaplanner/how-it-works.md | 26 ---
docs/optaplanner/optaplanner.mdx | 37 ----
docs/optaplanner/use-cases.md | 18 --
docs/sonataflow/get-started.md | 23 --
docs/sonataflow/sonataflow.mdx | 42 ----
docs/tools/chrome.md | 20 --
docs/tools/consoles.md | 12 --
docs/tools/editors.md | 12 --
docs/tools/get-started.md | 28 ---
docs/tools/kie-sandbox.md | 15 --
docs/tools/tools.mdx | 41 ----
docs/tools/vscode.md | 39 ----
docusaurus.config.ts | 55 +----
sidebars.ts | 7 +-
src/componentSections.ts | 79 -------
src/components/ComponentBanner/index.tsx | 98 ---------
src/components/ComponentBanner/styles.module.css | 130 -----------
src/components/KogitoHighlights/index.tsx | 112 ----------
src/components/KogitoHighlights/styles.module.css | 9 -
src/css/custom.css | 67 ------
src/pages/drools.tsx | 5 +
src/pages/jbpm.tsx | 5 +
src/pages/kogito.tsx | 5 +
src/pages/optaplanner.tsx | 5 +
src/pages/sonataflow.tsx | 5 +
src/pages/tools.tsx | 5 +
src/theme/DocBreadcrumbs/index.tsx | 135 ------------
src/theme/DocBreadcrumbs/styles.module.css | 7 -
src/theme/Navbar/Logo/index.tsx | 73 -------
src/theme/Navbar/Logo/styles.module.css | 63 ------
src/theme/Root.tsx | 49 +----
static/fonts/cinzel-latin-ext.woff2 | Bin 8344 -> 0 bytes
static/fonts/cinzel-latin.woff2 | Bin 15228 -> 0 bytes
static/img/kogito.svg | 2 +-
static/img/kogito/hero-background.svg | 12 --
static/img/kogito/homepage_graphic_1.png | Bin 5163 -> 0 bytes
static/img/kogito/homepage_graphic_1@2x.png | Bin 11258 -> 0 bytes
static/img/kogito/homepage_graphic_2.png | Bin 6054 -> 0 bytes
static/img/kogito/homepage_graphic_2@2x.png | Bin 12964 -> 0 bytes
static/img/kogito/homepage_graphic_3.png | Bin 6546 -> 0 bytes
static/img/kogito/homepage_graphic_3@2x.png | Bin 39303 -> 0 bytes
static/img/navbar-logo.svg | 2 +-
static/img/sonataflow.svg | 2 +-
92 files changed, 815 insertions(+), 2281 deletions(-)
diff --git a/docs/about/components.md b/docs/about/components.md
index e3ec35f..6ca37dc 100644
--- a/docs/about/components.md
+++ b/docs/about/components.md
@@ -7,32 +7,31 @@ sidebar_position: 1
The components that make up Apache KIE predate the umbrella by many years. Each
one stands on its own, and they are designed to work together.
-## [Drools](/drools)
+## Drools
The rule engine at the core of KIE. Started in 2001 as an open source rule
engine and grew into a full business rule management system, today covering DRL
-rules and the [DMN](https://www.omg.org/spec/DMN/) decision standard.
+rules and the DMN decision standard.
-## [OptaPlanner](/optaplanner)
+## OptaPlanner
A constraint solver for planning problems — scheduling, routing, rostering and
the like. It began in 2006 as Drools Planner before becoming a project in its
own right.
-## [jBPM](/jbpm)
+## jBPM
-A workflow engine for long-running business processes, covering
-[BPMN 2.0](https://www.omg.org/spec/BPMN/2.0/), case management and human
-tasks. From jBPM 5 onwards it was rebuilt around the same
+A workflow engine for long-running business processes, covering BPMN, case
+management and human tasks. From jBPM 5 onwards it was rebuilt around the same
knowledge core as Drools.
-## [Kogito](/kogito)
+## Kogito
The cloud-native generation of the engines, announced in 2019. It builds on
Quarkus and code generation to run rules, decisions and processes as
microservices.
-## [SonataFlow](/sonataflow)
+## SonataFlow
A workflow engine for building serverless applications, implementing the
[CNCF Serverless Workflow](https://serverlessworkflow.io/) specification —
@@ -40,7 +39,7 @@ SonataFlow worked with
[version 0.8](https://github.com/serverlessworkflow/specification/tree/0.8.x).
It grew out of Kogito.
-## [Tools](/tools)
+## Tools
The editors, extensions and developer tooling used to author and run KIE assets.
@@ -54,3 +53,4 @@ years, some of which grew into projects of their own:
- [TrustyAI](https://github.com/trustyai-explainability), for explainability and
auditing of AI-augmented decision services, which continues as an independent
open source project.
+- SonataFlow, which grew out of Kogito.
diff --git a/docs/components/drools/_category_.json b/docs/components/drools/_category_.json
new file mode 100644
index 0000000..00edc95
--- /dev/null
+++ b/docs/components/drools/_category_.json
@@ -0,0 +1,6 @@
+{
+ "label": "Drools",
+ "position": 1,
+ "collapsible": false,
+ "collapsed": false
+}
diff --git a/docs/components/drools/books.mdx b/docs/components/drools/books.mdx
new file mode 100644
index 0000000..4170d0e
--- /dev/null
+++ b/docs/components/drools/books.mdx
@@ -0,0 +1,74 @@
+---
+id: drools_books
+title: Books
+sidebar_position: 1
+---
+
+# Books
+
+## Drools Books
+
+[](https://www.packtpub.com/product/ai-and-business-rule-engines-for-excel-power-users/9781804619544)
+
+**Business Rule Engines and AI for Excel Power Users: Capture and scale your business knowledge into the cloud – with Microsoft 365, Decision Models, and AI tools from IBM and Red Hat**
+* Paul Browne
+* ISBN: 9781804619544
+
+[](https://item.jd.com/10038443959313.html)
+
+**The first Chinese book on Drools in China mainly includes basic knowledge, intermediate and advanced grammar, as well as practical cases. It is applicable to programmers and technology enthusiasts of all levels.**
+* ZhiHui Lai(来志辉)
+* ISBN：9787301305492
+
+[](https://www.packtpub.com/en-us/product/mastering-jboss-drools-6-9781783288632)
+
+## Related Books
+
+**Jess in Action: Java Rule-based Systems**
+* Ernest Friedman-Hill
+* ISBN: 1930110898
+
+**Expert Systems: Principles and Programming**
+* Joseph Giarratano, Gary D. Riley
+* ISBN: 0534384471
+
+**Introduction to Expert Systems**
+* Peter Jackson
+* ISBN: 0201876868
+
+**Smart Enough Systems**
+* James Taylor, Neil Raden
+* Print ISBN-10: 0-13-234796-2
+* Print ISBN-13: 978-0-13-234796-9
+
+**Business Rules and Information Systems: Aligning IT with Business Goals**
+* Tony Morgan
+* ISBN: 0201743914
+
+**Principles of the Business Rule Approach**
+* Ronald G. Ross
+* ISBN: 0201788934
+
+**Business Rules Applied**
+* Von Halle
+* ISBN: 0471412937
+
+**DMN Method and Style. 2nd Edition: A Business Pracitioner's Guide to Decision Modeling**
+* Bruce Silver
+* ISBN: 9780982368176
+
+**DMN Cookbook: 50 Decision Modeling Recipes to Accelerate Your Business Rules Projects with Trisotech, Red Hat, and Drools**
+* Bruce Silver, Edson Tirelli
+* ISBN: 9780982368183
+
+**DMN Method and Style: 3rd edition, with DMN Cookbook**
+* Bruce Silver
+* ISBN: 9798218313302 ([link](https://methodandstyle.com/dmn-method-and-style-3rd-edition-preface))
+
+**Knowledge Automation: How to Implement Decision Management in Business Processes**
+* Alan N. Fish
+* ISBN: 9781118236796
+
+**Real-World Decision Modeling with DMN: Effective Communication of Decision-Making - 2nd Edition Updated for DMN 1.5**
+* James Taylor, Jan Purchase
+* ISBN: 9798218234669
diff --git a/static/img/drools/books/AI-and-Business-Rule-Engines-for-Excel-Power-Users.jpg b/docs/components/drools/books/AI-and-Business-Rule-Engines-for-Excel-Power-Users.jpg
similarity index 100%
rename from static/img/drools/books/AI-and-Business-Rule-Engines-for-Excel-Power-Users.jpg
rename to docs/components/drools/books/AI-and-Business-Rule-Engines-for-Excel-Power-Users.jpg
diff --git a/static/img/drools/books/DroolsTechnicalGuide.png b/docs/components/drools/books/DroolsTechnicalGuide.png
similarity index 100%
rename from static/img/drools/books/DroolsTechnicalGuide.png
rename to docs/components/drools/books/DroolsTechnicalGuide.png
diff --git a/static/img/drools/books/Mastering-JBOSS-Drools-6.png b/docs/components/drools/books/Mastering-JBOSS-Drools-6.png
similarity index 100%
rename from static/img/drools/books/Mastering-JBOSS-Drools-6.png
rename to docs/components/drools/books/Mastering-JBOSS-Drools-6.png
diff --git a/docs/components/drools/dmn.mdx b/docs/components/drools/dmn.mdx
new file mode 100644
index 0000000..b9b9ffa
--- /dev/null
+++ b/docs/components/drools/dmn.mdx
@@ -0,0 +1,52 @@
+---
+id: drools_dmn
+title: DMN
+sidebar_position: 0
+---
+
+# DMN
+
+The Decision Model and Notation (DMN™) is a Standard by OMG® providing a common and visual notation readily understandable by all users and personas. With DMN, business analysts can define the initial decision requirements and then formalize more detailed decision models; technical developers can automate the decisions in any process with a portable execution semantic, while business stakeholders can manage and monitor those decisions.
+
+The official webpage of the DMN Standard specification is available at [OMG website](https://www.omg.org/dmn).
+Drools DMN engine is an open source Java™ implementation providing full runtime support for DMN models at Conformance level 3, meaning 100% of the features in the Standard.
+
+- [What is DMN? in 100 seconds](https://www.youtube.com/watch?v=rJyYvNk4QZs)
+
+## At a glance
+
+> DMN is trying to do for Business Decision Management what BPMN did for Business Process Management a decade ago: empower the business to take charge of the logic that drives its operations, through a vendor-independent diagramming language. To be effective, that language must be both usable by business analysts and stakeholders in the business and verifiable for completeness and consistency. DMN is both.
+>
+> — Bruce Silver, [What is DMN?](https://methodandstyle.com/what-is-dmn)
+
+
+
+Manage any decision complexity by decomposing and structuring decision services with Decision Requirement Graph (DRG).
+
+
+
+Model business logic with DMN Decision Table, an effective instrument understandable by all personas. Drools DMN engine performs static analysis of the DMN Decision Table to detect gaps, overlaps, and ensure the table rules follow industry best practices.
+
+
+
+Model more complex business logic with the power of all the FEEL Boxed Expression constructs made available by the DMN Standard specification.
+
+Integrate DMN with [BPMN](https://jbpm.org) and [CMMN](https://jbpm.org) to describe an executable and semantically defined business logic to be used in business processes.
+
+
+
+
+
+Drools DMN engine provides full runtime support for DMN models at Conformance level 3, meaning 100% of the features in the Standard.
+
+We contribute to the [DMN Technology Compatibility Kit (DMN TCK)](https://dmn-tck.github.io/tck), a community-led proposal for a verifiable and executable method to demonstrate the Conformance level of support provided by a vendor-supplied DMN implementation.
+
+
+
+## Resources
+
+Looking for a gentle introduction to the DMN standard? We have just the right crash course on DMN, freely available for you at [learn-dmn-in-15-minutes.com](http://learn-dmn-in-15-minutes.com).
+
+Drools DMN engine: the [DMN FEEL handbook](https://kiegroup.github.io/dmn-feel-handbook) is a vademecum for the FEEL expression language from the DMN specification, as also implemented by the Drools DMN open source engine.
+
+Drools documentation: [DMN support in Drools](pathname:///docs/10.0.x/drools/drools/DMN/index.html).
diff --git a/static/img/drools/dmn/DMNBPMN.png b/docs/components/drools/dmn/DMNBPMN.png
similarity index 100%
rename from static/img/drools/dmn/DMNBPMN.png
rename to docs/components/drools/dmn/DMNBPMN.png
diff --git a/static/img/drools/dmn/DMNBoxed.png b/docs/components/drools/dmn/DMNBoxed.png
similarity index 100%
rename from static/img/drools/dmn/DMNBoxed.png
rename to docs/components/drools/dmn/DMNBoxed.png
diff --git a/static/img/drools/dmn/DMNDRG.png b/docs/components/drools/dmn/DMNDRG.png
similarity index 100%
rename from static/img/drools/dmn/DMNDRG.png
rename to docs/components/drools/dmn/DMNDRG.png
diff --git a/static/img/drools/dmn/DMNDT.png b/docs/components/drools/dmn/DMNDT.png
similarity index 100%
rename from static/img/drools/dmn/DMNDT.png
rename to docs/components/drools/dmn/DMNDT.png
diff --git a/static/img/drools/dmn/DMNTCK.png b/docs/components/drools/dmn/DMNTCK.png
similarity index 100%
rename from static/img/drools/dmn/DMNTCK.png
rename to docs/components/drools/dmn/DMNTCK.png
diff --git a/docs/components/drools/dmn/drools-dmn-engine-historical-milestones.png b/docs/components/drools/dmn/drools-dmn-engine-historical-milestones.png
new file mode 100644
index 0000000..1f18794
Binary files /dev/null and b/docs/components/drools/dmn/drools-dmn-engine-historical-milestones.png differ
diff --git a/docs/components/drools/drools.md b/docs/components/drools/drools.md
new file mode 100644
index 0000000..6db5674
--- /dev/null
+++ b/docs/components/drools/drools.md
@@ -0,0 +1,9 @@
+---
+id: drools
+title: Drools
+sidebar_position: 0
+---
+
+# Drools
+
+Drools is a set of projects focusing on intelligent automation and decision management, most notably providing a forward-chaining and backward-chaining inference-based rule engine, DMN decisions engine and other projects. A rule engine is a fundamental building block to create an expert system which, in artificial intelligence, is a computer system that emulates the decision-making ability of a human expert.
diff --git a/docs/components/drools/papers.mdx b/docs/components/drools/papers.mdx
new file mode 100644
index 0000000..38c9ffa
--- /dev/null
+++ b/docs/components/drools/papers.mdx
@@ -0,0 +1,228 @@
+---
+id: drools_papers
+title: Papers
+sidebar_position: 1
+---
+
+# Papers
+
+*Rete: A fast algorithm for the many pattern/many object pattern match problem*
+* Author - Charles L. Forgy
+* Artificial Intelligence, Volume 19, Issue 1, September 1982, Pages 17-37
+
+*Production Matching for Large Learning Systems (Rete/UL)*
+* Author - Robert B. Doorenbos
+* PhD thesis, Carnegie Mellon University, January 31, 1995
+
+*The LEAPS Algorithms*
+* Author - Don Batory
+* Technical Report 94-28, Department of Computer Sciences, University of Texas at Austin, 1994
+
+*Putting BPMN and DMN to Work: a Pediatric Surgery Case Study*
+* Authors - Anna Maria Bianchi, Matteo Mortari, Claudio Pintavalle, Giuseppe Pozzi
+* Paper - 2021 IEEE International Conference on Digital Health (ICDH), 2021, pp. 154-159, doi: 10.1109/ICDH52753.2021.00028
+* [Paper URL](https://doi.org/10.1109/ICDH52753.2021.00028)
+* University - Politecnico di Milano, Italy
+
+*Modeling surgical pediatric processes with BPMN and DMN*
+* Author - Claudio Pintavalle
+* Supervisor - Anna Maria Bianchi
+* Co-Supervisor - Giuseppe Pozzi
+* Master’s degree thesis [URL](http://hdl.handle.net/10589/150128)
+* University - Politecnico di Milano, Italy
+
+*Application of Drools in network fault management system*
+* Authors - Ma Xiu-li, Wang Hong-xia, Zhang Ling-yun
+* Paper - Computer Engineering and Design, Vol. 30, No. 8 (2009/04/28)
+* [Paper URL](http://www.citeulike.org/user/mzygmunt/article/6482668)
+* University - University,Shenyang 110168,China
+
+*A Snort-based agent for a JADE multi-agent intrusion detection system*
+* Authors - Mosqueira-Rey, Alonso-Betanzos, Guijarro-Berdinas, Alonso-Rios, Lago-Pineiro
+* [Paper URL](http://www.ingentaconnect.com/content/ind/ijiids/2009/00000003/00000001/art00007)
+* University - Department of Computer Science, University of A Corufia, ESPAGNE
+
+*Achieving Rule Interoperability Using Chains of Model Transformations*
+* Authors - Marcos Didonet Del Fabro, Patrick Albert, Jean Bézivi, Frédéric Jouault
+* [Paper URL](http://www.springerlink.com/content/0174252285737q74/)
+* Paper ISBN - 978-3-642-02407-8
+
+*Implementing a Rule-Based Contract Compliance Checker*
+* Authors - Massimo Strano, Carlos Molina-Jimenez, Santosh Shrivastava
+* [Paper URL](http://www.cs.ncl.ac.uk/publications/trs/papers/1150.pdf)
+* Paper ISBN - 978-3-642-04279-9
+* University - Newcastle University, Newcastle upon Tyne, UK
+
+*Want to Know How to Play the Game? Ask the ORACLE!*
+* Authors - Paola Rizzo, Michael Kriege, Rui Figueiredo, MeiYii Lim and Ruth Aylett
+* Paper ISBN - 978-3-642-04379-6
+* [Paper URL](http://www.springerlink.com/content/855l02875w70221p/)
+* Universities - Interagens s.r.l., c/o ITech, Rome, Italy; Heriot-Watt University, Riccarton, Edinburgh, UK; INESC-ID, Porto Salvo, Portugal
+
+*Off-line Analysis Research and Implementation Based on Drools*
+* Authors - XIU Jie-lei XU Nan-shan WEI Sheng-jun
+* [Paper URL](http://en.cnki.com.cn/Article_en/CJFDTOTAL-WJSJ200903063.htm)
+* Universities - School of Information Science, Beijing University of Chemical Technology,Beijing, China; Laboratory of Computer Network Defense Technology, Beijing Institute of Technology,Beijing,China
+
+*An industry survey of autonomic infrastructure*
+* Authors - Michael Keith Nunez, Gary Mueller
+* [Paper URL](http://portal.acm.org/citation.cfm?id=1555312.1555316)
+* Paper ISBN - 978-1-60558-612-0
+* Organisation - Sun Microsystems, Inc. , Broomfield, CO, USA
+
+*An Automatically Composable OWL Reasoner for Resource Constrained Devices*
+* Authors - BRENNAN, ROB, O'SULLIVAN, DECLAN, KEENEY, JOHN
+* [Paper URL](http://www.tara.tcd.ie/handle/2262/38086)
+* University - Trinity College Dublin, Dublin 2, Ireland
+
+*Semi-automatic Composition of Geospatial Web Services Using JBoss Rules*
+* Authors - Raluca Zaharia (1) and Laurentiu Vasiliu (1) and Costin Badica (2)
+* (1) Digital Enterprise Research Institute, National University of Ireland, Galway, Ireland
+* (2) Software Engineering Department, University of Craiova, Romania
+* Keywords: Semantic Web Services, WSMO/L/X, ASM
+* [Paper URL](http://www.springerlink.com/content/j347l97t18137163/fulltext.pdf)
+
+*Building Machine Learning with Drools Reteoo (Red Hat sponsored research)*
+* Student - Gizil Oguz
+* Mentor - Viktor Kuncak
+* [Paper URL](http://infoscience.epfl.ch/record/126292/files/oguz-thesis_final.pdf)
+* University - Ecol Polytechnique Federale de Lausanne
+
+*Development of a Rich Client based GUI for Expert Systems* (in German)
+* Student - Dennis Huning
+* Mentor - Prof. Nikolaus Wulff
+* Bachelor Thesis [URL](http://www.lab4inf.fh-muenster.de/lab4inf/docs/thesis/BA_DHuning.pdf)
+* University - University of Applied Sciences, Fachhochschule Muenster, Germany
+
+*Reasoning with Uncertainty in Drools*
+* Student - Davide Sottara
+* Mentor - Prof. Paola Mello
+* Paper - Adding Uncertainty to Rete-OO engines (To be published)
+* University - DEIS, Faculty of Engineering, University of Bologna
+
+*Program, Enhance Thyself! Demand-Driven Pattern-Oriented Program Enhancement*
+* Student - Eli Tilevich
+* Mentor - Godmar Back
+* Paper ISBN - ISBN:978-1-60558-044-9
+* [Paper URL](http://portal.acm.org/citation.cfm?id=1353482.1353485&coll=GUIDE&dl=GUIDE&CFID=1526005&CFTOKEN=47419151)
+* University - Virginia Tech
+
+*Can URML model successfully Drools rules?*
+* Student: Emilian Pascalau
+* Mentor: Dr Adrian Giurca
+* Paper ISBN: 978-960-6843-02-0
+* [Paper URL](http://www.informatik.tu-cottbus.de/~agiurca/papers/RuleApps2008.pdf)
+* University - Brandenburg University of Technology
+
+*Knowledge-based Desing Pattern for Detailed Steel Structural Design*
+* Student: Michael Zimmermann
+* Mentor - Prof. Dr. Robert Bronsart
+* Phd Thesis
+** work in progress
+** for a short summary, see [URL](http://blog.athico.com/2008/09/improving-naval-engineering-process.html))
+* University - University of Rostock, Chair of Naval Architecture
+
+*Policy-driven middleware*
+* Student - Kris Verlaenen
+* Mentor - Prof. Dr. ir. W. Joosen
+* Phd dissertation - K. Verlaenen, Middleware for advanced service configuration: a policy-based approach. March 2008.
+* University - Katholieke Universiteit Leuven
+
+*Solving Patient Admission Scheduling problem with Drools Solver and Constraint Solver Library*
+* Student - Wim Van Croonenburg
+* Mentor - Peter Demeester
+* University - Katholieke Hogeschool Sint-Lieven Gent
+
+*Knowledge Representation in Services Oriented Architecture*
+* Student - Piotr Grobelny
+* Mentor - >
+* [Paper URL](http://www.astec.net/brochure/Paper_KNWS2008_Piotr_Grobelny.pdf)
+* University - University of Zielona Gora, Faculty of Electrical Engineering, Computer Science and Telecommunications
+
+*Runtime Evolution for Online Gaming: A Case Study using JBoss and Drools*
+* Student - Lei Zhu
+* Mentor - Graham Morgan
+* [Paper URL](http://homepages.cs.ncl.ac.uk/lei.zhu1/source/leiZhuGDTW08.pdf)
+* University - University of Newcastle, School of Computing Science
+
+*Time to the Rescue - Supporting Temporal Reasoning in the Rete Algorithm for Complex Event Processing*
+* Authors - Karen Walzer, Matthias Groch1 and Tino Breddin
+* Paper ISBN - 978-3-540-85653-5
+* [Paper URL](http://www.springerlink.com/content/303241m22n52g0g2/)
+
+*Combat SystemApplication of Change-Tolerant Technology: Using Rules Engine for Decision Automation*
+* Authors - Catherine L. Payne, Mark E. Schmid, Barbara A. Shapter, and Brian T. Taylor
+* [Papers URL](http://member.navalengineers.org/SiteCollectionDocuments/2008%20Proceedings%20Documents%20%28Papers%20and%20Presentations%29/ASNE%20Day%202008/paper7.pdf)
+* Organisation - Naval Engineers
+
+*A Knowledge Authoring Tool for Clinical Decision Support*
+* Authors - Dustin Dunsmuir, Jeremy Daniels, Christopher Brouse, Simon Ford and J. Mark Ansermino
+* [Paper URL](http://www.springerlink.com/content/03246251j36pn6q2/)
+* University - The University of British Columbia, Vancouver, Canada
+
+*JSON Rules*
+* Authors - A Giurca, E Pascalau, G Kaiserslautern
+* [Paper URL](http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.142.6370&rep=rep1&type=pdf#page=15)
+* Organisation -31st German Conference on Artificial Intelligence
+
+*Advances in Autonomic Components & Services*
+
+* Authors - Marco Aldinucci, Marco Danelutto, Giorgio Zoppi and Peter Kilpatrick
+* [Paper URL](http://www.springerlink.com/content/m0k7562u0v043610/)
+* Paper ISBN - 978-0-387-09454-0 (Print) 978-0-387-09455-7 (Online)
+* Universities - Dept. Computer Science, University of Pisa, Pisa, IT; Dept. Computer Science, Queen's University Belfast, UK
+
+*Integrating flaw-response modelling tools used for inspection qualification into a Multi-Agent System software platform*
+* Authors - J P McKenna, N McLean, A Gachagan1, S D J McArthur, G Hayward
+* [Paper URL](http://www.atypon-link.com/BINT/doi/abs/10.1784/insi.2008.50.2.70)
+* University - University of Strathclyde, Glasgow
+
+*Mobile and Stationary Sensors for Local Surveillance: System Architecture and Applications*
+* Authors - Sandro Leuchter, Thomas Partmann and Lothar Berger
+* [Paper URL](http://www.springerlink.com/content/l62048u947n69735/)
+* Paper ISBN - 978-3-540-89899-3
+* University - Fraunhofer Institute for Information and Data Processing
+
+*Behavioural Skeletons Meeting Services*
+* Authors - M. Danelutto and G. Zoppi
+* [Paper URL](http://www.springerlink.com/content/m186g31118144078/)
+* Paper ISBN - 978-3-540-69383-3
+* Universities - Dept. Computer Science, Univ. Pisa; CoreGRID Programming Model Institute,
+
+*An Intelligent Plot-Centric Interface for Mastering Computer Role-Playing Games*
+* Authors - Carlos León, Federico Peinado, Álvaro Navarro and Héctor Cortiguera
+* [Paper URL](http://www.springerlink.com/content/a371722747m4u652/)
+* Paper ISBN - 978-3-540-89424-7
+* University - Departamento de Ingeniería del Software e Inteligencia Artificial, Universidad Complutense de Madrid, Spain
+
+*Design and realization of rule-based workflow task assignment system*
+* Authors - Li, Chun-Fang | Tan, Qing-Ping | Xu, Jian-Jun | Xiao, Xiao-Li
+* [Paper URL](http://md1.csa.com/partners/viewrecord.php?requester=gs&collection=TRD&recid=200902900014604CI&q=drools+OR+%22jboss+rules%22&uid=789178026&setcookie=yes)
+* Organisation - Jisuanji Gongcheng yu Sheji (Computer Engineering and Design). Vol. 29, no. 21, pp. 5572-5575. Nov. 2008
+
+*Arriclides: An architecture integrating clinical decision support models*
+* Student - Kris Verlaenen
+* Mentor - Prof. Dr. ir. W. Joosen
+* Published Paper - K. Verlaenen, W. Joosen, and P. Verbaeten. Arriclides: An architecture integrating clinical decision support models. In Proceedings of the 40th Annual Hawaii International Conference on System Sciences, January 2007.
+* University - Katholieke Universiteit Leuven
+
+*Towards simplified policy specification and reasoning*
+* Student - Kris Verlaenen
+* Mentor - Prof. Dr. ir. W. Joosen
+* Published Paper - K. Verlaenen, B. De Win, and W. Joosen. Towards simplified specification of policies in different domains. In Proceedings of the 10th Symposium on Integrated Network Management, May 2007.
+* Published Paper - K. Verlaenen, B. De Win, and W. Joosen. Policy analysis using a hybrid semantic reasoning engine. In Proceedings of the 8th International Workshop on Policies for Distributed Systems and Networks, June 2007.
+* University - Katholieke Universiteit Leuven
+
+*On Interchange between JBoss Rules and Jess*
+* Student: Oana Nicolae
+* Mentor: Dr Adrian Giurca
+* Paper ISBN: 978-3-540-74929-5
+* [Paper URL](http://www.springer.com/cda/content/document/cda_downloaddocument/9783540749295-t1.pdf)
+* University - Brandenburg University of Technology
+
+*Sharing rules between JBoss Rules and Jena*
+* Student - Oana Nicolae, Mircea Diaconescu,
+* Mentor: Dr. Adrian Giurca, Prof. Gerd Wagner
+* Paper ISBN: 0-7695-3078-8
+* [Paper URL](http://csdl.computer.org/dl/proceedings/synasc/2007/3078/00/30780105.pdf)
+* University - Brandenburg University of Technology
diff --git a/docs/drools/upgrade-recipe.mdx b/docs/components/drools/upgrade_recipe.mdx
similarity index 97%
rename from docs/drools/upgrade-recipe.mdx
rename to docs/components/drools/upgrade_recipe.mdx
index a189a81..4662421 100644
--- a/docs/drools/upgrade-recipe.mdx
+++ b/docs/components/drools/upgrade_recipe.mdx
@@ -1,14 +1,14 @@
---
-id: upgrade-recipe
-title: Upgrade recipe
-sidebar_position: 7
+id: drools_upgrade_recipe
+title: Upgrade Recipe
+sidebar_position: 100
---
-## Upgrade to 10+
+# Upgrade recipe
For migration to 10.0.0 or later, please refer to the [Migration Guide](pathname:///docs/10.0.x/drools/drools/migration-guide/index.html).
-## Upgrade recipe 7.0
+# Upgrade recipe 7.0
**KIE public API classes are backwards compatible** (per series), but users often also use implementation classes (which are documented in the reference manual too). This upgrade recipe _minimizes the pain_ to upgrade your code.
diff --git a/docs/components/drools/videos.mdx b/docs/components/drools/videos.mdx
new file mode 100644
index 0000000..a78c339
--- /dev/null
+++ b/docs/components/drools/videos.mdx
@@ -0,0 +1,40 @@
+---
+id: drools_videos
+title: Videos
+sidebar_position: 1
+---
+
+# Videos
+
+For general KIE community videos, playlists, and live streams, see the [Videos page under Community](/community/videos).
+
+## Drools: DMN Engine
+A collection of presentations covering the DMN open source engine of Drools.
+
+- [Drools DMN Engine presentations playlist](https://www.youtube.com/playlist?list=PLdbdefeRIj9RW_bWDmx17oXzKshu-4T9H)
+
+## Video archive
+See [Mark Proctor’s playlist on YouTube for KIE Workbench](https://www.youtube.com/playlist?list=PLb9jQNHBKBRj9IJkc_F5nCJAvXaegOGW8).
+
+- [KIE Workbench Installation and Setup (Full Screen 720HD)](http://youtu.be/vj3MNmiUnvY?list=PLb9jQNHBKBRj9IJkc_F5nCJAvXaegOGW8)
+- [Authoring Perspective - Project Explorer (Full Screen 720HD)](http://youtu.be/EX5Kmdqqi_Q?list=PLb9jQNHBKBRj9IJkc_F5nCJAvXaegOGW8)
+- [Authoring Perspective - Window System (Full Screen 720HD)](http://youtu.be/Xu2q5iq2eGc?list=PLb9jQNHBKBRj9IJkc_F5nCJAvXaegOGW8)
+- [Authoring Perspective - Problems and Versioning (Full Screen 720HD)](http://youtu.be/550pFOYIOKk?list=PLb9jQNHBKBRj9IJkc_F5nCJAvXaegOGW8)
+- [Project Editor and Deployment Perspective (Full Screen 720HD)](http://youtu.be/FKVFkRHLGjQ?list=PLb9jQNHBKBRj9IJkc_F5nCJAvXaegOGW8)
+- [Organization Unit and Repository Administration Perspective (Full Screen 720HD)](http://youtu.be/Owb_cj7JgGQ?list=PLb9jQNHBKBRj9IJkc_F5nCJAvXaegOGW8)
+
+See [Mark Proctor’s playlist on YouTube for Drools Editor Metaphors](https://www.youtube.com/playlist?list=PLb9jQNHBKBRipbtadRC-UaUObjwp0aBHJ).
+
+- [Create a Project (Full Screen 720HD)](http://youtu.be/zYZs8NsC3BA?list=PLb9jQNHBKBRipbtadRC-UaUObjwp0aBHJ)
+- [Create a Model (Full Screen 720HD)](http://youtu.be/R4KsdsyqGdo?list=PLb9jQNHBKBRipbtadRC-UaUObjwp0aBHJ)
+- [Limited Entry Guided Decision (Full Screen 720HD)](http://youtu.be/RbUDpXhW8pk?list=PLb9jQNHBKBRipbtadRC-UaUObjwp0aBHJ)
+- [Extended Entry Guided Decision Table (Full Screen 720HD)](http://youtu.be/6_eSg0h-yeg?list=PLb9jQNHBKBRipbtadRC-UaUObjwp0aBHJ)
+- [Rule Template (Full Screen 720HD)](http://youtu.be/gnKSX61X9yA?list=PLb9jQNHBKBRipbtadRC-UaUObjwp0aBHJ)
+- [Rule Fragment in Guided Decision Table (Full Screen 720HD)](http://youtu.be/DNXZmFnvvYA?list=PLb9jQNHBKBRipbtadRC-UaUObjwp0aBHJ)
+- [Score Cards (Full Screen 720HD)](http://youtu.be/xFLlgtBMTDY?list=PLb9jQNHBKBRipbtadRC-UaUObjwp0aBHJ)
+
+### Other videos
+- [Backward Chaining with Drools](http://youtu.be/fCjIRVSRFvA)
+- [Space Invaders in 8 minutes with Drools](http://youtu.be/wORlAZoxtA)
+- [Build a Graphical Adventure Game in 20 minutes using JBoss Drools : All Hail the Wumpus](http://youtu.be/4CvjKqUOEzM)
+- [Adventure In Prolog (swf)](http://downloads.jboss.org/drools/videos/text-adventures.swf)
diff --git a/docs/components/jbpm/_category_.json b/docs/components/jbpm/_category_.json
new file mode 100644
index 0000000..dabc702
--- /dev/null
+++ b/docs/components/jbpm/_category_.json
@@ -0,0 +1,6 @@
+{
+ "label": "jBPM",
+ "position": 2,
+ "collapsible": false,
+ "collapsed": false
+}
diff --git a/static/img/jbpm/efficient_business_process_management.png b/docs/components/jbpm/efficient_business_process_management.png
similarity index 100%
rename from static/img/jbpm/efficient_business_process_management.png
rename to docs/components/jbpm/efficient_business_process_management.png
diff --git a/docs/components/jbpm/getting_started/getting_started.md b/docs/components/jbpm/getting_started/getting_started.md
new file mode 100644
index 0000000..0d57c8c
--- /dev/null
+++ b/docs/components/jbpm/getting_started/getting_started.md
@@ -0,0 +1,97 @@
+---
+id: jbpm_getting_started
+title: Getting Started
+sidebar_position: 0
+---
+
+# Business Applications - Getting Started
+## Overview
+
+Business application can be defined as an automated solution, built with selected frameworks and capabilities that implements business functions and/or business problems. Capabilities can be (among others):
+
+* persistence
+* messaging
+* transactions
+* business processes, business rules
+* planning solutions
+
+Business application is more of a logical grouping of individual services that represent certain business capabilities. Usually they are deployed separately and can also be versioned individually. Overall goal is that the complete business application will allow particular domain to achieve their business goals e.g. order management, accommodation management, etc.
+Business application is
+
+* Build on any runtime
+* Deployable to cloud with just single command
+* UI agnostic (doesn’t enforce any UI frameworks and let users to make their own choice)
+* Configurable database profiles
+* Generated
+
+Business application consists of (though are not restricted to have only one of each project types)
+
+* data model project - shared data model between business assets and service
+* business assets (kjar) project - easily importable into workbench
+* service project - actual service with various capabilities
+
+**Service project** is the one that is deployable but will in most of the cases include business assets and data model projects.
+
+**Data model project** represents the common data structures that will be shared between service implementation and business assets. That enables proper encapsulation and promotes reuse and at the same time reduces shortcuts to make data model classes something more than they are - include too much of implementation into data models.
+
+**Business assets project** represents your business logic as processes, cases, rules, decision tables and more.
+
+Following are the maven archetype commands need to be used to generate different types of projects:
+
+* Data model archetype
+
+ ```
+ mvn archetype:generate -B -DarchetypeGroupId=org.kie -DarchetypeArtifactId=kie-model-archetype -DarchetypeVersion=7.74.1.Final -DgroupId=com.company -DartifactId=business-application-model -Dversion=1.0-SNAPSHOT -Dpackage=com.company.model
+ ```
+This command creates a project which generates business-application-model-1.0-SNAPSHOT.jar
+
+* Business assets project archetype
+
+ ```
+ mvn archetype:generate -B -DarchetypeGroupId=org.kie -DarchetypeArtifactId=kie-kjar-archetype -DarchetypeVersion=7.74.1.Final -DgroupId=com.company -DartifactId=business-application-kjar -Dversion=1.0-SNAPSHOT -Dpackage=com.company
+ ```
+This command creates a project which generates business-application-kjar-1.0-SNAPSHOT.jar
+
+* Dynamic assets project archetype
+
+ ```
+ mvn archetype:generate -B -DarchetypeGroupId=org.kie -DarchetypeArtifactId=kie-kjar-archetype -DarchetypeVersion=7.74.1.Final -DcaseProject=true -DgroupId=com.company -DartifactId=business-application-kjar -Dversion=1.0-SNAPSHOT -Dpackage=com.company
+ ```
+This command creates a project which generates business-application-kjar-1.0-SNAPSHOT.jar
+
+Service project archetype can be used based on the capabilities that are needed in the project. Capabilities essentially define the features that your business application will be equipped with. Available options are:
+
+* Business automation(bpm) covers features for process management, case management, decision management and optimization. These will be by default configured in the service project of your business application. Although you can turn them off via configuration.
+
+ ```
+ mvn archetype:generate -B -DarchetypeGroupId=org.kie -DarchetypeArtifactId=kie-service-spring-boot-archetype -DarchetypeVersion=7.74.1.Final -DgroupId=com.company -DartifactId=business-application-service -Dversion=1.0-SNAPSHOT -Dpackage=com.company.service -DappType=bpm
+ ```
+* Decision management(brm) covers mainly decision and rules related features (backed by Drools project)
+
+ ```
+ mvn archetype:generate -B -DarchetypeGroupId=org.kie -DarchetypeArtifactId=kie-service-spring-boot-archetype -DarchetypeVersion=7.74.1.Final -DgroupId=com.company -DartifactId=business-application-service -Dversion=1.0-SNAPSHOT -Dpackage=com.company.service -DappType=brm
+ ```
+* Business optimization(planner) covers planning problems and solutions related features (backed by OptaPlanner project)
+
+ ```
+ mvn archetype:generate -B -DarchetypeGroupId=org.kie -DarchetypeArtifactId=kie-service-spring-boot-archetype -DarchetypeVersion=7.74.1.Final -DgroupId=com.company -DartifactId=business-application-service -Dversion=1.0-SNAPSHOT -Dpackage=com.company.service -DappType=planner
+ ```
+These commands create a project which generates business-application-service-1.0-SNAPSHOT.jar
+
+## Build your first Business Application
+
+To build your first business application,use the above mentioned maven archetype commands to generate a Data project,Business assets project and a Service project with desired capabilities.
+
+It is recommended to generate all the three types of projects Data Model, Business assets and Service projects using the archetypes in same directory on your computer.
+
+Once you have the application on your computer just follow these steps to have it up and running
+
+* go to directory suffixed with -service
+* execute ```./launch.sh clean install``` for unix or ```launch.bat clean install``` for windows
+* once the boot has finished go to http://localhost:8090
+
+## More examples
+[Go to examples repository](https://github.com/business-applications)
+
+
+
diff --git a/docs/components/jbpm/jbpm.md b/docs/components/jbpm/jbpm.md
new file mode 100644
index 0000000..43bc946
--- /dev/null
+++ b/docs/components/jbpm/jbpm.md
@@ -0,0 +1,73 @@
+---
+id: jbpm
+title: jBPM
+sidebar_position: 0
+---
+
+# jBPM
+
+
+
+## What is jBPM?
+
+jBPM is a toolkit for building business applications to help automate business processes and decisions.
+
+jBPM originates from BPM (Business Process Management) but it has evolved to enable users to pick their own path in business automation. It provides various capabilities that simplify and externalize business logic into reusable assets such as cases, processes, decision tables and more.
+
+* business processes (BPMN2)
+* case management (BPMN2 and CMMN)
+* decision management (DMN)
+* business rules (DRL)
+* business optimisation (Solver)
+
+jBPM can be used as standalone service or embedded in custom service. It does not mandate any of the frameworks to be used, it can be successfully used in
+
+* traditional JEE applications - war/ear deployments
+* SpringBoot or Thorntail (formerly known as WildFly Swarm) - uberjar deployments
+* standalone Java programs
+
+jBPM is typically used to build business applications. A business application could be defined as a domain-specific solution (built with selected frameworks and capabilities) that solves a particular business problem. To implement the business logic it leverages capabilities from various frameworks like business processes, business rules and planning constraints, but also persistence, messaging, transactions, etc.
+
+jBPM is open source software, released under the Apache License 2.0. It is written in 100% pure Java™, runs on any JVM and is available in the Maven Central repository too.
+
+## Cloud-native?
+
+Looking for a pure cloud-native process automation solution, specifically targeted towards creating intelligent business applications in the cloud? Take a look at [Kogito](/components/kogito), based on jBPM.
+
+
+## What does jBPM do?
+
+A business process allows you to model your business goals by describing the steps that need to be executed to achieve that goal and the order, using a flow chart. This greatly improves the visibility and agility of your business logic, results in higher-level and domain-specific representations that can be understood by business users and is easier to monitor.
+
+The core of jBPM is a light-weight, extensible workflow engine written in pure Java that allows you to execute business processes using the latest BPMN 2.0 specification. It can run in any Java environment, embedded in your application or as a service.
+
+On top of the core engine, a lot of features and tools are offered to support business processes throughout their entire life cycle:
+
+* Eclipse-based and web-based editor to support the graphical creation of your business processes and case definitions (drag & drop).
+* Pluggable persistence and transactions based on JPA / JTA.
+* Pluggable human task service based on WS-HumanTask for including tasks that need to be performed by human actors.
+* Management console supporting process instance management, task lists and task form management, and reporting.
+* Optional process repository to deploy your process (and other related knowledge).
+* History logging (for querying / monitoring / analysis).
+* Integration with various frameworks such as CDI/EJB, Spring(Boot), OSGi, etc.
+
+BPM makes the bridge between business analysts, developers and end users, by offering process management features and tools in a way that both business users and developers like it. Domain-specific nodes can be plugged into the palette, making the processes more easily understood by business users.
+
+jBPM supports adaptive and dynamic processes that require flexibility to model complex, real-life situations that cannot easily be described using a rigid process. We bring control back to the end users by allowing them to control which parts of the process should be executed, to dynamically deviate from the process, etc.
+
+jBPM is also not just an isolated process engine. Complex business logic can be modeled as a combination of business processes with business rules and complex event processing. jBPM can be combined with the Drools project to support one unified environment that integrates these paradigms where you model your business logic as a combination of processes, rules and events.
+
+## Documentation
+Please refer to [Documentation](/documentation) for the latest features.
+
+## Slides
+These slides are viewable in your browser:
+
+[Show the jBPM presentations](http://www.slideshare.net/krisverlaenen/presentations)
+
+
+## Books
+[](http://kverlaen.blogspot.be/2015/07/book-mastering-jbpm6.html)
+[](http://kverlaen.blogspot.be/2014/09/jbpm6-developer-guide.html)
+[](http://kverlaen.blogspot.be/2012/12/book-jbpm5-developer-guide.html)
+[](http://www.schabell.org/2018/03/book-launced-effective-business-process-management-with-jboss-bpm.html)
diff --git a/static/img/jbpm/jbpm5_developer_guide.png b/docs/components/jbpm/jbpm5_developer_guide.png
similarity index 100%
rename from static/img/jbpm/jbpm5_developer_guide.png
rename to docs/components/jbpm/jbpm5_developer_guide.png
diff --git a/static/img/jbpm/jbpm6_developer_guide.png b/docs/components/jbpm/jbpm6_developer_guide.png
similarity index 100%
rename from static/img/jbpm/jbpm6_developer_guide.png
rename to docs/components/jbpm/jbpm6_developer_guide.png
diff --git a/static/img/jbpm/mastering_jbpm6.png b/docs/components/jbpm/mastering_jbpm6.png
similarity index 100%
rename from static/img/jbpm/mastering_jbpm6.png
rename to docs/components/jbpm/mastering_jbpm6.png
diff --git a/docs/components/kogito/_category_.json b/docs/components/kogito/_category_.json
new file mode 100644
index 0000000..2405d71
--- /dev/null
+++ b/docs/components/kogito/_category_.json
@@ -0,0 +1,6 @@
+{
+ "label": "Kogito",
+ "position": 5,
+ "collapsible": false,
+ "collapsed": false
+}
diff --git a/docs/components/kogito/kogito.md b/docs/components/kogito/kogito.md
new file mode 100644
index 0000000..819d2e5
--- /dev/null
+++ b/docs/components/kogito/kogito.md
@@ -0,0 +1,30 @@
+---
+id: kogito
+title: Kogito
+sidebar_position: 6
+---
+
+# Kogito
+Cloud-native business automation for building intelligent applications, backed by battle-tested capabilities.
+
+
+# Kogito ergo cloud
+Kogito (powered by jBPM) is designed from ground up to run at scale on cloud infrastructure. If you think about business automation think about the cloud as this is where your business logic lives these days. By taking advantage of the latest technologies (Quarkus, knative, etc.), you get amazingly fast boot times and instant scaling on orchestration platforms like Kubernetes.
+
+
+# Kogito ergo domain
+Kogito adapts to your business domain rather than the other way around. No more leaking abstraction of the tool into your client applications. Stay focused on what the business is about instead of being concerned with technology behind it.
+
+# Kogito ergo power
+Kogito offers a powerful developer experience based on battle-tested components. Achieve instant developer efficiency by having:
+
+* Tooling embeddable wherever you need it
+* Code generation taking care of 80% of the work
+* Flexibility to customize, only use what you need
+* Simplified local development with live reload
+
+# Examples
+Kogito can be used in many ways, so to help you get started, we provide a wide range of examples demonstrating from simple hello world to more advanced use cases using DMN, BPMN, KNative, Serverless Workflow and more. Head to Kogito examples repository in GitHub and start exploring. The team is constantly updating this repository with new and exciting features as they are added to Kogito.
+
+# Documentation
+Please refer to [Documentation](/documentation) for the latest walk through examples and documentation.
diff --git a/docs/components/optaplanner/_category_.json b/docs/components/optaplanner/_category_.json
new file mode 100644
index 0000000..6d8ba79
--- /dev/null
+++ b/docs/components/optaplanner/_category_.json
@@ -0,0 +1,6 @@
+{
+ "label": "OptaPlanner",
+ "position": 4,
+ "collapsible": false,
+ "collapsed": false
+}
diff --git a/docs/components/optaplanner/optaplanner.md b/docs/components/optaplanner/optaplanner.md
new file mode 100644
index 0000000..cfef2eb
--- /dev/null
+++ b/docs/components/optaplanner/optaplanner.md
@@ -0,0 +1,92 @@
+---
+id: optaplanner
+title: OptaPlanner
+sidebar_position: 0
+---
+
+# OptaPlanner
+
+A fast, easy-to-use, open source AI constraint solver for software developers
+
+# What can OptaPlanner do?
+
+OptaPlanner optimizes plans and schedules with *hard constraints* and *soft constraints*.
+It **reduces costs** substantially, improves **service quality**, **fulfills employee wishes** and **lowers carbon emissions**.
+
+
+- Vehicle routing
+ - Quick router for a fleet of vehicles.
+- Employee rostering
+ - Assign shifts to employees by skills and availability.
+- Maintenance scheduling
+ - Timely upkeep of machinery and equipment.
+- Conference scheduling
+ - Schedule speakers and talks by availability and topic.
+- School timetabling
+ - Compact schedules for teachers and students.
+- Task assigment
+ - Assign tasks by priority, skills and affinity.
+- Cloud optimization
+ - Bin packaging and defragmentation of cloud resources.
+- Job shop scheduling
+ - Reduce makespan for assembly lines.
+
+# What is OptaPlanner?
+
+OptaPlanner is a Open Source Java™ AI constraint solver to optimize conference schedules.
+
+OptaPlanner is a lightweight, embeddable planning engine. It enables everyday Java™ programmers to solve optimization problems efficiently. It is also compatible with other JVM languages (such as Kotlin and Scala). Constraints apply on plain domain objects and can call existing code. There’s no need to input constraints as mathematical equations. Under the hood, OptaPlanner combines sophisticated Artificial Intelligence optimization algorithms (such as Tabu Search, Simulated Annealing, L [...]
+
+OptaPlanner is open source software, released under the Apache License. It is written in 100% pure Java™, runs on any JVM and is available also in the Maven Central repository.
+
+
+# Modern mathematical optimization
+OptaPlanner is a lightweight, embeddable planning engine. It enables everyday programmers to solve optimization problems efficiently. Constraints apply on plain domain objects and can call existing code. It is Object Oriented Programming (OOP) and Functional Programming (FP) friendly. There’s no need to input constraints as mathematical equations.
+OptaPlanner supports
+- **Continuous planning** to weekly publish the schedule, 3 weeks before execution
+- **Non-disruptive replanning** for changes to an already published schedule
+- **Real-time planning** to react on real-time disruptions in the plan within milliseconds
+- **Overconstrained planning** when there are too few resources to cover all the work
+- **Pinning** so the user is still in control over the schedule
+
+Under the hood, OptaPlanner combines sophisticated Artificial Intelligence optimization algorithms (such as Tabu Search, Simulated Annealing, Late Acceptance and other metaheuristics) with very efficient score calculation and other state-of-the-art constraint solving techniques for NP-complete or NP-hard problems.
+
+# Compatibility
+
+Compatibility
+OptaPlanner works directly from:
+- Java
+- Kotlin
+- Scala
+- Python (experimental)
+
+OptaPlanner integrates seamlessly with:
+
+- Quarkus
+- Spring Boot
+
+OptaPlanner runs on:
+
+- Kubernetes and OpenShift
+- All major clouds
+
+OptaPlanner is open source software, released under the Apache License.
+
+# Code example
+To optimize a problem from Java™ code, add the <code>optaplanner-core</code> jar and call <code>Solver.solve()</code>:
+
+```
+ SolverFactory<MyRoster> factory = SolverFactory.create(...);
+
+ // My domain specific class as input
+ MyRoster problem = ...;
+
+ Solver<MyRoster> solver = factory.buildSolver();
+ // My domain specific class as output
+ MyRoster solution = solver.solve(problem);
+
+ for (MyShift shift : solution.getShifts()) {
+ // Each shift is now assigned to an employee
+ assertNotNull(shift.getEmployee());
+ }
+```
diff --git a/docs/components/sonataflow/_category_.json b/docs/components/sonataflow/_category_.json
new file mode 100644
index 0000000..594e96c
--- /dev/null
+++ b/docs/components/sonataflow/_category_.json
@@ -0,0 +1,6 @@
+{
+ "label": "SonataFlow",
+ "position": 3,
+ "collapsible": false,
+ "collapsed": false
+}
diff --git a/docs/sonataflow/integrations.md b/docs/components/sonataflow/sonataflow.md
similarity index 69%
rename from docs/sonataflow/integrations.md
rename to docs/components/sonataflow/sonataflow.md
index 4040088..900e071 100644
--- a/docs/sonataflow/integrations.md
+++ b/docs/components/sonataflow/sonataflow.md
@@ -1,13 +1,16 @@
---
-id: integrations
-title: Integrations
-sidebar_position: 2
+id: sonataflow
+title: SonataFlow
+sidebar_position: 0
---
-Currently, with SonataFlow you can integrate with services and events in your architecture using:
+# SonataFlow
+
+
+SonataFlow is a tool for building cloud-native workflow applications. You can use it to do the services and events orchestration and choreography. Currently, with SonataFlow you can integrate with services and events in your architecture using:
* CloudEvents. Ideal for an Event-Driven architecture where the services are ready to consume and produce events working in a more reactive way.
* Sync or Async REST services invocations via OpenAPI/AsyncAPI. There are options even to directly call a REST service in the architecture or ecosystem. Either async or sync methods are supported depending on your requirements.
* Internal Service execution or invocation. SonataFlow is also a workflow framework to build applications. You can use it to create custom services in the same thread to run a lightweight workflow-based application within the same instance.
-You can learn how to create, manage, and deploy your workflow applications with the guides included in the [Documentation](/documentation).
+You can learn how to create, manage, and deploy your workflow applications with the guides included in the [Documentation](/documentation).
\ No newline at end of file
diff --git a/docs/components/tools/_category_.json b/docs/components/tools/_category_.json
new file mode 100644
index 0000000..f387bd2
--- /dev/null
+++ b/docs/components/tools/_category_.json
@@ -0,0 +1,6 @@
+{
+ "label": "Tools",
+ "position": 6,
+ "collapsible": false,
+ "collapsed": false
+}
diff --git a/docs/components/tools/tools.md b/docs/components/tools/tools.md
new file mode 100644
index 0000000..9a44d66
--- /dev/null
+++ b/docs/components/tools/tools.md
@@ -0,0 +1,17 @@
+---
+id: tools
+title: Tools
+sidebar_position: 0
+---
+
+# Tools
+A suite of tooling and extensions for working with the Apache KIE technologies — including editors for BPMN, DMN, and other KIE assets, VS Code extensions, Chrome extensions, the KIE Sandbox, command-line utilities, and developer libraries.
+
+- **KIE Sandbox**: [sandbox.kie.org](https://sandbox.kie.org)
+- **VS Code Marketplace**: [Apache KIE extensions on the VS Code Marketplace](https://marketplace.visualstudio.com/search?term=Apache%20KIE&target=VSCode)
+- **Chrome Extensions**: [Apache KIE extensions on the Chrome Web Store](https://chromewebstore.google.com/search/apache%20kie)
+- **jBPM Quarkus Dev UI**: [jbpm-quarkus-devui on Maven Central](https://central.sonatype.com/artifact/org.jbpm/jbpm-quarkus-devui)
+- **Standalone Editors** (embeddable in any web app):
+ - [@kie-tools/bpmn-editor-standalone](https://www.npmjs.com/package/@kie-tools/bpmn-editor-standalone) (starting from 10.2)
+ - [@kie-tools/dmn-editor-standalone](https://www.npmjs.com/package/@kie-tools/dmn-editor-standalone) (starting from 10.1)
+ - [@kie-tools/kie-editors-standalone](https://www.npmjs.com/package/@kie-tools/kie-editors-standalone) (historical — BPMN Editor (classic) and DMN Editor (classic))
diff --git a/docs/drools/books.md b/docs/drools/books.md
deleted file mode 100644
index 9635ab3..0000000
--- a/docs/drools/books.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-id: books
-title: Books
-sidebar_position: 4
----
-
-Books about Drools, and about business rules and decision modelling more
-broadly.
-
-## Drools books
-
-### [Business Rule Engines and AI for Excel Power Users](https://www.packtpub.com/product/ai-and-business-rule-engines-for-excel-power-users/9781804619544)
-
-[](https://www.packtpub.com/product/ai-and-business-rule-engines-for-excel-power-users/9781804619544)
-
-- Paul Browne — ISBN 9781804619544
-- Capture and scale your business knowledge into the cloud — with Microsoft
- 365, Decision Models, and AI tools from IBM and Red Hat.
-
-### [Technical Guide to Drools Rule Engine](https://item.jd.com/10038443959313.html)
-
-[](https://item.jd.com/10038443959313.html)
-
-- ZhiHui Lai (来志辉) — ISBN 9787301305492
-- The first Chinese book on Drools in China, covering basic knowledge,
- intermediate and advanced grammar, and practical cases. Applicable to
- programmers and technology enthusiasts of all levels.
-
-### [Mastering JBoss Drools 6](https://www.packtpub.com/en-us/product/mastering-jboss-drools-6-9781783288632)
-
-[](https://www.packtpub.com/en-us/product/mastering-jboss-drools-6-9781783288632)
-
-## Related books
-
-- **Jess in Action: Java Rule-based Systems** — Ernest Friedman-Hill. ISBN 1930110898.
-- **Expert Systems: Principles and Programming** — Joseph Giarratano, Gary D. Riley. ISBN 0534384471.
-- **Introduction to Expert Systems** — Peter Jackson. ISBN 0201876868.
-- **Smart Enough Systems** — James Taylor, Neil Raden. ISBN 978-0-13-234796-9.
-- **Business Rules and Information Systems: Aligning IT with Business Goals** — Tony Morgan. ISBN 0201743914.
-- **Principles of the Business Rule Approach** — Ronald G. Ross. ISBN 0201788934.
-- **Business Rules Applied** — Von Halle. ISBN 0471412937.
-- **DMN Method and Style, 2nd Edition: A Business Practitioner's Guide to Decision Modeling** — Bruce Silver. ISBN 9780982368176.
-- **DMN Cookbook: 50 Decision Modeling Recipes to Accelerate Your Business Rules Projects with Trisotech, Red Hat, and Drools** — Bruce Silver, Edson Tirelli. ISBN 9780982368183.
-- **[DMN Method and Style, 3rd edition, with DMN Cookbook](https://methodandstyle.com/dmn-method-and-style-3rd-edition-preface)** — Bruce Silver. ISBN 9798218313302.
-- **Knowledge Automation: How to Implement Decision Management in Business Processes** — Alan N. Fish. ISBN 9781118236796.
-- **Real-World Decision Modeling with DMN: Effective Communication of Decision-Making, 2nd Edition Updated for DMN 1.5** — James Taylor, Jan Purchase. ISBN 9798218234669.
diff --git a/docs/drools/dmn.mdx b/docs/drools/dmn.mdx
deleted file mode 100644
index 4fda1aa..0000000
--- a/docs/drools/dmn.mdx
+++ /dev/null
@@ -1,83 +0,0 @@
----
-id: dmn
-title: DMN
-sidebar_position: 3
----
-
-The Decision Model and Notation (DMN™) is a Standard by [OMG®](https://www.omg.org/) providing a common and visual notation readily understandable by all users and personas. With DMN, business analysts can define the initial decision requirements and then formalize more detailed decision models; technical developers can automate the decisions in any process with a portable execution semantic, while business stakeholders can manage and monitor those decisions.
-
-The official webpage of the DMN Standard specification is available at [OMG website](https://www.omg.org/dmn).
-Drools DMN engine is an open source Java™ implementation providing full runtime support for DMN models at Conformance level 3, meaning 100% of the features in the Standard.
-
-- [What is DMN? in 100 seconds](https://www.youtube.com/watch?v=rJyYvNk4QZs)
-
-## At a glance
-
-> DMN is trying to do for Business Decision Management what BPMN did for Business Process Management a decade ago: empower the business to take charge of the logic that drives its operations, through a vendor-independent diagramming language. To be effective, that language must be both usable by business analysts and stakeholders in the business and verifiable for completeness and consistency. DMN is both.
->
-> — Bruce Silver, [What is DMN?](https://methodandstyle.com/what-is-dmn)
-
-
-
-Manage any decision complexity by decomposing and structuring decision services with Decision Requirement Graph (DRG).
-
-
-
-Model business logic with DMN Decision Table, an effective instrument understandable by all personas. Drools DMN engine performs static analysis of the DMN Decision Table to detect gaps, overlaps, and ensure the table rules follow industry best practices.
-
-
-
-Model more complex business logic with the power of all the FEEL Boxed Expression constructs made available by the DMN Standard specification.
-
-Integrate DMN with [BPMN 2.0](https://www.omg.org/spec/BPMN/2.0/) and [CMMN](https://www.omg.org/spec/CMMN/) to describe an executable and semantically defined business logic to be used in business processes.
-
-
-
-## The DMN TCK
-
-The [DMN Technology Compatibility Kit (DMN TCK)](https://dmn-tck.github.io/tck)
-is a community-led proposal for a verifiable and executable method to
-demonstrate the Conformance level of support provided by a vendor-supplied DMN
-implementation: a shared suite of test cases that any engine can run, with the
-[results published](https://dmn-tck.github.io/tck/) for anyone to compare.
-
-The Drools DMN engine provides full runtime support for DMN models at
-Conformance level 3, meaning 100% of the features in the Standard. That claim
-is measured, not asserted: we contribute to the TCK, and as of Apache KIE
-10.2.0 the engine passes 99.9% of its tests.
-
-
-
-## Some historical milestones
-
-Each version of the DMN standard, and the release that first supported it —
-often before OMG formally published the specification. In between, the asides
-mark engine milestones that were not tied to a DMN version.
-
-- **DMN 1.1** — Drools 7.0, May 2017. First-to-market open source project with
- **full Conformance level 3** support.
-- **DMN 1.2** — Drools 7.11, even before OMG formally published it.
-- **DMN 1.3** — Drools 7.31, even before OMG formally published it.
-
-> _November 2020 — **Kogito 1.0**: DMN support in Kogito, with automatic
-> Swagger/OpenAPI and Native Image compilation._
->
-> _February 2021 — **JITExecutor**: an interpreted evaluator for DMN in the
-> cloud, enabler for disruptive innovation in KIE Sandbox._
-
-- **DMN 1.4** — Drools 7.65, even before OMG formally published it.
-
-> _October 2022 — **Drools 8** released, including support for DMN._
-
-- **DMN 1.5** — Apache KIE 10.0.0, December 2024. The first release made at
- Apache.
-- **DMN 1.6** — Apache KIE 10.2.0, April 2026. The latest version of the
- standard.
-
-## Resources
-
-Looking for a gentle introduction to the DMN standard? We have just the right crash course on DMN, freely available for you at [learn-dmn-in-15-minutes.com](http://learn-dmn-in-15-minutes.com).
-
-Drools DMN engine: the [DMN FEEL handbook](https://kiegroup.github.io/dmn-feel-handbook) is a vademecum for the FEEL expression language from the DMN specification, as also implemented by the Drools DMN open source engine.
-
-Drools documentation: <a href="/docs/10.0.x/drools/drools/DMN/index.html">DMN support in Drools</a>.
diff --git a/docs/drools/drl.mdx b/docs/drools/drl.mdx
deleted file mode 100644
index b31fbf5..0000000
--- a/docs/drools/drl.mdx
+++ /dev/null
@@ -1,187 +0,0 @@
----
-id: drl
-title: DRL
-sidebar_position: 2
----
-
-DRL — the Drools Rule Language — is the native language of the Drools rule
-engine. Where DMN gives business analysts a visual, standardized notation, DRL
-gives developers the full expressive power of the engine in plain text files
-that live in your source tree, next to your Java code, under version control.
-
-A rule says *when* something is true, *then* do something. You never call a
-rule; you give the engine facts and it works out which rules match, in what
-order, and re-evaluates as those facts change.
-
-## A first rule
-
-```drl
-package org.acme.orders
-
-import org.acme.orders.Order
-
-rule "Free shipping over 100"
-when
- $order : Order( total > 100, freeShipping == false )
-then
- modify( $order ) { setFreeShipping( true ) };
-end
-```
-
-`when` holds the conditions — patterns matched against the facts the engine
-knows about. `Order( total > 100 )` reads as "there is an `Order` whose
-`total` is greater than 100"; `$order` binds the match so the `then` block can
-use it. `modify` changes a fact *and* tells the engine it changed, so any other
-rule that cares about `freeShipping` gets reconsidered. That is the part that
-makes a rule engine different from a pile of `if` statements: rules react to
-each other, and you never wrote the control flow.
-
-## Rule units
-
-A loose bag of rules and a shared session works, but it gets hard to reason
-about at scale. Rule units are the modern way to organize DRL: a unit is a
-typed container that declares the data its rules operate on, so the rules and
-their inputs are one cohesive, injectable thing.
-
-The data holder is a plain Java class:
-
-```java
-public class HelloWorldUnit implements RuleUnitData {
-
- private final DataStore<String> strings = DataSource.createStore();
- private final List<String> results = new ArrayList<>();
-
- public DataStore<String> getStrings() { return strings; }
- public List<String> getResults() { return results; }
-}
-```
-
-The DRL binds itself to that unit and navigates its data sources with OOPath
-expressions — the `/strings[ ... ]` syntax:
-
-```drl
-package org.acme;
-unit HelloWorldUnit;
-
-rule HelloWorld
-when
- /strings [ this == "Hello World" ]
-then
- results.add("it worked!");
-end
-```
-
-And running it is three lines, with no session bootstrapping to speak of:
-
-```java
-HelloWorldUnit unit = new HelloWorldUnit();
-unit.getStrings().add("Hello World");
-
-try (RuleUnitInstance<HelloWorldUnit> instance =
- RuleUnitProvider.get().createRuleUnitInstance(unit)) {
- instance.fire();
-}
-```
-
-Rule units are also what [Kogito](/kogito) generates REST endpoints from, so
-the same unit you unit-test locally becomes a decision service without
-rewriting it.
-
-## Beyond simple matching
-
-DRL is a language, not a table format, and the interesting parts show up once
-the conditions stop being row-shaped.
-
-**Absence** is a first-class condition. `not`, `exists` and `forall` let you
-match on facts that *aren't* there — something no lookup table expresses
-naturally:
-
-```drl
-rule "Flag unreviewed high-value orders"
-when
- $order : Order( total > 10000 )
- not Review( order == $order )
-then
- $order.flagForReview();
-end
-```
-
-**Aggregation** over the whole working memory, via `accumulate`:
-
-```drl
-rule "Bulk discount"
-when
- $customer : Customer()
- Number( intValue >= 10 ) from accumulate(
- $o : Order( customer == $customer, status == "OPEN" ),
- count( $o ) )
-then
- $customer.applyBulkDiscount();
-end
-```
-
-**Queries** ask the engine questions instead of firing actions, and they can
-recurse — which is how you get backward chaining:
-
-```drl
-query isContainedIn( String x, String y )
- /locations[thing := x, location := y]
- or
- ( /locations[z := thing, location := y] and isContainedIn(x, z;) )
-end
-```
-
-**Truth maintenance**: facts inserted logically are retracted automatically
-when the reason for them stops holding, so you never write the cleanup pass.
-
-**Execution control** when you need it — `salience` to order rules,
-`no-loop` to stop a rule re-triggering itself, `agenda-group` to partition the
-agenda into phases.
-
-## Events and time
-
-Declare a type as an event and the same language becomes a
-[complex event processing](/drools#complex-event-processing-cep-engine)
-engine. Events carry timestamps and durations, they can be reasoned about with
-temporal operators, and they expire on their own:
-
-```drl
-declare TemperatureReading
- @role( event )
-end
-
-rule "Sustained overheating"
-when
- $r : TemperatureReading( celsius > 90 ) over window:time( 10s )
- from entry-point SensorStream
-then
- alerts.add( new Alert( $r ) );
-end
-```
-
-`over window:time( 10s )` slides a ten-second window over the stream, and
-`from entry-point` keeps that stream partitioned from the rest of working
-memory. Because events expire, long-running streams don't grow the session
-without bound.
-
-## Other ways to write the same rules
-
-DRL text is one surface. The same semantics are reachable through decision
-tables in Excel (`drools-decisiontables`), rule templates, and the executable
-model API for building rules programmatically in Java — all of which compile
-down to the same engine.
-
-Rules also compose with the rest of the platform: a BPMN business rule task in
-[jBPM](/jbpm) calls straight into a DRL rule set, in the same service, with no
-remote hop.
-
-## Resources
-
-Drools documentation: the
-[DRL language reference](pathname:///docs/10.2.x/drools/drools/language-reference/index.html)
-is the complete specification — every keyword, operator and conditional
-element. The
-[rule engine guide](pathname:///docs/10.2.x/drools/drools/rule-engine/index.html)
-covers how matching, the agenda and truth maintenance actually work underneath.
-
-Ready to write some? [Get started](/drools/get-started).
diff --git a/docs/drools/drools.mdx b/docs/drools/drools.mdx
deleted file mode 100644
index cf369b4..0000000
--- a/docs/drools/drools.mdx
+++ /dev/null
@@ -1,37 +0,0 @@
----
-id: drools
-title: Drools
-sidebar_label: Overview
-sidebar_position: 0
-hide_title: true
----
-
-import DroolsLogo from "@site/static/img/drools.svg";
-import ComponentBanner, {
- Feature,
- FeatureGrid,
-} from "@site/src/components/ComponentBanner";
-
-<ComponentBanner Logo={DroolsLogo} name="Drools">
- A set of projects for intelligent automation and decision management — a
- forward-chaining and backward-chaining inference-based rule engine, a DMN
- decision engine, and more.
-</ComponentBanner>
-
-<FeatureGrid>
- <Feature title="Rule engine" id="rule-engine">
- A forward-chaining and backward-chaining inference-based rule engine — the
- building block of an expert system, a program that emulates the
- decision-making of a human expert. Write rules in [DRL](/drools/drl).
- </Feature>
- <Feature title="DMN engine" id="dmn-engine">
- Full runtime support for [Decision Model and Notation](/drools/dmn) models
- at Conformance level 3: every feature in the
- [OMG](https://www.omg.org/) standard.
- </Feature>
- <Feature title="CEP engine" id="complex-event-processing-cep-engine">
- Complex Event Processing: reason over streams of events in the same
- engine — temporal operators, sliding time and length windows, and event
- expiration.
- </Feature>
-</FeatureGrid>
diff --git a/docs/drools/get-started.md b/docs/drools/get-started.md
deleted file mode 100644
index 1009496..0000000
--- a/docs/drools/get-started.md
+++ /dev/null
@@ -1,33 +0,0 @@
----
-id: get-started
-title: Get started
-sidebar_position: 1
----
-
-Everything you need to write and run your first rules.
-
-## Prerequisites
-
-1. **An IDE** — [VS Code](https://code.visualstudio.com/Download) (preferred),
- [IntelliJ IDEA](https://www.jetbrains.com/idea/download/) or
- [Eclipse](https://www.eclipse.org/downloads/).
-2. **JDK 21** (preferred) or JDK 17 — [Temurin](https://adoptium.net/) works
- well.
-3. **Maven 3.9+** — [Apache Maven](https://maven.apache.org/).
-
-## Step by step
-
-1. **[Understand what Drools is](pathname:///docs/10.2.x/drools/drools/introduction/)**
- — what a rule engine does, and when declarative rules beat imperative code.
-2. **[Build your first rule project](pathname:///docs/10.2.x/drools/drools/getting-started/#first-rule-project_getting-started)**
- — create a Maven project from an archetype, write your first DRL rules and
- run them from a test, in either the rule unit or the traditional style.
-3. **[Build your first decision service](pathname:///docs/10.2.x/drools/drools/getting-started/#assembly-getting-started-decision-services)**
- — the Traffic Violation example: model decision requirements, decision
- tables and custom data types in [DMN](/drools/dmn), then evaluate them from
- your application.
-
-From here, the
-[reference manual](pathname:///docs/10.2.x/drools/drools/introduction/) covers
-the rule engine, the rule language and DMN in depth, published with every
-Apache KIE release.
diff --git a/docs/drools/papers.md b/docs/drools/papers.md
deleted file mode 100644
index fde0fb8..0000000
--- a/docs/drools/papers.md
+++ /dev/null
@@ -1,237 +0,0 @@
----
-id: papers
-title: Papers
-sidebar_position: 5
----
-
-Academic papers and theses about rule engines and decision automation, from Forgy's original Rete paper onwards.
-
-### Rete: A fast algorithm for the many pattern/many object pattern match problem
-
-- Author: Charles L. Forgy
-- Artificial Intelligence, Volume 19, Issue 1, September 1982, Pages 17-37
-
-### Production Matching for Large Learning Systems (Rete/UL)
-
-- Author: Robert B. Doorenbos
-- PhD thesis, Carnegie Mellon University, January 31, 1995
-
-### The LEAPS Algorithms
-
-- Author: Don Batory
-- Technical Report 94-28, Department of Computer Sciences, University of Texas at Austin, 1994
-
-### [Putting BPMN and DMN to Work: a Pediatric Surgery Case Study](https://doi.org/10.1109/ICDH52753.2021.00028)
-
-- Authors: Anna Maria Bianchi, Matteo Mortari, Claudio Pintavalle, Giuseppe Pozzi
-- Paper: 2021 IEEE International Conference on Digital Health (ICDH), 2021, pp. 154-159, doi: 10.1109/ICDH52753.2021.00028
-- University: Politecnico di Milano, Italy
-
-### [Modeling surgical pediatric processes with BPMN and DMN](http://hdl.handle.net/10589/150128)
-
-- Author: Claudio Pintavalle
-- Supervisor: Anna Maria Bianchi
-- Co-Supervisor: Giuseppe Pozzi
-- Master’s degree thesis
-- University: Politecnico di Milano, Italy
-
-### [Application of Drools in network fault management system](http://www.citeulike.org/user/mzygmunt/article/6482668)
-
-- Authors: Ma Xiu-li, Wang Hong-xia, Zhang Ling-yun
-- Paper: Computer Engineering and Design, Vol. 30, No. 8 (2009/04/28)
-- University: University,Shenyang 110168,China
-
-### [A Snort-based agent for a JADE multi-agent intrusion detection system](http://www.ingentaconnect.com/content/ind/ijiids/2009/00000003/00000001/art00007)
-
-- Authors: Mosqueira-Rey, Alonso-Betanzos, Guijarro-Berdinas, Alonso-Rios, Lago-Pineiro
-- University: Department of Computer Science, University of A Corufia, ESPAGNE
-
-### [Achieving Rule Interoperability Using Chains of Model Transformations](http://www.springerlink.com/content/0174252285737q74/)
-
-- Authors: Marcos Didonet Del Fabro, Patrick Albert, Jean Bézivi, Frédéric Jouault
-- Paper ISBN: 978-3-642-02407-8
-
-### [Implementing a Rule-Based Contract Compliance Checker](http://www.cs.ncl.ac.uk/publications/trs/papers/1150.pdf)
-
-- Authors: Massimo Strano, Carlos Molina-Jimenez, Santosh Shrivastava
-- Paper ISBN: 978-3-642-04279-9
-- University: Newcastle University, Newcastle upon Tyne, UK
-
-### [Want to Know How to Play the Game? Ask the ORACLE!](http://www.springerlink.com/content/855l02875w70221p/)
-
-- Authors: Paola Rizzo, Michael Kriege, Rui Figueiredo, MeiYii Lim and Ruth Aylett
-- Paper ISBN: 978-3-642-04379-6
-- Universities: Interagens s.r.l., c/o ITech, Rome, Italy; Heriot-Watt University, Riccarton, Edinburgh, UK; INESC-ID, Porto Salvo, Portugal
-
-### [Off-line Analysis Research and Implementation Based on Drools](http://en.cnki.com.cn/Article_en/CJFDTOTAL-WJSJ200903063.htm)
-
-- Authors: XIU Jie-lei XU Nan-shan WEI Sheng-jun
-- Universities: School of Information Science, Beijing University of Chemical Technology,Beijing, China; Laboratory of Computer Network Defense Technology, Beijing Institute of Technology,Beijing,China
-
-### [An industry survey of autonomic infrastructure](http://portal.acm.org/citation.cfm?id=1555312.1555316)
-
-- Authors: Michael Keith Nunez, Gary Mueller
-- Paper ISBN: 978-1-60558-612-0
-- Organisation: Sun Microsystems, Inc. , Broomfield, CO, USA
-
-### [An Automatically Composable OWL Reasoner for Resource Constrained Devices](http://www.tara.tcd.ie/handle/2262/38086)
-
-- Authors: BRENNAN, ROB, O'SULLIVAN, DECLAN, KEENEY, JOHN
-- University: Trinity College Dublin, Dublin 2, Ireland
-
-### [Semi-automatic Composition of Geospatial Web Services Using JBoss Rules](http://www.springerlink.com/content/j347l97t18137163/fulltext.pdf)
-
-- Authors: Raluca Zaharia (1) and Laurentiu Vasiliu (1) and Costin Badica (2)
-- (1) Digital Enterprise Research Institute, National University of Ireland, Galway, Ireland
-- (2) Software Engineering Department, University of Craiova, Romania
-- Keywords: Semantic Web Services, WSMO/L/X, ASM
-
-### [Building Machine Learning with Drools Reteoo (Red Hat sponsored research)](http://infoscience.epfl.ch/record/126292/files/oguz-thesis_final.pdf)
-
-- Student: Gizil Oguz
-- Mentor: Viktor Kuncak
-- University: Ecol Polytechnique Federale de Lausanne
-
-### [Development of a Rich Client based GUI for Expert Systems](http://www.lab4inf.fh-muenster.de/lab4inf/docs/thesis/BA_DHuning.pdf) (in German)
-
-- Student: Dennis Huning
-- Mentor: Prof. Nikolaus Wulff
-- Bachelor Thesis
-- University: University of Applied Sciences, Fachhochschule Muenster, Germany
-
-### Reasoning with Uncertainty in Drools
-
-- Student: Davide Sottara
-- Mentor: Prof. Paola Mello
-- Paper: Adding Uncertainty to Rete-OO engines (To be published)
-- University: DEIS, Faculty of Engineering, University of Bologna
-
-### [Program, Enhance Thyself! Demand-Driven Pattern-Oriented Program Enhancement](http://portal.acm.org/citation.cfm?id=1353482.1353485&coll=GUIDE&dl=GUIDE&CFID=1526005&CFTOKEN=47419151)
-
-- Student: Eli Tilevich
-- Mentor: Godmar Back
-- Paper ISBN: ISBN:978-1-60558-044-9
-- University: Virginia Tech
-
-### [Can URML model successfully Drools rules?](http://www.informatik.tu-cottbus.de/~agiurca/papers/RuleApps2008.pdf)
-
-- Student: Emilian Pascalau
-- Mentor: Dr Adrian Giurca
-- Paper ISBN: 978-960-6843-02-0
-- University: Brandenburg University of Technology
-
-### [Knowledge-based Desing Pattern for Detailed Steel Structural Design](http://blog.athico.com/2008/09/improving-naval-engineering-process.html)
-
-- Student: Michael Zimmermann
-- Mentor: Prof. Dr. Robert Bronsart
-- Phd Thesis
-- work in progress
-- for a short summary, see
-- University: University of Rostock, Chair of Naval Architecture
-
-### Policy-driven middleware
-
-- Student: Kris Verlaenen
-- Mentor: Prof. Dr. ir. W. Joosen
-- Phd dissertation: K. Verlaenen, Middleware for advanced service configuration: a policy-based approach. March 2008.
-- University: Katholieke Universiteit Leuven
-
-### Solving Patient Admission Scheduling problem with Drools Solver and Constraint Solver Library
-
-- Student: Wim Van Croonenburg
-- Mentor: Peter Demeester
-- University: Katholieke Hogeschool Sint-Lieven Gent
-
-### [Knowledge Representation in Services Oriented Architecture](http://www.astec.net/brochure/Paper_KNWS2008_Piotr_Grobelny.pdf)
-
-- Student: Piotr Grobelny
-- University: University of Zielona Gora, Faculty of Electrical Engineering, Computer Science and Telecommunications
-
-### [Runtime Evolution for Online Gaming: A Case Study using JBoss and Drools](http://homepages.cs.ncl.ac.uk/lei.zhu1/source/leiZhuGDTW08.pdf)
-
-- Student: Lei Zhu
-- Mentor: Graham Morgan
-- University: University of Newcastle, School of Computing Science
-
-### [Time to the Rescue - Supporting Temporal Reasoning in the Rete Algorithm for Complex Event Processing](http://www.springerlink.com/content/303241m22n52g0g2/)
-
-- Authors: Karen Walzer, Matthias Groch1 and Tino Breddin
-- Paper ISBN: 978-3-540-85653-5
-
-### [Combat SystemApplication of Change-Tolerant Technology: Using Rules Engine for Decision Automation](http://member.navalengineers.org/SiteCollectionDocuments/2008%20Proceedings%20Documents%20%28Papers%20and%20Presentations%29/ASNE%20Day%202008/paper7.pdf)
-
-- Authors: Catherine L. Payne, Mark E. Schmid, Barbara A. Shapter, and Brian T. Taylor
-- Organisation: Naval Engineers
-
-### [A Knowledge Authoring Tool for Clinical Decision Support](http://www.springerlink.com/content/03246251j36pn6q2/)
-
-- Authors: Dustin Dunsmuir, Jeremy Daniels, Christopher Brouse, Simon Ford and J. Mark Ansermino
-- University: The University of British Columbia, Vancouver, Canada
-
-### [JSON Rules](http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.142.6370&rep=rep1&type=pdf#page=15)
-
-- Authors: A Giurca, E Pascalau, G Kaiserslautern
-- Organisation: 31st German Conference on Artificial Intelligence
-
-### [Advances in Autonomic Components & Services](http://www.springerlink.com/content/m0k7562u0v043610/)
-
-- Authors: Marco Aldinucci, Marco Danelutto, Giorgio Zoppi and Peter Kilpatrick
-- Paper ISBN: 978-0-387-09454-0 (Print) 978-0-387-09455-7 (Online)
-- Universities: Dept. Computer Science, University of Pisa, Pisa, IT; Dept. Computer Science, Queen's University Belfast, UK
-
-### [Integrating flaw-response modelling tools used for inspection qualification into a Multi-Agent System software platform](http://www.atypon-link.com/BINT/doi/abs/10.1784/insi.2008.50.2.70)
-
-- Authors: J P McKenna, N McLean, A Gachagan1, S D J McArthur, G Hayward
-- University: University of Strathclyde, Glasgow
-
-### [Mobile and Stationary Sensors for Local Surveillance: System Architecture and Applications](http://www.springerlink.com/content/l62048u947n69735/)
-
-- Authors: Sandro Leuchter, Thomas Partmann and Lothar Berger
-- Paper ISBN: 978-3-540-89899-3
-- University: Fraunhofer Institute for Information and Data Processing
-
-### [Behavioural Skeletons Meeting Services](http://www.springerlink.com/content/m186g31118144078/)
-
-- Authors: M. Danelutto and G. Zoppi
-- Paper ISBN: 978-3-540-69383-3
-- Universities: Dept. Computer Science, Univ. Pisa; CoreGRID Programming Model Institute,
-
-### [An Intelligent Plot-Centric Interface for Mastering Computer Role-Playing Games](http://www.springerlink.com/content/a371722747m4u652/)
-
-- Authors: Carlos León, Federico Peinado, Álvaro Navarro and Héctor Cortiguera
-- Paper ISBN: 978-3-540-89424-7
-- University: Departamento de Ingeniería del Software e Inteligencia Artificial, Universidad Complutense de Madrid, Spain
-
-### [Design and realization of rule-based workflow task assignment system](http://md1.csa.com/partners/viewrecord.php?requester=gs&collection=TRD&recid=200902900014604CI&q=drools+OR+%22jboss+rules%22&uid=789178026&setcookie=yes)
-
-- Authors: Li, Chun-Fang | Tan, Qing-Ping | Xu, Jian-Jun | Xiao, Xiao-Li
-- Organisation: Jisuanji Gongcheng yu Sheji (Computer Engineering and Design). Vol. 29, no. 21, pp. 5572-5575. Nov. 2008
-
-### Arriclides: An architecture integrating clinical decision support models
-
-- Student: Kris Verlaenen
-- Mentor: Prof. Dr. ir. W. Joosen
-- Published Paper: K. Verlaenen, W. Joosen, and P. Verbaeten. Arriclides: An architecture integrating clinical decision support models. In Proceedings of the 40th Annual Hawaii International Conference on System Sciences, January 2007.
-- University: Katholieke Universiteit Leuven
-
-### Towards simplified policy specification and reasoning
-
-- Student: Kris Verlaenen
-- Mentor: Prof. Dr. ir. W. Joosen
-- Published Paper: K. Verlaenen, B. De Win, and W. Joosen. Towards simplified specification of policies in different domains. In Proceedings of the 10th Symposium on Integrated Network Management, May 2007.
-- Published Paper: K. Verlaenen, B. De Win, and W. Joosen. Policy analysis using a hybrid semantic reasoning engine. In Proceedings of the 8th International Workshop on Policies for Distributed Systems and Networks, June 2007.
-- University: Katholieke Universiteit Leuven
-
-### [On Interchange between JBoss Rules and Jess](http://www.springer.com/cda/content/document/cda_downloaddocument/9783540749295-t1.pdf)
-
-- Student: Oana Nicolae
-- Mentor: Dr Adrian Giurca
-- Paper ISBN: 978-3-540-74929-5
-- University: Brandenburg University of Technology
-
-### [Sharing rules between JBoss Rules and Jena](http://csdl.computer.org/dl/proceedings/synasc/2007/3078/00/30780105.pdf)
-
-- Student: Oana Nicolae, Mircea Diaconescu,
-- Mentor: Dr. Adrian Giurca, Prof. Gerd Wagner
-- Paper ISBN: 0-7695-3078-8
-- University: Brandenburg University of Technology
diff --git a/docs/drools/videos.md b/docs/drools/videos.md
deleted file mode 100644
index fd8b897..0000000
--- a/docs/drools/videos.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-id: videos
-title: Videos
-sidebar_position: 6
----
-
-For general KIE community videos, playlists, and live streams, see the
-[Videos page under Community](/community/videos).
-
-## Drools: DMN Engine
-
-A collection of presentations covering the DMN open source engine of Drools.
-
-- [Drools DMN Engine presentations playlist](https://www.youtube.com/playlist?list=PLdbdefeRIj9RW_bWDmx17oXzKshu-4T9H)
-
-## Other videos
-
-- [Backward Chaining with Drools](https://youtu.be/fCjIRVSRFvA)
-- [Build a Graphical Adventure Game in 20 minutes using JBoss Drools: All Hail the Wumpus](https://youtu.be/4CvjKqUOEzM)
-- [Space Invaders in 8 minutes with Drools](http://youtu.be/wORlAZoxtA)
-- [Adventure In Prolog (swf)](http://downloads.jboss.org/drools/videos/text-adventures.swf)
-
-## KIE Workbench (pre-Apache)
-
-[Mark Proctor's playlist on YouTube for KIE Workbench](https://www.youtube.com/playlist?list=PLb9jQNHBKBRj9IJkc_F5nCJAvXaegOGW8).
-
-- [Installation and Setup](https://youtu.be/vj3MNmiUnvY?list=PLb9jQNHBKBRj9IJkc_F5nCJAvXaegOGW8)
-- [Authoring Perspective — Project Explorer](https://youtu.be/EX5Kmdqqi_Q?list=PLb9jQNHBKBRj9IJkc_F5nCJAvXaegOGW8)
-- [Authoring Perspective — Window System](https://youtu.be/Xu2q5iq2eGc?list=PLb9jQNHBKBRj9IJkc_F5nCJAvXaegOGW8)
-- [Authoring Perspective — Problems and Versioning](https://youtu.be/550pFOYIOKk?list=PLb9jQNHBKBRj9IJkc_F5nCJAvXaegOGW8)
-- [Project Editor and Deployment Perspective](https://youtu.be/FKVFkRHLGjQ?list=PLb9jQNHBKBRj9IJkc_F5nCJAvXaegOGW8)
-- [Organization Unit and Repository Administration Perspective](https://youtu.be/Owb_cj7JgGQ?list=PLb9jQNHBKBRj9IJkc_F5nCJAvXaegOGW8)
-
-## Drools Editor Metaphors (pre-Apache)
-
-[Mark Proctor's playlist on YouTube for Drools Editor Metaphors](https://www.youtube.com/playlist?list=PLb9jQNHBKBRipbtadRC-UaUObjwp0aBHJ).
-
-- [Create a Project](https://youtu.be/zYZs8NsC3BA?list=PLb9jQNHBKBRipbtadRC-UaUObjwp0aBHJ)
-- [Create a Model](https://youtu.be/R4KsdsyqGdo?list=PLb9jQNHBKBRipbtadRC-UaUObjwp0aBHJ)
-- [Limited Entry Guided Decision](https://youtu.be/RbUDpXhW8pk?list=PLb9jQNHBKBRipbtadRC-UaUObjwp0aBHJ)
-- [Extended Entry Guided Decision Table](https://youtu.be/6_eSg0h-yeg?list=PLb9jQNHBKBRipbtadRC-UaUObjwp0aBHJ)
-- [Rule Template](https://youtu.be/gnKSX61X9yA?list=PLb9jQNHBKBRipbtadRC-UaUObjwp0aBHJ)
-- [Rule Fragment in Guided Decision Table](https://youtu.be/DNXZmFnvvYA?list=PLb9jQNHBKBRipbtadRC-UaUObjwp0aBHJ)
-- [Score Cards](https://youtu.be/xFLlgtBMTDY?list=PLb9jQNHBKBRipbtadRC-UaUObjwp0aBHJ)
diff --git a/docs/jbpm/books.md b/docs/jbpm/books.md
deleted file mode 100644
index ecb01d2..0000000
--- a/docs/jbpm/books.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-id: books
-title: Books
-sidebar_position: 3
----
-
-Books about jBPM, written by members of the community.
-
-## jBPM books
-
-### [Mastering jBPM6](https://www.packtpub.com/product/mastering-jbpm6/9781783289578)
-
-[](https://www.packtpub.com/product/mastering-jbpm6/9781783289578)
-
-- Simone Fiorini, Arun V Gopalakrishnan — ISBN 9781783289578
-- A deep dive into the jBPM6 platform, from modelling processes through to the
- engine that runs them and the APIs applications build on.
-
-### [jBPM6 Developer Guide](https://www.packtpub.com/en-us/product/jbpm6-developer-guide-9781783286614)
-
-[](https://www.packtpub.com/en-us/product/jbpm6-developer-guide-9781783286614)
-
-- Mariano Nicolas De Maio, Mauricio Salatino, Esteban Aliverti — ISBN 9781783286614
-- For Java developers and architects who want to understand how a Business
- Process Management framework behaves in a real implementation, pairing the
- theory behind BPM systems with building adaptable applications on jBPM6.
-
-### [jBPM5 Developer Guide](https://kverlaen.blogspot.com/2012/12/book-jbpm5-developer-guide.html)
-
-[](https://kverlaen.blogspot.com/2012/12/book-jbpm5-developer-guide.html)
-
-- Mauricio Salatino, Esteban Aliverti — ISBN 9781849516440
-- An introduction to BPM and to modelling processes with the
- [BPMN 2.0](https://www.omg.org/spec/BPMN/2.0/) standard, working up to more
- complex examples that integrate business rules.
-
-### [Effective Business Process Management with JBoss BPM](http://www.schabell.org/2018/03/book-launced-effective-business-process-management-with-jboss-bpm.html)
-
-[](http://www.schabell.org/2018/03/book-launced-effective-business-process-management-with-jboss-bpm.html)
-
-- Eric D. Schabell — free ebook
-- A guide to the Red Hat JBoss BPM Suite tooling: data modelling, designing
- business rules and processes, worked real-world examples and tips for
- testing.
diff --git a/docs/jbpm/get-started.md b/docs/jbpm/get-started.md
deleted file mode 100644
index f3e0e1a..0000000
--- a/docs/jbpm/get-started.md
+++ /dev/null
@@ -1,36 +0,0 @@
----
-id: get-started
-title: Get started
-sidebar_position: 1
----
-
-Everything you need to build and run your first process service. In Apache
-KIE 10, the jBPM process engine ships inside [Kogito](/kogito) — you build a
-Kogito service and model your processes in
-[BPMN 2.0](https://www.omg.org/spec/BPMN/2.0/).
-
-## Prerequisites
-
-1. **An IDE** — [VS Code](https://code.visualstudio.com/Download) (preferred),
- [IntelliJ IDEA](https://www.jetbrains.com/idea/download/) or
- [Eclipse](https://www.eclipse.org/downloads/).
-2. **JDK 21** (preferred) or JDK 17 — [Temurin](https://adoptium.net/) works
- well.
-3. **Maven 3.9+** — [Apache Maven](https://maven.apache.org/).
-
-## Step by step
-
-1. **[Build your first service](pathname:///docs/10.2.x/kogito/#chap-kogito-creating-running)**
- — create a Maven project, design its logic in the Kogito modelers, then run
- the service and interact with it.
-2. **[Model your process in BPMN 2.0](pathname:///docs/10.2.x/kogito/#proc-bpmn-model-creating_kogito-developing-process-services)**
- — create and edit BPMN 2.0 models in the [BPMN modeler](/tools/), from
- start event to end event.
-3. **[Develop your process service](pathname:///docs/10.2.x/kogito/#chap-kogito-developing-process-services)**
- — process variables, user tasks, persistence, messaging, and integrating
- processes with decisions.
-
-From here, the
-[example applications](pathname:///docs/10.2.x/kogito/#proc-kogito-app-examples-running_kogito-creating-running)
-include `orders.bpmn2`, a small process to run and pick apart. For jBPM 7 and
-earlier releases, the manuals are under [Documentation](/documentation).
diff --git a/docs/jbpm/jbpm.mdx b/docs/jbpm/jbpm.mdx
deleted file mode 100644
index ebe164d..0000000
--- a/docs/jbpm/jbpm.mdx
+++ /dev/null
@@ -1,44 +0,0 @@
----
-id: jbpm
-title: jBPM
-sidebar_label: Overview
-sidebar_position: 0
-hide_title: true
----
-
-import JbpmLogo from "@site/static/img/jbpm.svg";
-import ComponentBanner, {
- Feature,
- FeatureGrid,
-} from "@site/src/components/ComponentBanner";
-
-<ComponentBanner Logo={JbpmLogo} name="jBPM">
- A workflow engine for building business applications that automate business
- processes.
-</ComponentBanner>
-
-<FeatureGrid>
- <Feature title="Business processes" id="business-processes">
- Model your business goals as
- [BPMN 2.0](https://www.omg.org/spec/BPMN/2.0/) flow charts, executed by a
- light-weight, extensible workflow engine written in pure Java.
- </Feature>
- <Feature title="Human tasks" id="human-tasks">
- Bring people into the flow: user tasks with pluggable lifecycles,
- assignment strategies, notifications and deadlines — and consoles to work
- on them.
- </Feature>
- <Feature
- title="Rules and decisions orchestration"
- id="rules-and-decisions-orchestration"
- >
- Business rule tasks call out to [DMN](https://www.omg.org/spec/DMN/)
- decisions and DRL rules in the same service, evaluated by
- [Drools](/drools/).
- </Feature>
- <Feature title="Long-running by design" id="long-running-by-design">
- Processes that live for days or months: durable state, timers, signals and
- message correlation, service-level agreements, and migration of running
- instances onto a new process version.
- </Feature>
-</FeatureGrid>
diff --git a/docs/jbpm/what-is-jbpm.md b/docs/jbpm/what-is-jbpm.md
deleted file mode 100644
index a686d4f..0000000
--- a/docs/jbpm/what-is-jbpm.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-id: what-is-jbpm
-title: What is jBPM?
-sidebar_position: 2
----
-
-jBPM originates from BPM (Business Process Management) but it has evolved to enable users to pick their own path in business automation. It provides various capabilities that simplify and externalize business logic into reusable assets such as processes, tasks, decision tables and more.
-
-* business processes ([BPMN 2.0](https://www.omg.org/spec/BPMN/2.0/))
-* human tasks, with pluggable lifecycles, assignment strategies and deadlines
-* decision management ([DMN](https://www.omg.org/spec/DMN/))
-* business rules (DRL)
-
-jBPM is a workflow engine, not a server: it is a set of Java libraries that your service embeds. In Apache KIE 10 the supported way to build that service is [Kogito](/kogito), on either [Quarkus](https://quarkus.io/) or [Spring Boot](https://spring.io/projects/spring-boot). Your BPMN 2.0 models are compiled at build time into the code that runs them, so there is no runtime deployment step and no process repository to manage.
-
-jBPM is typically used to build business applications. A business application could be defined as a domain-specific solution (built with selected frameworks and capabilities) that solves a particular business problem. To implement the business logic it leverages capabilities from various frameworks like business processes and business rules, but also persistence, messaging, transactions, etc.
-
-jBPM is open source software, released under the Apache License 2.0. It is written in 100% pure Java™, runs on any JVM and is available in the Maven Central repository too.
-
-## Cloud-native?
-
-Looking for a pure cloud-native process automation solution, specifically targeted towards creating intelligent business applications in the cloud? Take a look at [Kogito](/kogito) — it is the cloud-native runtime that the jBPM engine ships inside, so the two are not alternatives: when you add process capabilities to a Kogito service, jBPM is what executes them. Start at [Get started](/jbpm/get-started).
-
-## What does jBPM do?
-
-A business process allows you to model your business goals by describing the steps that need to be executed to achieve that goal and the order, using a flow chart. This greatly improves the visibility and agility of your business logic, results in higher-level and domain-specific representations that can be understood by business users and is easier to monitor.
-
-The core of jBPM is a light-weight, extensible workflow engine written in pure Java that allows you to execute business processes using the latest BPMN 2.0 specification. It can run in any Java environment, embedded in your application or as a service.
-
-Its BPMN 2.0 coverage is broad: all the gateways (exclusive, inclusive, parallel, complex and event-based), intermediate catch and throw events, boundary events, errors, escalations, signals, messages, timers and links, embedded, event and ad-hoc sub-processes, call activities, multi-instance activities, compensation and transactions, lanes, and collaboration with message correlation.
-
-On top of the core engine, a lot of features and tools are offered to support business processes throughout their entire life cycle:
-
-* Web-based and IDE-based [modelers](/tools/) to support the graphical creation of your business processes (drag & drop).
-* Pluggable persistence for long-running process state — PostgreSQL and other JDBC databases, MongoDB, Infinispan, RocksDB or the filesystem — added to your service as an add-on.
-* A human task service for including tasks that need to be performed by human actors, including a WS-HumanTask-compatible lifecycle.
-* Consoles supporting process instance management, task lists and task form management, backed by the Data Index and audit services.
-* Timers and scheduled work, delegated to an embedded scheduler or to a standalone Jobs Service.
-* Service-level agreement tracking, and migration of already-running process instances onto a new version of a process definition.
-* History logging (for querying / monitoring / analysis) through the Data Index and Data Audit add-ons.
-
-BPM makes the bridge between business analysts, developers and end users, by offering process management features and tools in a way that both business users and developers like it. Domain-specific nodes can be plugged into the palette — declare them in a work item definition (`.wid`) file and the [BPMN editor](/tools/) picks them up as custom tasks — making the processes more easily understood by business users.
-
-jBPM is also not just an isolated process engine. Complex business logic can be modeled as a combination of business processes with business rules and decisions: a business rule task in your process calls straight into a DRL rule set or a DMN decision, evaluated by [Drools](/drools) in the same service.
diff --git a/docs/kogito/get-started.md b/docs/kogito/get-started.md
deleted file mode 100644
index 6aa8779..0000000
--- a/docs/kogito/get-started.md
+++ /dev/null
@@ -1,30 +0,0 @@
----
-id: get-started
-title: Get started
-sidebar_position: 1
----
-
-Everything you need to build and run your first Kogito service.
-
-## Prerequisites
-
-1. **An IDE** — [VS Code](https://code.visualstudio.com/Download) (preferred),
- [IntelliJ IDEA](https://www.jetbrains.com/idea/download/) or
- [Eclipse](https://www.eclipse.org/downloads/).
-2. **JDK 21** (preferred) or JDK 17 — [Temurin](https://adoptium.net/) works
- well. Optionally [GraalVM](https://www.graalvm.org/) for native compilation.
-3. **Maven 3.9+** — [Apache Maven](https://maven.apache.org/).
-
-## Step by step
-
-1. **[Understand what Kogito is](pathname:///docs/10.2.x/kogito/#con-kogito-automation_kogito-creating-running)**
- — what Kogito is, and when it becomes the core of your domain-specific
- cloud-native services.
-2. **[Build your first service](pathname:///docs/10.2.x/kogito/#chap-kogito-creating-running)**
- — create a Maven project, design its logic with
- [DMN](https://www.omg.org/spec/DMN/) and
- [BPMN 2.0](https://www.omg.org/spec/BPMN/2.0/) in the Kogito
- modelers, then run the service and interact with it.
-3. **[Read the example applications](pathname:///docs/10.2.x/kogito/#ref-kogito-app-examples_kogito-creating-running)**
- — a sequence of applications of increasing complexity, covering
- persistence, messaging with Kafka and data indexing.
diff --git a/docs/kogito/guides.md b/docs/kogito/guides.md
deleted file mode 100644
index 7bfdffa..0000000
--- a/docs/kogito/guides.md
+++ /dev/null
@@ -1,101 +0,0 @@
----
-id: guides
-title: Guides
-sidebar_position: 2
----
-
-You have gone through the [Get started guides](/kogito/get-started). You are
-now ready to dive into specific topic guides.
-
-## Process services
-
-### [Developing process services with Kogito](pathname:///docs/10.2.x/kogito/#chap-kogito-developing-process-services)
-
-As a developer of business processes, you can use Kogito business automation to
-develop process services using
-[Business Process Model and Notation (BPMN) 2.0](https://www.omg.org/spec/BPMN/2.0/)
-models. BPMN 2.0 process models are graphical representations of the steps
-required to achieve a business goal. You can design your BPMN 2.0 processes
-with the Kogito BPMN modeler in VS Code or import existing BPMN 2.0 processes
-into your Kogito projects for deployment and execution.
-
-### [BPMN 2.0 support in Kogito](pathname:///docs/10.2.x/kogito/#con-bpmn_kogito-developing-process-services)
-
-Business Process Model and Notation (BPMN) 2.0 is a standard established by the
-[Object Management Group (OMG)](https://www.omg.org/) for describing and
-modeling business processes.
-
-### [Persistence in Kogito services](pathname:///docs/10.2.x/kogito/#con-persistence_kogito-developing-process-services)
-
-Kogito supports runtime persistence for preserving process data in your
-services across application restarts. Kogito persistence is based on key-value
-storage to persist data, such as active process nodes and process instance
-variables.
-
-### [Kogito Management Console](pathname:///docs/10.2.x/kogito/#con-management-console_kogito-developing-process-services)
-
-The Kogito Management Console is a user interface for viewing the state of all
-available Kogito services and managing process instances. You can use the
-Management Console to view process, subprocess, and node instance details,
-abort process instances, and view domain-specific process data.
-
-## Decision services
-
-### [Developing decision services with Kogito](pathname:///docs/10.2.x/kogito/#collection-kogito-developing-decision-services)
-
-As a developer of business decisions, you can use Kogito business automation to
-develop decision services using
-[Decision Model and Notation (DMN)](https://www.omg.org/spec/DMN/) models,
-Drools Rule Language (DRL) rules, XLS or XLSX spreadsheet decision tables, or a
-combination of all three methods.
-
-### [Using DMN models in Kogito services](pathname:///docs/10.2.x/kogito/#chap-kogito-using-dmn-models)
-
-As a business analyst or business rules developer, you can use Decision Model
-and Notation (DMN) to model a decision service graphically in a decision
-requirements diagram (DRD). This diagram consists of one or more decision
-requirements graphs (DRGs) that trace business decisions from start to finish,
-with each decision node using logic defined in DMN boxed expressions such as
-decision tables.
-
-### [Using DRL rules in Kogito services](pathname:///docs/10.2.x/kogito/#chap-kogito-using-drl-rules)
-
-As a developer of business decisions, you can define business rules using
-Drools Rule Language (DRL) directly in free-form .drl text files. A DRL file
-can contain one or more rules that define at a minimum the rule conditions
-(when) and actions (then).
-
-### [Using spreadsheet decision tables in Kogito services](pathname:///docs/10.2.x/kogito/#chap-kogito-using-spreadsheet-decision-tables)
-
-As a developer of business decisions, you can define business rules in a
-tabular format in spreadsheet decision tables and then include the spreadsheet
-file in your Kogito project. These rules are compiled into Drools Rule Language
-(DRL) for the decision service in your project.
-
-### [Decision engine in Kogito](pathname:///docs/10.2.x/kogito/#chap-kogito-decision-engine)
-
-As a developer of business decisions, your understanding of the decision engine
-in Kogito can help you design more effective business assets and a more
-scalable decision management architecture. The decision engine is the Kogito
-component that stores, processes, and evaluates data to execute business rules
-and to reach the decisions that you define.
-
-## Environment configuration
-
-### [Configuring Kogito supporting services and runtime capabilities](pathname:///docs/10.2.x/kogito/#chap-kogito-configuring)
-
-As a developer of business processes and decisions, you can configure Kogito
-supporting services and runtime properties for advanced use cases with your
-Kogito services.
-
-### [Using the Kogito Data Index Service](pathname:///docs/10.2.x/kogito/#con-data-index-service_kogito-configuring)
-
-Kogito provides a Data Index Service that stores all Kogito events related to
-processes, tasks, and domain data. The Data Index Service is at the core of all
-Kogito search, insight, and management capabilities.
-
-### [Using the Kogito Jobs Service](pathname:///docs/10.2.x/kogito/#con-jobs-service_kogito-configuring)
-
-Kogito provides a Jobs Service for scheduling Business Process Model and
-Notation (BPMN) 2.0 process events that are configured to be executed at a
-specified time. These time-based events in a process model are known as jobs.
diff --git a/docs/kogito/kogito.mdx b/docs/kogito/kogito.mdx
deleted file mode 100644
index 2e6d2aa..0000000
--- a/docs/kogito/kogito.mdx
+++ /dev/null
@@ -1,19 +0,0 @@
----
-id: kogito
-title: Kogito
-sidebar_label: Overview
-sidebar_position: 0
-hide_title: true
----
-
-import KogitoLogo from "@site/static/img/kogito.svg";
-import ComponentBanner from "@site/src/components/ComponentBanner";
-import KogitoHighlights from "@site/src/components/KogitoHighlights";
-
-<ComponentBanner Logo={KogitoLogo} name="Kogito">
- <strong>Kogito ergo automate:</strong> cloud-native business automation for
- building intelligent applications, backed by the battle-tested
- [Drools](/drools) and [jBPM](/jbpm).
-</ComponentBanner>
-
-<KogitoHighlights />
diff --git a/docs/optaplanner/code-example.md b/docs/optaplanner/code-example.md
deleted file mode 100644
index 330ccb7..0000000
--- a/docs/optaplanner/code-example.md
+++ /dev/null
@@ -1,24 +0,0 @@
----
-id: code-example
-title: Code example
-sidebar_position: 4
----
-
-To optimize a problem from Java™ code, add the `optaplanner-core` jar and call
-`Solver.solve()`:
-
-```java
-SolverFactory<MyRoster> factory = SolverFactory.create(...);
-
-// My domain specific class as input
-MyRoster problem = ...;
-
-Solver<MyRoster> solver = factory.buildSolver();
-// My domain specific class as output
-MyRoster solution = solver.solve(problem);
-
-for (MyShift shift : solution.getShifts()) {
- // Each shift is now assigned to an employee
- assertNotNull(shift.getEmployee());
-}
-```
diff --git a/docs/optaplanner/compatibility.md b/docs/optaplanner/compatibility.md
deleted file mode 100644
index 1da84db..0000000
--- a/docs/optaplanner/compatibility.md
+++ /dev/null
@@ -1,24 +0,0 @@
----
-id: compatibility
-title: Compatibility
-sidebar_position: 5
----
-
-OptaPlanner works directly from:
-
-- Java
-- Kotlin
-- Scala
-- Python (experimental)
-
-OptaPlanner integrates seamlessly with:
-
-- Quarkus
-- Spring Boot
-
-OptaPlanner runs on:
-
-- Kubernetes and OpenShift
-- All major clouds
-
-OptaPlanner is open source software, released under the Apache License.
diff --git a/docs/optaplanner/get-started.md b/docs/optaplanner/get-started.md
deleted file mode 100644
index c85b662..0000000
--- a/docs/optaplanner/get-started.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-id: get-started
-title: Get started
-sidebar_position: 1
----
-
-Everything you need to solve your first planning problem.
-
-## Prerequisites
-
-1. **An IDE** — [VS Code](https://code.visualstudio.com/Download) (preferred),
- [IntelliJ IDEA](https://www.jetbrains.com/idea/download/) or
- [Eclipse](https://www.eclipse.org/downloads/).
-2. **JDK 21** (preferred) or JDK 17 — [Temurin](https://adoptium.net/) works
- well.
-3. **Maven 3.9+** — [Apache Maven](https://maven.apache.org/).
-
-## Step by step
-
-1. **[Understand what OptaPlanner is](pathname:///docs/10.2.x/optaplanner/)**
- — what a planning problem is, and how a constraint solver tackles it.
-2. **[Do the Hello World quick start](pathname:///docs/10.2.x/optaplanner/#helloWorldJavaQuickStart)**
- — optimize a school timetable from a plain Java application: model the
- domain, define the constraints and solve.
-3. **[Move to a framework](pathname:///docs/10.2.x/optaplanner/#quarkusJavaQuickStart)**
- — the same timetable as a REST application on Quarkus (recommended), or on
- [Spring Boot](pathname:///docs/10.2.x/optaplanner/#springBootJavaQuickStart).
diff --git a/docs/optaplanner/how-it-works.md b/docs/optaplanner/how-it-works.md
deleted file mode 100644
index 4edcf97..0000000
--- a/docs/optaplanner/how-it-works.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-id: how-it-works
-title: How it works
-sidebar_position: 3
----
-
-## Modern mathematical optimization
-
-OptaPlanner is a lightweight, embeddable planning engine that lets everyday
-Java™ programmers solve optimization problems efficiently. It is also
-compatible with other JVM languages, such as Kotlin and Scala. Constraints
-apply on plain domain objects and can call existing code — there is no need to
-express them as mathematical equations.
-
-Under the hood, OptaPlanner combines sophisticated Artificial Intelligence
-optimization algorithms (such as Tabu Search, Simulated Annealing, Late
-Acceptance and other metaheuristics) with very efficient score calculation and
-other state-of-the-art constraint solving techniques for NP-complete and
-NP-hard problems.
-
-OptaPlanner is open source software, released under the Apache License. It is
-written in 100% pure Java™, runs on any JVM and is available in the Maven
-Central repository.
-
-See the [OptaPlanner documentation](pathname:///docs/10.2.x/optaplanner/) for the
-reference manual, published with every Apache KIE release.
diff --git a/docs/optaplanner/optaplanner.mdx b/docs/optaplanner/optaplanner.mdx
deleted file mode 100644
index 3d1243c..0000000
--- a/docs/optaplanner/optaplanner.mdx
+++ /dev/null
@@ -1,37 +0,0 @@
----
-id: optaplanner
-title: OptaPlanner
-sidebar_label: Overview
-sidebar_position: 0
-hide_title: true
----
-
-import PlannerLogo from "@site/static/img/planner.svg";
-import ComponentBanner, {
- Feature,
- FeatureGrid,
-} from "@site/src/components/ComponentBanner";
-
-<ComponentBanner Logo={PlannerLogo} name="OptaPlanner">
- A fast, easy-to-use, open source AI constraint solver for software
- developers.
-</ComponentBanner>
-
-<FeatureGrid>
- <Feature title="Continuous planning" id="continuous-planning">
- Publish the schedule weekly, three weeks before execution, so planning
- keeps pace with the business rather than happening once.
- </Feature>
- <Feature title="Replanning" id="replanning">
- Handle changes to an already published schedule without turning it upside
- down, and react to real-time disruptions within milliseconds.
- </Feature>
- <Feature title="Overconstrained planning" id="overconstrained-planning">
- Plan even when there are too few resources to cover all the work, so the
- solver degrades gracefully instead of failing.
- </Feature>
- <Feature title="Pinning" id="pinning">
- Keep the user in control of the schedule by locking the parts of it that
- should not move.
- </Feature>
-</FeatureGrid>
diff --git a/docs/optaplanner/use-cases.md b/docs/optaplanner/use-cases.md
deleted file mode 100644
index cb2a873..0000000
--- a/docs/optaplanner/use-cases.md
+++ /dev/null
@@ -1,18 +0,0 @@
----
-id: use-cases
-title: Use cases
-sidebar_position: 2
----
-
-OptaPlanner optimizes plans and schedules with _hard constraints_ and _soft
-constraints_. It **reduces costs** substantially, improves **service quality**,
-**fulfills employee wishes** and **lowers carbon emissions**.
-
-- **Vehicle routing** — quick router for a fleet of vehicles.
-- **Employee rostering** — assign shifts to employees by skills and availability.
-- **Maintenance scheduling** — timely upkeep of machinery and equipment.
-- **Conference scheduling** — schedule speakers and talks by availability and topic.
-- **School timetabling** — compact schedules for teachers and students.
-- **Task assignment** — assign tasks by priority, skills and affinity.
-- **Cloud optimization** — bin packing and defragmentation of cloud resources.
-- **Job shop scheduling** — reduce makespan for assembly lines.
diff --git a/docs/sonataflow/get-started.md b/docs/sonataflow/get-started.md
deleted file mode 100644
index e9516a8..0000000
--- a/docs/sonataflow/get-started.md
+++ /dev/null
@@ -1,23 +0,0 @@
----
-id: get-started
-title: Get started
-sidebar_position: 1
----
-
-Everything you need to build and run your first workflow.
-
-## Step by step
-
-1. **[Prepare your environment](pathname:///docs/10.2.x/sonataflow/serverlessworkflow/latest/getting-started/preparing-environment.html)**
- — an all-in-one guide to everything the SonataFlow guides expect on your
- local machine.
-2. **[Get familiar with the tooling](pathname:///docs/10.2.x/sonataflow/serverlessworkflow/latest/getting-started/getting-familiar-with-our-tooling.html)**
- — the editors and dev tools available for authoring workflows.
-3. **[Create, run and deploy your first project](pathname:///docs/10.2.x/sonataflow/serverlessworkflow/latest/getting-started/introduction-sonataflow-development-guide.html)**
- — the starting guide for SonataFlow development, from an empty directory to
- a deployed workflow application.
-
-From here, [Integrations](/sonataflow/integrations) shows the ways SonataFlow
-connects to the services and events in your architecture, and the
-[SonataFlow guides](pathname:///docs/10.2.x/sonataflow/) cover individual
-topics in depth, published with every Apache KIE release.
diff --git a/docs/sonataflow/sonataflow.mdx b/docs/sonataflow/sonataflow.mdx
deleted file mode 100644
index 178ecf0..0000000
--- a/docs/sonataflow/sonataflow.mdx
+++ /dev/null
@@ -1,42 +0,0 @@
----
-id: sonataflow
-title: SonataFlow
-sidebar_label: Overview
-sidebar_position: 0
-hide_title: true
----
-
-import SonataFlowLogo from "@site/static/img/sonataflow.svg";
-import ComponentBanner, {
- Feature,
- FeatureGrid,
-} from "@site/src/components/ComponentBanner";
-
-<ComponentBanner Logo={SonataFlowLogo} name="SonataFlow">
- A platform for building cloud-native workflow applications. Use it for the
- orchestration and choreography of your services and events.
-</ComponentBanner>
-
-<FeatureGrid>
- <Feature title="Orchestration" id="orchestration">
- Coordinate the services in your architecture into end-to-end workflows,
- with a workflow in control of every call.
- </Feature>
- <Feature title="Choreography" id="choreography">
- Let workflows react to events and publish their own, so services
- collaborate without a central controller.
- </Feature>
- <Feature title="An open standard" id="an-open-standard">
- Workflows are written against the
- [CNCF Serverless Workflow](https://serverlessworkflow.io/) specification,
- a vendor-neutral standard for describing workflows declaratively.
- SonataFlow worked with
- [version 0.8](https://github.com/serverlessworkflow/specification/tree/0.8.x)
- of the specification.
- </Feature>
- <Feature title="Integrations" id="integrations">
- Connect workflows to the services and events already in your
- architecture — see [Integrations](/sonataflow/integrations) for the full
- list.
- </Feature>
-</FeatureGrid>
diff --git a/docs/tools/chrome.md b/docs/tools/chrome.md
deleted file mode 100644
index dcecf60..0000000
--- a/docs/tools/chrome.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-id: chrome
-title: Chrome extensions
-sidebar_position: 5
----
-
-The Chrome extensions add a graphical editor to GitHub itself, so a model in a
-pull request can be read — and edited — as a diagram rather than as XML.
-
-- **[Apache KIE™ BPMN, DMN & Test Scenario Editors for GitHub](https://chromewebstore.google.com/detail/apache-kie-bpmn-dmn-test/mgkfehibfkdpjkfjbikpchpcfimepckf)** — visualize and edit BPMN, DMN and Test Scenario files using a graphical editor on GitHub
-
-## Legacy
-
-Deprecated since 10.3, with 10.2 as their final release. Still installable, but
-no longer developed.
-
-- **[Apache KIE™ Serverless Workflow Editor for GitHub](https://chromewebstore.google.com/detail/apache-kie-serverless-wor/ijamhkegfogkfnmfnfkjdiadomlphfej)** — visualize and edit Serverless Workflow files using a graphical editor on GitHub
-
-Both are listed on the
-[Chrome Web Store](https://chromewebstore.google.com/search/apache%20kie).
diff --git a/docs/tools/consoles.md b/docs/tools/consoles.md
deleted file mode 100644
index d7b4320..0000000
--- a/docs/tools/consoles.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-id: consoles
-title: Dev consoles
-sidebar_position: 6
----
-
-Development consoles for inspecting a running service: the processes and tasks
-it holds, and their state. They ship as artifacts you add to your own
-application rather than as separate deployments.
-
-- **jBPM Quarkus Dev UI**: [jbpm-quarkus-devui on Maven Central](https://central.sonatype.com/artifact/org.jbpm/jbpm-quarkus-devui)
-- **jBPM Spring Boot Web Console**: [jbpm-spring-boot-web-console on Maven Central](https://central.sonatype.com/artifact/org.jbpm/jbpm-spring-boot-web-console) (starting from 10.3)
diff --git a/docs/tools/editors.md b/docs/tools/editors.md
deleted file mode 100644
index fd8d201..0000000
--- a/docs/tools/editors.md
+++ /dev/null
@@ -1,12 +0,0 @@
----
-id: editors
-title: Standalone editors
-sidebar_position: 4
----
-
-Embeddable builds of the editors, published to npm, for putting a modeller
-inside your own web application.
-
-- [@kie-tools/bpmn-editor-standalone](https://www.npmjs.com/package/@kie-tools/bpmn-editor-standalone) (starting from 10.2)
-- [@kie-tools/dmn-editor-standalone](https://www.npmjs.com/package/@kie-tools/dmn-editor-standalone) (starting from 10.1)
-- [@kie-tools/kie-editors-standalone](https://www.npmjs.com/package/@kie-tools/kie-editors-standalone) (historical — BPMN Editor (classic) and DMN Editor (classic))
diff --git a/docs/tools/get-started.md b/docs/tools/get-started.md
deleted file mode 100644
index 7e89de7..0000000
--- a/docs/tools/get-started.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-id: get-started
-title: Get started
-sidebar_position: 1
----
-
-Everything you need to open your first
-[BPMN 2.0](https://www.omg.org/spec/BPMN/2.0/),
-[DMN](https://www.omg.org/spec/DMN/) or Test Scenario model.
-
-## Step by step
-
-1. **[Open KIE Sandbox](/tools/kie-sandbox)** — the editors in your browser,
- with nothing to install. Start from a sample or import a repository.
-2. **[Install the VS Code extensions](/tools/vscode)** — the same editors
- inside your IDE, working on files in your repository.
-3. **[Pick your integration](/tools/editors)** — embed the standalone editors
- in your own web application, or read models as diagrams directly on GitHub
- with the [Chrome extensions](/tools/chrome).
-
-The BPMN, DMN and Test Scenario editors were all rewritten on React, TypeScript
-and PatternFly. They read your existing files unchanged — see
-[the release post](/blog/new-generation-editors-kie-10-2) for the migration
-path.
-
-From here, the [overview](/tools/) walks through each editor in turn, and the
-[dev consoles](/tools/consoles) let you inspect processes and tasks in a
-running jBPM service.
diff --git a/docs/tools/kie-sandbox.md b/docs/tools/kie-sandbox.md
deleted file mode 100644
index aaed632..0000000
--- a/docs/tools/kie-sandbox.md
+++ /dev/null
@@ -1,15 +0,0 @@
----
-id: kie-sandbox
-title: Web — KIE Sandbox
-sidebar_position: 2
----
-
-[KIE Sandbox](https://sandbox.kie.org) runs the BPMN, DMN, Test Scenario and DRL
-editors in a browser tab. There is nothing to install and no account to create.
-
-It is the quickest way to open a model someone sent you, to try a change before
-committing to it, or to follow along with a tutorial. Sandbox can work against
-files in a GitHub repository, so a model you edit there can go back where it
-came from.
-
-- **KIE Sandbox**: [sandbox.kie.org](https://sandbox.kie.org)
diff --git a/docs/tools/tools.mdx b/docs/tools/tools.mdx
deleted file mode 100644
index 4f14653..0000000
--- a/docs/tools/tools.mdx
+++ /dev/null
@@ -1,41 +0,0 @@
----
-id: tools
-title: Tools
-sidebar_label: Overview
-sidebar_position: 0
-hide_title: true
----
-
-import ToolsLogo from "@site/static/img/tools.svg";
-import ComponentBanner, {
- Feature,
- FeatureGrid,
-} from "@site/src/components/ComponentBanner";
-
-<ComponentBanner Logo={ToolsLogo} name="Tools">
- Supporting tooling for authoring and managing the assets that
- [Drools](/drools), [jBPM](/jbpm) and [Kogito](/kogito) run — editors for
- processes, decisions, rules and test scenarios, and consoles for the
- services running them.
-</ComponentBanner>
-
-<FeatureGrid>
- <Feature title="BPMN Editor" id="bpmn-editor">
- Model business processes on a canvas, with a context-aware properties
- panel and validation as you draw. Supports
- [BPMN 2.0](https://www.omg.org/spec/BPMN/2.0/).
- </Feature>
- <Feature title="DMN Editor" id="dmn-editor">
- Build decision requirements diagrams and author boxed expressions,
- decision tables and FEEL. Supports
- [DMN](https://www.omg.org/spec/DMN/) 1.2 through DMN 1.6.
- </Feature>
- <Feature title="DRL Editor" id="drl-editor">
- Edit Drools Rule Language files as text, with syntax highlighting and
- completion for rules you would rather write by hand than draw.
- </Feature>
- <Feature title="Test Scenario Editor" id="test-scenario-editor">
- Write test scenarios for your decisions and rules in a spreadsheet-like
- grid, and keep them in version control next to the models they cover.
- </Feature>
-</FeatureGrid>
diff --git a/docs/tools/vscode.md b/docs/tools/vscode.md
deleted file mode 100644
index d027695..0000000
--- a/docs/tools/vscode.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-id: vscode
-title: VS Code extensions
-sidebar_position: 3
----
-
-The VS Code extensions put the editors inside your IDE, working directly on the
-files in your repository — so a model is reviewed, diffed and committed like any
-other source file.
-
-Two bundles cover the common cases; the rest install a single editor each, for
-when you only want one file type handled.
-
-## Bundles
-
-- **[Apache KIE™ Business Automation Bundle](https://marketplace.visualstudio.com/items?itemName=kie-group.vscode-extension-kie-ba-bundle)** — edit BPMN, DMN and Test Scenario files
-- **[Apache KIE™ Kogito Bundle](https://marketplace.visualstudio.com/items?itemName=kie-group.vscode-extension-kogito-bundle)** — edit BPMN, DMN and Test Scenario files
-
-## Individual editors
-
-- **[Apache KIE™ BPMN Editor](https://marketplace.visualstudio.com/items?itemName=kie-group.bpmn-vscode-extension)** — edit BPMN files
-- **[Apache KIE™ DMN Editor](https://marketplace.visualstudio.com/items?itemName=kie-group.dmn-vscode-extension)** — edit DMN and Test Scenario files
-- **[Apache KIE™ DRL Editor](https://marketplace.visualstudio.com/items?itemName=kie-group.drl-vscode-extension)** — edit DRL files (starting from 10.3)
-
-## Supporting extensions
-
-- **[Apache KIE™ Extended Services](https://marketplace.visualstudio.com/items?itemName=kie-group.extended-services-vscode-extension)** — enhances the capabilities of the DMN and BPMN editors
-
-## Legacy
-
-Deprecated since 10.3, with 10.2 as their final release. Still installable, but
-no longer developed.
-
-- **[Apache KIE™ PMML Editor](https://marketplace.visualstudio.com/items?itemName=kie-group.pmml-vscode-extension)** — edit PMML scorecards
-- **[Apache KIE™ YARD Editor](https://marketplace.visualstudio.com/items?itemName=kie-group.yard-vscode-extension)** — edit YARD definitions
-- **[Apache KIE™ Serverless Workflow Editor](https://marketplace.visualstudio.com/items?itemName=kie-group.swf-vscode-extension)** — edit Serverless Workflow definitions
-
-All of the above are published by `kie-group`, and the full list is on the
-[VS Code Marketplace](https://marketplace.visualstudio.com/search?term=Apache%20KIE&target=VSCode).
diff --git a/docusaurus.config.ts b/docusaurus.config.ts
index 54b2a6a..87f818e 100644
--- a/docusaurus.config.ts
+++ b/docusaurus.config.ts
@@ -6,9 +6,7 @@ const config: Config = {
title: "Apache KIE (incubating)",
tagline:
"The home of the most popular business automation open-source technologies",
- // The favicon is set in src/theme/Root.tsx, not here: pages under a
- // component hotsite fly that component's logo instead of the site icon, and
- // with both set two `rel="icon"` links are emitted, the last one winning.
+ favicon: "img/favicon.ico",
// Set the production url of your site here
url: "https://kie.apache.org/",
@@ -61,31 +59,6 @@ const config: Config = {
[
"@docusaurus/plugin-client-redirects",
{
- // Each component used to live under /components/<name> in the docs
- // tree. They now have their own sections at the site root, so the old
- // paths are redirected to keep inbound links working.
- redirects: [
- { from: "/components/drools", to: "/drools/" },
- { from: "/components/drools/drools_books", to: "/drools/books" },
- { from: "/components/drools/drools_dmn", to: "/drools/dmn" },
- { from: "/components/drools/drools_papers", to: "/drools/papers" },
- {
- from: "/components/drools/drools_upgrade_recipe",
- to: "/drools/upgrade-recipe",
- },
- { from: "/components/drools/drools_videos", to: "/drools/videos" },
- { from: "/components/optaplanner", to: "/optaplanner/" },
- { from: "/components/jbpm", to: "/jbpm/" },
- {
- from: "/components/jbpm/getting_started",
- to: "/jbpm/get-started",
- },
- { from: "/jbpm/getting-started", to: "/jbpm/get-started" },
- { from: "/components/kogito", to: "/kogito/" },
- { from: "/components/sonataflow", to: "/sonataflow/" },
- { from: "/components/tools", to: "/tools/" },
- ],
-
// The docs plugin's `routeBasePath` was changed from "/docs" to "/",
// moving every docs page from `/docs/<x>` to `/<x>`. This plugin
// emits a static HTML redirect at `/docs/<x>` for each existing
@@ -123,19 +96,10 @@ const config: Config = {
label: "About",
},
{
- type: "dropdown",
- label: "Components",
+ type: "docSidebar",
+ sidebarId: "componentsSidebar",
position: "right",
- // Kept in the same order, and with the same labels, as the cards in
- // src/components/HomepageComponents.
- items: [
- { label: "Drools", to: "/drools/" },
- { label: "OptaPlanner", to: "/optaplanner/" },
- { label: "jBPM", to: "/jbpm/" },
- { label: "Kogito", to: "/kogito/" },
- { label: "SonataFlow", to: "/sonataflow/" },
- { label: "Tools", to: "/tools/" },
- ],
+ label: "Components",
},
{
type: "docSidebar",
@@ -212,17 +176,6 @@ const config: Config = {
footer: {
style: "dark",
links: [
- {
- title: "Components",
- items: [
- { label: "Drools", to: "/drools" },
- { label: "OptaPlanner", to: "/optaplanner" },
- { label: "jBPM", to: "/jbpm" },
- { label: "Kogito", to: "/kogito" },
- { label: "SonataFlow", to: "/sonataflow" },
- { label: "Tools", to: "/tools" },
- ],
- },
{
title: "Get involved",
items: [
diff --git a/sidebars.ts b/sidebars.ts
index 065ce0b..0d0e526 100644
--- a/sidebars.ts
+++ b/sidebars.ts
@@ -13,16 +13,11 @@ import type { SidebarsConfig } from "@docusaurus/plugin-content-docs";
const sidebars: SidebarsConfig = {
// By default, Docusaurus generates a sidebar from the docs folder structure
aboutSidebar: [{ type: "autogenerated", dirName: "about" }],
- droolsSidebar: [{ type: "autogenerated", dirName: "drools" }],
- optaplannerSidebar: [{ type: "autogenerated", dirName: "optaplanner" }],
- jbpmSidebar: [{ type: "autogenerated", dirName: "jbpm" }],
- kogitoSidebar: [{ type: "autogenerated", dirName: "kogito" }],
- sonataflowSidebar: [{ type: "autogenerated", dirName: "sonataflow" }],
- toolsSidebar: [{ type: "autogenerated", dirName: "tools" }],
examplesSidebar: [{ type: "autogenerated", dirName: "examples"}],
documentationSidebar: [{ type: "autogenerated", dirName: "documentation" }],
downloadSidebar: [{ type: "autogenerated", dirName: "downloads" }],
communitySidebar: [{ type: "autogenerated", dirName: "community" }],
+ componentsSidebar: [{ type: "autogenerated", dirName: "components" }]
// But you can create a sidebar manually
/*
diff --git a/src/componentSections.ts b/src/componentSections.ts
deleted file mode 100644
index 750566e..0000000
--- a/src/componentSections.ts
+++ /dev/null
@@ -1,79 +0,0 @@
-/**
- * The component hotsites: Drools, jBPM and friends, each of which owns a
- * top-level docs section.
- *
- * One list, because several places need the same facts about a section and
- * they must not drift: the breadcrumbs need its name to sit between Home and
- * the page, and every page under it flies the component's logo as the
- * favicon.
- */
-export type ComponentSection = {
- /** Sidebar name in sidebars.ts. */
- sidebar: string;
- /** The component's name, as a reader would say it. */
- label: string;
- /** The section's landing page, and the prefix every page under it shares. */
- basePath: string;
- /** The component's logo, used as the favicon across the section. */
- logo: string;
-};
-
-export const COMPONENT_SECTIONS: ComponentSection[] = [
- {
- sidebar: "droolsSidebar",
- label: "Drools",
- basePath: "/drools/",
- logo: "/img/drools.svg",
- },
- {
- sidebar: "optaplannerSidebar",
- label: "OptaPlanner",
- basePath: "/optaplanner/",
- logo: "/img/planner.svg",
- },
- {
- sidebar: "jbpmSidebar",
- label: "jBPM",
- basePath: "/jbpm/",
- logo: "/img/jbpm.svg",
- },
- {
- sidebar: "kogitoSidebar",
- label: "Kogito",
- basePath: "/kogito/",
- logo: "/img/kogito.svg",
- },
- {
- sidebar: "sonataflowSidebar",
- label: "SonataFlow",
- basePath: "/sonataflow/",
- logo: "/img/sonataflow.svg",
- },
- {
- sidebar: "toolsSidebar",
- label: "Tools",
- basePath: "/tools/",
- logo: "/img/tools.svg",
- },
-];
-
-export function findSectionBySidebar(
- sidebarName: string | undefined,
-): ComponentSection | undefined {
- return COMPONENT_SECTIONS.find((s) => s.sidebar === sidebarName);
-}
-
-/**
- * The section a page belongs to. Matches the landing page itself (with or
- * without its trailing slash) and everything beneath it.
- */
-export function findSectionByPath(
- pathname: string,
-): ComponentSection | undefined {
- return COMPONENT_SECTIONS.find(
- (s) =>
- pathname === s.basePath ||
- pathname === s.basePath.replace(/\/$/, "") ||
- pathname.startsWith(s.basePath),
- );
-}
diff --git a/src/components/ComponentBanner/index.tsx b/src/components/ComponentBanner/index.tsx
deleted file mode 100644
index e039085..0000000
--- a/src/components/ComponentBanner/index.tsx
+++ /dev/null
@@ -1,98 +0,0 @@
-import React from "react";
-import clsx from "clsx";
-import Heading from "@theme/Heading";
-
-import styles from "./styles.module.css";
-
-type BannerProps = {
- Logo: React.ComponentType<React.ComponentProps<"svg">>;
- name: string;
- children: React.ReactNode;
-};
-
-/**
- * The hero of a component overview page: the component's logo and name over
- * its one-paragraph definition, all centered. Pages using it set
- * `hide_title: true` — the banner's name is the page's h1. The overview page
- * carries nothing after the cards, so Docusaurus's own "Next: Get started"
- * pagination is the page's call to action.
- */
-export default function ComponentBanner({
- Logo,
- name,
- children,
-}: BannerProps): JSX.Element {
- return (
- // Not a <header>: the docs theme zeroes the top margin of whatever
- // follows a header element, which would glue the cards to the banner.
- <div className={styles.banner}>
- <Logo className={styles.logo} role="img" aria-hidden="true" />
- <Heading as="h1" className={styles.name}>
- {name}
- </Heading>
- <div className={styles.tagline}>{children}</div>
- </div>
- );
-}
-
-/**
- * The component's sub-components (engines, editors, capabilities) as cards.
- * `wideLast` puts the cards in two columns and lets the last one span both,
- * for an odd card out that would otherwise sit alone in a ragged row.
- */
-export function FeatureGrid({
- wideLast,
- stacked,
- children,
-}: {
- wideLast?: boolean;
- /** One full-width card per row, rather than a grid of columns. */
- stacked?: boolean;
- children: React.ReactNode;
-}): JSX.Element {
- return (
- <div
- className={clsx(
- styles.grid,
- wideLast && styles.gridWideLast,
- stacked && styles.gridStacked,
- )}
- >
- {children}
- </div>
- );
-}
-
-export function Feature({
- title,
- id,
- media,
- mediaSide,
- children,
-}: {
- title: string;
- id?: string;
- /** Optional illustration. Shown above the title unless `mediaSide` is set. */
- media?: React.ReactNode;
- /** Put the illustration beside the text instead of above it. */
- mediaSide?: "left" | "right";
- children: React.ReactNode;
-}): JSX.Element {
- return (
- <section
- className={clsx(
- styles.feature,
- mediaSide && styles.featureRow,
- mediaSide === "right" && styles.featureRowReverse,
- )}
- >
- {media}
- <div>
- <Heading as="h2" id={id} className={styles.featureTitle}>
- {title}
- </Heading>
- {children}
- </div>
- </section>
- );
-}
diff --git a/src/components/ComponentBanner/styles.module.css b/src/components/ComponentBanner/styles.module.css
deleted file mode 100644
index d795f81..0000000
--- a/src/components/ComponentBanner/styles.module.css
+++ /dev/null
@@ -1,130 +0,0 @@
-.banner {
- display: flex;
- flex-direction: column;
- align-items: center;
- text-align: center;
- padding: 2rem 1rem 0.5rem;
-}
-
-/* Hero art behind the banner, bled to the edges of the content column. The
- pseudo-element (rather than a background on .banner itself) is what lets it
- bleed past the column's padding; `isolation` keeps the negative z-index
- inside the banner instead of dropping it behind the page. */
-.logo {
- /* Same treatment as the homepage cards: the logo is a single shape filled
- with the theme's primary color. */
- height: clamp(5.5rem, 12vw, 8rem);
- width: clamp(5.5rem, 12vw, 8rem);
- fill: var(--ifm-color-primary);
- margin-bottom: 1.25rem;
-}
-
-/* Same wordmark treatment as "KIE" in the homepage hero. */
-.name {
- font-family: "Quicksand", var(--ifm-font-family-base);
- font-size: 2.75rem;
- margin-bottom: 0.75rem;
-}
-
-.tagline {
- max-width: 42rem;
- font-size: 1.125rem;
- /* Full strength rather than the muted grey body text: this is the one line
- that defines the component. Mirrored to white on a dark page, where pure
- black would be unreadable. */
- color: #000;
-}
-
-[data-theme="dark"] .tagline {
- color: #fff;
-}
-
-.tagline p:last-child {
- margin-bottom: 0;
-}
-
-.grid {
- display: grid;
- grid-template-columns: repeat(auto-fit, minmax(14rem, 1fr));
- gap: 1rem;
- margin: 3rem 0;
-}
-
-.gridStacked {
- grid-template-columns: 1fr;
-}
-
-/* Exactly four cards read better as a 2×2 than as 3 + 1. */
-@media (min-width: 700px) {
- .grid:has(> :nth-child(4):last-child),
- .gridWideLast {
- grid-template-columns: repeat(2, minmax(0, 1fr));
- }
-
- .gridWideLast > :last-child {
- grid-column: 1 / -1;
- }
-}
-
-.feature {
- padding: 1.25rem 1.5rem;
- border: 1px solid var(--ifm-color-emphasis-200);
- border-radius: 8px;
- /* Not quite opaque: on a page with hero art behind the cards this lifts the
- text clear of it while still letting the art register through. */
- background-color: rgb(255 255 255 / 0.82);
-}
-
-[data-theme="dark"] .feature {
- background-color: rgb(36 37 38 / 0.82);
-}
-
-/* Illustration beside the text rather than above it. */
-.featureRow {
- display: flex;
- align-items: center;
- gap: 1.75rem;
-}
-
-.featureRowReverse {
- flex-direction: row-reverse;
-}
-
-/* A list beside an illustration only fills part of the card, leaving it tall
- with dead space alongside. Two columns spend the width instead. */
-@media (min-width: 700px) {
- .featureRow ul {
- columns: 2;
- column-gap: 2.5rem;
- }
-
- .featureRow li {
- break-inside: avoid;
- }
-}
-
-/* Too narrow to sit side by side: the illustration goes back above the text,
- where it needs the gap the flex layout was providing. */
-@media (max-width: 700px) {
- .featureRow {
- display: block;
- }
-
- .featureRow > :first-child {
- margin-bottom: 0.75rem;
- }
-}
-
-.feature p:last-child,
-.feature ul:last-child {
- margin-bottom: 0;
-}
-
-.feature ul {
- padding-left: 1.1rem;
-}
-
-.featureTitle {
- font-size: 1.15rem;
- margin-bottom: 0.5rem;
-}
diff --git a/src/components/KogitoHighlights/index.tsx b/src/components/KogitoHighlights/index.tsx
deleted file mode 100644
index 3914ae9..0000000
--- a/src/components/KogitoHighlights/index.tsx
+++ /dev/null
@@ -1,112 +0,0 @@
-import useBaseUrl from "@docusaurus/useBaseUrl";
-
-import { Feature, FeatureGrid } from "@site/src/components/ComponentBanner";
-import styles from "./styles.module.css";
-
-type Highlight = {
- title: string;
- image: string;
- /** Multiplier on the base illustration size; taller cards carry bigger art. */
- imageScale?: number;
- body: React.ReactNode;
-};
-
-const HIGHLIGHTS: Highlight[] = [
- {
- title: "Kogito ergo cloud",
- image: "/img/kogito/homepage_graphic_1",
- imageScale: 2,
- body: (
- <p>
- Kogito is designed from ground up to run at scale on cloud
- infrastructure. By taking advantage of the latest technologies (Quarkus,
- Spring Boot, etc.), you get amazingly fast boot times and instant
- scaling on orchestration platforms like Kubernetes.
- </p>
- ),
- },
- {
- title: "Kogito ergo domain",
- image: "/img/kogito/homepage_graphic_2",
- imageScale: 1.5,
- body: (
- <p>
- Kogito adapts to your business domain rather than the other way around.
- No more leaking abstraction of the tool into your client applications.
- Stay focused on what the business is about instead of being concerned
- with technology behind it.
- </p>
- ),
- },
- {
- title: "Kogito ergo power",
- image: "/img/kogito/homepage_graphic_3",
- imageScale: 2,
- body: (
- <>
- <p>
- Kogito offers a powerful developer experience based on battle-tested
- components:
- </p>
- <ul>
- <li>Tooling embeddable wherever you need it</li>
- <li>Code generation taking care of 80% of the work</li>
- <li>Flexibility to customize, only use what you need</li>
- <li>Simplified local development with live reload</li>
- </ul>
- </>
- ),
- },
-];
-
-function HighlightCard({
- highlight,
- mediaSide,
-}: {
- highlight: Highlight;
- mediaSide: "left" | "right";
-}): JSX.Element {
- const image = useBaseUrl(`${highlight.image}.png`);
- const image2x = useBaseUrl(`${highlight.image}@2x.png`);
- return (
- <Feature
- title={highlight.title}
- mediaSide={mediaSide}
- media={
- <img
- className={styles.image}
- style={
- {
- "--kie-highlight-image-scale": highlight.imageScale ?? 1,
- } as React.CSSProperties
- }
- src={image}
- srcSet={`${image} 1x, ${image2x} 2x`}
- alt=""
- aria-hidden="true"
- />
- }
- >
- {highlight.body}
- </Feature>
- );
-}
-
-/**
- * The three "Kogito ergo ..." cards, embedded in the Kogito overview doc.
- * Same cards as the other component overviews, but stacked full width with
- * the illustrations alternating side to side down the page.
- */
-export default function KogitoHighlights(): JSX.Element {
- return (
- <FeatureGrid stacked>
- {HIGHLIGHTS.map((highlight, index) => (
- <HighlightCard
- key={highlight.title}
- highlight={highlight}
- mediaSide={index % 2 === 0 ? "left" : "right"}
- />
- ))}
- </FeatureGrid>
- );
-}
diff --git a/src/components/KogitoHighlights/styles.module.css b/src/components/KogitoHighlights/styles.module.css
deleted file mode 100644
index 7ef42f0..0000000
--- a/src/components/KogitoHighlights/styles.module.css
+++ /dev/null
@@ -1,9 +0,0 @@
-/* The cards themselves come from ComponentBanner, shared with the other
- component overviews. Only Kogito's illustration sizing lives here. */
-
-.image {
- display: block;
- flex: 0 0 auto;
- width: calc(5rem * var(--kie-highlight-image-scale, 1));
- height: auto;
-}
diff --git a/src/css/custom.css b/src/css/custom.css
index fdfcadb..372c03d 100644
--- a/src/css/custom.css
+++ b/src/css/custom.css
@@ -28,31 +28,6 @@
U+20A0-20AB, U+20AD-20C0, U+2113, U+2C60-2C7F, U+A720-A7FF;
}
-/* Cinzel, self-hosted alongside Quicksand (SIL Open Font License). Used only
- for the "Kogito ergo ..." headings — its lowercase is small caps, so it is
- a display face, not a text one. */
-@font-face {
- font-family: 'Cinzel';
- font-style: normal;
- font-weight: 600;
- font-display: swap;
- src: url('/fonts/cinzel-latin.woff2') format('woff2');
- unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA,
- U+02DC, U+0304, U+0308, U+0329, U+2000-206F, U+20AC, U+2122, U+2191, U+2193,
- U+2212, U+2215, U+FEFF, U+FFFD;
-}
-
-@font-face {
- font-family: 'Cinzel';
- font-style: normal;
- font-weight: 600;
- font-display: swap;
- src: url('/fonts/cinzel-latin-ext.woff2') format('woff2');
- unicode-range: U+0100-02BA, U+02BD-02C5, U+02C7-02CC, U+02CE-02D7, U+02DD-02FF,
- U+0304, U+0308, U+0329, U+1D00-1DBF, U+1E00-1E9F, U+1EF2-1EFF, U+2020,
- U+20A0-20AB, U+20AD-20C0, U+2113, U+2C60-2C7F, U+A720-A7FF;
-}
-
html {
scrollbar-gutter: stable;
}
@@ -224,45 +199,3 @@ html {
height: 3rem;
margin-right: 0.5rem;
}
-
-/* The Kogito hero, carried over from kogito.kie.org so the overview keeps that
- site's vibe. It hangs off the docs main container rather than the banner
- itself: the banner is inset by the content column's padding, so the art
- would end in a hard vertical edge partway across the page. On <main> it
- spans the full width and its own aspect ratio sets the band's height, so
- nothing is cropped. Scoped to the Kogito overview by the doc id Docusaurus
- puts on <html> (the id contains a slash, hence the attribute selector). */
-html[class*="docs-doc-id-kogito/kogito"] main[class*="docMainContainer"] {
- position: relative;
- isolation: isolate;
-}
-
-html[class*="docs-doc-id-kogito/kogito"] main[class*="docMainContainer"]::before {
- content: "";
- position: absolute;
- top: 0;
- left: 0;
- width: 100%;
- /* The art is drawn 2619x884 and scaled to 125% of the column so it reads at
- hero size. Anchored top left, so it grows out to the right and the mascot
- watermark stays whole. The band's height follows the same scale
- (884 x 1.25 = 1105) so the bottom of the composition isn't clipped; keep
- the two in step if the scale changes. A background image can't overflow
- its box, so the bleed costs no horizontal scroll. */
- aspect-ratio: 2619 / 1105;
- z-index: -1;
- pointer-events: none;
- background: url("/img/kogito/hero-background.svg") no-repeat top left;
- background-size: 125% auto;
- opacity: 0.33;
-}
-
-/* The art is drawn for a light page: the mascot watermark multiplies away on
- a dark one, leaving only the geometric shapes, which need holding back. */
-[data-theme='dark']
- html[class*="docs-doc-id-kogito/kogito"]
- main[class*="docMainContainer"]::before,
-html[class*="docs-doc-id-kogito/kogito"][data-theme='dark']
- main[class*="docMainContainer"]::before {
- opacity: 0.16;
-}
diff --git a/src/pages/drools.tsx b/src/pages/drools.tsx
new file mode 100644
index 0000000..93cc690
--- /dev/null
+++ b/src/pages/drools.tsx
@@ -0,0 +1,5 @@
+import {Redirect} from '@docusaurus/router';
+
+export default function DroolsRedirect(): JSX.Element {
+ return <Redirect to="/components/drools" />;
+}
diff --git a/src/pages/jbpm.tsx b/src/pages/jbpm.tsx
new file mode 100644
index 0000000..dd502b7
--- /dev/null
+++ b/src/pages/jbpm.tsx
@@ -0,0 +1,5 @@
+import {Redirect} from '@docusaurus/router';
+
+export default function JbpmRedirect(): JSX.Element {
+ return <Redirect to="/components/jbpm" />;
+}
diff --git a/src/pages/kogito.tsx b/src/pages/kogito.tsx
new file mode 100644
index 0000000..330d507
--- /dev/null
+++ b/src/pages/kogito.tsx
@@ -0,0 +1,5 @@
+import {Redirect} from '@docusaurus/router';
+
+export default function KogitoRedirect(): JSX.Element {
+ return <Redirect to="/components/kogito" />;
+}
diff --git a/src/pages/optaplanner.tsx b/src/pages/optaplanner.tsx
new file mode 100644
index 0000000..131db49
--- /dev/null
+++ b/src/pages/optaplanner.tsx
@@ -0,0 +1,5 @@
+import {Redirect} from '@docusaurus/router';
+
+export default function OptaPlannerRedirect(): JSX.Element {
+ return <Redirect to="/components/optaplanner" />;
+}
diff --git a/src/pages/sonataflow.tsx b/src/pages/sonataflow.tsx
new file mode 100644
index 0000000..d46ccc2
--- /dev/null
+++ b/src/pages/sonataflow.tsx
@@ -0,0 +1,5 @@
+import {Redirect} from '@docusaurus/router';
+
+export default function SonataFlowRedirect(): JSX.Element {
+ return <Redirect to="/components/sonataflow" />;
+}
diff --git a/src/pages/tools.tsx b/src/pages/tools.tsx
new file mode 100644
index 0000000..acc745e
--- /dev/null
+++ b/src/pages/tools.tsx
@@ -0,0 +1,5 @@
+import {Redirect} from '@docusaurus/router';
+
+export default function ToolsRedirect(): JSX.Element {
+ return <Redirect to="/components/tools" />;
+}
diff --git a/src/theme/DocBreadcrumbs/index.tsx b/src/theme/DocBreadcrumbs/index.tsx
deleted file mode 100644
index 21d0199..0000000
--- a/src/theme/DocBreadcrumbs/index.tsx
+++ /dev/null
@@ -1,135 +0,0 @@
-/**
- * Swizzled from @docusaurus/theme-classic to add a section crumb.
- *
- * Every docs section here is an `autogenerated` sidebar over a flat folder, so
- * Docusaurus has no category to put between the home crumb and the page, and
- * every page reads "Home > Overview". This adds the section itself — the name
- * a reader would call the hotsite — giving "Home > Drools > Overview".
- */
-import React from "react";
-import clsx from "clsx";
-import { ThemeClassNames } from "@docusaurus/theme-common";
-import {
- useSidebarBreadcrumbs,
- useHomePageRoute,
- useDocsSidebar,
-} from "@docusaurus/theme-common/internal";
-import Link from "@docusaurus/Link";
-import { translate } from "@docusaurus/Translate";
-import HomeBreadcrumbItem from "@theme/DocBreadcrumbs/Items/Home";
-
-import { findSectionBySidebar } from "@site/src/componentSections";
-import styles from "./styles.module.css";
-
-function BreadcrumbsItemLink({
- children,
- href,
- isLast,
-}: {
- children: React.ReactNode;
- href?: string;
- isLast: boolean;
-}) {
- const className = "breadcrumbs__link";
- if (isLast) {
- return (
- <span className={className} itemProp="name">
- {children}
- </span>
- );
- }
- return href ? (
- <Link className={className} href={href} itemProp="item">
- <span itemProp="name">{children}</span>
- </Link>
- ) : (
- <span className={className}>{children}</span>
- );
-}
-
-function BreadcrumbsItem({
- children,
- active,
- index,
- addMicrodata,
-}: {
- children: React.ReactNode;
- active?: boolean;
- index: number;
- addMicrodata?: boolean;
-}) {
- return (
- <li
- {...(addMicrodata && {
- itemScope: true,
- itemProp: "itemListElement",
- itemType: "https://schema.org/ListItem",
- })}
- className={clsx("breadcrumbs__item", {
- "breadcrumbs__item--active": active,
- })}
- >
- {children}
- <meta itemProp="position" content={String(index + 1)} />
- </li>
- );
-}
-
-export default function DocBreadcrumbs(): JSX.Element | null {
- const breadcrumbs = useSidebarBreadcrumbs();
- const homePageRoute = useHomePageRoute();
- const sidebar = useDocsSidebar();
-
- if (!breadcrumbs) {
- return null;
- }
-
- const section = findSectionBySidebar(sidebar?.name);
- const items = section
- ? [
- { type: "link" as const, label: section.label, href: section.basePath },
- ...breadcrumbs,
- ]
- : breadcrumbs;
-
- return (
- <nav
- className={clsx(
- ThemeClassNames.docs.docBreadcrumbs,
- styles.breadcrumbsContainer,
- )}
- aria-label={translate({
- id: "theme.docs.breadcrumbs.navAriaLabel",
- message: "Breadcrumbs",
- description: "The ARIA label for the breadcrumbs",
- })}
- >
- <ul
- className="breadcrumbs"
- itemScope
- itemType="https://schema.org/BreadcrumbList"
- >
- {homePageRoute && <HomeBreadcrumbItem />}
- {items.map((item, idx) => {
- const isLast = idx === items.length - 1;
- const href =
- item.type === "category" && item.linkUnlisted
- ? undefined
- : item.href;
- return (
- <BreadcrumbsItem
- key={idx}
- active={isLast}
- index={idx}
- addMicrodata={!!href}
- >
- <BreadcrumbsItemLink href={href} isLast={isLast}>
- {item.label}
- </BreadcrumbsItemLink>
- </BreadcrumbsItem>
- );
- })}
- </ul>
- </nav>
- );
-}
diff --git a/src/theme/DocBreadcrumbs/styles.module.css b/src/theme/DocBreadcrumbs/styles.module.css
deleted file mode 100644
index 535b44a..0000000
--- a/src/theme/DocBreadcrumbs/styles.module.css
+++ /dev/null
@@ -1,7 +0,0 @@
-/* Copied verbatim from @docusaurus/theme-classic alongside the swizzled
- DocBreadcrumbs component. */
-
-.breadcrumbsContainer {
- --ifm-breadcrumb-size-multiplier: 0.8;
- margin-bottom: 0.8rem;
-}
diff --git a/src/theme/Navbar/Logo/index.tsx b/src/theme/Navbar/Logo/index.tsx
deleted file mode 100644
index 823b2fe..0000000
--- a/src/theme/Navbar/Logo/index.tsx
+++ /dev/null
@@ -1,73 +0,0 @@
-import Logo from "@theme/Logo";
-import Link from "@docusaurus/Link";
-import useBaseUrl from "@docusaurus/useBaseUrl";
-import { useLocation } from "@docusaurus/router";
-
-import styles from "./styles.module.css";
-
-type Component = {
- /** Root path of the component's section, e.g. "/drools". */
- path: string;
- /** Component name, spelled out next to the Apache KIE mark. */
- title: string;
- /** Square component mark, served from static/img. */
- logo: string;
-};
-
-const COMPONENTS: Component[] = [
- { path: "/drools", title: "Drools", logo: "/img/drools.svg" },
- { path: "/optaplanner", title: "OptaPlanner", logo: "/img/planner.svg" },
- { path: "/jbpm", title: "jBPM", logo: "/img/jbpm.svg" },
- { path: "/kogito", title: "Kogito", logo: "/img/kogito.svg" },
- { path: "/sonataflow", title: "SonataFlow", logo: "/img/sonataflow.svg" },
- { path: "/tools", title: "Tools", logo: "/img/tools.svg" },
-];
-
-function findComponent(pathname: string): Component | undefined {
- const current = pathname.replace(/\/+$/, "");
- return COMPONENTS.find(
- (component) =>
- current === component.path || current.startsWith(`${component.path}/`)
- );
-}
-
-/**
- * Swizzled to append a component lockup to the Apache KIE logo while browsing
- * a component section, so the navbar reads "Apache KIE / Drools". Every other
- * page renders the stock logo.
- */
-export default function NavbarLogo(): JSX.Element {
- const { pathname } = useLocation();
- const component = findComponent(pathname);
- const logoUrl = useBaseUrl(component?.logo ?? "/img/favicon.ico");
-
- const kieLogo = (
- <Logo
- className="navbar__brand"
- imageClassName="navbar__logo"
- titleClassName="navbar__title text--truncate"
- />
- );
-
- if (!component) {
- return kieLogo;
- }
-
- return (
- <div className={styles.lockup}>
- {kieLogo}
- <span className={styles.separator} aria-hidden="true">
- /
- </span>
- <Link to={component.path} className={styles.componentBrand}>
- <img
- className={styles.componentLogo}
- src={logoUrl}
- alt=""
- aria-hidden="true"
- />
- <span className={styles.componentTitle}>{component.title}</span>
- </Link>
- </div>
- );
-}
diff --git a/src/theme/Navbar/Logo/styles.module.css b/src/theme/Navbar/Logo/styles.module.css
deleted file mode 100644
index a00ccf5..0000000
--- a/src/theme/Navbar/Logo/styles.module.css
+++ /dev/null
@@ -1,63 +0,0 @@
-.lockup {
- display: flex;
- align-items: center;
- min-width: 0;
-}
-
-.lockup :global(.navbar__brand) {
- margin-right: 0;
-}
-
-/* Only the trailing margin is dropped — the mark itself is left at exactly the
- size it renders everywhere else on the site. */
-.lockup :global(.navbar__logo) {
- margin-right: 0;
-}
-
-.separator {
- margin: 0 1rem;
- font-size: 1.5rem;
- line-height: 1;
- color: var(--ifm-color-emphasis-400);
- user-select: none;
-}
-
-.componentBrand {
- display: flex;
- align-items: center;
- min-width: 0;
- color: var(--ifm-navbar-link-color);
-}
-
-.componentBrand:hover {
- color: var(--ifm-color-primary);
- text-decoration: none;
-}
-
-.componentLogo {
- height: 2rem;
- width: 2rem;
- margin-right: 0.5rem;
- flex: 0 0 auto;
-}
-
-/* Quicksand is the wordmark typeface — used for names only, never for
- surrounding UI text. */
-.componentTitle {
- font-family: "Quicksand", var(--ifm-font-family-base);
- font-size: 1.25rem;
- font-weight: var(--ifm-font-weight-bold);
- white-space: nowrap;
- overflow: hidden;
- text-overflow: ellipsis;
-}
-
-@media (max-width: 996px) {
- .componentTitle {
- display: none;
- }
-
- .separator {
- margin: 0 0.75rem;
- }
-}
diff --git a/src/theme/Root.tsx b/src/theme/Root.tsx
index 8514c85..ba7ad3c 100644
--- a/src/theme/Root.tsx
+++ b/src/theme/Root.tsx
@@ -1,46 +1,9 @@
-import Head from "@docusaurus/Head";
-import { useLocation } from "@docusaurus/router";
-import useBaseUrl from "@docusaurus/useBaseUrl";
+import {useEffect} from 'react';
+import {useLocation, useHistory} from '@docusaurus/router';
-import { findSectionByPath } from "@site/src/componentSections";
+export default function Root({children}: {children: React.ReactNode}): JSX.Element | null {
+ const location = useLocation();
+ const history = useHistory();
-const SITE_FAVICON = "/img/favicon.ico";
-
-/**
- * Flies the component's own logo as the favicon on every page of a component
- * hotsite, so a tab parked on the Drools docs is recognisable as Drools, and
- * the site's own icon everywhere else.
- *
- * The favicon is set here rather than by `favicon` in docusaurus.config.ts.
- * With both, two `rel="icon"` links are emitted and the browser honours the
- * last one — which was the config's, so the component logo never won.
- */
-function Favicon(): JSX.Element {
- const { pathname } = useLocation();
- const section = findSectionByPath(pathname);
- const icon = section?.logo ?? SITE_FAVICON;
- const href = useBaseUrl(icon);
-
- return (
- <Head>
- <link
- rel="icon"
- href={href}
- {...(icon.endsWith(".svg") ? { type: "image/svg+xml" } : {})}
- />
- </Head>
- );
-}
-
-export default function Root({
- children,
-}: {
- children: React.ReactNode;
-}): JSX.Element {
- return (
- <>
- <Favicon />
- {children}
- </>
- );
+ return <>{children}</>;
}
diff --git a/static/fonts/cinzel-latin-ext.woff2 b/static/fonts/cinzel-latin-ext.woff2
deleted file mode 100644
index 9ccb351..0000000
Binary files a/static/fonts/cinzel-latin-ext.woff2 and /dev/null differ
diff --git a/static/fonts/cinzel-latin.woff2 b/static/fonts/cinzel-latin.woff2
deleted file mode 100644
index b48b912..0000000
Binary files a/static/fonts/cinzel-latin.woff2 and /dev/null differ
diff --git a/static/img/kogito.svg b/static/img/kogito.svg
index 34a260f..2228a24 100644
--- a/static/img/kogito.svg
+++ b/static/img/kogito.svg
@@ -1 +1 @@
-<svg id="Layer_1" data-name="Layer 1" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 1024 1024"><defs><style>.kogito-cls-2{fill:#fff;}.kogito-cls-3{fill:#f5891f;}.kogito-cls-4{fill:#97d4e8;}</style></defs><title>kogito_icon_rgb_color_default</title><path fill="#085870" d="M929.37,30.5A70.31,70.31,0,0,0,872.19,1C868.09,1,738,23.67,738,23.67a70.15,70.15,0,0,0-48.1,33.25L668,93.77c-48.41-42.46-101.74-64.7-156-64.7S404.43,51.31,356,93.77L334.11,56.92A70.13,70.13,0,0,0,286,23.67S155.9,1,151. [...]
\ No newline at end of file
+<svg id="Layer_1" data-name="Layer 1" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 1024 1024"><defs><style>.cls-1{fill:#085870;}.cls-2{fill:#fff;}.cls-3{fill:#f5891f;}.cls-4{fill:#97d4e8;}</style></defs><title>kogito_icon_rgb_color_default</title><path class="cls-1" d="M929.37,30.5A70.31,70.31,0,0,0,872.19,1C868.09,1,738,23.67,738,23.67a70.15,70.15,0,0,0-48.1,33.25L668,93.77c-48.41-42.46-101.74-64.7-156-64.7S404.43,51.31,356,93.77L334.11,56.92A70.13,70.13,0,0,0,286,23.67S155.9,1,151.8 [...]
\ No newline at end of file
diff --git a/static/img/kogito/hero-background.svg b/static/img/kogito/hero-background.svg
deleted file mode 100644
index f40d01b..0000000
--- a/static/img/kogito/hero-background.svg
+++ /dev/null
@@ -1,12 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" width="2619" height="884" viewBox="0 0 2619 884">
- <defs>
- <style>
- .cls-1 {
- opacity: 0.5;
- mix-blend-mode: multiply;
- }
- </style>
- </defs>
- <image id="hero_background_element" data-name="hero background element" x="804" y="-432" width="1794" height="1223" xlink:href="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAABwIAAATHCAYAAADu57OzAAAgAElEQVR4nOzdD7Cs513Y9+fq35WMiGz8BxmbqPwztpCDXVzUTkixPaeGCY7JH4iYUOi0DS1SOowyTUb2dJrpZDo1SqZFSSa+NB5I+ZMExU5CiE2Je8YRDJmOaRhjdEc2GYxRJFvXNsY2XJCELd3O3rvP1Z5zds/uvu/7PO/z5/OZuXN1zx6fPed91nt29/v+nj0TAGBCF++/7ZYQwntCCH/75vse/TnHlrlcvP+2G0II7woh/MLN9z16zkIAAHDcwcHB3SGEbw8hfPfh4eEfnfgEyOTg4OAtIYS/ [...]
- <image id="logo_watermark" data-name="logo watermark" class="cls-1" x="-111" y="-156" width="861" height="1022" xlink:href="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAA10AAAP+CAYAAADw83UfAAAgAElEQVR4nOzdedAlxXnv+R/0SrPvidjFJiCF2BG72CVLsi3b8ibbknV1JZct29czEZ6JmH/mn4mYOzFxr8eWXdptydo3hCRA7PsmQAhIse/NUg1NL0A3vfdENs9pHU6d9+2zn8qq7yfixPtSdfqlKuucynwqM5/cTg2Rh2KepD0l7WU/d5a0k70W2StaaD83SXpd0gpJr0paaj/ja3nm3camlB0AAACgt9rUcyTtbu3p9rb1bta+3t7eusZ+rrbXG/Z6vb1tnXm3vgkFW8ugKw/FfEn7STpA0jsk7W8f [...]
-</svg>
diff --git a/static/img/kogito/homepage_graphic_1.png b/static/img/kogito/homepage_graphic_1.png
deleted file mode 100644
index c69fbb0..0000000
Binary files a/static/img/kogito/homepage_graphic_1.png and /dev/null differ
diff --git a/static/img/kogito/homepage_graphic_1@2x.png b/static/img/kogito/homepage_graphic_1@2x.png
deleted file mode 100644
index 3045b97..0000000
Binary files a/static/img/kogito/homepage_graphic_1@2x.png and /dev/null differ
diff --git a/static/img/kogito/homepage_graphic_2.png b/static/img/kogito/homepage_graphic_2.png
deleted file mode 100644
index 3ecd045..0000000
Binary files a/static/img/kogito/homepage_graphic_2.png and /dev/null differ
diff --git a/static/img/kogito/homepage_graphic_2@2x.png b/static/img/kogito/homepage_graphic_2@2x.png
deleted file mode 100644
index 36d3000..0000000
Binary files a/static/img/kogito/homepage_graphic_2@2x.png and /dev/null differ
diff --git a/static/img/kogito/homepage_graphic_3.png b/static/img/kogito/homepage_graphic_3.png
deleted file mode 100644
index 65b0508..0000000
Binary files a/static/img/kogito/homepage_graphic_3.png and /dev/null differ
diff --git a/static/img/kogito/homepage_graphic_3@2x.png b/static/img/kogito/homepage_graphic_3@2x.png
deleted file mode 100644
index 1b03e70..0000000
Binary files a/static/img/kogito/homepage_graphic_3@2x.png and /dev/null differ
diff --git a/static/img/navbar-logo.svg b/static/img/navbar-logo.svg
index 235d015..14de23f 100644
--- a/static/img/navbar-logo.svg
+++ b/static/img/navbar-logo.svg
@@ -1 +1 @@
-<svg width="50px" height="50px" id="Layer_1" data-name="Layer 1" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 1024 1024"><defs><style>.kie-cls-1{fill:#f5891f;}.kie-cls-2{fill:#97d4e8;}.kie-cls-3{fill:#fff;}.kie-cls-4{fill:#085870;}</style></defs><title>kie_icon_rgb_fullcolor_default</title><path class="kie-cls-1" d="M921.17,381.72V280.19l-251.84,85.9a188.74,188.74,0,0,0-102.28,96.54l-46.6,101.14,45.25,30.1L512,719.41,458.29,593.87l45.26-30.1L456.94,462.63a188.62,188.62,0,0,0-101.47-96 [...]
\ No newline at end of file
+<svg width="50px" height="50px" id="Layer_1" data-name="Layer 1" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 1024 1024"><defs><style>.cls-1{fill:#f5891f;}.cls-2{fill:#97d4e8;}.cls-3{fill:#fff;}.cls-4{fill:#085870;}</style></defs><title>kie_icon_rgb_fullcolor_default</title><path class="cls-1" d="M921.17,381.72V280.19l-251.84,85.9a188.74,188.74,0,0,0-102.28,96.54l-46.6,101.14,45.25,30.1L512,719.41,458.29,593.87l45.26-30.1L456.94,462.63a188.62,188.62,0,0,0-101.47-96.22l-252.65-81v96.29 [...]
\ No newline at end of file
diff --git a/static/img/sonataflow.svg b/static/img/sonataflow.svg
index 8a371c3..daa6cf6 100644
--- a/static/img/sonataflow.svg
+++ b/static/img/sonataflow.svg
@@ -1 +1 @@
-<?xml version="1.0" encoding="UTF-8"?><svg id="Layer_1" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 235.66 235.66"><defs><style>.sf-cls-1{fill:none;stroke:#085870;stroke-miterlimit:10;stroke-width:4.59px;}.sf-cls-2{fill:#97d4e8;}.sf-cls-2,.sf-cls-3,.sf-cls-4,.sf-cls-5,.sf-cls-6{stroke-width:0px;}.sf-cls-3{fill:#085870;}.sf-cls-4{fill:#15aae2;}.sf-cls-5{fill:#f5891f;}.sf-cls-6{fill:#fff;}</style></defs><circle class="sf-cls-1" cx="117.83" cy="117.83" r="115.53"/><circle class="sf-cls- [...]
\ No newline at end of file
+<?xml version="1.0" encoding="UTF-8"?><svg id="Layer_1" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 235.66 235.66"><defs><style>.cls-1{fill:none;stroke:#0d5971;stroke-miterlimit:10;stroke-width:4.59px;}.cls-2{fill:#94d2e5;}.cls-2,.cls-3,.cls-4,.cls-5,.cls-6{stroke-width:0px;}.cls-3{fill:#0d5971;}.cls-4{fill:#15aae2;}.cls-5{fill:#f38821;}.cls-6{fill:#fff;}</style></defs><circle class="cls-1" cx="117.83" cy="117.83" r="115.53"/><circle class="cls-2" cx="117.73" cy="117.66" r="91.71"/>< [...]
\ No newline at end of file
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org