-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Reorganize Guides in a more logical order #8262
Conversation
🪼 branch checks and previews
Install Gradio from this PR pip install https://gradio-builds.s3.amazonaws.com/9902084af09803564bfab74c98154460314aa7f9/gradio-4.31.0-py3-none-any.whl Install Gradio Python Client from this PR pip install "gradio-client @ git+https://github.com/gradio-app/gradio@9902084af09803564bfab74c98154460314aa7f9#subdirectory=client/python" |
🦄 change detectedThis Pull Request includes changes to the following packages.
With the following changelog entry.
Maintainers or the PR author can modify the PR title to modify this entry.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! I agree this is much better.
Can you add redirect routes for old links? Not a big deal but can be helpful https://github.com/gradio-app/gradio/blob/main/js/_website/src/routes/redirects.js
Is it needed, I thought moving the guides to different sections does not affect the url, e.g. https://www.gradio.app/guides/the-interface-class |
yeah you're right, i meant for the ones you removed, which i guess is just key-features |
right, will add |
Thanks @aliabd for the review! |
The ordering of the Guides currently doesn't make sense, as we introduce
gr.Interface
in the Quickstart, then cover all sorts of key features that are quite advanced, and then lots of details related to sharing, before jumping back togr.Interface
.Now, I think the ordering makes more sense. These are the new sections
I've also fixed some typos, etc. I want to rework the guides some more but I didn't want to mix refactoring & other changes in a single PR.