test

.github/dependabot.yml

@@ -0,0 +1,19 @@
+# To get started with Dependabot version updates, you'll need to specify which
+# package ecosystems to update and where the package manifests are located.
+# Please see the documentation for all configuration options:
+# https://docs.github.com/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file
+
+---
+version: 2
+updates:
+  # When the Dependabot ignore-manifests issue is fixed, we can just ignore the
+  # /lessons directory only:
+  # https://github.com/dependabot/dependabot-core/issues/4364
+  - package-ecosystem: "pip"
+    directory: "/scripts"
+    schedule:
+      interval: "weekly"
+  - package-ecosystem: "github-actions"
+    directory: "/.github"
+    schedule:
+      interval: "weekly"

.github/workflows/jekyll-gh-pages.yml

@@ -0,0 +1,64 @@
+---
+name: Deploy Jekyll with GitHub Pages dependencies preinstalled
+
+on:
+  push:
+    branches: ["gh-pages"]
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+# Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.
+# However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.
+concurrency:
+  group: "pages"
+  cancel-in-progress: false
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      # Generate event posts by reading them from the UofTCoders/Events issues.
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: 3.12
+      - name: Install pipenv
+        run: pip install pipenv
+      - name: Publish events
+        working-directory: scripts
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: |
+          pipenv install
+          pipenv run publish_events
+
+      - name: Setup Pages
+        uses: actions/configure-pages@v4
+      - name: Build with Jekyll
+        uses: actions/jekyll-build-pages@v1
+        with:
+          source: ./
+          destination: ./_site
+      - name: Upload artifact
+        uses: actions/upload-pages-artifact@v3
+
+  deploy:
+    permissions:
+      contents: read
+      pages: write
+      id-token: write
+
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    runs-on: ubuntu-latest
+    needs: build
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v4

.gitignore

@@ -1 +1,9 @@
+_site/
+
+# Google calendar secret key
 client_secret.json
+
+.Rproj.user
+_emails/
+.Rbuildignore
+

CONTRIBUTING.md

@@ -0,0 +1,138 @@
+---
+layout: page
+title: Contributing to UofT Coders
+---
+Welcome to the Contributing guideline for UofT Coders. Thanks for taking the time to contribute! 
+
+The following is a set of guidelines for contributing to the UofT Coders community, whether it be by teaching a lesson, fixing the website, helping to plan and organize our various events, or taking on a leadership role.
+
+### Table of Contents
+
+1. [About UofT Coders](#about-uoft-coders)
+    - [Code of Conduct](#code-of-conduct)
+
+2. [How You Can Contribute](#how-you-can-contribute)
+    - [Leading a Lesson](#leading-a-lesson)
+        - [Creating the Content](#creating-the-content)
+        - [Teaching in Class](#teaching-in-class)
+    - [Fixing and Updating the Website](#fixing-and-updating-the-website)
+    - [Other Ways to Get Involved](#other-ways-to-get-involved)
+
+-----
+# About UofT Coders
+
+UofT Coders was formed to share and learn about coding techniques and
+best practices for computing and analysis in research. We hold weekly sessions
+in the format of code-alongs, coworking sessions or journal clubs/discussions.
+To see our previous and upcoming events, you can visit our [Events repo](https://github.com/UofTCoders/Events/issues) or [website](https://uoftcoders.github.io/studyGroup/#events).
+To learn more about our group, you can read our [constitution](https://github.com/UofTCoders/council/blob/master/Constitution.md).
+
+## Code of Conduct
+
+We adhere to a [Code of Conduct](https://github.com/UofTCoders/studyGroup/blob/gh-pages/codeOfConduct.md)
+and by participating, you agree to also uphold this code. Please report any 
+unacceptable behaviour to [email protected]. If you feel that a member of 
+the executive team has been violating the Code of Conduct, please email 
+[email protected] to report.
+
+-----
+# How You Can Contribute
+
+## Leading a Lesson
+
+The Mozilla Study Group
+handbook [**here**](https://mozillascience.github.io/studyGroupHandbook/lessons.html#reuse)
+and [**here**](https://mozillascience.github.io/studyGroupHandbook/event-types.html#workalong)
+has several very good points about making a lesson. This section summarizes bits
+of the handbook, but also adds pieces that are missing from it. Check out the
+[lesson bank too](https://github.com/mozillascience/studyGroupLessons/issues).
+
+### Creating the Content
+
++ **Minimal use of slides**: The most effective sessions are ones that are very
+hands-on. We strongly encourage [*live-coding*](#more-on-live-coding) as a 
+teaching method; it's best to keep slides to a minimum or avoid them completely.
++ **Keep in mind beginners**: Make few assumptions about the knowledge of the audience,
+unless specified that this is an intermediate level lesson, requiring prior knowledge.
+Keep it simple. Don't attempt to cover too much material in a single session.
++ **Use Built-in Datasets**: Use built-in sample datasets instead of requiring
+attendees to download files. 
++ **Code Review**: The lesson code is posted to GitHub along with a pull request to
+[UofTCoders/studyGroup](https://github.com/UofTCoders/studyGroup) repository at
+least 1 full day prior to the lesson date to allow for review.
+See [Submitting a Pull Request](https://uoftcoders.github.io/studyGroup/pull-request/)
+
+#### More on Live-Coding
+
+Live-coding is a hands-on method of teaching coding to a group in which the instructor 
+shares their screen with the group and types all commands on their computer while the 
+group follows along. Live-coding is a very effective teaching technique: it forces the 
+instructor to go slowly and ensures that participants get to try out every command 
+being used. It allows learners to experience common errors themselves and debug them 
+in a supportive environment, to explore variations on material as they go, and to 
+immediately check their understanding by trying things hands-on. 
+
+Live-coding is a technique used by [Software Carpentry](https://software-carpentry.org/about/). 
+Software Carpentry has lots of great resources explaining the why and how of live-coding:
++ [10 tips and tricks for instructing and teaching by means of live coding](https://software-carpentry.org/blog/2016/04/tips-tricks-live-coding.html)
++ The Software Carpentry [instructor training manual](http://carpentries.github.io/instructor-training/) 
+includes many resources about programming education.
+
+To see live-coding in action in the UofT Coders group, watch a portion of the 
+[Intro to R livestream](https://www.youtube.com/watch?v=b74V54VFL98) taught by 
+[Ahmed](https://github.com/aays), or look over the code that was covered in an 
+[R lesson](https://github.com/UofTCoders/studyGroup/blob/gh-pages/lessons/r/intro/Intro_R_Sept21.R) 
+created by [Luke](https://github.com/lwjohnst86). 
+
+### Teaching in Class
+
++ **Arrive early**: Come 10 minutes before the lesson starts to set up.
++ **Introduce yourself**: Start by introducing yourself and perhaps why you're teaching this lesson.
++ **Stay on time**: Keep mindful of the time, lessons are 50-60 minutes long.
++ **Start from the very beginning**: Briefly explain all aspects of the what you are doing when live-coding including:
+    - show how to open the program or IDE (e.g. RStudio/Jupyter Notebook/Shell or Terminal/etc)
+    - how to run code (e.g. press `Shift+Enter` in the Jupyter Notebook)
+    - if this is an intro lesson, explain the concept of an IDE or shell
+    - importing modules and packages such as  `import numpy as np` or `library(dplyr)`
+
++ **Live-coding**: Use of slides is minimal, majority of lesson involves writing the code WITH the audience during the lesson
++ **Stay on topic**: There is only one hour, if a question arises that is off-topic, you can always suggest discussing afterwards.
++ **Check in with participants**: We distribute coloured sticky notes to each 
+participant so that they can flag problems with one colour and success with 
+another colour. Use these indicators to stay aware of your pacing and where the group is at, 
+and/or verbally ask how everyone is doing and leave time for questions.
+
+-----
+
+## Fixing and updating the website
+
+There are two ways of fixing or adding to the website, either by:
+
+- Creating an [Issue](https://github.com/UofTCoders/studyGroup/issues/new)
+describing the problem or enhancement. This is technically not doing anything
+yourself, just recommending something to be done.
+- Submitting a Pull Request from a clone of this repo. This way takes a bit more work and requires knowledge of Git and likely HTML. But we
+ would appreciate any help! No harm in giving it a try! That's a beauty of using Git, it's hard to mess up and break something.
+
+If you want to view the website before submitting a Pull Request to make sure
+your changes are as you expect, you'll need to:
+
+- Install Jekyll by following these [instructions](https://help.github.com/articles/setting-up-your-github-pages-site-locally-with-jekyll/).
+- To build the site locally, run `jekyll serve`.
+- The built site can also be viewed at your forked version
+(`https:://yourusername.github.io/studyGroup`).
+
+----
+
+## Other Ways to Get Involved
+
+### Helping Out at Our Events
+
+We hold various sessions that incorporate code-alongs, and having the help of more advanced users to help out the beginners is very much appreciated.
+- If you see a session topic that is more beginner than your current level, we highly encourage you to attend anyway and help answer questions or provide more one-on-one support during lessons.
+- You can also lend a hand at our co-working sessions to people who have come to work on their own projects.
+- We do a call for helpers for all our Software Carpentry workshops, and we definitely wouldn't be able to run these without the help of volunteers like you!
+
+### Taking On A Leadership Role
+
+The planning and organization of our the group and our various events are done by our executive council. We hold elections every April to elect the executive council members, however, we are always open to suggestions on new roles and positions for interested members of the UofT Coders community who wish to take on more a leadership role. To read more about these positions, please see our [Council Roles](https://github.com/UofTCoders/council/blob/master/Council_Roles.md) document.

DESCRIPTION

@@ -0,0 +1,22 @@
+Package: studyGroup
+Version: 0.0.0.9000
+Title: Website for UofTCoders
+Description: Content for studyGroup website.
+Encoding: UTF-8
+LazyData: true
+ByteCompile: true
+Imports: 
+    yaml,
+    here,
+    purrr,
+    dplyr,
+    stringr,
+    lubridate,
+    glue,
+    fs,
+    gh,
+    usethis,
+    assertr,
+    readr
+URL: https://github.com/SaraMati/studyGroup
+BugReports: https://github.com/SaraMati/studyGroup/issues

ISSUE_TEMPLATE.md

@@ -0,0 +1,13 @@
+<!-- 
+If you're posting an event, volunteer, job or other
+opportunity to the UofT Coders Study Group, please address 
+all of the following points in your post:
+
+- Your Name, or Organization Name
+- Contact information
+- Type of Post: Event, Volunteer or Job Opportunity, or other (please specify)
+- Details of issue/event/opportunity
+- Why you think UofT Coders can help or would be interested?
+
+Thanks for sharing with the community! 
+-->

README.md

@@ -1,6 +1,8 @@
 Mozilla Study Groups
 ============
 
+[![Join the chat at https://gitter.im/UofTCoders/Lobby](https://badges.gitter.im/UofTCoders/studyGroup.svg)](https://gitter.im/UofTCoders/Lobby?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
+
 Welcome to [Mozilla Science Lab](https://www.mozillascience.org/)'s Study Group project! From here, we'll set you up with everything you need to start your own study group.
 
 ### Wait What's a 'Mozilla Study Group'?
@@ -11,12 +13,14 @@ Mozilla Study Groups are fun, informal meetups of your friends and colleagues fr
 
 Welcome to our Mozilla Study Group! A few things to do & know now that you're here:
 
- - **Watch this repo:** up in the top right, there's a button that says 'Watch'; click it, and set yourself to 'Watching'. This will send you email notifications of new discussions; if you don't want email, but would like an alert just on GitHub, change the setting in Settings -> Notification Center (Settings is the little cog in the top right).
+ - **Watch the [Events](https://github.com/UofTCoders/Events) repo and/or this repo:** up in the top right, there's a button that says 'Watch'; click it, and set yourself to 'Watching'. This will send you email notifications of new discussions. If you only want to be notified about events (and not any other discussion topics), watch just the [Events](https://github.com/UofTCoders/Events) repo. If you want to stay updated on all group doings, watch this repo AND the Events repo. If you don't want email, but would like an alert just on GitHub, change the setting in Settings -> Notification Center (Settings is the little cog in the top right).
  - **Check out the issue tracker:** click on 'issues' in the sidebar on the right; this is where all the conversations this study groups is having live. Use this space to ask questions, request events, make suggestions, or just say hi.
  - **Read the code of conduct:** this Study Group is for everyone - we abide by a [set of rules](https://www.mozillascience.org/code-of-conduct/) that require everyone be treated with respect. Help us make a space where everyone feels welcome, and we'll all have a better time!
  - **Add yourself to the website:** If you'd like to appear on the website under the 'Who we Are' section, have a look at the `_data/members.yml`; send us a pull request with an entry for yourself, or open an issue and we'll do it for you.
 
-## For Organizers
+## For Organizers/Instructors
+
+Check out the [`CONTRIBUTING` file](https://github.com/UofTCoders/studyGroup/blob/gh-pages/CONTRIBUTING.md) or [the page on the site](https://uoftcoders.github.io/studyGroup/CONTRIBUTING) for more details.
 
 ### It's Broken, I Need Help
 
@@ -70,7 +74,7 @@ When you're ready to list a new event for your Study Group, follow these steps,
 
     where `YYYY-MM-DD` is the date of your event, and `word` is anything you want.
  4. **Cut and paste the following into your new file:**
- 
+
     ```
     ---
     title: Study Group Meetup
@@ -106,7 +110,7 @@ Your website includes a gallery of participants in your Study Group; adding peop
 
 ```
 - name: their human name
-  affiliation: school, lab, department, business....
+  degree: school, lab, department, business....
   github: their GitHub handle
   interests:
     - list one to three

_config.yml

@@ -1,9 +1,10 @@
 #Setup ~~~
 #Follow these 2 steps to set up your site.
+exclude: [".Rproj.user"]
 
 #Step 1: give your study group a name and a short description:
-title: Our Study Group
-description: "A study group."
+title: University of Toronto Coders
+description: "We are a group of students and researchers dedicated to learning about and sharing scientific coding techniques and knowledge in an effort to improve scientific research."
 
 #Step 2: press the green 'Commit Changes' button at the bottom of this page.
 
@@ -16,20 +17,34 @@ description: "A study group."
 # Optional Configuration
 # None of these things need to be changed - but feel free!
 
-titleBackground: "https://s3-us-west-2.amazonaws.com/webmaker-kits/learning%402x.jpg"
-headlineSmall: "Welcome To Our Study Group!"
+headlineSmall: "Welcome To The U of T Coders Group!"
 headlineMain: "Let's Work Together"
+avatar: "img/logos/logo_icon_dark.png"
 
 # Setup Google Calendar
 # Usage:
 # 1. create a new google account; set the calendar to 'public'
 # 2. change 'USER' in the example urls below to the username of the google account you made for your calendar
 # 3. set calendar_on: True.
 
-calendar_on: False
-calendar_embed_url: "https://www.google.com/calendar/embed?src=USER@gmail.com"
-calendar_ical_url: "https://www.google.com/calendar/ical/USER@gmail.com/public/basic.ics"
+calendar_on: True
+calendar_embed_url: "https://www.google.com/calendar/embed?src=uoftcoders@gmail.com"
+calendar_ical_url: "https://www.google.com/calendar/ical/uoftcoders@gmail.com/public/basic.ics"
 
+# ===============================
+# Categories for sorting lessons.
+# ===============================
+
+languages:
+  - python
+  - r
+  - git
+  - misc
+
+levels:
+  - beginner
+  - intermediate
+  - advanced
 
 #========================================
 # No touching anything below this line :)
@@ -43,3 +58,4 @@ color:
 # Build settings
 markdown: kramdown
 permalink: pretty
+future: true