Services
Vue and Nuxt
development.
If your product is built on Vue or Nuxt, it helps to have a developer who knows the framework's patterns and trade-offs well. I've used Vue and Nuxt on long-term contracts and scoped projects alike - shared component frameworks, server-rendered and statically generated sites, and staff applications. This site is built with Nuxt, too.
When to bring me in
Vue and Nuxt work
that needs framework depth.
Shared components across several apps
A Vue component framework distributed through npm, with a strict semantic versioning strategy, lets several applications share one brand and one set of components. I built that for Nyx as part of moving their frontend from AngularJS to Vue.
Server rendering or static generation
Nuxt can render pages per request or generate them at build time. I've shipped both: server rendering for a coaching platform's customer app and a headless WordPress site, and static generation for DK Hostmaster's timeline and an insurer's staff application.
A CMS the editors already know
A headless CMS keeps editors in familiar tools while Nuxt renders the public site. For Savage Studio, WordPress runs as a headless content API and the Nuxt front end fetches content over its REST API.
Staff and back-office applications
Many Vue projects are internal tools with dense workflows. In Nyx's back office I built the frontend for booking, shift management, membership approval and a drag-and-drop table and floor plan editor.
What you get
Framework work
in Vue and Nuxt.
The work here is specific to Vue and Nuxt. For broader frontend help, such as architecture across several products or a React codebase, frontend development is the better fit.
- Vue component frameworks distributed through npm with semantic versioning
- Nuxt applications with server rendering or static generation, chosen per project
- Headless CMS front ends, for example on the WordPress REST API
- Staff and back-office single-page applications
- Pre-rendered static sites with content kept in the repository
- Migration of older frontends, such as AngularJS, to Vue
Cases
Vue and Nuxt
in production.
- Long-term contract
A shared Vue framework and a large back office
I built Nyx's reusable Vue component framework and led the frontend for their largest back-office application. The platform serves more than 250,000 users.
A Vue component framework shared across Nyx's frontend applications through npm, and the version 2.0 back office built on it: 147 reusable components and a frontend that talked to more than 120 REST API endpoints.
- Marketing site
A marketing site the studio could publish from WordPress, and visitors would feel in the browser.
Scoped project for a design-led agency: mockups translated to a Nuxt front end, with WordPress headless so the team could ship cases and campaigns without learning a new CMS.
Headless WordPress and a server-rendered Nuxt front end, with content fetched over the REST API so each route could be tuned for the performance and SEO it needs.
- Campaign site
DK Hostmaster's 20-year story, for the public and the press.
Static Nuxt front end with year-by-year storytelling and predictable hosting. Content lives in the repo so the team could update and hand it off without a CMS.
Nuxt static generation for DK Hostmaster's 20-year timeline: every year pre-rendered as a static page, with each year's story kept in JSON files in the repository.
"He continuously impresses me with not only exceptional development skills, but also by consistently going the extra mile."
Nicolai Qvindbjerg
Art Director @ Savage Studio
How it works
From a first message
to launch and after.
Share the context
Tell me what you're building, who it's for and what timeline you're working toward. Stack preferences, design constraints and links to a repo, Figma file or existing product all help.
Agree on the setup
I work on an hourly rate and I'm transparent about it before we start. For scoped work, you get an honest hour estimate tied to a clearly defined brief, so you know what you're committing to upfront.
Work inside your workflow
I join your Slack, follow your Git workflow, attend your standups and fit into your existing processes, whether the team is a startup or a large enterprise.
Launch and keep going
I don't disappear after deployment. Most of my clients keep me on for maintenance, iterations and new features, and some partnerships have been running for 4-8 years.
FAQ
Hiring a Vue
or Nuxt developer.
It depends on the content and who edits it. Static generation suited DK Hostmaster's timeline, where content lived in the repository and hosting had to stay simple. Server rendering suited Savage Studio, where the team publishes from WordPress without a deploy for every text change.
Yes. Joining an existing team and codebase is one of the most common setups I work in. I follow your Git workflow and fit into your existing processes.
Yes. At Nyx, the new component framework was part of moving their frontend from AngularJS to Vue. We built the shared framework first and then implemented new versions of their frontend platforms on it.
Yes. Vue and Nuxt are my default, and I also work with React and Next.js. For work that spans frameworks, frontend development is the better fit.
No. On some Nuxt projects I also worked on the backend behind it, for example a Laravel API on the coaching platform and Slim PHP services at an insurer. Full-stack development covers that side of the work.
Related services
Other ways
I can help.
Frontend development
Frontend architecture, product UI and component libraries across Vue, React and TypeScript, inside your team or as a scoped project.
Full-stack development
When the Nuxt app needs an API, integrations, hosting and deploy pipelines behind it.
Looking for
the right developer?
Whether you're ready to start or just exploring your options, feel free to reach out. No commitment, no pressure.
I usually respond within 2 hours.