Difference between revisions of "PKC Applications Workflow"

Latest revision as of 14:28, 25 July 2021

TO BE DEPRECATED: When you see this, please consider moving the logic model below from Template:Logic Model to Template:LogicModel

1. Context	PKC serves as the infrastructure of all applications. For each application, PKC needs to be further configured or extended to cater to application needs. So the different versions of extensions
2. Goal	Manage the current version and intended version of an application.
3. Success Criteria
4. Outputs	5. Process	6. Inputs
A page of all applications a page for current application which contains goals and features. The workflow to switch between different applications.
7. Boundary Conditions

PKC Application Version
Follow Docker Workflow to customize the software and align with application goal.

@@ Line 1: / Line 1: @@
+{{Logic Model
-= Application: thewiki.us =
+|context=
+# [[PKC]] serves as the infrastructure of all applications. For each application, PKC needs to be further configured or extended to cater to application needs. So the different versions of extensions
-* The Localsettings.php shows all the configurations
+|goal=
+# Manage the current version and intended version of an application.
-== All extensions to install in thewiki.us ==
+|criteria=
+|outputs=
+# A page of all applications
+# a page for current application which contains goals and features.
+# The workflow to switch between different applications.
+|process=
+|inputs=
+|boundaries=
+}}
+[[PKC Applications Workflow/Process]]
+== All Applications ==
+* [[PKC Application Version]]
 * Follow [[Docker Workflow]] to customize the software and align with application goal.