-
-
Notifications
You must be signed in to change notification settings - Fork 8.6k
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
Proposal: add unlisted/draft banners in dev mode #8285
Comments
Thanks Docusaurus 3.0, now is easy to doing this by create a remark plugins: |
@dkoprowski If you expect a different behaviour indeed you should create a separate issue though i'm not sure if we'll modify this behavior directly unless there is a demand for that. Also it might be possible to achieve what you request by creating a remark plugin to remove the banner of unlisted content only during production build (i'm not sure about that) |
Yes it's expected to see the banner in production mode, this way you know that the page is unlisted and don't forget to remove the flag once ready. I'd like to keep it this way. But this can easily be changed by swizzling The banner is not in the Markdown so it can't be removed with a remark plugin. At best you can remove the unlisted front matter, but then your doc becomes listed (which removes the banner, but may not be what you want) |
Have you read the Contributing Guidelines on issues?
Motivation
#8004 brings support for
unlisted
to all 3 content plugins, including a banner to make it clear a content is unlisted:I think it could improve the DX to also display such a banner in dev for both
draft: true
andunlisted: true
Note in our current implementation, the doc
metadata.unlisted
is never true in dev mode so this metadata is not a good way to display the banner in dev. We could readfrontMatter.unlisted
directly instead.Self-service
The text was updated successfully, but these errors were encountered: