I am trying to use Statuses to build something like this:

https://slack.com/

The basic idea is that there is a left column of available 'channels' and then a main content area with a micropublishing stream, like statuses provides.

So I think all the functionality is here in this module and companion modules and I'm just wondering what the best way to organize the user interface, with some suggestions from the community.

For example, I suppose I could create a root page like '/statuses' and put no content in it, or hide it, or make the page content an introduction, and attach the statuses block to the main content region there, attached to '/statuses' and '/statuses/*'

Then, could I add a block to the left that was a list of 'channels' or available contexts? If so, I could link them to 'statuses/channel_name', abd make the statuses block grab the context 'channel_name' form the url arguments. Or something.

Or maybe I should use panels and do something similar where the panel context gets a channel name to set the appropriate stream for the statuses block inside it?

Any suggestions or pointers are welcome.

Comments

meecect created an issue. See original summary.

IceCreamYou’s picture

Status: Active » Fixed

Statuses isn't a chat module; it won't automatically update anything when someone else posts a status. Everything else could just be done at the theming layer but that is a pretty tricky (and resource-intensive) aspect if you don't go with a pure chat module.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.