Hi, all!

For those of you who work in organizations that do decent documentation, what are you using?

We currently just have a bunch of word docs in a SharePoint document library. I’ve previously used dedicated solutions for this such as Bookstack and Confluence. The company is very anti-Atlassian, so Confluence is out.

Just want to see what y’all are using as I search for a better solution.

Thanks!

  • mythnubb@vlemmy.net
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    Not using it, but Bookstack looked real nice for a documentation site.

    We’re using a different wiki at the moment for it.

    • Scott@beehaw.org
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      We’ve been migrating a lot of documentation into Bookstack this year, and like it a lot so far.

    • Scrappy Duncan@lemm.ee
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      I setup bookstack at my last job and personally loved it. But yeah, takes a lot to get everyone on board with something like that. I liked that you could export stuff out of it easily too. Bridges the gap if you need to email documentation.

  • bladewdr@infosec.pub
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    I recently migrated all our various Excel and Word documents from Sharepoint into a self-hosted Bookstack instance. I love it.

    I have one shelf for stuff like SOP, contracts, etc, and another for customer documentation.

  • jocose
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    1 year ago

    Matterport tours. This is by far one of the best decisions we have made. We have notes, photos, documents, all linked in a 3D space of the site. We also use photogrammetry generated from drone footage for some of the larger exterior spaces and our wireless runs.

    If we are on the phone with a client we usually pull the tour up in one window and the text notes up in another and we can walk them through anything. We also do cameras so I often link the cameras in the tour so we can just click and have Realtime interactions and see what the issue is.

  • g7s
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    We use WikiJs for documentation and user guides

      • g7s
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        I had to get used to it a little bit but I love it now as well. Especially nice thing is that you can connect it to a ldap server for accounts :)

  • flof@feddit.de
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    You could have them take s look at XWiki - Tomcat-based, very Confluence-like, open source.

  • bamboo@beehaw.org
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    What are you using for bug tracking? IMO, the two should be hand in hand. If you’re using GitHub issues, then GitHub wiki would make sense to me.

    I’ve never had good luck using SharePoint or Google Docs for documentation, it just gets lost. If you’re searching GitHub for an issue, it’s easy to expand the search to include wiki. Having documentation in a separate system means searching two places, which is not ideal.

  • fourstepper
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    For technical documentation, most of our teams are currently using Gitlab pages, however we are steadily moving to Backstage

    • StaticFlow@feddit.uk
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      How is backstage? I look at it and feel perhaps we should just be using all the features of gitlab. Does it really bring something better to the table?

      • fourstepper
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        Depends on how far you are looking to take it, I would say. Generally, I can see how a larger organization (around 500 people) can benefit from it, at the same time I can see how it can be a massive waste of time in other orgs.

  • polystruct@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    Currently Confluence. We do have a split documentation policy, where long-lived and broadly communicated information should be on M365 (SharePoint and affiliated services) whereas more technical or short-lived (project) documentation is on Confluence.

    But even certain broad-use information is showing up on Confluence more and more given it’s easier use (wiki and plugins like the draw.io support).

    • kalipike@lemmy.oneOP
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Cool, thanks for sharing! Yeah I think it would be hard to convince anyone to use anything but SharePoint but I’m just formating options. Definitely want as little friction but with decent structure as possible to encourage active use of it.

    • kalipike@lemmy.oneOP
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      I love the look of ITGlue and one member of our team used it at several other orgs and loved it. It just seems pretty overkill with all the features since we have other platforms that handle the passwords/secrets/assets/etc. I do like the look of it though, and am considering it.