Difference between revisions of "PKC Applications Workflow"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
{{Logic Model | |||
|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. | |||
|goal= | |||
# Manage the requirement, design, implementation, and deployment of a certain application. | |||
|criteria= | |||
|outputs= | |||
# A workflow page. | |||
|process= | |||
|inputs= | |||
|boundaries= | |||
}} | |||
= Application: thewiki.us = | = Application: thewiki.us = | ||
Revision as of 13:14, 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 |
| ||
| 2. Goal |
| ||
| 3. Success Criteria | |||
| 4. Outputs | 5. Process | 6. Inputs | |
|
|
||
| 7. Boundary Conditions | |||
Application: thewiki.us
- The Localsettings.php shows all the configurations
All extensions to install in thewiki.us
- Follow Docker Workflow to customize the software and align with application goal.