Makes sense to me!

We talked about this in the team meeting and came up with the following ideas:

1. The Dashboard should still be visible to users who aren't logged in, but of course they won't be able to see any data specific to a logged-in user (e.g., "My Contributions"). So the Dashboard needs to be configured to only render certain components if there is a currently logged-in user. We could also have some kind of message indicating that the user ought to log in to see more.

2. Related to the above, the "My Contributions" table element needs to display something when the currently-logged in user has no contributions. Slavina suggested something like "Click here to get started." (presumably a link that would return to the Home view)

3. We were in broad agreement about Slavina's idea that the input bar for tasks be rendered immediately on the Homepage, without the user having to click "Yes Please." It reduces unnecessary clicking and makes for a more streamlined user experience.

4. So if we drop the "Yes Please" button, we could prompt the user to log in upon clicking "submit", but it might be even better to prompt them to login if they click the input bar (I'm thinking this because, in the process of logging in, any data entered into the input bar may be lost -- unless you capture and store it somehow -- and that would mean that the user's time had been wasted).