[christophepas]

Thanks for the feedback !

For the differenciation with Slack, the similarity really stops with the channels pattern. Using Slite allows you to separate use cases: Slack or equivalent to communicate instantly, Slite to write and retrieve information.

As a back story, Slack did try something similar a few years back: they built Slack posts with a similar vision in mind. But having those burried in threads and writing in a constantly ringing place defeated their purpose. From talking to our users, it seems like really few people use posts as they were intended in the first place. At the end of the day, having to organize your content and handling collaborative edition is a job for a standalone product

For the wording indeed, a teammate just mentionned the same thing on "public" wording, we'll think of a better term, "team-wide" maybe.

As for the templating option it's clearly something we're thinking about, the challenge is to make the feature simple enough.