Sales Cycle: Difference between revisions

From Freephile Wiki
No edit summary
reorder content; tag
 
(3 intermediate revisions by one other user not shown)
Line 1: Line 1:
== Distinct Namespace ==
This page uses the [https://www.mediawiki.org/wiki/Extension:Mermaid mermaid extension] compared with the [[mw:Extension:Flex Diagrams]] to draw the same flow chart from simple markup, both leveraging the Mermaid.js diagramming library.
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.
 
In order to embed the diagram into a wiki page, you then use the extension's <code>#display_diagram</code> parser function.
 
<pre>{{#display_diagram:Mermaid:Sales_Cycle}}</pre>
produces the following diagram from the source at [[Mermaid:Sales Cycle]]
 
{{#display_diagram:Mermaid:Sales_Cycle}}


== Diagram inline ==
== Diagram inline ==
Line 57: Line 49:




This page uses the [https://www.mediawiki.org/wiki/Extension:Mermaid mermaid extension] compared with the [[mw:Extension:Flex Diagrams]] to draw the flow chart from simple markup.
== 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:


== Tools ==
# 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


Use the [https://mermaid-js.github.io/mermaid-live-editor/ live (javascript) Mermaid Editor here]
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.
 
<pre>{{#display_diagram:Mermaid:Sales_Cycle}}</pre>
produces the following diagram from the source at [[Mermaid:Sales Cycle]]
 
{{#display_diagram:Mermaid:Sales_Cycle}}


There are a ton of integrations for editing the Mermaid script language in your content platform of choice. See https://mermaid.js.org/ecosystem/integrations-community.html


[[Category:Sales]]
{{References}}
[[Category:Company]]
[[Category:Diagrams]]

Latest revision as of 14:03, 16 June 2025

This page uses the mermaid extension compared with the mw:Extension:Flex Diagrams to draw the same flow chart from simple markup, both leveraging the Mermaid.js diagramming library.

Diagram inline[edit]

Using the Mermaid extension, and its #mermaid parser function, you can create diagrams right in your page.

The syntax after the parser function is passed to Mermaid.js for interpretation.

{{#mermaid:graph TD;
 A[Prospecting] -->|Original/Initial Contact| B(Contract Award / Purchase / Agreement of Terms)
 B --> C{Let me think}
 C -->|Qualifying| D[Qualified]
 C -->|Presentation/Demonstration| E[Comfortable]
 C -->|Follow-through Proposal/Value Proposition| F[fa:fa-car Incentivized]
 D --> G(Document Buying Cycle or Itch Cycle)
 E --> G
 F --> G
 G --> H(Negotiations)
 G --> I(Overcome Objections)
 G --> J(Establish Deliverables)
 G --> K(Maintain Contact)
 H --> L(Obtain Referrals)
 I --> L(Obtain Referrals)
 J --> L(Obtain Referrals)
 K --> L(Obtain Referrals)
 L --> A}}
 
produces


Distinct Namespace[edit]

Using the Extension:Flex Diagrams extension[1], 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 #display_diagram parser function.

{{#display_diagram:Mermaid:Sales_Cycle}}

produces the following diagram from the source at Mermaid:Sales Cycle

graph TD; A[Prospecting] -->|Original/Initial Contact| B(Contract Award / Purchase / Agreement of Terms) B --> C{Let me think} C -->|Qualifying| D[Qualified] C -->|Presentation/Demonstration| E[Comfortable] C -->|Follow-through Proposal/Value Proposition| F[fa:fa-car Incentivized] D --> G(Document Buying Cycle or Itch Cycle) E --> G F --> G G --> H(Negotiations) G --> I(Overcome Objections) G --> J(Establish Deliverables) G --> K(Maintain Contact) H --> L(Obtain Referrals) I --> L(Obtain Referrals) J --> L(Obtain Referrals) K --> L(Obtain Referrals) L --> A


References[edit]

  1. Flex Diagrams does allow you to create 5 different types of diagrams:
    1. BPMN diagrams (using the bpmn-js library)
    2. Gantt charts (using the DHTMLX Gantt JS library)
    3. DOT graphs, also known as Graphviz graphs (using the Viz.js library)
    4. Mermaid diagrams
    5. Drawio/diagrams.net diagrams
    The Flex Diagrams extension is most notable for its ability to do BPMN and Drawio diagrams.