v3 Feature Parity Checklist #6844
Comments
|
Hey @NGPixel this is great! I'm not sure how many active devs are in the community but could we use this to divide up some of the work with volunteers so get v3 over the line? I'll also note this list above seems not to include all selectively deprecated features, like 3rd party search engines. |
|
Thanks for the detailed list of features and progress of each. How long will it take you to go Live with V3? What's the roadmap (with phases)? |
|
What would help get the multi-site version out of beta? |
|
@NGPixel we've deployed the latest alpha as a container (from ghcr.io/requarks/wiki:3.0.0-alpha.334) and I was wondering if that's the same as the beta you're talking here right now? |
|
@nwcm 3rd party search engines are listed as deprecated under the "Modules" section. @simedia-ivansieder There's no beta release yet but yes the alpha.334 is currently the latest build that corresponds to this list. It will transition into beta releases once remaining permission issues are fixed. |
|
looking forward to this new release |
1 similar comment
|
looking forward to this new release |
Thanks for all the amazing work you've put into this project Nick. We are very much looking forward to the beta; in particular our most desired feature is the multisite capability. - if it were available today, we'd already be using it! Adding you as a sponsor as well - WikiJS has become such a core part of our business operations. Best Wiki project out there! |
|
Hi, what's default password? I running wiki:3.0.0-alpha.344 from docker image, the Use PgSQL, I find admin account is [email protected], password is hash string.... |
Ops, is my mistake! sorry. I find the Vega branch and find default password (https://github.com/requarks/wiki/tree/vega). |
How stable is this Version? And what about SSO? |
the version is very "Instability"! I can't save my article..... so I back to 2.x version. |
|
Is this still being worked on? Man I think Wikijs is awesome and I would hate for it to turn into a quill situation where it takes 8 years to get the next major version but then the community has mostly abandoned it by then. Is there anything we can do to help? I feel like PRs have gone mostly uncommented on or touched and it's extremely discouraging to see that or want to contribute in those cases |
|
@CollinHerber Seeing pull requests go uncommented and untouched is extremely discouraging, especially for those of us who want to contribute and help move things forward. It's difficult to stay motivated when it seems like there's no progress or communication. Is there anything we, as a community, can do to help? We’re passionate about Wiki.js and want to see it succeed. Perhaps more transparency about the roadmap and regular updates, even if they are small, could help maintain our enthusiasm and commitment. |
Yes - stop being so entitled, and consider becoming a sponsor. @NGPixel has put an unbelievable amount of work into this while balancing that with being a human being. There's an active Discord where people's support questions are answered usually same day, for an amazing software that provided for free. There's also new releases happening on schedule - 3.0 is a massive overhaul and 2.0 is still being updated. If you followed the timeline at all, you will see a lot of progress has been made, and the progress on 2.0 vs 3.0 are not mutually exclusive. |
I think there might be a misunderstanding. My comments are not coming from a place of entitlement but from a genuine desire to see Wiki.js thrive. I fully acknowledge the immense effort @NGPixel and the team have put into this project, and I am grateful for the incredible software that Wiki.js is. My concern stems from a place of passion and a desire to contribute meaningfully to a project I believe in. I understand that development takes time and that balancing this with personal commitments is challenging. My suggestion for more transparency and regular updates is meant to foster a stronger community connection and help maintain momentum. It’s not about demanding more, but about finding ways we can support the project and its developers better. |
My Concerns About @NGPixel and Support for Version 3 of the ProjectFirst, I want to clarify that my previous posts, in which I expressed concern for @NGPixel, may have been misunderstood. My concern is genuine and relates to his work-life balance and his overall workload. I am truly concerned about his well-being. I work on social projects myself and know how hard this work can be. I often spend more than 18 hours helping or working. Since I work without financial compensation, I can't donate money, but I support people in other ways, where I excel. We are building an alternative infrastructure that facilitates mutual aid – free of charge or at cost price. If I had more IT specialists available, I would gladly send them to you, although this is not possible at the moment. But this will hopefully change soon. It is a fact that many people are currently struggling, especially after these difficult times. Therefore, we should be particularly mindful of each other. My mistake is not being active on Discord, only on GitHub. However, if @NGPixel is doing well, that makes me very happy. I hope that he can continue his work and also enjoy the fruits of his labor. Meanwhile, I have a question: how many people are working on the project (V3) and how is the work distributed? Is he the only one working on it? It would be inhumane to manage this alone. What do you specifically need, aside from financial support? What kind of hands-on help can be provided? I find it impressive what you are accomplishing, and I hope we will see further progress soon. I am closely following the Vega branch. All the best and much strength for the coming times! |
|
No this project isn't dead, I just didn't have time to work on it in the past months. I hope to put some time on it in the coming weeks. @Lord-KalEl Yes I'm the only one working on it. It's easy to say "get some other devs to help" but the reality is that you need quite capable devs, that have a solid understanding of the project, to be able to help in any meaningful way. And as I'm sure you're aware, adding more people to a project takes even more of your time because you now need to review their code and guide them on how you want things. Add the fact that I'm quite opiniated when it comes to how a feature should work and look. And before someone ask, no I don't have an ETA so don't ask for one. |
I have been silently following Wiki.js and using it in some of my projects. I heard about v3 a long time ago and have been keeping an eye on the blog. Today, I saw this issue and then noticed your comment. Dude @joeldeteves , come on, do you really need to be so aggressive? Where did you see anyone trying to be entitled? Everybody just wants provide help and wants to see this amazing project go thriving. Saying things like "if you followed the timeline at all,", dude, this is GitHub, you have to allow that people might not know there's an Wiki.js Discord community, right? Responding in such a tone makes you seem smart? The funniest part: I did not find your name or your company to be displayed on any backer's page or previous backer's page, anyway, as long as you feel proud about what you did and what you said. To help others who don't know about the Discord community, here is the link I just found: |
|
@MFYDev Funny you should mention entitlement when I am the one putting my money where my mouth is and sponsoring this project. WikiJS is free as in beer. If you don't like the development schedule, or the direction the project is taking; you are free to fork it. Besides - I am not affiliated with the project or @NGPixel. I am just someone who understands what free means, and how much work goes into a project like this. You whining in a GitHub thread isn't going to change that. |
|
Could we, please, move on, before it will all escalate to "Yo momma" level? sigh |
This table tracks the current feature parity state between v2 and v3. The plan is to stay in beta until all v2 features have been implemented in v3. If you rely on features that are not yet implemented in v3, it's recommended to stay on v2 for now.
Note: this table doesn't list any new feature exclusive to v3, such as multi-sites.
Note: The state
Not Implementedmay refer to v2 code that has not been adapted yet or not connected yet. Most features are re-using code from v2 when possible.Administration
Site
Groups
Users
Modules
System
/_graphqlAssets
Authentication
Editors
Navigation
Pages
Search
Users
The text was updated successfully, but these errors were encountered: