diff --git a/blog-posts/blog-post-1.md b/blog-posts/blog-post-1.md
new file mode 100644
index 0000000..c5d1b64
--- /dev/null
+++ b/blog-posts/blog-post-1.md
@@ -0,0 +1,81 @@
+# Blog Post 1
+
+Hi everyone! This is an update on the first two months of working on the GSOD-NumPy project, the "NumPy Contributor Comics".
+
+For the the project roadmap, check it out here.
+
+Aim of blog psot: Sharing methodology, aim, unusual, replicate similar projects
+
+## Setting up my Repo
+I've created a Github repository that contains all the artifacts for this project in the gsod-numpy Github repo. It's my effort to share non-code contribution on Github.
+Graphic designers and artists usually host their work platforms that developers and open-source folks don't frequent, such as Behance and Dribble.
+I've decided to meet where the NumPy community and comic's target audience gathers. I'm also familiar with Github, having used it for years before this project.
+
+Artefacts in the repo:
+- Concept art
+- Brainstorming documents
+-  Scripts
+- Community meeting notes
+- Annoucements to mailing list
+
+## Stages
+In the past 4 months, we have finished major stages. The stages are:
+- Brainstorming and Gathering Community Input
+- Outlining
+- Review #1
+- Writing Script, Thumbnailing
+
+### Brainstorming and Gathering community input
+Coming into the project, I already had some prototypes from last year. These were inspired by conversations in the NumPy Community meetings. This provided a strong starting point, since it's easier to with a scribble instead of a blank page. 
+
+I hosted brainstorming sessions in three community meetings in May 2023.
+- Community
+- Docs
+- Newcomers
+Each one links to the full meeting notes, if you're interested.
+
+### Jammin' together!
+I primarily used a Google Jamboard, a digital whiteboard. I wanted to encourage people to think in visual and non-linear ways. A digital whiteboard where anyone can leave comments, add and drag images around or even draw with their mouse was great for that.
+
+I haven't seen digital whiteboards used before in the NumPy space, but similar tools such as FigJam and Miro are used by UX/UI teams.
+
+In comparison, typing straight into the hack.md meeting notes felt a little stilted. That format reinforces the primacy of words over images, and I wanted to nudge it in the other direction. (If you're interested in reading some theory and unapacking of that, check out, Unflattening, a dissertion in the form of a comic book).
+
+Each meeting had a good amount of prep-work. I released annoucements to the NumPy mailing list withthe dates I would host the sessions and links to the Jamboard.
+
+I prepared the Jamboard beforehand. I didn't want to have only one slide with the prototype. Nor did I want it be too vague. Rather, I arranged it a comic pitch.
+
+### Hosting the session
+The beginning opens with the prototype and how it attempts o answer the reoccuring question of 'How do we increase the number and variety of contributions to maintain the long-term health of a project?'. The middle shifts to inspiration such as the Turing Way Community Handbook and The Manga Guide to Databases. All this is twirled up into the pitch of the NumPy Contributor Comics.
+
+The last two slides posed key questions and the rest blank to be filled with comments,
+
+By roughly following the agenda and watching the time, each session took a minimum of 20 minutes. I didn't want to call for a seperate meeting for these sessions, but rather slot into existing meetings and adjust from there. So the longest session was a full hour, at the NumPy Newcomers meeting.
+
+The biggest turnout was at the NumPy Community meeting with total of 9 people attending, higher than the usual of 4-6 people.
+
+### Scooping up different opinions
+By going to different community meetings, I was able to get scoop up different opinions. With Newcomers, there was a focus on non-linear pathways. At the Docs meeting, how the metaphor to explain contributon pathways may fall flat. A the Community meeting, the difficulty of quantifying the un-quantifable, especially in roles and expectations.
+
+In this way, I conducted infomal user testing. I tested how users responded to the comics pitch. But it also opened a broader conversation of how the NumPy community is moving and if we want to continue or change the contribution experience.
+
+It was great fun to doodle people's concerns, group ideas together by moving sticky notes, and compare people's experience in entering the NumPy space several years ago vs in the past few weeks.
+
+Alas, the very strengths of the Jamboard was also it's greatst downfall. As the Jamboard was not in a plain text format such as a Markdown document, it was archived as PDF in the repository. I also transcribed the major points back into text. Despite these extra steps, it was worthwhile for me introuce powerful and fun collaboration tool.
+
+### Outlining
+Take all the feedback, turn into something solid
+Concept Art
+Met with creator, artist, editor, Tony. Take a different perspective in mind
+Alternate betwen community needs and artisitic vision, skills.
+
+### Review #1
+Change direction
+
+### Writing Script, Thumbailing
+- Google Doc
+
+## Difficulty
+## Proud
+Not usual, expanding what doc look like
+however existing knowledge, comfortable in community. as community member receiving grant, familiarity to running start. Curious other visual skill people without this background do similar, share resources, more people.
\ No newline at end of file
diff --git a/reivew-1/numpy-community-2023-06-21.md b/review-1/numpy-community-2023-06-21.md
similarity index 100%
rename from reivew-1/numpy-community-2023-06-21.md
rename to review-1/numpy-community-2023-06-21.md
diff --git a/reivew-1/numpy-docs-2023-06-19.md b/review-1/numpy-docs-2023-06-19.md
similarity index 100%
rename from reivew-1/numpy-docs-2023-06-19.md
rename to review-1/numpy-docs-2023-06-19.md