-
Notifications
You must be signed in to change notification settings - Fork 835
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RFC Modernize repository #1316
Comments
I'm willing to try to convert some components to hooks, for instance I can make a PR to the modernize branch, sounds good ? |
Yep, that sounds good. We may need to rebase it after #1317 . @Xiot would that be easier or should we start with the yarn workspaces branch? |
Probably start with the yarn workspace branch. I can merge that into modernize once I clean it up. |
Hey all, I would recommend starting with yarn workspace then we can dig into the rest. I’ll gladly implement hooks as needed 👍 I have experience with workspaces if that’s something you want me to look at or help out with. |
@reiff12 We've already started on moving over to yarn workspaces #1317 |
At this point, the docs generation is the main challenge before we can merge the workspaces PR. Though I think it's ok to merge it before we have it fully worked out, since the website build has been broken for a while now. @ibgreen : what doc practices are you all following for your projects? Is there a repo that shows your latest docs practices? Perhaps we could leverage them here and it might be less work to migrate to that compared to rethinking how to generate docs here. Separately, for folks interested in looking at the hooks conversion: how about putting up some RFCs/proposals on approaches for discussion via #1320? |
~/*
)From offline sync with @Xiot
The text was updated successfully, but these errors were encountered: