Overview
Jaskółka works across the Polish equestrian ecosystem, combining horse-related services, animal records, stable operations, sales, rentals, transport, and public-facing equestrian content.
The project combined two custom public websites, Jaskółka and Tinker.pl, with a shared headless CMS, external animal records, custom CMS workflows, and multi-site publishing logic.
The goal was to support different public surfaces while keeping content, animal-related data, services, prices, media, multilingual pages, and publishing decisions manageable from one structured content layer.
Instead of duplicating records between websites, content was modeled as reusable business data and rendered on the right public surface through CMS visibility rules, publishing states, external integrations, and static regeneration workflows.
Some internal workflows and data sources are private, so this case focuses on the public websites, CMS structure, publishing logic, integrations, and regeneration workflows that can be shown safely.
Contribution
I owned the end-to-end delivery of both public websites, from structure, visual direction, and UI design to frontend implementation, CMS integration, deployment, and launch.
I built reusable Next.js sections connected to structured CMS data, so public pages could be generated from editable content instead of hardcoded layouts.
I worked on custom CMS workflows for non-technical users, including multi-site visibility, pricing, galleries, drafts, previews, publishing states, validation, filtering, custom fields, and content controls.
I also integrated external animal-related records, allowing selected horse data and statuses to be reused inside public pages and CMS-driven workflows.
On the technical side, I connected the frontend with the headless CMS, external data sources, and custom webhook endpoints for ISR-based static regeneration when relevant collections were updated.
Multi-site Content System
One headless-based CMS powered two public websites, giving the owners a single place to manage content, assets, services, pricing, and publishing decisions.
Domain Content Model
Accommodation, activities, animals, attractions, services, prices, galleries, and posts were modeled as structured business entities instead of static page content.
Multi-site Visibility Control
Content could be shared selectively across Jaskółka and Tinker.pl, so owners could decide where each entry should appear without duplicating records manually.
Animal Records Integration
Animal-related data was connected through an external API, allowing selected records and statuses to be reused inside the public websites.
Editorial Workflow
The CMS supported roles, drafts, previews, and publishing states, making it safer for non-technical users to manage public content.
Validation & Filtering Rules
Admin workflows included validation and filtering logic to reduce content mistakes and keep business data predictable across public pages.
Static Publishing Pipeline
Public pages were generated with Next.js and ISR, while custom webhook endpoints triggered static regeneration when relevant CMS collections were updated.
Multilingual SEO-ready Pages
The websites supported multilingual content across PL, EN, DE, and NL, with SEO-oriented structure, metadata, pre-rendered pages, and performance checks.
Tinker
Jaskółka
