cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carlos Santana <>
Subject Re: What's Stopping us From Independent Platform Releases
Date Thu, 21 Aug 2014 01:59:58 GMT
Yes Ray, that's what I meant as a new Design for the Docs website. To be a
consolidated simple view of the docs, but the real docs will be associated
with each component as an implementation detail.

It can also be a consolidated view of docs as utility of the cordova CLI,
for example "$cordova docs" launches a local web server, open the browser,
and serves a local website with the content coming form the versions of the
things being used in your cordova project/folder (ios, plugin1, plugin2)

We need to try different things, get feedback and iterate

And feedback from coming form developers such as yourself.


On Wed, Aug 20, 2014 at 8:58 PM, Ray Camden <> wrote:

> Keep in mind - the average developer probably has no idea what
> cordova-ios, cordova-cli, and cordova-lib means. They npm install cordova,
> and to them, that's it.
> ________________________________________
> From: Carlos Santana <>
> Sent: Wednesday, August 20, 2014 7:54 PM
> To:
> Subject: Re: What's Stopping us From Independent Platform Releases
> I think we need to come down to the same conclusion as we did for plugins.
> The documentation for each "component" meaning "cordova-ios",
> "cordova-cli", "cordova-lib" needs to live with it's repo/code and version
> together.
> The remaining things can be left in cordova-docs that are independent of a
> version of a component to an extent like security guide.
> The Cordova Docs Website will need to have a new UX design to make sense of
> where links point and somehow allow the user know what's the latest release
> and the different components with each respective version.

Carlos Santana

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