[Long Term] New Channel Types

[alzalia1]

Problem

First off : this is by no mean urgent. Thanks a lot for all the work produced !
Also, english is not my main language so I excuse for the weird sentences.

Right now there are three channel types :

• Text
• Voice
• Link

Per the roadmap, forums, threads and stage channels are also part of the plan.

On the long term, however, I believe it would be interesting to integrate even more channel types.

Caution

Those suppositions are, as their name suggests, purely theoretical. This list is purely here as a suggestion, I am not able to assess the feasibility of those proposal. Please, if one (or all) of the proposals seem inconceivable even in a distant future, notify me so I can remove it. My intention is merely to give ideas and to help group ideas of channels in one issue. By no mean do I intend on putting pressure on anyone !

Proposed solution

• Calendar : To plan events on a calendar, with each channel being its own calendar

Description : We can further imagine each event to be its own "thread", in a way : a place to discuss the event, list information... The content of an event could be spread in two parts : a "header", compiling all the "main" information (a title, a description, a date, maybe a location (of type channel or text), and then maybe some custom fields) and then a second part, the "body", the discussion part, functioning just like a normal text channel. While a message in the body would belong to a specific user, the header could be modified by anyone with the permission to do so. Whether to set those permissions on a calendar or event basis can be debated.
Use cases : Let a team organize meetings ; gamers organize play sessions ; communities plan events in general

• Kanban : To organize tasks more easily

Description : Just like the Calendar, a task could be split in two parts : a header with the main information (title, desc, image, other fields) and a body to discuss . A task would then be a card on a board that can be moved between different categories, defined by the user. Just like the Calendar, the header could be modified by people with the permission to do so while the body would be filled with personal messages. In fact, Kanban could probably be a view type of the Calendar, although I think it would be preferable that the two are dissociated (Or a channel where you can enable / disable each view ?)
Use cases : Let a community plan its next posts on social media ; gamers plan out the next phases in their factory building ; communities keep track of what they need to do in general

• Documentation : A blank page to write and document

Description : A page, maybe with tabs, where you write but no answers are expected. Maybe this can be thought as an html canvas where one can build some sort of mini website (with no javascript of course) ? Or maybe a more controlled environment where you let people build with predefined components. Overall : somewhere you are free of the constraints of a normal textual channel, where you can arrange elements in a nice way to make an informative (or not) page. Editing would be restrained page-wide to those with permissions.
Use cases : A content producer presents oneself ; a community exposes rules in a nice way ; someone show a tutorial on how to make a good mock-up

Notes (optional)

If anyone wishes to add on this, whether by adding on one of the already mentioned proposals, or with a new one, please, do !

This issue is bound to be edited as ideas come and go.

If creating such a "large scale" issue (in a way, I mean idk) is a problem, I am very sorry for the inconvenience caused :/

Checks

• I searched for existing issues and didn't find a duplicate.