Merge pull request #83 from resbazaz/add-events-festival

Add ResBaz Festival to "events" (WIP)

.gitignore

@@ -3,4 +3,5 @@ _site
 /.quarto/
 .Rproj.user
 **.Rhistory
-**.Rproj
+**.Rproj
+.DS_Store

README.md

@@ -10,21 +10,13 @@
 
 ### 2\. Clone this Repository
 
-(TODO: need to update this if/when the repo moves!)
-
 ```
-git clone https://github.com/resbazaz/website-draft
-# TODO: switch to this once the website is ready:
-# git clone https://github.com/resbazaz/website.git
+git clone https://github.com/resbazaz/website.git
 ```
 
-### 3\. TODO
-
-(probably need python, r, etc setup... might be optional?)
-
-### 4. Previewing changes
+### 3. Previewing changes
 
-This should build the website on your machine, serve it locally, and open a browser window to see any changes as you make them:
+This should build the website on your machine, serve it locally. This should automatically open a browser window, showing any changes as you make them:
 
 ```
 cd website
@@ -39,11 +31,15 @@ TODO: basic git fork + commit + PR flow
 
 ### Editing page contents
 
-TODO: where to find markdown
+TODO: document qmd files, `_quarto.yml`
+
+### Updating page components
+
+TODO: link to quarto docs
 
-### Updating page elements
+We have a few custom elements, in the `components` directory (documentation about each should be in the corresponding file):
 
-TODO: where to find HTML, how includes and \_data work
+- [randomAvatars](https://github.com/resbazaz/website/blob/main/components/randomAvatars.ojs)
 
 ### Customizing styles
 
@@ -53,7 +49,17 @@ TODO: Alpine, Tailwind stuff
 
 TODO: document `.github/workflows/build.yml`
 
-Be advised that `localData/people.json` in your local respository is just an example file, that will be overwritten by the latest ResBazAZ teams on Github—so to update who is shown, and what teams are shown, you should edit the Github teams, not the JSON file.
+### Data about people
+
+`data/people.json` is a collection of public GitHub profiles, for people in our organization. It is used to create various visual elements, such as the `randomAvatars` widget, or the `nodeLinkDiagram` visualization on the "Who We Are" page.
+
+This file is automatically generated whenever a branch is merged to `main`. For details on how this works, see [Changing how Github builds and deploys the site](#changing-how-github-builds-and-deploys-the-site).
+
+A few things to be careful about:
+
+1. To update who is shown, what teams are shown, etc., you should edit the `resbazaz` GitHub organization Teams and encourage members to updaite their GitHub profiles, instead of editing `data/people.json` directly.
+2. The information in your local repository may not always be up to date. For the latest information, especially when you're developing locally, navigate to `https://researchbazaar.arizona.edu/data/people.json`, and download it to replace `data/people.json`
+3. Although this is currently just a copy of publicly-available information, please keep in mind that it's still data about people! Especially if we adapt this process to include more than public GitHub profiles, where this data is stored / how it is collected may need to be revised.
 
 ### Reconfiguring the site's infrastructure
 

components/randomAvatars.ojs

@@ -1,5 +1,14 @@
-peopleFile = FileAttachment('data/people.json').json();
+peopleFile = FileAttachment("data/people.json").json();
 
+/**
+ * An observable.js widget that shows profile pictures for ResBaz GitHub Team
+ * members; see index.qmd for examples. Additionally, some relevant styles are
+ * in styles/index.css
+ *
+ * @param teamName A string that should correspond to the name of an entry in
+ * data/people.json, under data.organization.teams.nodes
+ * @returns A DOM element that can be embedded via an ojs cell
+ */
 function randomAvatars(teamName) {
   const team = peopleFile.data.organization.teams.nodes.find(
     (team) => team.name === teamName
@@ -11,13 +20,14 @@ function randomAvatars(teamName) {
       )
     )
     .sort(() => 2 * Math.random() - 1);
-  const container = d3.create('div')
-    .classed('randomAvatars', true);
-  container.selectAll('img')
+  const container = d3.create("div").classed("randomAvatars", true);
+  container
+    .selectAll("img")
     .data(people)
     .enter()
-      .append('img')
-      .attr('src', person => person.avatarUrl)
-      .attr('title', person => person.name);
+    .append("img")
+    .attr("src", (person) => person.avatarUrl)
+    .attr("title", (person) => person.name);
+  // TODO: link to the Who We Are page, when a profile picture is clicked
   return container.node();
 }

index.qmd

@@ -83,6 +83,29 @@ randomAvatars("Hacky Hour");
 
 :::::
 
+### ResBaz Festival 
+
+::::: {.split-section}
+
+![ResBaz Festival](img/resbazAZ2024_squareFlyer.png){.side-image .lightbox} \
+
+::: {.split-chunk}
+**Where**: Arizona
+
+**When**: Annually, for a few days in the spring (Apr/May)
+
+**What**: Learn, Network, Teach, Help, and Discuss are just a few of the availble things to do at ResBaz. Use the festival to add organizing events or presenting technical workshops to your resume, or simply attend and pick up a new data science trick, the choice is all yours!
+
+**Who you're likely to see**:
+
+```{ojs}
+randomAvatars("Festival2024");
+```
+
+:::
+
+:::::
+
 ### Related Community Events
 
 #### Code Commons

resbaz/resbazTucson2024.qmd

@@ -39,7 +39,7 @@ Learn, Network, Teach, Help, and Discuss are just a few of the availble things t
 
 #### Accessibility
 
-We are committed to making this workshop accessible to everybody. For any accommodation requests, please contact us at <[email protected]>. We will do our best to make the event inclusive to all. 
+We are committed to making this workshop accessible to everybody. For any accommodation requests, please contact us at <ResBazAZ+JEDI@gmail.com>. We will do our best to make the event inclusive to all. 
 
 ## Previous years
 

styles/index.css

@@ -29,6 +29,7 @@
 }
 .randomAvatars {
   display: flex;
+  flex-wrap: wrap;
   gap: 1em;
 }
 .randomAvatars img {