Updated projects and leadership for 2021 school year

codethechange · Sep 30, 2021 · a18236f · a18236f
1 parent 45bebb8
commit a18236f
Show file tree

Hide file tree

Showing 7 changed files with 265 additions and 292 deletions.
diff --git a/package.json b/package.json
@@ -15,9 +15,9 @@
     "css-loader": "*",
     "jquery": "^3.5.0",
     "moment": "^2.23.0",
-    "node-sass": "^4.11.0",
+    "node-sass": "^6.0.1",
     "popper.js": "^1.14.6",
-    "sass-loader": "^7.1.0",
+    "sass-loader": "10",
     "style-loader": "^0.23.1",
     "vue": "^2.5.17",
     "vue-loader": "^15.5.0",

diff --git a/setup/README.md b/setup/README.md
@@ -26,7 +26,7 @@ Next, automatically get the correct environment by running `pipenv shell` within
 
 ### A Quick Overview of `projects.json`
 All the project UI is loaded from one JSON array: `src/data/projects.json`.
-For each project is a JSON objcet with the following structure:
+For each project is a JSON object with the following structure:
 - background: The main iconography for the project. It should be a file path to an image within the `public/assets` folder.
 - bullets: A JSON string array that summarizes the work in a couple bullet points. This will be displayed in the profile listing in the top card.
 - featured: a boolean that determines whether this project will be displayed.
@@ -60,4 +60,4 @@ python add_images_to_project.py [name] [path_to_image_file] [caption]
 ```
 The `[name]` field should correspond to the same field in the JSON object described above, and the `[caption]` field should be the string that you want to be displayed under the image to give it context.
 
-If you have any questions, feel free to contact [drewgreg@stanford.edu]
+If you have any questions, feel free to contact [aperez01@stanford.edu] or [[email protected]].
diff --git a/setup/hospitalrun.html b/setup/hospitalrun.html
@@ -6,8 +6,9 @@
         (release build), which will be a significant improvement for current users compared to the beta build.
       </p>
       <p>
-        More on this prospective project coming soon! For additional information about HospitalRun’s mission and implementation,
-        visit <a href="https://hospitalrun.io">hospitalrun.io.</a>
+        Some of the features we worked on last year include viewable diagnoses, inventory modules, and incident notes! For 
+        additional information about HospitalRun’s mission and implementation, visit 
+        <a href="https://hospitalrun.io">hospitalrun.io.</a>
       </p>
     </div>
   </body>

diff --git a/src/data/people.json b/src/data/people.json
@@ -36,7 +36,7 @@
         },
         "name": "Anthony Perez",
         "leadership": true,
-        "role": "Financial Officer/Design Lead"
+        "role": "Co-President/Team Lead"
     },
     "austinryanchow": {
         "imageSrc": "./assets/austinchow.jpg",
@@ -85,7 +85,6 @@
             "github": "https://github.com/U8NWXD",
             "linkedin": "https://www.linkedin.com/in/christopher-skalnik"
         },
-        "leadership": true,
         "name": "Chris Skalnik",
         "role": "Co-President/Team Lead"
     },
@@ -100,7 +99,6 @@
         "role": "Developer"
     }, 
     "drew": {
-        "leadership": true,
         "imageSrc": "./assets/drew_photo.jpg",
         "links": {
             "email": "mailto:[email protected]",
@@ -227,7 +225,8 @@
             "linkedin": "https://www.linkedin.com/in/james-zheng2/"
         },
         "name": "James Zheng",
-        "role": "Developer"
+        "leadership": true,
+        "role": "Financial Officer/Team Lead"
     },    
     "jasonzhao": {
         "imageSrc": "./assets/jason_zhao_photo.JPG",
@@ -335,7 +334,7 @@
         },
         "name": "Nadin Tamer",
         "leadership": true,
-        "role": "Social Coordinator/Developer"
+        "role": "Co-President/Team Lead"
     },
     "raymondyao": {
         "imageSrc": "./assets/raymond_yao_photo.jpg",

diff --git a/src/data/projects.json b/src/data/projects.json
@@ -181,14 +181,9 @@
         "narrative": "<p>Unlike other education platforms, <a href='https://www.oppiafoundation.org/about'>Oppia</a> is heavily volunteer-based, from the people who create the lessons to the developers who build new features. Because of this, it is structured as a strong network of open source developers, artists, teachers, and students. From day 1, as a part of the Oppia team, you will be welcomed by an onboarding team at Oppia, which will help you through an initial starter project.</p><p>In previous years, students who worked with Oppia have developed new features like Takeout, which lets users manage and delete their own data, and a Docker container to allow Oppia's Windows developers to have the same convenience as Linux and macOS developers. As an open source developer for Oppia, you will be interacting with programmers who have the same motivations as you all across the world, from India to Malaysia to the US.</p><p>Based on AngularJS and Python, Oppia is constantly improving its platform through direct feedback from the students, teachers, and volunteers. Oppia regularly tests its lessons with students around the world, and they conduct randomized trials to ensure their platform is effective. Therefore, you can rest assured that your contributions to Oppia are actually supporting students' education around the world. Examples of future projects that you can work on include creating features to help teachers craft effective lessons, developing Oppia's Android application, improving the lesson feedback pipeline from the user to the teacher, and developing Oppia's testing and quality assurance infrastructure to make sure the platform is reliable for students.</p><p>If you would like to learn more, check out Oppia's <a href='https://github.com/oppia/oppia'>GitHub</a> and <a href='https://oppia.org'>website</a>.",
         "organization": "Oppia is an online education platform that serves almost 430,000 students worldwide. ",
         "summary": "We support high-quality online learning experiences for students with limited access to formal education.",
-        "team": [
-            "chris",
-            "nadintamer",
-            "avigupta",
-            "scottxu"
-        ],
+        "team": [],
         "wip": true,
-        "year": 2020
+        "year": 2021
     },
     {
         "assets": [
@@ -251,10 +246,8 @@
         "narrative": "<p>        During the 2019-2020 school year, we built a filtering system for Tarjimly so that users within the app can        search for translators with specific criteria such as professional expertise, phone interpretation, document        translation, and demographic preferences. These filters enable refugees and aid workers to bypass the vocational        and cultural barriers that arise with traditional language translation.      </p><p>        For the front-end work, we used React Native and Redux in order to populate the UI and maintain the application\u2019s        state when users select certain filters. When a user selects the \u201cFilters\u201d button before searching for translators,        they are introduced to a pop-up modal that shows them a list of two types of filters: \u201chard\u201d filters and \u201csoft\u201d        filters. Hard filters (e.g. medical or legal translating) are mandatory constraints that are guaranteed to be met        when connecting with a translator, while soft filters (e.g. urgent translator, translator from my organization)        are satisfied given certain constraints such as the number of translators available, the number of other soft        filters satisfied, etc.      </p><p>        Once we enabled the ability to select filters on the front-end, the next step was to create a REST API endpoint        that parses and sends these filters (in addition to other data) to the server for processing. From here, the final        step to select a sufficient number of filtered translators was to build a Python + Django microservice to fetch        translators from the database, algorithmically filter out the ineligible translators based on various parameters,        and then return the remaining translators back to the server. At this point, the final step entailed sending a        response back to the front-end, where the user could finally be matched with a translator based on the filters.      </p><p>        Overall, this was an excellent opportunity for us to learn about full-stack engineering, product planning (both        design-wise and algorithmically), and teamwork. Our Tarjimly project provided the right balance between having a        robust support structure and allowing for creative freedom. If this kind of project seems interesting to you, there        are several ongoing projects that we think you\u2019d like!      </p>",
         "organization": "Tarjimly",
         "summary": "Tarjimly provides humanitarian assistance to refugees struggling with language barriers by connecting them with live translators.",
-        "team": [
-            "anthonyperez"
-        ],
-        "wip": false,
+        "team": [],
+        "wip": true,
         "year": "2020"
     },
     {
@@ -268,17 +261,15 @@
         "bullets": [
             "HospitalRun is free, open source software that provides hospitals and other medical care facilities in the developing world with access to offline-first electronic health records and an easy-to-use hospital information system."
         ],
-        "featured": false,
+        "featured": true,
         "icon": null,
         "name": "HospitalRun",
-        "narrative": "<p>For the upcoming school year, our focus will be on getting HospitalRun\u2019s desktop and web React apps to version 2.0        (release build), which will be a significant improvement for current users compared to the beta build.      </p><p>        More on this prospective project coming soon! For additional information about HospitalRun\u2019s mission and implementation,        visit <a href=\"https://hospitalrun.io\">hospitalrun.io.</a></p>",
+        "narrative": "<p>        For the upcoming school year, our focus will be on getting HospitalRun\u2019s desktop and web React apps to version 2.0        (release build), which will be a significant improvement for current users compared to the beta build.      </p><p>        Some of the features we worked on last year include viewable diagnoses, inventory modules, and incident notes! For         additional information about HospitalRun\u2019s mission and implementation, visit         <a href=\"https://hospitalrun.io\">hospitalrun.io.</a></p>",
         "organization": "HospitalRun",
         "summary": "HospitalRun is free, open source software that provides hospitals and other medical care facilities in the developing world with access to offline-first electronic health records and an easy-to-use hospital information system.",
-        "team" : [
-            "drew", "anthonyperez", "cpondoc", "gabrielacortes", "jameszheng", "jeremykim", "cynthiachen"
-        ],
+        "team": [],
         "wip": true,
-        "year": "2020"
+        "year": "2021"
     },
     {
         "assets": [
@@ -302,4 +293,4 @@
         "wip": false,
         "year": "2020"
     }
-]
+]
diff --git a/src/views/Partner.vue b/src/views/Partner.vue
@@ -129,7 +129,7 @@ export default {
             this.submitting = false
             if (res.error) {
               this.finishedTitle = 'Form Submission Error. '
-              this.finishedMessage = 'Unfortunately, we\'ve encountered some server error. Please email drewgreg [at] stanford [dot] edu with your form contents.'
+              this.finishedMessage = 'Unfortunately, we\'ve encountered some server error. Please email nadint [at] stanford [dot] edu with your form contents.'
             } else {
               this.finishedTitle = 'Form Submitted!'
               this.finishedMessage = 'Thank you for reaching out. We will get back to you if we think your project is a good fit.'
@@ -140,7 +140,7 @@ export default {
               this.submitted = true
               this.submitting = false
               this.finishedTitle = 'Form Submission Error. '
-              this.finishedMessage = 'Unfortunately, we\'ve encountered some server error. Please email drewgreg [at] stanford [dot] edu with your form contents.'
+              this.finishedMessage = 'Unfortunately, we\'ve encountered some server error. Please email nadint [at] stanford [dot] edu with your form contents.'
             }
           })
       }