Okay~~~ https://jenkins-wiki-exporter.g4v.dev/ is now updated to support markdown, or a zip of markdown + images
Gavin On Sun, Oct 20, 2019 at 2:11 PM Gavin Mogan <ga...@gavinmogan.com> wrote: > Thanks for the PR, I've deployed the change, and started to get prepped > for straight up markdown, markdown + zip with images, and eventually adoc > > I'm totally up for forking it to infra or something, I have no idea how to > do that though. > > On Sun, Oct 20, 2019 at 1:50 AM Oleg Nenashev <o.v.nenas...@gmail.com> > wrote: > >> Thanks Gavin! >> >> I submitted the pull request for truncating RAW HTML which should improve >> the layout. More pull requests to come soon. I would suggest hosting this >> service on jenkinsci or jenkins-infra. I think we can get a lot of >> contributions. Also, I think we should reserve opportunities to add support >> of Asciidoc export for jenkins.io and README.adoc later, so probably the >> final name could be `jenkins-wiki-exporter` or so. >> >> One of the topics we will need to think about is images. Right now the >> tool references images from Confluence, which is a bad idea. >> I will try to reimplement by guidelines in JS and to add support of ZIP >> download if you agree, Gavin. It will imply some temporary file magic. >> >> BR, Oleg >> >> >> On Saturday, October 19, 2019 at 9:54:25 PM UTC+2, Gavin Mogan wrote: >>> >>> Last night I started a little web app to make the migration easier for >>> people >>> >>> https://jenkins-wiki-md.g4v.dev/ (for example, try out "blueocean") >>> >>> I have to incorporate some of the items oleg mentioned in the doc, but >>> its a start. >>> >>> Gavin >>> >>> >>> On Sat, Oct 19, 2019 at 12:53 AM Oleg Nenashev <o.v.n...@gmail.com> >>> wrote: >>> >>>> First version of the plugin Wiki=>GitHub migration guide is available >>>> here: >>>> https://jenkins.io/doc/developer/publishing/wiki-page/#migrating-from-wiki-to-github >>>> Later it will be improved once I finish the migration tool on the top >>>> of Pandoc >>>> >>>> Could use GitHub topics? Or just add to the readme >>>>> >>>> >>>> Yes, I agree we should use GitHub topics. I already have a prototype of >>>> integration between GitHub topics and the plugin site, and we can also >>>> replace queries on the Wiki page while moving it to jenkins.io >>>> >>>> On Friday, October 18, 2019 at 6:52:02 PM UTC+2, Tim Jacomb wrote: >>>>> >>>>> Could use GitHub topics? Or just add to the readme >>>>> >>>>> On Fri, 18 Oct 2019 at 15:24, Robert Sandell <rsan...@cloudbees.com> >>>>> wrote: >>>>> >>>>>> And how do I mark a plugin as up for adoption without the wiki labels? >>>>>> >>>>>> /B >>>>>> >>>>>> Den fre 18 okt. 2019 kl 14:52 skrev Jesse Glick <jgl...@cloudbees.com >>>>>> >: >>>>>> >>>>>>> On Fri, Oct 18, 2019 at 6:27 AM Daniel Beck <m...@beckweb.net> >>>>>>> wrote: >>>>>>> > I propose that we restore write access for plugin maintainers at >>>>>>> least for a time, to allow them to clear out wiki pages after migrating >>>>>>> the >>>>>>> content elsewhere. >>>>>>> >>>>>>> Makes sense, but is there some plan to notify maintainers of plugins >>>>>>> who have not done this? There are a couple thousand pages out there, >>>>>>> and many people will not see mailing list notifications reliably. >>>>>>> >>>>>>> -- >>>>>>> You received this message because you are subscribed to the Google >>>>>>> Groups "Jenkins Developers" group. >>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>> send an email to jenkin...@googlegroups.com. >>>>>>> To view this discussion on the web visit >>>>>>> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1k8X17Z3P%2Bs89%2BmUnUXtJW%2BiM2zMc09hPu9_AQ08_k6A%40mail.gmail.com >>>>>>> . >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> *Robert Sandell* >>>>>> Software Engineer >>>>>> CloudBees, Inc. >>>>>> [image: CloudBees-Logo.png] <http://www.cloudbees.com/> >>>>>> E: rsan...@cloudbees.com >>>>>> Twitter: robert_sandell >>>>>> >>>>>> -- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "Jenkins Developers" group. >>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>> send an email to jenkin...@googlegroups.com. >>>>>> To view this discussion on the web visit >>>>>> https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS01y0687MwFnRZvXX3jEsGW5iPVNre6ymGUDuC90sDMpA%40mail.gmail.com >>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS01y0687MwFnRZvXX3jEsGW5iPVNre6ymGUDuC90sDMpA%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>>>> . >>>>>> >>>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Jenkins Developers" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to jenkin...@googlegroups.com. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/jenkinsci-dev/c9d5e4ee-6987-4138-9b48-299b3e58cb7e%40googlegroups.com >>>> <https://groups.google.com/d/msgid/jenkinsci-dev/c9d5e4ee-6987-4138-9b48-299b3e58cb7e%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to jenkinsci-dev+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/282c2420-40a7-4f91-b74c-12f00bfa4edd%40googlegroups.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/282c2420-40a7-4f91-b74c-12f00bfa4edd%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DusEXTw2jgo6Dw1uRD_hpGBEH9njO6RPcvLuzrpbEaEEwA%40mail.gmail.com.
