Back to the shelf

028

Venus Remedies Website

A ground-up rebuild of the Venus Remedies corporate website: Astro, Tailwind CSS, TypeScript, built to last.

Launched · Started March 2026 · Website · Vibe-Coded

That's the whole thing.

The site's sound is off. The narration still plays.

This reading didn't load. The transcript is below.

Read the transcript

Venus Remedies is a global pharmaceutical manufacturer. Its previous website had aged out of modern web standards: hard to maintain, hard to extend, and not the kind of web presence that fit the scale of the company. That was worth fixing.

I rebuilt it from the ground up. Astro, Tailwind, TypeScript. Better performance, a cleaner design, search-friendliness built in, and a codebase that is straightforward to maintain. The old site stays alongside as an archive while the new one settles in.

I vibe-coded this with AI. Started March twenty twenty-six. That same month, I rebuilt my own site on Astro too. Same month, same stack. It's launched.

Narrated in my own cloned voice, generated with ElevenLabs v4.

The old Venus Remedies site had aged out of modern web standards. It was hard to maintain, hard to extend. For a global pharmaceutical manufacturer, that mattered.

I rebuilt it from the ground up. The new site runs on Astro, Tailwind CSS, and TypeScript. It’s faster, the design is cleaner, it’s built for search engines to read, and the codebase is something a team can actually maintain and build on. That’s a professionally built web presence for a global pharmaceutical manufacturer.

I started in March 2026, the same month I rebuilt my own site on Astro. There was something fitting about that: two sites, same stack, same month, one personal, one for the company I work with.

The old site isn’t gone. I kept it alongside the new one as a working archive, so there’s a clear reference point during the transition.

Vibe-coded with AI. It’s launched.

The making

  • Astro
  • Tailwind CSS
  • TypeScript

01 · The problem

Before it existed

What hurt

The old corporate website had aged out of modern web standards. It was hard to maintain and hard to extend.

Who uses it

  • Visitors to the company site
  • The people who maintain it
  • Developers who extend it

02 · The flow

4 steps, in the order they happen

  1. 01 / 04

    Open the new site

    You
    Visits the company website
    It answers
    Serves a faster, cleaner build on Astro
  2. 02 / 04

    Be found

    You
    Searches for the company
    It answers
    Meets pages built to be read by search engines
  3. 03 / 04

    Maintain it

    You
    A developer opens the codebase
    It answers
    Finds a plain Astro, Tailwind CSS and TypeScript project
  4. 04 / 04

    Compare with the old site

    You
    Opens the archive
    It answers
    Keeps the legacy site beside the new one as a working reference

03 · What was special

What it stands on

  1. An archive, not a deletion

    The legacy site stays in the workspace as a reference while the new one takes over.

  2. Built to be maintained

    Astro, Tailwind CSS, and TypeScript – chosen so a team can extend the site without a rewrite.

  3. Same month as my own site

    I moved my own site to Astro in the same month, on the same stack.

A rebuild that keeps the old site beside it.

Making-Of

A corporate site rebuilt to be maintained, with the old one kept as a reference.

Notion entry, date started

  1. The world before

    The company’s previous website no longer met modern web standards and was hard to maintain and extend.

  2. One day

    6 March 2026. The rebuild begins in a workspace holding a new-site folder and an old-site archive.

  3. Until finally

    The rebuilt site is launched.

The evidence Process, hands, and artifacts

Process

  1. Origin

    Rebuild from the ground up on Astro

  2. Archive

    Old site kept in the workspace as a reference

Hands

Akshansh

  • Concept and the choice of stack
  • Direction of the rebuild