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

Add HA like version label to sidebar #4503

Draft
wants to merge 11 commits into
base: current
Choose a base branch
from
Draft

Conversation

shvmm
Copy link
Contributor

@shvmm shvmm commented Dec 12, 2024

Description:

Added HA like version label to esphome doc sidebar

Related issue (if applicable): fixes NONE

Pull request in esphome with YAML changes (if applicable): esphome/esphome# NONE

Checklist:

  • I am merging into next because this is new documentation that has a matching pull-request in esphome as linked above.
    or

  • I am merging into current because this is a fix, change and/or adjustment in the current documentation and is not for a new component or feature.

  • Link added in /index.rst when creating new documents for new components or cookbook.

Copy link

netlify bot commented Dec 12, 2024

Deploy Preview for esphome ready!

Name Link
🔨 Latest commit c59b8df
🔍 Latest deploy log https://app.netlify.com/sites/esphome/deploys/6762890d7cf7b90008225916
😎 Deploy Preview https://deploy-preview-4503--esphome.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@shvmm shvmm marked this pull request as ready for review December 12, 2024 18:06
Copy link
Contributor

coderabbitai bot commented Dec 12, 2024

Walkthrough

This pull request introduces several updates across multiple files, primarily focusing on enhancing the styling and layout through CSS modifications. A new class .release-date is added, and existing styles are updated to improve readability and responsiveness. The HTML files are modified to reflect changes in link text and to include a new version display. Additionally, the Sphinx configuration is updated to incorporate a version-specific sidebar template.

Changes

File Change Summary
_static/custom.css Added .release-date class; updated styles for headings and body text; enhanced dark theme styles; modified media queries for responsiveness.
_templates/contact.html Updated link text from "Join the community" to "Join our Discord".
_templates/version.html Added a new <div> with a link displaying the latest version number and release date.
conf.py Added "version.html" to the html_sidebars dictionary for sidebar templates.

Possibly related PRs

  • Tabs label CSS dark mode fix #4367: This PR modifies the same CSS file (_static/custom.css) and includes changes to classes and styles that are relevant to dark mode, which aligns with the enhancements made in the main PR regarding dark theme styles.

Suggested reviewers

  • kbx81
  • jesserockz

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bf3040a and e185f8a.

📒 Files selected for processing (2)
  • _static/custom.css (2 hunks)
  • _templates/version.html (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
  • _templates/version.html
  • _static/custom.css

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Experiment)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)
_static/custom.css (1)

289-296: Consider optimizing the CSS for better maintainability.

  1. The border-radius is inconsistent between themes (5px vs 4px)
  2. Common properties are duplicated between themes

Consider this optimization:

 .release-date {
     font-size: 12px;
     padding: 0 5px 0 5px;
     background: #e8edf0;
     height: fit-content;
     color: #007fa8;
     border-radius: 4px;
 }

 @media (prefers-color-scheme: dark) {
   .release-date {
-    font-size: 12px;
-    padding: 0 5px 0 5px;
-    height: fit-content;
     background: #393939;
     color: #3fc3ff;
-    border-radius: 4px;
   }
 }

Also applies to: 477-484

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f39ceef and 0a4e347.

📒 Files selected for processing (4)
  • _static/custom.css (2 hunks)
  • _templates/contact.html (1 hunks)
  • _templates/version.html (1 hunks)
  • conf.py (1 hunks)
✅ Files skipped from review due to trivial changes (2)
  • _templates/contact.html
  • _templates/version.html
🧰 Additional context used
📓 Path-based instructions (2)
conf.py (1)

Pattern **: - Do not generate or add any sequence diagrams

_static/custom.css (1)

Pattern **: - Do not generate or add any sequence diagrams

🔇 Additional comments (2)
conf.py (1)

167-167: LGTM! Addition of version template to sidebar configuration.

The placement of version.html in the sidebar configuration is appropriate, positioned before the search box and navigation elements.

_static/custom.css (1)

289-296: LGTM! Well-implemented version label styles with proper theme support.

The implementation provides good contrast ratios and consistent styling across both light and dark themes.

Also applies to: 477-484

@shvmm shvmm changed the title Add HA like version label to esphome main page Add HA like version label Dec 12, 2024
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)
_static/custom.css (1)

289-296: LGTM! Consider adding hover state for better UX.

The styling for the version label is well-implemented with appropriate colors, spacing, and visual treatment. The color contrast ratio is sufficient for accessibility.

Consider adding a hover state for better user experience:

 .release-date {
     font-size: 12px;
     padding: 0 5px 0 5px;
     background: #e8edf0;
     height: fit-content;
     color: #007fa8;
     border-radius: 5px;
+    transition: background-color 0.2s ease;
 }
+.release-date:hover {
+    background: #d8e0e4;
+}
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0a4e347 and 85dec07.

📒 Files selected for processing (1)
  • _static/custom.css (2 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
_static/custom.css (1)

Pattern **: - Do not generate or add any sequence diagrams

🔇 Additional comments (2)
_static/custom.css (2)

477-480: LGTM! Dark theme implementation is well-considered.

The dark theme colors maintain good contrast while staying consistent with the site's dark theme palette. The implementation correctly uses the prefers-color-scheme media query.


289-296: Verify consistency with Home Assistant's version label.

Let's ensure our implementation aligns with Home Assistant's version label styling.

Also applies to: 477-480

✅ Verification successful

Version label styling looks appropriate and includes dark mode support

The implementation includes all essential styling properties for the version label:

  • Light mode with subtle background (#e8edf0), blue accent color (#007fa8)
  • Dark mode adaptation with darker background (#393939) and lighter blue (#3fc3ff)
  • Proper spacing with padding and border-radius for a pill-like appearance
  • Appropriate font size and height settings

The styling achieves a clean, modern look that's consistent with modern documentation practices and includes proper dark mode support.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Compare our version label implementation with Home Assistant's
# Expected: Similar styling properties for version labels

# Check Home Assistant's CSS for version label styling
curl -s https://www.home-assistant.io/css/custom.css | rg -A 5 'version|release.*date'

# Check if we're missing any styling properties used by Home Assistant
curl -s https://www.home-assistant.io/css/custom.css | rg '@media.*dark' -A 10 | rg 'version|release.*date'

Length of output: 443


Script:

#!/bin/bash
# Let's try a different approach to find Home Assistant's styling
# First, let's check their repository directly for CSS files
fd -e css | xargs rg -l 'release-date|version'

# Then let's examine our implementation
cat _static/custom.css | rg -A 10 'release-date'

# Let's also check if there are any other similar styling classes in our codebase
fd -e css | xargs rg 'release-date|version' -A 5

Length of output: 1053

@shvmm shvmm changed the title Add HA like version label Add HA like version label to sidebar Dec 13, 2024
@jesserockz
Copy link
Member

Converting to draft pending design review/decision

@jesserockz jesserockz marked this pull request as draft December 13, 2024 09:48
shvmm added 11 commits December 18, 2024 14:04
Join our community is nondescript of containing a discord link.
fixed it to reflect that.
include release-date formatting for version text
switched from p to div
added dark mode css for release-date class
removed common properties from dark mode css
added !important to sort priority with div.sphinxsidebar
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants