+ +_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.
+
+
+
+
+The difference lies in how much computation you are using. With a virtual server, you are paying for every second the server is alive, regardless of whether your code is running in it. In comparison, a serverless function will only cost you the computation of the function itself.
+
+It's optimized for elasticity, so it's only feasible in scenarios where you need elasticity. If you have inconsistent or unpredictable usage, serverless is a nice fire-and-forget deployment method where you app will scale up and down automatically as needed.
+
+
+ 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. +
++ 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 +
+
+
+
+
+
-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](/leadershape-article.jpeg). +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. diff --git a/src/data/showcase/experiences/images/leadershape-group.jpg b/src/data/showcase/experiences/leadershape/banner.jpg similarity index 100% rename from src/data/showcase/experiences/images/leadershape-group.jpg rename to src/data/showcase/experiences/leadershape/banner.jpg diff --git a/src/data/showcase/experiences/images/leadershape.png b/src/data/showcase/experiences/leadershape/logo.png similarity index 100% rename from src/data/showcase/experiences/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/images/roundtable.png b/src/data/showcase/experiences/roundtable/logo.png similarity index 100% rename from src/images/roundtable.png rename to src/data/showcase/experiences/roundtable/logo.png diff --git a/src/data/showcase/projects/hackathon.md b/src/data/showcase/projects/hackathon.md index 6d8ee1c..d6fbc72 100644 --- a/src/data/showcase/projects/hackathon.md +++ b/src/data/showcase/projects/hackathon.md @@ -18,13 +18,13 @@ 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. -
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
diff --git a/src/pages/blog/index.tsx b/src/pages/blog/index.tsx
index 64f313a..b1f40fd 100644
--- a/src/pages/blog/index.tsx
+++ b/src/pages/blog/index.tsx
@@ -41,8 +41,8 @@ export const query = graphql`
`
const ArticleCard: FC<
- { article: IArticle; allTags: ITag[] } & HTMLAttributes
- Twitter
- Facebook
- Instagram
+
+ Twitter
+ {" "}
+
+
+ Facebook
+ {" "}
+
+
+ Instagram
+
-
- Welcome to my site!
-
+
+
+
+
+ 
+
+
+
+ Welcome!
++ I am a software developer and an aspiring software architect and + content creator. +
+ +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
{
path={path}
image={
article.frontmatter.image
- ? `/images/blog/${article.frontmatter.id}.png`
+ ? `/seo-images/blog/${article.frontmatter.id}.png`
: undefined
}
>
diff --git a/src/templates/experience-page.tsx b/src/templates/experience-page.tsx
index f3b8466..05387ed 100644
--- a/src/templates/experience-page.tsx
+++ b/src/templates/experience-page.tsx
@@ -9,22 +9,20 @@ const ExperiencePageTemplate = ({ pageContext }) => {
const experience: IExperience = pageContext.experience
const __html = experience.page?.childMarkdownRemark.html
- const image = experience.pageImage ? getSrc(experience.pageImage) : ``
+ const image = experience.pageImage
return (
<>
-
diff --git a/src/templates/project-page.tsx b/src/templates/project-page.tsx
index fa23ebc..ece98c7 100644
--- a/src/templates/project-page.tsx
+++ b/src/templates/project-page.tsx
@@ -23,7 +23,9 @@ const ProjectPageTemplate = ({ pageContext }) => {
title={project.name}
description={project.description}
path={path}
- image={project.image ? `/images/projects/${project.id}.png` : undefined}
+ image={
+ project.image ? `/seo-images/projects/${project.id}.png` : undefined
+ }
>
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/static/leadershape-article.jpeg b/static/images/experiences/leadershape/leadershape-article.jpeg
similarity index 100%
rename from static/leadershape-article.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/hackathon-deployment.png b/static/images/projects/hackathon/deployment.png
similarity index 100%
rename from static/hackathon-deployment.png
rename to static/images/projects/hackathon/deployment.png
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/images/blog/index.html b/static/seo-images/blog/index.html
similarity index 100%
rename from static/images/blog/index.html
rename to static/seo-images/blog/index.html
diff --git a/static/images/projects/index.html b/static/seo-images/experiences/index.html
similarity index 100%
rename from static/images/projects/index.html
rename to static/seo-images/experiences/index.html
diff --git a/static/seo-images/projects/index.html b/static/seo-images/projects/index.html
new file mode 100644
index 0000000..e69de29