+1 for keeping them with the code.
On Thu, Jul 23, 2015 at 1:58 PM, Victor Sosa wrote:
> +1 on keeping them where they are.
> For me, and I bet for many as well, having to search for plugins on npmjs
> makes it easy to read the docs there. I know there is work refining the
> search in plugins.cor
+1 on keeping them where they are.
For me, and I bet for many as well, having to search for plugins on npmjs
makes it easy to read the docs there. I know there is work refining the
search in plugins.cordova.io as it is right now it's kind of useless just
for the fact that I cannot have a context (d
+1 for keep docs where they are.
23 Июл 2015 г. 22:52 пользователь "Steven Gill"
написал:
> +1 to keep them with the code. The readme is the English doc currently for
> our plugins.
> On Jul 22, 2015 11:10 PM, "Carlos Santana" wrote:
>
> > It was discuss in the past. And we decided to have the d
+1 to keep them with the code. The readme is the English doc currently for
our plugins.
On Jul 22, 2015 11:10 PM, "Carlos Santana" wrote:
> It was discuss in the past. And we decided to have the docs together with
> the code.
>
> Easier for contributors to find the doc affected by the code change
It was discuss in the past. And we decided to have the docs together with
the code.
Easier for contributors to find the doc affected by the code change.
Easier to keep the doc corresponding to the correct version of the code.
On Thu, Jul 23, 2015 at 1:37 AM Dmitry Blotsky
wrote:
> Hi folks,
>
>
Hi folks,
If we move core plugin docs to our main docs website, where would we like our
plugin docs source (the Markdown files) to live? There are two options:
1. Keep the Markdown files in their respective plugin repos, and fetch them
when the docs site is built
2. Keep the Markdown files in th
