community
community copied to clipboard
zowe
Create strategy for zowe community resources/information guides
There are a number of different sets of information that zowe needs to aggregate for our customers, each might have different personas. This epic aims to capture some of the info, so we can make a co-ordinated decision and actions going forward.
We have a lot of great content already, but have had a lot of feedback that the community (including core members) don't know that it exists, or where to find it, so we need to do a better job of aggregating these excellent resources.
I think the key is to break it down into resources that different personas are interested in, so it doesn't become too cluttered and information overload. Here are a few of the different ones we might want to consider:
- Marketing/product manager: overviews of zowe, why you would use it
- Evangelists: latest zowe decks to show at conferences/events
- Users: how to use it, what the key features are (might align with product manager)
- System Admin: How to set it up - more deep technical information about how it works
- Extender: How to add to it, what the extension points are, conformance info. Does this break down
- Contributor: what the community release schedules are, how to use the pipeline, create and test features etc
- Support: Technote/stack overflow style FAQs, troubleshooting walkthroughs & case studies There will be overlap with these personas where info will be useful to more than just one of them
Some of these will mostly just point to existing content in git readmes/wikis etc, but we should probably have a common 'front door/portal' for users to find out more info.
Questions
- Should medium.com be the portal for all of these, or for the more technical guides do we want to use something like gitpages?
- How does this interplay with the documentation - docs should stay up to date and fresher than blogs, so should some of these blogs just point to doc, or are our doc pages good enough to be the place users go to
- Troubleshooting has an element of ages to it - technotes are a snapshot in time of problems (eg zowe 1.7.1 has y known error scenario). These are great things to be google indexable whereas hopefully we will fix these problems in future releases, so not want them cluttering the doc pages. Should we rely on something like stack overflow/blogs for these?
- How do other high profile OS projects (node, vscode, helm etc) do this - we should try and use them as inspiration
@stevenhorsman +1 to this proposal. I think the on-boarding squad had a similar proposal and the doc squad has been considering to create a resources page as well that lists available materials/topics per user role or areas of interest, which is to create a personalized experience.
I'd like to join the discussion if there is one. Here are some of my initial thoughts and findings:
-
IMHO, zowe.org should be a good fit for this kind of information as it's the official website and most new users will start their journey from here. Also, blog sites like Medium need access to maintain content. zowe.org or zowe docs can be collaboratively maintained through PR so whenever there is a new resource to add, it can be more conveniently done.
-
I have been thinking of a design or experience as follows. Just my two cents.
on zowe.org, there is a brief sections similar to the following one (from IBM Cloud). Users can select their role and then be redirected to the corresponding doc site page that contains related resources to the role.
-
I do not find similar experience from VSC.
-
Helm lists some useful links on their community website.
-
Node has a Get involved page on their website that shows resources such as Medium blog site, Slack community, twitter account and some learning resources, but still it's not personalized.
https://nodejs.org/en/get-involved/
