Open elizavetaRa opened 2 years ago
- feedback link (href, ariaLabel, description)
Customizing the href
is easy to implement via options
object in the config.json
. We can allow adding text for aria-label
and description
to that as well, but that won't be translatable then.
- tooltip help for "invite" searchfield (description text). The tooltip can be shown, if the description text exists.
IMO overriding text in the ui needs a concept first. Now starting to add overrides to some config or theme file and using that througout the code base will result in a big mess to be frank. :-/
More context: we currently use english text directly in the code, export that to transifex nightly, import translations from transifex nightly and store them in a json file (one per app). The english text is the key
in that json file / translations mapping and thus not stable (because it might be adjusted in the code at any time, e.g. because of typos, new better wording, etc). IMO we need a stable key for our translations. Then and only then it would be easy / easier to let strings be overridden via theming.
- Sidebar should have the possibility to inject content/extensions into the "Details" section (like cernbox@52bbf24e)
This one would deserve it's own ticket. ;-) This is one use case for a fine grained extension system we envision for web. The core team at ownCloud won't have time to work on that before our oCIS GA.
- tooltip help for "invite" searchfield (description text). The tooltip can be shown, if the description text exists.
If you can limit that requirements for just a handful of locations in the code then we can have a somewhat dirty patch here upstream.
- Sidebar should have the possibility to inject content/extensions into the "Details" section (like cernbox@52bbf24e)
Compromise at this point (also for the string adjustment above) could be that you introduce an eos
capability and we hardcode some stuff that will only be shown when eos=true
.
@elizavetaRa discussed internally again today, an additional option in the config.json would be better than a capability as it is only relevant for the web ui / has no implications for the backend or other clients.
It would be great to have the possibility to customize the following elements: