complicated design discussions best be handled in google docs
I tend to agree with the insights here: https://m.signalvnoise.com/is-group-chat-making-you-sweat-744659addf7d#.s765j3hhc “real-time sometimes, asynchronous most of the time”
À,, q
L
@marekweb dynamic stuff like pre-/post-event chatter can be prototyped with Disqus or a similar system. RSVP'ing will need to be a different service. Any thoughts on how to prototype RSVPs on a statically generated site?
... can be started as separate things, using different tech (appropriate to the need).
the value to users is what they can do with the information on the site. If I had to chose between 5 future events and 5 past events, the 5 future events are more valuable
@pcuci re issue #2 and Gitter comment: "Show what the platform is capable of when used by a fantastic community" I say we must focus on a small group (and we'll see whether we overload cognitive circuits). Currently the scroll up-down is going to cause us "never" to reach the past events, because the future events shall get longer and longer.
Limiting is an easier implementation that UX overhaul.
Other options exist too, like different smaller format for upcoming events 6th and father in the future.
Changing the scroll orientation from vertical to horizontal is more scss work
Pagination is another option
You can suggest more alternatives too
@frabrunelle can you send out a query in a few places and do some more good discovering; you found this template and jekyllRB (It's good)
Re: "... write a longer message later but basically we would have to use http://jekyllrb.com + https://pages.github.com. and in addition to generating an RSS feed, we also generate an ical feed: https://gist.github.com/woodworker/6725728. ...."
The query is to search for a way to show a timeline that's continous.
Re: "... write a longer message later but basically we would have to use http://jekyllrb.com + https://pages.github.com. and in addition to generating an RSS feed, we also generate an ical feed: https://gist.github.com/woodworker/6725728. ...."
The query is to search for a way to show a timeline that's continous.
@/all hey everyone, see the new http://bettermtl.com - it's now multilingual (you can add any number of languages), and has a few cool workshps/events posted
Which communities should we work with initially to populate the event calendar?
@/all switched http://bettermtl.com to French default, restyled and added locations and network collections to reduce data copying errors (normalization). We now have something solid to show for next Monday's http://notman.org/hackthehouse/ - plz test and let me know your comments, feedback much appreciated!
They made it such that people can request invites to join the jekyll core team, wonder what bot they're using to make that happen. We would then be able to notify teams with @bettermtl/content or @bettermtl/code or @bettermtl/ops - or whatever team names we end up creating
@David-Ro something like this would be cool
something like that, yes, and showing needs expressed by participants, needed before the event starts: physical needs and interpersonal needs; e.g. which participants are edge cases, exceptions. A paper checklist still works for physical and for logistics but real-time responsive software is the only way to handle the interpersonal needs outside of key-organizers' brains.
Wikified activities fact track (who what) events, link calendar, promote/show/hide data(meta(meta))
this one is too techy
Answers to newbies, is hot new need.
Too many needs. Burden on reading if all queries get posted.
Can we have a ( Bot Chatbot Slackbot https://en.wikipedia.org/wiki/Xiaoice )
Too many needs. Burden on reading if all queries get posted.
Can we have a ( Bot Chatbot Slackbot https://en.wikipedia.org/wiki/Xiaoice )
I think the ability to display any/every/thing in 2 or 3 languages at same time on same page
has to be abstractized to make it core before anything else.
e.g.
title of project
address
any button
Example: In Jordan the map (any map) has both Arabic and English here and there: not consistent. We can do this 10x better.