日本語

Practical Assessment

Hands-on conclusions and dated facts from implementing the Nuxt UI docs template.

Practical Assessment

This assessment was last researched and rebuilt on 2026-07-19. Opinions come from this implementation; linked version and feature facts can be checked independently.

Hands-on observations

  • The official template is a useful application blueprint rather than a new site-generator abstraction. Its Vue files make every behavior visible and editable, but there is more local application code than in an opinionated theme.
  • Nuxt UI's docs components fit together well: header, responsive sidebar, table of contents, previous/next links, search dialog, and color mode needed little custom styling.
  • The template has no end-to-end content i18n setup. Parallel /en and /ja trees, path filtering, HTML language metadata, and the locale control are project additions in this sample.
  • Static export works reliably once the nested baseURL, explicit prerender routes, and directory-index output are configured.

Verifiable snapshot

ItemObserved fact
Template sourceThe official nuxt-ui-templates/docs repository
Installed UI@nuxt/ui ^4.10.0, resolved in the checked-in Bun lockfile
Content@nuxt/content ^3.15.0 with filesystem navigation and search-section queries
FrameworkNuxt 4 and Vue 3, statically generated by nuxt generate
SearchThe template calls queryCollectionSearchSections and renders UContentSearch; this sample keeps that local client path
i18nNo i18n module exists in the official template's current package.json; this sample implements authored locale paths directly
Output.output/public contains 38 locale documents as index.html files

Selection summary

Choose this template when a team wants Nuxt UI's polished components while retaining direct ownership of a conventional Nuxt application. Choose Docus when more behavior should arrive through an opinionated layer, or a smaller SSG when dependency weight and minimal client JavaScript dominate the decision.