mahara-contributors team mailing list archive

[Kristina Hoeppner <1364000@xxxxxxxxxxxxxxxxxx>]

Thank you for the clarification, Luca. So basically, you'd disallow
users to create their own skins and they would only be able to choose
from the existing skins. As far as I can see, you'd even want to
restrict this further to only be able to use skins that were created by
a site admin.

Currently, we do not have the possibility to create institution skins.
So these would need to be implemented as well because if you have a
Mahara instance that has multiple institutions set up, they would need
to be able to select the institution skins and not only the site skins
as those may be based on a different theme.

In the short term, you could set up multiple themes and enable "page
themes" so that your users can select those for their pages, and then
disable skins.

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1364000

Title:
  Offer a set of skins, preventing uncontrolled growth

Status in Mahara ePortfolio:
  Confirmed

Bug description:
  Please consider the following feature request.

  Regarding skins, in Mahara 1.9, there are basically three options.

  Disallowing everything.
  Allowing everything.
  Disallowing everything theme-wide.

  I would like to propose a middle way in which a institutional designer
  would prepare some skins (which are in itself different, but adhere to
  the institution's CI/CD) the user could chose from. The user could not
  freely create and modify everything but all the same spice up and
  distinguish her/his own sites.

  Best regards

  Luca

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1364000/+subscriptions