Difference between revisions of "PageFlow"

From PKC
Jump to navigation Jump to search
 
(5 intermediate revisions by the same user not shown)
Line 7: Line 7:
Based on the description above, every page is a static data point, for the purpose of understanding, we can think of it as a node in a network that represents the so called [[site map]]. One possible way to visualize it is using a diagram composed of directed edges and nodes.
Based on the description above, every page is a static data point, for the purpose of understanding, we can think of it as a node in a network that represents the so called [[site map]]. One possible way to visualize it is using a diagram composed of directed edges and nodes.


 
<html>
[[wikipedia:Image:Sitemap_google.png]]
<img src="https://upload.wikimedia.org/wikipedia/commons/2/20/Sitemap_google.jpg" width="300" height="450" />
[[wikipedia:Image:Sitemap_google.jpg]]
</html>


PageFlow is our way to orient [[workflow]] for teams that have access to [[network-enabled]] [[PKC]] instances. PageFlow is a term defined here to help utilize features provided by [[wikipedia:Semantic MediaWiki|Semantic MediaWiki]].  
PageFlow is our way to orient [[workflow]] for teams that have access to [[network-enabled]] [[PKC]] instances. PageFlow is a term defined here to help utilize features provided by [[wikipedia:Semantic MediaWiki|Semantic MediaWiki]].  

Latest revision as of 03:33, 16 February 2022

Based on the notion of Universal Data Abstraction, all data content will be displayed using web pages for the purpose of data representation, and the relations between different data points are connected using Hyperlinks. This is our approach to implement a generalizable Data Workflow.

How to create a page

A page is one instance of a record in the Main namespace of PKC. The content of the page is usually encoded in wiki markdown syntax, but also allows the use of Lua programming language in the Module namespace. A page could either embed hyperlinks, include transclusion instructions in the format of magic words, and trigger functions defined in Module namespace.

Pages as Nodes

Based on the description above, every page is a static data point, for the purpose of understanding, we can think of it as a node in a network that represents the so called site map. One possible way to visualize it is using a diagram composed of directed edges and nodes.

<html> <img src="https://upload.wikimedia.org/wikipedia/commons/2/20/Sitemap_google.jpg" width="300" height="450" /> </html>

PageFlow is our way to orient workflow for teams that have access to network-enabled PKC instances. PageFlow is a term defined here to help utilize features provided by Semantic MediaWiki.

Particularly, we would love to help people utilize the following Special Pages:

  1. Special:CreateCategory
  2. Special:CreateForm
  3. Special:CreateProperty
  4. Special:Forms
  5. Special:CreateTemplate
  6. Special:MultiPageEdit
  7. Special:Properties

Other than Pages, we also consider two other forms of abstraction: Files, and Services.

Transporting data by moving Files

Kubernetes controls the data flow across Services