nuxt/create-nuxt-app

Add i18n as a step in the process

Open

#35 opened on Feb 15, 2018

View on GitHub
 (0 comments) (0 reactions) (0 assignees)JavaScript (442 forks)batch import
hacktoberfest

Repository metrics

Stars
 (3,451 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Title says it all, there is an i18n example in the documentation, though I think i18next would be preferable.

The documentation example, however, is naïve, it places the locales in one folder, which is okay for a framework default and as a starting point. As a developer with some localization experience I prefer to make each class/plugin/component etc. have their data, configuration, locales, etc. in the same place for maintenance and of course for creating parts that do one thing only.

I guess it's up to me to tool this?

Contributor guide

Research direction
Tech stack
Domain
Issue type
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Prerequisites
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.