karrot-dev / karrot-frontend

We migrated to https://codeberg.org/karrot/karrot-frontend
https://codeberg.org/karrot/karrot-frontend
428 stars 177 forks source link

Copy recommendation on Create New Group page #2706

Closed sbutler-gh closed 6 months ago

sbutler-gh commented 7 months ago

On the Create New Group page, I was confused by the public group information and group description textareas — I thought they was asking me for the same information, I wasn't sure what the difference was. Only when I investigated closer did I realize the difference. I thought some small copy changes could make this easier to understand off the bat, like this:

Public group information (visible to everyone)

Internal group description (visible to members)

Here is what the page currently looks like

Screen Shot 2024-02-19 at 9 06 53 PM

And what it could look like with this kind of change:

Screen Shot 2024-02-19 at 9 07 48 PM
nicksellen commented 7 months ago

Yup, makes sense! Are you interested to contribute the change? (not sure if you have that interest/skills).

Although, it might be worth changing the second one to "Internal group information", as in practise that's how it's often used.

We have this input too: https://community.karrot.world/t/transform-private-group-description-into-group-wall-description/1505 which explains the use case more like group information:

A description above the main wall would be really useful to show some common group stuff (reminder of rules, links to important documents or websites…).

There was also a previous pull request to rename the actual field to group information too (https://github.com/karrot-dev/karrot-frontend/pull/2465 and https://github.com/karrot-dev/karrot-backend/pull/1211), but unfortunately was not completed/merged (oops looks like my fault 🤦).

I'll cross reference this thread with our community forum one, and see what input is there! Getting the wording right is really important as can really confuse people otherwise (like you experienced).

nicksellen commented 7 months ago

So, from the input on the community forum, I think we could go with:

I'd suggest we have the parenthesis bits as seperate i18n strings, so they could be used elsewhere..., so 4 string in total:

nicksellen commented 6 months ago

As in other PR thread, we moved to codeberg!

See https://codeberg.org/karrot/karrot-frontend/issues/2706