-
-
Notifications
You must be signed in to change notification settings - Fork 508
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
Streamlit migration Guide #5027
Conversation
I see this PR surving multiple purposes. The primary purpose is to provide
But it also indirectly provides
If someone thinks a "migration guide" would be seen as "agressive" (?) we could re-purpose the guide and focus on one or more of the indirect uses. If all together we don't think this fits into our documentation I could publish this as a personal blog post. Personally I see a guide for users that comes with a Streamlit background as a helpful, natural thing to add and not aggressive at all. Streamlit is a benchmark and many users will better understand things in that context. As context I would also plan to contribute a similar guide for Gradio one day as I and Panel could learn a lot from that one as well. And it would help users that have learned the Gradio way of building data apps to use our framework. Please let me know (@maximlt , @philippjfr, @droumis ) if you think this guide should be repurposed or published as a personal blog post. Thanks. |
Personally I have no concerns here, we're not claiming Streamlit sucks we are just making it easier for existing users to translate concepts they already know if they find streamlit limiting. |
Same, migration guides are going to be very helpful to users coming from other libraries. |
Codecov Report
@@ Coverage Diff @@
## main #5027 +/- ##
===========================================
+ Coverage 72.62% 83.82% +11.19%
===========================================
Files 274 274
Lines 39583 39584 +1
===========================================
+ Hits 28749 33181 +4432
+ Misses 10834 6403 -4431
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 71 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
AssetsHello WorldOutputsInputsLayouts(Note: I could not find TemplatesInteractivity Basic ExampleShow ActivityInteractivity Multiple Updates ExampleInteractivity Multiple Outputs ExampleSession CacheSession State |
If this is to stay in the how_to guide then we need to break this up into individual sections. |
Do you mean the guide is too big and does not fit the concept of a how-to guide? |
Yep, but I think it could very cleanly be split up into a whole how-to section with various sub-guides. What do you think? |
It can probably be done but
|
Just a thought; the benefit of it being on one page is the ability to |
It'd be organized just like the other how-to guides, each card on https://panel.holoviz.org/how_to/index.html corresponds to a how-to section with multiple smaller guides. |
So at https://panel.holoviz.org/how_to/index.html there would be a section called Migration Guides One card would be Streamlit. Another Gradio. If you click Streamlit you would navigate to another page with several cards each representing a section in the Streamlit Migration guide? |
Exactly right. |
I'll start working on this. |
Really appreciate this, this is looking really great! |
Migration to standalone guides is done. I've done a first review. Probably needs one or more reviews to make sure everything makes sense as individual guides and together. I will try to do it before I leave for holiday later today. Otherwise feel free to do it and finalize 😄 |
Is it possible to get this one deployed to the |
You can always do this yourself: |
I just triggered it. After that I discovered you also triggered a docs build an hour ago @philippjfr . But the dev site seems not to be up? |
Yeah something seems to have gone wrong when migrating from pyviz-dev to holoviz-dev |
I'm merging and fixing followup issues in separate PRs. Thank you so much @MarcSkovMadsen and thanks for your review/contributions @ahuang11! |
And thanks for generator functions and more. Our Api just got much better. |
Closes #5016
You can preview the guides here
I really hope that this will help our users migrate. And that it will inspire us to improve our framework like in #5019.
Todo
Maybe one day in another PR
Describe migrating