Growth engineering and content platforms

Abstract measurement rings and a crawl graph

Site generators, browser extensions, and monorepos: templates, metadata pipelines, crawl-friendly structure, and repeatable publishing at scale.

Discuss this scopeContact form

Tell me the goal, stack constraints, and timeline — I reply on Telegram.

Scaling organic visibility is mostly engineering discipline: consistent templates, correct metadata, and automation your team can maintain. I build tooling and generators, not one-off tricks.

Need AI Overviews and chat-assistant visibility? See SEO, AEO & GEO.

Representative work

Recent deliveries include seo-sites-generator and revisitor—systems where growth engineering and content platforms skills (TypeScript, Node.js, site generators, browser extensions, monorepos, templates, metadata, content pipelines, automation, AI-assisted drafts) were applied end to end.

Those projects combined product UI, APIs, and operational concerns: roles, exports, integrations, and observability. The goal is always software your team can extend—not a one-off demo that collapses under real users.

Typical collaboration starts with a written brief: constraints, integrations, compliance, and what “done” means for the first release. We slice work into vertical milestones so you see progress every one to two weeks and can reprioritize without losing the thread.

After go-live we offer a short hypercare window: fix edge cases, tune performance, and transfer knowledge. Long-term support can stay with your in-house team or continue as a retainer—your choice.

We document decisions in plain language, keep staging environments aligned with production, and leave runbooks so your team is not blocked after handoff. If you already have designers or backend engineers, we plug into your rituals instead of inventing a parallel process.

Acceptance criteria

Done when

  • Agreed generator/extension flows run without manual hacks
  • Metadata templates produce valid output on sample set
  • Pipeline steps are documented for the editor

Deliverables

  • Repo + usage notes
  • Sample configs / templates

Out of scope

  • Unlimited content production

The final acceptance checklist is confirmed in the brief or contract; the list above is a scope alignment guide.

Selected portfolio work

All projects
seo-sites-generator

seo-sites-generator

Monorepo platform to generate and customize SEO-oriented websites: frontend, backend, AI service, SEO engine, templates and deployment workspaces. Focus on automation and repeatable content pipelines.

Details
revisitor

revisitor

Re-engagement and revisit tracking service in TypeScript. Node APIs for scheduling callbacks, lightweight analytics, and integration hooks.

Details
lagrant-seo-extension

lagrant-seo-extension

Browser extension supporting SEO checks and grant-site workflows for Lagrant. TypeScript-first tooling integrated with editorial habits.

Details

How I work

Request

You describe the goal, constraints, timeline, budget, and infrastructure.

Clarify

I ask questions, review existing code or a brief when needed, and lock scope.

Plan

I propose stages, priorities, and a timeline range; we agree on reporting.

Build

Iterations with intermediate results: commits, demos, and feedback.

Handoff & support

Deploy and docs as needed; we agree on maintenance or targeted follow-ups.

FAQ

Tap a question to expand the answer.

What is a site generator in your practice?

A template + data pipeline that outputs many consistent pages (landings, locales, metadata) instead of copy-pasting folders by hand.

How is this different from SEO/AEO/GEO?

This track is engineering for scale (generators, extensions, monorepos). SEO, AEO & GEO is visibility in search and AI answers.

Do you use AI to write content?

AI can draft; humans keep editorial control, fact checks, and guardrails so quality does not drift at scale.

What does a monorepo setup give us?

Shared types, one CI pipeline, coordinated releases across frontend, backend, and tooling—fewer drift bugs across site networks.

Can a Chrome extension be part of the platform?

Yes—extensions for research, metadata capture, or publishing workflows that feed the same generator or CMS.

Discuss this scopeContact form

Tell me the goal, stack constraints, and timeline — I reply on Telegram.