Merge branch 'main' into virtualbox_arm_support

Author: bmcutler

Gemfile.lock

@@ -221,7 +221,7 @@ GEM
       gemoji (>= 3, < 5)
       html-pipeline (~> 2.2)
       jekyll (>= 3.0, < 5.0)
-    json (2.13.2)
+    json (2.18.1)
     kramdown (2.4.0)
       rexml
     kramdown-parser-gfm (1.1.0)
@@ -283,7 +283,7 @@ GEM
       concurrent-ruby (~> 1.0)
     unicode-display_width (1.8.0)
     uri (0.13.0)
-    webrick (1.9.1)
+    webrick (1.9.2)
     yell (2.2.2)
 
 PLATFORMS

_docs/developer/getting_started/index.md

@@ -9,11 +9,23 @@ redirect_from:
 ---
 
 
+Join our Community Discussion on Zulip:
+[Contact Us](/contact)
 
-## Suggestions for New Developers
+## Setting Up
 
-* Join our Community Discussion on Zulip:
-  [Contact Us](/contact)
+* Submitty primarily uses the following languages/frameworks: 
+[PHP](/developer/software_and_system_design/coding_style_guide/php), 
+[Twig](/developer/developing_the_php_site/view#rendering-the-user-page-with-twig), 
+[JavaScript](/developer/software_and_system_design/coding_style_guide/javascript),
+[TypeScript](/developer/developing_the_php_site/javascript#typescript), 
+[Vue](/developer/developing_the_php_site/view#another-option-rendering-with-vue), 
+[PostgreSQL](/developer/software_and_system_design/database_design), 
+[Python](/developer/software_and_system_design/coding_style_guide/python), 
+[C++](/developer/software_and_system_design/coding_style_guide/c++).
+
+* To support development, Submitty uses Git/GitHub, Vagrant, [Cypress E2E Testing](/developer/testing/cypress), 
+PHP/Python unit tests, and a variety of linters and formatters.
 
 * You'll need to set up the full system on your own computer.  The
   easiest method is to
@@ -23,13 +35,13 @@ redirect_from:
   up networking, SSL/https, etc.) by following the
   [complete system administrator instructions](/sysadmin/installation/index).
 
-* Read through the
+* Once the system has been successfully installed, read through the
   [Student](/student/account/index),
   [Grader](/grader/index), and
   [Instructor](/instructor)
-  instructions and try it out.
+  instructions to test it out.
 
-* Learn how to use git.
+## Making Contributions
 
 * Browse our open [GitHub Pull Requests](https://github.com/Submitty/Submitty/pulls).
   Pick an open PR and read the PR notes, linked issues, and other documentation.
@@ -39,42 +51,38 @@ redirect_from:
 
 * Look through our [GitHub Issues lists](https://github.com/Submitty/Submitty/issues) for some ideas
   of problems to explore.
-
   * _**IMPORTANT NOTE**: We can only "assign" GitHub issues to users
-    who are already members of the Submitty GitHub organization.  But
+    who are already members of the Submitty GitHub organization, however,
     we are very happy to accept, review, and merge contributions from
-    outside of the organization.  Students selected for Google Summer
+    outside of the organization. Students selected for Google Summer
     of Code and active developers who already have multiple
     contributions will be added to the Submitty GitHub organization._
-  
+
 * Learn what sections of the code are relevant for those issues (so
   you’re not overwhelmed).
-
-   * Hint: Use "git grep" to search for variables/filenames/specific
+   * Use "git grep" to search for variables/filenames/specific
      strings within the source files/directories.  This can help you
      locate relevant files.
+   * For Developers using VS Code: Use `Ctrl+Shift+F` to search for words inside 
+     of files. Use `Ctrl+P` to search for filenames.
 
 * Add & delete things to the code, re-install that portion of the
   system and see what happens.  See also [Development Instructions](/developer/development_instructions).
 
-* Use inspector, browser debugger, javascript console, etc.
-
-   * Hint: It is helpful to set your javascript console errors to
-     be persistent (so they don't disappear when the page reloads).
-     E.g., in Chrome, you need to set "Console:Preserve log on
-     navigation", or in Firefox, "Enable persistent logs".
-
-* As you read the code, make a diagram for yourself of how the system
-  fits together.
-
-* Use jsfiddle (for testing or demoing new things).
+* Browser DevTools allow you to inspect, debug, and experiment with web pages.
+   * The `Elements/Inspector` tab provides a view of the DOM, and the CSS classes being applied to elements.
+   * The `Console` tab shows browser messages and allows you to run JS on the page.
+      * Use `console.log` in JavaScript to output to the console.
+      * HINT: Set your javascript console errors to
+        be persistent. This will make any outputs persist on reload.
+   * The `Network` tab is helpful for seeing what requests are being made.
+   * The `Application/Storage` tab allows you to view cookies and items in localStorage.
 
-* Keep a work diary / log: what did you plan to do today, keep track
-  of how long it took you to do things, difficulties, how did you
-  solve it, helpful reference links, and what’s your plan for
-  tomorrow.
+## Helpful Links
 
-* Get familiar with vagrant.
+These links may be useful throughout your development experience. _REMEMBER:_ If 
+you ever have any questions about the Submitty's workflow, the codebase, or a 
+specific feature, search `submitty.org` first.
 
 * Run the relevant portions of test suite locally:  
   [Submitty Testing Instructions](/developer/testing/)

_docs/developer/getting_started/make_a_pull_request.md

@@ -35,12 +35,17 @@ Be sure to read the [Suggestions for New Developers](/developer/getting_started/
    PRs can be made from either type of branch.
 
 
-3. Before submitting a PR or updating an existing PR, you should make
+3. Please note our policy on the [Usage of Generative AI / LLMs](https://github.com/Submitty/Submitty/blob/main/CONTRIBUTING.md).
+
+   Pull requests that do not adhere to these guidelines may be closed by the Submitty administrators.
+
+
+4. Before submitting a PR or updating an existing PR, you should make
    sure your code follows our [Style Guide](/developer/coding_style_guide)
    and passes the relevant [tests](/developer/testing).
 
 
-4. The PR title should be useful and descriptive.
+5. The PR title should be useful and descriptive.
 
     * Titles of PR, Issues, and commits should be <= 50 characters. 
 
@@ -119,7 +124,7 @@ Be sure to read the [Suggestions for New Developers](/developer/getting_started/
     it till it does pass validation.
 
 
-4. The body of the PR should describe the purpose of the PR.
+6. The body of the PR should describe the purpose of the PR.
 
      * When merged, this PR body will be part of the documentation for
        the