DEV Community: Christoffer Niska

Building CodeHub: Crafting the Technology Stack

Christoffer Niska — Sun, 04 Feb 2024 19:50:55 +0000

As we continue our journey in building CodeHub, we'll now shift our focus to the technology stack that powers our platform. In case you missed the beginning of our story, you can catch up on the origins of CodeHub to understand how it all began.

Choosing the right technologies

Given our extensive experience with TypeScript, React, and Next.js, choosing these technologies was an obvious decision. We were eager to launch our service as quickly as possible.

For server-to-client communication, we opted for GraphQL due to its strong typing, self-documenting capabilities, and the availability of numerous helpful libraries. We selected Apollo as our GraphQL server and client. My prior experience with Apollo, along with its built-in caching features and robust developer tools, influenced our choice.

Recognizing the relational nature of our data, we embraced PostgreSQL for its rich feature set. As our database client, we settled on Prisma, primarily for its schema prototyping capabilities with db push.

Next, we needed to decide on a user interface library. Our requirements were clear: a library with a rich collection of components. After brief research, we settled on Chakra UI for its simplicity, modularity, accessibility, and extensive component library. Its use of Styled System, with which I was familiar, further solidified our choice.

Finally, we had to select a platform for deployment. Having previously used Vercel for deploying Next.js projects, it was the natural choice. We also decided to explore Vercel's new offerings, including serverless PostgreSQL and fast object storage.

What's next?

In the upcoming part of this series, I'll share our journey in selecting the code editor for CodeHub. Trust me, it wasn't an easy task to find a solution that met all our needs.

Stay tuned for more.

Building CodeHub: Our Journey Begins

Christoffer Niska — Wed, 22 Nov 2023 13:16:43 +0000

This is the first part of our journey in creating CodeHub.

What is CodeHub?

CodeHub is an online community for developers, focused on sharing code snippets. You can create an account, vote on snippets, mark them as favorites for future reference, leave comments, and easily share them on social media.

But wait, doesn't such a service already exist?

Not exactly. While there are services with similar features, let's explore what sets CodeHub apart. GitHub Gist allows users to share files, but it doesn't foster a sense of community. Stack Overflow is a well-known developer community, but it primarily serves as a platform for asking and answering development-related questions. Additionally, services like CodePen offer an online code editing environment that's popular among front-end developers for creating and sharing HTML, CSS, and JavaScript snippets.

How it all began

Our story starts on a casual Friday evening in Helsinki last August, as we enjoyed a few drinks with friends and former colleagues after work. Conversation meandered through various topics until someone suggested how great it would be to have a platform where developers could easily exchange useful code snippets.

The idea quickly captured our imagination, and one of my friends, who was currently between projects, proposed that we should embark on creating this platform. To our amusement, the others initially thought we were joking. Little did they know that we had already committed to making this vision a reality. The very next day, we set the wheels in motion to create CodeHub.

The vision

At this point, we had a clear vision in our heads of what the service would look like. We knew that we wanted to keep the features to a minimum, at least in the beginning, and gather feedback from users before adding additional features.

The code editor needed to be simple; it didn't have to be a full-fledged editor, but it had to include syntax highlighting and serve its primary purpose, which was to enable users to modify their snippets without the need to copy them to an external editor and then back to the service.

I also recognized that the ability to generate preview images of the snippets was an essential feature for our service. This capability would enable us to provide an appealing preview of the code, complete with syntax highlighting, when a user shared a link to a snippet on social media.

What's next?

Our journey is just beginning, and in the next part, we'll delve into the technical decisions that powered the development of CodeHub. Join us as we explore the technology stack, tools, and building blocks that bring our community for developers to life.

Stay tuned for more.

Hello World!

Christoffer Niska — Wed, 18 Oct 2023 17:07:28 +0000

I'm here to test whether Dev Community's post feature is sufficient for my current needs.