Velora Rights - Case Study

Overview

The website for Velora Rights, the practice of an Indian intellectual property advocate who publishes educational content on trademarks, copyright, and creator rights. It carries practice-area guides, a blog, an about page, and a careers page for internships.

The owner set the priorities explicitly: being found first, both by search engines and by AI assistants that cite sources, then ease of editing for a non-technical owner, then visual polish. Every technical decision answers to that order.

It worked. Since launch the site has brought in internship applications and enquiries from prospective clients through search, with no paid promotion.

Next.js 16 React 19 TypeScript MDX Tailwind 4 JSON-LD Vitest Playwright Vercel

Problem & Solution

The Problem

A new practice with no presence beyond an Instagram account
Search and AI assistants increasingly decide who gets found
The owner needs to publish without a developer each time
Bar Council rules forbid advocates from advertising services
Thin or broken pages actively hurt search ranking

The Solution

Every page statically generated, with its full text in the HTML
Structured data, an llms.txt, and AI crawlers deliberately allowed
Posts written as Markdown files from a template, deployed on push
Informational copy only, with a first-visit disclaimer
Content validated at build time; stub pages left out

Key Highlights

Search Results
Verified with Google Search Console and Bing Webmaster Tools, with sitemaps submitted and key pages requested for indexing at launch; organic search now brings in internship applications and client enquiries

Structured Data
JSON-LD for the legal service, the founder, every blog post, breadcrumbs, and FAQs, built from one set of schema builders and emitted through a single escaping component

Written for AI Assistants
An llms.txt index and an RSS feed generated from the content, and AI crawlers allowed by choice, so assistants can read and cite the articles

Fully Static
No database, no CMS, no server state; a CI check fails the build if any route stops being statically generated

Owner-Editable
Posts and practice areas are Markdown files with simple frontmatter and a template, explained in a plain-language guide written for the owner

Share Cards
A generated Open Graph image for every route, from one branded template, so links shared on social media look intentional

Technical Approach

Kept content as portable frontmatter and Markdown, not JavaScript exports, so a visual CMS can be added later without migrating a single post
Chose a Markdown compiler that supports YAML frontmatter over Next.js's built-in MDX, which only accepts metadata written as code inside the file — worse for a non-technical editor
Made the filename the slug, with no separate field, so a post's URL and its file can never drift apart
Validated every post's frontmatter before each build, so a content mistake fails the deploy instead of publishing a broken page
Drove the visible breadcrumbs and their structured data from one array, so the two cannot disagree
Published only practice areas with real substance — four today — and deliberately deferred the rest, because thin pages are an SEO liability
Wrote all copy as information rather than promotion — no "hire me", testimonials, or superlatives — to stay within Bar Council of India Rule 36, with a disclaimer shown on first visit
Vendored the font files for share-card generation as WOFF, since the image renderer cannot read the WOFF2 files a site normally serves
Traced a site-wide styling failure to an unlayered CSS reset overriding every Tailwind utility, fixed it, and documented the rule so it cannot recur
Covered loaders, components, structured data, and generated routes with 17 Vitest files, plus 7 Playwright specs run against a real production build
Wrote three audience-specific documents: architecture decisions for future developers, a setup guide, and a step-by-step publishing guide for the owner

What This Demonstrates

Measurable Outcome: Built for discoverability and saw it pay off in real internship applications and client enquiries
Priorities Stated, Then Honoured: Turned the owner's ranking of goals into a default for every trade-off, written down so it outlives the original build
Working Within Regulation: Treated a professional advertising rule as a design constraint on copy and flows, not an afterthought
Designing for the Editor: Picked the content format and tooling for the person who will maintain the site, not the developer
Restraint: Left out a CMS, a database, and placeholder pages until there is a real need for each
Verification Beyond the Build: Checked rendered pages and raw HTML, because the worst bug built and type-checked cleanly