You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Module store

For 4.3 the goal is to to provide at least a listing of existing modules integrated in the admin interface, with links for manual download. It may just be an iframe that loads a page from magnolia.info, we may want to just to add a launcher page to pass all the needed information about magnolia version and already installed modules. A nice/cheap addon could be a page that lists currently installed modules (this one generated directly by magnolia).

This is an idea of how it could look:


The first page will be a simple listing of modules, a cleaned up version of the matrix on the wiki.
For each module we will display:

  • icon
  • name
  • description
  • author
  • update date
  • version
  • status (installed, not installed, upgradable)
  • license (probably it's enough to display this in the detail page?)

Clicking on a module will bring to a detail page:

Here we should have a screenshot, long description, licensing/price info, link to download and to original website.

What we could skip for this first release (note that everything can be upgraded "server side" in the following months, but we just have to have a good status to include the menu and launcher soon in 4.3):

  • user rating/commenting
  • categorization
  • sorting? (do we sort alphabetically?)
  • compatibiliy matrix/versions: since this will only we available for 4.3 we can just add only modules wich works with magnolia 4.3. Before the next release (if any, before 5.0) we will have to implement a compatibility matrix (see the atlassian plugin studio as an example)

The server-side part will obviously be implemented as a set of magnolia templates, for the first run the list of modules will have to be centrally managed, we could ask people who added their plugin to the wiki for details.

Questions:

  • do we lists only real *modules* or also other tools/libraries (for example the "Magnolia criteria query" lib)?
  • do we lists enterprise modules too, with a link to the "purchase enterprise" instead than a download? It could really be useful to make more clear what users can get by upgrading to enterprise
  • No labels