Sales Cycle: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
== Distinct Namespace == | == Distinct Namespace == | ||
Using the '''[[mw:Extension:Flex Diagrams|Extension:Flex Diagrams]]''' extension<ref>Flex Diagrams does allow you to create 5 different types of diagrams</ref>, each diagram must be handled in it's own namespace - where it's really a custom content model. This means that '''no other markup''' is allowed. So, you can't use wikitext (e.g. Categories) at all. A somewhat useful if not confusing by-product of this is that the source code of the diagram is displayed inline with the diagram when reading the page. | Using the '''[[mw:Extension:Flex Diagrams|Extension:Flex Diagrams]]''' extension<ref>Flex Diagrams does allow you to create 5 different types of diagrams: | ||
# BPMN diagrams (using the bpmn-js library) | |||
# Gantt charts (using the DHTMLX Gantt JS library) | |||
# DOT graphs, also known as Graphviz graphs (using the Viz.js library) | |||
# Mermaid diagrams | |||
# Drawio/diagrams.net diagrams | |||
The Flex Diagrams extension is most notable for its ability to do BPMN and Drawio diagrams. | |||
</ref>, each diagram must be handled in it's own namespace - where it's really a custom content model. This means that '''no other markup''' is allowed. So, you can't use wikitext (e.g. Categories) at all. A somewhat useful if not confusing by-product of this is that the source code of the diagram is displayed inline with the diagram when reading the page. | |||
In order to embed the diagram into a wiki page, you then use the extension's <code>#display_diagram</code> parser function. | In order to embed the diagram into a wiki page, you then use the extension's <code>#display_diagram</code> parser function. | ||