ROOT_NODE { schema: "Identity" }

I build the content infrastructure technical products publish on.

Schemas, content models, and the CMS architecture underneath. Built to survive the third page type without a rebuild, and to keep a redesign from becoming a six-month migration.

YEARS / REACT: 7+
YEARS / CONTENT INFRA: 4
BASED: EU / REMOTE
SANITY: PIONEER 2026

Let's talk See where I help

Object / Identity

name
role
loc

SELECT * FROM identity

I'm a content infrastructure engineer in Poznań, Poland, working remotely with technical product companies. I design the schemas and content models that sit underneath the product — the layer that decides whether a CMS scales with the team or turns into six-month migration debt. The work is content modeling, Sanity schema design, and headless CMS architecture that doesn't lock you into a vendor or a rewrite in 18 months. Usually TypeScript, React, and Next.js with Sanity, Vercel, and Supabase; where a stack already exists, I migrate it onto headless CMS.

SELECT * FROM packages

Open Source

One page-builder toolkit for Sanity: typed schema primitives, a Studio plugin for composing pages from sections, and runnable Next.js and Astro reference apps. A new Sanity plugin is in progress — it'll land here when it ships.

0x01

@maciejtrzcinski/sanity-page-builder-core

Type-safe page-builder primitives for Sanity.

npmv1.0.2236/mo

0x02

@maciejtrzcinski/sanity-plugin-section-builder

Studio plugin for composing pages from sections.

npmv1.0.076/mo

0x03

sanity-page-builder-astro-example

Astro reference app for the page builder.

github★ 02026.06

0x04

sanity-page-builder-example

End-to-end Next.js example, ready to clone.

github★ 02026.09

-- 4 rows

SELECT * FROM role

Content Infrastructure Engineer

A content infrastructure engineer designs the schemas, content models, and CMS architecture a technical product publishes on — the layer beneath the content. Done well, new page types scale without a rebuild, and a redesign or a change of CMS doesn't turn into a migration project.

SELECT * FROM offers

Where I Help

Key: 0x01Content.Infrastructure
Your CMS can't grow past one page type.
Schema and content-model design for technical product companies, built fresh or restructured in place. Marketing adds page types without an engineer in the loop. Migrations to Sanity run in-flight, without a content freeze. The model is structured so the next redesign or CMS change isn't another migration.
SanitySchema DesignContent ModelingMigration
Key: 0x02Greenfield.Build
You need version one in front of users this quarter.
Greenfield product builds in TypeScript, React, and Next.js — empty repo to something real users touch. Scope cut to what ships, with the content model designed before the first screen lands.
TypeScriptNext.jsVercelSupabase
Key: 0x03Design.Systems
Your component library gets forked instead of used.
Reusable TypeScript/React component libraries documented in Storybook, consumed without forking. Theming, accessibility, and a contract that holds.
StorybookTypeScriptTailwinda11y

ALSO_AVAILABLE

Hackathon and prototype mentoring — scope-cutting for 24–72h delivery, by arrangement.

-- ERD: content_infrastructure

const PHILOSOPHY = {

The Product Lens

How I think about building content infrastructure. Same lens whether the stack is greenfield or already in flight.

prop: "Stack_From_Constraints"

A stack should fit the product's actual shape: what the content types are, who edits them, who consumes them. Read those first, then pick.

prop: "Model_First"

Schemas decide whether a site scales. A model you can't extend becomes a rebuild in year two, and usually a migration off the CMS with it. Design it before the first screen lands.

prop: "Beyond_The_Demo"

A demo has one author and no edge cases. Production has neither. The boring foundations are what ship the product.

Production code is a longer game than a demo. What ships in week one is what runs in year three. Build for the year-three version.

SELECT * FROM community

Community

Active mentor in the European hackathon ecosystem since 2024, including HackNation PL at 1,500+ participants. Co-organiser of Hackathon for Builders (Poznań) and ADPList meetups (Poznań / Warsaw). Mentoring focus: scoping MVPs for 24–72h delivery and helping teams cut scope to ship.

keyperiodevent

roleloc