-
Notifications
You must be signed in to change notification settings - Fork 189
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
Update homepage to point to guideance for our core expected user groups #873
Comments
I like the idea of breaking down different personas of people accessing the website.
Even "core users" might be too restrictive. I think there will be people accessing the website who are not users at all, but rather might want to just get basic information. The groups you have outlined seem to have quite a bit of overlap. What's the difference between "scientist", "data scientists / data engineers", and "data engineers"? I know many people who might identify with all three. I would probably break it down as follows:
|
What about structuring around types of tasks or problems? I want to:
That gets away from people choosing 'I am XYZ user' and not finding the right info, in addition to avoiding the battle of 'what is a data scientist'. |
and there is the systems problem of 'solve the politics of getting this started' |
@abkfenris I like this breakdown of tasks and structuring the guides around tasks. It seems like we can either move forward with the set that you have proposed and/or discuss further which ones should be included. I think I would also add: See examples of what others and I can do with Pangeo (which links to the pangeo showcase) Should we prioritize this list? I'm inclined to starting with some of the low-hanging fruit / most beginner friendly:
Then
Finally
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it had not seen recent activity. The issue can always be reopened at a later date. |
Reviving this issue after @abarciauskas-bgse and I had some discussions + hacking today! Please see #878 for details |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it had not seen recent activity. The issue can always be reopened at a later date. |
My current assessment of who the core users of Pangeo might be:
If we agree these are the main groups I think we determine which guidance we should link to or create and open an issue to refine or create that page and make sure it's up to date, and add those "quick links" to the home page
The text was updated successfully, but these errors were encountered: