DEV Community: Manoj Kumar

I got tired of rebuilding client logo sections, so I made a tiny widget instead

Manoj Kumar — Wed, 11 Feb 2026 00:43:07 +0000

The background story

Every time I shipped a new website or side project, I found myself rebuilding the same thing again:

A logo section.

Grid? Scroll? Mobile?
New logo? Edit CSS again.
Different site? Repeat the whole process.

It wasn’t hard - just repetitive and surprisingly fragile.

So I built Client Logo Wall: a small, embeddable widget that lets you upload logos once, manage them from a dashboard, and drop them into any site with a single line of HTML.

What it does (and intentionally doesn’t)

Client Logo Wall is super simple to use:

Upload logos from a dashboard
Choose static or auto-scroll layout
Embed anywhere (WordPress, Shopify, Ghost, Webflow, plain HTML)
No frontend framework assumptions
No heavy JS or layout overrides

It’s not a CMS.
It’s not a page builder.
It’s just a reusable logo wall that doesn’t break.

Memories

I originally tried to build this back in 2023 using freelance coders because I didn't have the coding knowledge, but I abandoned it. Studied coding at a bootcamp (2023), took a break (2024), came back with some coding passion (2025) and after gaining more full-stack experience through my personal projects, I came back (2026) and rebuilt it properly - with performance, simplicity, and embeddability as the main goals.

Technical bits (for the curious)

MERN stack (Node, Express, MongoDB, React)
Widget rendered server-side and embedded via iframe
Stripe subscriptions with a free trial
Strict upload size limits to protect page performance
Security hardening (rate limiting, webhook verification, input sanitization)

Nothing flashy - just solid, predictable engineering.

Who it’s for

Indie hackers
Freelancers
Small SaaS founders
website developers/designers/builders
Anyone tired of tweaking logo layouts manually, anyone with a website

That's the story! :)

👉 Live demo & docs: https://clientlogowall.com

I’d genuinely love feedback:

Does this solve a real annoyance for you?
What would you expect from a tool like this?
Is this something you’d build differently?

Sometimes the best tools are the ones that quietly disappear after you embed them.

73. Built and launched: Share Your Kofi

Manoj Kumar — Sat, 26 Apr 2025 06:53:06 +0000

Introducing Share Your Kofi - Discover and Support Ko-fi Creators

What is Share Your Kofi?

Share Your Kofi is a directory for discovering amazing Ko-fi creators.

It allows creators to share their pages, and lets fans recommend their favourite creators - making it easier for everyone to find and support each other on Ko-fi.

Why I Built This Project

As a big fan of Ko-fi myself, I found it to be a fantastic platform - visually appealing, simple to use, and offering all the e-commerce features a creator could want.

However, I noticed that discovering other creators on Ko-fi wasn't easy unless you stumbled upon them through social media or random suggestions.

That's when the idea hit me:

"I love coding, I love Ko-fi and the Ko-fi creator community - why not build something to bring creators together?"

So I spent a weekend building Share Your Kofi - and I'm excited to share it with you!

Features of Share Your Kofi

Submit Your Ko-fi Page

If you're a creator, you can easily submit your Ko-fi page along with a short description and optional profile picture.
Recommend a Creator

Fans can recommend their favorite Ko-fi creators by simply submitting a Ko-fi link - no account needed.
Like and View Tracking

Visitors can "like" creators they enjoy, and each Ko-fi page shows live click and view stats.
Ko-fi Donation Widget

A floating donation button lets visitors support the site itself if they wish.
Mobile Friendly

The site is fully responsive, making it easy to browse and submit from any device.
SEO Optimized

Share Your Kofi includes full meta and OpenGraph optimization for better social sharing previews and discoverability.
About Section

Learn about why the project was built and the vision behind it.

How It Was Built

Frontend: React (hosted on Netlify)
Backend: Node.js, Express (hosted on Render)
Database: MongoDB Atlas
Other Integrations: Google Analytics, Ko-fi floating widget, OpenGraph SEO setup

Final Thoughts

I'm really excited to launch Share Your Kofi and contribute something positive to the creator community.

I hope it becomes a useful, simple space for Ko-fi fans and creators to find and support each other.

If you're a creator, feel free to submit your Ko-fi page!

If you're a fan, recommend someone awesome!

And if you enjoy the site, there's even a little Ko-fi button floating on the page where you can support the project. ☕💛

Thanks for checking it out!

Manoj

72. Built a crypto tracker over the Easter weekend

Manoj Kumar — Sun, 20 Apr 2025 11:18:35 +0000

Crypto investors often find themself asking:

“If my coin hits 2x, 5x, or 10x... how much would I make?”

And most people keep turning to spreadsheets or scribbled notes. 😅

So I built something better.

🚀 Coin Exit Tracker

(coinexittracker.com)

A simple web app to help crypto holders visualise profits across 1x to 25x exit points.

You just enter:

The coin you hold
Your average purchase price
Number of coins
Currency of choice (USD, AUD, EUR, etc.)

It fetches live prices via CoinGecko and displays:

🎯 Target price per multiplier
💰 Total value
📈 Profit and Profit %
🟩 Progress bars showing how close you are to your goals

All in one clean, responsive interface. No logins. No tracking.

Also implemented a Custom Sell Calculator that calculates how much you'd gain (or lose) if you sold your coins right now. It instantly shows:

Live price
Total sale amount
Multiplier achieved
✅ Profit or ❌ Loss

🛠️ Tech Stack

Frontend: React + React Router
Backend: Node.js + Express (deployed on Render)
API: Live pricing via CoinGecko
Hosting: Netlify (frontend) & Render (backend)
Styling: Custom CSS with responsive handling

💡 Why I Built It

The idea came out of nowhere while reading investors' posts and comments. So, I spent the Easter weekend (2025) building the whole thing. Turns out - this was one of the most satisfying weekend projects I’ve built.

🙌 Please check it out and let me know your thoughts, ideas and suggestions.

Thanks for reading, and happy building 💻🚀

71. Assignment 3 submitted (Day 69)

Manoj Kumar — Sun, 24 Dec 2023 12:40:26 +0000

I finished my assignment just in time for Christmas! For two weeks, I worked on making a travel checklist app using Python. This app lets you add, see, delete, and mark items as done. It’s pretty easy to use, but making it wasn’t easy at all.

Right before I had to submit it, I found a problem. Something was missing in the code. Fixing it took me an extra hour and a half. Luckily, my tutor saved the day! Even though it was Christmas Eve and he was traveling, he checked our school's chat and helped me out. The fix was simple—just moving one line of code up a bit. It's crazy how such a tiny thing caused so much trouble!

This whole experience made me realize that coding is more about thinking logically than doing math. It’s not just about numbers; it’s about making sense of things. So now, my goal for the holidays is to get better at this logical thinking in coding. I want to learn Python, HTML, and CSS really well, and I'm going to work on it every day during the holidays. It’s my way of celebrating the season—learning something new and getting better at it!

Merry Christmas everyone!

70. Assignment completed not submitted (Day 68)

Manoj Kumar — Sat, 23 Dec 2023 12:43:18 +0000

I've done it!

Finished my assignment. That was a marathon effort today! This is what I achieved:

Finished a Readme file
Recorded a video walk-thru of my Python app
Created a PowerPoint presentation
Updated a previous code block to include some Error Handling (tough one!)
Cleaned up grammar and typos in the app and documentation.

I began the journey at 10 AM this morning and finished exactly 11:30 PM, taking only a total of 3 hours break.

Moral of the story: There's always a frantic pace and very high productivity when one is close to the deadline!

I haven't submitted the assignment yet and will do so tomorrow once I run my eyes over everything. Let's say, I submit by 11:30 AM tomorrow. Once that is done, I am FREE to roam the streets of Sydney and enjoy my holiday season :)

69. Not sticking to my plan (Day 67)

Manoj Kumar — Fri, 22 Dec 2023 12:43:34 +0000

I could've achieved more today with my assignment but then these came along:

Catching up on world news and social media (1 hour), A long fitness session (2 hours), grocery shopping (30 mins), new suitcase purchase (30 mins), travel back home (15 mins), dinner (45 mins), and finally my evening meditation (30 mins). Total time spent = about 6 hrs.

So, I managed to squeeze in only about 2 hours of work on my assignment. I focused primarily on my PowerPoint presentation - taking screenshots of my code and explaining it on the slides. I have another 2-3 slides pending and I am done with that!

Tomorrow, I MUST complete the following:

The Presentation: 1 hour
The Video Walk-through: 2 hours
The QA test document: 1 hour
Readme.md file cleanup: 1 hour
2 Test cases: 1 hour
Final run-through of everything: 1 hour

That's 7 hours of work! That's my goal.

68. Sticking to the plan(Day 66)

Manoj Kumar — Thu, 21 Dec 2023 12:45:26 +0000

Today, I kept going with my assignment that's due on Sunday. I focused on my Readme.md file and the Powerpoint presentation, which need a bunch of writing and screenshots. I'm aiming to wrap it all up tomorrow, so I'll have two extra days just in case. That'd be perfect. Worst case, I'll finish it all on Saturday.

One big lesson I've picked up from these assignments is how crucial planning is — doing it early and sticking to it. Here's what I've learned about planning:

Make a big list of everything you need to do.
Sort it out into a Kanban board with four sections (to-do, in progress, completed, and abandoned for things you don't need anymore).
Give each task a start and end date.
Break down every task into smaller steps on the Kanban board.
Also, schedule a specific time each day to work on the assignment.
Try to finish a whole day before it's due.
Make sure your days aren't just about work — include stuff that matters to you, like exercising, cooking, music, chilling in the park, TV time, hanging out with family, or whatever makes you happy. Balance is key!

That's it from me. More tomorrow, I hope.

67. Nearing the assignment 3 finish line (Day 65)

Manoj Kumar — Wed, 20 Dec 2023 12:23:12 +0000

Today, I received my Assignment 2 marks - 94%! I am happy. I lost marks on the written theoretical component - I think I wasn't detailed enough. Lessons learned!

Hope my assignment 3 (due Sunday) fares well also. I am mentally preparing to put in everything over the next 3.5 days - hard work, fewer distractions, and marathon sessions at the coding desk! If I can submit the assignment on Sunday morning, that will be a great result.

My remaining work on the assignment is as follows:

Clean up code
Make some final GitHub commits
Commence PowerPoint presentation
Commence video presentation
Clean up the Readme file

Doesn't look like a lot of work but trust me it can easily end up being one!

66. Working on the testing doc (Day 64)

Manoj Kumar — Tue, 19 Dec 2023 11:49:36 +0000

Today, I dedicated some time to working on Assignment 3. Although I intended to invest more effort, I found myself distracted by various other tasks.

Specifically, I focused on two key areas:

Fine-tuning my Bash Script.
Drafting a testing document aimed at comprehensively capturing the functionality of all aspects of the application. While my initial goal was to complete this today, I've had to reschedule it for Thursday due to prior work commitments tomorrow. This is what my testing document looks like:

Reflecting on my overall sentiment regarding the assignment:

I find satisfaction in the completion and smooth functionality of my application.

However, I do harbor a degree of anxiety regarding the assignment rubric's criteria. I'm uncertain if I've covered all the necessary aspects within the given timeframe. Yet, I believe I've addressed the majority of the requirements.

Comparatively, I feel my application might be less complex than those attempted by my peers. Nevertheless, I acknowledge its current state and accept that it's the best representation of my work. I remain curious about the outcome and how it will be received.

In summary, that wraps up today's progress on Tuesday's tasks. Looking forward to the upcoming challenges and the finalization of this assignment.

65. Working on the Bash Script file (Day 63)

Manoj Kumar — Mon, 18 Dec 2023 12:17:57 +0000

Today, I spent a bit of time fine-tuning my Bash Script.

A Bash Script is a file that contains a series of commands. In my assignment project, I am using it to run certain commands automatically which otherwise I would have to manually type in the Terminal every time I have to execute my app. This will help another user who plans to execute my app as well.

This is what I did:

I started a new file, "run.sh" in my existing Python project. Here, I have the following commands inserted:

#!/bin/bash

# 1. checks if Python is installed on the system or not
python3 --version

# 2. check if venv (virtual environment) exists or not
if [ -d ".venv" ]; then
    echo ".venv - virtual environment present"
else
    python -m venv .venv
    echo ".venv - virtual environment created"
fi

source .venv/bin/activate
pip3 install colored
python3 main-app.py

#!/bin/bash - The Bash Script file begins with this command first. You can read about what it is and why it is used in this article here: Bash script

The next command (1) is checking the user's Python version and letting them of the same. If the user doesn't have Python, it will display a message for the user to install one to run this app.

The 2nd command checks if the app has a virtual environment to execute certain functions of the app. If there is no .venv, it will create a new one and if there is one existing, it will activate it.

pip3 install colored is an external package I installed to give my fonts in the Terminal some colors! Otherwise, it's the usual black text on a white background, or vice versa. You can find the package here: Colored

And finally, python3 main-app.py which is where all the python codes are, will be executed automatically when I run this Bash Script file.

This is how you run the Bash Script file: In the Terminal, action this command - ./run.sh

That's it for today. Planning to put in more effort tomorrow!

64. Working through the Readme doc for assignment (Day 62)

Manoj Kumar — Sun, 17 Dec 2023 12:45:59 +0000

A gloomy Sunday outside, and I've been working on my assignment 3 today as well. I am not lying but I just wanted to unwind completely, and found myself distracted many times throughout the day. I just wanted to daydream. This is what happens when it's end-of-year and the holiday season is here.

Anyway, today I worked on:

Removing some files I don't need from my GitHub repository
Adding some font styling to show up on the terminal
A lot of documentation work on the Readme

Although my checklist app is super simple, the documentation required for it is so large! The educators want us to include so much information on everything - functions, variables, loops, conditions, tests, managing the Kanban board, screenshots, flowcharts, and many other things!

I've got another 7 days remaining before the deadline, and hopefully, I can finish everything by then.

Time: 11:42 PM. Time to rest.

63. Working on my Python app assignment (Day 61)

Manoj Kumar — Sat, 16 Dec 2023 12:36:23 +0000

Another H.O.T Sydney Saturday was spent on my assignment and drinking lots of water!

This is what I achieved today:

Completed the full basic functionalities of my checklist terminal app. It can now accept new entries, delete new entries, mark past entries as complete, view all entries, and exit the menu.
Installed an external package for applying colors to my menu items (https://pypi.org/project/colored/).
Created an executable Batch Script file, so that anyone can download my repository and execute the program.
Consistent commits and push to GitHub.
Keeping track of my work on a Kanban board.

I thought I was mostly done as far as my program is concerned, but I have run into some errors now with the color package. When I run it outside of the executable file and the virtual environment, I get a "Module Not Found" error. Looks like I may have to install the color package again because it seems to have been deleted when I deleted the virtual environment before.

Anyway, I will work on this tomorrow I think because it's 11:30 PM now, and I am so sleepy!