Skip to main content

Gemini CLI and Manus changed my website

Back in April, I wrote about the verticalization of coding agents by comparing OpenAI’s Codex and Claude Code. Since then, I haven’t really used Codex — Claude Code just keeps getting better and better. But now there’s a new contender in the mix: Google’s own Gemini CLI, which (as the name implies) is powered by Gemini 2.5 Pro.

Gemini CLI is very similar in usage to the other two, with one potential advantage (or at least I hope so): it should be an expert in all things Google and Google Cloud. That’s important to me, since I host everything in Google Cloud.

That said, the real trigger for trying out Gemini CLI came from a different direction: Manus.

Manus is a Perplexity-style, AI-powered workflow builder. I’m not entirely sure how to categorize it, but you can prompt it with complex tasks and it delivers structured documents. I’ve used it to create presentations and parts of a business plan, and I’ve found it surprisingly effective.

Now, my website was built during my first real experience with “vibe coding” — and it shows. I wanted to completely redesign it and update it to reflect a more modern style. But first, here’s how it looked before:

blogs structure

welcome page


I gave Manus the following prompt:

Take a look at my current website: https://www.vanguardsignals.com. I would like to redesign it, but keep the same logo and ideally the same colors. It’s all written in Angular, and the blog functionality uses Blogger APIs to bring in the articles. Since I’d like to keep it Angular, focus on the design — something I can hand off to my coding agent.

Despite the prompt being somewhat ambiguous, Manus went to work. It researched modern web designs, created a style guide complete with example images, sample JavaScript code, a color palette — and bundled everything into a huge markdown file.

To give you a taste of what it produced, here are two examples:

An example of how the blogs could be structured

An example of how the blogs could be structured

Visual elements to use

Visual elements to use

Which brings us back to Gemini CLI. I had originally considered asking Claude Code to implement the new visual style — but this seemed like the perfect chance to try out Gemini CLI instead. And to my amazement, it mostly nailed it. Sure, there were a few artifacts I asked it to change or remove, but overall, the result was very solid.

And then I got greedy.

After changing all the HTML and stylesheets, Gemini reported that it had only used 11% of its context window. That’s when I remembered: Gemini 2.5 Pro has a 1 million token context window (compared to around 200K with Claude Code). So I thought — let’s see how far I can take this.

I started small: I added two new languages to the site — French and Japanese — just to see if Gemini understood how Angular handles i18n. No problem. The context usage barely moved.

Then I raised the bar. My site has a blog section, which pulls articles from Google’s aging Blogger platform (this article included), using their API. The challenge: translate these blog posts in real-time, based on the selected language — and cache the translations in Firestore to avoid paying for repeated translations.

I already knew this would require enabling Firestore, setting up Firebase Functions, and configuring Google Cloud services. In the past, this took some effort.

This time? It took 45 minutes

Gemini suggested using Google’s own Translation APIs (naturally), and wrote all the code — Firebase Functions, Firestore access, everything. The only thing I had to do was enable the Translation API for my project. That was it.

Here’s the final result:

👉 https://www.vanguardsignals.com

Is this getting crazy, or what?


Labels:

Comments

Post a Comment

Popular posts from this blog

The case for central bank digital currency as public infrastructure to enable digital assets

I have dabbled a fair amount with all sorts of crypto currencies and their respective permissionless networks. In fact, I have been dabbling since 2012 which is by my last count a whopping 12 years. While I have always maintained that I do believe the general concept for digitization and programmability of assets is on the right path, its implementation, the user experience, the accessibility, the fraudulent activities, and the overall inefficiencies permissionless DLTs have, never made me into a true believer. I have stated that opinion on several occasions, here , here and here . There are still barriers to entry when it comes to digitization of assets: sustainable- and interoperable infrastructure. To illustrate this, I recently asked a notary public here in Zurich, why they can’t store the notarized documents as PDFs, the answer surprised me: because they must keep records for at least 70 years. Now, think about what would have happened if we stored these documents on floppy disks...
Post a Comment
Read more

Apples Vision Pro Headset strategy is all about its Arm-chips.

  Apple has given us a vision of what their VR and AR future might entail. But as have others pointed out numerous times, the whole point of the showcase at the WWDC 23 was to let people experiment, I’ve heard others say that it’s like the launch of the Apple Watch when Apple didn’t really know what would become of it. This is similar and yet different.  Just like the Apple Watch (and the iPad before it), Apple sought to porting its whole ecosystem onto a watch – granted, the Apple Watch can’t live on its own and a better comparison would probably be the iPad. The iPad can live without any other Apple device and unlike the iPhone, never really had a clearly defined function other than to watch movies and browse the web. It was not until it gained the ability to be used with a pencil that artists and designers started to explore the potential.  I’m trying to point out that Apple took 5 years from the first iPad in 2010 to the iPad Pro with pencil in 2015 to find its “kille...
Post a Comment
Read more

Is the payment industry finally being shaken up by … Apple?

My starting point for this is the evolution of the Android SmartPos and in particular the version at the lowest common denominator also known as SoftPos, which allows most Android phones to become NFC payment terminals. This is the domain of the Android operating system because Google has allowed unrestricted access to NFC since the days of GooglePay (2015ish), hence it doesn't surprise that when we talk about the SmartPOS, we really talk about the Android operating system with custom hardware and software. Now, we have known for some time that Apple will be entering this space (and has in fact in some markets) with the iPhone given the acquisition of Mobeewave. What is different to the Android ecosystem, however, is that Apple is again controlling every aspect surrounding the user experience. Let me try to reach a bit further and just to be clear: I’m not an expert when it comes to Terminal hardware and PCI security. Further I have not signed an NDA with Apple, so a lot of this i...
Post a Comment
Read more