Update guide structure

contrib/index.rst → guides/contrib.rst

 .. _gsoc_contribution_guide:
 
-Contribution
-#############
+Contribution guide
+###################
 
 `GSoC <https://gsoc.beagleboard.io/>`_ site uses `OpenBeagle Continous Integration (CI) / Continous Development 
 (CD) <https://docs.gitlab.com/ee/ci/>`_ which is a continuous method of software development, where 

guides/index.rst

+.. _gsoc-guides:
+
+Guides
+######
+
+This section includes guides for :ref:`students <student-guide>` & :ref:`mentors <mentor-guide>` who want to participate 
+in GSoC 2024 with `BeagleaBoard.org <www.beagleboard/org>`_. It's highly recommended to check `GSoC Frequently Asked Questions 
+<https://developers.google.com/open-source/gsoc/faq>`_. For anyone who just want to contribute to this site we also have 
+a step by step :ref:`contribution guide <gsoc_contribution_guide>`.
+
+.. card::
+    :link: student-guide
+    :link-type: ref
+
+    **GSoC Contributor/Student Guide**
+    ^^^^
+
+    If you want to increase your chances of being accepted into (and succeed during) Google Summer of Code we strongly 
+    encourage you to read this guide! It is particularly helpful for tips on writing a good project proposal and how 
+    potential contributors should interact with the communities they are interested in working with during the program.
+
+.. card:: 
+    :link: mentor-guide
+    :link-type: ref 
+        
+    **Mentor Guide**
+    ^^^^
+
+.. card:: 
+    :link: mentor-guide
+    :link-type: ref 
+        
+    **Proposal Guide**
+    ^^^^
+
+.. card:: 
+    :link: mentor-guide
+    :link-type: ref 
+        
+    **Contribution Guide**
+    ^^^^
+
+
+
+
+.. toctree:: 
+    :hidden:
+    :maxdepth: 2
+
+    students 
+    mentors
+    proposal
+    contrib
\ No newline at end of file

guides/mentors.rst

+.. _mentor-guide:
+
+Mentor guide 
+############
\ No newline at end of file

guides/proposal.rst

+.. _proposal-guide:
+
+Proposal guide 
+###############
\ No newline at end of file

guides/students.rst

+.. _student-guide:
+
+Student guide 
+#############
+
+General requirements
+********************
+
+All projects have the following basic requirements:
+
+1. Students must create accounts on `OpenBeagle <https://openbeagle.org/>`_, `Discord <http://bbb.io/gsocchat>`_ and `Beagle Forum <http://bbb.io/gsocml>`_ prior to creating their application.
+2. All newly generated materials must be released under an `open source license <http://www.opensource.org/licenses>`_. Individual students shall retain copyright on their works.
+3. Students will demonstrate their ability to cross-compile and utilize version control software by creating a “Hello World” application and generating a pull request to `jadonk/gsoc-application <https://github.com/jadonk/gsoc-application/tree/master/ExampleEntryJasonKridner>`_. For assistance, please visit `Discord <http://bbb.io/gsocchat>`_ or utilize the `Beagle Forum <http://bbb.io/gsocml>`_. The “Hello World” application must print your name and the date out in an ARM Linux environment. Freely available emulators may be used to test your application or you can ask anyone on the chat or mailing list to help you test.
+4. All projects will produce reusable software components and will not be “what–I-built-over-my-summer-vacation” projects. Including a hardware component is welcome, but the project deliverable will be software that may be utilized by a wide audience of the `BeagleBoard.org <http://beagleboard.org/>`_ community.
+5. Students will demonstrate their ability to collaborate by creating a project proposal on this site using our :ref:`proposal template <proposal_template>` and utilizing `Discord <http://bbb.io/gsocchat>`_ to collect quotes regarding the usefulness of their proposal to the `BeagleBoard.org <http://beagleboard.org/>`_ community. **Use of Google Docs for proposal development is discouraged due to insufficient revision control and extensive use of computing resources having numerous documents open simultaneously**.
+6. Source code generated during the project must be released on OpenBeagle (and we’ll setup a mirror on `Github.com <http://github.com/>`_).
+7. Students will provide two recorded audio/video presentations uploaded to Youtube or Vimeo (screencasts are appropriate), one near the beginning of the project summarizing their project goals and another in the wrap-up phase to summarize their accomplishments. Examples can be found on `http://beagleboard.org/gsoc <http://beagleboard.org/gsoc>`_. There is no requirement to show your faces or use English.
+
+.. important:: 
+
+    To help you to break your project down into manageable chunks and also to help the project’s mentors to better support 
+    your efforts, weekly project status reports should be e-mailed to the the `Beagle Forum <http://bbb.io/gsocml>`_. 
+    Each status report should outline:
+
+    1. What was accomplished that week,
+    2. Any issues that prevented that week’s goals from being completed and
+    3. your goals for the next week.
\ No newline at end of file

index.rst

@@ -137,6 +137,6 @@ GSoC @ BeagleBoard.org
    :hidden:
 
    ideas/index
+   guides/index
    proposals/index
-   contrib/index
    projects/index