Projects and case studies

Each website went through five tools (Drive, Lovable, GitHub, FTP hosting, and a link shortener), with manual steps between them. There was no single view of where each client stood, and every manual step was a source of errors and rework.

Each project shows its current stage and next step in a single button, with batch generation and publishing. The client gets an approval link that stays the same when the site is rebuilt, and confirmation that a site is live comes from the actual workflow run. All credentials stay in the backend, and generation, the only paid step, runs only after it is explicitly enabled.

The briefing sets the delivery date of a website, but the 15-field form was abandoned halfway or came back with answers too short to write content from.

The server sets the script and validates every answer; the model only writes the text shown on screen. If the API is unavailable, the plugin keeps running in degraded mode with the same questions and the same submission, so the briefing always reaches the team by email with its attachments. The dashboard shows where people drop off and how long each question takes.

Non-technical clients got stuck on simple questions, such as what a domain is or how to attach images, and gave up or turned to the team.

Answers use only what is in the knowledge base, and pricing or out-of-scope questions go to human support. A server-side check blocks contacts, prices, and links that are not in the base, including while streaming. The dashboard groups questions that did not get a good answer, so the base is fixed with data.

Tracking happened in spreadsheets, with no central history, no access control, and no consolidated view of productivity and costs.

React, Express, and MySQL application with JWT authentication, access roles, dashboards, a delivery calendar, CSV import, and PDF reports. It also includes operational tools: uptime, SSL, and DNS monitoring for websites, and one-time links for sharing credentials.

Every release meant creating secrets, copying workflows, and finding the build folder of each framework by hand, repository by repository.

You pick the repository and enter the domain and credentials: the dashboard writes the encrypted secrets, generates the build and deploy workflows, and follows the run in real time. The GitHub token stays on the local server, which by default only accepts connections from the same machine.

Clients need websites that ship quickly, that their own team can edit, and that are looked after once they launch, without needing a developer for every change.

I build the layouts in WordPress with Elementor Pro and BeTheme and extend them in PHP where the builder falls short. After delivery, I handle migrations, DNS and SSL, updates, performance, and security. 41 client WordPress websites are live.

The companies needed the ERP adapted to their own business rules, with reliable production routines and integrations with other systems, without disrupting operations.

I gathered requirements directly with clients and implemented them in ObjectScript (InterSystems IRIS). I optimized SQL queries in critical routines, built REST API integrations, and investigated and fixed production issues.

Checking PDF payslips month by month is slow and error-prone, and the data stays locked in documents that cannot be compared over time.

The Flask back end extracts the entries with pdfplumber and regular expressions and classifies them as earnings or deductions. The React interface shows trends by period, each payslip in detail, and the monthly budget. AI analysis goes through the back end, which only accepts local connections.

Present my background, projects, and skills coherently in two languages, with the same content feeding both the website and the PDF CV.

Pages are prerendered at build time with SEO metadata and structured data. READMEs and the repository list come from GitHub during the build, and the CV and link-preview images are generated from the same content. Playwright end-to-end tests run in CI.

The signature was adjusted site by site, with no visual standard and no protection against unwanted changes.

A settings panel for status, light or dark logo, background color, and link. Images load from a CDN out of an approved repository, and sensitive settings are locked for users outside the company domain.

A study project to practice DOM manipulation, events, and chained operations.

Published on GitHub Pages, with an interface that adapts to desktop and mobile.

Explore animation, movement, and object behavior without external libraries.

A study published on GitHub Pages that spawns objects on demand and simulates their movement on screen.

A study project to practice mobile development: screen navigation, state, and local storage.

The app generates a password from a slider, copies it to the clipboard, and saves chosen passwords with AsyncStorage in a dedicated tab.