[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-why-nuxt-and-directus":3},{"slug":4,"title":5,"excerpt":6,"date":7,"readingMinutes":8,"cover":9,"coverAlt":10,"preview":11,"tags":16,"body":26,"caseStudies":27},"why-nuxt-and-directus","Nuxt and Directus for a client site: why I chose them","For Computravel I needed fast search pages, an admin the client could run themselves, and a third-party API tamed into shape. Here's why this pair fit.","2026-11-19",5,"\u002Fassets\u002F1bd9067a-2482-4bf9-97fe-cca83b60f226?width=1280&quality=80&format=auto","DIrectus and Nuxt are a powerful web stack offering powerful tools and flexible solutions",{"path":12,"alt":10,"width":13,"height":14,"type":15},"\u002Fassets\u002F1bd9067a-2482-4bf9-97fe-cca83b60f226?width=1200&height=630&fit=cover&format=jpg&quality=80",1200,630,"image\u002Fjpeg",[17,20,23],{"name":18,"slug":19},"Architecture","architecture",{"name":21,"slug":22},"Nuxt","nuxt",{"name":24,"slug":25},"Directus","directus","\u003Cp>When I rebuilt Computravel, a travel package site that had been built years earlier in PHP, I had three jobs to do at once: a branding revamp, a new search experience, and an integration with the Thompsons travel packages API. The stack I chose was Nuxt for the site and Directus behind it. This is why, and where it's worked well. The full story is in the \u003Ca href=\"\u002Fcase-study\u002Fcomputravel\">Computravel case study\u003C\u002Fa>.\u003C\u002Fp>\u003Ch2>What the site needed\u003C\u002Fh2>\u003Cul>\u003Cli>\u003Cp>No user accounts: it's a brochure of holiday packages, with general and package-specific enquiry forms.\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>Search by location, category and price that feels instant.\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>Pages that search engines can read, because that's where the customers come from.\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>An admin the client can use without calling a developer.\u003C\u002Fp>\u003C\u002Fli>\u003Cli>\u003Cp>Data from a supplier API, reorganised around geography instead of the supplier's own business logic.\u003C\u002Fp>\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>Why Directus\u003C\u002Fh2>\u003Cp>Directus is a headless CMS written in Node that sits on top of an ordinary SQL database. Out of the box it gives you users, roles and permissions, file and image handling, and an admin dashboard, all configurable. That's weeks of work I didn't have to do, and the client gets an admin that's actually pleasant to use.\u003C\u002Fp>\u003Cp>Because it's a real database underneath, the data stays the client's, in a shape that makes sense to them. I could map the supplier's confusing field names into a clean model once, on the way in, instead of everywhere they're used.\u003C\u002Fp>\u003Cp>One thing I'd tell anyone starting with it: you can change the schema by clicking in the admin, but don't do that on production. I keep every schema change in a migration in the repository, so each environment gets the same change the same way, and the deploy applies it.\u003C\u002Fp>\u003Ch2>Why Nuxt\u003C\u002Fh2>\u003Cp>Nuxt is a full stack framework built on Vue. Server-side rendering means every page arrives as real HTML, which is good for search engines and for people on slow phones. On top of that I cache pages on the server and let a CDN cache the images, and purge the cache automatically when the client publishes a change in Directus, so the site is fast without ever showing stale content for long.\u003C\u002Fp>\u003Cp>I also keep the search state in the URL. Every search has a link you can share or bookmark, and search engines see the same pages people do.\u003C\u002Fp>\u003Ch2>Would I choose it again?\u003C\u002Fh2>\u003Cp>Yes, for this kind of site: content that a team edits, data from somewhere else, and pages that need to be fast and findable. I run my own site, Truelathe, on the same pair. For an app with complex real-time behaviour or heavy custom business logic I'd weigh other options, and I'd write more of the backend myself, often in Go.\u003C\u002Fp>\u003Cp>Current Lighthouse testing shows that the homepage's time to first contentfull paint is 0.06s, and the full page loads in about 1 second. This is for a huge and complex page.\u003C\u002Fp>\u003Cp>If you're planning a site like this, \u003Ca href=\"\u002Fservices\">here's what I offer\u003C\u002Fa>.\u003C\u002Fp>",[]]