Researcher · Developer · Builder

I build digital systems around real problems.

I'm Prabakaran Shankar. Alongside my work as a scientific researcher, I build websites, web applications and operational systems—usually because I encountered a problem that needed a better solution.

Live portfolio example: a real-time website homepage developed by Prabakaran Shankar for NViews Web

What I build

Built for real use.

Websites

Public-facing platforms designed around content, performance, usability, and purpose.

Web tools

Focused utilities built to solve recurring development or workflow problems.

Business systems

Internal applications designed around actual operational requirements.

Infrastructure

Domains, DNS, deployment, email, APIs, security, and supporting systems.

Current toolbox

Tools chosen around the problem.

Tools change. I choose them around the problem rather than building the problem around the stack.

AstroTypeScriptJavaScriptWordPressCloudflareWorkersGitHubAPIsDNSEmail infrastructureStructured dataAutomationAI-assisted development

Secure by practice

Data protection is part of how I build.

I treat privacy, security, and responsible data handling as design requirements—not work to add after a system is finished.

Data minimisation

Collect and retain only the information a system genuinely needs.

Access control

Limit sensitive data and administrative actions to authorised people and services.

Secure delivery

Use encrypted connections, security headers, validation, and careful deployment practices.

Recovery and review

Plan backups, safe change management, monitoring, and recovery before they are needed.

Selected work

Things I’ve built to solve something specific.

These projects began with practical requirements—presenting complex information clearly, reducing repetitive work, connecting systems, or building a tool that did not exist in the form I needed.

Clamp Generator website showing responsive typography and layout tools

Developer tool

Clamp Generator

A browser-based utility for generating responsive CSS clamp() values and typography scales, created to make a recurring front-end task easier to calculate, preview, and reuse.

My path

I didn’t start as a developer.

I started in scientific research.

Development came later—first through managing websites and domains, then solving infrastructure problems, building tools, and eventually developing applications around real business workflows.

Research taught me to observe, test, question assumptions, and work systematically. Development gave me another place to apply that way of thinking.

A research mindset applied to development.

I usually begin by understanding the problem, identifying the constraints, separating assumptions from evidence, and testing what can fail before choosing the technology.

I care less about using the newest framework and more about whether the resulting system is clear, maintainable, secure, and genuinely useful.

Research-led personal website for Prabakaran Shankar

Academic web

Helping researchers build a stronger digital presence.

Good research can still be difficult to discover outside publications and institutional profiles. I’m interested in building digital systems that make a researcher’s expertise, publications, projects, methods, and scientific contributions easier to find, understand, and connect.

As search increasingly includes AI-assisted discovery, clear structure, authoritative content, and machine-readable research information matter more than simply having another website.

Commercial academic website projects are delivered through NViews Web.

Connect

Have something interesting to discuss?

Whether it’s a system I’ve built, a technical problem, research technology, or an unusual idea worth exploring, I’m always interested in a useful conversation.