Repository navigation
fix: clarify device compatibility and match the docs theme - #750
Merged
Merged
Conversation
This branch was successfully deployed
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The supported-device embed mixes dark rows with a white document canvas and low-contrast logos. Device rows are also hard to scan: identifiers crowd the name, feature badges jump to a separate column, and generic compatibility prose repeats the same accessory requirements.
Match the hosted document’s color scheme to the docs theme and use a white tile for manufacturer logos, since monochrome catalog assets are not necessarily dark-mode variants. Present device name/type, a consistent feature list with support icons, and grouped requirement notes with bridge/keypad icons and affected features. Move all model identifiers/provider information into keyboard-accessible Model details while keeping it searchable. Suppress known boilerplate while preserving specific constraints and conditional/beta support. Remove the duplicate catalog footer inside iframes; standalone visits retain it and docs retain their existing fallback link.
Validation:
Fixes DEVDB-464.