Closed luxumbra closed 3 years ago
I'm interested in helping with this. Just worked through a Docusaurus v2 project in my Raid Guild cohort (we hosted our cohort site on IPFS with Docusaurus as well)
Sweet!
Have you done any work with NetlifyCMS @jonathanprozzi?
@luxumbra I have a long time ago! Would need to revisit it but happy to dig in a bit this weekend!
I have a Docusaurus v2 'playground' I set up for various testing purposes. Going to set up NetlifyCMS with MDX on it and will then report back with findings from doing this.
Amazing. Thanks for the update
@luxumbra -- Just for my testing purposes -- do we think we'd want to set up some form of GitHub auth? The other option for editors is to use Netlify Identity (email/password).
I think maybe eventually we'd want to try to use a web3 auth?
I'm going to test both Netlify Identity and GItHub auth for now and will keep reporting back!
Hey @jonathanprozzi Probably go with Github auth as many already have github accounts. Isn't netflify identity part of their paid service? Web3 auth would be pretty sweet. 👍🏻
@luxumbra Netlify Identity is free up to 1000 users! On my test ground I set it up so that people can create accounts for it via GitHub auth. I think Identity used to perhaps be paid? I never explored it before for that reason. We can likely set roles too.
We'd probably be able to keep under that limit since these users would be strictly for editing/updating the Wiki.
I definitely think Web3 auth would be great goal eventually!
Greetings Gentlemen! Where are we on this? What's the timeline for moving the wiki over to Docusaurus V2?
just checking this one out now! had some node issues on my end which has solved a few painpoints I had on both this and the app.
Running through the migration process right now hopefully can close this one out soon
getting some weird errors but going to try and migrate the site by hand by spinning up a v2 project and moving everything over and checking if that works
Ok so after some digging, looking at our version for the wiki "@docusaurus/core": "^2.0.0-alpha.64",
which isn't currently maintained; I think maybe it would make sense if we spun up a version for 2.0.0-beta.4 which is the current stable built for the wiki and just manually move things over perhaps?
I've never used docusaurus before myself but after checking online and asking some questions I think this seems like an approach that makes sense
if anyone has any other suggestions I'd love to hear! will keep digging and trying for a little bit tonight in the mean time :rocket:
I found this documentation on upgrading:
https://docusaurus.io/docs/installation#updating-your-docusaurus-version
Can we just do that instead of spinning up a new version and manually transferring things? The instructions seem super simple so I'll probably just try it and see if it works.
https://docusaurus.io/docs/installation#updating-your-docusaurus-version
Can we just do that instead of spinning up a new version and manually transferring things? The instructions seem super simple so I'll probably just try it and see if it works.
~The weird errors are what prevent us from following the super simple upgrade instructions - it has been tried before and breaks a number of things.~ I commented on #300, saying that maybe it is time to devote some energy into sorting the wiki out.
Edit: Interesting, I just tried an upgrade to beta6 and while there are errors in the console, it does run fine with no noticeable issues on the UI.
I tried some stuff with it a few months back and I think that was the best way at the time but I could be wrong. if I remember correctly there was some problems with upgrading the existing and migrating could in theory at least that I've found it could be an option to move forward
On Sat, Oct 16, 2021 at 5:18 PM Luxumbra @.***> wrote:
https://docusaurus.io/docs/installation#updating-your-docusaurus-version
Can we just do that instead of spinning up a new version and manually transferring things? The instructions seem super simple so I'll probably just try it and see if it works.
The weird errors are what prevent us from following the super simple upgrade instructions - it has been tried before and breaks a number of things. I commented on #300 https://github.com/MetaFam/metagame-wiki/pull/300, saying that maybe it is time to devote some energy into sorting the wiki out.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/MetaFam/metagame-wiki/issues/246#issuecomment-944945029, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEXDQ66XXEGIJHJURBIXJB3UHGQUDANCNFSM46Q7BWGA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
This was fixed with PR #309. We're now on the latest stable version, 2.0.0-beta.7!
For what it's worth we were already on version 2. Someone else fixed that awhile back.
There's a new version of Docusaurus out which should address some of our issues as mentioned in the wiki migration call 11 June.
See Docusaurus blog post