Forem: Partho Protim

I Built the Best Free Portfolio Builder

Partho Protim — Wed, 13 May 2026 06:23:11 +0000

I kept meeting developers who were getting passed over for jobs they were clearly qualified for. Strong GitHub profiles. Real shipped projects. Solid technical skills. And still, weeks of silence after every application.

The pattern was always the same. Their GitHub was a graveyard of repos with no context. Their LinkedIn said "Full Stack Developer" and listed the same five technologies as everyone else. Non-technical recruiters could not tell their work apart from a hundred other candidates with similar profiles. So I built a free portfolio website builder designed specifically for this problem, and this post is the long explanation of why and how.

The portfolio looks like:

If you are searching for the best free portfolio builder, an online portfolio builder that does not lock features behind a trial, or a serious portfolio builder for developers who want their work to actually speak for itself, this is for you.

The problem with relying on GitHub

GitHub is a great tool for engineers. It is a terrible tool for getting hired.

A recruiter scrolling your GitHub sees green squares and repo names. They cannot tell if your top-pinned repo is a polished production app or a half-finished tutorial follow-along. They cannot watch your app run. They cannot read your case study. They cannot understand the decisions you made, why you chose Postgres over Mongo, why you pulled out Redux for Zustand, why you rewrote the auth flow three times.

This matters because in skills-based hiring, the candidate who is easy to verify wins. The candidate who is hard to verify gets skipped silently. There is no rejection email. The recruiter just moves on to the next profile.

A working portfolio fixes this. A good one lets a recruiter understand your work in thirty seconds and a senior engineer go deep in five minutes. The same page serves both. That is the bar I wanted to hit.

Why existing portfolio tools fail developers

I looked at every option before building my own. Each one failed in a different way.

The drag-and-drop builders. They assume you want to spend a Saturday choosing fonts. You do not. You want to ship a portfolio in one evening and move on.

The "developer-focused" template repos. Fork the repo, edit a JSON file, redeploy when you want to add a project. The friction is so high that most people never update their portfolio after the initial push. A static, stale portfolio is worse than no portfolio.

The paid SaaS builders. Free tier shows you the dashboard. The moment you want to publish, remove the watermark, or add analytics, the credit card prompt appears. That is not a free portfolio website builder. That is a trial.

The generic site builders. They treat your work as a flat grid of screenshots. A static image cannot show proof of skills for a developer building a real application. You need video. You need context. You need a real project page, not a card.

I wanted a tool that fixed all of these at once, stayed genuinely free, and treated a developer's work like the multi-layered thing it actually is.

What the SkillEvidence portfolio builder does

Every feature below is in the free tier. There is no paid plan. No trial. No credit card. I made that decision early because the people who need this most are usually the ones with the least budget. A bootcamp graduate cannot afford a $15/month portfolio tool. Neither can a junior developer between jobs.

Here is what you get.

YouTube embeds that stop the scroll

Paste any YouTube link. A watch URL, a youtu.be short link, or a YouTube Shorts URL. The builder auto-converts it to an inline embed. The video plays directly on your project page. No uploading, no encoding, no hosting bill. YouTube handles the streaming.

For developers, this is the single most underrated feature in any portfolio. A thirty-second Loom of your app actually running, with your voice walking through the architecture, will outperform a wall of screenshots every time. A recruiter who watches your demo gets it. A recruiter who scrolls past screenshots does not.

This is also where most paid portfolio builders fall short. They either do not support inline video or charge extra for it. Free should mean free, including the most important feature.

A dedicated project page for every project

Each project gets its own full page with a clean URL, not just a card in a grid. You add a title, a slug, a short summary, a full rich-text description, a featured image, and a media gallery. No cap on projects.

Individual project page looks like this: https://skillevidence.com/en/u/partho-protim/portfolio/ai-article-writer-auto-blogger-saves-cost-upto-200-times

The technical benefit is that you can link directly to a single project. Hiring manager wants to see your one Stripe integration project? Send them that URL, not your whole portfolio. Senior engineer doing a deep dive before an interview? They can open the project page, read the case study, watch the video, and click through to the repo, all in one tab.

Every project page is crawlable, has its own meta description, and shows up in the sitemap. Your work becomes findable by Google, not just by people who already have your link. That is how a professional portfolio website should behave by default.

Image and video gallery per project

Each project supports a full gallery. Mix images and YouTube videos in any order. Visitors swipe through on mobile or use the built-in slider on desktop.

For developers, this means you can layer your proof. The architecture diagram. The screen recording of the working feature. The screenshot of your analytics dashboard. The before-and-after of the performance fix. Each project becomes a small case study instead of a single screenshot.

This is also what makes the tool work for designers, video editors, motion artists, and product folks who often work with developers. One portfolio format, many disciplines.

Built-in contact form with dashboard inbox

Every portfolio comes with a contact form. Messages arrive in your dashboard and your email. No third-party plugin, no separate email service, no Formspree account.

The point is to remove friction between "interested" and "in contact." A recruiter who just watched your demo can message you in the same tab, in the same moment. For freelancers, this turns the portfolio into a working lead channel instead of a static page.

For anyone trying to stand out to recruiters, removing that one extra step matters more than it sounds.

Visitor analytics that are actually free

Total visitors, per-project view counts, traffic sources, thirty-day chart. All of it free.

For job seekers, this is a feedback loop. You can see which projects pull attention before deciding which one to lead with in your next application. You can A/B test your strongest work. You can find out which traffic source is actually converting, LinkedIn versus Twitter versus direct.

Every paid portfolio tool treats analytics as a premium feature. I treat it as table stakes. A career growth tool without measurement is just decoration.

Project categories, tech tags, and skill tags

Every project supports tech and skill tags. You also assign projects to categories you define yourself: Web, Mobile, Backend, DevOps, ML, whatever buckets fit your work. Visitors filter by category to find exactly what they care about.

For a polyglot developer, this is huge. A recruiter looking for a React engineer does not have to wade through your Go side projects. A client looking for a backend specialist does not have to dig past your CSS experiments. They filter, they see relevant work, they reach out.

This is also what makes the tool a real portfolio builder for students showing different bootcamp projects, and a flexible portfolio builder for job seekers targeting more than one kind of role from one shared URL.

Rich text editor with code block support

Project descriptions are not plain text. The built-in editor supports headings, bold, italic, colors, highlights, bullet and numbered lists, links, and code blocks.

For developers, the code block support matters. You can paste actual code samples into your project write-up. Show the tricky reducer. Show the SQL query you optimized. Show the API call signature. Real code in a real description signals real work in a way that no screenshot can.

Formatting matters because it signals care. Care signals that you do the same in your code.

Services section for freelancers

You can list the services you offer with a headline and description for each. Visitors immediately see what you can be hired for.

This is what turns a developer portfolio into a hire-me page. Freelancers can list productized offerings: "Stripe integration for SaaS, 1 week, fixed scope." Solo developers can list the stacks they take projects in. Consultants can list package tiers.

A portfolio that only shows work makes visitors guess what you want from them. A portfolio with a services section ends the guessing in one scroll.

Bio, headline, and about-you section

Headline under your name. Short primary bio. Long secondary bio. Avatar. Skill tags in the sidebar.

The headline is your one-line pitch. The short bio is the elevator version. The long bio is for the visitor who is already interested and wants the full story. Three layers of depth, the visitor picks how deep to go.

Work alone is not enough. People hire people. The bio is where you stop being a username and start being someone the visitor can imagine on their team.

SEO and clean URLs

Every project page has its own meta description and a clean URL. Pages are crawlable, included in the sitemap, indexable by Google. No JavaScript-rendered content that crawlers cannot see.

This is how passive opportunities show up. A recruiter searches for "Next.js developer with Postgres experience" and your project page shows up. A client searches for "React Native payment integration" and lands on your case study. None of that happens with a closed, paywalled portfolio.

For a serious developer portfolio builder workflow where discoverability matters, this is non-negotiable. I built it to be SEO-correct from day one.

External project links

Each project supports an external link. Live site, GitHub repo, App Store, Play Store, npm package, demo deployment, Figma file, case study on your company blog.

This respects the truth that no portfolio page can fully replace the original artifact. The visitor who wants to read your code clicks through to GitHub. The visitor who only wants the summary stays on the project page. You serve both.

Publish and draft control

Every project can be toggled between published and draft. The whole portfolio can be set to public, unlisted, or private.

Students prepping for a job hunt can build quietly and publish on launch day. Freelancers can keep NDA work unlisted and share only with the right clients. Career changers can build slowly and flip the page public the day they are ready. You never have to apologize for a half-finished page. You only show what is ready.

Shareable portfolio URL

You get a clean, memorable URL. Put it on LinkedIn, in your resume, in your email signature, at the end of every cold pitch, in your GitHub bio, in your Twitter profile.

This is the link that works when you are not in the room. The shorter and cleaner, the more people click.

Mobile-friendly design

The portfolio looks professional on phones, tablets, and desktops. Layout reflows automatically. Galleries, videos, and project pages all adapt.

This matters because a lot of recruiters open your link from their phone between meetings. A page that breaks on mobile loses them in three seconds.

Who I built this for

This is a portfolio builder for developers who want a real project page per app, not a JSON config in a repo they have to redeploy every time they ship something new. It is for portfolio builder for students who need a first-job hunt page that actually converts. It is for freelancers who want services, analytics, and a contact form on one page. It is for career changers moving into tech who need to show proof of skills without years of formal experience.

If you want a portfolio without coding the page itself, where you can share your work online in a way that respects how busy the viewer is, this is the build. It is the best portfolio builder I would have wanted ten years ago when I was applying for my first dev job.

A real example from an early user

Rohit finished a six-month bootcamp and had three projects to show. He built his page in one evening, paid nothing, and embedded a YouTube screencast for each app instead of using flat screenshots. He pasted the link into ten job applications the next week. Two recruiters replied within forty-eight hours, both mentioning the video walkthroughs by name. His analytics showed one project had four times the views of the other two, so he led every new application with that one. He had his first offer in nineteen days.

That is the kind of outcome I built this for.

How to get started

Sign up for a free account.
Add your headline, short bio, and skill tags.
Create your first project.
Paste a YouTube link if you have one. If not, write a clear description and add a featured image.
Add an external link to the live site or repo.
Publish.
Repeat for two more projects.
Copy your portfolio URL. Put it on LinkedIn, in your resume, and in your GitHub bio today.

There is nothing to install. There is nothing to pay for. No contract.

This is genuinely the best free portfolio builder I could ship, and I keep it free on purpose because the developers who need it most are the ones who cannot pay for it.

The future of hiring is proof, not paper

I built this because the next decade of hiring belongs to candidates whose work can be verified in thirty seconds. Resumes describe. Portfolios prove. Recruiters are already moving in that direction. Clients have been there for years.

A PDF resume tells a story. A working portfolio ends the argument. Build your portfolio online before the next application, the next interview, the next cold email. The link you build tonight is the one that opens doors for you next week.

If you found this useful and you are about to start a job hunt, drop a comment with what stack you work in. I am genuinely curious which kinds of developers find this post and would love to know who shows up.

Built AI tool that Writes Article + SEO in 1 click

Partho Protim — Fri, 12 Sep 2025 19:17:05 +0000

Most AI tools can generate content, but very few can handle the entire blogging workflow, from research, to SEO, to publishing.

Here is how I made it the best AI blog article writer :

What problem does it solve ?

It generates long-form articles (1600–4000 words) with structured headings, metadata, and schema.
It automatically applies on-page SEO (meta tags, keyword optimization, image alt text, readability scoring).
It integrates directly with WordPress (and other CMS) so the content is published in one click.

The workflow is designed with developers and marketers in mind: automation, reliability, and scalability. What used to take hours (sometimes days) can now be done in less than a minute.

In this post, I’ll break down the technical architecture, the stack I used, and how the system evolved from a simple content generator into a full-scale AI blog writing engine.

For anyone building SaaS or experimenting with AI + automation, this is a blueprint for turning a complex multi-step process into a frictionless experience.

Why I Built This

Content creation is always the biggest bottleneck for businesses and bloggers. Even with AI writers, you still need to:

Research keywords.
Optimize for SEO.
Find images and videos.
Format the content.
Publish to WordPress (or another CMS).

Each step eats up time, breaks your flow, and adds manual overhead. I wanted to build something that collapses the entire workflow into one click - no handoff, no extra tools, no wasted hours.

The Core Workflow

(a more detailed description is in NanyBot Blog)

User Input & Validation

User enters a keyword or YouTube link.
Settings allow brand voice instructions and SEO preferences.
A validation layer ensures input quality before triggering generation.

AI-Powered Research

Fetches top search results with Google Custom Search.
Extracts insights, headlines, and competitive content structure.
Optionally, processes YouTube transcripts for video-based articles.

Article Generation

Orchestrated with GPT models for 1600–4000 words.
Generates metadata, H1–H4 structure, slug, and SEO-friendly text.
Expands each section in parallel for performance.

SEO Optimization

Auto-creates meta title + description.
Adds internal links (scans WordPress site).
Ensures keyword density and readability balance.

Media Automation

Fetches Pexels images with smart AI selection.
Embeds relevant YouTube videos.
Auto-generates alt text and captions for SEO.

Publishing

Pushes directly to WordPress via REST API.
Uploads featured image.
Injects RankMath/Yoast metadata.
Supports auto-scheduling and categorization.

Technical Stack

Frontend: Next.js 14 (with SSR), React 18, Redux Toolkit, Tailwind CSS.
Backend: Node.js + Express, Socket.io for real-time updates, Supabase for auth.
AI Layer: OpenAI GPT-4o-mini for cost-efficient long-form content.
External APIs: Google Custom Search, Pexels, YouTube Data API, WordPress REST API.
Infrastructure: Docker, Redis (caching + scheduling), PM2 for process management.

Everything runs with parallelization and caching, so even a 3000-word article with images, links, and SEO optimization is ready in 50–70 seconds.

Value It Creates

For bloggers: no need to juggle 5 different tools to go from idea → live article.
For agencies: scale content production across clients with multi-tenant architecture.
For enterprises: autopilot system generates content calendars, clusters keywords, and schedules posts at scale.

Bottom line: It reduces article production time by 95%, while maintaining SEO quality and consistency.

What’s Next

The system already handles research, writing, SEO, and publishing. The next frontier is:

Full analytics integration to measure content performance.
More CMS connectors (Ghost, Webflow, Shopify).
Smarter keyword clustering for autopilot campaigns.

This project is both a tech experiment and a real-world SaaS. If you’re building with AI and automation, I’d love to hear your thoughts. How would you extend this?