Object / IdentityMaciej Trzciński
ROOT_NODE { schema: "Identity" }

I build the content layer technical products scale on.

Schemas and content models for technical product companies — built to survive the third page type, and clean enough for AI agents to generate from. Hackathon mentor on the side.

YEARS / REACT
7+
GREENFIELD
0→1
BASED
EU / REMOTE
Object / Identity
Maciej Trzciński
name
"Maciej Trzciński"
role
"Content Infra Eng"
loc
"Poznań, PL"

About Maciej Trzciński

SELECT * FROM identity

Maciej Trzciński is a content infrastructure engineer based in Poznań, Poland, working remotely with technical product companies worldwide. He designs the schemas, content models, and CMS architecture that products publish on — typically in TypeScript, React, and Next.js with Sanity, Vercel, and Supabase — and migrates teams to headless CMS in-flight, without a content freeze. He also mentors hackathon teams on scope-cutting and rapid prototyping.

fn lookup_capabilities()

The Toolkit

A content infrastructure engineer designs the schemas, content models, and CMS architecture a technical product publishes on — the layer beneath the content, built so new page types scale without a rebuild and structured data stays correct for both search engines and AI agents.

Key: 0x01

Content Infrastructure

Schemas, content models, and the CMS architecture beneath them. Structured so new page types scale without a rebuild — and so structured data stays correct across every surface.

type: "Architecture"strict: true
Key: 0x02

0→1 Product Engineering

Greenfield Next.js. Stack picked from the product's actual constraints — TypeScript, React, Sanity, Vercel, Supabase. Owned end-to-end when solo, contract-bound when in a team.

stack: "Next.js"scope: end_to_end
Key: 0x03

Design Systems & Architecture

Reusable TypeScript/React component libraries documented in Storybook. Stack selection, state-management patterns, contract design, data-layer migrations. The boring foundations multiple product surfaces sit on.

docs: "Storybook"reuse: yes
SELECT * FROM offers

Where I Can Help

  • Key: 0x01Content.Infrastructure

    Your CMS can't grow past one page type.

    Schema and content-model design for technical product companies. Structured so marketing can add page types without an engineer in the loop.

    SanitySchema DesignContent ModelingTypeScript
  • Key: 0x02CMS.Migration

    Your CMS is slowing marketing down.

    Headless content migration to Sanity. Schema restructured so marketing can add page types without an engineer in the loop. Done in-flight, without a content freeze.

    SanityMigrationIn-flight
  • Key: 0x03Design.Systems

    Your component library isn't surviving the scale.

    Reusable TypeScript/React component libraries documented in Storybook. Consumed across multiple product surfaces without forking. Theming, accessibility, and a contract that holds.

    StorybookTypeScriptTailwinda11y
ALSO_AVAILABLE

Greenfield 0→1 product builds and human drop-in on Next.js — same stack, by arrangement.

ERD // content_infrastructuremigrates_toreferenceshas_manyconsumescreates · no_engineerContent.Infrastructurecms: Sanityschema: Strictmodel: ContentCMS.Migrationtarget: Sanitymode: In-flightfreeze: noneDesign.Systemsdocs: Storybookcss: Tailwinda11y: WCAGPageType.Newscale: Autorebuild: falseMarketing.Teamowns: Contentengineer: none
const PHILOSOPHY = {

Rules

The product lens — how I think about building content infrastructure, greenfield or already in flight.

prop: "Stack_From_Constraints"

A stack should fit the product's actual shape — content types, who edits, who consumes. Picked from constraints, not from a house template.

prop: "Model_First"

Schemas decide whether a site scales. A model that bends on the third page type is the one you rebuild in year two — design it before the first screen lands.

prop: "Beyond_The_Demo"

Content stacks live with real authors, real edge cases, and real scale — not the live demo. The boring foundations are what ship the product.

prop: "Year_Three_Default"

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. 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.

  • 0x01Mar 2026
    IDEA2IMPACT Hackathon
    MentorGdańsk, PL
  • 0x02Jan 2026
    European Critical Infrastructure Hackathon
    MentorGdańsk, PL
  • 0x03Dec 2025
    HackNation PL — 1500+ participants
    MentorBydgoszcz, PL
  • 0x042025
    Hackathon for Builders
    Co-organiserPoznań, PL
  • 0x052024
    ADPList Meetups
    Co-organiserPoznań / Warsaw, PL
-- 5 rows
FIELD_NOTES / recent
IMG_01
Mentoring teams at HackNation PL 2025 in Bydgoszcz
refhacknation_25
locBydgoszcz
IMG_02
European Critical Infrastructure hackathon in Gdańsk, January 2026
refcrit_infra_26
locGdańsk
IMG_03
Hackathon for Builders, Poznań
refbuilders_25
locPoznań
IMG_04
HackNation PL 2025 participants at work
refhacknation_25b
locBydgoszcz
SELECT * FROM packages

Open Source

Open-source packages and reference apps I maintain — published for anyone to use, fork, or build on.

-- 4 rows
STATUS_UPDATE / currently
Tonik

Four years building content infrastructure for technical product companies.

Stack

TypeScript, React, Next.js, Sanity, Vercel, Supabase.

Community

Active mentor in the European hackathon ecosystem.

initialize_handshake()hello@trzcinski.org

Need a content infrastructure engineer, a human pair of hands on a Next.js build, or a mentor for your hackathon? Any of the above.