spoko.space's Blog

Parts & Accessories Catalog

Thu, 02 Apr 2026 00:00:00 GMT

## VW Polo 6R Parts and Accessories Catalog A comprehensive, multilingual catalog of genuine OEM parts and accessories for the Volkswagen Polo 6R/6C, built with a fully decoupled headless architecture. The Astro-powered static frontend consumes a Laravel REST API at build time, producing pure HTML pages with zero runtime database queries. While not an e-commerce site, it shares many features with online stores — product listings, filtering, search, detailed specifications — except for payment processing. The project has evolved through several iterations: from an early Vue 2 SPA, through Vue 3, to the current Astro 6 SSG setup with Vue 3 islands for interactive components. ## Architecture: Headless CMS + Static Frontend The system is split into two independent repositories: **Frontend** ([catalog.polo.blue](https://catalog.polo.blue)) — Astro 6 static site generator with Vue 3 components, UnoCSS styling, and a custom design system. All data is fetched from the API exclusively during the build step. The browser never contacts the backend directly (except for client-side tools like the PR Codes Decoder). **Backend** — Laravel 13 application serving a REST API and a Filament 5 admin panel. Manages products, categories, translations, media, SEO data, and site deployments. Backed by MySQL, Redis (queues via Laravel Horizon for background jobs like image conversion, translations, and site builds), and Cloudflare R2 for CDN storage. Site deploys can be triggered directly from the admin panel. This separation means the frontend is a pure static site — fast, secure, and globally cacheable via Cloudflare CDN. ## Image Pipeline & CDN A key challenge was optimizing images given the extensive product catalog and predominantly mobile traffic. The solution evolved from build-time compression via Sharp/Astro to a backend-driven pipeline: 1. **Upload** — Images are stored on Cloudflare R2 (S3-compatible) via Spatie Media Library 2. **Conversion** — Background queues generate responsive thumbnails in modern formats (AVIF with WebP fallback) 3. **Delivery** — Served from `cdn.polo.blue` with denormalized URLs stored directly on Product/Category models to eliminate JOIN queries in list views 4. **Monitoring** — A CDN Stats widget in the admin panel tracks total storage, per-model breakdown, and the percentage of products with all AVIF conversions complete WebP serves as a fallback to AVIF due to its still limited indexing in Google Image Search. ## Multilingual Support & Automated Translations The catalog supports three languages — English, Polish, and German. All translatable content (products, categories, colors, materials, PR codes, FAQ entries, and more) shares a single unified translation system, so adding a new language requires no schema changes. - **DeepL API** automatically translates content from English into Polish and German via queued background jobs - **AI-generated descriptions** use a multi-provider fallback chain to generate English copy, which is then translated by DeepL - Per-locale URL structures (`/` for EN, `/pl/` for Polish, `/de/` for German) with properly configured `hreflang` tags - Static UI strings loaded from JSON files, content translations served already localized by the API ## Performance Optimizations ### Split Build System Building all three locales in a single Astro pass caused memory exhaustion (10-20 GB RAM). The solution: a custom split build script that processes one locale at a time, runs Pagefind indexing per locale, then merges everything into the final `dist/` directory. Total build time: ~4-5 minutes for all locales. ### API Call Reduction A category prefetch cache fetches all products per main category in a single API call, then filters locally. This reduced ~60 individual API requests to a handful of batch calls during build. ### Frontend Performance - `content-visibility: auto` on off-screen product rows to reduce rendering cost - Sidebar collapse state restored from `localStorage` before first paint to prevent CLS - Font preloading (VW brand fonts), preconnect to CDN and analytics domains - Vite manual chunks separating vendor code (Vue, design system) from page code - First 3 product images loaded eagerly, with `fetchpriority="high"` on the very first image; rest lazy-loaded ## SEO & Discoverability Strong SEO has been a primary driver of traffic, especially from image search engines. Key strategies include: - **Structured Data (JSON-LD)** — Rich `@graph` markup with `IndividualProduct` (not `Product`, to signal non-merchant catalog), `BreadcrumbList`, `ItemList` for category pages, and `Organization` entities - **XML Sitemaps** — Generated server-side per locale and type (products, categories, pages), fetched at build time with XSL stylesheets for browser-readable display - **llms.txt** — AI/LLM discoverability files following the llmstxt.org specification - **Internal linking** — Related Products, Similar Products, and in-category navigation buttons (validated via A/B testing) improve link equity and user flow - **Pagefind** — Offline full-text search indexed per locale, with no external dependencies - **SEO Dashboard** — Admin panel widgets audit short/long titles, missing descriptions, and data completeness across all three languages ## Interactive Tools Three client-side Vue 3 tools enhance the catalog's utility: - **Tire & Wheel Calculator** — Compares two tire/wheel configurations, calculates diameter differences and speedometer deviation, with SVG visualization - **Power Converter** — Converts between HP, kW, and PS with a visual bar chart - **PR Codes Decoder** — Decodes VW factory option codes (3-character codes) by querying the API, with client-side caching These tools are isolated in a separate Astro route to prevent their CSS (~25 KB) from affecting the main catalog pages. ## Backend & Admin Panel The backend, powered by **Laravel 13** and **Filament 5**, delivers the REST API and provides a comprehensive admin panel organized into functional clusters: ### Content Management - Product management with detailed specifications, PR codes, engine compatibility, and multi-language support - Hierarchical category organization with icon and OG image management - CMS page builder with 13 block types (hero, jumbotron, carousel, CTA, FAQ, statistics, etc.) - Translation management with DeepL batch automation and protection flags for critical translations ### REST API The API uses configurable response presets to control the depth of included data per endpoint — keeping responses lean for listings and rich for detail views. HTTP cache headers are tuned per route to maximize CDN hit rates. ### Analytics & Monitoring Dashboards - **Google Analytics 4** — Page views, visitors, sessions, devices, top referrers, geographic data (14 widgets) - **Google Search Console** — Clicks, impressions, CTR, average position, top pages and queries - **Core Web Vitals** — CLS, LCP, INP time-series tracking - **Google AdSense** — Multi-site earnings tracking with alerts for revenue drops ### Operations & Maintenance - One-click site deploy triggering Astro builds via queued jobs (separate `site-build` queue to avoid blocking translation/media jobs) - Cloudflare cache purging by URL, prefix, or model type - Database backup/restore utilities - Activity logging and full audit trail - Data completeness dashboard auditing missing media, translations, descriptions, and link quality ### Redirects & 404 Recovery A custom redirects module baked into the Filament admin turns broken URLs into a data-driven recovery workflow rather than a manual chore: - **CSV import from GSC and Ahrefs 404 reports** — URLs are uploaded in bulk with the source tagged on each entry (`gsc_404`, `ahrefs_404`, `manual`, `import`), so editors prioritize by real traffic impact rather than guess - **GSC context preserved per redirect** — clicks, impressions, and first/last detection dates stay attached to the row and are visible in the list view — you see at a glance which 404s were actually costing organic traffic - **Auto-resolution of crawl errors** — creating a redirect automatically marks matching unresolved `GscCrawlError` rows as resolved and links them back to the redirect ID, with the resolver user and timestamp logged - **Self-redirect prevention** — the model throws on save if `old_url === new_url` after path normalization (case is preserved, since URLs like `/6R0601025AEZ49/` vs `/6r0601025aez49/` are distinct) — infinite loops are caught before they hit production - **Regex patterns, soft deletes, full audit trail** via Spatie Activitylog, support for 301/302/307/308, plus `hit_count` and `last_hit_at` surfacing stale redirects that are safe to clean up ### WordPress Comments — Notifications & Replies The blog side of polo.blue runs on headless WordPress, but its comments are moderated entirely from the Filament panel — admins never have to open `wp-admin` to handle the daily stream: - **Two-way sync with the WP REST API** — `WordPressCommentSync` pulls new pending and approved comments incrementally (cached cursor with a one-minute overlap to guard against clock skew between WP and the panel) and pushes moderation actions back via `/wp-json/wp/v2/comments` - **Full moderation from the panel** — approve, mark as spam, move to trash, and reply — all without leaving Filament. Replies are posted back to WP as child comments, auto-approved, and linked on the parent row (`wp_reply_id`, `replied_by_user_id`, `replied_at`) so it's always clear who answered and when - **Push notifications on new pending comments** — admins receive a notification (title + author + post title, with a deep link to `/admin/blog-comments`), so no pending comment waits for a manual poll of `wp-admin` - **Multilingual aware** — each comment inherits the source post's language (EN/PL — the blog is maintained in two languages), making it filterable by locale in the list view - **Post metadata cached** — post titles and permalinks are resolved once per batch and reused for subsequent comments, eliminating redundant WP REST calls during sync - **Escape hatch** — every row still exposes `wpAdminUrl()` as a direct jump to the WP admin edit screen, for the rare cases when the native interface is required ### FAQ Knowledge Base The catalog includes an integrated FAQ system providing technical specifications and how-to guides for VW Polo 6R. Content is organized by product categories (tires, wheels, engine oil, HVAC, brakes, suspension, body parts) and supports multilingual display with links to detailed blog posts. ## Deployment The frontend uses an atomic deployment strategy: - Push to `main` triggers GitHub Actions - Astro split build runs on the hosting server - Each release gets a timestamped directory; `public_html` is a symlink - Rollback takes under 1 second by re-pointing the symlink to a previous release ## Used Technologies Strong SEO, image optimization, and structured data have driven significant organic traffic — particularly from image search engines — while the headless architecture keeps the site fast, secure, and easy to maintain.

Uper SEO Auditor

Wed, 28 Jan 2026 00:00:00 GMT

## Professional SEO Tool for Developers Chrome extension for comprehensive SEO analysis directly in browser Side Panel. Uper fills the gap between simple meta-tag readers and heavy crawlers, offering real-time debugging for modern SPA applications. Tool built by Senior Software Engineer with years of experience in technical audits and frontend optimization. ## Core Features ### Web Vitals with SPA Support Continuous monitoring of **LCP, CLS, and INP** with native *Soft Navigations* support. Plugin correctly collects metrics in React, Next.js, and Vue applications, where traditional tools only measure performance during hard page reloads. Instant notification of metric degradation without launching Lighthouse. ### Google Services and DataLayer Debugging Verification of Google Tag Manager events, Consent Mode status, and detection of CSP or Ad-blocker blocks "on the fly". DataLayer Inspector shows all events pushed to the data layer with every user interaction. Eliminates the need to launch heavy GTM debugging modes. ### Design System and Tech Stack Detection Automatic color extraction with export to Tailwind, UnoCSS, or CSS variables. Precise identification of frameworks (Vue.js, React, Next.js), UI systems (Bootstrap, Tailwind), CDN infrastructure, and analytics tools. Detailed list of fonts, their weights, and loading sources. ### Content and Meta Tags Analysis Realistic SERP preview with title and description length validation. Heading hierarchy analysis (H1-H6) and keyword density statistics (single words, bigrams, trigrams). AI support for content optimization directly in Side Panel. ### Sitemap Analyzer Built-in crawler for mass auditing hundreds of URLs from sitemap in seconds. Plugin automatically detects sitemap.xml and allows verification of HTTP statuses, meta tags, and response times. CSV export of results for further analysis or reporting. ### Schema.org and Structured Data Validation of JSON-LD, Microdata, and RDFa with built-in Schema.org definitions database. Detection of structural errors and missing properties required by Google Rich Results. Preview of Search Console rendering. ### Side Panel as Command Center Native Chrome Side Panel enables work without context switching. Ability to freely navigate the site, test purchase paths and forms with real-time metrics preview. One-click PDF report export. ## Technologies The plugin is regularly updated with new features and available for free in Chrome Web Store.

Garage Inventory Management System

Sun, 19 Oct 2025 00:00:00 GMT

## Private Garage & Workshop Management I developed a comprehensive inventory management system to organize my garage and workshop. The system handles automotive parts, tools, and consumable materials with precise location tracking and QR code scanning capabilities. ## Core Features ### Multi-tier Inventory Organization The system uses a hierarchical structure for precise item location: - **Locations** - Physical spaces (shelves, wall mounts, floor areas) with capacity tracking - **Containers** - Boxes, organizers, and bins assigned to locations - **Items** - Products, tools, and materials stored in containers or directly at locations Each level supports QR code generation and scanning, enabling quick inventory operations via mobile device. ### QR Code Scanning System Every entity (products, containers, locations, tools, materials) has a unique QR code for: - Quick item lookup by scanning - Bulk inventory operations - Container content verification - Location-based item search - Mobile-friendly warehouse navigation ### Public PWA Interface A separate mobile-friendly web app allows browsing inventory without logging into the admin panel: - QR code scanning for quick product/container/location lookup - Grid and list views with stock status indicators - Container and location overview pages with product listings - Touch-optimized interface for warehouse use ### Parts for Sale Integration Items marked for sale are exposed via REST API and displayed on a separate Astro-based storefront. The system supports: - Dual-language product descriptions (Polish/English) - Automatic price conversion (PLN/EUR via NBP rates) - Shop status tracking (available, reserved, sold) - SEO-friendly slugs generation - DeepL-powered automatic translations ### Tools & Materials Management Beyond car parts, the system tracks: - **Tools** - Categorized workshop equipment (wrenches, pliers, power tools, measuring instruments) - **Materials** - Consumables with expiry date tracking and low-stock alerts (adhesives, fluids, chemicals) ## Technical Implementation ### Transaction & Audit System Every inventory movement is recorded: - Receipt, issue, and transfer transactions - Automatic quantity updates - Location change history - Complete audit trail via Spatie Activity Log ### Admin Panel with FilamentPHP The FilamentPHP-based dashboard provides: - Grid and list views with advanced filtering - Bulk operations (move items, change locations, toggle for-sale status) - Excel exports with customizable filters - Low stock alerts and expiry warnings - Kanban board for task management - Role-based access control ## Used Technologies This private project streamlined garage organization and enabled selling unused parts through automated e-commerce integration.

Enhanced WP REST API Plugin

Wed, 20 Aug 2025 00:00:00 GMT

## Enhanced WordPress REST API I developed an open-source WordPress plugin that extends the REST API specifically for headless CMS architectures. The plugin enables WordPress to function as a robust backend API while modern frontend frameworks like Astro, Next.js, or Nuxt handle the presentation layer. ## The Problem WordPress's default REST API provides basic functionality but lacks essential features for production headless implementations: - Incomplete data structures requiring multiple API calls - Absolute URLs causing issues across environments (dev, staging, production) - No built-in analytics integration for popular posts - Limited multilingual support - Missing headless mode redirects - No custom taxonomy ordering This plugin solves these challenges with a comprehensive set of enhancements designed from real-world headless WordPress projects. ## Key Features ### Enhanced Data Structure The plugin enriches standard REST API responses with additional fields that frontend applications need: **Extended Author Data** - Complete author information including ID, name, nicename, avatar URL, description, and relative author page links in a single response. No need for separate `/users` endpoint calls. **Multiple Image Sizes** - The `featured_image_urls` field provides all registered WordPress image sizes (thumbnail, medium, large, full), eliminating the need for additional API calls to fetch different dimensions for responsive images. **Reading Time Estimates** - Automatic calculation of estimated reading duration based on content length (e.g., "5 min read"), useful for blog layouts and improving user experience. **Rich Taxonomy Information** - Expanded category and tag data with descriptions, post counts, parent category IDs, and relative URLs in the main post response. ### Environment-Agnostic URLs All URLs in API responses are converted to relative paths (e.g., `/blog/post-name/` instead of `https://example.com/blog/post-name/`). This applies to: - Post permalinks - Author page URLs - Category and tag archive URLs - Featured image URLs - Translation URLs (when Polylang is active) **Benefits:** - Consistent behavior across development, staging, and production environments - No need for environment-specific configuration or search-replace operations - Easier deployment workflows and testing - Frontend can construct full URLs with its own domain ### Polylang Integration Seamless multilingual support when [Polylang](https://polylang.pro/) plugin is active: **Translation Data** - The `translations_data` field exposes all available translations for posts, categories, and tags with complete information: - Post translations include ID, title, slug, excerpt, status, featured image ID, and relative link - Category/tag translations include ID, name, slug, and relative link - Perfect for building language switchers in headless frontends - **Critical for SEO** - enables proper `hreflang` tag implementation in Astro and other frontend frameworks, which was previously impossible to achieve efficiently without this data in the REST API response **Available Languages** - Lists all site languages in the `available_languages` field **Language Filtering** - Automatic language-aware API queries respect current language context **Why this matters for SEO:** Without the `translations_data` field, implementing proper hreflang tags in a headless architecture would require additional API calls for each translation, making it impractical for static site generation. This plugin solves this problem by providing all translation URLs in a single response, enabling search engines to correctly identify language variants and serve the right content to users. ### GA4 Analytics Integration Fetch popular posts based on real Google Analytics 4 pageview data instead of simple view counters: **Features:** - Posts ranked by actual pageviews from GA4 - Configurable time periods: 7, 14, 30, or 90 days - Language filtering for multilingual sites (Polylang integration) - Smart caching with configurable duration (1-24 hours) - JWT-based service account authentication - No Google SDK required - lightweight implementation using WordPress HTTP API **API Endpoint:** ``` /wp-json/wp/v2/posts/popular?limit=6&period=7d&lang=pl ``` **Response includes:** - Post data with all enhanced fields - Pageview counts for each post - Cache status and timestamp - Total results and period information This enables dynamic "trending posts" sections based on actual user behavior, perfect for increasing engagement and content discovery. ### Headless Mode Optional complete frontend redirect functionality for true headless WordPress: **How it works:** - 301 redirects send all frontend visitors to your headless application - Original URL paths are preserved for SEO (e.g., `/blog/post-slug` → `https://frontend.com/blog/post-slug`) - Admin panel remains accessible for authorized users (`edit_posts` capability) - REST API, GraphQL, WP-CLI, and CRON continue functioning normally **Benefits:** - Maintain WordPress as a pure backend/CMS - Prevent duplicate content issues - Proper SEO-friendly redirects - No need for separate headless mode plugins ### Custom Taxonomy Ordering Support for ordered categories and tags via `term_order` parameter: ``` /wp-json/wp/v2/categories?orderby=term_order /wp-json/wp/v2/tags?orderby=term_order ``` Respects manual taxonomy ordering from plugins, ensuring consistent navigation across WordPress admin and headless frontend. Categories default to ascending order. ### Comments API Enhancement Optional REST API configuration for anonymous commenting: - Allow unauthenticated comment submission via REST API - Configurable moderator email notifications for new comments - Perfect for Jamstack contact forms and headless comment systems - All configured through WordPress admin panel ## Code Example ```javascript // Fetch posts with all enhanced data fetch('/wp-json/wp/v2/posts') .then(res => res.json()) .then(posts => { const post = posts[0]; // Relative URLs ready for frontend console.log(post.relative_link); // "/blog/post-title" console.log(post.author_data.url); // "/author/john-doe" // Complete author data in one response console.log(post.author_data); // { // id: 1, // name: "John Doe", // nicename: "john-doe", // avatar: "/path/to/avatar.jpg", // description: "Author bio...", // url: "/author/john-doe" // } // All image sizes available console.log(post.featured_image_urls); // { // thumbnail: "/uploads/image-150x150.jpg", // medium: "/uploads/image-300x200.jpg", // large: "/uploads/image-1024x768.jpg", // full: "/uploads/image.jpg" // } // Reading time estimate console.log(post.read_time); // "5 min read" // Multilingual data (when Polylang active) console.log(post.translations_data); console.log(post.available_languages); // ["en", "pl"] }); ``` ## Real-World Usage This plugin was developed for and powers the [polo.blue](https://polo.blue) blog - a multilingual automotive enthusiast blog built with Astro frontend and WordPress headless backend. **polo.blue Implementation:** - **WordPress Backend** - Content management with Polylang for Polish/English translations - **Astro Frontend** - Static site generation consuming enhanced REST API - **GA4 Integration** - Popular posts sections based on real pageview data - **Relative URLs** - Seamless deployment across multiple environments - **Headless Mode** - Complete frontend separation with 301 redirects The plugin is also suitable for other headless WordPress implementations: - Multilingual blogs with modern frontend frameworks - Content sites with GA4-based trending sections - Marketing websites with WordPress backend and Next.js/Nuxt presentation - E-commerce content management with custom taxonomies The plugin is actively maintained and battle-tested in production environments. > Have a WordPress site that needs care, a speed-up, or headless migration? See [WordPress rescue packages](/wordpress-rescue/) — from €100 for emergency repair to headless migration from €900. ## Used Technologies The plugin is open-source (GPL v2 or later) and available on GitHub for community contributions. All features are optional and individually configurable via the WordPress admin panel.

Spoko Design System

Mon, 20 Jan 2025 00:00:00 GMT

## Spoko Design System I developed an open-source design system combining documentation site and reusable component library in a single package. The system is built with modern technologies (Astro, Vue 3, UnoCSS) and published on npm for easy integration into projects. ## Dual-Purpose Architecture The unique approach allows the project to serve two purposes simultaneously: **Documentation Site** - Interactive documentation at [sds.spoko.space](https://sds.spoko.space/) with live component previews, code examples, and comprehensive guides for: - Core design tokens (colors, typography, spacing, shadows) - 20+ production-ready components (buttons, modals, forms, carousels) - Design patterns and rich components - Full search functionality via Pagefind **npm Package** - Installable component library (`spoko-design-system`) providing: - Importable Vue 3 components with TypeScript support - Exportable UnoCSS configuration for consistent styling - Icon system configuration with 10+ curated Iconify collections - Tree-shakeable exports for optimal bundle size ## Key Features ### Modern Component Library The system includes carefully crafted components that work in both contexts - as part of the Astro documentation site and as importable npm package components: - Interactive UI elements (buttons, inputs, modals, dropdowns) - Navigation components (navbar, breadcrumbs, pagination) - Content components (cards, tabs, accordions) - Specialized automotive components (used in production on polo.blue projects) ### Unified Styling with UnoCSS UnoCSS configuration is split into maintainable modules: - **Theme system** - Colors, typography, breakpoints, dimensions - **Component shortcuts** - Pre-configured component styles organized by category - **Exportable config** - Consumers can extend the base configuration via `createSdsConfig()` This approach ensures consistency across projects while allowing customization. ### Icon System Integration The design system includes two coordinated icon systems working together: - **UnoCSS Icons** - Static imports via `i-{collection}-{name}` classes - **astro-icon** - Dynamic imports for Astro components Curated collections include Material Design Icons, Lucide, Carbon, Boxicons, and specialized sets for automotive and technology icons. ### Real-World Applications The design system is battle-tested in production across multiple live projects: - [catalog.polo.blue](https://catalog.polo.blue/) - VW Polo 6R parts catalog - [polo.blue](https://polo.blue) - Main automotive website - [polo6r.pl](https://polo6r.pl) - Polish automotive community This ensures components are production-ready and handle real-world edge cases. ## Automated Release Pipeline The project uses semantic-release for version management: - Conventional commits determine version bumps - Automatic CHANGELOG generation - GitHub releases creation - npm publishing on merge to main This ensures consistent versioning and reliable package updates. ## Used Technologies The design system is open-source (MIT License) and actively maintained with automated dependency updates via Renovate and code quality checks via SonarQube.

VW Polo 6R user manual

Fri, 12 Jul 2024 00:00:00 GMT

[Polo6R.pl](https://polo6r.pl) is an innovative virtual owner's manual for the Volkswagen Polo 6R in Polish language, transformed from the original paper manual and designed as a Progressive Web App (PWA) using Astro. This website offers a user-friendly, accessible alternative to traditional PDF manuals, with AI-enhanced images (for improved sharpness & clarity). Users can access detailed vehicle information online or install the manual for a native app-like experience. With fast performance, modern design, dark mode, and built-in search, Polo6R.pl ensures essential information is always at your fingertips, accessible even on mobile devices. ## Used Technologies ## Challenges The page includes [PR-Code decoder](https://polo6r.pl/prcodes/) which is an equipment code decoder, built as a component in Vue3 and integrated with a site using Astro. The integration with the REST API utilizes a backend in Laravel. The website features an automatic deployment system integrated with Netlify, utilizing GitHub for seamless updates. Every change pushed to our GitHub repository triggers an automated deployment process, ensuring that the site is always up-to-date with the latest improvements and content. This streamlined workflow allows us to deliver a reliable and efficient user experience. Additionally, Google Tag Manager has been implemented, with settings for Analytics.

Horze.de

Mon, 29 Jan 2024 00:00:00 GMT

# Horze: E-commerce Frontend Development (Salesforce Commerce Cloud) ## Project Overview From early 2020 to January 2024, as part of my role at [Rocksoft](https://rocksoft.pl), I contributed to Horze.de - an e-commerce platform powered by Salesforce Commerce Cloud. Throughout this nearly 4-year journey, I collaborated closely with various team members to deliver high-quality frontend solutions. ## Front-End Development Working from Figma designs, I implemented responsive components and UI features while maintaining close communication with the UX team. Regular refinement meetings allowed us to discuss implementation details and ensure alignment with design specifications. We placed strong emphasis on thorough mobile testing using BrowserStack, ensuring seamless functionality across different devices and browsers. Additionally, I worked closely with the external SEO team, implementing optimizations and improvements based on their recommendations to enhance the site's search engine performance. I executed tasks using the Scrumban methodology, which evolved from our initial use of Scrum to better accommodate the project's dynamic needs. My contributions include developing a wide range of components for Salesforce Page Designer, including promotional landing pages for seasonal events (Christmas, Easter, Valentine's Day), major sales campaigns (Black Friday), and various marketing initiatives. I also created standard e-commerce components such as carousels, checkout modules, and other custom elements to enhance the shopping experience. ## Technologies Used The Horze.de frontend was built within the Salesforce Commerce Cloud ecosystem using modern front-end tooling: This project enhanced my front-end development expertise while deepening my understanding of user-centered design within a dynamic e-commerce environment. Through collaborative teamwork and effective communication across different departments, my work has played a key role in delivering a seamless and engaging shopping experience, helping Horze stand out in the competitive online retail space.

Modern Car Blog

Fri, 09 Jun 2023 00:00:00 GMT

## A Comprehensive Blog for VW Polo 6R Enthusiasts Polo.blue is a meticulously crafted blog focused on the Shadow Blue Volkswagen Polo 6R, built with Astro, Vue3, and UnoCSS. Leveraging WordPress as an administrative panel, the blog features statically generated pages that connect to the API via GraphQL. The site offers detailed posts on modifications, maintenance, and enhancements, providing a rich resource for Polo 6R enthusiasts looking to improve and maintain their vehicles. ## Used Technologies ### Benefits of the Technology Stack **Performance:** Statically generated pages are served as plain HTML files, ensuring rapid load times. Astro’s partial hydration further enhances performance by loading only the necessary JavaScript. **Security:** By serving static pages, Polo.blue reduces the risk of common vulnerabilities associated with dynamic sites, such as SQL injection and cross-site scripting (XSS). The static front-end is decoupled from the WordPress back-end, adding an extra layer of security. > Have a WordPress site and want the same result without a full rewrite? See the [headless WordPress migration package](/wordpress-rescue/#headless) — keep the admin, get a 10× faster frontend. **SEO:** Fast loading times and a well-structured HTML output improve the site's SEO. Statically generated pages are easily crawled and indexed by search engines, enhancing visibility. **User Experience:** With a modern design and responsive layout, Polo.blue offers an optimal user experience across devices. The dark mode and built-in search feature enhance usability, allowing users to quickly find the information they need. **Developer Experience:** Astro’s integration with Vue3 and UnoCSS streamlines the development process. The use of GraphQL simplifies data fetching, making it easier to develop and maintain the site. ### Conclusion Polo.blue exemplifies how modern web development tools can create a high-performance, secure, and user-friendly blog. By leveraging Astro, Vue3, UnoCSS, WordPress, and GraphQL, the site delivers an exceptional experience for Volkswagen Polo 6R enthusiasts. The combination of static site generation and dynamic capabilities ensures that Polo.blue remains a valuable resource for its audience, with the performance and security benefits of a static site.

SEO agency website

Wed, 12 Apr 2023 00:00:00 GMT

The freelancer offers a comprehensive range of SEO services, including technical optimization, content refinement, and strategic link-building. SEO audits are emphasized as critical for enhancing website performance and boosting sales. The freelancer also specializes in local SEO to help businesses connect with customers in their vicinity. ## Technologies Used The site was built on a modern static stack that actually supports ranking — because the thing the client sells (SEO) must also be visible in their own website: ## Scope of work - Design and implementation of a business-card site with blog and project portfolio. - Structured data configuration (`Organization`, `Service`, `BreadcrumbList`, `FAQPage`) for rich snippets in Google. - Proper hreflang and canonical setup for a future multilingual version. - Image optimization (WebP/AVIF, lazy loading, `aspectRatio` to eliminate CLS). - Contact form integration and GA4 analytics. - Continuous deployment — every merge to `main` automatically publishes a new version. ## Outcomes - Core Web Vitals in green (LCP < 1.5 s, CLS < 0.01) on mobile. - Full page load under 1 second on a typical 4G connection. - Zero hosting costs on the client side (static site served from a CDN). - Easy content growth — the client adds blog posts in Markdown through a Git-based panel.

GotowySMS: Custom CMS & Frontend Development

Sun, 12 Jan 2020 00:00:00 GMT

# Developing GotowySMS.pl: A Custom Platform for SMS Templates ## Project Overview GotowySMS.pl is a specialized platform offering ready-to-use wish texts and SMS templates for various occasions — holidays, birthdays, name days, anniversaries. My role in the development of this project involved creating the layout, designing the front-end, and developing a custom CMS for the back-end. The project is actively maintained and recently went through a deep technology rebuild. ## Business Context: Wish Texts and Seasonal Traffic GotowySMS.pl is not a typical "SMS list" — it's a library of polished wish texts and occasional messages used mainly by people looking for ready-made content to quickly copy and send. The niche naturally generates a distinctly **seasonal traffic pattern** — pre-holiday periods (Christmas, Easter, Mother's Day) bring multi-fold traffic spikes with a narrow conversion window. That characteristic directly shaped the architectural decisions — the platform has to absorb sudden traffic peaks without putting pressure on the database or back-end. ## Layout Design The first step in developing GotowySMS.pl was designing a layout that would be both visually appealing and highly functional. The goal was to create a clean, modern design that made it easy for users to browse and select SMS templates. The layout was crafted to ensure that all elements, from navigation menus to content display areas, were intuitively arranged, providing a seamless user experience. ## Front-End Development Once the layout was finalized, I focused on developing the front-end layer using modern web technologies. The front-end was designed to be responsive, ensuring that the platform looked great and functioned well on all devices, including desktops, tablets, and smartphones. This was crucial for a service like GotowySMS.pl, where users might need to quickly access SMS templates on the go. The front-end development also included implementing interactive elements, such as search functionality and category filters, to help users easily find the SMS templates they needed. The design emphasized simplicity and speed, ensuring that users could quickly navigate the site and access content without unnecessary distractions. ## Custom CMS Development To manage the content on GotowySMS.pl, I developed a custom CMS tailored specifically to the platform’s needs. The CMS was designed to be user-friendly, allowing administrators to easily add, edit, and categorize SMS templates. It provided the flexibility to manage a growing database of templates while ensuring that the content remained organized and accessible. The custom CMS also included features for managing user interactions, such as submitting and rating templates, which helped enhance the overall user experience and engagement on the platform. ## Stack Evolution: from Plain PHP to Astro + Laravel 13 The project has gone through three technological phases during its lifetime: 1. **Plain PHP (project start).** The first version was a classic PHP site rendered server-side — templates began with something like `require_once $_SERVER['DOCUMENT_ROOT']."/config/db.php";`, and every subpage hit the database directly on every request. Everything felt heavily over-complicated, and SQL query optimization was a constant topic just to keep the site loading fast enough under real traffic. On the front-end, jQuery and the libraries required by the old Bootstrap were fashionable at the time and piled on extra JS — every kilobyte counted in Lighthouse. The sum of these factors made a full rebuild a more rational choice than yet more patching. 2. **InfyOm Laravel Generator.** Migrating to [InfyOm](https://infyom.com/) delivered a productivity jump — the Laravel-based CRUD generator built the backbone of the admin in days instead of weeks. This freed up time to extend the CMS with features that had previously been backlogged. 3. **Laravel 13 + FilamentPHP + Astro 6 (current).** The latest rebuild separated the layers: Laravel 13 with [FilamentPHP](https://filamentphp.com/) as the CMS admin (a polished, consistent admin UI out of the box), Astro 6 as a static front-end consuming content through the API. Supported by Spatie Permissions for editorial roles and Sanctum for API authentication. The panel also exposes redirect management (301/302) directly in the UI — previously every URL change required hand-editing `.htaccess`, today editors handle it themselves in two clicks, without pulling in a developer. ## Architecture: Static Front, Database Only at Deploy Time The key decision of the current version is **generating static pages through the Laravel API during the Astro build**. In practice, this means three things: - **User runtime → zero database queries.** Every visitor receives pre-rendered HTML from the CDN — even thousands of concurrent requests never touch Laravel or MySQL. - **The database is only hit during build/deploy.** When editors add new wish texts in FilamentPHP, a webhook triggers an Astro build → it pulls the latest content from the API → regenerates the static files → ships them to the CDN. - **Seasonal spikes become a non-issue.** Scaling reduces to the CDN layer, which is practically unlimited — instead of stressing about database capacity on Christmas Eve, you just watch the traffic graphs calmly. This approach — static generation from a [headless Laravel CMS](/web-application-frameworks-2026/) — is one of the most efficient architectures for sites with cyclically changing content and sudden traffic surges. End result: the platform runs stably even through holiday spikes, with solid Core Web Vitals — an outcome that would have been hard to reach on the old monolithic PHP stack with jQuery and Bootstrap without aggressive caching and constant worry about server capacity. ## Technologies Used GotowySMS.pl combines a modern static frontend with a custom Laravel-based CMS: ## Conclusion The development of GotowySMS.pl was a comprehensive project that combined creative design with technical expertise. By creating a visually appealing layout, developing a responsive front-end, and building a custom CMS, I was able to deliver a platform that effectively serves its users and meets the client’s needs. This project reinforced the importance of user-focused design and the value of custom-built solutions in creating a successful online service. GotowySMS.pl stands as a user-friendly and efficient tool for anyone in need of quick and ready-to-use SMS templates.

Wholesale Security Systems

Sun, 12 Jan 2020 00:00:00 GMT

Montersi is a premier wholesaler specializing in security systems and building automation solutions. The online store offers a wide range of products, from surveillance cameras to home automation devices, catering to both residential and commercial needs. ## Description While working at [LizardMedia UX & Software House](https://lizardmedia.pl), I developed the front-end for Montersi.pl using Bootstrap 4. This ensured a responsive and user-friendly design and custom admin dashboard. The e-commerce platform is powered by PrestaShop, providing a robust and scalable solution for managing inventory, orders, and customer interactions. Montersi.pl combines advanced technology with a seamless shopping experience, making it a go-to destination for security and automation products. I worked closely with a team that included a graphic designer, a back-end developer, and another front-end developer. This collaborative approach allowed us to create a cohesive and efficient platform, ensuring that all aspects of the project were aligned and optimized. ## Technologies Used A B2B/B2C security-industry shop needs more than an off-the-shelf theme — it has to handle thousands of SKUs, product variants, installer pricing tiers, and wholesaler integration:

CITS: Multilingual Corporate WordPress Website

Thu, 09 Jan 2020 00:00:00 GMT

# CITS Krosno: A Multilingual WordPress Website ## Project Overview CITS Krosno is a straightforward, multilingual website designed to provide essential information about the company's services. The site was developed on the WordPress platform while I was working at Lizard Media Software House. The focus was on creating a clean, easy-to-navigate site that could effectively serve a diverse audience by supporting multiple languages. ## Multilingual strategy A multilingual company site is more than just dropping in a translation plugin. Several technical decisions directly affect SEO and user experience: - **URL structure**: each language version on its own path (`/en/`, `/de/`) rather than parameters — better indexed by Google and clearer for users. - **`hreflang` tags**: auto-generated by Polylang, telling Google which version of the page is meant for which market. - **Language switcher**: a consistent component on every page, redirecting to the equivalent in the other language (not just the home page). - **Content translation workflow**: the editorial team could create separate language versions of posts and pages, with a clear translation status indicator in the admin panel. ## Custom WordPress theme Instead of using an off-the-shelf template, I built the theme from scratch to match the graphic design provided by the client. This approach has concrete business advantages: - **Minimal code** = faster loading and better Core Web Vitals scores. - **No unnecessary features** means a smaller attack surface and fewer updates during maintenance. - **Full control over the layout** — pixel-perfect design implementation without the compromises imposed by ready-made themes. - **Tailored to the client's specifics** — sections, content types, and custom fields mirror the actual structure of the company's offering rather than the generic categories of a template. ## Outcomes and ongoing management The client received a site they can update on their own — with an intuitive admin panel matched to the multilingual structure. The lightweight theme generates clean, semantic HTML, which translates to both good performance and correct indexing in Google for every language version. ## Technologies Used The CITS website was built on the WordPress platform with a custom theme and multilingual capabilities: ## Conclusion The development of CITS Krosno highlights the effectiveness of a simple, yet well-executed multilingual WordPress site. It ensured that users from different linguistic backgrounds could access the necessary information easily, all while maintaining a clean and functional design.

Profiles manufacturing showcase

Tue, 09 Apr 2019 00:00:00 GMT

# Developing Profile.GrupaKety.com: A Multilingual Corporate Website ## Project Overview Profile.GrupaKety.com is a multilingual corporate website designed to serve a global audience in Polish, English, and German. The project was developed while I was working at Lizard Media Software House and involved building the site on the WordPress platform, following a detailed graphic design provided by the client. The goal was to create a visually consistent and user-friendly website that would effectively communicate the brand’s message across different languages while offering easy content management for the client. ## Multilingual Implementation with Polylang Given the international scope of the Grupa Kęty brand, the site supports three languages: Polish, English, and German. Translations are handled by **[Polylang](https://polylang.pro/)** — a plugin that treats each language version as a separate post/page linked by a translation relationship, rather than duplicating content inside a single entity. In practice this means the editorial team creates separate entries for PL/EN/DE and links them in the admin panel — the trade-off is more organizational discipline in exchange for no structural constraints between languages (e.g., the German version can carry different sections than the Polish one if marketing decides so). I also added dedicated translation-status views to the admin panel — editors can see at a glance which entry already has all three versions and which is still missing a language. Support for `hreflang` and separate XML sitemaps per language comes from Polylang without extra configuration. The site's content, images, and other media were managed to ensure accurate, culturally appropriate translations across all three markets. ## Custom WordPress Development The website was built on WordPress, chosen for its flexibility and user-friendly content management capabilities. However, to meet the specific needs of the client, I customized the WordPress administration panel. This involved tailoring the back-end interface to ensure that the client could easily edit and update all content without requiring technical expertise. The customization included intuitive controls for managing multilingual content, making it simple for the client to maintain the site in all three languages. ## Custom CSS and Design Implementation The front-end of the website was developed using custom CSS to faithfully replicate the provided graphic design. The design was meticulously implemented to ensure that the visual elements aligned perfectly with the client’s branding and aesthetic requirements. Custom CSS allowed for precise control over the layout, typography, and responsiveness, ensuring that the website looked and performed well on all devices, from desktops to smartphones. ## Industry context Grupa Kęty is one of Europe's largest producers of **aluminum profiles** — components used in architecture, automotive, rail transport, and industrial automation. The Extruded Products Segment serves customers from all over Europe, which is why the offering needed to be presented in three languages (Polish, English, German). A corporate website in this industry has a different function than a typical online store — its job is to **educate technical decision-makers** (architects, designers, engineers) about the capabilities and specifications of the profiles. Content is technically dense, often containing parameter tables, drawings, and PDF documentation — the site architecture had to handle all of this without compromising performance. ## Scope of work - Full layout implementation from the graphic design (desktop, tablet, mobile). - Custom content types for product and service categories specific to the industry. - A tailored admin panel — the editorial team manages trilingual content without technical expertise. - Responsive handling of technical tables and product specifications on mobile devices. - Technical SEO: hreflang, `Organization` schema, XML sitemap for all three language versions. - Integration with the Grupa Kęty brand-book system — consistent typography, color palette, and graphic elements. ## Outcomes The client received a professional, multilingual corporate site accessible to international markets — with a custom editorial panel that lets them update content independently without involving a developer. Visual consistency with the Grupa Kęty brand identity was preserved across every language version. ## Retrospective: would I build this on WordPress today? From today's perspective (2026), **no** — although it's worth giving credit to the context of the time. WordPress was *the* standard whenever you needed to put up a site quickly with an easy-to-use admin panel — for a non-technical editorial team the choice was essentially obvious. Realistic alternatives were scarce: apart from PyroCMS and a handful of similar niche platforms, a custom solution required a full team — a front-end developer, a back-end developer, and a graphic designer. Cost and delivery time were multiples higher, so for a corporate showcase site WordPress was a rational choice even knowing its long-term maintenance burden. In 2026 the economics have shifted fundamentally. Thanks to AI, a single person can deliver a showcase-style site faster and better than the agency of that era — there's no longer a need to engage a full software house for this kind of project, which significantly lowers the cost threshold. A custom build is no longer a luxury reserved for large budgets, and its technical advantages come to the front: - **Maintenance.** Standard WordPress requires continuous care — core, plugin, theme, and PHP updates. Any of them can break production, and skipping them leaves an open door for attackers. A custom panel without a sprawling plugin ecosystem has a significantly smaller surface of change. - **Security.** WordPress as a platform is the most common target of automated attacks on the web — every outdated plugin is a potential entry point. Custom solutions are not in the constant rotation of CVE scanners, which materially reduces risk in practice. - **Frontend stack.** The project used vanilla JS + jQuery — the standard in 2019, but jQuery is no longer used in modern sites. Current builds I ship on [Astro with Vue/React islands](/web-application-frameworks-2026/), applied only where interactivity is actually required — the rest stays as static HTML. When does WordPress still make sense? For editorial teams that already know the admin panel and publish large volumes of short content quickly. For a corporate product catalog in 2026, I would pick an architecture based on a static site generator + [a headless CMS](/modern-car-blog/) instead — fewer moving parts, fewer updates, faster loading, none of the issues from the three points above. ## Conclusion The development of Profile.GrupaKety.com was a successful collaboration that resulted in a polished, multilingual corporate website. By leveraging WordPress's capabilities and customizing the CMS to suit the client's needs, I was able to deliver a platform that is not only visually appealing but also easy for the client to manage. The use of custom CSS ensured that the design was implemented accurately, reflecting the brand's identity across different languages and regions. This project highlights the importance of adaptability and attention to detail in creating a website that effectively serves a global audience.

UX & Software House website

Thu, 09 Aug 2018 00:00:00 GMT

# Developing LizardMedia.pl: A Rebranded Corporate Website ## Project Overview LizardMedia.pl is a corporate website developed as part of a comprehensive rebranding effort for Lizard Media. The project involved creating a new version of the website based on a design provided in Adobe XD by a graphic designer. Built on the WordPress platform, the site was prepared for a future English version, featuring custom fields and templates, as well as tools for managing call-to-action banners and advertisements. Additionally, a strong focus was placed on WordPress security to ensure the site’s integrity and protection. ## Technologies Used The website stack was chosen for fast content updates by the marketing team and easy future expansion (additional languages, campaign landing pages). ## Conclusion The development of LizardMedia.pl involved close collaboration to bring the rebranding vision to life through a modern and adaptable WordPress website. With custom features and a focus on security, the site not only reflects the new brand identity but is also prepared for future expansions, including the addition of an English version.

GSM Forum: Managing a Mobile Tech Community

Sun, 12 Feb 2017 00:00:00 GMT

# Developing and Managing GSMX.pl: A Forum for Mobile Enthusiasts ## Project Overview GSMX.pl is a popular online forum dedicated to discussions about mobile technology, providing a space for enthusiasts to share knowledge, seek advice, and stay updated on the latest trends. Over the years, the forum has undergone several significant upgrades and migrations to ensure it remains a robust and user-friendly platform. My involvement in the project included creating the initial layout, collaborating on script and template modifications, managing migrations across different forum software, and overseeing the technical management of the forum on a VPS server. ## Layout Design and Script Modifications The journey with GSMX.pl began with designing a custom layout that was both visually appealing and easy to navigate. The layout was tailored to enhance user experience, with a focus on accessibility and functionality, ensuring that forum members could easily engage in discussions and find relevant information. In addition to the layout, I collaborated closely on modifying the forum script and templates to align with the specific needs of the community. These modifications involved customizing features, optimizing performance, and ensuring compatibility with the evolving requirements of the forum’s user base. ## Forum Migrations As the forum grew and technology advanced, it became necessary to migrate GSMX.pl from its original platform to more modern and capable solutions. The first major migration involved moving the forum from **phpBB2** to **vBulletin 3**, a more powerful and feature-rich forum software that provided better scalability and enhanced user management tools. After several years on vBulletin, another significant migration was undertaken, this time from **vBulletin 3** to **xenForo**. XenForo offered a more modern interface, improved performance, and better support for contemporary web technologies. During this migration, I also took on the task of developing the Polish language version for xenForo, ensuring that the forum remained accessible and user-friendly for its Polish-speaking community. ## Server Management In addition to design and development work, I was responsible for the technical management of the forum on a **VPS server** running **Debian 7 Wheezy**. This involved configuring and optimizing the server environment, which included using **nginx** as the web server and **MariaDB** as the database management system. Managing the VPS server required ensuring the forum’s stability, security, and performance, which were critical for maintaining a smooth user experience. ## Technologies Used GSMX.pl evolved through multiple forum platforms and infrastructure stacks over the years: ## Conclusion Working on GSMX.pl was a comprehensive project that involved both creative and technical challenges. From designing the initial layout and customizing the forum’s features to managing complex migrations and maintaining the server infrastructure, the project highlighted the importance of adaptability and attention to detail. Through these efforts, GSMX.pl evolved into a modern, efficient, and user-friendly forum, continuing to serve its community of mobile technology enthusiasts effectively. This experience also underscored the value of ongoing collaboration and technical management in maintaining a thriving online community.

SHE swimwear online store

Sat, 09 Apr 2016 00:00:00 GMT

# Developing the Front-End for SHE Swimwear Store: A Comprehensive Project Overview ## Project Overview While working at AQIMO, I developed the front-end for the SHE swimwear online store. This project involved implementing a custom design that aligned with the brand's aesthetic while ensuring the site's functionality across multiple devices. ## Front-End Development The front-end of the SHE swimwear store was meticulously crafted to reflect the brand's identity and provide a smooth user experience. Built on a custom Phalcon backend, the website was designed to be both visually engaging and user-friendly. Following the provided graphic design, I implemented responsive layouts that ensured the store looked great on desktops, tablets, and mobile devices. One of the standout features of this project was the custom swimsuit size configurator. This tool allowed customers to select their ideal swimwear size, enhancing the shopping experience by providing a tailored fit. The configurator was fully responsive, ensuring it worked seamlessly across all devices, including smartphones. ## Multilingual and Multicurrency Support Given the international reach of the SHE brand, the website was developed to support multiple currencies and languages. Customers could browse and shop in PLN, USD, and EUR, with language options available in Polish, English, Italian, German, French, and Spanish. This multilingual and multicurrency support was crucial in catering to a diverse global audience, making the shopping process convenient for users from different regions. ## SEO and Blog Management In addition to the front-end development, I managed a Private Blog Network (PBN) to boost the store's search engine optimization (SEO) efforts. The PBN was strategically used to improve the website's visibility and ranking on search engines, driving more organic traffic to the site. This aspect of the project was essential for ensuring the long-term success and competitiveness of the SHE swimwear brand online. ## Technologies Used The SHE swimwear store combined a Phalcon backend with a bespoke responsive frontend: ## Conclusion The SHE swimwear store project was a valuable experience that combined technical challenges with creative problem-solving. By delivering a responsive, multilingual, and user-friendly front-end, I ensured that the online store not only met the client's expectations but also provided a smooth and enjoyable shopping experience for customers worldwide. Additionally, this project allowed me to enhance my collaboration skills, working closely with the client to understand their vision, with the graphic designer to bring that vision to life, and with the backend developer to ensure seamless integration of all features. This holistic approach contributed to the successful launch of a sophisticated e-commerce platform that effectively supports the SHE brand’s global presence.

Android App & Game reviews

Fri, 12 Feb 2016 00:00:00 GMT

Website with reviews of Android games and applications, initially based on the ZURB Foundation 5 framework and custom CMS as backend, later migration to Bootstrap 3 as frontend and Wordpress as backend. # Developing Droida.pl: A Platform for Android Game and Application Reviews ## Project Overview Droida.pl is a comprehensive website dedicated to providing in-depth reviews of Android games and applications. The project began with a focus on creating a user-friendly and visually appealing platform that could handle a large volume of content while ensuring easy navigation for users. Initially, the site was built using the **ZURB Foundation 5** framework for the front-end and a custom CMS for the back-end. However, as the site evolved, it underwent a significant migration to **Bootstrap 3** for the front-end and **WordPress** for the back-end, enhancing its functionality and scalability. ## Initial Development In the early stages, Droida.pl was designed with **ZURB Foundation 5**, a framework known for its responsive design capabilities. This choice ensured that the website was accessible across various devices, providing a consistent user experience whether visitors were browsing on a desktop, tablet, or smartphone. The custom CMS used on the back-end allowed for tailored content management, specifically designed to handle the needs of a review-based website. The initial design and development focused on creating a clean and intuitive interface, allowing users to easily find reviews, navigate through categories, and discover new Android games and applications. The custom CMS provided the flexibility needed to manage a growing database of reviews, complete with ratings, screenshots, and detailed descriptions. ## Migration and Evolution As the website grew and the needs of the platform expanded, a migration to **Bootstrap 3** and **WordPress** was undertaken. Bootstrap 3 provided a more modern and widely supported front-end framework, enhancing the site’s responsiveness and visual appeal. The switch to WordPress as the back-end system brought several advantages, including a more user-friendly content management interface, better scalability, and access to a wide range of plugins and tools to further enhance the site’s functionality. This transition allowed Droida.pl to handle an increasing volume of content while maintaining the same level of usability and performance. The move to WordPress also opened up new possibilities for SEO optimization, user engagement through comments and social sharing, and easier updates and maintenance. ## Conclusion The development and evolution of Droida.pl showcase the importance of adaptability in web development. Starting with a custom solution and later migrating to more mainstream technologies like Bootstrap 3 and WordPress allowed the site to grow and improve without sacrificing performance or user experience. This project highlighted the importance of choosing the right tools for the job and being open to change as the needs of the website and its users evolved. Today, Droida.pl stands as a reliable and accessible platform for Android enthusiasts to discover and explore the latest games and applications.

Children’s Winter Clothing Store

Sat, 09 Jan 2016 00:00:00 GMT

# Developing the Front-End for Pilgini: A Children's Winter Clothing Store ## Project Overview While working at AQIMO, I developed the front-end for **Pilgini.com**, a store specializing in high-quality winter apparel for children. The project was built on the Phalcon framework, allowing for a robust and efficient platform that met the specific needs of the client. ## Target Market and Brand Positioning The store was primarily oriented toward the Russian market — back then, before the war, this was a fully viable and promising direction for expansion. Expensive, prestigious winter clothing for children, decorated with Swarovski crystals, enjoyed particular recognition there among higher-income parents. The garments themselves were manufactured in Poland, and in-store payments were handled through PayPal — a choice that suited an international customer base and removed the overhead of supporting many local payment methods. ## Front-End Development The front-end development of Pilgini.com focused on creating an engaging shopping experience that catered to the needs of parents looking for winter clothing for their children. I utilized modern web technologies to ensure that the website was not only aesthetically pleasing but also responsive and easy to navigate on all devices, from desktops to smartphones. The design was implemented with a focus on usability, featuring clear product categories, detailed item descriptions, and high-quality images that showcased the clothing's quality and warmth. This approach ensured that customers could easily find and purchase the products they were looking for, enhancing their overall shopping experience. ## Collaboration and Technical Integration Working on this project provided me with valuable experience in collaboration, as I worked closely with the graphic designer to bring the visual concepts to life and with the backend developer to ensure seamless integration with the Phalcon framework. This teamwork was crucial in delivering a final product that was not only visually appealing but also technically sound, with smooth performance and quick load times. ## Cross-Browser Mobile Perfection One of the more interesting technical aspects of the project was how high the client's bar was for mobile consistency. The site had to render flawlessly even in less mainstream browsers — I tested it in [Dolphin Browser](https://dolphin.com/) among others, which at the time held a noticeable share of the mobile market outside the Chrome and Safari ecosystems. On top of that, Firefox in that era still lacked many of the CSS features that already worked in WebKit-based engines. A large share of the work went into workarounds — manual vendor prefixes, alternative layout implementations, and additional JavaScript paths to keep visual and behavioral consistency across engines. These "small details" are what teach the kind of cross-browser discipline that pays off throughout an entire career. ## Technologies Used The Pilgini.com storefront ran on a Phalcon-based backend with a custom frontend layer: ## Conclusion The development of the Pilgini.com front-end was a rewarding project that combined creativity with technical expertise. I was able to create a store that effectively showcases the brand's winter clothing for children, making it easy and enjoyable for customers to shop. Working closely with other team members was key to delivering a successful and cohesive online store that meets the client’s expectations.

VWTECH: Website with Admin Panel & Packshots

Wed, 09 Sep 2015 00:00:00 GMT

# Developing a Customized Website for VWtech: A Comprehensive Project Overview ## Project Overview VWtech is a company specializing in the sale and customization of car parts. I developed their website, handling both the front-end and back-end aspects of the project to effectively showcase their products and services. ## Front-End Development The front-end of the VWtech website was designed to be user-friendly and visually engaging. I utilized **jQuery**, **Vanilla JS**, and **Bootstrap 3** to create a responsive and interactive interface. The website’s design is clean, with intuitive navigation that allows users to easily find the information they need, whether it’s browsing car parts, viewing completed projects, or contacting the company. One of the key features of the front-end is the product display, which includes high-quality images and detailed descriptions. I was responsible for processing these images, including product packshots, to ensure they were optimized for the web while maintaining high visual standards. This attention to detail helps create a professional and trustworthy image for VWtech. ## Back-End Development The back-end of the website was built with a proprietary CMS (Content Management System) tailored to the specific needs of VWtech. The CMS was designed to be flexible and easy to use, allowing the client to manage their website content without needing extensive technical knowledge. Key functionalities of the CMS include: - **Publishing Posts**: VWtech can easily publish and manage posts about their recent projects and news, helping to keep the website content fresh and engaging. - **Product Sales Offers**: The CMS enables the client to manage their car parts sales offers, including adding new products, updating prices, and managing inventory. - **Photo Management**: The system includes robust photo management tools, allowing VWtech to upload, organize, and display images of their products and projects. - **Product Search**: To enhance the user experience, the website features an advanced product search function, making it easy for visitors to find specific car parts quickly. - **Contact Form Integration**: To ensure secure and spam-free communication, the contact forms on the website are integrated with Google’s invisible reCAPTCHA. This feature helps protect the website from spam bots while providing a seamless user experience. ## Technologies Used The development of the VWtech website involved several key technologies: ## Conclusion By meticulously crafting both the front-end and back-end components, I was able to deliver a website that not only meets the client’s current needs but also provides a robust platform for future growth. The custom CMS empowers VWtech to manage their online presence with ease, while the responsive design ensures that users have a seamless experience across all devices. This project highlights the importance of aligning technology with business goals to create a digital presence that is both functional and impactful.

Mieszacz: Article Paraphrasing (Pre-AI Era)

Fri, 09 Jan 2015 00:00:00 GMT

# Mixer: A Paraphrasing Tool for SEO Texts ## Project Overview Before AI tools emerged, quickly generating unique content was a major challenge in digital marketing. To address this need, I developed **Mieszacz** — a paraphrasing tool designed to rewrite articles by word replacement, useful for creating affordable SEO texts. What started as a personal project eventually evolved into a publicly available tool. ## Development Process The Mieszacz tool was built using **PHP** and **Bootstrap**, providing a simple yet effective platform for users to quickly and efficiently paraphrase text. PHP served as the backbone for processing the text and generating paraphrased versions, while Bootstrap was used to create a responsive and user-friendly interface. This combination ensured that the tool was not only functional but also accessible across different devices, including desktops and mobile phones. ## From Personal Use to Public Release Initially, Mieszacz was created to meet my own needs for content rewriting, helping me to generate unique variations of articles quickly and easily. However, recognizing the broader demand for such a tool in the SEO community, I decided to make it publicly available. This decision allowed others to leverage the tool for their own content creation needs, particularly those looking for an efficient way to produce low-cost SEO texts. ## How it worked — the algorithm Under the hood, Mieszacz did one simple thing: **synonym substitution from a dictionary**. Input text was tokenized, the tool looked up available synonyms for each word, then picked one (at random or according to rules). The result was text with the same meaning but different words. For Polish this is a bigger challenge than for English — **inflection** means that for each word you have to preserve the correct grammatical form (case, number, gender). Mieszacz's simplified approach worked well for simple texts, but in more complex sentences it produced awkward results. ## Context: SEO before the AI era By 2015 Google was already fighting content farms with the Panda algorithm (introduced in 2011). Penalties for **duplicate content** and low-quality text were a real threat to affiliate sites, PBN networks, and link schemes. Tools like Mieszacz allowed people to quickly generate "unique enough" variants of texts that slipped below Google's radar without investing in real copywriting. It was the golden age of **grey-hat SEO** — Mieszacz fit into that niche alongside article spinners, rewriters, and content generators. ## Why tools like this are dead today Mieszacz lost its reason to exist for two reasons: 1. **AI generates better text**. GPT-class models can write from scratch while preserving context, tone, and natural syntax — you don't need an input text to "paraphrase" anymore. Cost: a few cents per thousand words. 2. **Google learned to detect it**. Since 2022 (Helpful Content Update), the algorithm is much better at spotting low-quality content — regardless of whether it came from AI, a spinner, or a human. Today you achieve a similar effect (unique content at scale) through AI + human editing, with far better quality and lower risk of penalties. ## Technologies Used Mieszacz used a straightforward pre-AI-era stack for a tool of this kind: ## Conclusion Today, when AI can generate and rewrite texts in seconds, tools like this have become obsolete. Nevertheless, Mieszacz remains an interesting example of solving problems with the methods available at the time, documenting the approach to content automation before the AI era.