Skip to content
Back to projects
lab

SharapovLab — Personal Brand & Technology Laboratory

SharapovLab itself: a personal technology laboratory focused on AI systems, blockchain, automation and future digital products.

Founder / Architect

Private project

Overview

SharapovLab is a personal technology laboratory focused on AI systems, blockchain, automation and future digital products — and this site is itself one of its projects: a no-database, MDX/JSON-driven platform with a private Git-backed dashboard.

Problem

A personal brand site is usually either a static resume template or a heavyweight CMS with a database to maintain. Neither fits someone who wants full control over content as code, without operating a database or a generic CMS.

Solution

SharapovLab is built as a statically-prerendered React application where every project, service and article is a version-controlled MDX/JSON file — "Git is the database" — edited through a private, owner-only dashboard that commits directly to the repository.

Architecture

  • React
  • TypeScript
  • Node.js
  • AI Agents
  • Web3 Technologies
  • React + TypeScript frontend, statically prerendered per locale/route for crawlers (search engines and AI assistants alike).
  • Node.js-based serverless functions handle the dashboard's content commits and contact form.
  • Content lives entirely as MDX + JSON — no database, ever.
  • The platform's own content pipeline is designed to support AI agents and future automation as first-class citizens, not just human editors.

Features

  • Bilingual (English/Russian) content and interface, per page.
  • Private dashboard gated to a single owner account, editing MDX/JSON directly.
  • SEO and AI-crawler-oriented structured data on every page.

Technologies

  • React
  • TypeScript
  • Node.js
  • AI Agents
  • Web3 Technologies

Gallery

In development — visual materials will be added as the platform evolves.

Videos

No video published yet.

Roadmap

  1. Content engine + public site

  2. Private dashboard with GitHub-backed persistence

  3. Full analytics + SEO tooling

Challenges

Keeping "no database" genuinely true while still supporting a working content-editing dashboard in production required routing every save through the GitHub API instead of the filesystem — the core architectural decision behind the whole platform.

Lessons

To be added as the platform matures further.

Future

SharapovLab is in active development — this project page will keep pace with the platform itself.

GitHub

In development — repository details will be added here once finalized.

Demo

You're using it right now.

FAQ

Is this website itself a SharapovLab project?

Yes — the site, its dashboard and its content pipeline are one of SharapovLab's own projects.

Why no database?

Content is version-controlled as MDX/JSON files, edited through a dashboard that commits directly to Git — so Git itself is the database.