Alternatives to Docusaurus logo

Alternatives to Docusaurus

Confluence, Gitbook, Postman, Swagger UI, and Apiary are the most popular alternatives and competitors to Docusaurus.
33
117
+ 1
3

What is Docusaurus and what are its top alternatives?

Docusaurus is a project for easily building, deploying, and maintaining open source project websites.
Docusaurus is a tool in the Documentation as a Service & Tools category of a tech stack.
Docusaurus is an open source tool with 15.3K GitHub stars and 1.5K GitHub forks. Here’s a link to Docusaurus's open source repository on GitHub

Docusaurus alternatives & related posts

Confluence logo

Confluence

6.8K
4.4K
183
6.8K
4.4K
+ 1
183
One place to share, find, and collaborate on information
Confluence logo
Confluence
VS
Docusaurus logo
Docusaurus

related Confluence posts

David Ritsema
David Ritsema
Frontend Architect at Herman Miller · | 10 upvotes · 89.6K views
atHerman MillerHerman Miller
Jira
Jira
Confluence
Confluence
GitHub
GitHub

We knew how we wanted to build our Design System, now it was time to choose the tools to get us there. The essence of Scrum is a small team of people. The team is highly flexible and adaptive. Perfect, so we'll work in 2 week sprints where each sprint can be a mix of new R&D stories, a presentation of decisions made, and showcasing key development milestones.

We are also able to run content stories in parallel, focusing development efforts around key areas of the site that our authors need first. Our stories would exist in a Jira backlog, documentation would be hosted in Confluence , and GitHub would host our codebase. If developers identify technical improvements during the sprint, they can be added as GitHub issues and transferred to Jira if we decide to represent them as stories for the Backlog. For Sprint Retrospectives, @groupmap proved to be a great way to include our remote members of the dev team.

This worked well for our team and allowed us to be flexible in what we wanted to build and how we wanted to build it. As we further defined our Backlog and estimated each story, we could accurately measure the team's capacity (velocity) and confidently estimate a launch date.

See more
Priit Kaasik
Priit Kaasik
Engineering Lead at Katana MRP · | 9 upvotes · 118.7K views
atKatana MRPKatana MRP
Slack
Slack
Jira
Jira
Intercom
Intercom
Confluence
Confluence
Bitbucket
Bitbucket
appear.in
appear.in
Papertrail
Papertrail
#RemoteTeam
#Agile
#CustomerSupportChat
#Notes
#SourceCode
#Logging
#Release
#InProductCommunication
#ContinuousDelivery
#Alerts
#Documentation
#Requirements

As a new company we could early adopt and bet on #RemoteTeam setup without cultural baggage derailing us. Our building blocks for developing remote working culture are:

  • Hiring people who are self sufficient, self-disciplined and excel at video and written communication to work remotely
  • Set up periodic ceremonies ( #DailyStandup, #Grooming, Release calls and chats etc) to keep the company rhythm / heartbeat going across remote cells
  • Regularly train your leaders to take into account remote working aspects of organizing f2f calls, events, meetups, parties etc. when communicating and organizing workflows
  • And last, but not least - select the right tools to support effective communication and collaboration:
  1. All feeds and conversations come together in Slack
  2. #Agile workflows in Jira
  3. InProductCommunication and #CustomerSupportChat in Intercom
  4. #Notes, #Documentation and #Requirements in Confluence
  5. #SourceCode and ContinuousDelivery in Bitbucket
  6. Persistent video streams between locations, demos, meetings run on appear.in
  7. #Logging and Alerts in Papertrail
See more
Gitbook logo

Gitbook

65
40
0
65
40
+ 1
0
Document Everything! For you, your users and your team
    Be the first to leave a pro
    Gitbook logo
    Gitbook
    VS
    Docusaurus logo
    Docusaurus

    related Postman posts

    Noah Zoschke
    Noah Zoschke
    Engineering Manager at Segment · | 29 upvotes · 393.6K views
    atSegmentSegment
    Postman
    Postman
    Markdown
    Markdown
    ReadMe.io
    ReadMe.io
    Swagger UI
    Swagger UI
    #Documentation
    #Api
    #QA

    We just launched the Segment Config API (try it out for yourself here) — a set of public REST APIs that enable you to manage your Segment configuration. A public API is only as good as its #documentation. For the API reference doc we are using Postman.

    Postman is an “API development environment”. You download the desktop app, and build API requests by URL and payload. Over time you can build up a set of requests and organize them into a “Postman Collection”. You can generalize a collection with “collection variables”. This allows you to parameterize things like username, password and workspace_name so a user can fill their own values in before making an API call. This makes it possible to use Postman for one-off API tasks instead of writing code.

    Then you can add Markdown content to the entire collection, a folder of related methods, and/or every API method to explain how the APIs work. You can publish a collection and easily share it with a URL.

    This turns Postman from a personal #API utility to full-blown public interactive API documentation. The result is a great looking web page with all the API calls, docs and sample requests and responses in one place. Check out the results here.

    Postman’s powers don’t end here. You can automate Postman with “test scripts” and have it periodically run a collection scripts as “monitors”. We now have #QA around all the APIs in public docs to make sure they are always correct

    Along the way we tried other techniques for documenting APIs like ReadMe.io or Swagger UI. These required a lot of effort to customize.

    Writing and maintaining a Postman collection takes some work, but the resulting documentation site, interactivity and API testing tools are well worth it.

    See more
    Nicholas Rogoff
    Nicholas Rogoff
    at Avanade UK Ltd. · | 7 upvotes · 227.8K views
    atNHS Digital (NHS.UK)NHS Digital (NHS.UK)
    .NET Core
    .NET Core
    C#
    C#
    Microsoft SQL Server
    Microsoft SQL Server
    JavaScript
    JavaScript
    jQuery
    jQuery
    Git
    Git
    Azure DevOps
    Azure DevOps
    Postman
    Postman
    Newman
    Newman
    Visual Studio Code
    Visual Studio Code
    Visual Studio
    Visual Studio

    Secure Membership Web API backed by SQL Server. This is the backing API to store additional profile and complex membership metadata outside of an Azure AD B2C provider. The front-end using the Azure AD B2C to allow 3rd party trusted identity providers to authenticate. This API provides a way to add and manage more complex permission structures than can easily be maintained in Azure AD.

    We have .Net developers and an Azure infrastructure environment using server-less functions, logic apps and SaaS where ever possible. For this service I opted to keep it as a classic WebAPI project and deployed to AppService.

    • Trusted Authentication Provider: @AzureActiveDirectoryB2C
    • Frameworks: .NET Core
    • Language: C# , Microsoft SQL Server , JavaScript
    • IDEs: Visual Studio Code , Visual Studio
    • Libraries: jQuery @EntityFramework, @AutoMapper, @FeatureToggle , @Swashbuckle
    • Database: @SqlAzure
    • Source Control: Git
    • Build and Release Pipelines: Azure DevOps
    • Test tools: Postman , Newman
    • Test framework: @nUnit, @moq
    • Infrastructure: @AzureAppService, @AzureAPIManagement
    See more

    related Swagger UI posts

    Noah Zoschke
    Noah Zoschke
    Engineering Manager at Segment · | 29 upvotes · 393.6K views
    atSegmentSegment
    Postman
    Postman
    Markdown
    Markdown
    ReadMe.io
    ReadMe.io
    Swagger UI
    Swagger UI
    #Documentation
    #Api
    #QA

    We just launched the Segment Config API (try it out for yourself here) — a set of public REST APIs that enable you to manage your Segment configuration. A public API is only as good as its #documentation. For the API reference doc we are using Postman.

    Postman is an “API development environment”. You download the desktop app, and build API requests by URL and payload. Over time you can build up a set of requests and organize them into a “Postman Collection”. You can generalize a collection with “collection variables”. This allows you to parameterize things like username, password and workspace_name so a user can fill their own values in before making an API call. This makes it possible to use Postman for one-off API tasks instead of writing code.

    Then you can add Markdown content to the entire collection, a folder of related methods, and/or every API method to explain how the APIs work. You can publish a collection and easily share it with a URL.

    This turns Postman from a personal #API utility to full-blown public interactive API documentation. The result is a great looking web page with all the API calls, docs and sample requests and responses in one place. Check out the results here.

    Postman’s powers don’t end here. You can automate Postman with “test scripts” and have it periodically run a collection scripts as “monitors”. We now have #QA around all the APIs in public docs to make sure they are always correct

    Along the way we tried other techniques for documenting APIs like ReadMe.io or Swagger UI. These required a lot of effort to customize.

    Writing and maintaining a Postman collection takes some work, but the resulting documentation site, interactivity and API testing tools are well worth it.

    See more
    Tim Nolet
    Tim Nolet
    Founder, Engineer & Dishwasher at Checkly · | 7 upvotes · 146.8K views
    atChecklyHQChecklyHQ
    JavaScript
    JavaScript
    Node.js
    Node.js
    hapi
    hapi
    Vue.js
    Vue.js
    Swagger UI
    Swagger UI
    Slate
    Slate

    JavaScript Node.js hapi Vue.js Swagger UI Slate

    Two weeks ago we released the public API for Checkly. We already had an API that was serving our frontend Vue.js app. We decided to create an new set of API endpoints and not reuse the already existing one. The blog post linked below details what parts we needed to refactor, what parts we added and how we handled generating API documentation. More specifically, the post dives into:

    • Refactoring the existing Hapi.js based API
    • API key based authentication
    • Refactoring models with Objection.js
    • Validating plan limits
    • Generating Swagger & Slate based documentation
    See more

    related ReadMe.io posts

    Noah Zoschke
    Noah Zoschke
    Engineering Manager at Segment · | 29 upvotes · 393.6K views
    atSegmentSegment
    Postman
    Postman
    Markdown
    Markdown
    ReadMe.io
    ReadMe.io
    Swagger UI
    Swagger UI
    #Documentation
    #Api
    #QA

    We just launched the Segment Config API (try it out for yourself here) — a set of public REST APIs that enable you to manage your Segment configuration. A public API is only as good as its #documentation. For the API reference doc we are using Postman.

    Postman is an “API development environment”. You download the desktop app, and build API requests by URL and payload. Over time you can build up a set of requests and organize them into a “Postman Collection”. You can generalize a collection with “collection variables”. This allows you to parameterize things like username, password and workspace_name so a user can fill their own values in before making an API call. This makes it possible to use Postman for one-off API tasks instead of writing code.

    Then you can add Markdown content to the entire collection, a folder of related methods, and/or every API method to explain how the APIs work. You can publish a collection and easily share it with a URL.

    This turns Postman from a personal #API utility to full-blown public interactive API documentation. The result is a great looking web page with all the API calls, docs and sample requests and responses in one place. Check out the results here.

    Postman’s powers don’t end here. You can automate Postman with “test scripts” and have it periodically run a collection scripts as “monitors”. We now have #QA around all the APIs in public docs to make sure they are always correct

    Along the way we tried other techniques for documenting APIs like ReadMe.io or Swagger UI. These required a lot of effort to customize.

    Writing and maintaining a Postman collection takes some work, but the resulting documentation site, interactivity and API testing tools are well worth it.

    See more
    Todd Gardner
    Todd Gardner
    President at TrackJS · | 4 upvotes · 292.2K views
    atTrackJSTrackJS
    Jekyll
    Jekyll
    GitHub Pages
    GitHub Pages
    ReadMe.io
    ReadMe.io
    Read the Docs
    Read the Docs
    Gatsby
    Gatsby

    We recently needed to rebuild our documentation site, currently built using Jekyll hosted on GitHub Pages. We wanted to update the content and refresh the style to make it easier to find answers.

    We considered hosted services that could accept our markdown content, like ReadMe.io and Read the Docs, however both seemed expensive for essentially hosting the same platform we already had for free.

    I also looked at the Gatsby Static Site generator to modernize Jekyll. I don't think this is a fit, as our documentation is relatively simple and relies heavily on Markdown. Jekyll excels at Markdown, while Gatsby seemed to struggle with it.

    We chose to stick with the current platform and just refresh our template and style with some add-on JavaScript.

    See more
    jsdoc logo

    jsdoc

    68
    58
    0
    68
    58
    + 1
    0
    An API documentation generator for JavaScript
      Be the first to leave a pro
      jsdoc logo
      jsdoc
      VS
      Docusaurus logo
      Docusaurus
      Read the Docs logo

      Read the Docs

      48
      67
      16
      48
      67
      + 1
      16
      Create, host, and browse documentation
      Read the Docs logo
      Read the Docs
      VS
      Docusaurus logo
      Docusaurus

      related Read the Docs posts

      Todd Gardner
      Todd Gardner
      President at TrackJS · | 4 upvotes · 292.2K views
      atTrackJSTrackJS
      Jekyll
      Jekyll
      GitHub Pages
      GitHub Pages
      ReadMe.io
      ReadMe.io
      Read the Docs
      Read the Docs
      Gatsby
      Gatsby

      We recently needed to rebuild our documentation site, currently built using Jekyll hosted on GitHub Pages. We wanted to update the content and refresh the style to make it easier to find answers.

      We considered hosted services that could accept our markdown content, like ReadMe.io and Read the Docs, however both seemed expensive for essentially hosting the same platform we already had for free.

      I also looked at the Gatsby Static Site generator to modernize Jekyll. I don't think this is a fit, as our documentation is relatively simple and relies heavily on Markdown. Jekyll excels at Markdown, while Gatsby seemed to struggle with it.

      We chose to stick with the current platform and just refresh our template and style with some add-on JavaScript.

      See more
      Slate logo

      Slate

      27
      56
      7
      27
      56
      + 1
      7
      Beautiful static documentation for your API, inspired by Stripe's and Paypal's API docs
      Slate logo
      Slate
      VS
      Docusaurus logo
      Docusaurus

      related Slate posts

      Tim Nolet
      Tim Nolet
      Founder, Engineer & Dishwasher at Checkly · | 7 upvotes · 146.8K views
      atChecklyHQChecklyHQ
      JavaScript
      JavaScript
      Node.js
      Node.js
      hapi
      hapi
      Vue.js
      Vue.js
      Swagger UI
      Swagger UI
      Slate
      Slate

      JavaScript Node.js hapi Vue.js Swagger UI Slate

      Two weeks ago we released the public API for Checkly. We already had an API that was serving our frontend Vue.js app. We decided to create an new set of API endpoints and not reuse the already existing one. The blog post linked below details what parts we needed to refactor, what parts we added and how we handled generating API documentation. More specifically, the post dives into:

      • Refactoring the existing Hapi.js based API
      • API key based authentication
      • Refactoring models with Objection.js
      • Validating plan limits
      • Generating Swagger & Slate based documentation
      See more
      Ardoq logo

      Ardoq

      10
      15
      4
      10
      15
      + 1
      4
      SaaS Platform focusing on automating and visualizing your documentation.
      Ardoq logo
      Ardoq
      VS
      Docusaurus logo
      Docusaurus
      DocGen logo

      DocGen

      7
      10
      0
      7
      10
      + 1
      0
      Better documentation for software products
        Be the first to leave a pro
        DocGen logo
        DocGen
        VS
        Docusaurus logo
        Docusaurus
        MireDot logo

        MireDot

        5
        5
        14
        5
        5
        + 1
        14
        Generate your Java REST API Documentation in 5 Minutes
        MireDot logo
        MireDot
        VS
        Docusaurus logo
        Docusaurus
        Wiki.js logo

        Wiki.js

        5
        1
        0
        5
        1
        + 1
        0
        A wiki engine running on Node.js and written in JavaScript
          Be the first to leave a pro
          Wiki.js logo
          Wiki.js
          VS
          Docusaurus logo
          Docusaurus
          Docsify logo

          Docsify

          5
          12
          0
          5
          12
          + 1
          0
          A documentation site generator without the static html files
            Be the first to leave a pro
            Docsify logo
            Docsify
            VS
            Docusaurus logo
            Docusaurus
            Airstory logo

            Airstory

            4
            3
            0
            4
            3
            + 1
            0
            A writing software with upgrade options for businesses that have advanced needs, like personal support
              Be the first to leave a pro
              Airstory logo
              Airstory
              VS
              Docusaurus logo
              Docusaurus
              ESDoc logo

              ESDoc

              3
              3
              0
              3
              3
              + 1
              0
              Used to generate the documentation of JavaScript projects
                Be the first to leave a pro
                ESDoc logo
                ESDoc
                VS
                Docusaurus logo
                Docusaurus
                Dimer logo

                Dimer

                3
                26
                0
                3
                26
                + 1
                0
                Dimer generates a clean and beautiful documentation website from Markdown.
                  Be the first to leave a pro
                  Dimer logo
                  Dimer
                  VS
                  Docusaurus logo
                  Docusaurus
                  zeroheight logo

                  zeroheight

                  2
                  5
                  0
                  2
                  5
                  + 1
                  0
                  UX design docs that stay up-to-date
                    Be the first to leave a pro
                    zeroheight logo
                    zeroheight
                    VS