Alternatives to MediaWiki logo

Alternatives to MediaWiki

Microsoft SharePoint, WordPress, Confluence, DokuWiki, and Drupal are the most popular alternatives and competitors to MediaWiki.
165
79
+ 1
0

What is MediaWiki and what are its top alternatives?

It is a free server-based software. It is an extremely powerful, scalable software and a feature-rich wiki implementation that uses PHP to process and display data stored in a database, such as MySQL.
MediaWiki is a tool in the Knowledge Management category of a tech stack.

Top Alternatives to MediaWiki

  • Microsoft SharePoint
    Microsoft SharePoint

    It empowers teamwork with dynamic and productive team sites for every project team, department, and division. Share and manage content, knowledge, and applications to empower teamwork, quickly find information, and seamlessly collaborate across the organization. ...

  • WordPress
    WordPress

    The core software is built by hundreds of community volunteers, and when you’re ready for more there are thousands of plugins and themes available to transform your site into almost anything you can imagine. Over 60 million people have chosen WordPress to power the place on the web they call “home” — we’d love you to join the family. ...

  • Confluence
    Confluence

    Capture the knowledge that's too often lost in email inboxes and shared network drives in Confluence instead – where it's easy to find, use, and update. ...

  • DokuWiki
    DokuWiki

    It is a simple to use and highly versatile Open Source wiki software that doesn't require a database. It has clean and readable syntax. The ease of maintenance, backup and integration makes it an administrator's favorite. Built in access controls and authentication connectors make it especially useful in the enterprise context and the large number of plugins contributed by its vibrant community allow for a broad range of use cases beyond a traditional wiki. ...

  • Drupal
    Drupal

    Drupal is an open source content management platform powering millions of websites and applications. It’s built, used, and supported by an active and diverse community of people around the world. ...

  • XWiki
    XWiki

    It is a free wiki software platform written in Java with a design emphasis on extensibility. It is an enterprise wiki. It includes WYSIWYG editing, OpenDocument based document import/export, semantic annotations and tagging, and advanced permissions management. ...

  • Markdown
    Markdown

    Markdown is two things: (1) a plain text formatting syntax; and (2) a software tool, written in Perl, that converts the plain text formatting to HTML. ...

  • Obsidian
    Obsidian

    It is a powerful knowledge base that works on top of a local folder of plain text Markdown files. ...

MediaWiki alternatives & related posts

Microsoft SharePoint logo

Microsoft SharePoint

379
261
6
Content collaboration for the modern workplace
379
261
+ 1
6
PROS OF MICROSOFT SHAREPOINT
  • 2
    Great online support
  • 1
    Perfect version control
  • 1
    Stable Platform
  • 1
    Seamless intergration with MS Office
  • 1
    Secure
CONS OF MICROSOFT SHAREPOINT
  • 2
    Rigid, hard to add external applicaions
  • 1
    User interface. Steep learning curve, old-fashioned

related Microsoft SharePoint posts

WordPress logo

WordPress

90.3K
33.8K
2.1K
A semantic personal publishing platform with a focus on aesthetics, web standards, and usability.
90.3K
33.8K
+ 1
2.1K
PROS OF WORDPRESS
  • 412
    Customizable
  • 362
    Easy to manage
  • 351
    Plugins & themes
  • 258
    Non-tech colleagues can update website content
  • 246
    Really powerful
  • 144
    Rapid website development
  • 77
    Best documentation
  • 51
    Codex
  • 44
    Product feature set
  • 35
    Custom/internal social network
  • 16
    Open source
  • 8
    Great for all types of websites
  • 6
    Huge install and user base
  • 5
    Best
  • 5
    It's simple and easy to use by any novice
  • 5
    Perfect example of user collaboration
  • 5
    Open Source Community
  • 5
    Most websites make use of it
  • 5
    I like it like I like a kick in the groin
  • 4
    Community
  • 4
    API-based CMS
  • 3
    Easy To use
  • 2
    <a href="https://secure.wphackedhel">Easy Beginner</a>
CONS OF WORDPRESS
  • 12
    Plugins are of mixed quality
  • 12
    Hard to keep up-to-date if you customize things
  • 9
    Not best backend UI
  • 2
    Complex Organization
  • 1
    Great Security

related WordPress posts

Dale Ross
Independent Contractor at Self Employed · | 22 upvotes · 1.2M views

I've heard that I have the ability to write well, at times. When it flows, it flows. I decided to start blogging in 2013 on Blogger. I started a company and joined BizPark with the Microsoft Azure allotment. I created a WordPress blog and did a migration at some point. A lot happened in the time after that migration but I stopped coding and changed cities during tumultuous times that taught me many lessons concerning mental health and productivity. I eventually graduated from BizSpark and outgrew the credit allotment. That killed the WordPress blog.

I blogged about writing again on the existing Blogger blog but it didn't feel right. I looked at a few options where I wouldn't have to worry about hosting cost indefinitely and Jekyll stood out with GitHub Pages. The Importer was fairly straightforward for the existing blog posts.

Todo * Set up redirects for all posts on blogger. The URI format is different so a complete redirect wouldn't work. Although, there may be something in Jekyll that could manage the redirects. I did notice the old URLs were stored in the front matter. I'm working on a command-line Ruby gem for the current plan. * I did find some of the lost WordPress posts on archive.org that I downloaded with the waybackmachinedownloader. I think I might write an importer for that. * I still have a few Disqus comment threads to map

See more
Siddhant Sharma
Tech Connoisseur at Channelize.io · | 12 upvotes · 916.8K views

WordPress Magento PHP Java Swift JavaScript

Back in the days, we started looking for a date on different matrimonial websites as there were no Dating Applications. We used to create different profiles. It all changed in 2012 when Tinder, an Online Dating application came into India Market.

Tinder allowed us to communicate with our potential soul mates. That too without paying any extra money. I too got 4-6 matches in 6 years. It changed the life of many Millennials. Tinder created a revolution of its own. P.S. - I still don't have a date :(

Posting my first article. Please have a look and do give feedback.

Communication InAppChat Dating Matrimonial #messaging

See more
Confluence logo

Confluence

23K
16.6K
200
One place to share, find, and collaborate on information
23K
16.6K
+ 1
200
PROS OF CONFLUENCE
  • 93
    Wiki search power
  • 62
    WYSIWYG editor
  • 42
    Full featured, works well with embedded docs
  • 3
    Expensive licenses
CONS OF CONFLUENCE
  • 3
    Expensive license

related Confluence posts

David Ritsema
Frontend Architect at Herman Miller · | 11 upvotes · 650.3K views

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
Engineering Lead at Katana MRP · | 9 upvotes · 499.5K views

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
DokuWiki logo

DokuWiki

67
92
0
Open Source wiki software that doesn't require a database
67
92
+ 1
0
PROS OF DOKUWIKI
    Be the first to leave a pro
    CONS OF DOKUWIKI
      Be the first to leave a con

      related DokuWiki posts

      Drupal logo

      Drupal

      10.2K
      3.3K
      346
      Free, Open, Modular CMS written in PHP
      10.2K
      3.3K
      + 1
      346
      PROS OF DRUPAL
      • 73
        Stable, highly functional cms
      • 59
        Great community
      • 43
        Easy cms to make websites
      • 41
        Highly customizable
      • 21
        Digital customer experience delivery platform
      • 16
        Really powerful
      • 15
        Customizable
      • 10
        Flexible
      • 10
        Good tool for prototyping
      • 8
        Enterprise proven over many years when others failed
      • 7
        Open source
      • 7
        Each version becomes more intuitive for clients to use
      • 7
        Well documented
      • 7
        Headless adds even more power/flexibility
      • 6
        Lego blocks methodology
      • 4
        Caching and performance
      • 3
        Powerful
      • 3
        Built on Symfony
      • 3
        Can build anything
      • 2
        Views
      • 1
        API-based CMS
      CONS OF DRUPAL
      • 1
        Steep learning curve
      • 1
        DJango

      related Drupal posts

      Hi, I am working as a web developer (PHP, Laravel, AngularJS, and MySQL) with more than 8 years of experience and looking for a tech stack that pays better. I have a little bit of knowledge of Core Java. For better opportunities, Should I learn Java, Spring Boot or Python. Or should I learn Drupal, WordPress or Magento? Any guidance would be really appreciated! Thanks.

      See more
      Jan Vlnas
      Developer Advocate at Superface · | 4 upvotes · 2.6K views

      Depends on what options and technologies you have available, and how do you deploy your website.

      There are CMSs which update existing static pages through FTP: You provide access credentials, mark editable parts of your HTML in a markup, and then edit the content through the hosted CMS. I know two systems which work like that: Cushy CMS and Surreal CMS.

      If the source of your site is versioned through Git (and hosted on GitHub), you have other options, like Netlify CMS, Spinal CMS, Siteleaf, Forestry, or CloudCannon. Some of these also need you to use static site generator (like 11ty, Jekyll, or Hugo).

      If you have some server-side scripting support available (typically PHP) you can also consider some flat-file based, server-side systems, like Kirby CMS or Lektor, which are usually simpler to retrofit into an existing template than “traditional” CMSs (WordPress, Drupal).

      Finally, you could also use a desktop-based static site generator which provides a user-friendly GUI, and then locally generates and uploads the website. For example Publii, YouDoCMS, Agit CMS.

      See more
      XWiki logo

      XWiki

      15
      27
      0
      The Advanced Open Source Enterprise Wiki
      15
      27
      + 1
      0
      PROS OF XWIKI
        Be the first to leave a pro
        CONS OF XWIKI
          Be the first to leave a con

          related XWiki posts

          Markdown logo

          Markdown

          18.5K
          13.8K
          961
          Text-to-HTML conversion tool/syntax for web writers, by John Gruber
          18.5K
          13.8K
          + 1
          961
          PROS OF MARKDOWN
          • 344
            Easy formatting
          • 245
            Widely adopted
          • 194
            Intuitive
          • 136
            Github integration
          • 40
            Great for note taking
          • 2
            Defacto GitHub lingo
          CONS OF MARKDOWN
          • 1
            Inconsistend flavours eg github, reddit, mmd etc
          • 1
            Limited syntax
          • 1
            Not suitable for longer documents
          • 1
            Non-extensible
          • 1
            No right indentation
          • 1
            No underline
          • 1
            Cannot centralise (HTML code needed)
          • 1
            Unable to indent tables

          related Markdown posts

          Johnny Bell

          For Stack Decisions I needed to add Markdown in the decision composer to give our users access to some general styling when writing their decisions. We used React & GraphQL on the #Frontend and Ruby & GraphQL on the backend.

          Instead of using Showdown or another tool, We decided to parse the Markdown on the backend so we had more control over what we wanted to render in Markdown because we didn't want to enable all Markdown options, we also wanted to limit any malicious code or images to be embedded into the decisions and Markdown was a fairly large to import into our component so it was going to add a lot of kilobytes that we didn't need.

          We also needed to style how the markdown looked, we are currently using Glamorous so I used that but we are planning to update this to Emotion at some stage as it has a fairly easy upgrade path rather than switching over to styled-components or one of the other cssInJs alternatives.

          Also we used React-Mentions for tagging tools and topics in the decisions. Typing @ will let you tag a tool, and typing # will allow you to tag a topic.

          The Markdown options that we chose to support are tags: a, code, u, b, em, pre, ul, ol, li.

          If there are anymore tags you'd love to see added in the composer leave me a comment below and we will look into adding them.

          #StackDecisionsLaunch

          See more

          More than year ago I was looking for the best editor of Angular 2 application and I've tried Visual Studio Code and Atom. Atom had performance issues that put me off completely to use it again. Visual Studio Code became my main editor #Typescript files (and partly editor of #Java files). I'm happy with Visual Studio Code and I've never look back on Atom. There wasn't any reason to try Atom again, because Visual Studio Code fulfills my requirements very well. I use it for editing of TypeScript, #HTML, #Sass, JSON, Docker and Markdown.

          See more
          Obsidian logo

          Obsidian

          117
          100
          0
          A second brain, for you, forever
          117
          100
          + 1
          0
          PROS OF OBSIDIAN
            Be the first to leave a pro
            CONS OF OBSIDIAN
              Be the first to leave a con

              related Obsidian posts