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

Connect ZBT1: Remove unavailability note #35911

Draft
wants to merge 1 commit into
base: current
Choose a base branch
from

Conversation

c0ffeeca7
Copy link
Contributor

@c0ffeeca7 c0ffeeca7 commented Nov 22, 2024

Proposed change

Type of change

  • Spelling, grammar or other readability improvements (current branch).
  • Adjusted missing or incorrect information in the current documentation (current branch).
  • Added documentation for a new integration I'm adding to Home Assistant (next branch).
  • Added documentation for a new feature I'm adding to Home Assistant (next branch).
  • Removed stale or deprecated documentation.

Additional information

  • Link to parent pull request in the codebase:
  • Link to parent pull request in the Brands repository:
  • This PR fixes or closes issue: fixes #

Checklist

  • This PR uses the correct branch, based on one of the following:
    • I made a change to the existing documentation and used the current branch.
    • I made a change that is related to an upcoming version of Home Assistant and used the next branch.
  • The documentation follows the Home Assistant documentation standards.

Summary by CodeRabbit

  • New Features

    • Updated the landing page to reflect the rebranding from "Home Assistant SkyConnect" to "Home Assistant Connect ZBT-1."
    • Expanded FAQs with detailed information on product features, usage, and support.
  • Bug Fixes

    • Removed "Temporarily unavailable" message from the banner, indicating product availability.
  • Documentation

    • Enhanced user guidance regarding the transition and support for the Connect ZBT-1.

@home-assistant home-assistant bot added the current This PR goes into the current branch label Nov 22, 2024
Copy link

netlify bot commented Nov 22, 2024

Deploy Preview for home-assistant-docs ready!

Name Link
🔨 Latest commit d503867
🔍 Latest deploy log https://app.netlify.com/sites/home-assistant-docs/deploys/6740ba4dd770d700081b5622
😎 Deploy Preview https://deploy-preview-35911--home-assistant-docs.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.

@c0ffeeca7 c0ffeeca7 marked this pull request as draft November 22, 2024 17:08
Copy link
Contributor

coderabbitai bot commented Nov 22, 2024

📝 Walkthrough

Walkthrough

The changes in the pull request primarily involve updates to the index.html file for the Home Assistant Connect ZBT-1 landing page. Key modifications include the removal of the "Temporarily unavailable" message, a rebranding from "Home Assistant SkyConnect" to "Home Assistant Connect ZBT-1," and an expanded FAQs section that provides detailed information about the transition, product usage, multiprotocol support, and a replacement program. Additionally, a script was added to display a rebranding banner based on the URL hash, while maintaining the existing styling of the page.

Changes

File Path Change Summary
source/connectzbt1/index.html - Removed "Temporarily unavailable" from the banner overlay header.
- Updated product name to "Home Assistant Connect ZBT-1."
- Expanded FAQs section with detailed explanations on branding transition, USB extension cable inclusion, recommended use cases, multiprotocol support, and a replacement program for faulty devices.
- Added script logic to display a rebranding banner based on URL hash.
- Retained existing styling for visual consistency.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Webpage
    participant FAQSection

    User->>Webpage: Access landing page
    Webpage-->>User: Display updated product name
    Webpage-->>User: Show rebranding banner if URL hash present
    User->>FAQSection: View FAQs
    FAQSection-->>User: Provide detailed information on product and support
Loading

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between ba5a066 and d503867.

📒 Files selected for processing (1)
  • source/connectzbt1/index.html (0 hunks)
💤 Files with no reviewable changes (1)
  • source/connectzbt1/index.html

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 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 or @coderabbitai title 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
current This PR goes into the current branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants