Skip to content

Change references to Hass.io to Home Assistant #12014

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

Closed
wants to merge 1 commit into from

Conversation

brianhanifin
Copy link
Contributor

Proposed change

I made a pass at rewording the Hass.io installation page to use the new branding of Home Assistant instead of Hass.io. I even included a brief explanation at the top of the page introducing the branding change, which includes a link to the blog post explaining the change.

I suspect you may not want to make the naming changes one page at a time. I'm wondering if a separate branch of the site needs to be worked on so the changes can be made all at once (including reorganizing the paths to exclude references to hassio)?

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:
  • This PR fixes or closes issue:

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.

I made a pass at rewording the Hass.io installation page to use the new branding of Home Assistant instead of Hass.io. I even included a brief explanation at the top of the page introducing the branding change, which includes a link to the blog post explaining the change.

I suspect you may not want to make the naming changes one page at a time. I'm wondering if a separate branch of the site needs to be worked on so the changes can be made all at once (including reorganizing the paths to exclude references to hassio).
@probot-home-assistant probot-home-assistant bot added the current This PR goes into the current branch label Feb 8, 2020
@frenck
Copy link
Member

frenck commented Feb 10, 2020

Duplicate of #11986

@frenck frenck marked this as a duplicate of #11986 Feb 10, 2020
@frenck frenck closed this Feb 10, 2020
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