I use Craft CMS for projects that need a flexible content structure, a clear editorial panel and better control over the codebase than a standard template can provide.
My work includes corporate websites, content platforms and custom Craft CMS plugins. I also handle PHP and Twig optimization, integrations with external systems and caching layers based on Varnish, Cloudflare or CDN services.
Craft CMS is often a good fit when the website needs to grow over time without becoming difficult to manage.
Below you can find selected implementations and plugins built around practical business requirements.

Varnish Cache integration with ISPConfig 3, Nginx SSL and Apache for WordPress and Craft CMS, with purging, Cloudflare and Brotli support.

Craft CMS plugin for automated cache purging and warming with Varnish, Cloudflare, sitemap processing, URL exclusions and queued jobs.

Craft CMS plugin for automated versioning of CSS, JavaScript and other static assets to prevent stale-cache issues after deployment.

Craft CMS plugin for generating PDFs from Twig templates, HTML and URLs, with Assets integration, caching, QR codes, watermarks and PDF/A or PDF/X support.

Craft CMS project for Sienkiewicz MAT-BUD with an interactive Mapbox project map, marker clustering and automated PDF datasheets.

Craft CMS website for Torpol Oil & Gas with service information for the oil, gas, chemical and energy sectors.

Craft CMS website for Dekofloor with structured service pages, project galleries, a contact form, location map and mobile-friendly layout.

Craft CMS website for a local initiative with news, interactive elements, a map and an editorial panel for day-to-day updates.
A good project starts with understanding the real problem. Before I write any code, I review the requirements, look at the current setup and suggest an approach that makes sense for the business, the budget and the expected scale.
I think about data protection, maintainability and failure prevention before development starts. These are part of the architecture, not fixes added later.
I optimize the code, database and server environment according to the way the system will actually be used. This includes everyday traffic, seasonal demand and predictable spikes during campaigns or product launches.
I explain the technical decisions in plain language. You know what is being built, why a particular solution was chosen and what alternatives were considered.
I do not treat projects as an assembly line. I work on a limited number of implementations at a time so I can stay involved in the details and make sensible technical decisions throughout the process.
You describe the project, the current problem or the planned changes. I review the requirements and usually reply within 24 hours with initial feedback, follow-up questions and an estimated scope of work.
Before development starts, we define the scope and select the right tools. Depending on the project, this may include WordPress, WooCommerce, Craft CMS, PrestaShop, custom PHP development, external integrations or Linux server configuration.
I handle the implementation, testing, deployment and performance tuning. After launch, I can also take care of updates, monitoring, further development and server maintenance when ongoing support is needed.