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

Better room creation on-boarding with settings presets for most common use cases #1612

Open
3 tasks
trosel opened this issue Sep 24, 2019 · 2 comments
Open
3 tasks

Comments

@trosel
Copy link

trosel commented Sep 24, 2019

As a user, I don't want to fiddle with granular settings to create rooms for common reasons.

  • Create a json config file that assigns a name to a group of preset settings for a room
    • Determine most common room use cases for the initial config options. Eg:
      • Public Forum (not encrypted, history always visible, clear hierarchy of mods/admins)
      • Private Party (encrypted, history visible after someone joins, maybe just one admin)
      • Friend Hangout (encrypted, history always visible, democratic)
      • Broadcast Channel (not encrypted, nobody can post except for admins)
  • Create Metadata tags on rooms that allow for UI sorting of rooms based on presets (similar to 1-to-1 rooms are separate from groups today)
  • Create an onboarding UI flow for room creation
    1. Prompt the user to name the room
    2. Load preset settings options from the config file and let the users either choose one of the options or go fully manual
    3. Prompt the user to invite people to the room now (invite in UI or show them a URL link to the room), or do it later
@trosel
Copy link
Author

trosel commented Sep 24, 2019

@trosel
Copy link
Author

trosel commented Sep 27, 2019

See example templates in my comment here element-hq/element-web#2349 (comment)

@t3chguy t3chguy transferred this issue from element-hq/element-web May 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant