Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#54 bulk upload entire wiki

implemented
Chris Tsai
wiki (3)
Project-Summary-Page
2013-11-15
2013-01-24
Chris Korda
No

Is there any way to upload a big collection of wiki pages all at once? I write documentation in my own markup syntax, which I can then convert to a web site, help file, or whatever via a conversion script. I could easily write another script to convert my documentation to SF markdown, but there are too many pages to upload them one by one. I would also need some way to update or regenerate the wiki, e.g. deleting all the pages and uploading them again might work. I could just give up and provide documentation only on the project web site (as I did for my other SF projects) but I'm trying to make use of the new SF tools. Is this an unusual request? Am I trying to do something wiki wasn't intended for?

Discussion

  • Chris Tsai
    Chris Tsai
    2013-01-24

    • status: unread --> pending
    • assigned_to: Chris Tsai
     
  • Chris Tsai
    Chris Tsai
    2013-01-24

    Greetings,

    What you're trying to do sounds like just the thing that the Allura API was made for, check that out and let me know if it helps!

    Regards,
    Chris Tsai, SourceForge.net Support

     
  • Chris Korda
    Chris Korda
    2013-01-24

    Hasn't anyone wrapped all these gnarly details in a higher-level interface yet? I'm no Python wiz, honestly I was hoping for something more along the lines of an "upload wiki" button, or FTP access, like the project website.

    BTW the API is so complicated that there's a CodeProject page devoted to it.
    http://www.codeproject.com/Articles/75424/Step-by-Step-Guide-to-Delicious-OAuth-API

    Regards,
    Chris

     
  • Chris Tsai
    Chris Tsai
    2013-01-24

    Ticket moved from /p/forge/site-support/2544/

    Can't be converted:

    • _page:
    • _related:
     
  • Chris Tsai
    Chris Tsai
    2013-01-24

    We do not have a bulk-upload script already written, so I've moved this ticket to our feature-request ticket tracker, so that it can be voted on and that will help gauge demand for such a built-in feature and/or API script.

     
    • Chris Korda
      Chris Korda
      2013-01-28

      Ah thank you. I was just about to ask if this thread belongs in feature requests, but you're way ahead of me.

      It seems reasonable that others will eventually bump into this same issue. One of the most obvious applications for the wiki is a user guide. Complex projects are likely to have their own tools for maintaining documentation, so that they can output it in multiple formats and/or multiple languages. Authors of such projects are not going to want to update the wiki version of their user guide--which could include many dozens of pages--one page at a time. Nor are they likely to be enthusiastic about learning the Allura API, since this would require investing a considerable amount of time which would be better spent on project development. Hence they will not use the wiki, which would be an unfortunate waste of a valuable feature.

       
  • Chris Tsai
    Chris Tsai
    2013-01-24

    • status: pending --> open
    • category: --> Project-Summary-Page
     
  • Chris Korda
    Chris Korda
    2013-02-06

    I finally waded through getting python installed, installing oauth2, etc. only to discover that it's impractical to host a user guide as a wiki with one topic per page, because the page loading delay would drive the poor reader insane. Instead it seems to make more sense to just put the user guide in a single page. In theory length could be a problem, but in practice it loads fast enough, and once it's loaded, the internal links are super-fast.

    Does this seem a reasonable approach to you? Here's a link to the wiki page:
    http://sourceforge.net/p/waveshop/wiki/WaveShop%20Help/

    Of course it doesn't look very nice due to Markdown's eccentric HTML parsing. This is the same file, but interpreted as HTML instead of Markdown:
    http://waveshop.sourceforge.net/Help/printable/WaveShopHelp.htm

    One problem (which others have apparently encountered) is that Markdown doesn't implement internal links within a document. It's possible to implement them using HTML anchors and references, but then Markdown turns the anchors blue and underlines them, which makes them look like links. How confusing is that?

     
  • Dave Brondsema
    Dave Brondsema
    2013-11-15

    • status: open --> implemented