MediaWiki/Marketing: Difference between revisions

Revision as of 15:50, 2 May 2023

For "Enterprise MediaWiki" we need a number of initiatives to be completed in order to realize the goal of effortlessly penetrating the market, selling the product and services, as well as servicing customers

Elevator pitch[edit | edit source]

What is the product? "Knowledge Management" software is probably the easiest definition. However, with SMW + carefully curated extensions + 'packages' that are available via Page Exchange we need to assemble industry solutions that are available 'out of the box' (See Inspiration -> Installation Profiles below).

Features list[edit | edit source]

An improved version of Features

Example of translating raw configurations available in the software and mapping those into a "feature": https://www.mywikis.com/privacy MediaWiki has config settings. ENTERPRISE MediaWiki has "Privacy" profiles

Dedicated Contractual Support[edit | edit source]

Inspiration[edit | edit source]

Acquia is an example org that does what we need to do

Installation Profiles[edit | edit source]

Drupal has installation profiles that define a 'pre-packaged' setup of the raw CMS + modules + settings to address a particular type of solution. Similarly, we need to define solutions to specific use cases.

Content Needs[edit | edit source]

Content that addresses basic questions like "Why use this vs. my already paid M$ license for SharePoint?"

@@ Line 1: / Line 1: @@
-Need elevator pitch for "Enterprise MediaWiki"
+For "Enterprise MediaWiki" we need a number of initiatives to be completed in order to realize the goal of effortlessly penetrating the market, selling the product and services, as well as servicing customers
-Product definition: "Knowledge Management" software is the first definition that we can land on.
-"Features" list
-Dedicated Contractual Support
+== Elevator pitch ==
+* What is the product? "Knowledge Management" software is probably the easiest definition. However, with SMW + carefully curated extensions + 'packages' that are available via Page Exchange we need to assemble industry solutions that are available 'out of the box' (See Inspiration -> Installation Profiles below).
-Acquia is an example org that does what we need to do
-Content that addresses basic questions like "Why use this vs. my already paid M$ license for SharePoint?"
+== Features list ==
+An improved version of [[Features]]
+Example of translating raw configurations available in the software and mapping those into a "feature": https://www.mywikis.com/privacy MediaWiki has config settings. ENTERPRISE MediaWiki has "Privacy" profiles
+== Dedicated Contractual Support ==
+== Inspiration ==
-== Installation Profiles ==
+Acquia is an example org that does what we need to do
-Drupal has installation profiles, and similarly, we need to setup configurations that define solutions to specific use cases.
-Example of configuration mapping into "feature"
+=== Installation Profiles ===
-https://www.mywikis.com/privacy
+Drupal has installation profiles that define a 'pre-packaged' setup of the raw CMS + modules + settings to address a particular type of solution. Similarly, we need to define solutions to specific use cases.
-MediaWiki has config settings. ENTERPRISE MediaWiki has "Privacy" profiles
+== Content Needs ==
+Content that addresses basic questions like "Why use this vs. my already paid M$ license for SharePoint?"
 [[Category:MediaWiki]]
 [[Category:Enterprise MediaWiki]]