[Jenkins-infra] Ideas for plugin existing docs/seo/etc

[Gavin]

Ack, re-sending to infra using gmail address

On Mon, Jan 27, 2020 at 8:34 PM Gavin Mogan <gavin at gavinmogan.com> wrote:

> * Migrate all existing wiki (which is read only) to a single github repo,
> which can be edited as needed by docs team. If a maintainer wants to update
> docs, they need to fix the <url> in their plugin
>   * I've started a script/repo to mass convert using the exporter tool
>   *
> https://github.com/halkeye/_all_plugin_docs/blob/master/index.js#L8-L57
> is a list of plugins with missing docs
> * Once the plugin site (& api) are using the github, then setup redirects
> for confluence to redirect any existing wiki link to automatically goto
> plugins.jenkins.io/$name
> * Once https://github.com/jenkins-infra/jenkins-infra/pull/1410 gets
> merged, and we have some stats, start setting up redirects from any pages
> that have new migrated content, such as
> https://wiki.jenkins.io/display/JENKINS/Building+Jenkins to
> https://github.com/jenkinsci/jenkins/blob/master/CONTRIBUTING.md
> * If https://github.com/jenkins-infra/plugin-site-api/pull/79 gets
> merged, then pulling full file paths from github (such as $plugin/README.md
> or $plugin/README.adoc instead of $plugin) should be super fast and cheap
> Site note - does github not support asciidoc well? should I be migrating
> to markdown?
>
> https://github.com/halkeye/_all_plugin_docs/blob/master/content/clone-workspace-scm/README.adoc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20200127/b80b6355/attachment.html>