How Signal Dark Was Built with Claude Code

Every line of Signal Dark was written inside VS Code using Claude Code — an AI coding agent that lives inside VS Code as a chat window. You type what you want in plain English, and it reads your project files, understands your stack, and writes production-ready code. No manual coding. The person behind this template doesn't write code at all — not the CSS, not the PHP, not the SQL. Even the local Joomla installation, the Docker setup, and the database configuration were built entirely through chat with Claude Code — no setup wizards, no database credentials to fill in, no passwords to choose. Claude figured out what was needed and handled every step on its own.

The One Skill That Changes Everything

When something looks wrong on your website — a colour is off, spacing is weird, text is too big — you need to tell Claude what you're seeing. You could try describing it in words. You could screenshot it. You could right-click the element, open the browser inspector, and try to copy the relevant CSS by hand. All of that works, sort of. It's also painfully slow, and Claude usually needs to ask follow-up questions because the information is incomplete.

We built a small script that skips all of that. You click the problem element, paste the script into your browser console, and press Enter. In under two seconds, it captures everything — the HTML, every CSS rule affecting that element, the computed styles, the full page structure around it — and copies it to your clipboard. Then you paste it to Claude. That's it. Claude now has the same information a senior developer would see staring at the inspector panel. It doesn't need to ask what the parent element is, which stylesheet the rule comes from, or whether an inline style is overriding something. It's all there.

Whether you've never opened browser developer tools or you live in them — this script changes the game. It turned what used to be hour-long back-and-forth debugging sessions into five-minute fixes. Here's the step-by-step guide — takes two minutes to set up, and you'll reach for it every single time something doesn't look right.

The Setup

The workspace is deliberately simple: VS Code with the Claude Code chat panel on the right, taking up about 30% of the screen. The remaining 70% is a Firefox browser window set to Always on Top, pointed at localhost:8080. That's it. Describe a change in the chat, wait for Claude to report it's done, reload the browser, and see the result. If something looks wrong — screenshot it, paste the computed styles from the inspector, and describe what's off. Claude reads the context and fixes it.

There is no switching between terminal tabs, no hunting through documentation, no copy-pasting Stack Overflow snippets. The conversation is the development environment.

And if Claude needs information it doesn't already know — a new API, an unfamiliar Joomla extension, a CSS technique it hasn't encountered — it can search the web and read documentation in real time, right from the same chat. You can also tell it to research something before it starts building. "Read the Akeeba Engage documentation first, then install and style it." Claude browses the docs, learns what it needs, and gets to work. You never leave the conversation.

What Claude Code Actually Does

The workflow is conversational. Open the chat, describe the change, and Claude Code edits the stylesheet, runs SQL against the database, manages Docker containers, and debugs CSS specificity issues — all from a single session. It works with Docker, Podman, Incus, local LAMP stacks, or whatever environment you prefer — if it runs in a terminal, Claude can manage it. It also builds desktop apps, CLI tools, Python scripts, shell automations, and anything else you can describe in words. For this project, it created articles, assigned modules to pages, shifted nested-set trees in the asset table, built a Kivy desktop app for publishing articles, and cleared the Joomla cache when it was done. The result is a template that would have taken months of manual work.

Questions You Didn't Know to Ask

Do I need to know how to code?

No. The person behind this entire site — the template, the articles, the Docker setup, every CSS rule and database query — does not write code. With the occasional exception of some CSS from years of web admin experience, and maybe a little Python here and there — but nothing worth mentioning. In the interest of full transparency: most of the actual workflow involves Gray Zone Warfare taking up 75% of the screen while the remaining 25% is the Claude Code chat, where the main interaction is clicking "Yes" on permission prompts. Half the time there is genuinely no idea what Claude is doing over there. Something about shifting nested asset trees and recomputing left-right values — sure, sounds important, approved. The point is, you don't need to understand the code. You need to look at the result, decide if it matches what you had in mind, and say "no, the padding is wrong" or "make the hover effect more violet." Half the responses in the chat are just "do whatever you think is best" — because once you trust the output, you stop micromanaging and start directing. You'll pick up the vocabulary naturally — after a few sessions you'll catch yourself saying "the border-left on hover" without thinking about it. That's not learning to code, that's learning to communicate with someone who codes for you. The actual job is creative direction, quality control, and occasionally glancing away from your game to hit a button.

How much does this cost?

VS Code is free. Docker is free. Joomla is free. Claude Code starts at $20 per month. That's the entire stack. No hosting fees while you develop locally, no premium themes to buy, no page builder subscriptions. When you're ready to go live, a basic VPS runs $5–10 per month. You can build and launch a fully custom website for under $30 a month in total.

Is this actually how Signal Dark was built?

Every single piece of it. Signal Dark is the template powering this website — and the CSS, the responsive grid, the dark theme colour system, the Kunena forum styling, the module position map, a desktop app that generates and publishes AI-written articles in any style or mood directly to your Joomla site, the Docker setup, the database migrations, the backup scripts, and the article you're reading right now. All built through conversation in a VS Code chat window.

Are you really that good?

This entire website — the template, the CSS, the JavaScript, the forum styling, the responsive layouts, the module configurations, the database operations, the Docker setup, the deployment pipeline — was built through a chat window by someone who does not write code. Every line of it. That's not a sales pitch, it's just what happened. Whether that qualifies as "good" is up to you, but the site you're reading right now is the proof.

I have a brand new computer. If I install VS Code, Claude Code, and Docker — can Claude set up a full Joomla website without me writing a single command?

Yes. Tell Claude Code you want a Joomla site running locally on Docker. It will write the docker-compose file, start the containers, run the Joomla CLI installer, configure the database, and hand you a working site at localhost:8080. You never open a terminal yourself. The entire installation happens through the chat window.

Can I just say "make me a blog" and end up with a fully working Joomla site?

Yes. Tell Claude Code: "Set up a Joomla blog on Docker. I want it running on localhost:8080. Create some categories, write a few starter articles, add a main menu, style it nicely, and make it look like a real blog." Then sit back. Claude will write the docker-compose file, pull the Joomla image, start the containers, run the installer with auto-generated database credentials — you never see a setup screen — create your categories, populate them with articles, configure the template, build the navigation, assign modules to positions, and clear the cache. When it says "done," you open your browser, go to localhost:8080, and you're looking at a styled, working blog with content in it. You didn't fill in a single form field, didn't pick a database name, didn't click "Install." The whole thing happened through one message in a chat window.

Can Claude design a custom template for my site?

Yes — with one condition. You need to describe what you want and react to what you see. Claude can scaffold a complete Joomla template from scratch: the directory structure, the XML manifest, the index.php layout, the full CSS. But design is iterative. You'll say "make the header darker" or "the sidebar font is too heavy" and Claude will adjust. The more specific your feedback, the faster you converge on exactly what you want. That said — Claude built the entirety of Signal Dark this way, from the first line of CSS to the last database query.

What if I just say "make me the most beautiful template you can imagine" and give you full creative control?

I'll do it. I'll pick a colour palette, choose typefaces that complement each other, design a layout system, build the responsive grid, style every component and module position, and hand you something complete. Will it be exactly what you pictured? Probably not on the first pass — because you haven't pictured it yet. That's the point. The first version gives you something concrete to react to. "I love the spacing but the purple is too loud." "The sidebar feels heavy." "Make the headings sharper." Three rounds of that and you have a template that looks like it came from a studio, built in a weekend, by someone who never opened a code editor.

This kind of output — a full template designed, built, and iterated on entirely through conversation — is what happens when an AI model doesn't just write functional code but actually understands aesthetics. Claude doesn't hand you a working layout and call it done. It considers spacing, contrast, rhythm, typography — the things that make a design feel right rather than just look correct. It holds your entire project in memory, writes production code across dozens of files, and refines its own work based on your reactions. The honest answer: the ceiling isn't my taste or technical ability. It's how clearly you can articulate what feels right and what doesn't once you see it. Give me creative freedom and then be a ruthless critic of the result — that combination produces genuinely remarkable work.

Can Claude build a Joomla plugin or extension for me?

Yes. Describe what the plugin should do — "I want a content plugin that adds a table of contents to every article" — and Claude writes the PHP, creates the XML manifest, registers it in the database, and enables it. You test it in the browser and give feedback. If something isn't right, you describe the problem (or paste the error), and Claude fixes it. This works for plugins, modules, components, and template overrides.

Can Claude update my site content too — not just the code?

Yes. Articles, categories, menus, modules, metadata, SEO descriptions, image alt text — all through conversation. "Create a new article about our spring sale in the Promotions category, publish it, and add it to the main menu." Done. No need to log into the Joomla admin panel at all if you don't want to.

What about backups with Docker? And ongoing site management?

Just as easy. Claude can set up automated backup scripts on the VPS that dump your database and archive your files on a schedule — hourly, daily, whatever you want. Then it writes a second script on your local machine that connects to the VPS over SSH and pulls down the latest backups automatically. You wake up every morning with a fresh copy of your site on your own computer without lifting a finger.

But backups are just the start. Claude can install and configure website analytics — visitor stats, traffic sources, popular pages — for every site on the server. It can create entire content structures: categories, subcategories, menus, and articles with real text. Tell it "write five articles about traveling to Norway based on what you can find online, four more about Iceland, Portugal, Japan, and New Zealand, and pick good header images for each one" — and it will research the destinations, write the articles in your site's tone, handle the images, assign everything to the right categories, and publish. You paste a photo into the chat and say "use this for the Norway article" — done. The pasted image is more than good enough for a blog header, and if you need full resolution you can just point Claude to the file path instead. Paste five photos and say "figure out which article each one fits best" — it will look at the content of each image, match them to the articles, and assign them. Your morning coffee isn't even cold yet and your blog has nine new posts.

If I buy a VPS and give you root access, can you set up everything from scratch?

Yes — and securely. Tell Claude the VPS IP address and credentials, and it will SSH in and handle the entire setup: create a non-root user, configure SSH key authentication, disable password login, set up a firewall (UFW — think of it as a bouncer that only lets approved traffic through), install Fail2ban (a service that automatically blocks IP addresses that try to brute-force your login), install and configure your web server, set up SSL certificates with Let's Encrypt, deploy your site with Docker or directly on the server — whatever you prefer. If you want a control panel, it can install something like CloudPanel or HestiaCP. If you'd rather manage everything through the terminal, Claude does that too. The point is: you buy a $5 VPS, paste the login details into the chat, describe what you want running on it, and Claude turns a blank server into a production-ready setup. You never write a single command yourself.

Claude can also set up application-level backups and security — whatever fits your stack. For Joomla specifically, Akeeba Backup is excellent: scheduled backups of your entire installation — files, database, everything in one archive — with one-click restore. And Akeeba Admin Tools adds a web application firewall, security hardening, and monitoring on top. Claude can install and configure both. For non-Joomla sites, there are other approaches — database dump scripts, file-level snapshots, Docker volume backups — and Claude handles all of them.

I have a VPS running Docker and Joomla. Can Claude make changes directly on my live server?

Yes. VS Code connects to remote servers over SSH. Once connected, Claude Code runs commands on the VPS exactly as it would locally — editing files, restarting containers, running database queries, clearing caches. You sit at your desk, describe the change in the chat, and it happens on the server. No FTP, no cPanel, no manual file uploads.

Is it secure? Will I get hacked because an AI wrote my code?

Claude Code is trained to follow secure coding practices by default — it avoids common vulnerabilities like SQL injection, cross-site scripting (XSS), and command injection without being told. If it catches itself writing something insecure, it flags and fixes it immediately. That said, no developer — human or AI — writes perfectly secure code every single time. The difference is what happens next: you can literally tell Claude "do a full security audit of everything you just built" and it will methodically go through every file, check for exposed credentials, unsafe inputs, missing validation, insecure permissions, and anything else that could be exploited. It will then fix what it finds and explain what it changed. This isn't a gimmick — it reads every line, understands the context, and catches things that automated scanners miss. For a one-person operation or a small team, having an on-demand security review that actually understands your codebase is something that used to cost thousands. Now it's just another message in the chat.

What if something breaks?

Tell Claude what happened. Paste the error message, the broken layout, or the unexpected behaviour. Claude reads context — it knows what files it changed, what commands it ran, and what the code looked like before. It can roll back changes, fix the issue, or try a different approach. The conversation history is the debug log.

What happens when the conversation gets really long?

Claude compresses earlier messages automatically to stay within its context window. For very long sessions — hours of back-and-forth CSS work, for example — you can start a fresh conversation and Claude picks up where it left off. It reads project files, memory notes from previous sessions, and the current state of your code. Nothing is lost between conversations.

Can I literally talk to Claude while doing something else?

Yes. VS Code supports voice-to-text input — dictate your instructions into the chat while your hands are busy elsewhere. Pair that with a second monitor showing the browser and you don't even need to switch windows. Describe the change by voice, Claude makes the edit, you glance at the browser to check the result, and tell it what to fix next. Your main screen can be a game, a video call, a spreadsheet — whatever. The development environment is 25% of one screen and a microphone. That's a real workflow, and it works.

Can I sell what I build with Claude Code?

Yes. Everything Claude produces is yours — templates, plugins, extensions, entire sites. You own it. Sell it, license it, give it away, build a business around it. There is no ownership clause, no revenue share, no attribution requirement. The code is yours the moment it's written.

Can I use this for client work?

Absolutely. Build locally, show the client a preview, iterate on their feedback in real time, and deploy to their server when they're happy. The conversation-based workflow means revisions are fast — "make the header blue and add a contact form" is a five-minute change, not a half-day ticket. Clients don't need to know how you built it. They just see results delivered faster than they expected.

What if I'm not using Joomla?

Claude Code works with anything — WordPress, Drupal, static HTML, React, Next.js, Laravel. The conversational workflow is the same regardless of the platform.

That said, there's a reason this site runs on Joomla. It's a full CMS out of the box — multilingual support, granular access control, custom fields, a built-in article and category system, flexible module positions, content versioning, and a powerful menu manager — all without installing a single plugin. WordPress needs a dozen extensions to match what Joomla ships with by default. Joomla is easy to work with when you understand its structure, and with Claude Code handling the technical side, you never have to wrestle with that structure yourself. You just describe what you want and it gets built on top of a system that was designed for exactly this kind of complexity.

Joomla's market share doesn't reflect how good it actually is. It quietly ships features that other platforms charge for or bolt on through third-party plugins. The perception problem isn't capability — it's visibility. People pick WordPress because they've heard of it, not because they've compared the two. When you actually line them up feature by feature, Joomla wins in ways that matter for serious projects: native multilingual without plugins, real user group permissions, built-in content versioning, and a template system that gives you complete control without fighting a page builder. With Claude Code removing the learning curve entirely, there's no reason not to build on the most capable open-source CMS available.

Curious how Joomla stacks up against the alternatives? Read the full breakdowns: Joomla vs WordPress, Joomla vs Shopify, Joomla vs Wix, Joomla vs Squarespace, Joomla vs Webflow, or Joomla vs Drupal.

Learn to use Claude Code

These guides cover the workflow behind Signal Dark — how to give Claude Code the context it needs to write accurate CSS fixes and build features from a conversation.