##// END OF EJS Templates
docs/usage: rework and rename section 'Visual settings in admin pannel'...
Thomas De Schampheleire -
r4963:daa83b2d default
parent child Browse files
Show More
@@ -119,47 +119,32 b' clone url in summary page.'
119 119
120 120
121 121
122 Visual settings in admin pannel
123 -------------------------------
124
122 Specific features configurable in the Admin settings
123 ----------------------------------------------------
125 124
126 Visualisation settings in Kallithea settings view are extra customizations
127 of server behavior. There are 3 main sections in the settings.
125 In general, the Admin settings should be self-explanatory and will not be
126 described in more detail in this documentation. However, there are a few
127 features that merit further explanation.
128 128
129 General
130 ~~~~~~~
129 Repository extra fields
130 ~~~~~~~~~~~~~~~~~~~~~~~
131 131
132 The `Use repository extra fields` option allows to set a custom fields
133 for each repository in the system. Each new field consists of 3
134 attributes: ``field key``, ``field label``, ``field
135 description``. Example usage of such fields would be to define company
136 specific information into repositories, e.g., defining a
137 ``repo_manager`` key that would give info about a manager of each
138 repository. There's no limit for adding custom fields. Newly created
139 fields are accessible via API.
140
141 The `Show Kallithea version` option toggles displaying the exact
142 Kallithea version in the footer
143
132 In the `Visual` tab, there is an option `Use repository extra
133 fields`, which allows to set custom fields for each repository in the system.
134 Each new field consists of 3 attributes: ``field key``, ``field label``,
135 ``field description``.
144 136
145 Dashboard items
146 ~~~~~~~~~~~~~~~
147
148 Number of items in main page dashboard before pagination is displayed.
149
150
151 Icons
152 ~~~~~
153
154 Show public repo icon / Show private repo icon on repositories - defines if
155 public/private icons should be shown in the UI.
156
137 Example usage of such fields would be to define company-specific information
138 into repositories, e.g., defining a ``repo_manager`` key that would give info
139 about a manager of each repository. There's no limit for adding custom fields.
140 Newly created fields are accessible via the API.
157 141
158 142 Meta-Tagging
159 143 ~~~~~~~~~~~~
160 144
161 With this option enabled, special metatags that are recognisible by Kallithea
162 will be turned into colored tags. Currently available tags are::
145 In the `Visual` tab, option `Stylify recognised meta tags` will cause Kallithea
146 to turn certain meta-tags, detected in repository and repository group
147 descriptions, into colored tags. Currently recognised tags are::
163 148
164 149 [featured]
165 150 [stale]
General Comments 0
You need to be logged in to leave comments. Login now