You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by "Dmitry Blotsky (JIRA)" <ji...@apache.org> on 2018/03/02 19:04:00 UTC
[jira] [Commented] (CB-13941) Why should Plugin APIs be included in
the docs?
[ https://issues.apache.org/jira/browse/CB-13941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16383992#comment-16383992 ]
Dmitry Blotsky commented on CB-13941:
-------------------------------------
I believe this was done for convenience: it's nice to have the plugin docs be part of the whole site, and be styled the same way. This way also the site search can index them, and we capture plugin docs for older versions (at least mostly correctly). Also, this sounds like an Improvement or a Feature, not a Bug.
> Why should Plugin APIs be included in the docs?
> -----------------------------------------------
>
> Key: CB-13941
> URL: https://issues.apache.org/jira/browse/CB-13941
> Project: Apache Cordova
> Issue Type: Bug
> Components: cordova-docs
> Reporter: Jan Piotrowski (Sujan)
> Priority: Major
>
> What is the use of copying the plugin documentation over to the website?
> These are is always less current than the actual GitHub README itself and also has strange effects on both sides (Frontmatter on GitHub, outdated README without version info in old Cordova docs, strange badge tables in Cordova docs).
> Having a list of Core Plugins with links to the actual documentation of them of course makes total sense and could replace the copied over READMEs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org