You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When migrating to a new system, a VM, I had to re-install HACS, and I was left extremely confused by the new method of enabling themes. The current method of just showing it based on if Home Assistant is configured to be able to see the themes isn't very intuitive for new users.
Describe the solution you'd like
Put tab visibility in the settings of HACS, allow enabling and disabling of the Themes/Python Scripts/etc tabs be just a setting that you can flip on and off. Maybe make the default settings of the visibility based on the current system, and if the user enables anything they don't have properly configured like enabling the themes tab without adding "!include_dir_merge_named theme" to your configuration.yaml it has a giant red card at the top of the themes tab telling the user that it's not properly configured, and prompting the user to visit the proper page in the documentation to configure it properly.
Describe alternatives you've considered
Maybe instead, or really in addition to, just rework the documentation flow to be more of a step by step format? Following the hacs.xyz page isn't super easy to follow. Starting at installation and clicking "next" like what is intuitive doesn't take you to the next step most of the time. The page structure goes directly from installing to removing when following the "next" button like one would expect to do, and if you don't know what links to click through, you won't ever see the /themes page where it tells the user how to enable the themes tabs. When following instructions, and it's not super clear to a new user the actual process to follow.
Additional context
I would be willing to help work on the documentation front, and plan on making some PRs next time I have some free time, probably in late February early march.
The text was updated successfully, but these errors were encountered:
Make sure you have read the issue guidelines and that you filled out the entire template.
fortepc
changed the title
Allow enabling and disabling of any HACs category in the settings.
Feature Suggestion: Allow enabling and disabling of any HACs category in the settings.
Feb 6, 2020
Is your feature request related to a problem? Please describe.
When migrating to a new system, a VM, I had to re-install HACS, and I was left extremely confused by the new method of enabling themes. The current method of just showing it based on if Home Assistant is configured to be able to see the themes isn't very intuitive for new users.
Describe the solution you'd like
Put tab visibility in the settings of HACS, allow enabling and disabling of the Themes/Python Scripts/etc tabs be just a setting that you can flip on and off. Maybe make the default settings of the visibility based on the current system, and if the user enables anything they don't have properly configured like enabling the themes tab without adding "!include_dir_merge_named theme" to your configuration.yaml it has a giant red card at the top of the themes tab telling the user that it's not properly configured, and prompting the user to visit the proper page in the documentation to configure it properly.
Describe alternatives you've considered
Maybe instead, or really in addition to, just rework the documentation flow to be more of a step by step format? Following the hacs.xyz page isn't super easy to follow. Starting at installation and clicking "next" like what is intuitive doesn't take you to the next step most of the time. The page structure goes directly from installing to removing when following the "next" button like one would expect to do, and if you don't know what links to click through, you won't ever see the /themes page where it tells the user how to enable the themes tabs. When following instructions, and it's not super clear to a new user the actual process to follow.
Additional context
I would be willing to help work on the documentation front, and plan on making some PRs next time I have some free time, probably in late February early march.
The text was updated successfully, but these errors were encountered: