Skip to content

Conversation

@mcanouil
Copy link
Contributor

@mcanouil mcanouil commented Oct 25, 2024

This is a small addition to clearly state that Quarto Pub only support static content thus no shiny document which requires a server to run the app.

Should it be a callout note, as for the size limit of 100 Mb?

@mcanouil mcanouil changed the title docs: mention it's only for static content docs: Quarto Pub is only for static content Oct 25, 2024
@cscheid
Copy link
Collaborator

cscheid commented Oct 25, 2024

Should it be a callout note, as for the size limit of 100 Mb?

No. That's a soft limit that we purposefully do not officially promise.

@mcanouil
Copy link
Contributor Author

Sorry, I was not clear.
I meant the fact that Quarto Pub is for static content, should it be a call-out to be more visible?

In text is the minimum as right now it is not stated at all.

@cscheid
Copy link
Collaborator

cscheid commented Oct 28, 2024

We should improve the situation, but I'm not sure that adding "static" will reduce the confusion for people who don't already understand how Shiny and interactive=True Python widgets work. I think we need a bit more.

@mcanouil
Copy link
Contributor Author

mcanouil commented Oct 29, 2024

I agree, but right now there is nothing stating what Quarto Pub is and supports.
So, users are not confused, they simply have no way to know it won't work.

@cscheid cscheid merged commit efc105a into quarto-dev:main Mar 14, 2025
3 checks passed
@github-actions
Copy link
Contributor

Successfully created backport PR for prerelease:

github-actions bot pushed a commit that referenced this pull request Mar 14, 2025
cscheid pushed a commit that referenced this pull request Mar 14, 2025
(cherry picked from commit efc105a)

Co-authored-by: Mickaël Canouil <[email protected]>
@mcanouil mcanouil deleted the patch-1 branch March 14, 2025 13:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants