Website rebuild · Furniture catalogue
A new furniture catalogue to replace KUBE’s old website
Client — KUBE furniture store in Riga.
We replaced KUBE’s old website with a new WordPress and WooCommerce solution, cleaned up the product data and completely rebuilt the public storefront with search, filters and product pages.
Starting point
The old website was technically outdated
KUBE’s website ran on PHP 5.6 and a WooCommerce version roughly a decade old. Its design, catalogue structure and loading speed no longer met the company’s needs. We developed a new version to replace it while retaining and organising the existing product data.
Delivered
The rebuild covers the full path from homepage to product choice
WordPress and WooCommerce remain the data foundation; we rebuilt the customer-facing storefront.
New homepage
A branded homepage with furniture slider, room categories, arrivals, store details and services.
Furniture catalogue
A lightweight catalogue with category and price filters, sorting and WooCommerce product data.
Search
Furniture-focused search with quick queries and direct product results.
Product page
A new layout for gallery, price, dimensions, description and related products.
Purchase sections
Cart, checkout and account views in one visual system while retaining WooCommerce behaviour.
Information pages
About, contacts, delivery and finance pages with map, route buttons and contact form.
Catalogue structure
Products can be found by room, category or name
Navigation follows the way people choose furniture.
Choose a room
Living, dining or interior.
Narrow the choice
Category, price and sorting.
Open a product
Images, dimensions, materials and availability.
Get in touch
Phone, WhatsApp, Google Maps and Waze.
Content management
The KUBE team manages more than products
A dedicated “KUBE saturs” area manages homepage copy, links, images, room blocks, contacts and the hero slider.
- Add several slider images at once
- Drag to reorder slides
- Replace or delete an individual image
- Preview and alt text for every slide
- Up to 24 slides without code changes
Data and domain migration
The new site launched without losing the old one
Development ran on a test domain. Before launch we backed up the old files and database, moved the new version to www.kube.lv, replaced internal URLs and tested the catalogue, products, forms and mobile views.
Test environment
Development without affecting the old site.
Backup
Old files and database retained.
Migration
New site and data moved to the main domain.
Verification
Links, forms, cache and devices tested in production.
Speed and security
The public catalogue is cached; private pages never are
Public content is separated from cart, account and order data. The catalogue uses LiteSpeed cache, while private sections are generated per user.
Light public pages
Purpose-built HTML views replace heavy universal layouts.
Smart image loading
The first hero slide loads immediately; others only when needed.
Cache separation
Public pages are cached while cart and checkout use no-store.
Security headers
HSTS, SAMEORIGIN, nosniff, referrer policy and disabled XML-RPC.
Catalogue and search
Canonical categories and shareable product links
Duplicate categories were merged and old URLs point to the unified catalogue. Categories and products receive appropriate titles, descriptions, canonical and Open Graph data.
Technical solution
Technologies
Need to rebuild an existing WordPress shop?
We will identify what is worth keeping, migrate the data and build a fast storefront without interrupting the current site.
Questions and answers
About the KUBE rebuild
Was the old KUBE site repaired?
No. It was retained as a fallback while we developed a new platform to replace it, then launched the new site on the main domain after testing.
What can KUBE edit without a developer?
Products and categories in WooCommerce; homepage copy, links, contacts, blocks and slider in the dedicated KUBE saturs area.
How was loading improved?
Heavy public layouts were replaced with lightweight views, images were optimised and deferred, and public cache was separated from private WooCommerce pages.