FunctionalHacker/hugo-toha
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Cleaned up notes and added images

Browse source
This commit is contained in:
Sharwin Patil 2025-01-05 20:22:23 -08:00
parent 5deb935997
commit fc16c0345d
19 changed files with 41 additions and 682 deletions
Download patch file Download diff file Expand all files Collapse all files

BIN
assets/images/bike_dealer.jpg Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 3.6 MiB

BIN
assets/images/chess.jpg Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 184 KiB

BIN
assets/images/kavar.jpg Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 137 KiB

BIN
assets/images/pure-pursuit.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 7.5 KiB

4
config.yaml
View file

@ -130,10 +130,6 @@ params:
title: "Project Posts"
enable: true
showAuthor: true
# Share post on different social media
# shareButtons:
# linkedin: true
# email: true
analytics:
enabled: false
services:

54
content/notes/search.bn.md
View file

@ -1,54 +0,0 @@
---
title: "অনুসন্ধানের ফলাফল"
date: 2010-06-08T08:06:25+06:00
weight: 999999
sitemap:
priority : 0.1
layout: "search"
url: search
---
This file exists solely to respond to /search URL with the related `search` layout template.
No content shown here is rendered, all content is based in the template layouts/page/search.html
Setting a very low sitemap priority will tell search engines this is not important content.
This implementation uses Fusejs and mark.js
## Initial setup
Search depends on additional output content type of JSON in config.toml
\```
[outputs]
home = ["HTML", "JSON"]
\```
## Searching additional fields
To search additional fields defined in front matter, you must add it in 2 places.
### Edit layouts/_default/index.JSON
This exposes the values in /index.json
i.e. add `category`
\```
...
"contents":{{ .Content | plainify | jsonify }}
{{ if .Params.tags }},
"tags":{{ .Params.tags | jsonify }}{{end}},
"categories" : {{ .Params.categories | jsonify }},
...
\```
### Edit fuse.js options to Search
`assets/scripts/pages/search.js`
\```
keys: [
"title",
"contents",
"tags",
"categories"
]
\```

54
content/notes/search.cn.md
View file

@ -1,54 +0,0 @@
---
title: "Search Results"
date: 2010-06-08T08:06:25+06:00
weight: 999999
sitemap:
priority : 0.1
layout: "search"
url: search
---
This file exists solely to respond to /search URL with the related `search` layout template.
No content shown here is rendered, all content is based in the template layouts/page/search.html
Setting a very low sitemap priority will tell search engines this is not important content.
This implementation uses Fusejs and mark.js
## Initial setup
Search depends on additional output content type of JSON in config.toml
\```
[outputs]
home = ["HTML", "JSON"]
\```
## Searching additional fields
To search additional fields defined in front matter, you must add it in 2 places.
### Edit layouts/_default/index.JSON
This exposes the values in /index.json
i.e. add `category`
\```
...
"contents":{{ .Content | plainify | jsonify }}
{{ if .Params.tags }},
"tags":{{ .Params.tags | jsonify }}{{end}},
"categories" : {{ .Params.categories | jsonify }},
...
\```
### Edit fuse.js options to Search
`assets/scripts/pages/search.js`
\```
keys: [
"title",
"contents",
"tags",
"categories"
]
\```

54
content/notes/search.de.md
View file

@ -1,54 +0,0 @@
---
title: "Search Results"
date: 2010-06-08T08:06:25+06:00
weight: 999999
sitemap:
priority : 0.1
layout: "search"
url: search
---
This file exists solely to respond to /search URL with the related `search` layout template.
No content shown here is rendered, all content is based in the template layouts/page/search.html
Setting a very low sitemap priority will tell search engines this is not important content.
This implementation uses Fusejs and mark.js
## Initial setup
Search depends on additional output content type of JSON in config.toml
\```
[outputs]
home = ["HTML", "JSON"]
\```
## Searching additional fields
To search additional fields defined in front matter, you must add it in 2 places.
### Edit layouts/_default/index.JSON
This exposes the values in /index.json
i.e. add `category`
\```
...
"contents":{{ .Content | plainify | jsonify }}
{{ if .Params.tags }},
"tags":{{ .Params.tags | jsonify }}{{end}},
"categories" : {{ .Params.categories | jsonify }},
...
\```
### Edit fuse.js options to Search
`assets/scripts/pages/search.js`
\```
keys: [
"title",
"contents",
"tags",
"categories"
]
\```

54
content/notes/search.es.md
View file

@ -1,54 +0,0 @@
---
title: "Resultados de Búsqueda"
date: 2010-06-08T08:06:25+06:00
weight: 999999
sitemap:
priority : 0.1
layout: "search"
url: search
---
Este archivo existe únicamente para responder a la URL /search con la plantilla de diseño `search` relacionada.
No se muestra ningún contenido aquí, todo el contenido se basa en la plantilla layouts/page/search.html
Establecer una prioridad muy baja en el mapa del sitio le dirá a los motores de búsqueda que éste no es un contenido importante.
Esta implementación utiliza Fusejs, jquery y mark.js
## Configuración inicial
La búsqueda depende del tipo de contenido de salida adicional de JSON en config.toml
\```
[outputs]
home = ["HTML", "JSON"]
\```
## Búsqueda de archivos adicionales
Para buscar campos adicionales definidos en el front matter, debes añadirlo en 2 lugares.
### Editar layouts/_default/index.JSON
Esto expone los valores en /index.json: por ejemplo, para agregar `categories`
\```
...
"contents":{{ .Content | plainify | jsonify }}
{{ if .Params.tags }},
"tags":{{ .Params.tags | jsonify }}{{end}},
"categories" : {{ .Params.categories | jsonify }},
...
\```
### Editar las opciones de fuse.js para buscar
`assets/scripts/pages/search.js`
\```
keys: [
"title",
"contents",
"tags",
"categories"
]
\```

54
content/notes/search.fr.md
View file

@ -1,54 +0,0 @@
---
title: "Search Results"
date: 2010-06-08T08:06:25+06:00
weight: 999999
sitemap:
priority : 0.1
layout: "search"
url: search
---
This file exists solely to respond to /search URL with the related `search` layout template.
No content shown here is rendered, all content is based in the template layouts/page/search.html
Setting a very low sitemap priority will tell search engines this is not important content.
This implementation uses Fusejs and mark.js
## Initial setup
Search depends on additional output content type of JSON in config.toml
\```
[outputs]
home = ["HTML", "JSON"]
\```
## Searching additional fields
To search additional fields defined in front matter, you must add it in 2 places.
### Edit layouts/_default/index.JSON
This exposes the values in /index.json
i.e. add `category`
\```
...
"contents":{{ .Content | plainify | jsonify }}
{{ if .Params.tags }},
"tags":{{ .Params.tags | jsonify }}{{end}},
"categories" : {{ .Params.categories | jsonify }},
...
\```
### Edit fuse.js options to Search
`assets/scripts/pages/search.js`
\```
keys: [
"title",
"contents",
"tags",
"categories"
]
\```

54
content/notes/search.hi.md
View file

@ -1,54 +0,0 @@
---
title: "Search Results"
date: 2010-06-08T08:06:25+06:00
weight: 999999
sitemap:
priority : 0.1
layout: "search"
url: search
---
This file exists solely to respond to /search URL with the related `search` layout template.
No content shown here is rendered, all content is based in the template layouts/page/search.html
Setting a very low sitemap priority will tell search engines this is not important content.
This implementation uses Fusejs and mark.js
## Initial setup
Search depends on additional output content type of JSON in config.toml
\```
[outputs]
home = ["HTML", "JSON"]
\```
## Searching additional fields
To search additional fields defined in front matter, you must add it in 2 places.
### Edit layouts/_default/index.JSON
This exposes the values in /index.json
i.e. add `category`
\```
...
"contents":{{ .Content | plainify | jsonify }}
{{ if .Params.tags }},
"tags":{{ .Params.tags | jsonify }}{{end}},
"categories" : {{ .Params.categories | jsonify }},
...
\```
### Edit fuse.js options to Search
`assets/scripts/pages/search.js`
\```
keys: [
"title",
"contents",
"tags",
"categories"
]
\```

54
content/notes/search.id.md
View file

@ -1,54 +0,0 @@
---
title: "Search Results"
date: 2010-06-08T08:06:25+06:00
weight: 999999
sitemap:
priority : 0.1
layout: "search"
url: search
---
This file exists solely to respond to /search URL with the related `search` layout template.
No content shown here is rendered, all content is based in the template layouts/page/search.html
Setting a very low sitemap priority will tell search engines this is not important content.
This implementation uses Fusejs and mark.js
## Initial setup
Search depends on additional output content type of JSON in config.toml
\```
[outputs]
home = ["HTML", "JSON"]
\```
## Searching additional fields
To search additional fields defined in front matter, you must add it in 2 places.
### Edit layouts/_default/index.JSON
This exposes the values in /index.json
i.e. add `category`
\```
...
"contents":{{ .Content | plainify | jsonify }}
{{ if .Params.tags }},
"tags":{{ .Params.tags | jsonify }}{{end}},
"categories" : {{ .Params.categories | jsonify }},
...
\```
### Edit fuse.js options to Search
`assets/scripts/pages/search.js`
\```
keys: [
"title",
"contents",
"tags",
"categories"
]
\```

54
content/notes/search.it.md
View file

@ -1,54 +0,0 @@
---
title: "Search Results"
date: 2010-06-08T08:06:25+06:00
weight: 999999
sitemap:
priority : 0.1
layout: "search"
url: search
---
This file exists solely to respond to /search URL with the related `search` layout template.
No content shown here is rendered, all content is based in the template layouts/page/search.html
Setting a very low sitemap priority will tell search engines this is not important content.
This implementation uses Fusejs and mark.js
## Initial setup
Search depends on additional output content type of JSON in config.toml
\```
[outputs]
home = ["HTML", "JSON"]
\```
## Searching additional fields
To search additional fields defined in front matter, you must add it in 2 places.
### Edit layouts/_default/index.JSON
This exposes the values in /index.json
i.e. add `category`
\```
...
"contents":{{ .Content | plainify | jsonify }}
{{ if .Params.tags }},
"tags":{{ .Params.tags | jsonify }}{{end}},
"categories" : {{ .Params.categories | jsonify }},
...
\```
### Edit fuse.js options to Search
`assets/scripts/pages/search.js`
\```
keys: [
"title",
"contents",
"tags",
"categories"
]
\```

54
content/notes/search.jp.md
View file

@ -1,54 +0,0 @@
---
title: "Search Results"
date: 2010-06-08T08:06:25+06:00
weight: 999999
sitemap:
priority : 0.1
layout: "search"
url: search
---
This file exists solely to respond to /search URL with the related `search` layout template.
No content shown here is rendered, all content is based in the template layouts/page/search.html
Setting a very low sitemap priority will tell search engines this is not important content.
This implementation uses Fusejs and mark.js
## Initial setup
Search depends on additional output content type of JSON in config.toml
\```
[outputs]
home = ["HTML", "JSON"]
\```
## Searching additional fields
To search additional fields defined in front matter, you must add it in 2 places.
### Edit layouts/_default/index.JSON
This exposes the values in /index.json
i.e. add `category`
\```
...
"contents":{{ .Content | plainify | jsonify }}
{{ if .Params.tags }},
"tags":{{ .Params.tags | jsonify }}{{end}},
"categories" : {{ .Params.categories | jsonify }},
...
\```
### Edit fuse.js options to Search
`assets/scripts/pages/search.js`
\```
keys: [
"title",
"contents",
"tags",
"categories"
]
\```

54
content/notes/search.ko.md
View file

@ -1,54 +0,0 @@
---
title: "Search Results"
date: 2010-06-08T08:06:25+06:00
weight: 999999
sitemap:
priority : 0.1
layout: "search"
url: search
---
This file exists solely to respond to /search URL with the related `search` layout template.
No content shown here is rendered, all content is based in the template layouts/page/search.html
Setting a very low sitemap priority will tell search engines this is not important content.
This implementation uses Fusejs and mark.js
## Initial setup
Search depends on additional output content type of JSON in config.toml
\```
[outputs]
home = ["HTML", "JSON"]
\```
## Searching additional fields
To search additional fields defined in front matter, you must add it in 2 places.
### Edit layouts/_default/index.JSON
This exposes the values in /index.json
i.e. add `category`
\```
...
"contents":{{ .Content | plainify | jsonify }}
{{ if .Params.tags }},
"tags":{{ .Params.tags | jsonify }}{{end}},
"categories" : {{ .Params.categories | jsonify }},
...
\```
### Edit fuse.js options to Search
`assets/scripts/pages/search.js`
\```
keys: [
"title",
"contents",
"tags",
"categories"
]
\```

54
content/notes/search.ru.md
View file

@ -1,54 +0,0 @@
---
title: "Search Results"
date: 2010-06-08T08:06:25+06:00
weight: 999999
sitemap:
priority : 0.1
layout: "search"
url: search
---
This file exists solely to respond to /search URL with the related `search` layout template.
No content shown here is rendered, all content is based in the template layouts/page/search.html
Setting a very low sitemap priority will tell search engines this is not important content.
This implementation uses Fusejs and mark.js
## Initial setup
Search depends on additional output content type of JSON in config.toml
\```
[outputs]
home = ["HTML", "JSON"]
\```
## Searching additional fields
To search additional fields defined in front matter, you must add it in 2 places.
### Edit layouts/_default/index.JSON
This exposes the values in /index.json
i.e. add `category`
\```
...
"contents":{{ .Content | plainify | jsonify }}
{{ if .Params.tags }},
"tags":{{ .Params.tags | jsonify }}{{end}},
"categories" : {{ .Params.categories | jsonify }},
...
\```
### Edit fuse.js options to Search
`assets/scripts/pages/search.js`
\```
keys: [
"title",
"contents",
"tags",
"categories"
]
\```

54
content/notes/search.vn.md
View file

@ -1,54 +0,0 @@
---
title: "Search Results"
date: 2010-06-08T08:06:25+06:00
weight: 999999
sitemap:
priority : 0.1
layout: "search"
url: search
---
This file exists solely to respond to /search URL with the related `search` layout template.
No content shown here is rendered, all content is based in the template layouts/page/search.html
Setting a very low sitemap priority will tell search engines this is not important content.
This implementation uses Fusejs and mark.js
## Initial setup
Search depends on additional output content type of JSON in config.toml
\```
[outputs]
home = ["HTML", "JSON"]
\```
## Searching additional fields
To search additional fields defined in front matter, you must add it in 2 places.
### Edit layouts/_default/index.JSON
This exposes the values in /index.json
i.e. add `category`
\```
...
"contents":{{ .Content | plainify | jsonify }}
{{ if .Params.tags }},
"tags":{{ .Params.tags | jsonify }}{{end}},
"categories" : {{ .Params.categories | jsonify }},
...
\```
### Edit fuse.js options to Search
`assets/scripts/pages/search.js`
\```
keys: [
"title",
"contents",
"tags",
"categories"
]
\```

60
data/en/sections/projects.yaml
View file

@ -39,6 +39,7 @@ projects:
tags: ["Python", "ROS", "Robotics", "Franka Robot Arm"]
- name: Automated Poker Table
image: /images/bike_dealer.jpg
role: "ECE 2023 Capstone"
timeline: "Jan 2023 - May 2034"
url: "/posts/automated-poker-table/"
@ -46,15 +47,26 @@ projects:
summary: An robotic system that faciliates a game of poker with automated shuffling, dealing, and game management.
tags: ["Arduino", "Python", "Raspberry Pi", "I2C"]
- name: Napkin.ai Code Assistant
role: "Hack@Brown 2024 Project"
timeline: "Feb 2024"
url: "/posts/napkin-ai/"
repo: "https://github.com/Sharwin24/HackAtBrown"
summary: A fast, lightweight graph retrieval-augmented generation tool for navigating codebases.
tags: ["Python", "PyTorch", "Retrieval-Augmented Generation", "Knowledge Graphs", "Language Models"]
- name: Chess Robot
role: "NEU Robotics Club Project"
image: /images/chess.jpg
timeline: "Sept 2021 - Dec 2021"
url: "/posts/chess-robot/"
repo: "https://github.com/Connor205/Chess-Robot-NURobotics"
summary: A gantry robot with a camera that plays chess against a human opponent.
tags: ["Python", "OpenCV", "Arduino", "Stepper Motors"]
- name: Robot Arm Educational Kit
image: /images/kavar_background.jpg
role: "Personal Project"
timeline: "May 2022 - May 2024"
url: "/posts/robot-arm-edu/"
repo: https://github.com/Shawin24/
summary: A 3D-printed robot arm kit for educational purposes.
tags: ["3D Printing", "Arduino"]
- name: AGV Odometry & Motion Planning
image: /images/pure-pursuit.png
role: "VEXU Team HSKY"
timeline: "Sept 2022 - Dec 2022"
url: "/posts/agv-hsky/"
@ -62,6 +74,14 @@ projects:
summary: Implemented Odometry from scratch in C++ for spline motions
tags: ["C++", "Multi-threading", "Spline Interpolation"]
- name: SLAM Simulation
role: "ME495: Embedded Systems Homework"
timeline: "Nov 2024 - Dec 2024"
url: "/posts/slam-simulation/"
repo: https://github.com/ME495-EmbeddedSystems/homework-4-Sharwin24
summary: A simulation of a robot navigating an environment using SLAM with frontier exploration.
tags: ["Python", "ROS", "Gazebo", "Nav2"]
- name: Autonomous Drone Swarm Simulation
role: "RoboTech 2022 Hackathon Project"
timeline: "April 2022"
@ -70,26 +90,18 @@ projects:
summary: A simulation of a swarm of drones using ROS and Gazebo
tags: ["Python", "RRT", "A*"]
- name: Chess Robot
role: "NEU Robotics Club Project"
timeline: "Sept 2021 - Dec 2021"
url: "/posts/chess-robot/"
repo: "https://github.com/Connor205/Chess-Robot-NURobotics"
summary: A gantry robot with a camera that plays chess against a human opponent.
tags: ["Python", "OpenCV", "Arduino", "Stepper Motors"]
- name: Robot Arm Educational Kit
role: "Personal Project"
timeline: "May 2022 - May 2024"
url: "/posts/robot-arm-edu/"
repo: https://github.com/Shawin24/
summary: A 3D-printed robot arm kit for educational purposes.
tags: ["3D Printing", "Arduino"]
- name: Robot Pen Thief
role: "Personal Project"
timeline: "Sept 2024"
url: "/posts/pen-thief/"
repo: https://github.com/Sharwin24/Pen-Challenge
summary: Combining a PincherX 100 robot arm with an Intel Realsense to identify and grab pens.
tags: ["Python", "ROS", "Intel Realsense"]
tags: ["Python", "ROS", "Intel Realsense"]
- name: Napkin.ai Code Assistant
role: "Hack@Brown 2024 Project"
timeline: "Feb 2024"
url: "/posts/napkin-ai/"
repo: "https://github.com/Sharwin24/HackAtBrown"
summary: A fast, lightweight graph retrieval-augmented generation tool for navigating codebases.
tags: ["Python", "PyTorch", "Retrieval-Augmented Generation", "Knowledge Graphs", "Language Models"]

11
data/en/site.yaml
View file

@ -13,12 +13,11 @@ description: Sharwin Patil's Portfolio and project showcases.
# they will be separated by a divider from the main menus.
customMenus:
- name: Resume
url: static/files/main.pdf
# url: https://toha-guides.netlify.app/posts/
# # specify whether to hide the menu item from top navbar or not.
# hideFromNavbar: false
# # specify whether to show the menu item in footer or not.
# # if you set it to true, make sure you have set `footer.navigation.customMenus: true` in your config.yaml
url: post/files/main.pdf
showOnFooter: true
- name: GitHub
url: https://github.com/Sharwin24
showOnFooter: true
# Specify OpenGraph Headers