Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Wiki.js

wiki.js.org

Post reply on HN
Print view View original

51–60 of 213 posts

Re: Wiki.js

#51

Post by wukerplank »

hombre_fatal wrote: post #40

Slightly related PSA: Everyone should consider running a wiki locally just for yourself. It's like being able to organize your brain. I just got into it two days ago and basically spent the whole weekend dumping things into it in a way I can actually browse and revisit, like the short stories I'd written, spread out across Notes.app and random folders. You don't need to run WAMP, MySQL, Apache, phpmyadmin or anything…

I started writing a master thesis in a MediaWiki a long time ago. Did not work for me, maybe lack of keeping a proper index. It was a data graveyard. On the other hand, so is my whole home folder...

Re: Wiki.js

#52

Post by Dennip »

Keyframe wrote: post #21

I need one function in a wiki platform that I haven't seen so far. When I write text, in its WYSIWYG editor, I need an ability to paste in an image (a screenshot that I just grabbed, let's say) and for it to automatically upload it and embed it into text. Does this support something like that?

Confluence supports this, although its not free!

Re: Wiki.js

#53

Post by drcongo »

Mandatum wrote: post #47
hombre_fatal wrote: post #40

Slightly related PSA: Everyone should consider running a wiki locally just for yourself. It's like being able to organize your brain. I just got into it two days ago and basically spent the whole weekend dumping things into it in a way I can actually browse and revisit, like the short stories I'd written, spread out across Notes.app and random folders. You don't need to run WAMP, MySQL, Apache, phpmyadmin or anything…

I've been using Obsidian for note taking recently, and as much as I really enjoy it - having hypermedia would be quite useful too. I can paste images in Obsidian, but it tends to put the pasted image in the root folder, and I can't display it inline with my notes. EDIT: VisualEditor, the de facto standard for pasting things like screenshots into your articles seems to be a pain to install. Got my local env up and run…

I may have misunderstood, but I'm using images in Obsidian without any trouble. Create a folder inside Obsidian, right click it, choose "Use as attachment folder" and then drag and drop / paste images into your documents however you like. It saves to this folder and automatically generates the markup when you put an image in.

Re: Wiki.js

#54

Post by tweetle_beetle »

I'm looking to launch an internal wiki and Wiki.js came out on top for my requirements:

- easy to use for technical and non-technical staff alike: multiple editing options

- third party authentication: really comprehensive offering

- quality search: comprehensive internal and third party search offering

- ease of maintenance: largely everything is built-in, so no module/dependency maintenance headaches

- user management: solid user/group management system

With internal tools you need things to stick, and fast. As much as I am fond of mediawiki, the editing experience is a barrier to usage for many. And the extension ecosystem, while rich and diverse, is just more of a liability than a single installation. A quality search is also really important to adoption, so having options there is great.

I'd been using Docsify on a small scale with authentication through GitLab to edit, GitLab CD to build and Cloudflare Access to secure the front end. It works really well, but the lack of user management and the editing experience mean that it's time to move on.

It would be great to hear if this is a case of the grass always being greener on the other side.

Re: Wiki.js

#55

Post by load »

eitland wrote: post #14
load wrote: post #8

Earlier quoted context omitted.

I mean, I appreciate the effort put into building this, but external tools like AWB, and userscripts/gadgets (plus a host of other goodies) can't be accessed over globally if it's on a completely different software. Almost every wiki on the net uses MediaWiki for good reason. I will be happy if this Wiki.js platform does have compatibility with these features, though.

> Almost every wiki on the net uses MediaWiki for good reason. It is unclear to ne if you refer to statistics or gut feeling here. Would you mind clarifying?

By 'MediaWiki' I'm referring to the wikis and wiki farms that use MediaWiki or a variant of it. This includes:

- Wikimedia

- FANDOM

- Gamepedia

- Miraheze

FANDOM is the most massive wiki farm with over 360,000+ (as of 2016) wikis[1], which I'd give at lowest an estimate of 60% of the total number of wikis on the net, and is 88th on the Alexa rankings.[2] FANDOM is a wiki powerhouse, and you bet it uses MediaWiki.

Excluding WikiHow, I have never seen a wiki not use MediaWiki. As one of the guys that hops across many different wikis and wiki farms doing automated work, I cannot stress this enough.

[1] Brandon Rhea, FANDOM VP of Growth https://community.fandom.com/wiki/Choosing_Fandom?diff=next&... (dated June 14, 2016)

[2] Alexa.com https://www.alexa.com/siteinfo/fandom.com#section_traffic (dated ~21 July 2020)

Re: Wiki.js

#56

Post by Aengeuad »

Hamcha wrote: post #11

docs.requarks.io, which is said to be using Wiki.js, straight up doesn't load without Javascript, and even with Javascript enabled it's a multi-page application that just feels slower browsing page to page than your average 10-year-old mediawiki install (probably also heavier on the backend). Who exactly is asking for slower software?

I was excited for a moment when wiki.js.org rendered properly without Javascript but similarly disappointed when docs.requarks.io only showed a fairly typical white page.

Also noticed that it feels slow page to page, thinking that it might be an issue with my Firefox configuration I opened the page on a fresh profile and it's still slow, but if you open it in Chrome page to page becomes almost instant and is more comparable to MediaWiki. So maybe this particular performance issue on FF can be resolved but it does seem like a worse end user experience when compared to MediaWiki.

Re: Wiki.js

#57

Post by Vaslo »

amq wrote: post #42

I was looking into open source knowledge / wiki base solutions recently, and I found https://www.getoutline.com/ to be the most usable.

10 bucks a month though...

Re: Wiki.js

#58

Post by Normal_gaussian »

hombre_fatal wrote: post #40

Slightly related PSA: Everyone should consider running a wiki locally just for yourself. It's like being able to organize your brain. I just got into it two days ago and basically spent the whole weekend dumping things into it in a way I can actually browse and revisit, like the short stories I'd written, spread out across Notes.app and random folders. You don't need to run WAMP, MySQL, Apache, phpmyadmin or anything…

> I just got into it two days ago

This is the rub. I started a tiddlywiki last year, and stuck with it for several months, but now it has fallen to the wayside as too cumbersome.

Re: Wiki.js

#59

Post by ta20200710 »

schoolornot wrote: post #17

This is exciting. A compelling FOSS alternative to Atlassian Confluence was sorely needed. Mediawiki has some UX and RBAC challenges that makes it difficult to scale to large organizations.

> large organizations

Interestingly Amazon just finished a multi-year effort to migrate off MediaWiki internally to comply with an infosec mandate that PHP is banned company wide.

Re: Wiki.js

#60

Post by andrewshadura »

oneplane wrote: post #27

I wonder why it's AGPL and not dual-licensed or some different GPL. As it is right now it's dead in the water for any commercial usage unless you're manually installing the thing on a manually installed server somewhere (which you probably aren't). With automation you'd build images based on their images but run via your own CI/CD with your own security scans and any additions you might need (like additional logging…

> With automation you'd build images based on their images but run via your own CI/CD with your own security scans and any additions you might need (like additional logging infrastructure). Doing that is not possible with AGPL.

None of that is impossible with AGPL.

Post reply on HN