Table of Contents



Overview#

Quick notes for now, will refine into documentation
—Dave Koelmeyer, 2016-04-12T10:35:36.762Z

Idea grab-bag#

  • Documenting JSPWiki's clear strengths, use cases, target audience(s).
  • Friendly user community.
  • Improving the appearance of the JSPWikiSites page to be more visually attractive, perhaps with thumbnail icons – something other than a long listing of text.
  • What are our specific advantages compared to alternate wiki engines?
  • Increasing our release cadence such that fixes are more visible. Witness Mozilla Thunderbird.
  • Marketing aside, where does JSPWiki come up short compared to alternate wiki engines?
  • Blog. A tip or feature of the week (especially for Haddock) is an easy way to generate content. Need to determine a blog home (Apache-hosted would be quickest and easiest).
  • Also for blog content, maybe a feature on more obscure JSPWiki features, like categories, little-known plugins, JSPWiki variables?
  • Reach out (somehow) to folks running old JSPWiki installations – how can we persuade them to upgrade and switch to Haddock? Sites running the legacy skins may work against us in marketing a modern wiki with a fresh look and feel.
  • A logo/brand refresh? Ideally we have a designer work on this, perhaps via a community contribution. Cover photos for social networks, maybe a new logo for JSPWiki itself (there are some historical emails on this from a few years back – locate and review).
  • Focusing our marketing message on attracting businesses and organisations (not exclusively, mind) might help with raising our notability (e.g. for re-establishing a Wikipedia presence, industry articles.)

Collate all the discussion on the users mailing list around the "Open Discussion - How to increasing JSPWiki publicity" thread and sum up/document the various comments.