Survey Feedback to Interpret across FAQ's
Questions for FAQ
- [ ] What is the @dev Program is not clear
- [ ] Confused about where to start & what’s the intermediate call to action
- [ ] Need to add own personal touch
- [ ] Exciting and confused - the benefits are great but I don't know who this is catered to - I also don't know how popular you are
What is liked about the site and can expand on in FAQ?
- [ ] Straight point of @protocol benefits
- [ ] Can easily access of social media platforms
- [ ] Organised resources
- [ ] Clean navigation
- [ ] Neatly organized
Added Jen Monroe to this card. She has not been attending the sprints but is directly associated with this program and should be included on the FAQ refinements. I would add Jen as a driver and myself as a reviewer.
@ksanty Thanks! Is this feedback about these pages?
https://atsign.dev/devprogram.html
https://atsign.dev/commissions.html
https://atsign.dev/certification.html
Esther and I have written a lot more content that is intended to go live when the program is all ready (online contract, earnings dashboard).
This is a direct response to feedback we got from users around @dev. Some of the content may be ready to go and some may need to be developed. The to-do is to review the feedback, review what we have and where there are holes and determine plan for filling holes.
Thanks, @JoryDJD This is the draft that Esther and I put together: https://docs.google.com/document/d/1W5TfjTol-0JxRRAEhEDH-2G8fOiis53GMdNQ08V1Dfo/edit?ts=602a7ca3
@jenmonroe, @eskao654 thanks for the look! I've edited and made suggestions to include the new site map and tone. I've been looking at comparable dev sites and really like the simplicity. I think design constraints forced us to over-explain a lot. It reads very conversationally, which feels right for the commercial site, but less for the dev site. Let's take the redesign as an opportunity to streamline the copy and experience. I made some edits to that effect, but there will need to be a more major paring back of copy, which could take a bit of time.
@eskao654 & @jenmonroe - this task is about FAQs and Code Snippets. The attachment listed above talks more about the program, tools, etc. We already have 3 articles which are good Q & A content that we put together for Paul Armstrong and Phillippe. That should be the starting point for this task.
@eskao654 I know you are working on this - can you please provide an update and next steps? TY
@ksanty, @tinashe404 and I are compiling the FAQs from the 3 articles to begin. We will choose the questions we feel are relevant and provide more recommendations based on the tickets that were logged over the past few months.
@eskao654 great! Please make sure to look at the survey feedback. :)
https://docs.google.com/document/d/11hK3Ile-DKg4oPYKQUJWwm1o00k3czJ17BHGnkj_ezk/edit