Thanks a lot of working on this. I’ve tested and it works great.
But I bring you here some suggestions for making it simpler to use. I am assuming the use-case where a staff member of the forum it not very familiar with the internals of BigBlueButton and the only previous experience he/she has is by using BigBlueButton’s interface for creating rooms (greenlight).
With that said, here are by suggestions:
-
Explain in original post how one creates “Start conference” buttons
After installing it took me quite a while to figure that to add a BigBlueButton button I needed to do it though the “options” (gear icon) in the text editor. Maybe mentioning that in the instructions could avoid some confuction. -
Make passwords easier to create
- buttons for generating random passwords: We all know people are lazy and they’ll probably pick a lazy password. So one might give the user an even lazier option that actually makes them more secure
- label the passwords as “(optional)” (alternative solution) and when that is not set, generate a random password. But the user should still be informed by a note that a random password will be created instead
-
consider hiding the passwords options under “advanced”
I guess these options can even be hidden as most people will probably just want to create a room from within discourse and not connect it to a room created with another application -
not mentioning technical jargon
- I know discourse always mentions iframe, but an average user does what that is, if the label was changed to “Show inside post” instead, it would make it more clear.
- Meeting ID is the jargon of BigBlueButton. For most users, I guess “meeting name” would be better. And perhaps adding bellow a greyed out instruction explaining that is the “meeting ID”
The image bellow has some of the “features” explained bellow. (It’s just a mockup with no functionality)
But again, It’s already a very nice-to-have plugin especially for people working on education. So thanks again!