Remove welcome text & instructions on homepage if user has tasks? #1713

New Issue

deanishe · 2020-04-02T18:23:17Z

deanishe commented

2020-04-02 18:23:17 +00:00

The "Hi dean! Click on a list…" text takes up a large amount of the screen on mobile (I have a small phone) that could be used for showing tasks.

If a user has some tasks, it seems reasonable to assume that they know how to use Vikunja, so perhaps the welcome text & instructions could be hidden?

The big "import" button also takes up a lot of space, but I think #61 is about hiding that.

The "Hi dean! Click on a list…" text takes up a large amount of the screen on mobile (I have a small phone) that could be used for showing tasks. If a user has some tasks, it seems reasonable to assume that they know how to use Vikunja, so perhaps the welcome text & instructions could be hidden? The big "import" button also takes up a lot of space, but I *think* #61 is about hiding that.

konrad commented

2020-04-02 19:58:22 +00:00

Hiding the text if the user has tasks seems like a good idea. I thought of hiding it, but couldn't think of a good way to determine if the user has used Vikunja - I like your proposition.

I'd like to postpone this a bit until we have user settings to also move the migration button to the setting - then we could have it all hidden in one go.

Hiding the text if the user has tasks seems like a good idea. I thought of hiding it, but couldn't think of a good way to determine if the user has used Vikunja - I like your proposition. I'd like to postpone this a bit until we have user settings to also move the migration button to the setting - then we could have it all hidden in one go.

👍 1

konrad referenced a pull request from vikunja/frontend that will close this issue

2020-06-15 16:35:26 +00:00

Hide hints on start page if a user has tasks #159

konrad closed this issue

2020-06-15 16:47:18 +00:00

konrad commented

2020-06-15 16:47:44 +00:00

Implemented in vikunja/frontend#159.

Implemented in https://kolaente.dev/vikunja/frontend/pulls/159.

konrad referenced this issue from a commit

2024-02-07 14:00:33 +00:00