Articles (#395)

* articles section

* Articles section updated

---------

Co-authored-by: Kevin Burnett <18027+burnettk@users.noreply.github.com>

docs/appendices/articles.md

@@ -0,0 +1,47 @@
+# Articles ![data_input](images/articles.png) 
+
+**[#1 - Build your own Low-Code Business Applications with SpiffWorkflow](https://medium.com/@danfunk/build-your-own-low-code-business-applications-with-spiffworkflow-1d0730acc1f3)**
+
+This article introduces SpiffWorkflow as a low-code application development tool using flow-chart diagrams. It emphasizes the involvement of clients in the architectural decision-making process and highlights the use of BPMN diagrams, user tasks, script tasks, and exclusive gateways. The article concludes by showcasing a Python code example for loading and executing BPMN diagrams with SpiffWorkflow.
+
+----
+
+**[#2 - SpiffWorkflow, A New Hope](https://medium.com/@danfunk/spiffworkflow-a-new-hope-3f0c1dc72adb)**
+
+SpiffWorkflow empowers non-coders to control app logic using flow-chart diagrams. It emphasizes collaboration, integration, and future goals like custom diagram tools and process management. The article introduces components of the system and invites reader involvement.
+
+----
+
+**[#3 - Understanding BPMN’s Data Objects with SpiffWorkflow](https://medium.com/@danfunk/understanding-bpmns-data-objects-with-spiffworkflow-26e195e23398)**
+
+This article explains BPMN Data Objects and their implementation in the SpiffWorkflow project. It covers the default data flow behavior, the use of Data Objects for controlling data access, and the benefits of using them. The article also mentions data transformations and the two types of data in SpiffWorkflow. It concludes with information on upcoming releases and encourages reader involvement.
+
+----
+
+**[#4 - Understanding BPMN Messages](https://medium.com/@danfunk/understanding-bpmn-messages-7b0fee2d6a81)**
+
+This article explores BPMN 2.0 Messages and their implementation in the SpiffWorkflow project. It covers concepts like messages, collaborations, and correlations in BPMN diagrams. The article discusses changes made to SpiffWorkflow applications to support message handling and communication between processes. It emphasizes the importance of maintaining correlation consistency and highlights the benefits of enabling communication between complex systems.
+
+----
+
+**[#5 - Getting Started with SpiffArena](https://medium.com/@danfunk/getting-started-8ec59afe3a48)**
+
+The article offers a tutorial on using SpiffArena to create and run executable SpiffWorkflow diagrams. It covers installation, building a simple workflow process using BPMN diagrams and tasks, and concludes with shutting down the application. The tutorial highlights the potential of SpiffWorkflow in enhancing transparency and collaboration in complex business processes.
+
+----
+
+**[#6 - The Low Code Wall](https://medium.com/@danfunk/the-low-code-wall-fa2e3476cc10)**
+
+The article discusses low-code and no-code tools for software development, emphasizing the challenges and pitfalls that may arise. It suggests considering open standards, collaboration with IT departments, and introduces SpiffArena as an open-source alternative that encourages collaboration and utilizes visual tools and familiar interfaces.
+
+----
+
+**[#7 - SpiffArena, the low-code visual workflow builder, awaits you like a clean canvas…](https://medium.com/@danfunk/spiffarena-the-low-code-visual-workflow-builder-awaits-you-like-a-clean-canvas-e7b9bd20ae71)**
+
+SpiffArena is a browser-based tool that allows you to create flow-chart-like diagrams for automating business workflows. It offers features like form builders, application connections, timers, custom APIs, and robust permissions. SpiffArena combines BPMN and Python to provide a powerful and configurable solution.
+
+----
+
+**[#8 - A Visual Workflow Library for Python](https://medium.com/@danfunk/a-visual-workflow-library-for-python-d19e1387653)**
+
+SpiffWorkflow is a Python library that simplifies complex business logic by using BPMN diagrams, allowing non-developers to make changes to application flows. It improves communication within teams, increases contributions, and adapts to changing requirements. Visual software development environments like SpiffWorkflow are the future of solving complex problems.

docs/appendices/bpmn_references.md

@@ -1,16 +1,21 @@
 # Decision Tables
 
+```{tip} 
+:class: note
+🧾 Read more about Data Objects [here](https://medium.com/@danfunk/understanding-bpmns-data-objects-with-spiffworkflow-26e195e23398).
+```
+
 DMN tables are powerful tools for modeling and implementing business rules and decision logic. They allow you to define rules and their associated conditions and actions in a structured manner. By evaluating the conditions in each rule, the DMN engine can determine which rules are triggered based on the provided inputs and execute the corresponding actions. This provides a flexible and configurable approach to decision-making in various scenarios.
 
 A DMN (Decision Model and Notation) table consists of several components that help define the decision logic and structure the decision-making process. The main components of a DMN table are:
 
 ## DMN Components
 
-- ***Input Variables:**** These are the variables that represent the information or data used as input for the decision. Each input variable is typically represented as a column in the table. Multiple columns represent multiple input variables.
-- ***Conditions:**** Conditions specify the criteria or constraints that need to be evaluated for each input variable. They define the rules or expressions that determine when a particular decision rule should be triggered. Conditions are usually represented in the "When" column of the table.
-- ***Actions or Expressions:**** Actions or expressions define the operations or calculations that are executed when a specific rule is triggered. They represent the logic associated with the decision outcome and are represented in the same row as the conditions in the table.
-- ***Decision Rules:**** Decision rules are the individual rows in the DMN table. Each rule represents a specific combination of conditions and actions that define the behavior or logic for a particular scenario. Decision rules combine the input conditions and output actions in a structured manner.
-- ***Hit Policy:**** The hit policy determines how the decision engine selects or combines the applicable decision rules when multiple rules are triggered. It defines the behavior for resolving conflicts or overlaps between rules. Common hit policies include "First," "Unique," "Priority," "Any," and "Collect."
+- **Input Variables:** These are the variables that represent the information or data used as input for the decision. Each input variable is typically represented as a column in the table. Multiple columns represent multiple input variables.
+- **Conditions:** Conditions specify the criteria or constraints that need to be evaluated for each input variable. They define the rules or expressions that determine when a particular decision rule should be triggered. Conditions are usually represented in the "When" column of the table.
+- **Actions or Expressions:** Actions or expressions define the operations or calculations that are executed when a specific rule is triggered. They represent the logic associated with the decision outcome and are represented in the same row as the conditions in the table.
+- **Decision Rules:** Decision rules are the individual rows in the DMN table. Each rule represents a specific combination of conditions and actions that define the behavior or logic for a particular scenario. Decision rules combine the input conditions and output actions in a structured manner.
+- **Hit Policy:** The hit policy determines how the decision engine selects or combines the applicable decision rules when multiple rules are triggered. It defines the behavior for resolving conflicts or overlaps between rules. Common hit policies include "First," "Unique," "Priority," "Any," and "Collect."
 
 ## Hit Policy
 

docs/in_depth_topics/data_objects.md

@@ -1,5 +1,10 @@
 # Data Objects
 
+```{tip} 
+:class: note
+🧾 Read more about Data Objects [here](https://medium.com/@danfunk/understanding-bpmns-data-objects-with-spiffworkflow-26e195e23398).
+```
+
 In BPMN (Business Process Model and Notation), a data object represents the information or data used and produced by activities within a business process. It represents the data elements or artifacts that are relevant to the process and provides a way to model the flow of data through the process.
 They help in clarifying the data flow and dependencies within the process, making it easier to understand how information is utilized and transformed throughout the process execution.
 

docs/index.md

@@ -59,6 +59,7 @@ installation_integration/permission_url.md
 :maxdepth: 3
 :caption: Appendices
 appendices/bpmn_references.md
+appendices/articles.md
 glossary/glossary.md
 learn_basics/bpmn_terminology.md