Copy recommendation on Create New Group page about karrot-frontend

[nicksellen]

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

• Public group information (visible to everyone)
• Internal group description (visible to members only)

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

• Public group information
• Internal group description
• visible to everyone
• visible to members only

[nicksellen]

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 (#2465 and karrot-dev/karrot-backend#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]

As in other PR thread, we moved to codeberg!

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