diff --git a/_static/images/logo-latex.pdf b/_static/images/logo-latex.pdf
index deaa2699d6de4ab582af1ae276ca36d8f341cca0..5491dbf79bebb11b097c750078a4402941b6a9b8 100644
Binary files a/_static/images/logo-latex.pdf and b/_static/images/logo-latex.pdf differ
diff --git a/_static/latex/preamble.tex b/_static/latex/preamble.tex
new file mode 100644
index 0000000000000000000000000000000000000000..e13368a5c75605a23fd88423ca902350431ef83f
--- /dev/null
+++ b/_static/latex/preamble.tex
@@ -0,0 +1,25 @@
+% LaTeX documentation preamble
+%
+% Copyright (c) 2021 Nordic Semiconductor ASA
+% SPDX-License-Identifier: Apache-2.0
+
+\usepackage[some]{background}
+\usepackage{sectsty}
+\usepackage{lscape}
+\usepackage{longtable}
+\usepackage{fontspec}
+\usepackage{comment}
+\defaultfontfeatures{Mapping=tex-text,Scale=MatchLowercase}
+\setmainfont{DejaVuSans}
+\setmonofont{FreeMono}
+
+\definecolor{bg-color}{HTML}{a97f2c}
+
+\setcounter{tocdepth}{2}
+
+\addto\captionsenglish{\renewcommand{\contentsname}{Table of contents}}
+
+\allsectionsfont{\color{bg-color}}
+
+\let\oldtabular\tabular
+\renewcommand{\tabular}{\footnotesize\oldtabular}
diff --git a/_static/latex/title.tex b/_static/latex/title.tex
new file mode 100644
index 0000000000000000000000000000000000000000..b6b842995a9102e42dc92a41022a841b82d8d76d
--- /dev/null
+++ b/_static/latex/title.tex
@@ -0,0 +1,43 @@
+% LaTeX documentation title page
+%
+% Copyright (c) 2021 Nordic Semiconductor ASA
+% SPDX-License-Identifier: Apache-2.0
+
+\makeatletter
+\newgeometry{top=3cm,left=0cm,right=0cm,bottom=2.5cm}
+
+\backgroundsetup{
+    scale=1,
+    contents={\sphinxlogo},
+    opacity=0.7,
+    angle=0,
+    position={0.40\textwidth,-0.60\textheight}
+}
+
+\BgThispage
+
+\begin{minipage}{2cm}
+    \color{bg-color} \rule{2cm}{1.7cm}
+\end{minipage}
+\hspace{0.2cm}
+\begin{minipage}{2cm}
+    \sphinxlogo
+\end{minipage}
+\hspace{0.2cm}
+\begin{minipage}{14cm}
+    \color{bg-color} \Large \textbf{\@title}
+\end{minipage}
+
+\vspace{21cm}
+
+\begin{flushright}
+    \begin{minipage}{4cm}
+        \large \@author\\\@date
+    \end{minipage}
+    \begin{minipage}{1.5cm}
+        \color{bg-color} \rule{1.5cm}{1.3cm}
+    \end{minipage}
+\end{flushright}
+
+\restoregeometry
+\makeatother
diff --git a/conf.py b/conf.py
index 6295fdf202533199e004227437da9d7651d2c329..97c04781da4ec56b23d4a7df26d45c326fb32e8f 100644
--- a/conf.py
+++ b/conf.py
@@ -33,11 +33,10 @@ exclude_patterns = ['_build', 'Thumbs.db', '.DS_Store', 'env', ".venv"]
 
 pages_url = "https://gsoc.beagleboard.io"
 pages_slug = "latest"
-gitlab_user = "gsoc"
-gitlab_version = "main"
-gitlab_url = "https://openbeagle.org"
-gitlab_repo = "gsoc.beagleboard.io"
-docs_url = "https://gsoc.beagleboard.io/latest/"
+
+# What was here was not part of the "General configuration"
+# first place I could find something was at https://pydata-sphinx-theme.readthedocs.io/en/stable/user_guide/source-buttons.html
+
 
 # -- Options for HTML output -------------------------------------------------
 # https://www.sphinx-doc.org/en/master/usage/configuration.html#options-for-html-output
@@ -83,7 +82,7 @@ html_theme_options = {
         },
         {
             "name": "BeagleBoard.org",
-            "url": "https://beagleboard.org",
+            "url": "https://www.beagleboard.org",
             "icon": "_static/images/boris.svg",
             "type": "local",
             "attributes": {"target": "_blank"},
@@ -113,14 +112,39 @@ html_theme_options = {
 
 html_context = {
     "display_gitlab": True,
-    "gitlab_url": gitlab_url,
-    "gitlab_user": gitlab_user,
-    "gitlab_repo": gitlab_repo,
+    "gitlab_url": "https://openbeagle.org",
+    "gitlab_user": "gsoc",
+    "gitlab_repo": "gsoc.beagleboard.io",
     "gitlab_version": "main",
     "doc_path": "",
     "conf_py_path": "",
     "show_license": True,
-    "pages_url": pages_url,
-    "pages_slug": pages_slug,
-    "docs_url": docs_url,
-}
\ No newline at end of file
+    "pages_url": "https://gsoc.beagleboard.io",
+    "pages_slug": "",
+    "docs_url": "https://docs.beagleboard.org/latest/",
+    "edit_page_url_template": "{{ my_vcs_site }}{{ file_name }}",
+    "edit_page_provider_name": "OpenBeagle",
+    "my_vcs_site": "https://openbeagle.org/gsoc/gsoc.beagleboard.io/-/edit/main/",
+}
+
+# -- Options for proposal PDF generation --
+latex_elements = {
+    "papersize": "a4paper",
+    "maketitle": open("_static/latex/title.tex").read(),
+    "preamble": open("_static/latex/preamble.tex").read(),
+    "sphinxsetup": ",".join(
+        (
+            "verbatimwithframe=false",
+            "VerbatimColor={HTML}{f0f2f4}",
+            "InnerLinkColor={HTML}{2980b9}",
+            "warningBgColor={HTML}{e9a499}",
+            "warningborder=0pt",
+            r"HeaderFamily=\rmfamily\bfseries",
+        )
+    ),
+}
+latex_engine = "xelatex"
+latex_logo = str("_static/images/logo-latex.pdf")
+latex_documents = [
+    ("proposals/template", "template.tex", "Project proposal template 2024", "John Doe", "manual"),
+]
\ No newline at end of file
diff --git a/contrib/index.rst b/contrib/index.rst
index ea78709242c6358bf3327e42b7f9a3d05cad307c..81ede1c14cfed42ab80987364c1845aecf1edc48 100644
--- a/contrib/index.rst
+++ b/contrib/index.rst
@@ -9,7 +9,7 @@ you continuously build, test, deploy, and monitor iterative code changes. which
 anything on your local machine to update anything on the site. To contribute to this site, you can follow the 
 simple steps provided below.
 
-.. note:: `OpenBeagle <https://openbeagle.org/>`_ is a self hosted instance of OpenSource program called `GitLab <https://about.gitlab.com/>`_.
+.. note:: `OpenBeagle <https://openbeagle.org/>`_ is a self hosted instance of open source program called `GitLab <https://about.gitlab.com/>`_.
 
 Fork the project
 *****************
@@ -48,16 +48,16 @@ After selecting the file you have to click on ``edit button`` and then choose ei
     :align: center
 
 .. note:: 
-    Choosing Web IDE will load a `Visual Studio Code Server <https://code.visualstudio.com/docs/remote/vscode-server>`_ 
+    Choosing ``Web IDE`` will load a `Visual Studio Code Server <https://code.visualstudio.com/docs/remote/vscode-server>`_
     instance which is a feature rich source code editor. Depending on the internent connection your machine will take some to 
     load the editor and it can be a bit heavy for some machines to handle. Once fully loaded it should run smoothly but, if that is 
-    not the case then please consider using single file editor option. Considering majority of the users will be using Web IDE option, 
-    we are using the Web IDE for the rest of this guide. 
+    not the case then please consider using single file editor option. Considering majority of the users will be using ``Web IDE`` option,
+    we are using the ``Web IDE`` for the rest of this guide.
 
 Start editing
 *************
 
-If you select to open your file in web IDE you'll see a familar interface. The GitLab web IDE is actually a rich 
+If you select to open your file in ``Web IDE`` you'll see a familar interface. The GitLab Web IDE is actually a rich
 `Visual Studio Code Server <https://code.visualstudio.com/docs/remote/vscode-server>`_ hosted on OpenBeagle.
 
 .. image:: media/ide.png
@@ -79,8 +79,6 @@ If you select to open your file in web IDE you'll see a familar interface. The G
    For more detailed comparison you can checkout `this article on reStructuredText vs. Markdown for technical 
    documentation <https://eli.thegreenplace.net/2017/restructuredtext-vs-markdown-for-technical-documentation/>`_
 
-
-
 Now you have to select a file and start editing. Below image shows some,
 
 1. Edits made to the `ideas/index.rst` highlighted with green bar on left side of code editor window near line numbers.
@@ -156,4 +154,4 @@ below shows all the feilds you have to update,
     :align: center
 
 Now wait for the review and if comments/requests are raised then you can continue working on the project 
-until everything looks perfect and your changes are merged in upstream.
\ No newline at end of file
+until everything looks perfect and your changes are merged in upstream.
diff --git a/ideas/linux-kernel-improvements.rst b/ideas/linux-kernel-improvements.rst
index 645b21793ab939bfc1430e35c45207da92b151c2..72b335bf7f87d09da25d0261447c4716c51a6732 100644
--- a/ideas/linux-kernel-improvements.rst
+++ b/ideas/linux-kernel-improvements.rst
@@ -7,7 +7,7 @@ Below are the projects that comes under linux kernel improvements category.
 
 .. card:: 
 
-    :fab:`linux;pst-color-secondary` **BeagleBone Cape (add-on board) compatibility layer (BB-CCL)**
+    :fab:`linux;pst-color-secondary` **BeagleBone Cape (add-on board) compatibility layer (BB-CCL)** :bdg-danger:`High priority` :bdg-success:`Medium complexity` :bdg-danger-line:`Large size`
     ^^^^
 
     - **Goal:** Update the cape compatibility layer for BeagleBone Black, AI-64, and newer boards to support more kernel versions.
@@ -23,10 +23,13 @@ Below are the projects that comes under linux kernel improvements category.
         - `GSoC 2020 project page <https://elinux.org/BeagleBoard/GSoC/2020_Projects/Cape_Compatibility>`_
         - `lorforlinux's GSoC project documentation website <https://lorforlinux.github.io/GSoC2020_BeagleBoard.org/>`_
 
-
     ++++
 
-    :bdg-danger:`High priority` :bdg-success:`Medium complexity` :bdg-danger-line:`Large size`
+    .. button-link:: https://example.com
+      :color: secondary
+      :expand:
+
+      :fab:`gitlab;pst-color-light` Discuss on forum
 
 .. card:: 
 
diff --git a/index.rst b/index.rst
index 2a93db42276525930d6cfb30a4c118bf252f703a..db0dedfe958e3f69322e038be80e8ab60a0fc468 100644
--- a/index.rst
+++ b/index.rst
@@ -8,35 +8,35 @@
 GSoC @ BeagleBoard.org
 #######################
 
-Work on awesome OpenSource projects this summer with BeagleBoard.org!
+Work on awesome open source projects this summer with BeagleBoard.org!
 
 .. admonition:: What is Google Summer of Code?
    :class: admonition-code
 
-   Spend your summer break writing code and learning about open source development while earning money! 
-   Accepted students work with a mentor and become a part of the open source community. Many become lifetime 
-   open source developers! The 2024 student application window will be open from 
-   `March 18th 2024 <https://developers.google.com/open-source/gsoc/timeline#march_18_-_1800_utc>`_ to 
-   `April 2nd 2024 <https://developers.google.com/open-source/gsoc/timeline#april_2_-_1800_utc>`_! 
-   But don't wait for then to engage! Come to our `Discord <https://discord.com/invite/e58xECGWfR>`_ and 
-   `Forum <https://forum.beagleboard.org/>`_ to share ideas today.
+   Spend your summer break writing code and learning about open source development while earning money!
+   Accepted students work with a mentor and become a part of the open source community. Many become lifetime
+   open source developers! The 2024 student application window will be open from
+   `March 18th 2024 <https://developers.google.com/open-source/gsoc/timeline#march_18_-_1800_utc>`_ to
+   `April 2nd 2024 <https://developers.google.com/open-source/gsoc/timeline#april_2_-_1800_utc>`_!
+   But don't wait for then to engage! Come to our `Discord <https://discord.com/invite/e58xECGWfR>`_ and
+   `Forum <https://forum.beagleboard.org/c/gsoc>`_ to share ideas today.
 
-.. note:: 
+.. note::
 
-   Google Summer of Code is open to individuals age 18 and older in most countries who are new or beginner 
-   contributors to open source coding projects. Read more on the GSoC site 
-   `Rules page <https://summerofcode.withgoogle.com/rules>`_ and the 
-   `FAQ page <https://developers.google.com/open-source/gsoc/faq>`_. 
+   Google Summer of Code is open to individuals age 18 and older in most countries who are new or beginner
+   contributors to open source coding projects. Read more on the GSoC site
+   `Rules page <https://summerofcode.withgoogle.com/rules>`_ and the
+   `FAQ page <https://developers.google.com/open-source/gsoc/faq>`_.
 
 .. grid:: 1 2 2 3
 
    .. grid-item-card::
       :link: https://openbeagle.org/
 
-      :fab:`gitlab;pst-color-primary` OpenSource Development
+      :fab:`gitlab;pst-color-primary` Open Source Development
       ^^^^^^^^^^
 
-      Experience working on impactful OpenSource project which 
+      Experience working on impactful open source project which
       will be used by thousands of people around the world!
 
    .. grid-item-card::
@@ -45,7 +45,7 @@ Work on awesome OpenSource projects this summer with BeagleBoard.org!
       :fas:`microchip;pst-color-primary` Free Hardware
       ^^^^^^^^^^
 
-      Recieve BeagleBoard.org OpenSource Single Board Computer, 
+      Recieve BeagleBoard.org open source single board computer,
       debugging tools, and other required hardware for free!
 
    .. grid-item-card::
@@ -54,65 +54,90 @@ Work on awesome OpenSource projects this summer with BeagleBoard.org!
       :fas:`sack-dollar;pst-color-primary` Handsome Stipend
       ^^^^^^^^^^
 
-      Earn while making impactful contributions to the OpenSource 
+      Earn while making impactful contributions to the open source
       community, Stipend can be upto $6600 based on your country.
 
-.. admonition:: BeagleBoard.org Background
+.. admonition:: BeagleBoard.org background
    :class: admonition-clock-back
 
-   BeagleBoard.org is a volunteer organization that seeks to advance the state of 
-   `open-source software <http://en.wikipedia.org/wiki/Open-source_hardware>`_ on open-source 
-   hardware platforms capable of running high-level languages and operating systems (primarily Linux) in embedded 
-   environments. Born from taking mobile phone processors and putting them on low-cost boards to build affordable 
-   desktop computers, BeagleBoard.org has evolved to focus on the needs of the "maker" community with greater focus 
-   on the I/O needed for controlling motors and reading sensors to build things like robots, 3d printers, flying 
-   drones, in-car computer systems and much more. Past BeagleBoard.org GSoC projects included `creating an interpreter 
-   for tiny CPUs <https://elinux.org/BeagleBoard/GSoC/2014_Projects#Project:_BotSpeak_PRU_Firmware>`_, `adding SPI 
-   and sensor support to Python <https://elinux.org/BeagleBoard/GSoC/2014_Projects#Project:_PyBBIO>`_, `an HTML and 
-   git based tutorial sharing environment <https://elinux.org/BeagleBoard/GSoC/2014_Projects#Project:_Bone101>`_, `porting 
-   autopilot software to Linux <https://elinux.org/BeagleBoard/GSoC/2014_Projects#Project:_BeaglePilot>`_, `an open source 
-   100MHz 14-channel logic analyzer <https://elinux.org/BeagleBoard/GSoC/2014_Projects#Project:_BeagleLogic>`_, `using Android 
-   tablets as Linux displays <https://elinux.org/BeagleBoard/GSoC/2014_Projects#Project:_Android_Remote_Display>`_, 
-   `putting ADC support in Linux under the IIO framework <https://elinux.org/BeagleBoard/GSoC/2013_Projects#Linux_ADC_IIO_Support>`_, 
-   `using Android phones as a network boot source <https://elinux.org/BeagleBoard/GSoC/2013_Projects#Android-based_Boot>`_, `Running Arduino 
-   code on Linux <https://elinux.org/BeagleBoard/GSoC/2013_Projects#Userspace_Arduino>`_, `Robot Operating System support 
-   within the Yocto Project build system <https://elinux.org/BeagleBoard/GSoC/2013_Projects#Robot_Operating_System>`_, 
-   `Minix I2C support <https://elinux.org/BeagleBoard/GSoC/2013_Projects#Minix_I2C>`_, `an RPC 
-   framework for heterogeneous processor communication <https://elinux.org/BeagleBoard/GSoC/2010_Projects/C6Run>`_, 
-   `a transparent USB packet sniffer <https://elinux.org/BeagleBoard/GSoC/2010_Projects/USBSniffer>`_, 
-   `ARM optimizations for XBMC <https://elinux.org/BeagleBoard/GSoC/2010_Projects/XBMC>`_, 
-   `ARM optimizations for FFTs <https://elinux.org/BeagleBoard/GSoC/2010_Projects/FFTW>`_, 
-   `make-shift pulse-width-modulation <https://elinux.org/BeagleBoard/GSoC/2010_Projects/Pulse_Width_Modulation>`_ and 
-   `RPC optimizations for OpenCV <https://elinux.org/BeagleBoard/GSoC/2010_Projects/OpenCV>`_. BeagleBoard.org has 
-   benefited from sponsorship from Texas Instruments, Circuitco, Digi-Key, element14 and others, but avoids any dependence 
-   on that sponsorship for sustaining the effort. The project has evolved over the past few years with over 1,000,000 
-   boards in circulation with developers worldwide and strong roots in the Linaro, Yocto Project, Angstrom Distribution, 
-   Debian and Linux communities---and support for running most major Linux distributions including Ubuntu, Android, Fedora, 
-   ArchLinux, Gentoo, Buildroot and many more.
-
-   BeagleBoard was `inspiration for Raspberry Pi <https://web.archive.org/web/20120302232755/www.linuxuser.co.uk/features/raspberry-pi-
-   interview-eban-upton-reveals-all>`_ and PocketBeagle is available for about $25 through over 30 distributors 
-   world-wide (and is even available at Micro Center in the USA), but is more than a throw-away computer. It is an instance 
-   of true open hardware, exposing users to the broader world of electronics, demystifying computers and fostering an environment 
+   BeagleBoard.org is a volunteer organization that seeks to advance the state of
+   `open-source software <http://en.wikipedia.org/wiki/Open-source_software>`_ on `open-source
+   hardware <https://en.wikipedia.org/wiki/Open-source_hardware>`_ platforms capable of
+   running high-level languages and operating systems (like Linux and Zephyr) in embedded
+   environments. Born from taking mobile phone processors and putting them on low-cost boards to build affordable
+   desktop computers, BeagleBoard.org has evolved to focus on the needs of the "maker" community with greater focus
+   on the I/O needed for controlling motors and reading sensors to build things like robots, 3d printers, flying
+   drones, in-car computer systems and much more.  BeagleBoard has `inspired creation of the Raspberry Pi <https://web.archive.org/web/20120302232755/www.linuxuser.co.uk/features/raspberry-pi-interview-eban-upton-reveals-all>`_, built over 6 million computers and made PocketBeagle available world-wide for about $25, but is more than a throw-away computer. It is an instance
+   of true open hardware, exposing users to the broader world of electronics, demystifying computers and fostering an environment
    of clones that have changed the industry for good.
 
-.. important:: 
+   Learn more at https://www.beagleboard.org/about.
 
-   Students will be expected to demonstrate an understanding of cross-compiling before being accepted, but support for 
-   demonstration is available through the IRC channel that typically has approximately 150 online chatters logged on at 
-   any time, most with sufficient experience to explain the process.
+.. admonition:: Some inspirational past projects
+   :class: admonition-youtube hint
 
-.. toctree::
-   :maxdepth: 2
-   :hidden:
-   :caption: Project Ideas
+   Get inspiration from some :ref:`Past_Projects`.
+
+.. grid:: 1 1 3 3
+
+   .. grid-item-card::
+
+      .. youtube:: -giV6Xr8RtY
+         :width: 100%
+
+   .. grid-item-card::
+
+      .. youtube:: RWBzyHNetOE
+         :width: 100%
+
+   .. grid-item-card::
+
+      .. youtube:: CDbEAq33vdA
+         :width: 100%
+
+.. important::
+
+   Students will be expected to execute a series of prerequisites to demonstrate and
+   expand familiarity with embedded systems development. Don't worry, the
+   `live chat <https://bbb.io/gsocchat>`_ channel has over 1,000 active members to
+   travel with you on your journey.
 
-   ideas/index
-   contrib/index
+
+.. admonition:: Some other amazing places to find Beagles
+   :class: hint
+
+   Beagles have been to the depths of space and the oceans, as well as
+   made cheeseburgers. Check the below projects made by incredible
+   professional innovators for some inspiration.
+
+.. grid:: 1 2 2 2
+
+   .. grid-item-card::
+
+      :fas:`rocket;pst-color-primary` Europa Rover Prototype
+      ^^^^^^^^^^
+
+      .. youtube:: sY5WQG3-3mo
+         :width: 100%
+
+   .. grid-item-card::
+
+      :fas:`burger;pst-color-primary` Cheeseburger Robot
+      ^^^^^^^^^^
+
+      .. youtube:: CbL_3le40qc
+         :width: 100%
+
+.. admonition:: Explore some specific project ideas for this year!
+   :class: hint
+
+   Now you are ready to explore this year's :ref:`gsoc-project-ideas`.
 
 .. toctree::
    :maxdepth: 2
    :hidden:
-   :caption: Past Projects
 
-   Projects/index
\ No newline at end of file
+   ideas/index
+   proposals/index
+   contrib/index
+   projects/index
diff --git a/Projects/2010.rst b/projects/2010.rst
similarity index 100%
rename from Projects/2010.rst
rename to projects/2010.rst
diff --git a/Projects/2013.rst b/projects/2013.rst
similarity index 100%
rename from Projects/2013.rst
rename to projects/2013.rst
diff --git a/Projects/2014.rst b/projects/2014.rst
similarity index 100%
rename from Projects/2014.rst
rename to projects/2014.rst
diff --git a/Projects/2015.rst b/projects/2015.rst
similarity index 100%
rename from Projects/2015.rst
rename to projects/2015.rst
diff --git a/Projects/2016.rst b/projects/2016.rst
similarity index 100%
rename from Projects/2016.rst
rename to projects/2016.rst
diff --git a/Projects/2017.rst b/projects/2017.rst
similarity index 100%
rename from Projects/2017.rst
rename to projects/2017.rst
diff --git a/Projects/2018.rst b/projects/2018.rst
similarity index 100%
rename from Projects/2018.rst
rename to projects/2018.rst
diff --git a/Projects/2019.rst b/projects/2019.rst
similarity index 100%
rename from Projects/2019.rst
rename to projects/2019.rst
diff --git a/Projects/2020.rst b/projects/2020.rst
similarity index 100%
rename from Projects/2020.rst
rename to projects/2020.rst
diff --git a/Projects/2021.rst b/projects/2021.rst
similarity index 100%
rename from Projects/2021.rst
rename to projects/2021.rst
diff --git a/Projects/2022.rst b/projects/2022.rst
similarity index 100%
rename from Projects/2022.rst
rename to projects/2022.rst
diff --git a/Projects/2023.rst b/projects/2023.rst
similarity index 100%
rename from Projects/2023.rst
rename to projects/2023.rst
diff --git a/Projects/index.rst b/projects/index.rst
similarity index 70%
rename from Projects/index.rst
rename to projects/index.rst
index 395515abe963fb05a32cd2709bd467e9175854fc..31518f0ab7fb63a182319726f01f260419bb0201 100644
--- a/Projects/index.rst
+++ b/projects/index.rst
@@ -1,12 +1,10 @@
 .. _Past_Projects:
 
-Archive
-########
+Past Projects
+##############
 
 An overview of the significant contributions made to BeagleBoard.org through 
 GSoC over the previous years is given in the section that follows. 
-These initiatives cover a variety of topics, such as software optimizations 
-and firmware upgrades.
 
 .. toctree:: 
     :maxdepth: 2
@@ -22,4 +20,4 @@ and firmware upgrades.
     2015
     2014
     2013
-    2010
\ No newline at end of file
+    2010
diff --git a/proposals/index.rst b/proposals/index.rst
new file mode 100644
index 0000000000000000000000000000000000000000..3cb1745c20c985ab05113f2593b1c76fd1825e33
--- /dev/null
+++ b/proposals/index.rst
@@ -0,0 +1,11 @@
+.. _proposals:
+
+Proposals
+#########
+
+
+
+.. toctree:: 
+    :hidden:
+
+    template
\ No newline at end of file
diff --git a/proposals/template.rst b/proposals/template.rst
new file mode 100644
index 0000000000000000000000000000000000000000..66184dbc884fef46916be160876c22c86548b98c
--- /dev/null
+++ b/proposals/template.rst
@@ -0,0 +1,217 @@
+.. _proposal_template:
+
+Proposal template 
+#################
+
+Introduction
+*************
+
+Summary links
+=============
+
+- **Student:** ``@ayush1325``
+- **Mentors:** ``@jkridner``, ``@vaishnav``
+- **Code:** `Google Summer of Code / greybus / cc1352-firmware · GitLab <https://openbeagle.org/gsoc/greybus/cc1352-firmware>`_
+- **Documentation:** `Ayush Singh / docs.beagleboard.io · GitLab <https://openbeagle.org/ayush1325/docs.beagleboard.io>`_
+- **GSoC:** `Google Summer of Code <https://summerofcode.withgoogle.com/archive/2023/projects/iTfGBkDk>`_ 
+
+Status
+=======
+
+This project is currently just a proposal.
+
+Proposal
+========
+
+Please complete the requirements listed on the `GSoc Ideas <https://forum.beagleboard.org/t/gsoc-ideas/35850/1>`_ 
+and fill out this template.
+
+About 
+=====
+
+- **Forum:** ``@ayush1325``
+- **OpenBeagle:** `Ayush Singh · GitLab <https://openbeagle.org/ayush1325>`_
+- **IRC:**
+- **Github:** `jadonk (Jason Kridner) · GitHub <https://github.com/jadonk>`_
+- **School:** Greatest University
+- **Country:** Worldistan
+- **Primary language:** Igpay Atinlay
+- **Typical work hours:** 8AM-5PM US Eastern
+- **Previous GSoC participation:** 
+
+Project
+********
+
+**Project name:** About my super cool project.
+
+Description
+============
+
+In 10-20 sentences, what are you making, for whom, why and with what technologies 
+(programming languages, etc.)? (We are looking for open source SOFTWARE submissions.)
+
+Software
+=========
+
+Which software or technology stack are you going to use to complete this project.
+
+Hardware
+========
+
+A list of hardware that you are going to use for this project.
+
+Timeline
+********
+
+Provide a development timeline with 10 milestones, one for each week of development without 
+an evaluation, and any pre-work. (A realistic, measurable timeline is critical to our selection process.)
+
+.. note:: This timeline is based on the `official GSoC timeline <https://developers.google.com/open-source/gsoc/timeline>`_
+
+
+Timeline summary
+=================
+
+.. table:: 
+
+    +------------------------+----------------------------------------------------------------------------------------------------+
+    | Date                   | Activity                                                                                           |                                  
+    +========================+====================================================================================================+
+    | February 26            | Connect with possible mentors and request review on first draft                                    |
+    +------------------------+----------------------------------------------------------------------------------------------------+
+    | March 4                | Complete prerequisites, verify value to community and request review on second draft               |
+    +------------------------+----------------------------------------------------------------------------------------------------+
+    | March 11               | Finalized timeline and request review on final draft                                               |
+    +------------------------+----------------------------------------------------------------------------------------------------+
+    | March 21               | Submit application                                                                                 |
+    +------------------------+----------------------------------------------------------------------------------------------------+
+    | May 1                  | Start bonding                                                                                      |
+    +------------------------+----------------------------------------------------------------------------------------------------+
+    | May 27                 | Start coding and introductory video                                                                |
+    +------------------------+----------------------------------------------------------------------------------------------------+
+    | June 3                 | Release introductory video and complete milestone #1                                               |
+    +------------------------+----------------------------------------------------------------------------------------------------+
+    | June 10                | Complete milestone #2                                                                              |
+    +------------------------+----------------------------------------------------------------------------------------------------+
+    | June 17                | Complete milestone #3                                                                              |
+    +------------------------+----------------------------------------------------------------------------------------------------+
+    | June 24                | Complete milestone #4                                                                              |
+    +------------------------+----------------------------------------------------------------------------------------------------+
+    | July 1                 | Complete milestone #5                                                                              |
+    +------------------------+----------------------------------------------------------------------------------------------------+
+    | July 8                 | Submit midterm evaluations                                                                         |
+    +------------------------+----------------------------------------------------------------------------------------------------+
+    | July 15                | Complete milestone #6                                                                              |
+    +------------------------+----------------------------------------------------------------------------------------------------+
+    | July 22                | Complete milestone #7                                                                              |
+    +------------------------+----------------------------------------------------------------------------------------------------+
+    | July 29                | Complete milestone #8                                                                              |
+    +------------------------+----------------------------------------------------------------------------------------------------+
+    | August 5               | Complete milestone #9                                                                              |
+    +------------------------+----------------------------------------------------------------------------------------------------+
+    | August 12              | Complete milestone #10                                                                             |
+    +------------------------+----------------------------------------------------------------------------------------------------+
+    | August 19              | Submit final project video, submit final work to GSoC site and complete final mentor evaluation    |
+    +------------------------+----------------------------------------------------------------------------------------------------+
+
+Timeline detailed
+=================
+
+Community Bonding Period (May 1st - May 26th)
+==============================================
+
+GSoC contributors get to know mentors, read documentation, get up to speed to begin working on their projects
+
+Coding begins (May 27th)
+=========================
+
+Milestone #1, Introductory YouTube video (June 3rd)
+===================================================
+
+Milestone #2 (June 10th)
+==========================
+
+Milestone #3 (June 17th)
+=========================
+
+Milestone #4 (June 24th)
+==========================
+
+Milestone #5 (July 1st)
+========================
+
+Submit midterm evaluations (July 8th)
+=====================================
+
+.. important:: 
+    
+    **July 12 - 18:00 UTC:** Midterm evaluation deadline (standard coding period) 
+
+Milestone #6 (July 15th)
+=========================
+
+Milestone #7 (July 22nd)
+=========================
+
+Milestone #8 (July 29th)
+=========================
+
+Milestone #9 (Aug 5th)
+=======================
+
+Milestone #10 (Aug 12th)
+========================
+
+Final YouTube video (Aug 19th)
+===============================
+
+Submit final project video, submit final work to GSoC site 
+and complete final mentor evaluation
+
+Final Submission (Aug 24nd)
+============================
+
+.. important::
+
+    **August 19 - 26 - 18:00 UTC:** Final week: GSoC contributors submit their final work 
+    product and their final mentor evaluation (standard coding period)
+
+    **August 26 - September 2 - 18:00 UTC:** Mentors submit final GSoC contributor 
+    evaluations (standard coding period)
+
+Initial results (September 3)
+=============================
+
+.. important:: 
+    **September 3 - November 4:** GSoC contributors with extended timelines continue coding
+
+    **November 4 - 18:00 UTC:** Final date for all GSoC contributors to submit their final work product and final evaluation
+
+    **November 11 - 18:00 UTC:** Final date for mentors to submit evaluations for GSoC contributor projects with extended deadline
+
+Experience and approch
+***********************
+
+In 5-15 sentences, convince us you will be able to successfully complete your project in the timeline you have described.
+
+Contingency
+===========
+
+What will you do if you get stuck on your project and your mentor isn’t around?
+
+Benefit
+========
+
+If successfully completed, what will its impact be on the `BeagleBoard.org <http://beagleboard.org/>`_ community? Include quotes from `BeagleBoard.org <http://beagleboard.org/>` 
+community members who can be found on `Discord <https://discord.com/invite/e58xECGWfR>`_ and `BeagleBoard.org forum <https://forum.beagleboard.org/c/gsoc/13>`_.
+
+Misc
+====
+
+Please complete the requirements listed in the `General Requirements <https://forum.beagleboard.org/t/gsoc-ideas/35850#general-requirements-5>`_. 
+Provide link to merge request.
+
+Suggestions
+===========
+
+Is there anything else we should have asked you?
\ No newline at end of file