How do you name git repositories?

Question

git

Hey!
We have two departments: frontend and backend.
We use bitbucket (we have a common team).
Turnips can be created by both backend and frontend developers.
Initially, we agreed to name with a department postfix, for example toster-backend/toster-frontend.
Over time, there were a lot of repositories and confusion with names appeared, since bitbucket does not provide the ability to somehow group repositories in the web interface (except for the filter by programming language).
It also annoys that "backend repositories" are used for real projects, and not some "toster.ru" repository.
If you give access to the team to a new developer, he will not immediately understand in which repository he needs to work. Sometimes we ourselves are forced to get into deploy scripts in order to peep some kind of repository used on a particular project.
I would like to ask readers what rules for naming repositories are adopted in your team?
Thanks

Answer 1

gitlab, dividing projects into groups, everyone is happy.
Another option is one repository for backend and frontend (why not?)
Do you store deployment scripts outside the repository?