Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document all UI settings you can change in config.json #7174

Closed
WebFreak001 opened this issue Aug 16, 2018 · 8 comments
Closed

Document all UI settings you can change in config.json #7174

WebFreak001 opened this issue Aug 16, 2018 · 8 comments
Labels
A-Documentation P1 T-Task Tasks for the team like planning

Comments

@WebFreak001
Copy link

The default UI settings should be changable per deployed riot instance. Right now only the theme is changable but I would like to enable/disable by default some of the extra checkboxes in there like gif playback, url preview, timestamps, etc.

For our instance we want to reduce extra information like profile pic changes, etc. as much as possible to not confuse our users, because they are not very tech-savvy.

@t3chguy
Copy link
Member

t3chguy commented Aug 16, 2018

Every setting default can be changed in config just how to do so is at present undocumented. Pinging @turt2live

@WebFreak001
Copy link
Author

@t3chguy
Copy link
Member

t3chguy commented Aug 16, 2018

Yes any of those can be tweaked in config.json just the docs on how are missing from https://github.com/matrix-org/matrix-react-sdk/blob/master/docs/settings.md

@WebFreak001 WebFreak001 changed the title Ability to change default UI settings of new users Document all UI settings you can change in config.json Aug 17, 2018
@lampholder lampholder added T-Task Tasks for the team like planning P2 A-Documentation labels Aug 20, 2018
@tulir
Copy link
Contributor

tulir commented Feb 4, 2019

Duplicate of #6791?

@jryans
Copy link
Collaborator

jryans commented Feb 4, 2019

Yes, this seems to be a duplicate of #6791, but this one seems to have more detail and is easier to find, so I think I'll close #6791 in favor of this one.

@WebFreak001
Copy link
Author

can we change this to p1 then because the other issue was p1?

@jryans jryans added P1 and removed P2 labels Feb 4, 2019
@jryans
Copy link
Collaborator

jryans commented Feb 4, 2019

Sure, updated priority.

@turt2live
Copy link
Member

Closing in favour of #8449

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Documentation P1 T-Task Tasks for the team like planning
Projects
None yet
Development

No branches or pull requests

6 participants