Colkgirl shines a spotlight on women in tech, diversity, and inclusion initiatives, providing a platform for celebrating the contributions and achievements of women in the technology industry. Developers engaging with Colkgirl's content can expect to discover inspiring stories, insightful interviews, and  articles that highlight the experiences and perspectives of women in tech. 

Code Like A Girl

Implementing dark mode on a personal website turned into a full UI system refactor. The key lessons: hardcoded colors had to be replaced with semantic CSS variables (e.g., --text-primary), pure black/white contrast is too harsh so grey shades work better, Tailwind's typography plugin needed explicit variable mapping, code syntax highlighting required two themes switched dynamically, SVG diagrams needed separate versions per mode, and a flash-of-wrong-theme bug required moving theme detection before browser render. Dark mode isn't a surface-level toggle — it's a cross-cutting system concern that every UI layer must support intentionally.

I Thought Dark Mode Was Just a Toggle. It Turned Into a Full-System Refactor

An independent Squad for discussions, questions and answers about Next.JS. 


NextJS

With editors like vscode, its easier to change all the colors to css variables using the search feature, search for a hex value, replace it with a variable, buts its often nice to start a project with maintenence in mind from day one

That is true. I also recently gained my first experience implementing a dark mode for a web app. My key takeaway was that you should definitely plan the logic consciously right from the start of development; what seemed like a small feature turned into a task that took me a full week. There are various approaches, of course, but since I develop with React, I decided on the React Context API. I can highly recommend this approach as it is very accessible and easy to implement.

It’s really cumbersome to write dark mode from scratch.