Hi Kristina, I agree having a separate site-admin account vs user account of the person who is admin would be best practice. For large Universities site- admin is often a dedicated role not involved in developing content anyway, so it's more often seen in smaller institutes (I'm struggling to find the right term due to the Mahara specific use of Institution!) with a single learning tech responsible for everything - in which case it makes sense to have separate site-admin and creator/facilitator identities.
It would be useful to have the site-admin ability to override institutional themes with anything installed at site level, though it may be better to require the theme is enabled at institutional level if restrictions had been imposed, so admins would need to agree internally what is allowed (good practice), but I can anticipate the arguement "it's just for this group we don't want everyone to be able to use it" so don't know if that's a viable solution. When using csv - yes, you would want to choose theme by the display name as that would be much less confusing. Group admins won't know the actual theme name if they only have front-end access, and the institution/site default theme would be used if nothing is specified. I often find picking the right theme is a bit trial and error - until the content exists it's not always clear which theme suits best unless you're after a specific colour/brand look for those pages, so while it's useful to have the option at setup it's maybe more useful to be able to apply the change retrospectively. I guess the only other area to consider alongside this is what to do about skins? If they are enabled then the same rule should probably apply to them as well as themes. I appreciate that could add another menu and layer of complexity, but skins probably allow much more local group flexibility than installed themes simply because they are so readily customised. Regards, Gordon. -- 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/1488463 Title: group wide theme Status in Mahara: Confirmed Bug description: Hi, As a feature enhancement it would be useful if there was an option in group admin settings to specify a theme for all pages within the group. This is really important for sites where the default institutional theme doesn't work well with the content of a specific group, but currently the only way to deal with that is to edit every page manually to apply the theme - having to change 20-30 pages (or more) is time consuming - not to mention having to remember to make the change for every new page, so being able to set a default theme at a group level would be a logical improvement. In anticipation of the question - yes I think it would be fine to override this default manually on a per-page basis later, but being able to set all pages to a consistent look from the group admin settings would be extremely useful. Regards, Gordon. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1488463/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~mahara-contributors Post to : [email protected] Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
