Release v1.1.1-231 show new group features

TODO-next-update.md

@@ -2,11 +2,17 @@
 
 When you overtake this deploy and rebrand repo to your network you have to recognize the following changes and doings …
 
+## This Latest Version >= 1.1.1 with 'ocelotDockerVersionTag' 1.1.1-231
+
+### Yunite Deployment/Rebranding PR –  chore: 🍰 Release v1.1.1-231 - New Group Features #14
+
+- You have to add the file `webapp/constants/groups.js` as `branding/constants/groups.js` which should include `SHOW_GROUP_BUTTON_IN_HEADER` set to your needs.
+
 ## This Latest Version >= 1.1.0 with 'ocelotDockerVersionTag' 1.1.0-205
 
 ### Deployment/Rebranding PR –  chore: 🍰 Release v1.1.0 - Implement Categories Again #63
 
-- You have to add the `CATEGORIES_ACTIVE` from the `deployment/kubernetes/values.template.yaml` to your `deployment/kubernetes/values.yaml` and set it to your prevered value.
+- You have to add the `CATEGORIES_ACTIVE` from the `deployment/kubernetes/values.template.yaml` to your `deployment/kubernetes/values.yaml` and set it to your preferred value.
 - Make sure the correct categories are in your Neo4j database on the server.
 
 ## Version >= 1.0.9 with 'ocelotDockerVersionTag' 1.0.9-199

branding/constants/groups.js

@@ -0,0 +1,5 @@
+// this file is duplicated in `backend/src/constants/group.js` and `webapp/constants/group.js`
+export const GROUPNAME_MIN_LENGTH = 3
+export const GROUPNAME_MAX_LENGTH = 50
+export const GROUPDESCRIPTION_WITHOUT_HTML_LENGTH_MIN = 100 // with removed HTML tags
+export const SHOW_GROUP_BUTTON_IN_HEADER = false

package.json

@@ -1,7 +1,7 @@
 {
   "name": "yunite.net",
   "version": "1.1.1",
-  "ocelotDockerVersionTag": "1.1.1-228",
+  "ocelotDockerVersionTag": "1.1.1-231",
   "dockerOrganisation": "tirokk",
   "description": "yunite.net Branded",
   "author": "yunite.net Community",