DEV Community: Peter Bankole

I built GitCard, a visual portfolio for developers

Peter Bankole — Fri, 04 Sep 2026 04:20:29 +0000

I’ve been working on a side project called GitCard, and I’m finally at the point where I’d like other developers to try it.

The original idea was pretty simple:

Developers have GitHub, LinkedIn, resumes, and personal websites, but it can still be difficult to quickly show someone what you’ve actually built.

Designers have platforms like Behance where the work itself is front and center, so I started wondering what a more visual project showcase could look like for developers.

That idea turned into GitCard.

Right now, GitCard lets developers connect their GitHub account and build a profile around their projects.

You can showcase repositories, add project screenshots and descriptions, highlight the technologies you used, and create a profile you can share with other developers, recruiters, or people you meet.

I also experimented with something a little different: a wallet-sized physical card with a QR code that links back to your GitCard profile.

The thought was that at a meetup, hackathon, conference, career fair, or even just a random conversation, someone could scan your card and immediately see the projects you’ve worked on.

I’m still figuring out whether that part is genuinely useful or just something I personally think is cool.

Longer term, I’m interested in exploring whether GitCard could become more community-driven — somewhere developers can discover interesting projects, find other people working with similar technologies, collaborate, and learn from what others are building.

But I don’t want to get too far ahead of myself.

Right now, I mostly want to find out whether the basic product is useful.

If anyone here is willing to try it, I’d really appreciate feedback on a few things:

Does the profile make a developer’s work easier to understand than just looking through GitHub?
Which parts of the profile feel useful, and which feel unnecessary?
Would you actually share a GitCard profile with someone?
Does the physical QR card idea make sense to you?
What would make you want to return after creating your profile?
Is there something you expected the product to do that it currently doesn’t?

The site is:

https://gitcard.io

There are still bugs and rough edges, so criticism is completely welcome. I’d rather find out what developers actually want than keep adding features based only on my own assumptions.

I’m also happy to answer questions about how I built it or why I made certain product decisions.

Gitcard Weekly Challenge #1: Build Something That Solves an Everyday Problem

Peter Bankole — Mon, 17 Aug 2026 23:25:11 +0000

Developers, builders, and makers — welcome to the first Gitcard Weekly Challenge.

GitCard: https://gitcard.io

This week's challenge is simple:

🎯 The Challenge

Build a small application, tool, website, API, automation, or AI project that solves an annoying everyday problem.

It can be something that saves time, automates a repetitive task, helps people make better decisions, improves productivity, or simply makes life easier.

Your project does not need to be huge.

A small project that solves one problem really well can win.

Examples

You could build:

An AI email organizer
A smart grocery-list generator
A browser productivity tool
A meeting summarizer
A personal finance utility
A developer productivity tool
A scheduling assistant
A simple accessibility tool
An automation that eliminates a repetitive task
Something completely different

Creativity is encouraged.

📅 Challenge Period

Starts: August 17, 2026
Submission Deadline: August 23, 2026 at 11:59 PM Pacific Time

🏆 Prize

The winning project will receive a free Gitcard and will be featured by Gitcard.

This is the first of what I hope becomes a recurring series of weekly developer challenges.

How to Enter

1. Build Your Project

Use any programming language, framework, platform, API, or technology you want.

AI-assisted development is allowed.

Your project should be functional enough for someone else to understand what you built and why it is useful.

2. Publish Your Code on GitHub

Your project must have a GitHub repository.

Include a README explaining:

What the project does
The problem it solves
How to run or test it
Technologies used
Screenshots or demo link, if available

3. Create Your Gitcard Profile (gitcard.io)

Go to Gitcard.io and create your developer profile.

4. Add the Project to Your Gitcard

Add your challenge project to your Gitcard profile and include the GitHub repository.

Your Gitcard project should clearly explain what you built.

5. Identify Your Submission

To make sure I can find your entry, include:

Dev.to Challenge #1 — [date project was posted on Gitcard]

For example:

Dev.to Challenge #1 — August 21, 2026

Put this in one of these two places:

Option A: Comment on this DEV.to post with your Gitcard project/profile link.

Option B: Add the phrase above to your project's description on Gitcard.io.

You can do both if you'd like.

This lets me identify your challenge submission and contact you about the result.

✅ Submission Checklist

Before the deadline, make sure you have:

A working project
A GitHub repository
A Gitcard.io profile
Your project added to your Gitcard
Your GitHub repository connected to the project
Dev.to Challenge #1 — [date] included in your DEV.to comment or Gitcard project description

🔍 How Projects Will Be Judged

Projects will be evaluated primarily on:

1. Usefulness
Does it solve a real problem?

2. Execution
Does the project actually work?

3. Creativity
Is the solution interesting or different?

4. Simplicity
Does it solve the problem without unnecessary complexity?

5. Presentation
Can someone quickly understand what you built from your GitHub repository and Gitcard project?

You don't need the most complicated application to win.

A clever, polished solution to a small problem can beat a huge unfinished project.

Who Can Participate?

Everyone.

Beginners, students, professional developers, indie hackers, AI developers, vibe coders, and experienced engineers are all welcome.

You may participate individually or as a team.

One Rule Above Everything Else

Ship something.

Don't spend the entire week trying to build the perfect startup.

Find a problem.

Build the solution.

Push it to GitHub.

Put it on your Gitcard.

Then show us what you made.

Good luck. 🚀

Gitcard Weekly Challenge #1 starts now.

Why GitHub Alone Isn't Enough to Showcase What You've Built as a Developer

Peter Bankole — Thu, 16 Jul 2026 05:50:36 +0000

As developers, we spend countless hours building projects, contributing to open source, fixing bugs, and learning new technologies. Yet when it's time to apply for a job, collaborate on a project, or attract freelance clients, we often end up sharing a long list of links:

GitHub
Portfolio website
LinkedIn
Resume
Individual project demos

I kept wondering why there wasn't a simpler way to showcase everything in one place.

That question led me to build GitCard.

GitCard is a platform where developers can create a single profile that brings together their GitHub activity, projects, skills, experience, and portfolio. Beyond showcasing your work, the vision is to help developers discover collaborators, connect with other builders, and make it easier for recruiters and clients to find talented developers.

The current version is still in beta, and I'm looking for honest feedback from the developer community before continuing development.

If you're interested, I'd really appreciate your thoughts.

https://gitcard.io

Some questions I'd love your feedback on:

Does this solve a problem you've experienced?
What would make you create a GitCard?
What feature would make it part of your developer workflow?

Constructive criticism is more valuable than compliments at this stage. Thanks for taking a look!