*

Author: ivanreese

community.md

@@ -8,6 +8,22 @@ We share and discuss ideas, prototypes, weekly demo videos, and inspirational li
 
 Before joining the community, please familiarize yourself with the [member handbook](/member-handbook).
 
-You can join the [Future of Coding Slack community right here](https://join.slack.com/t/futureofcoding/shared_invite/zt-8vhwkhg2-rKZkVYJRKTwLbumJWVNaSw). If this link doesn't work on your mobile device, try it on a computer. Our community is open to any topic related to furthering the evolution of computing. We also have a [Matrix bridge](#matrix-bridge).
+### Slack
 
+You can join the [Future of Coding Slack community right here](https://join.slack.com/t/futureofcoding/shared_invite/zt-8vhwkhg2-rKZkVYJRKTwLbumJWVNaSw). If this link doesn't work on your mobile device, try it on a computer. Our community is open to any topic related to furthering the evolution of computing.
+
+### History Search
 You can explore the archives of our Slack using this [History Search](http://history.futureofcoding.org) tool (h/t to [Mariano Guerra](https://marianoguerra.github.io)).
+
+
+### Matrix Bridge
+Our 4 most popular channels are bridged to Matrix rooms. They should be accessible in any Matrix client using the following aliases:
+
+* [#_slack_futureofcoding_general:matrix.org](https://matrix.to/#/#_slack_futureofcoding_general:matrix.org)
+* [#_slack_futureofcoding_feedback:matrix.org](https://matrix.to/#/#_slack_futureofcoding_feedback:matrix.org)
+* [#_slack_futureofcoding_introductions:matrix.org](https://matrix.to/#/#_slack_futureofcoding_introductions:matrix.org)
+* [#_slack_futureofcoding_random:matrix.org](https://matrix.to/#/#_slack_futureofcoding_random:matrix.org)
+
+You can also search for "Future of Coding" in a Matrix client to find them. Thanks to [J. Ryan Stinnett](https://twitter.com/jryans) for facilitating these, and for suggesting the following etiquette:
+
+When responding to someone, be sure to use your Matrix client's "reply" feature, rather than (say) block-quoting manually in Markdown or something. Exact steps will differ per client. For Riot Web, you hover on the message to reply to, an action bar appears on the top right of the message, and you can pick "reply" (the curved arrow icon) from there and type your reply. For Riot iOS and Android, you long press on the message to reply to, and then you can choose "reply" from the menu and type your reply.

episodes/049.md

@@ -0,0 +1,9 @@
+Back in the previous life, I sent a link to slides that present an overview of several ideas behind Sketch-n-Sketch. In case you think it would be useful as a link, here is something similar but in text form (this "research statement" is part of a tenure review file that I just submitted):
+
+http://people.cs.uchicago.edu/~rchugh/static/other/chugh-research-jun-2020.pdf
+
+
+
+I forget whether we talked about plans to teach a new Creative Coding class, but now it's official and slated to start next spring. Not that I think linking to this course catalog is interesting, but it includes the course description in case you find that useful. I'm happy that Creative Coding will count towards a recently-created Media Arts and Design minor. I haven't written anything for this class yet, but I did have fun posting this:
+
+https://twitter.com/ravi_chugh/status/1229751960737394690

member-handbook.md

@@ -11,6 +11,7 @@ You'll learn our preferred ways to structure discussions, what channels we have
 
 Note: This guide is currently a work-in-progress under active development (as of August 17th, 2020). Watch for nails!
 
+<br>
 
 ## How We Slack
 
@@ -22,6 +23,7 @@ When you want to respond to someone's post, always use threaded replies. On desk
 
 Please try to keep thread replies on-topic with respect to the original post. If you want to fork a discussion off in a new direction — say, if you feel a tangent coming on — by all means start a new top-level post that includes a link back to whatever message sparked your digression.
 
+<br>
 
 ## Channels
 
@@ -63,17 +65,3 @@ Post if you are hiring or looking for work. Work related to the future of coding
 <br>
 
 There are a handful of other channels, focussed on meetups and subject-specific discussion. When you first arrive, be sure to check them out and join the ones that fit your interests.
-
-<br>
-
-## Matrix Bridge
-Our 4 most popular channels are bridged to Matrix rooms. They should be accessible in any Matrix client using the following aliases:
-
-* [#_slack_futureofcoding_general:matrix.org](https://matrix.to/#/#_slack_futureofcoding_general:matrix.org)
-* [#_slack_futureofcoding_feedback:matrix.org](https://matrix.to/#/#_slack_futureofcoding_feedback:matrix.org)
-* [#_slack_futureofcoding_introductions:matrix.org](https://matrix.to/#/#_slack_futureofcoding_introductions:matrix.org)
-* [#_slack_futureofcoding_random:matrix.org](https://matrix.to/#/#_slack_futureofcoding_random:matrix.org)
-
-You can also search for "Future of Coding" in a Matrix client to find them. Thanks to [J. Ryan Stinnett](https://twitter.com/jryans) for facilitating these, and for suggesting the following etiquette:
-
-When responding to someone, be sure to use your Matrix client's "reply" feature, rather than (say) block-quoting manually in Markdown or something. Exact steps will differ per client. For Riot Web, you hover on the message to reply to, an action bar appears on the top right of the message, and you can pick "reply" (the curved arrow icon) from there and type your reply. For Riot iOS and Android, you long press on the message to reply to, and then you can choose "reply" from the menu and type your reply.