- Notifications
You must be signed in to change notification settings - Fork 823
Closed
Description
I think these links could be organized a bit better,
I propose two options,
basically i think we should favour the official channels at the top of the list.
I moved elixir-core to the second list in my first proposal. and I have added the StackOverflow link,
and removed the word "Elixir" when it was a bit repetitive and I could do it.
JOIN THE COMMUNITY
- #elixir-lang on freenode IRC
- Elixir on Slack
- elixir-talk mailing list (questions)
- @elixirlang on Twitter
- Questions on Stack Overflow
- Meetups around the world
- Wiki with events, resources and talks organized by the community
IMPORTANT LINKS
- Source Code
- Issue tracker
- elixir-core mailing list (development)
- Crash course for Erlang developers
or..
OFFICIAL LINKS
- Source Code
- Issue tracker
- #elixir-lang on freenode IRC
- @elixirlang on Twitter
- elixir-talk mailing list (questions)
- elixir-core mailing list (development)
JOIN THE COMMUNITY
- Elixir on Slack
- Meetups around the world
- Wiki with events, resources and talks organized by the community
- Questions on Stack Overflow
Crash course for Erlang developers
*The problem with this approach is that Crash course it doesn't fit in any of those two categories.
Metadata
Metadata
Assignees
Labels
No labels