) => {
return (
-
+
{project.tools.map((tool, i) => {
const toolData = allTools.find(t => t.id === tool)
if (!toolData) {
@@ -29,7 +29,7 @@ export const ProjectTools = ({
}
return
})}
-
+
)
}
@@ -59,49 +59,38 @@ export const ProjectCard = ({
i,
}: CardProps) => {
const col1 = (
-
-
+
+
{project.name}
-
+ {project.image && (
+
+ )}
)
const col2 = (
-
+
{project.description}
Tools
- Design Features
+ Design Features
)
return (
-
+
- {i % 2 === 0 ? (
- <>
- {col1}
- {col2}
-
- ) : (
- <>
- {col2}
- {col1}
-
- )}
+ {col1}
+ {col2}
diff --git a/src/components/portfolio/tag-badge.tsx b/src/components/portfolio/tag-badge.tsx
new file mode 100644
index 0000000..2f2ae7b
--- /dev/null
+++ b/src/components/portfolio/tag-badge.tsx
@@ -0,0 +1,16 @@
+import React from "react"
+import { Badge } from "react-bootstrap"
+import { ITag } from "../../data/blog/type"
+
+export const TagBadge: React.FC<{ tag: ITag }> = ({ tag }) => (
+
+ {tag.name}
+
+)
diff --git a/src/components/seo.js b/src/components/seo.js
index a268915..5a3fd71 100644
--- a/src/components/seo.js
+++ b/src/components/seo.js
@@ -1,16 +1,9 @@
-/**
- * SEO component that queries for data with
- * Gatsby's useStaticQuery React hook
- *
- * See: https://www.gatsbyjs.org/docs/use-static-query/
- */
-
import React from "react"
import PropTypes from "prop-types"
import { Helmet } from "react-helmet"
import { useStaticQuery, graphql } from "gatsby"
-function SEO({ description, lang, meta, title }) {
+function SEO({ description, lang, meta, title, image, path }) {
const { site } = useStaticQuery(
graphql`
query {
@@ -19,20 +12,26 @@ function SEO({ description, lang, meta, title }) {
title
description
author
+ twitter
+ image
+ url
}
}
}
`
)
+ const metaTitle = title || `Home`
const metaDescription = description || site.siteMetadata.description
+ const metaUrl = `${site.siteMetadata.url}${path}`
+ const metaImage = `${site.siteMetadata.url}${
+ image || site.siteMetadata.image
+ }`
return (
diff --git a/src/data/blog/articles/freshman.md b/src/data/blog/articles/freshman.md
new file mode 100644
index 0000000..7ba0d5b
--- /dev/null
+++ b/src/data/blog/articles/freshman.md
@@ -0,0 +1,89 @@
+---
+id: freshman
+title: "Year in Review - Freshman"
+date: "05-23-2019"
+tags: [honors, year_in_review]
+---
+
+_Man, what a year!_
+
+This was the exact reaction I had when I saw the email from my
+amazing Honors Advisor reminding me to write the year in
+review. My second reaction was _"This has been such a crazy year, can I even fit it into a few hundred words?"_
+. Regardless of the answer, I am going to try.
+
+Which is pretty much how the last year (and a few months
+before it) has been. I see an opportunity, I ask myself, _"Dev this is crazy, are you sure you want to do this?"_
+. Then I go for it. The biggest of them all was my decision to
+spend thousands of dollars and travel thousands of miles away
+from my family, friends and girlfriend, for college education.
+Was it crazy? I am not even answering that question. Did it
+pay off? Definetely!
+
+The year started out with a lot of excitement as I was looking
+forward to my life in a new country filled with strange people
+and awesome opportunities. Strangely though, I did not feel
+any anxiety or fear of living alone like I was told by others
+who have went through the same thing. That is, until I was on
+the plane headed for Cincy. I was completely fine, watching
+Young Sheldon and listening to my staple death metal songs,
+until my neighbour pulled up the map on the screen in front of
+us that displayed the current location of the flight. At that
+time, we were just crossing the Atlantic into east coast.
+Looking at that hit me with a wave of anxiety like I had never
+experienced before. That image somehow made the whole
+experience real and scary, and all I could think about was
+waking up in a completely strange town with no idea of what to
+do or who to talk to. I'm still not sure when or how I
+shrugged off that feeling. All I know that it came, made its
+mark, left, and never came back.
+
+Continuing on the theme of crazy things that happened, the
+craziest thing you can do to an introvert is to trap them in a
+room with a complete stranger. I had spent most of my time
+alone, so having a roommate was a new experience, one that I
+was not looking forward to. But lucky for me, my roommate
+seemed to respect my introverted nature, so we established a
+mutually beneficial no-talk business-only relationship. Making
+friends was never my strong suite, but I tried. Tried and
+failed. Just like I had been doing for the last 7 years. I did
+make a couple good friends eventually, and somehow I got
+better at creating and managing my social life. I have a few
+special people to thank for that.
+
+My academic and professional life were way better than I
+expected. I did not imagine that I would see so many
+opportunities that I would have to think twice before starting
+something new. So many organizations to get involved in, so
+many projects to chime in, so many assignments to complete, so
+many people to meet. It was crazy (no surprise there), and I
+did not know where to start. Again, took my some time, but
+eventually I found my way around the campus life. I got an
+interesting job, became a core member of a student
+organization, made nice connections and got to travel a bit.
+University Honors helped quite a bit. From the Gateway to
+Honors class to my first Honors experience, I learnt a lot of
+life skills that I have now incorporated into my everyday
+routine.
+
+So what now? I have been asking myself that question for
+several days now, so it's probably time I give it some serious
+thought. Now that the crazy part is out of the way
+(hopefully), it's time to flourish. Flourish my academic life
+by aiming for a higher GPA (not completely satisfied with my
+last 3.6), and flourish my professional life by making
+expanding my skillset, connections and opportunities. Student
+clubs are a great way to make connections, so getting involved
+in some is definitely in my todo-list. I also need to connect
+with some seniors and faculty members. The School of IT is an
+awesome and student-friendly community, and I plan to make the
+most of it.
+
+Probably the most important thing to do is to stay open and
+flexible. The future is unpredictable, and the more you plan,
+the more it goes against you. So the hope is that nothing goes
+wrong and my mission to flourish is achieved. But if I am
+flexible enough, I can make those wrong things work in my
+favor. This is another skill I have yet to pick up.
+
+_Hoping for one more crazy year!_
diff --git a/src/data/blog/articles/gcsp.md b/src/data/blog/articles/gcsp.md
new file mode 100644
index 0000000..7c86d0c
--- /dev/null
+++ b/src/data/blog/articles/gcsp.md
@@ -0,0 +1,98 @@
+---
+id: gcsp
+title: "Global Citizen Scholar Plan"
+date: "12-14-2018"
+tags: [honors]
+---
+
+
+
+ I am driven by my beliefs in passion, competency, and knowledge. I pursue these passions by utilizing my core strengths of analysis, exploration, and deliberative planning. I plan to live out these values through opportunities where I am researching and building to achieve excellence and reflection that impacts communities and technology. To do so, I will seek opportunities to use technology in new ways and change our perception of the world. When I face challenges or obstacles along the way, I will remember to stay flexible and maintain a hopeful outlook.
+
+
+
+ - My Global Citizen Scholar Mission
+
+
+
Sample Paragraph
` in a React component, React doesn't actually create a paragraph element in your HTML. It just created a dummy object that will be later converted into a `` HTML element by it's accompanying library `react-dom`. If you ever wondered why you had to install `react-dom` from npm along with `npm`, this is why. React doesn't interact with the browser DOM on it's own. Which just happens to be the criteria to being isomorphic.
+
+This means that React can be used in Nodejs to describe HTTP endpoints, generate PDF and DOCX files, and much more! However, the most common use of React on the server is server-rendered apps.
+
+## Rendering on the server
+
+After a huge shift from rendering HTML traditionally with PHP to client-rendered apps with React and Angular, we realized that there might be some performance and SEO costs of downloading hundreds of KBs of Javascript code before showing anything on the screen. So we went back to rendering on the server, but still using our new favorite language and framework. And thus frameworks like [Nextjs](https://nextjs.org/) and [Gatsby](https://www.gatsbyjs.com/) were born.
+
+These frameworks abstract the concepts of client and server when writing React components. So we can write components that use data from the server without having to fetch it through an HTTP api, and show that data using HTML elements. Weird, right? After a few years of writing client-rendered apps, Nextjs felt a little like magic to me, very similar to Meteor's sorcery.
+
+## But what if I don't like React?
+
+Tough luck.
+
+Just kidding.
+
+While React pioneered the virtual DOM, it is far from the only library that uses this concept. Most new frontend frameworks that came after React like [Vue](https://vuejs.org/) also make use of virtual DOM, and thus can be rendered on the server using [Nuxt](https://nuxtjs.org/). [Angular](https://angular.io/) does not use a virtual DOM, but uses an entirely different beast called [ahead-of-time compilation](https://angular.io/guide/aot-compiler), that also allows Angular code to be run on the server ([Angular Universal](https://angular.io/guide/universal) is it's server rendering framework).
+
+## But what if I don't like Javascript?
+
+Tough luck.
+
+Well, only kinda kidding this time.
+
+Since the advent of [Webassembly](https://webassembly.org/), it is possible to write code in languages other than Javascript that can run on the browser. Microsoft's [Blazor](https://dotnet.microsoft.com/en-us/apps/aspnet/web-apps/blazor) and Apache's [UNO](https://platform.uno/) are some of the most popular frameworks that makes use of webassembly to run C# code in the browser, which means you can use much of your C# code on both the client and server side. [PyScript](https://pyscript.net/) is a very new framework that runs python in the browser. And there's also a dinosaur called [Google Web Toolkit](https://www.gwtproject.org/) that allows creating browser applications in Java (Can you imagine Java in the browser? In 2022?).
+
+While these approaches exist, the most preferred way to build client applications is still through Javascript. And as long as that is true, we will keep finding ways to make the same code run everywhere. While the term "Isomorphic Javascript" has lost a little bit of it's buzzword status, it is a powerful technique that is still implemented in the most popular frameworks and applications.
diff --git a/src/data/blog/articles/junior.md b/src/data/blog/articles/junior.md
new file mode 100644
index 0000000..36ab80e
--- /dev/null
+++ b/src/data/blog/articles/junior.md
@@ -0,0 +1,113 @@
+---
+id: junior
+title: "Year in Review - Junior"
+date: "06-11-2022"
+tags: [honors, year_in_review]
+---
+
+_"Are you sure you can do this?"_
+
+Every couple months, something came up in my life when I had to ask myself this question.
+Sometimes every other day. Sometimes multiple times a day. Why? I thought the year of crazy was over!
+
+The theme I had set for this year in my last review was "grow".
+I wanted to spend the year looking at opportunities to grow and expand, whatever form that would take.
+
+The funny thing is, when you look for something vague like that, you will find the weirdest results.
+The things that you want will come packaged with the things you don't want, but you will need.
+If you accept the packaged deal, you will be thankful.
+If not, you'll soon end up looking for the same deal.
+
+Every time I was presented an opportunity like this,
+I found saying to myself _"This is a lot of work. Are you sure you can do this? You're not even good at this!"_.
+
+### I dub thee the new leader
+
+The year started off with not one, but **two** areas of my life where I had to be the unwilling leader.
+Remember the new high-profile project that I was assigned to?
+Well, soon more people would be assigned to the same project,
+and I would be given some leadership responsibilities.
+I didn't want to be in that position, but I got to work on an awesome new project,
+which I definitely wanted.
+Starting out it was just one other person, on the team over the summer, so it wasn't too bad,
+and it gave me an opportunity to experiment and test my leadership capabilities.
+
+But then in August, another person was added to the team, essentially doubling my concerns.
+Now I had to work even harder to make sure the team is motivated and productive.
+I don't think I did a great job being a leader and a team player there, even though I was a great programmer.
+
+### Students, Associate!
+
+The other interesting and eventful area of my life was the **IT Student Association** (ITSA). My fasciation
+of student tech orgs and events is not hidden from anyone. I have been involved with ACM@UC for a while now,
+and there are a lot of things that I wanted to do but didn't get the opportunity to do so
+with ACM@UC. I also had some outsider feelings at ACM since it's almost entirely comprised of
+EECS students. I wanted an org like this but with IT students.
+
+ITSA had existed for years, but they had been inactive for a couple years due to the old exec graduating, and COVID preventing
+events. There was no one with enough motivation to pick up the org and host some activities.
+
+Except me.
+
+After having spent a considerable time in organizations and events, I felt confident that I could revive this org.
+I also wanted to take this opportunity to grow my network among the students, faculty, and industry,
+and host fun and educational events.
+
+But obviously, I couldn't have done it alone. Running an organization also meant leading an organizations,
+which I was not good at. I still took the jump and held an election to get more executive members,
+and then selected some people to be committee chairs. But I could not follow through on a lot
+of things, especially sharing my passion and enthusiasm for hosting events and creating
+a community.
+
+I will go into more detail on my time as the President of ITSA in my upcoming Honors Experience Showcase.
+
+### Hack so others can hack
+
+Speaking of organizations and events, I also love organizing larger events, especially hackathons.
+Since 2020, we have been doing 2 hackathons every year **RevolutionUC** and **MakeUC**, each hosted by different organizations.
+However, because of my interest in organizing, and the application I have built to help
+hackathon organizers, I have been a part of every hackathon. Last year, I led the web team
+of RevolutionUC.
+
+This year, I got the same opportunity for MakeUC, which I refused, because last
+time it didn't go as well as I wanted it to (check out my RevolutionUC Honors Experience Showcase).
+So I instead volunteered as a regular volunteer instead of a lead, while still having a somewhat
+of a technical leadership role (since I was the most experienced).
+
+In hindsight, I am not sure if rejecting that role was a good choice, because the hackathon ended
+up being pretty fun, and it was a good opportunity for me to re-test my leadership skills. Although
+the person who ended up leading the team did great, and I am not sure if I had the time to
+make that commitment. This is one of the opportunities that I now kinda regret not taking.
+
+Something that did make me feel better about my leadership skills though is watching
+someone be a terrible leader and basically create a hostile environment and not understand
+how authority works. It gave me the feeling that while I might not be a great leader,
+at least I don't have the capability of being such a terrible leader.
+
+### The beginning of the spider web
+
+While being a leader in ITSA was not the best experience, getting to host a variety of
+educational activities brought some of the best fruits I can imagine. I was able to network with a lot
+of great people, both in the industry and the faculty at UC. The ITSA executives (and by extension me)
+have been recognized as the leaders and representatives of the entire IT student body
+on multiple occasions, giving us the opportunity to work with people I never thought I would.
+On top of that, ITSA allowed me to attend a very high-profile tech conference and meet a lot more
+people who are deep in the industry that I want to get into, and I have built connections that
+will undoubtedly help me in the long term.
+
+### On the next episode...
+
+As I start a new year, my goals for the near future have become more clear and approachable.
+Now that I have started building my network, I can't progress much further with it until I have something
+to show people why they should look at me. So I have started working on this portfolio website a lot more.
+I have already added 2 new sections, Projects Showcase, and Blog. I want to turn this into an actual
+portfolio of my skills and my work by showcasing what I've done over the years, and writing about
+things that will capture attention and show how much I actually know about things. While I am
+pretty confident that I am ahead of my peers in this field, I also need to show some tangible
+evidence to support this claim, and this is the best way to do so. I have also started working on video
+content that I can put up on YouTube or TikTok and expand my reach even further.
+
+So it seems pretty clear to me that the goal for this year is _craft_. Craft a personal brand that
+is catchy, unique, and represent who I am, craft my skill set to be something that I am proud of,
+craft applications and technology that helps the community, and craft my network using all of these things
+and expand my reach even further.
diff --git a/src/data/blog/articles/pitch.md b/src/data/blog/articles/pitch.md
new file mode 100644
index 0000000..8f17e87
--- /dev/null
+++ b/src/data/blog/articles/pitch.md
@@ -0,0 +1,59 @@
+---
+id: pitch
+title: "Reflection: Problem Pitch"
+date: "12-10-2018"
+tags: [honors]
+---
+
+In the beginning of October 2018, I chose the topic
+**Cure for diseases (Cancer, aids, etc)** for
+working on as a first step towards becoming a “Global Citizen
+Scholar”. To be honest, I did not have a lot of prior
+knowledge on interest in this field. I chose it because it was
+the topic that I was “most comfortable” with. But about a
+month later, I was glad that I made this decision.
+
+I was working with two other students on this problem, I saw
+them taking this with so much interest and sincerity, it made
+me wonder “Why? How?”. Both of my partners had a lot of
+knowledge, experience and contacts that they could put to use
+for working on this problem. I know that because I have been
+there. I have always taken up projects in fields of my
+interest. This was probably the first time I had moved so far
+from my comfort zone.
+
+Then it hit me. We are not born as a “Global Citizen Scholar”.
+To be one,you need to grow and develop. You need to step
+outside your comfort zone and find new ways to help yourself
+and the people around you. So I did. I started doing my
+homework. I started looking into new developments in the field
+of medicine and pharmacy. I also discussed potential interview
+candidates with my partners. We had a brief and informative
+talk with James Hester, a Roche Diagnostics sales
+representative for Northern Indiana. The interview gave me new
+insight into the whole process of medicine research, testing,
+marketing and utilization. James gave us interesting knowledge
+into the making and working of a cancer treatment, and how the
+presence of a specific gene mutation can affect not only the
+severity of the disease, but also decides whether the
+treatment will work or not. He also told us about how the
+pharmaceutical industry could change in the near future with
+the advent of new technologies, which will help us better
+understand the biology of these diseases.
+
+Unfortunately, this is an area where getting involved is not
+easy, as it requires a significant amount of knowledge and
+experience to make a significant contribution. Or, atleast
+that’s what I thought. James told us that getting involved in
+this area is a lot easier than I think, because researchers
+are constantly looking for interested students to hire as
+interns and assistants, and they make a significant
+contribution in moving the project forward.
+
+This whole experience taught me why the Honors program wants
+us to be “Global Citizen Scholars”, and what that exactly
+means. It is not only about helping others, but also about
+self-development (and that’s the part that appeals to me the
+most because, you know, I’m selfish ;P). I know that there
+will be challenges in this new mission, and I am ready to face
+them.
diff --git a/src/data/blog/articles/pre-junior.md b/src/data/blog/articles/pre-junior.md
new file mode 100644
index 0000000..1fe553e
--- /dev/null
+++ b/src/data/blog/articles/pre-junior.md
@@ -0,0 +1,123 @@
+---
+id: pre-junior
+title: "Year in Review - Pre-Junior"
+date: "05-05-2021"
+tags: [honors, year_in_review]
+---
+
+_Well, that worked out great!_
+
+This was a year of pleasant surprises for me. Things that I
+initially thought could be bad for me, turned out better than
+expected.
+
+I know this might sound weird.
+_“Isn’t 2020 supposed to be one of the worst years of our lifetime?”_
+, you might ask.
+
+Like most questions, the answer to this one is
+_“It depends”_. Depends on your situation, and your
+ability to take advantage of certain circumstances.
+
+I am in no way denying that 2020 was a bad year. So many lives
+were lost, so many families destroyed, so many jobless people
+struggling to survive, so many people with mental health
+issues. COVID hit India much worse, so I definitely have no
+shortage of examples. Overall, this year sucked, and it will
+take a hot minute for us to recover from it.
+
+But for me personally, it was a good year. Maybe even the best
+of my life so far. Starting right in March 2020, the pandemic
+forced most non-essential workplaces to work remotely, right
+around the time I was fantasizing about how great it would be
+for me to be able to sit and home and earn money. I was kind
+of used to working from home back in my freelance days, so it
+didn’t take me too long to adjust. In fact, it was a nice
+productivity boost for me.
+
+My roommate moved out early in May, and I had to live alone
+for the rest of the year. While I was in the search for
+roommates, I came to enjoy living alone, and I decided that I
+will not actively search for roommates. Especially after me
+and my last roommate parted on bad terms. We were great
+friends, but soon I realized that he was toxic person, and I
+didn’t want anything pulling down my productivity.
+
+Just like any other Indian parent, mine started to call me
+back home for some reason. I didn’t want to go back because I
+had a job here and I couldn’t work overseas, but I was
+starting to miss my family and my girlfriend a little too
+much. So, I decided to go back to India for the rest of the
+year. I did have to give up my job for the semester, which I
+wasn’t particularly fond of. But once I got home, I realized
+that it was a good thing that I wasn’t allowed to work
+overseas, because I wouldn’t have gotten enough time to do so
+anyways. Instead, I spent my time with family, friends, and
+girlfriend. I also started a side-project, which I am really
+passionate about, and it’s a nice way for me to work on my
+skills and showcase them to potential employers.
+
+An emotional journey started for me when I went back. While I
+absolutely loved my girlfriend, the long-distance relationship
+was taking its toll on me. I just couldn’t see a way for me to
+stay sane for however many years we will have to stay on
+opposite sides of the planet. So, in early December, I broke
+up with her. I had been mentally preparing myself for this for
+a couple months, so it did not hit me emotionally as bad as I
+thought. However, she was hit with an emotional truck. She had
+a few very bad days, then some more bad days. We stopped
+talking after a while, and I came back to the US. I might not
+be completely over her yet, just because she was such a great
+person and I really enjoyed being with her. It’s depressing to
+know that life can throw such huge obstacles at you and you
+can never get through without sacrificing something of
+importance. You will have to make a really difficult decision,
+and then you will spend a lot of time wondering if you made
+the right one.
+
+But another pleasant surprise for me was a new relationship
+that started in late February. A couple years ago, I met this
+great girl who is almost as ambitious as me, with a lot more
+energy and compassion that I can ever hope to achieve. We both
+came back to the states in January, and we started dating in
+late February. Coming out of a 2+ years long distance
+relationship, it is a nice change of pace to be able to
+experience a normal relationship, one where we can actually
+get to share a part of our lives with each other.
+
+As soon as I came back in January, I got to continue working
+at my last company, but on a different project. From the
+beginning, I was told that this new project is a very
+high-profile project, and will involve quite a bit of
+politics, strict deadlines, high expectation, and quality
+work. If they were trying to make me nervous and anxious,
+mission accomplished. But after spending a few weeks on it, I
+got a good handle of everything, and it turns out that there
+is vast potential in this project.
+
+Looking back at last year’s review, I set a goal of “work”.
+And I believe that I worked hard to take good advantage of my
+circumstances, and really propel myself in my personal and
+professional life. Of course, the work is never going to end.
+But I did gain quite a bit of momentum this year, thanks to
+all the “flourishing” I was able to do.
+
+For me, the next logical step here would probably be to
+expand. Use the momentum I have built up to expand my reach,
+work, skills, connections, and personality. It might seem like
+a synonym to “flourish”, which was the theme of 2019, but in
+my mind, the two have really different meanings. “Flourish”
+was a phase where we transition from something very small and
+awkward to something elegant and beautiful, like a seed
+turning into a plant. Expansion is when the plant grows into a
+tree, expanding its roots and branches into the environment,
+and making its presence dominant and significant. As a wise
+man once said,
+
+
+
+_We only get one life. Might as well use it to put a dent on the universe._
+
+
+
+_Cheers, and keep up the good work!_
diff --git a/src/data/blog/articles/senior.md b/src/data/blog/articles/senior.md
new file mode 100644
index 0000000..8fd6efc
--- /dev/null
+++ b/src/data/blog/articles/senior.md
@@ -0,0 +1,101 @@
+---
+id: senior
+title: "Year in Review - Senior"
+date: "07-23-2023"
+tags: [year_in_review]
+featured: 1
+---
+
+*“I had everything, then I had nothing.”*
+
+In the past year, I found myself uttering this overly dramatic sentence to describe areas of my life to myself and close friends.
+
+Obviously, I didn’t actually lose ***everything***. Broadly speaking, my life has certainly leveled up quite a bit since I wrote the last year-in-review. I have a
+new job
+as a Developer Advocate in a rapidly growing startup, I am
+making content
+about things I enjoy, I am
+traveling to conferences
+and meeting
+people that I look up
+to and enjoy chatting with, and I’m earning a decent enough paycheck to keep my mom and debt happy. I even
+graduated college
+and acquired work authorization in the US! Objectively speaking, I have more things now that I did 2 years ago.
+
+**Then why do I feel like I have lost more than I have gained?**
+
+### Craft, Crack, Crash
+
+In the last year-in-review, I decided the theme of the upcoming year to be *Craft*. I wanted to spend some time carefully crafting my brand, my content, my skills, and my network.
+
+Where did I get this idea from? Why did I decide the theme to be “craft” and not something else?
+
+I can sit here and say that for the last 4 years I have been reflecting on how my year went and logically deciding what the next step should be to come up with the theme for the upcoming year. That would be a lie. Maybe there is a subconscious part of my brain that actually is doing that calculation and helping me decide the theme, I wouldn’t be surprised if that were the case.
+
+But I mostly feel like I look into a crystal ball to see what the upcoming year might be like, what I expect myself to be doing, and pick a theme based on that.
+
+It seems like last year when I looked into the crystal ball, things were foggy and unclear, and all I saw out of it was an engraving with three letters - *cra...*, and then I made up the rest and decided on *craft*.
+
+I wish there was a way to rewind the clock back a year so that I can take a better look at what the crystal ball was trying to tell me. Was it actually trying to show me the things I have *crafted*? Was it an indicator of the *cracks* forming in my life? Or was it a warning that things are going to *crash*?
+
+What if it was all three?
+
+### The Cracks
+
+The cracks in my life had already started to show when I started writing the last year-in-review. I had low energy and motivation, missed the first couple deadlines, then hastily wrote it past due date and sent an apologetic letter to my amazing advisor Ashley for not finishing the year in review early enough. I wasn’t very happy with what I had written, but I published it anyways because I couldn’t be bothered with it. I was tired.
+
+I took some time recently to read back all my year-in-reviews, and apparently I did a pretty good job of structuring and formulating my thoughts last year, even while lacking the energy and motivation to do so. However, the cracks in my life subtly reveal themselves in this review if you know what to look for.
+
+I had started to grow unhappy. Unhappy with my academics, with my job, with my relationship, and with my living conditions. This was causing more frustration and exhaustion than I would have cared to admit at that time. Needless to say, the feeling of “my life is perfect” that I had a couple years ago was almost gone - I just hadn’t noticed it yet.
+
+I made attempts at fixing stuff - I tried to move out of my apartment and live at a new place with new people. I started applying to new jobs, and even asked my employer at that time to accommodate my requests. I tried fixing my relationship and make more room to enjoy each others’ company instead of getting annoyed by each others’ presence. All of my attempts failed, and led to the inevitable crash.
+
+### The Crash
+
+In December, I decided to take the winter holidays to travel back to India and go on a vacation with my family. I had a great time - got to reconnect with my family and some old friends, met my brother’s newborn for the first time and realized that babies are kinda cute, and took some amazing photos enjoying snow on the top of the mighty Himalayas. For the most part I was just enjoying the moment of break from my usual life, and I wasn’t spending too much time thinking about the fact that I had just resigned from my job and broke up with my girlfriend.
+
+Financially I was in a decent enough position that not having a job for a few months would not be a big deal - I was pretty confident that I would have a job by the time I graduated college. However, any idea I had of experiencing “the perfect life” crashed and crumbled, as the two biggest pillars that it stood on couldn’t bear the cracks that had formed over the year.
+
+While I came back from that vacation in January with a fresh motivation to start crafting again, the crash caught up with me very quickly. I was feeling unmotivated, wasting most of my time doomscrolling and looking for those little dopamine hits, procrastinating and missing basically every single deadline. I had never felt this low and unmotivated in my life. Even my last breakup in 2020, which I expected to have serious consequences on my mental health, did not come close to what I was going through a few months ago, and still am at the time of writing this.
+
+For the longest time, I was unwilling to accept that something was wrong and needed to be fixed. I kept chugging along, making promises that I couldn’t keep, setting expectations I couldn’t meet, and pretending to do things I wasn’t actually doing.
+
+Finally, a couple weeks ago, I decided to stop everything else and ask some serious questions about what had happened to me. I spent an entire night trying to remember and note down every significant event from the last 5 years, and how one event led to another, in an attempt to pinpoint the source of the cracks and the crash. Weirdly, the conclusion was both satisfying and unsatisfying at the same time.
+
+### It was... inevitable?
+
+Free will is an illusion. We are just a collection of terribly-designed bio-electrical machines capable of remembering and communicating ideas. Actions and decisions are purely based on past events and experiences instead of some internal choice making process that many people believe we possess and label as “free will”.
+
+Subscribing to this deterministic ideology comes with some nice perks - the entire reason I am able to reconstruct the past and track my mental state through time is because that’s how I believe the world works. It gives me insight into why people do the things they do, and leverage that information for everyone’s benefit. This is why I study psychology - it reveals how determinism manifests within people, similar to how physics reveals the determinism of objects. It’s also a great sympathy building tool - at no point can I ever really blame someone for what they did, because I am fully aware that there are deterministic reasons that led to it. We can only learn from what has already happened and hope that we are better prepared for the next time.
+
+But determinism is a double edged sword - it’s not that difficult to slip into nihilism from here. Do we have any control over our lives at all? If I am simply a cog in the grand cosmic machine, can I do something that I wouldn’t already be doing? Do I have the power to hold things together when fate is hell-bent on pulling them apart?
+
+Maybe I was afraid of asking myself these questions, which is why I couldn’t accept that something was wrong and needed to be fixed. Maybe I was afraid of coming to the realization that there is nothing to pinpoint - it was one small thing after another that slowly caused those cracks, things that were natural, organic, and inevitable. My experience of “the perfect life” was never going to be permanent, instead it was a naïve portrayal of one short phase of my life when I felt very happy and satisfied with everything, a phase that would slowly slip away without me noticing, and I would just be left watching it happen and experiencing the consequences.
+
+The general frustration with life and feelings of burnout seemed to form a feedback loop - I started to grow a little unhappy about things, which led to loss of energy and rise in frustration, which impacted my ability to cope with them and led to making more mistakes, which lead to even more unhappiness, and eventually to the inevitable crash. After the dust had settled, all I was left with were ashes, which I continued to carry around for months, without ever fully healing from the burnout.
+
+### The Craft
+
+So far I have painted a pretty bleak picture of my life over the last year. And it certainly was at times. This is why I am very surprised at how much of my initial promise of *crafting* I was still able to keep up.
+
+Content creation has been an absolute boon for me. I had zero expectations of ever getting even slightly famous or recognized in the industry. I had zero expectations of unlocking opportunities I didn’t know existed. I just wanted to look at a camera and rant about microservices for a bit. But as I dove into the world of content creation, I started to see more and more opportunities, and I tried to grab as many of them as I could. This is a legitimate industry now and I am excited to see how far I can push myself and what kind of content I can craft.
+
+My venture into content creation led me to discover Developer Relations - an industry closely tied to content creation but with very specific goals. I decided to pursue a career in DevRel as an opportunity to see what I can learn about this fascinating new industry. This means that my career as a Software Developer has been put on hold and moved to the back burner for the time being. I am unsure if this was the best decision, and there are times when I wish that I still had my old job, or some other job that allowed me to explore the complexities and intricacies of developing software systems at scale. But, that will have to wait. I first need to explore this new position that I have crafted for myself.
+
+I never thought of myself as someone who is excited to meet and talk to people. But throughout the year the benefits of professional networking and making industry connections have presented themselves to me like an angel visiting me in my dreams and granting my wishes. Soon enough, I found myself enjoying communities and industry events and random meetups. I also realized that to take the best advantage of these opportunities, I am in serious need of a mindset shift. I cannot be my usual shy and introverted self anymore - I have to actually learn how to make myself more approachable, more trustworthy, and most of all, a good and fun person to be around. I started crafting something that I always thought was immutable - my personality.
+
+I have also taken my love for organizing events to the next level - by helping organize a pretty large tech conference, along with volunteering at others, and helping out with local meetups. I am starting to recognize the special role of these events in our industry, and I want to help craft events that have a meaningful long term impact on everyone.
+
+### Recover
+
+I don't think this time I need to look into a crystal ball to figure out what I need to be doing. It's pretty obvious - *recover*. Recover from the crash, fill in the cracks with something stronger than whatever was holding it together before, and get back to a state of mind where I am free to craft whatever I want to without burning myself out. A lot of people are counting on me, and rooting for me, and I am not letting them down again. I need to get my act together push forward.
+
+But recovering is not enough - it's not like I was in a great state even 2 years ago. Yes I was happy, but there were still things that I was doing wrong, things that led to the cracks in the first place. I hope I am able to identify these issues and do my best to ensure they don't ruin my life ever again. As a wise man once said,
+
+
+
+_Sometimes the best you can do is to help yourself._
+
+
+
+_Cheers, and take care!_
diff --git a/src/data/blog/articles/serverless.md b/src/data/blog/articles/serverless.md
new file mode 100644
index 0000000..fa98d47
--- /dev/null
+++ b/src/data/blog/articles/serverless.md
@@ -0,0 +1,119 @@
+---
+id: serverless
+title: "Serverless Deployment"
+date: "06-16-2022"
+featured: 2
+image: images/serverless.png
+tags: [technology, software_development]
+---
+
+Image sourced from Hexaware
+
+This infamous depiction of serverless has been circulating around for years now. According to this image, Serverless Functions, also called "Functions as a Service", is way to write an application with a focus on business logic and not worrying about infrastructure or runtime.
+
+## I'm new to serverless, how does this work?
+
+Well if you're written traditional web apis before, it might look something like this -
+
+```ts
+// index.ts
+import express from "express"
+import Cat from "./models/cat"
+
+const app = express()
+
+app.get(`/`, async (req, res) => {
+ const cats = await Cat.findAll()
+ res.json({ cats })
+})
+
+app.listen(process.env.PORT)
+```
+
+To have a similar application on a serverless platform like AWS Lambda, your code would look like this -
+
+```ts
+// handler.ts
+import Cat from "./models/cat"
+
+export const getCats = async (event) => {
+ const cats = await Cat.findAll()
+ return { data: { cats } }
+})
+
+```
+
+Instead of express (or any other web framework) registering this function as an API handler, Lambda registers it as a handler function, which can configured to be triggered by a variety of events/conditions (including http requests).
+
+```yml
+# serverless.yml
+functions:
+ get-cats:
+ handler: handler.getCats
+ events:
+ - http:
+ path: /
+ method: get
+```
+
+
+ Serverless Framework Configuration
+
+
+This can now be deployed to Lambda using the AWS CLI (or something vendor-agnostic like the serverless framework). Based on the configuration file, when a trigger event happens, a new container will spin up and execute this function.
+
+You just wrote some code and deployed it without thinking about any infrastructure or runtime!
+
+## Execution On Demand
+
+When you deploy traditional apps, you (or your trusty Continuous Delivery service) will spin up a container, start your application process inside the container, establish a network connection, and send an alert to your slack channel. This application will now wait for network requests and react to them as told. All this while, it's consuming memory and processing power, even when it does not receive any requests.
+
+
+
+In comparison, when you deploy a serverless function, a service like Lambda will only bill you for the time your function is actually running, which only happens when it's triggered. When there is a trigger event, Lambda will find the corresponding function for that trigger, then either spin up a new container and load the function in it (cold start) or find an existing container that has the function already loaded in memory (hot start), and execute the function. The container will then either stay on and wait for more requests, or die out.
+
+
+
+So you can start to notice some differences here. If you receive 1 request every second, you will only have 1 running function every second. However, if you get a thousand requests at the same time, Lambda will run a thousand containers with the function. So this approach is extremely elastic. You will use and pay for only the exact resources that you use. If you have multiple functions, each function is deployed as a separate Lambda, so you also will only be using the resources required to run that one function.
+
+## So it's always cheaper?
+
+Not really.
+
+For a base unit of computation (like an hour of server usage), you will pay more to the serverless service than you would for a virtual server.
+
+
+
+ AWS Lambda costs around
$0.06 for a full hour of execution with 1 GB of memory (calculated per ms of use).
+ AWS EC2 can cost between
$0.008 to
$0.01 per hour for an instance with 1 GB of memory.
+
+ Sources:
+ EC2 Pricing,
+ Lambda Pricing
+
+
+
+
+
+
+If you have some consistent patterns in usage, and you don't mind having to manage containers or servers, serverless is probably not going to be feasible for you.
+
+
+
+
+
+## How do I start then?
+
+Well, hold your horses.
+
+There is one other case where you can't simply deploy to serverless. If your application is currently in a state of spaghetti, serverless will cause more pain than harm.
+
+Since your functions are loaded and executed separate from each other, you can apply a lot of the principles of Microservices here. The functions should be small, independent, and fulfil a single responsibility. I have another post coming up on Microservices, that's where I'll talk more about the purpose and strategy behind Microservices.
+
+Serverless seems (for now) to be the pinnacle of what cloud technology is hoping to achieve - allowing us, the developers, to write code that serves business functions with minimal management of the infrastructure that the code will run on.
diff --git a/src/data/blog/articles/sophomore.md b/src/data/blog/articles/sophomore.md
new file mode 100644
index 0000000..930e892
--- /dev/null
+++ b/src/data/blog/articles/sophomore.md
@@ -0,0 +1,115 @@
+---
+id: sophomore
+title: "Year in Review - Sophomore"
+date: "06-02-2020"
+tags: [honors, year_in_review]
+---
+
+_Here we go... let's see what I can do!_
+
+As I finished writing my last year in review, this is what I
+told myself. In the last year in review I talked about how
+crazy the year had been for me, and how I was going to use
+this year to flourish. Looking back, I think I succeded!
+
+The year started out by immediately pulling me into new
+situations. I was chosen as the Conferences and Education
+Chair for the ACM@UC organization, which not only meant that I
+get to see how a proper organization works, but also that I
+will be given responsibilities, and I'll have to work with
+some new people. Being much more of a "I work alone" person,
+this was a new experience, one that I was not really looking
+forward to, but I'm glad I did it. Being a part of a student
+organization taught me some much-needed social and management
+skills. I also got an opportunity to work with some of the
+best people in the organization to organize the monster of an
+event called RevolutionUC. I loved being a part of this
+organization, so I applied to be an executive member for the
+year 2020-21. And they much have liked having me around,
+because I got elected as the Webmaster! I think this is the
+perfect position for me, because I get to use me skills as a
+software developer to contribute to the organization.
+
+The second situation I got thrown into was a bit more
+unexpected. It was a gradual change over the course of a few
+months, but I never realized how deep I got into it and how
+much it had affected me, or will affect me. There are a couple
+people in India who work as UC Ambassadors for all the newly
+admitted Indian international students. Every year, they make
+a group on Whatsapp with every person who has received an
+admission offer from UC, and they also add some current
+students who want to guide the incoming students and answer
+any queries related to academics, campus life and such. I was
+one of the students who were added. I spent a lot of time on
+that group answering the hundreds of queries thrown to us,
+mostly because I remember being in that position myself, and
+how scary and confusing the whole experience is. What I did
+not see coming was the transition from the FAQ bank to a
+mentor. I did not want this change, but it happened, and
+suddenly there were people looking up to me. So I tried my
+best to play the role of a coach. It's not like I have the
+life experience to be an effective mentor, but I believe I had
+enough for that time. And it worked. I got a couple new
+friends out of it, and I got to learn a lot about how to be a
+good mentor. It also helps that I was taking the Introduction
+to Interpersonal Communication class at that time.
+
+An experience that was not so positive was my research
+assistant job. We had some new people joining us for the ride,
+and one of them was supposed to work with me on the I was
+working on. For the first couple months, we worked pretty hard
+on it, got a paper written and submitted to an ACM conference,
+and it got accepted! That was a great motivating factor for
+us, so we decided to write papers for more research venues. We
+used to work long nights and weekends, because it felt like we
+were onto something, and we had a great time doing it. But
+some incidents made me once again realize the reason why I
+always preferred working alone. There are always some people
+who will push you down when you think they will pull you up,
+even if it's unintentional. I still don't fully understand the
+possible reasoning behind that. Maybe he wasn't committed to
+the work as much as I was (or as much as I wanted him to be),
+or maybe he was in over his head. Either way, the work we did
+in the last couple months of 2019 was far from satisfactory,
+but I learned a lot throughout the whole experience.
+
+Things changed a lot when I started my co-op in January. I was
+able to go back to my element of the software development
+world. This is a world that is vast and ever-changing, and
+even though I like to think that my breadth of knowledge is
+pretty big, I know that it's only at the surface. My co-op,
+enabled me to freely explore this exciting world and basically
+explode my skillset in a matter of months. I also got to learn
+a lot from my co-workers, while getting the opportunity to be
+the teacher for some others.
+
+So at the end of another crazy year, as I write this essay, I
+am thinking back to what I wanted the theme of this year to
+be. Looking back, I wanted to take advantage of as many
+opportunities as I can, and use them to flourish. But going
+into the year, I was not really sure how to. It took me some
+time to get into the flow of my new life living off-campus on
+my own, cooking my own food, figuring out how to travel
+everyday, and managing the load of work. Figuring all this out
+was the first step in the flourishing process. The next was
+learning how to work with people that come in my life in the
+form of peers, co-workers, teachers and mentees. The final,
+and in my opinion, the most important step, was to figure out
+exactly where to go from here.
+
+Don't get me wrong; "flourish" is not the same as "grow". I
+still have a lot to learn, and a lot to do. This year was a
+transition from a crazy and confusing chapter to a much more
+streamlined and structured chapter in the story. But to make
+sure the following chapters don't get off-track, I have to put
+in the work that's needed. So that's the theme I'm choosing
+for the next year - **work**. As a wise man once
+said,
+
+
+
+_Your dreams won't work unless you do._
+
+
+
+_Cheers, and stay safe out there!_
diff --git a/src/data/blog/tags/data.yaml b/src/data/blog/tags/data.yaml
new file mode 100644
index 0000000..3b2b848
--- /dev/null
+++ b/src/data/blog/tags/data.yaml
@@ -0,0 +1,20 @@
+tags:
+ - id: year_in_review
+ name: Year In Review
+ color: "white"
+ bgColor: "#007acc"
+
+ - id: honors
+ name: University Honors Program
+ color: "black"
+ bgColor: "#bae1ff"
+
+ - id: technology
+ name: Technology
+ color: "white"
+ bgColor: "#a4c439"
+
+ - id: software_development
+ name: Software Development
+ color: "white"
+ bgColor: "#b8011c"
diff --git a/src/data/blog/type.d.ts b/src/data/blog/type.d.ts
new file mode 100644
index 0000000..aff1796
--- /dev/null
+++ b/src/data/blog/type.d.ts
@@ -0,0 +1,21 @@
+import { ImageDataLike } from "gatsby-plugin-image"
+
+export interface IArticle {
+ frontmatter: {
+ id: string
+ title: string
+ date: string
+ image: ImageDataLike & { absolutePath: string }
+ tags: string[]
+ }
+ timeToRead: number
+ excerpt: string
+ html: string
+}
+
+export interface ITag {
+ id: string
+ name: string
+ color: string
+ bgColor: string
+}
diff --git a/src/data/showcase/experiences/data.yaml b/src/data/showcase/experiences/data.yaml
new file mode 100644
index 0000000..6fe169b
--- /dev/null
+++ b/src/data/showcase/experiences/data.yaml
@@ -0,0 +1,38 @@
+experiences:
+ - id: itsa
+ name: Student Organization Leadership
+ description: Lead one of the largest tech orgs on campus
+ date: January 2022
+ image: ./itsa/logo.png
+ pageImage: ./itsa/banner.png
+ page: ./itsa/article.md
+
+ - id: roundtable
+ name: Student Leader Round Table
+ description: The student leader illuminati
+ date: January 2022
+ image: ./roundtable/logo.png
+ page: ./roundtable/article.md
+
+ - id: mentorship
+ name: Welcome Experience Mentorship
+ description: Mentoring the next generation of university honors
+ date: August 2021
+ image: ./mentorship/logo.png
+ page: ./mentorship/article.md
+
+ - id: revolutionuc
+ name: RevolutionUC Organizing
+ description: A hackathon hosted at the University of Cincinnati
+ date: February 2021
+ image: ./revuc/logo.png
+ pageImage: ./revuc/banner.jpeg
+ page: ./revuc/article.md
+
+ - id: leadershape
+ name: LeaderShape Institute
+ description: Blooming leaders of tomorrow
+ date: January 2019
+ image: ./leadershape/logo.png
+ pageImage: ./leadershape/banner.jpg
+ page: ./leadershape/article.md
diff --git a/src/data/showcase/experiences/itsa/article.md b/src/data/showcase/experiences/itsa/article.md
new file mode 100644
index 0000000..156a5d8
--- /dev/null
+++ b/src/data/showcase/experiences/itsa/article.md
@@ -0,0 +1,13 @@
+Having experienced a touch of organizational leadership and hosting events through ACM@UC and RevolutionUC, I decided to increase the challenge and really test my abilities as an organization leader. I was also interested in fostering a student community similar to what I had experience in the computer science space but in the information technology space.
+
+And ITSA was the perfect opportunity for this. Not only was ITSA the primary student organization in the IT community, it was also almost dead and anyone who was interested in sustaining ITSA had already graduated. This meant I got to use an existing recognized brand name but still start from scratch in terms of ideas and activities.
+
+My vision for the ITSA was simply this - _The go-to club for tech enthusiasts at UC_. This meant hosting events that are educational and provide networking opportunities, exposing students to the industry, and fostering a community where people with mutual interests can share ideas and form groups.
+
+For the Fall 2021 semester, we did events almost every week on wednesdays, which ranged from simple ice-breakers and get-to-knows to workshops on programming and web development, to informational sessions on research or data analysis from professionals. We collaborated with the Civic Tech Research Lab to host a session on research projects and methodologies, and invited speakers from companies like SmartData, Brooksource, and Skilled Inc. to share their professional wisdom. We also hosted an exam review session and study group before the final exams week to help students get a better handle on the course material.
+
+For the Spring semester, we decided to slow down the pace and host events every other month. We toured the CyrusOne data center, and the IT Solutions Center, to help students learn about industry teams and operations. We also sponsored students to attend the Momentum Developer Conference and React Miami Conference, both of which were huge learning and networking opportunities for the students.
+
+We were also recognized as the primary community of IT students by multiple university departments, and our executives as representatives of the IT student body as a whole. We were contacted by the School of IT and the Cincinnati Innovation District to help organize networking events that would be most useful to the students. We were also contacted by ELCE to provide feedback to changes to the EEP program from the perspective of a student. We also met with recruiters and company executives to help them meet more students to hire through sponsored events.
+
+This experience was a gold mine of personal and professional development for me. Each event involved a lot of marketing and logistics work, coordinating with speakers, members, and other organizers, and coming up with ideas or content. I also met a lot of good people in the industry who are going to be a great help to my professional life. This has been a great experience in leadership and community building for me.
diff --git a/src/data/showcase/experiences/itsa/banner.png b/src/data/showcase/experiences/itsa/banner.png
new file mode 100644
index 0000000..b532334
Binary files /dev/null and b/src/data/showcase/experiences/itsa/banner.png differ
diff --git a/src/data/showcase/experiences/itsa/logo.png b/src/data/showcase/experiences/itsa/logo.png
new file mode 100644
index 0000000..486a0b1
Binary files /dev/null and b/src/data/showcase/experiences/itsa/logo.png differ
diff --git a/src/data/showcase/experiences/leadershape/article.md b/src/data/showcase/experiences/leadershape/article.md
new file mode 100644
index 0000000..cf492b2
--- /dev/null
+++ b/src/data/showcase/experiences/leadershape/article.md
@@ -0,0 +1,12 @@
+One of the five competencies of the University Honors Program is Leadership. Leadership is the ability to influence and inspire a group of people and turning the group into a single unit which amplifies everyone's strengths and minimized weaknesses. A major mission on my way to become a Global Citizen Scholar and achieve my dream is to become an effective leader. And that is precisely what Leadershape Institute, a 6-day workshop/retreat, is meant for - to show us the path to becoming effective leaders.
+
+The approach taken by Leadershape to make us understand the building blocks of a leader was interesting and effective. They take a brief definition of what constitutes a leader, break it apart into pieces, and expand each piece over the course of an entire day so that we have a complete picture. Each day brought insight into a new dimension of life, forcing us to think about things in ways we never thought existed. The key takeaway was as simple as putting all the pieces gained throughout the course of the week together (which is much easier said than done).
+
+Perhaps the most interesting day for me was the day we were talking about the term "Vision". One of the most compelling attributes of a good leader is ambition, and only a person with an ambition mission can become a good leader. A Vision to realize, a mission to complete, these are great motivators. They drive a person and their actions like nothing else can. A leader needs to be driven towards a goal, only then can he inspire others to follow him on his campaign.
+I found this particularly interesting because I have always considered myself to be a very ambitious person. I often think about where I could be 5-10 years in the future, and those scenarios are sometimes not very realistic. But on this day, we had to think about a specific personal vision that we always have wanted to see realized. So unlike the other occasions when I used to dream about my future, this one had to be a little more realistic, specific and organized, so that I can easily convey it. This was followed by an activity, which made us write a news article that would be published when our vision would be realized, and the news article would describe the achievement. [Here is the article I wrote](/images/experiences/leadershape/leadershape-article.jpeg).
+
+Aside from the main objective, one important aspect of the whole experience was getting to know more like-minded people and talking about ideas, thoughts and feelings. On the very first day, we were told that to truly develop self, we need to stretch out of our comfort zone and try out new things, until those new things become our comfort zone. For me, this is exactly what happened throughout the week.
+
+Being a socially anxious person, the level of social exposure was something I have only experienced once in a similar workshop 4 years ago, and I was not very happy with my attempts at socializing. So going into Leadershape was a little tough for me. But in Leadershape, we were divided into what we called "Family clusters", which was a group of 6 or 7 students and a faculty member. And I am very grateful that everyone in my family cluster accepted me for who I am, helped me throughout the week in stretching myself out of my comfort zone, and allowed me to help them similarly.
+
+But that was not the limit of social interaction I was exposed to. We had multiple pair and group discussion sessions, often with random people, and we enjoyed many games and activities, all of which really broke the ice between us. Perhaps the most enjoyable aspect of the entire week was the late-night games that we students played. Those late nights forced me to get out of my fortress of solitude and connect with like-minded people on various levels. I am looking forward to seeing how these new relationships I have forged carry out of the workshop and develop into something greater.
diff --git a/src/images/leadershape1.jpg b/src/data/showcase/experiences/leadershape/banner.jpg
similarity index 100%
rename from src/images/leadershape1.jpg
rename to src/data/showcase/experiences/leadershape/banner.jpg
diff --git a/src/images/leadershape.png b/src/data/showcase/experiences/leadershape/logo.png
similarity index 100%
rename from src/images/leadershape.png
rename to src/data/showcase/experiences/leadershape/logo.png
diff --git a/src/data/showcase/experiences/mentorship/article.md b/src/data/showcase/experiences/mentorship/article.md
new file mode 100644
index 0000000..854fb40
--- /dev/null
+++ b/src/data/showcase/experiences/mentorship/article.md
@@ -0,0 +1,13 @@
+The [UHP Welcome Experience](https://www.uc.edu/campus-life/honors/students/experiences/welcome-experience-leaders.html) gives incoming first year students the opportunity to connect, build community, engage and learn more about UHP during their first few months here at UC. This year I applied to be a mentor for the Welcome Experience. Besides it being a pre-approved honors experience, it was an opportunity for me to leave my introverted comfort zone and meet new people, and help them learn about the university, the honors program, and help with their transition to the UC community.
+
+This was not my first time mentoring incoming students and helping them with the transition. Every year there is a large group of potential Indian international students, and current students (also Indian international) volunteer to be a resource to them by answering questions, scheduling meetups, and give a tour of the campus. When I was an incoming freshman, I received great help from my seniors. I would have faced a lot of difficulty throughout the transition if this program did not exist. This has led me to volunteering for this every year.
+
+Through the UHP Welcome Experience program, I found an opportunity to yet again serve the next generation of students as a mentor. I got to not only share my knowledge of UC and Cincinnati, but also of the University Honors Program and community. I got to connect with more UHP members, especially with my partner Mia, our co-ordinator Ashley, and ofcourse, our faculty leader Bria. Even in my 4th year at UC, I was pleasently surprised to see that UHP always has something more to offer.
+
+This experience also included some of my first face-to-face interactions with people after the pandemic hit and we were all forced to quarantine. While I have enjoyed my time in isolation away from forced social interactions, I also realized that real human connections are something I have been taking for granted.
+
+Our first meetup with the mentee group involved a tour of the campus disguised as a scavenger hunt. Me and my partner Mia met our mentee group at the bearcat statue, provided them with UHP t-shirts, and started the scavenger hunt. It was quite a workout walking circled around the campus, but it was well worth the conversations and stories we shared. While the mentees did have some knowledge of the campus thanks to their orientations, they were very happy to learn some of the shortcuts and not-so-obvious paths to get from one place to another.
+
+Our second meetup was a chill indoor meeting with cookies, and we talked about campus life, classes, organization involvement, social life etc. It was particularly rewarding to see the mentees applying some pieces of advice we gave them.
+
+A big part of why software development is my passion is that I like creating something and watching it grow and impact lives. I think it is also why I have always wanted to play the role of a mentor, to help shape a person into someone who can go on and make a lot more impact than I can by myself. This experience has taught me that while being a mentor is difficult and requires courage and virtue, it is far more rewarding and fulfilling. I hope I keep getting opportunities like these in the future.
diff --git a/src/images/mentorship.png b/src/data/showcase/experiences/mentorship/logo.png
similarity index 100%
rename from src/images/mentorship.png
rename to src/data/showcase/experiences/mentorship/logo.png
diff --git a/src/data/showcase/experiences/revuc/article.md b/src/data/showcase/experiences/revuc/article.md
new file mode 100644
index 0000000..a95c159
--- /dev/null
+++ b/src/data/showcase/experiences/revuc/article.md
@@ -0,0 +1,11 @@
+[RevolutionUC](https://revolutionuc.com/) is an annual hackathon hosted by the [ACM@UC](http://acmatuc.org/) student organization. I have been an executive member of the organization for 2 years, and I volunteered for organizing RevolutionUC both years. RevolutionUC organizers are split into 4 teams – Logistics, Sponsorship, Marketing, and Web. This year, I was given the opportunity to be the lead of the Web team, and I was equal parts excited and scared for this. But I recognize that we can only learn new things and develop ourselves when we do things outside our comfort zone, and that is always a scary endeavor. So, I happily accepted the opportunity. And I can confidently say that this has been one of the best experiences of my life.
+
+My work and responsibilities during this experience can be put into three broad roles: a Developer, a Leader and an Organizer.
+
+This opportunity allowed me to explore my passion of automation, software development, and problem solving. As the Developer, I designed some systems and applications that helped us organize the entire hackathon by automating some tasks. This [architecture diagram](/images/experiences/revolutionuc/architecture.png) shows all the various applications and services, and how they interact with each other, and with the users. Most of these were built from scratch by me and my team this year. Others were built by my predecessors and have existed for a few years. We just maintained them and gave them a few feature upgrades.
+
+Managing a system and a team proved to be the most difficult part of the experience for me, as I have always been a solo guy. But I do have a little bit of experience and exposure to how management is done effectively, so I knew where to start. In this age, our tools can do half the job for us, so we need to know the strengths and limitations of the tools we are using. I was using Microsoft Teams for meetings, notes, files and updates [(example)](/images/experiences/revolutionuc/teams.png). Trello was my choice for managing tasks. I made use of columns, checklists, labels, assignments, and integrations to customize the Trello board to our needs [(example)](/images/experiences/revolutionuc/trello.png).
+
+The day of event was a tough one, as my work started very early in the morning, so I had to skip breakfast. After getting done with my day-of chores like setting up the live site, making sure everyone is able to check in, and everything is running smoothly, I finally got a little time to grab a bite and a coffee. The rest of the day was all about talking to attendees on our Discord, helping participants with projects, and making new connections. We had over 230 participants from 11 countries, in addition to representatives from sponsor companies, mentors from the industry, and qualified judges. A bunch of mini-events were hosted for the attendees to take a break and socialize.
+
+This experience helped me develop myself in not just one or two, but all of the 5 UHP competencies. Additionally, the systems I built as a part of this experience are not mere hobby projects, but industry-grade software that is deployed in the cloud and is expected to handle hundreds of users. I can put this on my resume and showcase to potential employers. I am sure they will be interested in someone who can manage a system of this scale, as well as the soft skills that come with leading a team and organizing an event.
diff --git a/src/images/revolutionuc1.jpeg b/src/data/showcase/experiences/revuc/banner.jpeg
similarity index 100%
rename from src/images/revolutionuc1.jpeg
rename to src/data/showcase/experiences/revuc/banner.jpeg
diff --git a/src/images/revolutionuc.png b/src/data/showcase/experiences/revuc/logo.png
similarity index 100%
rename from src/images/revolutionuc.png
rename to src/data/showcase/experiences/revuc/logo.png
diff --git a/src/data/showcase/experiences/roundtable/article.md b/src/data/showcase/experiences/roundtable/article.md
new file mode 100644
index 0000000..29bf6e5
--- /dev/null
+++ b/src/data/showcase/experiences/roundtable/article.md
@@ -0,0 +1,72 @@
+As someone who is passionate about leadership and student organizations on campus, the Student Leader Round Table was the perfect opportunity for me to reflect on my experiences as a leader, share my own learnings and wisdom, as well as learn from other leaders in the university. Over the spring semester, the round table (or the student leader illuminati as I like to call it) met every other week and discussed a specific issue related to running a student organization. Each of us have had different approaches to the issues, so it was great to hear how the specific situation of an organization affects our approach of thinking about or solving an issue.
+
+## So what happened?
+
+Here are all the sessions listed in order and some ongoing reflection from each session.
+
+### Session 0: Jan 19
+
+We met for the very first time in January to get to know each other and plan out the semester. We broke out into 2 groups, and each group had to come up with 5 topics to talk about throughout the semester.
+This session was probably the first time I have interacted with other student leaders to talk about common issues in an abstract manner.
+
+### Session 1: Feb 2
+
+The first session topic was Hybrid Meetings and Events.
+This is a relatively new issue for student organizations, ever since COVID restrictions have relaxed. After the rise of virtual meetings, organizations have discovered that the convenience of attending an event from home is going to forever change how we connect with our community. At the same time, there are people who, after living in isolation for over a year, really want to get back to face to face interaction. So hybrid meetings seems like the best way to cater to every audience.
+However, since hybrid meetings have never been properly explored by anyone, let alone by student organizations. So we discussed motivations, ideas, challenges, etc. It was a great conversation that I learn a lot from, and hopefully it will allow me to improve the hybrid meeting experience for my organizations.
+
+### Session 2: Feb 16
+
+The topic of our second session was Recruitment.
+This is one of the most elementary issues that every organization has to deal with. To stay relevant in the community and continue to achieve our goals, we have to spread awareness about our organizations' existence and attract people who can contribute to the organization.
+The recruitment process has many different aspects, including (but not limited to) identifying the target audience, figuring out incentives and benefits, and formulating attractive marketing material.
+To exercise formulating elevator pitches, we did the classic "Sell me X in a minute" activity. The presenters chose a few random images, and a volunteer had to come up with an elevator pitch on the spot. This was a great exercise for me personally, because I am often put in a situation where I am in a conversation and I want to tell them about my organization and what we do and why they should get involved.
+
+### Session 3: March 2
+
+In our third meeting, we talked about Executive Transition.
+Executive transition is an issue that usually lives in the blind spot of organization leaders. If we are not conscious about how we are handling transitions to the new executives at the end of our tenures, the organization can potentially go through a very difficult start and change into something else.
+This mostly happens because every leader needs to have certain frameworks and processes to run an organization. If those frameworks are not handed to us by a previous leader, we will come up with our own, which will take a lot of time to figure out, and will be likely very different from what the previous leaders used.
+We talked about the timeline of executive transition - candidacy, elections, transitions and first meeting. For candidacy and elections, we discussed what the candidates and the voters need to know before the elections. We also discussed how different organizations can have different approaches to how the new executive is selected, or how elections are executed.
+Every executive role has some essential core aspects, which need to be clearly documented and shared with the newly elected members. The easiest way to achieve that is to write it in a document and hold a transition meeting between the outgoing and incoming member.
+
+### Session 4: March 23
+
+This is the meeting that I presented in along with a partner, and it was about Inter-Org Collab.
+I am very passionate about collaborations. I think collabs are a great way to build up relationships, expand outreach, and get access to more resources and do bigger projects. So that is what we started the discussion with - benefits of collaborating.
+I had a lot of experiences and anecdotes to share for this presentation, because almost all of ITSA events have been a collab of some sort. They also helped me come up with topics to talk about, as well as to make my point. For example, I brought up the idea of the ITSA partnering with a local cafe and coffee roaster to increase awareness about specialty coffee.
+This specific meeting was also a little disappointing in some ways. It finished in less than 40 minutes, where as all the previous ones went on until the 50-55 minute mark. While some of that can definitely be attributed to low attendance and participation by the other members of the roundtable, I definitely felt like the content we came up with in the meeting was not enough. What makes it worse is that my partner warned me of this, but for some reason I was confident that the content we have in the slides was more than enough. In hindsight looking at the slides of the other meetings, I definitely under-prepared.
+However, even though I did not get much feedback from the other members on this topic, just the preparation had an immense impact on how I think about collaborations, and it helped me organize a lot of my random thoughts and opinions into a clear framework, which I can document further.
+
+### Session 5: April 6
+
+This week the discussion was about UFB Funding and Fundraising.
+This was possibly the topic that I was looking forward to the most, since organization funding has been a concern for me ever since I started being an org leader. Unfortunately, another important event happened to be at the same time, and I was supposed to be a speaker at that event, so I had to make the difficult decision of skipping this round table session.
+I did learn about some of the discussions that happened during the session though, and we had also discussed funding a little in Session 0, so I think I have a good idea of what boat everyone is in.
+Dealing with the University Funding Board usually tends to be a daunting task, because the entire process of getting funds from the board is very intensive and long. While the process helps organizations with making sure the project is successful and we have the details figured out, it can be frustrating sometimes to have to deal with extremely strict deadlines with the amount of work required. And with time and practice, it can become muscle memory to create budget proposals. It also is a great way to learn more about corporate funding processes. While I don't have personal experience with many corporate processed, I would assume that the standards of detail and presentation would be similar to what UFB requires.
+Funding and Sponsorship in general is something that I love thinking about. I have spent a considerable amount of time figuring out how to get companies to fund some ITSA events, with quite a bit of progress. One of the questions during the session was how we pitch our organization to potential sponsors, and that is something I have worked on for my organization a lot. I recognized that what ITSA (and most student orgs) have to offer companies is access to resources and skills to host engaging events on campus. These events could be about anything, and the companies would love for the event to be about them, and they would be willing to pay a lot of money to make that happen.
+
+### Final Session: April 20
+
+Once again, circumstances forced me to make a difficult decision of not attending the roundtable session, since ITSA elections were being held on the same day. It's poetic, the last session of the roundtable was also my last day as a student leader.
+This session was supposed to be a final discussion and reflection day for the roundtable. We were to talk about some key learnings from participating in the discussions, how they have impacted the way we lead our orgs, and how we can learn to be even better.
+Even though I did not attend, I took some time that day after everything to just sit and reflect on my time as a student leader. The roundtable had been a great experience, not just because I got to talk to other passionate student leaders, but also because I was able to gather a lot of knowledge from them and use it to refine my thinking. It also forced me to organize and refine a lot of my own thoughts and ideas into nicely written and presented slides, which is something I don't do often enough. It is very difficult for me start writing down things, but once I start, it's like thoughts automatically flow through my fingers into a neatly structured sentence.
+I have already taken a lot of ideas and learnings from the roundtable and preached them to the new ITSA executive board. I hope they are as passionate to lead a tech org as I was. I also hope more and more people consider creating spaces for leaders to talk about issues and solutions, because it's very difficult to become a leader without help.
+
+## So am I a good leader now?
+
+Well I am certainly a _better_ leader now than I was 6 months ago. That's just how practice works, the more you do something the better you get at it.
+But am I a **good** leader?
+Was I a good leader 6 months ago?
+
+I don't think so.
+
+On April 20, after the ITSA elections had ended, I came back home, did some chores, and lied down on my bed. This is when I started reflecting into my life as a student leader. It was my last day as an official student leader, because my final year was coming up and I had to dedicate all my time to work and study to make sure I graduate with a bang. I also knew I would not have time to do exec transitions at the same time while I'm graduating, so it wouldn't be fair for me to hold that position.
+
+So I asked myself what I had learned throughout the my journey as a leader. I came up with an interesting dichotomous answer - I realized I was good at running an organization, but not leading an organization.
+
+This recent experience has thrown me back to a mentality I thought I left behind a couple years ago, which is that I don't know how to deal with people. Leadership is all about understanding and connecting with the people around us, sharing out vision and passion with them, and encourage collaborative activities to achieve a common goal. I have realized that it will take a lot more time that I thought to learn the skills associated with leadership. A couple workshops and a couple years of being a student leader are not even close to being enough.
+
+On the other hand, I have always been somewhat good with processes, frameworks, and systems. It is what has led me to my success as a software developer, and it has also led to the success of ITSA in such a short time. While I was not a good leader to the ITSA, I believe I was a great planner and organizer to ITSA, which is what many organizations lack. Unfortunately, those same abilities also hampered my leadership opportunities, as I did not put enough trust and faith in other students who wanted to contribute, and preferred doing everything myself.
+
+I hope that in the future I get many more opportunities to expand my leadership skills, and eventually I can get to a point where I can confidently say that I am a **good** leader. But until then, you can bet the I will be involved in as many organizations and events as possible.
diff --git a/src/data/showcase/experiences/roundtable/logo.png b/src/data/showcase/experiences/roundtable/logo.png
new file mode 100644
index 0000000..37469bf
Binary files /dev/null and b/src/data/showcase/experiences/roundtable/logo.png differ
diff --git a/src/data/showcase/experiences/type.d.ts b/src/data/showcase/experiences/type.d.ts
new file mode 100644
index 0000000..fa91fee
--- /dev/null
+++ b/src/data/showcase/experiences/type.d.ts
@@ -0,0 +1,13 @@
+import type { ImageDataLike } from "gatsby-plugin-image"
+
+export interface IExperience {
+ id: string
+ name: string
+ date: string
+ description: string
+ image: ImageDataLike
+ pageImage?: ImageDataLike
+ page?: {
+ childMarkdownRemark: { html: string }
+ }
+}
diff --git a/src/data/showcase/projects/bonfire.md b/src/data/showcase/projects/bonfire.md
new file mode 100644
index 0000000..c4f262f
--- /dev/null
+++ b/src/data/showcase/projects/bonfire.md
@@ -0,0 +1,15 @@
+## Project Goals
+
+This is a project in collaboration with the **University of Cincinnati Corrections Institute** (UCCI), who developed a suite of assessments tools to be used at various decision points across the criminal and juvenile justice systems . The application enables agencies to assess and house risk/need data and support assessment-driven case planning. In addition, the application offers reporting, configuration, and administration features.
+
+## Technology
+
+The application is split into microservices behind an API Gateway. Our clients can use our web application interface, or develop their own solutions that consumes our externally-available API.
+
+## My Role
+
+My role on this project was to develop new features, migrate parts of the application to use newer technology, and maintain the production version of the application by supporting user requests and bug fixes.
+
+## Links
+
+[UCCI Assessment Suite](https://cech.uc.edu/about/centers/ucci/products/assessments.html)
diff --git a/src/data/showcase/projects/data.yaml b/src/data/showcase/projects/data.yaml
index caadbb9..23e45d1 100644
--- a/src/data/showcase/projects/data.yaml
+++ b/src/data/showcase/projects/data.yaml
@@ -25,6 +25,7 @@ projects:
- integration
- rbac
- crossplatform
+ - monorepo
- id: thedynamics
name: TheDynamics Community Application
@@ -44,39 +45,41 @@ projects:
- multicloud
- integration
- # - id: osdp
- # name: Ohio Sentencing Data Platform
- # description: A system for courts to record and analyze sentencing data using standardized entry forms
- # image: images/osdp.png
- # page: ./osdp.md
- # tools:
- # - typescript
- # - react
- # - express
- # - postgres
- # - mongo
- # - drone
- # - docker
- # - linux
- # features:
- # - ddd
- # - devops
- # - rbac
- # - e2e
+ - id: osdp
+ name: Ohio Sentencing Data Platform
+ description: A system to help judges implement standard sentencing entries and empower courts with accessible and reliable information
+ image: images/osdp.png
+ page: ./osdp.md
+ tools:
+ - typescript
+ - react
+ - express
+ - postgres
+ - mongo
+ - drone
+ - docker
+ - linux
+ features:
+ - ddd
+ - devops
+ - rbac
+ - e2e
+ - monorepo
- # - id: bonfire
- # name: UCCI Risk Assessment
- # description: A system for risk assessment tracking for correction agencies
- # tools:
- # - typescript
- # - react
- # - express
- # - postgres
- # features:
- # - distributed
- # - rbac
- # - devops
- # - microservices
+ - id: bonfire
+ name: UCCI Risk Assessment
+ description: A system to enable criminal justice agencies to learn more about individuals in an effort to best address the risk and need factors specific to that person, and as a result best strategize for effective intervention treatment.
+ page: ./bonfire.md
+ tools:
+ - typescript
+ - react
+ - express
+ - postgres
+ features:
+ - distributed
+ - rbac
+ - devops
+ - microservices
- id: portfolio
name: Portfolio
diff --git a/src/data/showcase/projects/hackathon.md b/src/data/showcase/projects/hackathon.md
index 3b765ef..d6fbc72 100644
--- a/src/data/showcase/projects/hackathon.md
+++ b/src/data/showcase/projects/hackathon.md
@@ -1,7 +1,11 @@
-In terms of technical challenge, diversity, and educational value, this has been my biggest project so far.
+## Project Goals
The "Hackathon Suite" is a suite of applications and services that are designed to aid our hackathon organizing teams with various aspects of the hackathon. I joined this project in late 2019, at which point this project had a very small scope. I took charge of this project and the team in 2020, just as we were forced to go virtual. The need for more virtual assistance, along with my endeavors to automate as much as possible, increased the scope of this project drastically.
+## Composition
+
+In terms of technical challenge, diversity, and educational value, this has been my biggest project so far.
+
This project is composed of:
- The main website with all the hackathon information and a registration form. Statically generated using Jekyll.
@@ -14,4 +18,18 @@ This project is composed of:
- An emails server to process templates designed in HTML and SCSS and produce email templates. Built using Express and HEML.
- A modular monolith API server, built with NestJS and Postgres.
-
+
+
+## Architecture
+
+Deployment diagram
+
+
+
+## My Role
+
+I am the lead developer on this project.
+
+## Links
+
+[RevolutionUC Github](https://github.com/revolutionUC/)
diff --git a/src/data/showcase/projects/hitchd.md b/src/data/showcase/projects/hitchd.md
index e69de29..192088a 100644
--- a/src/data/showcase/projects/hitchd.md
+++ b/src/data/showcase/projects/hitchd.md
@@ -0,0 +1,17 @@
+I started my software development journey with this wedding planner app. This was around when my brother was getting married, and Indian weddings have a tendency to be... _extravagant_. I took that opportunity to refine my learnings and get some hands-on development experience, as well as build something we could use to help the planning process.
+
+I ran into [Meteorjs](https://www.meteor.com/) quite early in my life, and I loved how easy it is to have a full stack application up and running. It comes baked in with a lot of features while also maintaining a low learning curve.
+
+**Hitch'd** is a web and mobile app that helps people track and manage multiple aspects of wedding planning, like invitations, budget and expenses, tasks, agendas etc. It was never completed with all the features that I intended, but I was able to complete some features, build a working application complete with user authentication, and deploy to Heroku and Google Play.
+
+The project makes full use of some of the best features Meteor has to offer, like **realtime client-server communication** over websockets, **isomorphic code** in queries and methods, and built-in **cordova integration** to build for mobile.
+
+Hitch'd is not deployed anymore, and I can't seem to find its source code. I will update this page if I do happen to find it.
+
+## My Role
+
+This was a solo project. I was the only person on this project.
+
+## Links
+
+My blog posts about this project - [First](https://medium.com/@devagrawal09/my-first-app-68fdda99eb2f) [Second](https://medium.com/@devagrawal09/my-first-app-release-v0-1-1ab0a0b1dfc) [Third](https://medium.com/@devagrawal09/hitchd-27903ed39c20)
diff --git a/src/data/showcase/projects/hloapp.md b/src/data/showcase/projects/hloapp.md
index e69de29..cb64a9b 100644
--- a/src/data/showcase/projects/hloapp.md
+++ b/src/data/showcase/projects/hloapp.md
@@ -0,0 +1,13 @@
+## Project Goals
+
+This is the first software project that I got paid for. I got a freelance gig through a contact in Hong Kong. The project was for HealthyLovedOnes, a healthcare company based in Hong Kong. The application was a platform for caregivers to create their professional profiles, and get hired for jobs posted on the platform. Customers can create job postings with all the necessary details to find the perfect caregiver. They can also chat with the caregivers and pay them directly through the application.
+
+## Technology
+
+Like my first project [Hitch'd](../hitchd), I used Meteor for this project, and made good use of most of the features that come out of the box. It does not have the best user interface because I am not very good at designing, but it is packed with features of a complete job search platform like Glassdoor.
+
+The app is also translated into Traditional and Simplified Chinese. There were plans of growing the application with a lot more features and into east and south asian languages.
+
+## My Role
+
+I was the only developer working on this project.
diff --git a/src/data/showcase/projects/osdp.md b/src/data/showcase/projects/osdp.md
index 004831a..80c580f 100644
--- a/src/data/showcase/projects/osdp.md
+++ b/src/data/showcase/projects/osdp.md
@@ -1,5 +1,18 @@
----
-title: OSDP
----
+## Project Goals
-This is my current project
+This is a project in collaboration with the **Ohio Criminal Sentencing Commission** to collect criminal sentencing data from courts for analysis and research.
+
+Information about the project can be found at: [https://www.ohiosentencingdata.info](https://www.ohiosentencingdata.info). The platform will achieve goals that include: using data to inform decision-making; improving transparency; and, making data accessible for the public, practitioners, and research. The collection of sentencing data in a comprehensive and searchable database will inform decision-making and give judges the tools and information needed to impose sentences in accordance with the purposes and principles of felony sentencing.
+
+## Technology
+
+OSDP is a full-stack Javascript application with an externally-available Rest API. The application is a vertical-slice monolith with a single-page web application.
+
+## My Role
+
+I am a senior developer on this project with some architecture, management, and leadership responsibilities.
+
+## Links
+
+[OSDP Website](https://ohiosentencingdata.info/)
+[Ohio Criminal Sentencing Commission](https://www.supremecourt.ohio.gov/boards/sentencing/)
diff --git a/src/data/showcase/projects/portfolio.md b/src/data/showcase/projects/portfolio.md
index e69de29..ba7c38c 100644
--- a/src/data/showcase/projects/portfolio.md
+++ b/src/data/showcase/projects/portfolio.md
@@ -0,0 +1,21 @@
+## Project Goals
+
+This project started out as a required learning portfolio for the [University Honors Program (UHP)](https://www.uc.edu/campus-life/honors.html). Now it serves as a showcase of not only my learnings and experiences throughout my college life, but also my personal and professional life.
+
+This portfolio is a house to:
+
+#### Projects
+
+A showcase of software projects that I have been a part of that have made an impact on my life. These range from work projects to personal hobby projects.
+
+#### Experiences
+
+These are projects that are required by the UHP as a form of self development. These are usually 3-4 month long and have specific self-development goals, pre-defined objectives and path, and a reflection at the end.
+
+#### Blog
+
+My personal blog with articles about everything from software development to coffee brewing.
+
+## My Role
+
+This is a solo project.
diff --git a/src/data/showcase/projects/thedynamics.md b/src/data/showcase/projects/thedynamics.md
index d949ef8..62dd414 100644
--- a/src/data/showcase/projects/thedynamics.md
+++ b/src/data/showcase/projects/thedynamics.md
@@ -1,3 +1,13 @@
-This application is the primary platform for TheDynamics community. Members can create their profiles and showcase their projects, and find professional or technical events that interest them.
+## Project Goals
+
+This application is the primary platform for [TheDynamics](https://thedynamics.tech/) community. Members can create their profiles and showcase their projects, find professional or technical events that interest them, or find other members to collaborate with.
+
+This platform will also be used to host [Codetivate](https://codetivate.thedynamics.tech/), TheDynamics's flagship virtual event.
+
+## Technology
The project is a Next.js application deployed on Vercel, and the entire backend is in serverless architecture created using Next.js API Handlers. The application uses MongoDB as its database.
+
+## My Role
+
+I am the lead full-stack developer and architect on this project.
diff --git a/src/data/tech/features/data.yaml b/src/data/tech/features/data.yaml
index fed34fb..8db5d87 100644
--- a/src/data/tech/features/data.yaml
+++ b/src/data/tech/features/data.yaml
@@ -3,73 +3,94 @@ features:
name: Domain-Driven Design
color: "white"
bgColor: "#35524A"
+ description: "A software design approach focusing on modelling software to match a domain"
- id: distributed
name: Distributed
color: "white"
bgColor: "#627C85"
+ description: "Software split into multiple components and distributed across multiple machines on a network"
- id: multicloud
name: Multi-Cloud
color: "black"
bgColor: "#9C9CDB"
+ description: "Leveraging multiple cloud platforms to avoid vendor lock-in and improve cost"
- id: devops
name: DevOps
color: "black"
bgColor: "#A2E8DD"
+ description: "Continuous delivery and automation of software development"
- id: integration
name: External Integration
color: "black"
bgColor: "#32DE8A"
+ description: "Integration with external systems"
- id: rbac
name: Role-Based Access
color: "black"
bgColor: "#FCAA67"
+ description: "Software access defined by user roles"
- id: e2e
name: E2E Testing
color: "white"
bgColor: "#B0413E"
+ description: "End-to-end testing of software"
- id: microservices
name: Microservices
color: "white"
bgColor: "#eF207F"
+ description: "Software split into multiple independent and loosely-coupled services"
- id: isomorphic
name: Isomorphic
color: "white"
bgColor: "#2F40aF"
+ description: "Code that can run on both client and server side"
- id: i18n
name: Internationalization
color: "white"
bgColor: "#309f0F"
+ description: "User interface translation into multiple languages"
- id: pubsub
name: PubSub
color: "white"
bgColor: "#509f7F"
+ description: "Real-time communication between multiple clients and server using publish-subscribe"
- id: crossplatform
name: Cross Platform
color: "black"
bgColor: "#ffb4bb"
+ description: "Software that runs on multiple platforms"
- id: ssg
name: Static Site Generation
color: "white"
bgColor: "#3992ab"
+ description: "Static site generation using data at build time instead of at runtime"
- id: a11y
name: Accessibility
color: "white"
bgColor: "#292f4c"
+ description: "Software that is accessible to all users and devices with assistive technologies"
- id: serverless
name: Serverless
color: "white"
bgColor: "#025669"
+ description: "Software split into independent functions that are run on demand"
+
+ - id: monorepo
+ name: Monorepo
+ color: "white"
+ bgColor: "#3992ab"
+ description: "An approach to source code management of multiple projects in a single repository"
diff --git a/src/data/tech/tools/data.yaml b/src/data/tech/tools/data.yaml
index 0d15111..66d260d 100644
--- a/src/data/tech/tools/data.yaml
+++ b/src/data/tech/tools/data.yaml
@@ -4,129 +4,151 @@ tools:
color: "white"
bgColor: "#007acc"
devicon: typescript-plain
+ description: "A statically typed superset of JavaScript"
- id: react
name: React
color: "black"
bgColor: "#61DBFB"
devicon: react-original
+ description: "You know what React is."
- id: angular
name: Angular
color: "white"
bgColor: "#dd0031"
devicon: angularjs-plain
+ description: "A batteries-included front-end framework for building scalable applications"
- id: express
name: Express
color: "white"
bgColor: "#444444"
devicon: express-original
+ description: "A minimal and flexible Node.js web application framework"
- id: nest
name: Nest
color: "white"
bgColor: "#df234f"
devicon: nestjs-plain
+ description: "A dotnet style framework for building enterprise-level Node.js applications"
- id: postgres
name: PostgreSQL
color: "white"
bgColor: "#336791"
devicon: postgresql-plain
+ description: "A powerful, open source object-relational database system"
- id: mongo
name: MongoDB
color: "black"
bgColor: "#4faa41"
devicon: mongodb-plain
+ description: "A NoSQL database with a friendly user interface for JavaScript and Node.js developers"
- id: heroku
name: Heroku
color: "white"
bgColor: "#6762a6"
devicon: heroku-line
+ description: "A container-based cloud platform as a service (PaaS) for developers"
- id: docker
name: Docker
color: "white"
bgColor: "#019bc6"
devicon: docker-plain
+ description: "A containerization platform for distributed applications"
- id: linux
name: Linux
color: "white"
bgColor: "black"
devicon: linux-plain
+ description: "You know what Linux is."
- id: meteor
name: Meteor
color: "white"
bgColor: "#df5052"
devicon: meteor-plain
+ description: "A framework to build real-time full stack web applications with Node.js and MongoDB"
- id: android
name: Android
color: "white"
bgColor: "#a4c439"
devicon: android-plain
+ description: "A mobile operating system for mobile devices"
- id: aws
name: AWS
color: "black"
bgColor: "#f7a80d"
iconPng: "icons/aws.png"
+ description: "The most popular cloud platform"
- id: jekyll
name: Jekyll
color: "white"
bgColor: "#d80101"
iconPng: "icons/jekyll.png"
+ description: "A static site generator for Ruby"
- id: netlify
name: Netlify
color: "black"
bgColor: "#40a0b7"
iconPng: "icons/netlify.png"
+ description: "A cloud platform for hosting static sites"
- id: travis
name: Travis CI
color: "white"
bgColor: "#3EAAAF"
iconPng: "icons/travis.png"
+ description: "A cloud-based continuous integration platform for software development"
- id: drone
name: Drone CI
color: "white"
bgColor: "#1e375a"
iconPng: "icons/drone.png"
+ description: "An open source container-based continuous integration platform for software development"
- id: discord
name: Discord
color: "white"
bgColor: "#5560e9"
iconPng: "icons/discord.png"
+ description: "A cloud-based chat and voice application"
- id: cordova
name: Cordova
color: "black"
bgColor: "#4dc2e4"
iconPng: "icons/cordova.png"
+ description: "A cross-platform mobile application development framework"
- id: cloudflare
name: Cloudflare
color: "white"
bgColor: "#f6821f"
iconPng: "icons/cloudflare.png"
+ description: "A web application security platform"
- id: gatsby
name: Gatsby
color: "white"
bgColor: "#663399"
devicon: gatsby-plain
+ description: "A static site generator for React"
- id: next
name: Next.js
color: "white"
bgColor: "#111"
devicon: nextjs-plain
+ description: "A server-side rendering framework for React"
diff --git a/src/images/gatsby-astronaut.png b/src/images/gatsby-astronaut.png
deleted file mode 100644
index da58ece..0000000
Binary files a/src/images/gatsby-astronaut.png and /dev/null differ
diff --git a/src/images/gatsby-icon.png b/src/images/gatsby-icon.png
deleted file mode 100644
index 908bc78..0000000
Binary files a/src/images/gatsby-icon.png and /dev/null differ
diff --git a/src/images/generated-card-bg.png b/src/images/generated-card-bg.png
new file mode 100644
index 0000000..eee8d53
Binary files /dev/null and b/src/images/generated-card-bg.png differ
diff --git a/src/images/hackathon.jpg b/src/images/hackathon.jpg
deleted file mode 100644
index 5cd2661..0000000
Binary files a/src/images/hackathon.jpg and /dev/null differ
diff --git a/src/images/hitchd.jpg b/src/images/hitchd.jpg
deleted file mode 100644
index ec9aeea..0000000
Binary files a/src/images/hitchd.jpg and /dev/null differ
diff --git a/src/images/hlo.jpg b/src/images/hlo.jpg
deleted file mode 100644
index 31b3f36..0000000
Binary files a/src/images/hlo.jpg and /dev/null differ
diff --git a/src/images/icons/aws.png b/src/images/icons/aws.png
deleted file mode 100644
index b58af47..0000000
Binary files a/src/images/icons/aws.png and /dev/null differ
diff --git a/src/images/icons/cordova.png b/src/images/icons/cordova.png
deleted file mode 100644
index a1783f5..0000000
Binary files a/src/images/icons/cordova.png and /dev/null differ
diff --git a/src/images/icons/discord.png b/src/images/icons/discord.png
deleted file mode 100644
index 18442d3..0000000
Binary files a/src/images/icons/discord.png and /dev/null differ
diff --git a/src/images/icons/drone.png b/src/images/icons/drone.png
deleted file mode 100644
index 976c9ac..0000000
Binary files a/src/images/icons/drone.png and /dev/null differ
diff --git a/src/images/icons/jekyll.png b/src/images/icons/jekyll.png
deleted file mode 100644
index adc6683..0000000
Binary files a/src/images/icons/jekyll.png and /dev/null differ
diff --git a/src/images/icons/netlify.png b/src/images/icons/netlify.png
deleted file mode 100644
index faf3ac4..0000000
Binary files a/src/images/icons/netlify.png and /dev/null differ
diff --git a/src/images/icons/travis.png b/src/images/icons/travis.png
deleted file mode 100644
index 1ffdfa7..0000000
Binary files a/src/images/icons/travis.png and /dev/null differ
diff --git a/src/images/merge-images.ts b/src/images/merge-images.ts
new file mode 100644
index 0000000..7fcb1dd
--- /dev/null
+++ b/src/images/merge-images.ts
@@ -0,0 +1,91 @@
+import fs from "fs"
+import { Canvas, Image, loadImage } from "canvas"
+
+const bgSrc = `${process.cwd()}/src/images/generated-card-bg.png`
+const bgImage = loadImage(bgSrc)
+
+interface Source {
+ src: string
+ img?: Image
+ x?: number
+ y?: number
+ dWidth?: number
+ dHeight?: number
+}
+
+const mergeImages = async (sources: Source[] = [], targetUrl: string) => {
+ const images = await Promise.all(
+ sources.map(async source => {
+ if (source.img) {
+ console.log(`Already loaded ${source.src}`)
+ return source
+ }
+ console.log(`Loading image ${source.src}`)
+ const img = await loadImage(source.src)
+ source.img = img
+ console.log(`Loaded image ${source.src}`)
+ return source
+ })
+ )
+
+ const canvas = new Canvas(1200, 627)
+
+ const ctx = canvas.getContext("2d")
+
+ images.forEach(({ img, ...source }) => {
+ ctx.globalAlpha = 1
+
+ return ctx.drawImage(
+ img,
+ source.x || 0,
+ source.y || 0,
+ source.dWidth ? source.dWidth : img.width,
+ source.dHeight ? source.dHeight : img.height
+ )
+ })
+
+ const buffer = canvas.toBuffer("image/png")
+
+ return fs.promises.writeFile(targetUrl, buffer)
+}
+
+export const mergeWithBackground = async (fgImg, targetUrl) => {
+ const fgSrc = fgImg.absolutePath
+ if (!fgSrc) {
+ throw new Error(`Source image for ${targetUrl} not found`)
+ }
+
+ const imageData = fgImg.childImageSharp.gatsbyImageData
+
+ const maxHeight = 420
+ const maxWidth = 1140
+ const maxRatio = maxWidth / maxHeight
+
+ let dWidth = imageData.width
+ let dHeight = imageData.height
+
+ const ratio = imageData.width / imageData.height
+
+ if (ratio > maxRatio) {
+ dWidth = maxWidth
+ dHeight = maxWidth / ratio
+ } else {
+ dHeight = maxHeight
+ dWidth = maxHeight * ratio
+ }
+
+ const x = (1200 - dWidth) / 2
+ const y = (480 - dHeight) / 2 + 145
+
+ console.log(`Merging ${fgSrc} with ${bgSrc}`)
+
+ await mergeImages(
+ [
+ { src: bgSrc, x: 0, y: 0, img: await bgImage },
+ { src: fgSrc, x, y, dWidth, dHeight },
+ ],
+ targetUrl
+ )
+
+ console.log(`Generated ${targetUrl}`)
+}
diff --git a/src/images/osdp.png b/src/images/osdp.png
deleted file mode 100644
index 2c09c2e..0000000
Binary files a/src/images/osdp.png and /dev/null differ
diff --git a/src/images/roundtable.png b/src/images/roundtable.png
deleted file mode 100644
index 223173e..0000000
Binary files a/src/images/roundtable.png and /dev/null differ
diff --git a/src/pages/404.js b/src/pages/404.js
index 455c635..fac6d6a 100644
--- a/src/pages/404.js
+++ b/src/pages/404.js
@@ -3,7 +3,7 @@ import { Link } from "gatsby"
import Layout from "../components/layout"
const NotFoundPage = ({ location }) => (
-
+
diff --git a/src/pages/about.js b/src/pages/about.js
index eca8af1..2b786b6 100644
--- a/src/pages/about.js
+++ b/src/pages/about.js
@@ -4,7 +4,7 @@ import resume from "./resume.pdf"
import me from "../images/about.jpg"
const AboutPage = ({ location }) => (
-
+
![]()
(
-
+
About me
I am Dev Agrawal (The name 'Dev' translates to 'God', but I
- don't let that get to my head :P ). I am a third-year
+ don't let that get to my head :P ). I am a fifth-year
Information Technology major at the University of Cincinnati.
I am also a software developer, and currently I work at the UC
IT Solutions Center.
I was introduced into this world on the 9th of May 1999, the
- last summer of the millenium, in the beautiful and diverse
+ last summer of the millennium, in the beautiful and diverse
country of India. I was born to highly socially active
parents, with a large age gap between me and all of my older
cousins, including my brother. These factors made me a very
@@ -54,7 +54,7 @@ const AboutPage = ({ location }) => (
most of it is problem solving.
-
+
Check out my resume here!
diff --git a/src/pages/blog/index.tsx b/src/pages/blog/index.tsx
new file mode 100644
index 0000000..b1f40fd
--- /dev/null
+++ b/src/pages/blog/index.tsx
@@ -0,0 +1,146 @@
+import React, { FC, HTMLAttributes } from "react"
+import { Link, graphql } from "gatsby"
+import { GatsbyImage, getImage } from "gatsby-plugin-image"
+import { IArticle, ITag } from "../../data/blog/type"
+import Layout from "../../components/layout"
+import { Row, Col, Card } from "react-bootstrap"
+import { TagBadge } from "./../../components/portfolio/tag-badge"
+
+export const query = graphql`
+ query BlogQuery {
+ allMarkdownRemark(
+ filter: { frontmatter: { date: { ne: null } } }
+ sort: { fields: frontmatter___featured, order: ASC }
+ ) {
+ nodes {
+ frontmatter {
+ id
+ title
+ date
+ tags
+ image {
+ childImageSharp {
+ gatsbyImageData
+ }
+ }
+ }
+ timeToRead
+ excerpt
+ }
+ }
+
+ tagsYaml {
+ tags {
+ id
+ name
+ color
+ bgColor
+ }
+ }
+ }
+`
+
+const ArticleCard: FC<
+ { article: IArticle; allTags: ITag[]; image?: boolean } & HTMLAttributes
+> = ({ article, allTags, image, ...props }) => {
+ const tags = allTags.filter(tag => article.frontmatter.tags?.includes(tag.id))
+
+ return (
+ <>
+
+
+
+
+
+
+ {article.frontmatter.title}
+
+
+
+
+ Published on {article.frontmatter.date}
+
+
+ {article.timeToRead} minute read
+
+
+
+ {tags.map(tag => (
+
+ ))}
+ {article.frontmatter.image && image && (
+
+ )}
+
+ {article.excerpt}
+
+
+
+
+
+ )
+}
+
+const BlogHomePage = ({ location, data }) => {
+ const [first, second, third, ...articles]: IArticle[] =
+ data.allMarkdownRemark.nodes
+ const allTags: ITag[] = data.tagsYaml.tags
+
+ return (
+
+
+
+
Blog
+
+
+
+
+
+
+
+
+ {articles.map(article => (
+
+
+
+ ))}
+
+
-
-
- I am driven by my beliefs in passion, competency, and knowledge. I
- pursue these passions by utilizing my core strengths of analysis,
- exploration, and deliberative planning. I plan to live out these
- values through opportunities where I am researching and building to
- achieve excellence and reflection that impacts communities and
- technology. To do so, I will seek opportunities to use technology in
- new ways and change our perception of the world. When I face
- challenges or obstacles along the way, I will remember to stay
- flexible and maintain a hopeful outlook.
- {" "}
-
-
- My Global Citizen Scholar Mission
-
-
-
-
-
-
-
-
-
-
-
-
-
- Global Citizen Scholar Plan
-
-
-
- The world is run on ideas and beliefs. Our ideas point the way
- to go, and our beliefs guide us throughout the journey. This
- journey, called “life”, is a long and complicated one, and is
- full of not only obstacles, but twists and loops which can
- bring even the most prepared travelers to their submission.
- The key to a successful journey is to stick to the most basic
- virtues of your life, which are your ideas and your beliefs.
- Or at least, this is the popular opinion.
-
-
- What people don’t realize is that sometimes, you cannot stick
- to your ideas while holding on to your beliefs. This conflict
- has a way of making the strongest people enter existential
- crisis. Think about it yourself – would you hold on to a set
- of beliefs you have gathered over your life that define who
- you are as an individual? Or can you sacrifice your beliefs
- for an idea that could potentially change you and your life,
- and something that does a greater good to the community?
-
-
- It might seem easy to theorize that you can always stick to
- your beliefs and still work on your ideas. But believe me,
- everyone faces this conflict at least once in their lifetime.
- Most people spend their lifetime trying to figure out what to
- stick to. And the strongest people are the ones who want to
- work on their best ideas as much as they want to hold on to
- their beliefs, and are therefore hit the worst when they have
- to choose one.
-
-
- I have been fortunate enough to face this conflict early on in
- my life, when making the choice could not have devastated me.
- I chose to run towards my ideas, work on my future, and serve
- the greater good, even if it meant sacrificing what I believe
- in. I am not suggesting in any way that choosing ideas over
- beliefs is the right thing to do. What I will suggest,
- however, is that there is a “better” choice for everyone out
- there. I have no idea as to how to know what it is. Mine just
- came to me.
-
-
- So, what is it that I have planned for myself? A social
- worker? A scientist? A rockstar?
-
-
- I choose 2 simple ideas to be my guide – the first is a desire
- to reach greatness. It is the part of me that wants to be a
- name that every person on the planet knows. Its goals are very
- ambitious, even selfish sometimes. This is my primary
- objective, and it helps me make long-term decisions.
-
-
- But it is pretty easy to get lost and take wrong turns if you
- only have such a large ambition. Which is why I have the
- second idea – changing others’ lives for the better. This is a
- selfless mission of bringing about a change in the community,
- one that not only empowers the helpless, but also changes the
- way we perceive the world around us. Often when I get lost
- looking at the big picture and thinking about my ambition,
- this idea of greater good tells me what to do and brings me
- back on track.
-
-
- How do I achieve greatness and service my community? I again
- have a simple idea to stick to here – Find a way to achieve
- your goals doing what you like the most. If you know that I am
- majoring in Information Technology, it should come as no
- surprise that I intend to use my knowledge of technology to
- achieve both my goals. Knowledge is another competency that
- drives my actions – an endless thirst for knowledge,
- regardless of its utility. My love of learning new things
- fuels my actions and accomplishments.
-
-
- Reflection is also a competency that affects my decisions, and
- it’s one of the major topics of interest in the Honors
- program. Throughout the Gateway class, we have been encouraged
- to reflect upon our activities. This is something I am fond
- of, because your best teacher is your own past. Your
- accomplishments teach you about your strengths and how to use
- them to your advantage, and your mistakes tell you about your
- weaknesses and how to overcome them. Unfortunately, a lot of
- people do not realize the benefits of reflection and see it
- merely as a waste of time.
-
-
- These are the new set of beliefs I have adopted that will help
- me realize my mission of greatness and service to the
- community.
-
-
-
-
-
-
-
-
-
-
-
- Reflection
- Problem Pitch
-
-
- In the beginning of October 2018, I chose the topic{" "}
- Cure for diseases (Cancer, aids, etc) for
- working on as a first step towards becoming a “Global Citizen
- Scholar”. To be honest, I did not have a lot of prior
- knowledge on interest in this field. I chose it because it was
- the topic that I was “most comfortable” with. But about a
- month later, I was glad that I made this decision.
-
-
- I was working with two other students on this problem, I saw
- them taking this with so much interest and sincerity, it made
- me wonder “Why? How?”. Both of my partners had a lot of
- knowledge, experience and contacts that they could put to use
- for working on this problem. I know that because I have been
- there. I have always taken up projects in fields of my
- interest. This was probably the first time I had moved so far
- from my comfort zone.
-
-
- Then it hit me. We are not born as a “Global Citizen Scholar”.
- To be one,you need to grow and develop. You need to step
- outside your comfort zone and find new ways to help yourself
- and the people around you. So I did. I started doing my
- homework. I started looking into new developments in the field
- of medicine and pharmacy. I also discussed potential interview
- candidates with my partners. We had a brief and informative
- talk with James Hester, a Roche Diagnostics sales
- representative for Northern Indiana. The interview gave me new
- insight into the whole process of medicine research, testing,
- marketing and utilization. James gave us interesting knowledge
- into the making and working of a cancer treatment, and how the
- presence of a specific gene mutation can affect not only the
- severity of the disease, but also decides whether the
- treatment will work or not. He also told us about how the
- pharmaceutical industry could change in the near future with
- the advent of new technologies, which will help us better
- understand the biology of these diseases.
-
-
- Unfortunately, this is an area where getting involved is not
- easy, as it requires a significant amount of knowledge and
- experience to make a significant contribution. Or, atleast
- that’s what I thought. James told us that getting involved in
- this area is a lot easier than I think, because researchers
- are constantly looking for interested students to hire as
- interns and assistants, and they make a significant
- contribution in moving the project forward.
-
-
- This whole experience taught me why the Honors program wants
- us to be “Global Citizen Scholars”, and what that exactly
- means. It is not only about helping others, but also about
- self-development (and that’s the part that appeals to me the
- most because, you know, I’m selfish ;P). I know that there
- will be challenges in this new mission, and I am ready to face
- them.
-
-
-
-
-
-
-
Welcome to my site!
-
-
-
-)
-
-export default IndexPage
diff --git a/src/pages/index.tsx b/src/pages/index.tsx
new file mode 100644
index 0000000..72bd774
--- /dev/null
+++ b/src/pages/index.tsx
@@ -0,0 +1,59 @@
+import { Link } from "@gatsbyjs/reach-router"
+import { FontAwesomeIcon } from "@fortawesome/react-fontawesome"
+import { faAward, faCode, faNewspaper } from "@fortawesome/free-solid-svg-icons"
+
+import React from "react"
+import Layout from "../components/layout"
+import profileImg from "./profile.jpg"
+
+const IndexPage = ({ location }) => (
+
+
+
+
+
+
+
+
+
Welcome!
+
+ I am a software developer and an aspiring software architect and
+ content creator.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/src/pages/review/junior.js b/src/pages/review/junior.js
index a517958..fa13ecb 100644
--- a/src/pages/review/junior.js
+++ b/src/pages/review/junior.js
@@ -2,7 +2,7 @@ import React from "react"
import Layout from "../../components/layout"
const JuniorYearPage = ({ location }) => (
-
+
diff --git a/src/pages/review/sophomore.js b/src/pages/review/sophomore.js
index 21cb7a8..efcde96 100644
--- a/src/pages/review/sophomore.js
+++ b/src/pages/review/sophomore.js
@@ -2,7 +2,7 @@ import React from "react"
import Layout from "../../components/layout"
const SophomoreYearPage = ({ location }) => (
-
+
diff --git a/src/pages/showcase/experiences/index.js b/src/pages/showcase/experiences/index.js
deleted file mode 100644
index 0ffa6f2..0000000
--- a/src/pages/showcase/experiences/index.js
+++ /dev/null
@@ -1,142 +0,0 @@
-import React from "react"
-import { Link } from "gatsby"
-import Layout from "../../../components/layout"
-import leadershapeLogo from "../../../images/leadershape.png"
-import revucLogo from "../../../images/revolutionuc.png"
-import mentorshipLogo from "../../../images/mentorship.png"
-import roundtableLogo from "../../../images/roundtable.png"
-
-const ExperiencesPage = ({ location }) => (
-
-
-
-
My Honors Experiences
-
-
-
-
-
- Jan 2022
-
- Student Leader Round Table
-
-
-
-
-
-
-
-
-
-
The student leader illuminati
-
-
-
-
-
-
-
-
-
- August 2021
-
- Welcome Experience Mentorship
-
-
-
-
-
-
-
-
-
-
Mentoring the next generation of honors
-
-
-
-
-
-
-
-
-
- Feb 2021
-
- RevolutionUC Organizing
-
-
-
-
-
-
-
-
-
-
- A hackathon hosted at the University of Cincinnati
-
-
-
-
-
-
-
-
-
-
- Jan 2019
-
- LeaderShape Institute
-
-
-
-
-
-
-
-
-
-
Blooming leaders of tomorrow
-
-
-
-
-
-)
-
-export default ExperiencesPage
diff --git a/src/pages/showcase/experiences/index.tsx b/src/pages/showcase/experiences/index.tsx
new file mode 100644
index 0000000..429e42f
--- /dev/null
+++ b/src/pages/showcase/experiences/index.tsx
@@ -0,0 +1,79 @@
+import React from "react"
+import { graphql, Link } from "gatsby"
+import Layout from "../../../components/layout"
+import { IExperience } from "../../../data/showcase/experiences/type"
+import { GatsbyImage, getImage } from "gatsby-plugin-image"
+
+const ExperienceCard = ({ experience }: { experience: IExperience }) => {
+ return (
+
+
+
+
+
+ {experience.date}
+ {experience.name}
+
+
+
+
+
+
+
+
+
{experience.description}
+
+
+
+
+ )
+}
+
+export const query = graphql`
+ query ExperiencesQuery {
+ experiencesYaml {
+ experiences {
+ id
+ name
+ date
+ description
+ image {
+ childImageSharp {
+ gatsbyImageData(layout: CONSTRAINED, height: 200)
+ }
+ }
+ }
+ }
+ }
+`
+
+const ExperiencesPage = ({ location, data }) => {
+ const experiences: IExperience[] = data.experiencesYaml.experiences
+
+ return (
+
+
+
+
My Honors Experiences
+ {experiences.map((experience, i) => (
+
+ ))}
+
+
+
+ )
+}
+
+export default ExperiencesPage
diff --git a/src/pages/showcase/experiences/leadershape.js b/src/pages/showcase/experiences/leadershape.js
deleted file mode 100644
index c65f3f5..0000000
--- a/src/pages/showcase/experiences/leadershape.js
+++ /dev/null
@@ -1,113 +0,0 @@
-import React from "react"
-import Layout from "../../../components/layout"
-import leadershape1 from "../../../images/leadershape1.jpg"
-import leadershape2 from "../../../images/leadershape2.jpeg"
-
-const LeadershapePage = ({ location }) => (
-
-
-
-
-
-
-
-
-
- Jan 2019
- Leadershape
-
-
- One of the five competencies of the University Honors Program
- is Leadership. Leadership is the ability to influence and
- inspire a group of people and turning the group into a single
- unit which amplifies everyone's strengths and minimized
- weaknesses. A major mission on my way to become a Global
- Citizen Scholar and achieve my dream is to become an effective
- leader. And that is precisely what Leadershape Institute, a
- 6-day workshop/retreat, is meant for - to show us the path to
- becoming effective leaders.
-
-
- The approach taken by Leadershape to make us understand the
- building blocks of a leader was interesting and effective.
- They take a brief definition of what constitutes a leader,
- break it apart into pieces, and expand each piece over the
- course of an entire day so that we have a complete picture.
- Each day brought insight into a new dimension of life, forcing
- us to think about things in ways we never thought existed. The
- key takeaway was as simple as putting all the pieces gained
- throughout the course of the week together (which is much
- easier said than done).
-
-
- Perhaps the most interesting day for me was the day we were
- talking about the term "Vision". One of the most compelling
- attributes of a good leader is ambition, and only a person
- with an ambition mission can become a good leader. A Vision to
- realize, a mission to complete, these are great motivators.
- They drive a person and their actions like nothing else can. A
- leader needs to be driven towards a goal, only then can he
- inpire others to follow him on his campaign.
I found
- this particularly interesting because I have always considered
- myself to be a very ambitious person. I often think about
- where I could be 5-10 years in the future, and those scenarios
- are sometimes not very realistic. But on this day, we had to
- think about a specific personal vision that we always have
- wanted to see realized. So unlike the other occasions when I
- used to dream about my future, this one had to be a little
- more realistic, specific and organized, so that I can easily
- convey it. This was followed by an activity, which made us
- write a news artice that would be published when our vision
- would be realized, and the news artice would describe the
- achievement.{" "}
-
- Here is the article I wrote.
-
-
-
- Aside from the main objective, one important aspect of the
- whole experience was getting to know more like-minded people
- and talking about ideas, thoughts and feelings. On the very
- first day, we were told that to truly develop self, we need to
- stretch out of our comfort zone and try out new things, until
- those new things become our comfort zone. For me, this is
- exactly what happened throughout the week.
-
-
- Being a socially anxious person, the level of social exposure
- was something I have only experienced once in a similar
- workshop 4 years ago, and I was not very happy with my
- attempts at socializing. So going into Leadershape was a
- little tough for me. But in Leadershape, we were divided into
- what we called "Family clusters", which was a group of 6 or 7
- students and a faculty member. And I am very grateful that
- everyone in my family cluster accepted me for who I am, helped
- me throughout the week in stretching myself out of my comfort
- zone, and allowed me to help them similarly.
-
-
- But that was not the limit of social interaction I was exposed
- to. We had multiple pair and group discussion sessions, often
- with random people, and we enjoyed many games and activities,
- all of which really broke the ice between us. Perhaps the most
- enjoyable aspect of the entire week was the late-night games
- that we students played. Those late nights forced me to get
- out of my fortress of solitude and connect with like-minded
- people on various levels. I am looking forward to seeing how
- these new relationships I have forged carry out of the
- workshop and develop into something greater.
-
-
-
-
-
-
-)
-
-export default LeadershapePage
diff --git a/src/pages/showcase/experiences/mentorship.js b/src/pages/showcase/experiences/mentorship.js
deleted file mode 100644
index cb28a29..0000000
--- a/src/pages/showcase/experiences/mentorship.js
+++ /dev/null
@@ -1,107 +0,0 @@
-import React from "react"
-import Layout from "../../../components/layout"
-import revolutionuc1 from "../../../images/revolutionuc1.jpeg"
-
-const WelcomeExperiencePage = ({ location }) => (
-
-
-
-
-
-
-
-
-
- August 2021
-
- UHP Welcome Experience Mentorship
-
-
-
- The{" "}
-
- UHP Welcome Experience
- {" "}
- gives incoming first year students the opportunity to connect,
- build community, engage and learn more about UHP during their
- first few months here at UC. This year I applied to be a
- mentor for the Welcome Experience. Besides it being a
- pre-approved honors experience, it was an opportunity for me
- to leave my introverted comfort zone and meet new people, and
- help them learn about the university, the honors program, and
- help with their transition to the UC community.
-
-
- This was not my first time mentoring incoming students and
- helping them with the transition. Every year there is a large
- group of potential Indian international students, and current
- students (also Indian international) volunteer to be a
- resource to them by answering questions, scheduling meetups,
- and give a tour of the campus. When I was an incoming
- freshman, I received great help from my seniors. I would have
- faced a lot of difficulty throughout the transition if this
- program did not exist. This has led me to volunteering for
- this every year.
-
-
- Through the UHP Welcome Experience program, I found an
- opportunity to yet again serve the next generation of students
- as a mentor. I got to not only share my knowledge of UC and
- Cincinnati, but also of the University Honors Program and
- community. I got to connect with more UHP members, especially
- with my partner Mia, our co-ordinator Ashley, and ofcourse,
- our faculty leader Bria. Even in my 4th year at UC, I was
- pleasently surprised to see that UHP always has something more
- to offer.
-
-
- This experience also included some of my first face-to-face
- interactions with people after the pandemic hit and we were
- all forced to quarantine. While I have enjoyed my time in
- isolation away from forced social interactions, I also
- realized that real human connections are something I have been
- taking for granted.
-
-
- Our first meetup with the mentee group involved a tour of the
- campus disguised as a scavenger hunt. Me and my partner Mia
- met our mentee group at the bearcat statue, provided them with
- UHP t-shirts, and started the scavenger hunt. It was quite a
- workout walking circled around the campus, but it was well
- worth the conversations and stories we shared. While the
- mentees did have some knowledge of the campus thanks to their
- orientations, they were very happy to learn some of the
- shortcuts and not-so-obvious paths to get from one place to
- another.
-
-
- Our second meetup was a chill indoor meeting with cookies, and
- we talked about campus life, classes, organization
- involvement, social life etc. It was particularly rewarding to
- see the mentees applying some pieces of advice we gave them.
-
-
- A big part of why software development is my passion is that I
- like creating something and watching it grow and impact lives.
- I think it is also why I have always wanted to play the role
- of a mentor, to help shape a person into someone who can go on
- and make a lot more impact than I can by myself. This
- experience has taught me that while being a mentor is
- difficult and requires courage and virtue, it is far more
- rewarding and fulfilling. I hope I keep getting opportunities
- like these in the future.
-
-
-
-
-
-
-)
-
-export default WelcomeExperiencePage
diff --git a/src/pages/showcase/experiences/revolutionuc.js b/src/pages/showcase/experiences/revolutionuc.js
deleted file mode 100644
index 3657891..0000000
--- a/src/pages/showcase/experiences/revolutionuc.js
+++ /dev/null
@@ -1,118 +0,0 @@
-import React from "react"
-import Layout from "../../../components/layout"
-import revolutionuc1 from "../../../images/revolutionuc1.jpeg"
-import revolutionuc2 from "../../../images/revolutionuc2.png"
-import revolutionuc3 from "../../../images/revolutionuc3.png"
-import revolutionuc4 from "../../../images/revolutionuc4.png"
-
-const RevolutionUCPage = ({ location }) => (
-
-
-
-
-
-
-
-
-
- Feb 2021
-
- RevolutionUC Organizing
-
-
-
- RevolutionUC is an
- annual hackathon hosted by the{" "}
- ACM@UC student organization.
- I have been an executive member of the organization for 2
- years, and I volunteered for organizing RevolutionUC both
- years. RevolutionUC organizers are split into 4 teams –
- Logistics, Sponsorship, Marketing, and Web. This year, I was
- given the opportunity to be the lead of the Web team, and I
- was equal parts excited and scared for this. But I recognize
- that we can only learn new things and develop ourselves when
- we do things outside our comfort zone, and that is always a
- scary endeavor. So, I happily accepted the opportunity. And I
- can confidently say that this has been one of the best
- experiences of my life.
-
-
- My work and responsibilities during this experience can be put
- into three broad roles: a Developer, a{" "}
- Leader and an Organizer.
-
-
- This opportunity allowed me to explore my passion of
- automation, software development, and problem solving. As the
- Developer, I designed some systems and applications that
- helped us organize the entire hackathon by automating some
- tasks. This{" "}
-
- architecture diagram
- {" "}
- shows all the various applications and services, and how they
- interact with each other, and with the users. Most of these
- were built from scratch by me and my team this year. Others
- were built by my predecessers and have existed for a few
- years. We just maintained them and gave them a few feature
- upgrades.
-
-
- Managing a system and a team proved to be the most difficult
- part of the experience for me, as I have always been a solo
- guy. But I do have a little bit of experience and exposure to
- how management is done effectively, so I knew where to start.
- In this age, our tools can do half the job for us, so we need
- to know the strengths and limitations of the tools we are
- using. I was using Microsoft Teams for meetings, notes, files
- and updates (
-
- example
-
- ). Trello was my choice for managing tasks. I made use of
- columns, checklists, labels, assignments, and integrations to
- customize the Trello board to our needs (
-
- example
-
- ).
-
-
- The day of event was a tough one, as my work started very
- early in the morning, so I had to skip breakfast. After
- getting done with my day-of chores like setting up the live
- site, making sure everyone is able to check in, and everything
- is running smoothly, I finally got a little time to grab a
- bite and a coffee. The rest of the day was all about talking
- to attendees on our Discord, helping participants with
- projects, and making new connections. We had over 230
- participants from 11 countries, in addition to representatives
- from sponsor companies, mentors from the industry, and
- qualified judges. A bunch of mini-events were hosted for the
- attendees to take a break and socialize.
-
-
- This experience helped me develop myself in not just one or
- two, but all of the 5 UHP competencies. Additionally, the
- systems I built as a part of this experience are not mere
- hobby projects, but industry-grade software that is deployed
- in the cloud and is expected to handle hundreds of users. I
- can put this on my resume and showcase to potential employers.
- I am sure they will be interested in someone who can manage a
- system of this scale, as well as the soft skills that come
- with leading a team and organizing an event.
-
-
-
-
-
-
-)
-
-export default RevolutionUCPage
diff --git a/src/pages/showcase/experiences/roundtable.js b/src/pages/showcase/experiences/roundtable.js
deleted file mode 100644
index f33374b..0000000
--- a/src/pages/showcase/experiences/roundtable.js
+++ /dev/null
@@ -1,152 +0,0 @@
-import React from "react"
-import Layout from "../../../components/layout"
-
-const LeadershapePage = ({ location }) => (
-
-
-
-
-
-
-
-
- Jan 2022
-
- Student Leader Round Table
-
-
-
- As someone who is passionate about leadership and student
- organizations on campus, the Student Leader Round Table was
- the perfect opportunity for me to reflect on my experiences as
- a leader, share my own learnings and wisdom, as well as learn
- from other leaders in the university. Over the spring
- semester, the round table (or the student leader illuminati as
- I like to call it) met every other week and discussed a
- specific issue related to running a student organization. Each
- of us have had different approaches to the issues, so it was
- great to hear how the specific situation of an organization
- affects our approach of thinking about or solving an issue.
-
-
Session 0: Jan 19
-
- We met for the very first time in January to get to know each
- other and plan out the semester. We broke out into 2 groups,
- and each group had to come up with 5 topics to talk about
- throughout the semester.
- This session was probably the first time I have interacted
- with other student leaders to talk about common issues in an
- abstract manner.
-
-
Session 1: Feb 2
-
- The first session topic was{" "}
- Hybrid Meetings and Events.
- This is a relatively new issue for student organizations, ever
- since COVID restrictions have relaxed. After the rise of
- virtual meetings, organizations have discovered that the
- convenience of attending an event from home is going to
- forever change how we connect with our community. At the same
- time, there are people who, after living in isolation for over
- a year, really want to get back to face to face interaction.
- So hybrid meetings seems like the best way to cater to every
- audience.
- However, since hybrid meetings have never been properly
- explored by anyone, let alone by student organizations. So we
- discussed motivations, ideas, challenges, etc. It was a great
- conversation that I learn a lot from, and hopefully it will
- allow me to improve the hybrid meeting experience for my
- organizations.
-
-
Session 2: Feb 16
-
- The topic of our second session was{" "}
- Recruitment.
- This is one of the most elementary issues that every
- organization has to deal with. To stay relevant in the
- community and continue to achieve our goals, we have to spread
- awareness about our organizations' existence and attract
- people who can contribute to the organization.
- The recruitment process has many different aspects, including
- (but not limited to) identifying the target audience, figuring
- out incentives and benefits, and formulating attractive
- marketing material.
- To exercise formulating elevator pitches, we did the classic
- "Sell me X in a minute" activity. The presenters chose a few
- random images, and a volunteer had to come up with an elevator
- pitch on the spot. This was a great exercise for me
- personally, because I am often put in a situation where I am
- in a conversation and I want to tell them about my
- organization and what we do and why they should get involved.
-
-
Session 3: March 2
-
- In our third meeting, we talked about{" "}
- Executive Transition.
- Executive transition is an issue that usually lives in the
- blind spot of organization leaders. If we are not conscious
- about how we are handling transitions to the new executives at
- the end of our tenures, the organization can potentially go
- through a very difficult start and change into something else.{" "}
-
- This mostly happens because every leader needs to have certain
- frameworks and processes to run an organization. If those
- frameworks are not handed to us by a previous leader, we will
- come up with our own, which will take a lot of time to figure
- out, and will be likely very different from what the previous
- leaders used.
- We talked about the timeline of executive transition -
- candidacy, elections, transitions and first meeting. For
- candidacy and elections, we discussed what the candidates and
- the voters need to know before the elections. We also
- discussed how different organizations can have different
- approaches to how the new executive is selected, or how
- elections are executed.
- Every executive role has some essential core aspects, which
- need to be clearly documented and shared with the newly
- elected members. The easiest way to achieve that is to write
- it in a document and hold a transition meeting between the
- outgoing and incoming member.
-
-
Session 4: March 23
-
- This is the meeting that I presented in along with a partner,
- and it was about Inter-Org Collab.
I am
- very passionate about collaborations. I think collabs are a
- great way to build up relationships, expand outreach, and get
- access to more resources and do bigger projects. So that is
- what we started the discussion with - benefits of
- collaborating.
I had a lot of experiences and anecdotes
- to share for this presentation, because almost all of ITSA
- events have been a collab of some sort. They also helped me
- come up with topics to talk about, as well as to make my
- point. For example, I brought up the idea of the ITSA
- partnering with a local cafe and coffee roaster to increase
- awareness about specialty coffee.
- This specific meeting was also a little disappointing in some
- ways. It finished in less than 40 minutes, where as all the
- previous ones went on until the 50-55 minute mark. While some
- of that can definitely be attributed to low attendance and
- participation by the other members of the roundtable, I
- definitely felt like the content we came up with in the
- meeting was not enough. What makes it worse is that my partner
- warned me of this, but for some reason I was confident that
- the content we have in the slides was more than enough. In
- hindsight looking at the slides of the other meetings, I
- definitely under-prepared.
- However, even though I did not get much feedback from the
- other members on this topic, just the preparation had an
- immense impact on how I think about collaborations, and it
- helped me organize a lot of my random thoughts and opinions
- into a clear framework, which I can document further.
-
-
-
-
-
-
-)
-
-export default LeadershapePage
diff --git a/src/pages/showcase/projects/index.tsx b/src/pages/showcase/projects/index.tsx
index 23aa92b..afe429f 100644
--- a/src/pages/showcase/projects/index.tsx
+++ b/src/pages/showcase/projects/index.tsx
@@ -3,9 +3,9 @@ import { graphql } from "gatsby"
import Layout from "../../../components/layout"
import { ProjectCard } from "../../../components/portfolio/project-card"
-import type { IProject } from '../../../data/showcase/projects/type'
-import type { IFeature } from '../../../data/tech/features/type'
-import type { ITool } from '../../../data/tech/tools/type'
+import type { IProject } from "../../../data/showcase/projects/type"
+import type { IFeature } from "../../../data/tech/features/type"
+import type { ITool } from "../../../data/tech/tools/type"
export const query = graphql`
query ProjectsQuery {
@@ -25,16 +25,18 @@ export const query = graphql`
}
featuresYaml {
features {
- name
id
+ name
+ description
color
bgColor
}
}
toolsYaml {
tools {
- name
id
+ name
+ description
devicon
color
bgColor
@@ -53,22 +55,28 @@ const ProjectsPage = ({ location, data }) => {
const features: IFeature[] = data.featuresYaml.features
const tools: ITool[] = data.toolsYaml.tools
- return
-
-
-
My Projects
- {projects.map((project, i) =>
-
- )}
-
+ return (
+
+
+
+
My Projects
+ {projects.map((project, i) => (
+
+ ))}
+
+ )
}
export default ProjectsPage
diff --git a/src/styles/global.css b/src/styles/global.css
index e97653f..da1083e 100644
--- a/src/styles/global.css
+++ b/src/styles/global.css
@@ -69,10 +69,20 @@ p {
.section-heading .section-heading-lower {
display: block;
- font-size: 3rem;
+ font-size: 2.5rem;
font-weight: 100;
}
+@media (min-width: 768px) {
+ .section-heading .section-heading-lower {
+ font-size: 2.8rem;
+ }
+}
+
+.experience-img {
+ max-height: 200px;
+}
+
.bg-faded {
background-color: rgba(255, 255, 255, 0.85);
}
@@ -203,7 +213,6 @@ p {
.showcase {
background: rgba(94, 56, 41, 0.85);
- padding: 50px 150px;
border-radius: 0.5rem;
width: 80%;
margin: auto;
@@ -292,3 +301,39 @@ p {
.project-page .project-image {
width: 100%;
}
+
+.blog-article .text-muted,
+.blog-article .article-excerpt {
+ font-size: 0.9rem;
+}
+
+.blog-article .article-image {
+ width: 100%;
+ filter: brightness(0.8);
+}
+
+@media (min-width: 992px) {
+ .featured-article-card {
+ height: 27rem;
+ }
+
+ .article-card {
+ height: 12.5rem;
+ }
+}
+
+.text-justify-p p {
+ text-align: justify;
+}
+
+.landing {
+ text-shadow: 0 0 5rem rgba(0, 0, 0, 1);
+}
+
+.landing h1 {
+ font-size: 5rem;
+}
+
+.landing p {
+ font-size: 1.5rem;
+}
diff --git a/src/tech/features/type.d.ts b/src/tech/features/type.d.ts
deleted file mode 100644
index cb90ea9..0000000
--- a/src/tech/features/type.d.ts
+++ /dev/null
@@ -1,7 +0,0 @@
-export interface Feature {
- id: string;
- name: string;
- color: string;
- bgColor: string;
- description: string;
-}
\ No newline at end of file
diff --git a/src/tech/tools/type.d.ts b/src/tech/tools/type.d.ts
deleted file mode 100644
index 26d0bd2..0000000
--- a/src/tech/tools/type.d.ts
+++ /dev/null
@@ -1,9 +0,0 @@
-export interface Tool {
- id: string;
- name: string;
- color: string;
- bgColor: string;
- description: string;
- iconPng?: string;
- devicon?: string;
-}
\ No newline at end of file
diff --git a/src/templates/article-page.tsx b/src/templates/article-page.tsx
new file mode 100644
index 0000000..ac49dcf
--- /dev/null
+++ b/src/templates/article-page.tsx
@@ -0,0 +1,70 @@
+import { GatsbyImage, getImage } from "gatsby-plugin-image"
+import React, { useEffect } from "react"
+import hljs from "highlight.js"
+import Layout from "../components/layout"
+import { TagBadge } from "../components/portfolio/tag-badge"
+import { IArticle, ITag } from "../data/blog/type"
+
+import "highlight.js/styles/base16/dracula.css"
+
+const ArticlePageTemplate = ({ pageContext }) => {
+ const path: string = pageContext.pagePath
+ const article: IArticle = pageContext.article
+ const allTags: ITag[] = pageContext.tags
+
+ const tags = allTags.filter(tag => article.frontmatter.tags?.includes(tag.id))
+ const __html = article.html
+
+ useEffect(() => {
+ // @ts-ignore
+ document.querySelectorAll("pre code").forEach(hljs.highlightBlock)
+ }, [])
+
+ return (
+
+
+
+
+
+
+ {article.timeToRead} minute read
+
+
+ {article.frontmatter.title}
+
+
+ {article.frontmatter.date}
+
+
+ {tags.map(tag => (
+
+ ))}
+
+ {article.frontmatter.image && (
+
+ )}
+
+
+
+ )
+}
+
+export default ArticlePageTemplate
diff --git a/src/templates/experience-page.tsx b/src/templates/experience-page.tsx
new file mode 100644
index 0000000..05387ed
--- /dev/null
+++ b/src/templates/experience-page.tsx
@@ -0,0 +1,50 @@
+import React from "react"
+import { GatsbyImage, getImage, getSrc } from "gatsby-plugin-image"
+import Layout from "../components/layout"
+
+import { IExperience } from "../data/showcase/experiences/type"
+
+const ExperiencePageTemplate = ({ pageContext }) => {
+ const path: string = pageContext.pagePath
+ const experience: IExperience = pageContext.experience
+
+ const __html = experience.page?.childMarkdownRemark.html
+ const image = experience.pageImage
+
+ return (
+ <>
+
+
+
+ {image && (
+
+ )}
+
+
+
+
+
+
+ {experience.date}
+
+
+ {experience.name}
+
+
+ {__html &&
}
+
+
+
+
+
+
+ )
+}
+
+export default ExperiencePageTemplate
diff --git a/src/templates/project-page.tsx b/src/templates/project-page.tsx
index 1fbaabb..ece98c7 100644
--- a/src/templates/project-page.tsx
+++ b/src/templates/project-page.tsx
@@ -10,14 +10,23 @@ import type { IProject } from "../data/showcase/projects/type"
import type { IFeature } from "../data/tech/features/type"
import type { ITool } from "../data/tech/tools/type"
-const ProjectPageTemplate = ({ pageContext, location }) => {
+const ProjectPageTemplate = ({ pageContext }) => {
+ const path: string = pageContext.pagePath
const project: IProject = pageContext.project
const features: IFeature[] = pageContext.features
const tools: ITool[] = pageContext.tools
+
const __html = project.page?.childMarkdownRemark.html
return (
-
+
{
-
+
{project.description}
@@ -39,7 +48,12 @@ const ProjectPageTemplate = ({ pageContext, location }) => {
- {__html &&
}
+ {__html && (
+
+ )}
diff --git a/static/images/blog/serverless/consistent-execution.png b/static/images/blog/serverless/consistent-execution.png
new file mode 100644
index 0000000..c7d8fca
Binary files /dev/null and b/static/images/blog/serverless/consistent-execution.png differ
diff --git a/static/images/blog/serverless/execution-time.png b/static/images/blog/serverless/execution-time.png
new file mode 100644
index 0000000..9156a9a
Binary files /dev/null and b/static/images/blog/serverless/execution-time.png differ
diff --git a/static/images/blog/serverless/serverless-deploy.png b/static/images/blog/serverless/serverless-deploy.png
new file mode 100644
index 0000000..3c37d99
Binary files /dev/null and b/static/images/blog/serverless/serverless-deploy.png differ
diff --git a/static/images/blog/serverless/traditional-deploy.png b/static/images/blog/serverless/traditional-deploy.png
new file mode 100644
index 0000000..bf75c13
Binary files /dev/null and b/static/images/blog/serverless/traditional-deploy.png differ
diff --git a/src/images/leadershape2.jpeg b/static/images/experiences/leadershape/leadershape-article.jpeg
similarity index 100%
rename from src/images/leadershape2.jpeg
rename to static/images/experiences/leadershape/leadershape-article.jpeg
diff --git a/src/images/revolutionuc2.png b/static/images/experiences/revolutionuc/architecture.png
similarity index 100%
rename from src/images/revolutionuc2.png
rename to static/images/experiences/revolutionuc/architecture.png
diff --git a/src/images/revolutionuc3.png b/static/images/experiences/revolutionuc/teams.png
similarity index 100%
rename from src/images/revolutionuc3.png
rename to static/images/experiences/revolutionuc/teams.png
diff --git a/src/images/revolutionuc4.png b/static/images/experiences/revolutionuc/trello.png
similarity index 100%
rename from src/images/revolutionuc4.png
rename to static/images/experiences/revolutionuc/trello.png
diff --git a/static/images/projects/hackathon/deployment.png b/static/images/projects/hackathon/deployment.png
new file mode 100644
index 0000000..a488132
Binary files /dev/null and b/static/images/projects/hackathon/deployment.png differ
diff --git a/static/hackathon-web.jpg b/static/images/projects/hackathon/web.jpg
similarity index 100%
rename from static/hackathon-web.jpg
rename to static/images/projects/hackathon/web.jpg
diff --git a/static/seo-images/blog/index.html b/static/seo-images/blog/index.html
new file mode 100644
index 0000000..e69de29
diff --git a/static/seo-images/experiences/index.html b/static/seo-images/experiences/index.html
new file mode 100644
index 0000000..e69de29
diff --git a/static/seo-images/projects/index.html b/static/seo-images/projects/index.html
new file mode 100644
index 0000000..e69de29
diff --git a/static/social-card.png b/static/social-card.png
new file mode 100644
index 0000000..57534b0
Binary files /dev/null and b/static/social-card.png differ