Skip to content
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

Define a strategy for using unlisted:true #2829

Open
akeller opened this issue Oct 31, 2023 · 1 comment
Open

Define a strategy for using unlisted:true #2829

akeller opened this issue Oct 31, 2023 · 1 comment
Labels
component:docs Documentation improvements, including new or updated content

Comments

@akeller
Copy link
Member

akeller commented Oct 31, 2023

In #8004, we introduced a new unlisted: true front matter option, which will keep your pages available in production builds, while "hiding" them and making them impossible to discover unless you have the url. This enables convenient workflows where you can easily ask for feedback on a piece of content before the final publication.

This is related to https://github.com/camunda/developer-experience/issues/66 but doesn't quite cover it. However, we could consider this a "quick win" since it would be visible after merging (to stage).

We should add a docs-on-docs page explaining how and why to use 'unlisted:true' and when pages appear on stage.docs.camunda.io.

Dependent on V3 (#2719).

@akeller akeller added the component:docs Documentation improvements, including new or updated content label Oct 31, 2023
@akeller akeller changed the title Define a strategy for using 'unlisted:true' Define a strategy for using unlisted:true Oct 31, 2023
@akeller akeller moved this from 🆕 Inbox to 🛑 Blocked in Developer Experience Oct 17, 2024
@akeller
Copy link
Member Author

akeller commented Oct 17, 2024

Blocked until #3736

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component:docs Documentation improvements, including new or updated content
Projects
Status: 🛑 Blocked
Development

No branches or pull requests

1 participant