← All projects
LiveBuilt with Lovable

Deepthi's Reading — the marketing site

The website you are reading right now, built in Lovable

My first build in this series: a full marketing site for my books and knowledge packs. I started with nothing but an idea and a colour I liked, and ended up with routing, a design system, a database, roles and an admin area. Everything I learned while building it became Edition #001.

Tools I used

LovableTanStack StartReactTailwind CSSLovable Cloud
Chapter one

How it started

I had a book in my head and no place to put it. I opened Lovable and typed one sentence: I want a website to market my book.

The journey

What actually happened

The first version was a plain page. Then I said the word PINK, and everything changed — the site got a palette, a display font, a magazine layout. I learned that I did not have to know CSS to have taste; I only had to describe what I wanted and react to what came back. After the look was right, I asked the harder question: can my books and my projects talk to each other? That turned into a real database — projects, books, chapters, glossary terms — and suddenly the site stopped being a brochure and became a system I can keep writing into.

The conversation

Moments that changed the build

  • Me: "I want to market my book." → We scoped it into a five-page marketing site instead of one long page.
  • Me: "PINK." → A full design system appeared: Hot Pink Pop, Lora headings, Nunito Sans body, magazine layout.
  • Me: "Can you connect the books with all the projects?" → We turned static text into a database with projects, books, chapters and a glossary.
  • Me: "Did you read all the projects I worked in Third Eye Vitals?" → Honest answer: no. So I told the story, and it got written in.
Honest part

What broke

Nothing dramatic broke. What broke was my assumption that a website is pages — it is actually data with pages on top. Once I accepted that, the second half went faster than the first.

Takeaway

What I learned

Describe the outcome, not the code. Give one strong constraint (PINK) and the rest of the decisions get easier. And content lives in a database, not in a paragraph you retype every time.