Thanks, that’s super helpful to know.
I’m seeing that know by browsing other servers.
IMHO, the UI is probably going to need to be a little more affordant. Since Beehaw is a lot of people’s first Lemmy instance, some people are going to thing that only admins can create communities. There might need to be some sort of coaching copy in the UI so people know the functionality exists on the platform, but it’s disabled here.
I’m not saying having it in multiple places is bad, but it being set to admin only and why is covered in the philosophy posts you get shown when applying.
That’s true, but there is a lot of content in that sidebar, and despite reading it, I either glanced over it or didn’t retain it.
All in all, good experience design account for letting the user know what the contains of the UI are at the time they have a motivation to do something.
I do UI work for a living, and anytime I try to explain something in onboarding documentation, people glaze over it and or don’t retain it. Humans brains aren’t really the greatest at being information in that way.
Spitballing here, maybe a “create community” link / button that, when clicked, just tells people how to find an instance that allows community creation. Nothing complicated.
Some instances allow you to make your own community. However beehaw is not one of those instances
Thanks, that’s super helpful to know. I’m seeing that know by browsing other servers.
IMHO, the UI is probably going to need to be a little more affordant. Since Beehaw is a lot of people’s first Lemmy instance, some people are going to thing that only admins can create communities. There might need to be some sort of coaching copy in the UI so people know the functionality exists on the platform, but it’s disabled here.
I’m not saying having it in multiple places is bad, but it being set to admin only and why is covered in the philosophy posts you get shown when applying.
That’s true, but there is a lot of content in that sidebar, and despite reading it, I either glanced over it or didn’t retain it.
All in all, good experience design account for letting the user know what the contains of the UI are at the time they have a motivation to do something.
I do UI work for a living, and anytime I try to explain something in onboarding documentation, people glaze over it and or don’t retain it. Humans brains aren’t really the greatest at being information in that way.
just my 2¢
How would you communicate that in terms of UI?
Spitballing here, maybe a “create community” link / button that, when clicked, just tells people how to find an instance that allows community creation. Nothing complicated.
Could suggest it on here, seems reasonable and pragmatic : https://github.com/LemmyNet/lemmy-ui/issues
Good call out. I’ll do that!