This repository was archived by the owner on Jan 8, 2025. It is now read-only.
Remove the ScopedBlock from the docs engine#382
Merged
Conversation
Fixes #116 We added the `ScopedBlock` component to the docs engine in order to give docs readers only the information they needed for their Teleport edition, without providing distracting details about other Teleport editions. However, the vast majority of readers do not notice the scope switcher within the docs, meaning that any `ScopedBlock`s not assigned to the default scope (`oss`) go unseen. Removing the `ScopedBlock` will help us move toward a clearer information architecture that does not rely on scopes.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Contributor
Author
|
We need to get these backports merged before we can merge this: |
avatus
approved these changes
Aug 22, 2023
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #116
We added the
ScopedBlockcomponent to the docs engine in order to give docs readers only the information they needed for their Teleport edition, without providing distracting details about other Teleport editions.However, the vast majority of readers do not notice the scope switcher within the docs, meaning that any
ScopedBlocks not assigned to the default scope (oss) go unseen. Removing theScopedBlockwill help us move toward a clearer information architecture that does not rely on scopes.