- Students could fork your base template - but then anyone with the original could easily find each fork, just like a repo. Not sure how much we care, something to consider. Maybe we prefer that because it makes it easier for staff to keep track of them?
- Students could copy and paste into a new Gist - we'd need to think through how we collect and store links, etc. if we care to access that at any given time?
- Mod teams, you decide on the above bullet points! This is a PILOT, you can't really mess it up. The point is that we get some parts wrong and learn!
- Speaking of Mod 1 students, this is what they get and do in Mod 0 related to Markdown and GitHub Gists.
You might want these as you design your template, and you might consider offering them to your students. Remember, let's keep it SIMPLE and not overwhelm them with resources. They are resourceful and can find more if needed!
Hot take: Tables aren't worth your time.
We can write inline code just like we do in Slack!
def multi_line_code_too
end🔼Line Breaks might be nice🔼
🌶 Using Emojis could also spice it up 🌶
HAVE SOME FUN and when in doubt, choose the path of least resistance.