Browsing English (United Kingdom) translation

73.

remove my access notification

74.

.. image:: images/remove_portfolio_access.*

75.

|New in Mahara 22.10| :index:`Colour the address bar <pair: Tips; Colour address bar>`

76.

:index:`Some <single: New in Mahara 22.10; Colour address bar>` :index:`browsers <single: Theme; Colour address bar>` allow for websites to colourise the address bar for a more distinguished look. This is achieved via the *theme-color* meta tag that is available in a theme's ``themeconfig.php``.

77.

.. image:: images/theme_colour.*

78.

Screenshot of the 'Primary school' theme in Chrome on Android showing that the address bar is colourised in the theme's main colour blue

79.

This feature is only available in some browsers. A `compatibility chart <https://developer.mozilla.org/en-US/docs/Web/HTML/Element/meta/name/theme-color>`_ is available.

80.

|New in Mahara 22.10| :index:`Document customisations <pair: Tips; Document customisations>`

81.

:index:`Documentation <single: New in Mahara 22.10; Document customisations>` is important for any software, especially when you make customisations. Documentation can live in many different places, e.g. in a text document on a personal computer or a network drive, in a wiki, in a knowledge base, or directly in the repository where the code sits. Some of these places are more difficult to find than others, in particular for those new to a project.

82.

It is recommended to keep the documentation close to where the code sits so it can be found easily. Some people put it into the ``README`` file whereas others create separate files. Since Mahara comes with a ``README`` file for Mahara, adding project specific documentation to it would always result in conflicts. That's why there is a ``CUSTOMISATIONS`` file that can hold all of the client specific documentation.