Difference between revisions of "MediaWiki/Marketing"

From Freephile Wiki
Jump to navigation Jump to search
(2 intermediate revisions by the same user not shown)
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
+
Rich posted this article about 'Application Rationalizations' which is a specific issue.
 +
https://www.mediawiki.org/wiki/MediaWiki_Application_Rationalizations
  
Content that addresses basic questions like "Why use this vs. my already paid M$ license for SharePoint?"
 
  
 +
== Features list ==
  
== Installation Profiles ==
+
An improved version of [[Features]]
Drupal has installation profiles, and similarly, we need to setup configurations that define solutions to specific use cases.
 
  
Example of configuration mapping into "feature"
 
  
https://www.mywikis.com/privacy
+
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
  
MediaWiki has config settings. ENTERPRISE MediaWiki has "Privacy" profiles
+
 
 +
== Dedicated Contractual Support ==
 +
 
 +
 
 +
== Inspiration ==
 +
 
 +
Compile a list of organizations that exemplify the '''right way to do it''' and then replicate that.
 +
 
 +
Acquia is an example org that does for Drupal what we need to do for MediaWiki
 +
 
 +
=== Installation Profiles ===
 +
 
 +
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 ==
 +
 
 +
# A new MWStake.org website Lex has worked on https://mwstakeorg.dataspects.com/wiki/Main_Page
 +
# Content that addresses basic questions like "Why use this vs. my already paid M$ license for SharePoint?"
  
 
[[Category:MediaWiki]]
 
[[Category:MediaWiki]]
 
[[Category:Enterprise MediaWiki]]
 
[[Category:Enterprise MediaWiki]]

Revision as of 12:31, 25 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).

Rich posted this article about 'Application Rationalizations' which is a specific issue. https://www.mediawiki.org/wiki/MediaWiki_Application_Rationalizations


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]

Compile a list of organizations that exemplify the right way to do it and then replicate that.

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

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]

  1. A new MWStake.org website Lex has worked on https://mwstakeorg.dataspects.com/wiki/Main_Page
  2. Content that addresses basic questions like "Why use this vs. my already paid M$ license for SharePoint?"