I like the concept. IMO, the keys are going to be 1.) Showing how you differ from Slack 2.)simplifying, I'm already overwhelmed but I get what you are trying to do. and 3.)Ubiquity of the templates. Make it easy to make, clone, share, track them.
Edit: A few small quips. Audit how you use the word public. That's going to scare people. I assume you mean make the channel read/write for other members of my slite, not the public at large.
Someone else had this idea in the comments, I would also second the motion that adding controlled fields (select from drop down) could help with templates.
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.
Edit: A few small quips. Audit how you use the word public. That's going to scare people. I assume you mean make the channel read/write for other members of my slite, not the public at large.
Someone else had this idea in the comments, I would also second the motion that adding controlled fields (select from drop down) could help with templates.
Good luck!