I think there isn't a one-size-fits all because group dynamics differ across groups. A group collaboration strategy has requires experimentation and evolution.
Trello boards (Kanban boards in general) work great for certain types of people like designers, but they've never worked great for engineers I've worked with.
Jira is often just way too complicated.
Slack is great for asynchronous team meetings but if you're not checking in reguarly, you might find yourself scrolling way up to figure out what people are discussing.
A Github pull request + code review workflow is great for collaborating in code, but for documentation writing, some writers don't get it (and struggle with version control -- to them, track changes makes more sense). Google Docs makes more sense.
Almost all group collaboration solutions are at best local minima for the group you have right now and for the types of stuff you need to accomplish. Add or remove people from the group, and the dynamic changes.
That said, I have found my own local minima in Google Docs, and Markdown design docs + Mermaid diagrams in Azure Devops wikis (Github wikis are similar). But I also live in a word-centric culture. These things might not work so well in visual cultures.