Work, original
debarshidas.dev
A static-first identity and authority site built around verified claims, durable URLs, accessible HTML, and consent-controlled analytics.
- Role
- Designer, engineer, and author
- With
- On my own
- Status
- Active
- Years
- to
Hover a part to see its nameThe problem
A personal website can look polished and still fail its main job. Search engines may see thin HTML. AI systems may find inconsistent identity claims. Analytics code may run before a visitor makes a privacy choice. The site needed one verified source of truth and a release process that treated content, metadata, and implementation as one system.
The approach
I rebuilt the site with the Next.js App Router and Server Components. Public pages render complete HTML without depending on client-side JavaScript. A typed content layer keeps project attribution, dates, canonical paths, and social metadata together. Route metadata, JSON-LD, the sitemap, the feed, and visible page copy all derive from the same records.
Analytics that can identify a visitor waits behind one consent gate. Microsoft Clarity and Google Analytics, which can connect one visitor's activity across pages and visits, stay out of the active page until a visitor accepts analytics. Vercel Analytics and Speed Insights load for every visitor: they set no cookie and report only in aggregate. Rejecting or withdrawing consent does not restrict the site.
Engineering decisions
- Static rendering is the default for public content.
- Canonical URLs use one host and one path policy.
- Structured data uses stable identifiers for the person and website entities.
- Public claims must be supported by repository history or an approved identity record.
- CSS Modules and local fonts keep the rendering path small and predictable.
- Preview deployments remain outside search indexes.
Current limits
I publish no email address here; you can reach me on LinkedIn and GitHub. Search engines also take time to replace their older copies of the site after new pages ship.