Added new community page, in place of the much lighter 'resources' page

CHANGELOG.md

@@ -6,6 +6,7 @@
 
 ### Other
 
+- Added new community page, in place of the much lighter 'resources' page [#199](https://github.com/nre-learning/antidote/pull/199)
 
 ## v0.3.0 - February 11, 2019
 

docs/community.rst

@@ -0,0 +1,67 @@
+.. _community:
+
+Community Resources
+===================
+
+We're truly interested in building a community around both the Antidote platform, as well as the NRE Labs curriculum.
+To that end, we've created several diverse resources for getting involved with the project.
+
+Github
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Everything we produce in the Antidote project is on Github underneath the `nre-learning <https://github.com/nre-learning>`_
+organization. Underneath that organization, you'll find all kinds of repositories, including the platform software,
+operational tooling, blogs, and more.
+
+While there is no single repository that hosts everything, the canonically "main" repository is probably the
+`Antidote repo <https://github.com/nre-learning/antidote>`_. Most subcomponents of the Antidote project
+are hosted in their own dedicated repositories, but this will be a good starting point, as the README
+does contain references to other repositories you may also want to know about.
+
+Finally, all project planning related to the Antidote platform, such as for subcomponents like ``syringe``
+and ``antidote-web`` are done in `Github projects <https://github.com/orgs/nre-learning/projects>`_. Generally
+while we're working on a release, we'll open up a new project for that release, and all current status for that
+release can be found within that project. So, if you're looking for a status on current development efforts,
+this is where you want to go.
+
+Twitter
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Follow `@NRELabs <https://twitter.com/nrelabs>`_ on twitter for periodic updates on NRE Labs and the underlying platform.
+
+Discord Channel
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+We use Discord for chat and audio/video collaboration. You can think of it like Slack, but even better, because it's
+more purpose-built for some of things we want to do in the future with NRE Labs, and the authentication story is a
+bit better. :)
+
+Join our Discord channel via `this link <https://discord.gg/fRuSUyD>`_.
+
+Mailing List
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+For those that prefer email for communication, we have two mailing lists:
+
+- `Developers <https://groups.google.com/forum/#!forum/nre-labs-developers>`_
+- `Users <https://groups.google.com/forum/#!forum/nre-labs-users>`_
+
+Weekly Livestreams and Other Videos
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+We run a weekly livestream on Twitch at 10AM Pacific Time. Right now this is fairly informal - some weeks we might dive
+deep into a topic, other weeks we might just casually chat about what's next on the project plan.
+
+Check out our `Twitch channel <https://twitch.tv/nrelabs>`_ to watch live, and interact with us in the chat. Ask questions or
+provide feedback to us live, and we might talk about it on stream!
+
+If you can't join live, check out our `YouTube channel <https://www.youtube.com/channel/UCbfZq3sDGx6gmv7KRrhRh4g>`_, where we post the
+recordings for all our streams, as well as all other video content.
+
+Blog
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+The `Network Reliability Engineering blog <https://networkreliability.engineering/post/>`_ is where we like to write about NRE concepts
+and any big changes to NRE Labs. You may also be interested to know that this blog is powered by Hugo, and
+`maintained in Github <https://github.com/nre-learning/nre-blog>`_, so if you want to write a guest post by opening a pull request
+to that repo, we'd love to have you!
+
+
+Trello Board
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+For slightly less technical project planning around the Antidote community, see our `Trello Board <https://trello.com/b/QdT69weT/nre-labs>`_.
+This is where we plan anything that doesn't fit neatly into a platform release plan, which we manage in Github projects.

docs/conf.py

@@ -66,7 +66,7 @@
 # List of patterns, relative to source directory, that match files and
 # directories to ignore when looking for source files.
 # This pattern also affects html_static_path and html_extra_path .
-exclude_patterns = ['_build', 'Thumbs.db', '.DS_Store']
+exclude_patterns = ['_build', 'Thumbs.db', '.DS_Store', 'venv']
 
 # The name of the Pygments (syntax highlighting) style to use.
 pygments_style = 'sphinx'

docs/index.rst

@@ -13,14 +13,17 @@ Introduction to Antidote
    contributing/index.rst
    roadmap.rst
    nrelabs.rst
-   resources.rst
+   community.rst
 
-Welcome to Antidote!
+Antidote is a community initiatve to democratize interactive, dependency-free learning.
+With Antidote, you can create compelling, interactive learning experiences by building
+turnkey lesson materials that are fully browser-based, placing minimal burden on the
+learner to come with pre-requisite knowledge or environment configurations.
 
-Antidote is an open-source project aimed at making automated network operations
-more accessible with fast, easy and fun learning. It teaches from-scratch
-network automation skills for network reliability engineers (NREs) and other
-NetOps pros or amateurs.
+Antidote is composed of a set of is an open-source project aimed at making
+automated network operations more accessible with fast, easy and fun learning.
+It teaches from-scratch network automation skills for network reliability engineers
+(NREs) and other NetOps pros or amateurs.
 
 Antidote isn't just one application, but rather, a set of smaller applications
 that work together to provide this learning experience.