👋 Hello, I'm Jon

The Person Behind
HtmlColor.Codes

My name is Jon DeCosta. I'm a web designer, developer, and digital marketer with 10 years in the industry. I'm also a full-time blogger, and this site came out of one of those late-night research sessions where an idea turned into something real — fast. This page is the honest story of how it happened.

JD
Jon DeCosta
Web Designer · Developer · Blogger
10 Yrs Exp Full-Time Blogger Digital Marketer SEO
10+
Years Experience
5
Days to Launch
8+
Free Tools Built
140+
CSS Colors Covered

16.7M
Colors Accessible
8+
Free Tools
140
CSS Named Colors
60+
Curated Palettes
100%
Always Free

How HtmlColor.Codes Actually Started

I'll tell you exactly how this happened — no embellishment, no marketing spin. Just the genuine sequence of events that took this from a random idea to a live website inside of a week.

🔍
The Research Phase

Looking for a new niche to build in

I've been building websites and writing about digital topics for over a decade. After spending some time thinking about where I wanted to put my energy next, I decided to go back to basics and do proper keyword research — not just gut feeling, but actual data. I spent 2 to 3 days looking at search volumes, competition levels, and monetization potential across dozens of niches.

The process was slow at first. I kept landing on niches that were either too saturated or too narrow to build a sustainable site around. Then I started looking at developer and design tools — utility sites that people use daily rather than just visit once. That's when the keyword "HTML color codes" showed up on my radar. High volume, clear user intent, and a surprising amount of room for a better, more complete resource.

💡
The Domain Moment

A GoDaddy notification changed everything

Once I'd decided the niche had potential, the next obvious question was the domain. I started browsing for options — most of the obvious ones were taken or priced at a premium. I wasn't in a rush, so I was thinking I might have to get creative. Then, out of nowhere, a GoDaddy notification came through telling me that htmlcolor.codes was available at auction.

I don't usually move fast on domain decisions, but this one felt too specific to ignore. The domain literally said what the site was going to be about. No guesswork needed from a user's perspective, no extra explaining. I bought it without overthinking it, and I'm glad I did. That .codes extension also felt right for a site aimed at developers — it has a technical credibility to it that a generic .com equivalent wouldn't have.

🏗️
The Build

Five days of proper hard work

I did competition research first — went through all the top-ranking sites for color-related queries, made notes on what each one did well and where they left gaps. The gaps were real: most sites had one tool and a static color list. Nothing comprehensive, nothing that felt built by someone who actually understood the design and development workflow.

So I built what I'd want to use myself. A full-featured color picker with Hex, RGB, HSL, OKLCH, and CSS output. An image color picker that works entirely in the browser without uploading your files to a server. A complete color chart of all 140 CSS named colors — searchable and filterable. A curated color library with 60+ palettes. A gradient builder. A contrast checker. Everything in one place, all free, no account required. Five days from that GoDaddy notification to a live site.

🚀
Today

Ongoing and growing

The site went live and has been growing steadily. I keep building on it — new tools, better UX, more detailed content. Every update comes from either something I needed personally while doing client work or something that showed up repeatedly in search queries. The goal has always been the same: make it the most useful free color resource on the internet, full stop.


Why I Built This — and What Drives Every Update

I've used design tools my whole career. Most of the time, the free options feel like a compromise — basic features, annoying limitations, or built by someone who's never actually sat with a designer or developer trying to get real work done. That frustration is where this site came from.

🎯

Built for Actual Use

Every feature on this site exists because it solves a real problem that comes up in real design and development work — not because it looks good in a feature list. If it doesn't make someone's job easier, it doesn't make the cut.

🔓

Free Without Limits

No "free tier" with arbitrary limits. No account wall before you can use basic features. No watermarks. The tools here are free because they should be — design tools shouldn't be gatekept behind subscriptions for every small studio, student, or freelancer working alone.

🔒

Privacy Taken Seriously

The image color picker is a good example of this. Your image never leaves your browser — ever. All processing is done locally using the Canvas API. You can upload confidential brand assets or client files without any privacy concern at all.

📚

Content That Actually Explains

I write every piece of content on this site myself. Not to fill word count or tick a content marketing box — because I genuinely think understanding what a hex code is, or when to use HSL over RGB, makes you better at your work. The explanations here are the ones I wish existed when I was learning.

Performance First

Everything runs in your browser. No heavy frameworks, no unnecessary JavaScript, no slow API calls. Tools load fast because they should — nobody should have to wait for a color picker to become usable. Clean code and deliberate choices from the start.

Accessibility Considered

The contrast checker exists because accessibility isn't an afterthought in professional design work. Colors that fail WCAG standards are colors that real people can't read. I built the tool, and I use it myself — including while building this site.


What I Actually Know — 10 Years of Real Work

I'm not going to list every framework I've touched or every certification I've collected. Here's an honest picture of where my skills sit after a decade of doing this professionally.

🎨 Design

UI / UX Design92%
Color Theory95%
Typography88%
Figma / Design Tools90%

💻 Development

HTML / CSS97%
JavaScript85%
Responsive Design96%
Performance Optimization84%

📈 Digital Marketing & SEO

SEO / Keyword Research93%
Content Strategy90%
Technical SEO88%
Analytics & CRO82%

Tools I Use to Build and Run This Site

No affiliate deals, no sponsored placements — just the tools I genuinely use. Some of these I've been using for years; others I picked up specifically for this project.

🎨
Figma
Design
📝
VS Code
Dev Editor
🌐
Chrome DevTools
Testing
📊
Ahrefs
SEO Research
🔍
Google Search Console
SEO
📈
Google Analytics
Analytics
🌍
GoDaddy
Domain
Cloudflare
CDN / DNS
🖼️
SVGOMG
SVG Optimization
📱
BrowserStack
Cross-browser
🔒
PageSpeed Insights
Performance
W3C Validator
Code Quality

Every Free Tool on This Site

Each one was built to solve a specific gap I kept running into. Here's what's available — all free, all in your browser, all the time.


A Bit More About Me and How I Work

I've been working with websites in one form or another since before responsive design was a thing. Started doing simple HTML and CSS layouts, moved into full site builds, picked up digital marketing and SEO along the way, and eventually landed on blogging as my main focus because it gave me the flexibility to build things I actually found interesting rather than things clients specified.

Over the years I've worked with designers, developers, marketing teams, and business owners across a wide range of industries. That exposure gave me a pretty clear picture of the tools people actually need versus the ones that get built and promoted. Color tools specifically came up constantly — either someone needed a quick hex code, or they needed to understand why their button text wasn't readable enough, or they were trying to build a brand palette from a reference photo. The tools that existed handled each of these separately, and often not very well.

Why a niche color tool site, specifically

When I was doing my research phase for this project, I looked carefully at who was ranking for color-related queries and what those sites actually offered. Most of them were either old (some dating back to the early 2000s and never meaningfully updated) or thin — a color picker widget with minimal context and no real content around it.

The search queries told the story pretty clearly. People weren't just looking for a color picker — they were looking for explanations. What does this format mean? When should I use HSL instead of RGB? What are the 140 CSS named colors? How do I pick accessible text colors? These are questions that come up constantly in real work, and the answers were scattered across Stack Overflow threads, outdated MDN pages, and half-finished blog posts. Bringing them together with properly built tools felt like a genuine opportunity to build something useful.

On the "5 days" thing: People sometimes ask if that's really true. It is, but I want to be clear about what it means. Five days of focused, full-time work by someone who's been building websites for a decade. Not five days starting from zero — five days of applying everything I've learned over 10 years to a specific, well-researched problem. The research beforehand made the build efficient. The experience made the decisions fast. Anyone starting out would need more time, and that's completely fine.

What I'm still working on

The site is a living project. There are more tools I want to build — a proper CSS gradient generator with more controls, a color shade generator that works off HSL lightness scales, and a more detailed contrast checking interface that covers WCAG 2.2's new criteria. There's also more content I want to write: deep guides on building design system color tokens, color psychology in branding, accessibility best practices for color in UI.

I post updates regularly. If you're using the tools and run into something that doesn't work the way you expect, or you have a suggestion for a feature that would genuinely improve your workflow, I want to hear about it. The contact page is real — I read and respond to every message.

What "EEAT" Means to Me in Plain Terms

Google's quality guidelines talk about Experience, Expertise, Authoritativeness, and Trustworthiness — the factors that determine whether a site is worth recommending in search results. I don't think about these as boxes to tick. I think about them as questions to answer honestly.

Do I have real experience with this? Yes — I've used color tools professionally for 10 years, I've built websites with real color requirements for real clients, and I've encountered every edge case these tools need to handle. Do I have expertise? Yes — I understand why hex codes work the way they do, what HSL is better for, how the Canvas API processes pixel data for image color sampling. Is this site authoritative? That's earned over time through accurate, helpful content that people actually use. And trustworthy? I think the clearest signal is that I don't hide who I am, I explain how things work, and the tools do what they say they do.

This page exists partly because I believe the person behind a website matters. If you're going to use a tool for your work — whether you're a student building your first webpage or a professional designer on a client project — you deserve to know who built it and why. That's what this page is for.


Start Using the Tools

Everything on HtmlColor.Codes is free — no account, no limits, no watermarks. Built by someone who uses color tools daily, for everyone who does the same.

@ HtmlColor.Codes· All tools free · Built for designers & developers worldwide