nextcloud / nextcloud/collectives
Rebrand Collective App
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 195
- Forks
- 51
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 48
Description
First, I'm not questioning the choice you've made for the name, Collectives is a nice one, and I know that a lot of discussion was involved in the naming choice.
I'm just asking for freedom on the choice of the name, like already suggested in other issues (see #41 #189).
We would like for internal purpose and clarity rebrand the Collective Apps with Wiki (or Grimoire if we keep the same internal name of our previous wiki system to make a smooth transition for our users) and optionally change the logo. We want to use Collective Apps as an internal/shareable source of documentation.
For us, renaming would give more clarity for our end-users : we have already File, Tasks, Agenda, Contact Apps whose names are pretty straightforward, and we would like to keep this kind of consistency.
A way to do it would be exactly like rebranding Nextcloud:
- as admin, go to Settings, Choose Customize Collectives, change Name, and Logo (see for example settings/admin/theming)
Thanks a lot for this awesome app, we are seriously considering to replace our entire current wiki system with Collective Apps.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the existing rebranding approach in settings/admin/theming and review how the Collective Apps name is presented to end users. Define the admin settings flow for choosing a custom name, and determine whether logo customization is included. Done means administrators can apply a clearer internal name, with the chosen scope reflected consistently in the app.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100