3 ms·
> I just believe that Docusaurus is more featured and flexible, that's all. That’s not the problem. This is the problem: > they have their little use-cases I
by JimDabell 4y ago
> I just believe that Docusaurus is more featured and flexible, that's all.
That’s not the problem. This is the problem:
> they have their little use-cases
If you look at what other people in this thread are doing when they are comparing other tools to yours favourably, they are talking about what Docusaurus does better.
When you reply to somebody comparing other tools to yours unfavourably, you jump to belittling the other tool.
It gives a really bad impression of Docusaurus that, when you think about it in relation to other tools, you aren’t thinking of what Docusaurus does well, but immediately try to belittle the alternative in some way. Docusaurus can’t be all that great if the best things you can think of are insults about some other tool.
The most convincing comments in favour of Docusaurus are coming from everybody but you. I don’t think that’s what you are trying to achieve with your comments here is it?
- slorber 4y agoI'm not belittling all other tools, just MdWiki (and Docsify that I consider in the same category of client-side JS, hash-based docs tool). All the other docs tools are great too, and I'm not saying Docusaurus is better. I believe Docusaurus can scale from small sites to very advanced doc sites with minimal effort. If I were a Python dev looking for something simple but that remains quite flexible, I'd definitively try MkDocs. If I were a Vue dev I'd try first VitePress/VuePress before Docusaurus. It has less features but a great UI design, some convenient Md features, and it's convenient for a Vue dev/team to reuse their existing VueJS knowledge. If I had a Next.js site and wanted to integrate docs feature in the same site, I would try Nextra. Really, apart my comment on MdWiki (which I still stand by: most of you shouldn't use it), I think I'm fair with all the other tools?