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

implement welcome and help screens for better onboarding #51

Merged
merged 2 commits into from
Jun 26, 2023

Conversation

casperstorm
Copy link
Member

@casperstorm casperstorm commented Jun 23, 2023

Added a help and welcome screen to Halloy.
This also simplifies our logic initially so we don't pass down a config error all the way to empty buffer.

The welcome screen will be displayed if there's no configuration file found, and then guide the user through a few steps to set it up. The help screen will displayed as soon as something is wrong with the configuration file, and tell what went wrong.
If all is okay, we show dashboard.

Screenshot 2023-06-26 at 13 02 19 Screenshot 2023-06-26 at 13 02 36

closes #53

@casperstorm casperstorm force-pushed the feat/welcome-and-help branch 2 times, most recently from 504175d to ac72fec Compare June 24, 2023 19:54
@casperstorm casperstorm marked this pull request as ready for review June 26, 2023 11:02
@casperstorm casperstorm requested a review from tarkah June 26, 2023 11:04
@casperstorm casperstorm changed the title initial work on help and welcome screens implement welcome and help screens for better onboarding Jun 26, 2023
Copy link
Member

@tarkah tarkah left a comment

Choose a reason for hiding this comment

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

Looks great, @casperstorm!! Found just a couple things.

I think it might be wise for us to "pre-populate" a default config.yml file into the config dir if none exists. So when use is on welcome screen and they open config dir, there is already a file there for them to edit. We can include_bytes the repo file and write it there when they click open directory maybe?

Or should we instead include a GH link to the file for them to open / reference? This way we don't auto-create any file which would cause the welcome screen to not load next time if they took no action.

src/screen/welcome.rs Outdated Show resolved Hide resolved
src/screen/welcome.rs Outdated Show resolved Hide resolved
@casperstorm casperstorm merged commit 06bbf47 into main Jun 26, 2023
@casperstorm casperstorm deleted the feat/welcome-and-help branch June 26, 2023 19:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Better help and welcome screen
2 participants