We start with the layout and the path a visitor should take, and pick the tool to fit the project — not the other way round. Content then goes into fields and blocks, without touching the code.
We start with what is meant to happen on the site: who visits, what they are looking for and what they should click. Layout, mobile and desktop wireframes, heading and button hierarchy. Visual identity we leave to a designer — we work with yours or with material from your designer.
Bricks, a block theme on native WordPress blocks, or a theme written from scratch with ACF fields. Each has its place and each is in the work below — the choice follows from who will run the site and how unusual it needs to be.
Repeating things — products, varieties, services, team cards — are described in fields and rendered by a template. Adding another entry means filling in a form, not copying a section and fixing it in five places.
Images in modern formats, lighter font files, a stable layout that does not jump while loading, correct headings, image descriptions and keyboard support. Doing this up front costs less than fixing it after an audit.
Separate addresses for each version and markup for the search engine, so the languages do not compete with each other in results. Our work includes both WPML and TranslatePress — the choice follows from how much content gets translated and who will do it.
A store rarely fits the default templates. We replace them with our own product, listing and cart layouts, and write the logic — conditional shipping, variants, configurators — in PHP as part of the project rather than as yet another plugin.
We also handle what happens after the order: payments, delivery, transactional emails.
The winery store runs Polish payment methods including BLIK and bank transfers, delivery through InPost and DPD, the age gate required for alcohol, and a mega menu featuring a recommended wine. There we replaced the default WooCommerce templates with Bricks templates driven by dynamic data.
Design and build of the site and the store, default WooCommerce templates replaced with Bricks templates, a full wine taxonomy, an age gate, Polish payments and delivery. We still run it, SEO included.
winnicaamelie.pl →
A haulage company site in three language versions, with the audience split in the first screen: one path for people booking transport, another for truck servicing. A number strip and a four-step process from enquiry to delivery.
waldrom.pl →
WordPress on native blocks and a child theme, with no builder at all, in three languages. Nine species guides, a variety calendar rendered from fields across 45 pages, full keyboard support and descriptive alt text.
drzewka-kusek.pl →
A theme written from scratch, no builder. Every catalogue entry renders from fields: material, dimensions, weight, print type. Two named product lines and a voice of its own.
zostawmniewspokoju.pl →
A custom theme, ACF fields and our own PHP used for a register that rarely comes out well on WordPress: a masthead with the year, a dateline, drop caps, column rules, "continued on page three" pointers and an "in this issue" box.
zbuta.ovh →
A few sentences are enough. A brief, a design or a site that is to be replaced makes it easier still.
We write back with what we suggest, how long it takes and what it costs. Where possible, a fixed price instead of hours.
You see progress as it happens. At the end you get a working site, the credentials and a guide to the parts that have their own logic.
We pick the tool to fit the project: Bricks, a block theme on native WordPress blocks, or a theme written from scratch with ACF fields. When taking over an existing site, we work with whatever it is built on.
Yes. Content goes into fields and blocks, without touching the layout or the code. On larger sites we add a short guide for the parts that have their own logic.
We do layout, mobile and desktop wireframes, content hierarchy and the path to contact or purchase. Logos and visual identity we leave to a designer — we work with what you have or with material from your designer.
Yes, along with redirecting the old addresses to the new ones, so that what was already visible in search does not disappear after launch.
A company site is usually a few weeks, a store longer — depending on the number of products, integrations and how quickly the content arrives. We give the date after a conversation about scope, together with the quote.
Tell us what should be built and who it is for. We will write back with scope, timing and price.
Describe your project →Or by email: info@asymetria.com.pl