I’m looking for a wiki solution (either remotely hosted or self-hosted is fine) that takes Markdown input.

Thanks.

  • naeap@sopuli.xyz
    1·
    1 year ago

    I’m currently hosting a wiki.js
    you can either use markdown or a visual editor

    • kentucky444@eslemmy.es
      1·
      1 year ago

      My only gripe with wiki.js was the use of SQL for local storage. My wiki must be future proof and locking myself in an obscure SQL database was the deal breaker. I know that you can sync with a Git repo, but it felt like an overkill.

    • kentucky444@eslemmy.esEnglish
      1·
      1 year ago

      +1 Dokuwiki. It is a little complicated than most to configure the first time, but once you have everything running, it will work without complaints. Also, the whole wiki is stored as plain text files, which is awesome for backups.

      • xohshoo@lemmy.worldEnglish
        1·
        1 year ago

        piling on for Dokuwiki. Have been running it personally and for an org (2 different wikis) for like 7 or 8 years. No problems, and it’s own syntax is pretty easy too. I’ve migrated a few times too and love that it’s just plain text files

    • Dialectic Cake@lemmy.world
      0·
      1 year ago

      I switched from Tiddlywiki to Logseq 3-4 months ago and LOVE Logseq.

      Part of the reason I didn’t like Tiddlywiki was it kept everything in a single html file (including embedded images – eww) which made it annoying to move information around. (Note there is an option to run your own server which gives you extra flexibility, but I wasn’t interested in doing that.)

      With Logseq, it’s separate markdown file per journal entry / wiki page. I like the addons that are available as well as the queries, e.g., {{query (todo doing)}} displays my do now tasks on my journal page.

      Here’s a Beginner’s Guide on how to use LogSeq: YouTube video by Keep Productive