Topic
WordPress
Technical insights from FlareTech about WordPress.
- Web14 min read
Error pages that recover — 404, 500 and what must not die
A 404 is a way forward, not a brand joke. A 500 is an honest pause, not a reload loop. The page you show on error is still your site.
→Error pages that recover — 404, 500 and what must not die - Method13 min read
An honest cookie banner: consent that matches what you set
A cookie banner is honest when reject is as easy as accept, and when the network after no is empty. A CMP logo is not consent.
→An honest cookie banner: consent that matches what you set - Method13 min read
How to brief a redesign — so you do not discover scope in week four
A redesign brief says what must be true after launch, what must live, and what is out. A moodboard is taste. It is not a brief.
→How to brief a redesign — so you do not discover scope in week four - Method13 min read
First-party measurement after cookie consent
First-party analytics is measurement you own after an honest yes — or with no cookies. Not a new tag you hide behind Consent Mode.
→First-party measurement after cookie consent - Web12 min read
Web accessibility and the EAA: what does your site actually need?
The EAA is not a plugin and not a duty on every website. Here is what the law typically covers, what WCAG actually means, and what to fix first.
→Web accessibility and the EAA: what does your site actually need? - Web7 min read
Relaunch your website without losing SEO rankings
A new website can cost you traffic if URLs, redirects and content parity are not planned. Relaunch is an SEO project — not only a design project.
→Relaunch your website without losing SEO rankings - Web8 min read
Shopify vs. WooCommerce — what fits Danish webshops?
Choose Shopify when you want the commerce engine ready from day one. Choose WooCommerce when the WordPress ecosystem and full server control matter more than platform speed.
→Shopify vs. WooCommerce — what fits Danish webshops? - Web9 min read
Next.js vs. WordPress — when is which the right call?
Choose WordPress when editorial frequency and the plugin ecosystem are the strength. Choose Next.js when performance, control and developer flow decide the business outcome.
→Next.js vs. WordPress — when is which the right call? - Web5 min read
How to choose a headless CMS — without building a new WordPress
A headless CMS solves a specific problem: content must be editable without redeploying the entire app. It is not automatically better than WordPress — it is better when your site is an app, not a theme.
→How to choose a headless CMS — without building a new WordPress - Web6 min read
WordPress to Next.js — when migration makes sense
WordPress is still a good choice for many marketing sites. But when performance, security, and developer experience start costing you more than WordPress gives back, Next.js is often the natural next step — if you do it with a plan.
→WordPress to Next.js — when migration makes sense