Knowledge hub
The technologies and tools I work with. For each one I explain when it fits and when something else is the better choice.
E-commerce
- Headless commerceA store split into a front end and an engine joined by an API: what it gives, what it adds and when it pays off.
- Medusa.jsAn open-source commerce engine for stores whose rules don't fit a ready-made platform.
- Multi-vendor marketplaceOne site with many sellers: commissions, order splitting and payouts as decisions to make before launch.
- ShopifyA ready-made store platform for a standard buying process and a fast launch, also as a headless back end.
CMS & content
Frontend
- Next.jsA React web framework with server components, caching and deployment on your own server.
- AstroA framework for content sites: HTML at build time, JavaScript only in islands, content from a CMS.
- ReactA library for component-based interfaces, with state, Server Components and a compiler.
- Tailwind CSSA CSS framework of utility classes: tokens in CSS, only the rules in use generated, a consistent look across components.
- TypeScriptJavaScript with syntax for types: the compiler checks the shape of data and plain JavaScript comes out.
Backend & APIs
- Node.jsA JavaScript runtime outside the browser with an event loop, used for APIs and services: Node.js.
- Better AuthA TypeScript sign-in library: users and sessions live in your own app database, not with a vendor.
- FirebaseA Google platform with sign-in, a realtime database and cloud functions for mobile apps.
- GraphQLA query language for APIs with a typed schema, where the client asks only for the fields it needs: GraphQL.
- PostgreSQLAn open-source relational SQL database, ACID-compliant, the default under Payload CMS and Medusa.js.
- tRPCA TypeScript API library where server types reach the client with no schema and no code generation.
Mobile apps
Cloud & DevOps
- AWSS3, Lambda, AppSync, Cognito, CDK and SST: AWS as managed services instead of a server of my own.
- DockerContainers on a VPS of my own: the image, data in a volume and Coolify deployments.
- Google CloudGoogle Cloud Platform (GCP): Cloud Storage, Cloud Run and Identity Platform as managed services instead of a server.
- TerraformInfrastructure in files: plan, state and providers instead of console clicks, and when I prefer Pulumi.
Integrations
- AlgoliaHosted search over an index of records: attributes, ranking and facets. When it fits and when the database is enough.
- InPostParcel locker and courier delivery for an online store: choice at checkout, labels and statuses via API.
- KSeFIntegrating with the API of the Polish e-invoicing system: invoice data, test environment, outages.
- ResendSending email from an app through the Resend API: domain verification, React Email templates, idempotent sends.
- StripeOnline payments in a store and an app: choosing the flow, webhooks, idempotency and subscriptions.
AI
- OpenRouterA gateway to AI models of many providers: one API, routing, fallback models and the data on the way.
- RAGRetrieval-augmented generation: a model reads document chunks before it answers. When it fits, where it fails.
- Vercel AI SDKA TypeScript library for AI chats with streaming, tools and a swappable model provider.
SEO & analytics
- Core Web VitalsThree Google metrics judged on field data: loading, responsiveness and layout stability of a page.
- Google AdsConversion tracking built on GA4 events, with no campaign management.
- Google Search ConsoleOwnership verification, sitemap submission and indexing monitoring.
- Google Tag ManagerContainer, Data Layer and Consent Mode: when GTM fits and when direct code wins.
- Meta PixelPixel and Conversions API with event deduplication and a consent gate.
- SitemapSitemap audit, canonical URLs and robots.txt alignment.
- Structured data (Schema.org)Page content described in Schema.org as JSON-LD: what to mark up, what to skip, and the end of FAQ rich results.
Considering a technology that isn't listed? Describe your project, and I'll tell you straight whether and how I work with it.