cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Grieve <>
Subject Re: [Input request] Rethinking Plugin docs
Date Mon, 24 Feb 2014 17:32:36 GMT
My thoughts here:

- We may also want to include files in the translations.
- I like not having a subdir for en/ so as to differentiate it as the one
the others are based off of
- We don't need the version in the directory since we can use git tags to
find old versions


The plan is to render these on, so we can certainly add
logic there to maintain language pref.

On Mon, Feb 24, 2014 at 11:13 AM, Lisa Seacat DeLuca <>wrote:

> I noticed for the 3.4 release that the documentation for each of the
> plugins redirects to the github repository for each plugin and a document
> under doc/
> If we want to have translations for each of the plugins then we're going
> to need to rethink this a little.  Here are two options:
> 1. similar to the cordova-docs dir, we could have a language directory as
> the parent.
> ex. doc/en/
> and while we're at it we probably need the version as well
> ex. doc/en/3.4.0/
> If we do this then at least we can have the documentation for each
> language.  But that doesn't solve the problem of the user being always
> redirected to the english version of the documentation and not their
> specific language.
> 2. Is it hard to do a build of the for each plugin similar to
> how we build the cordova-doc md files into html files?  If it were seamless
> and part of the other documentation it would make my life
> *coughTranslationcough* so much easier.  Plus it won't be as confusing on
> end users having to choose their language more than one time.
> It'd be nice to get some input from everyone before I start writing a
> complicated automated script for the plugin translations.
> Lisa
> Lisa Seacat DeLuca
> Mobile Engineer | t: +415.787.4589 | **<>|
> ** <> | **<>|
> follow @LisaSeacat on twitter] <>| [image:
> follow Lisa Seacat DeLuca on linkedin]<>

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message