4 Week UI/UX Mock Ups #446
Comments
patrick727
added
zz-Marketing
|
@patrick727 @pmoorman @kitblake - based on the Governance Document above, please see the attached sitemap for review. |
|
Is there a meeting to discuss the UI/UX mock ups? If yes, please share meeting info. |
|
Share meeting info. Zoom always.
Sent from Yahoo Mail on Android
|
|
@AyAyRon-P Nice work on the sitemap. It captures all of the points in the Gov Doc above and can serve as a long term view. We should also refine a short term view which would comprise the structure and content we want to have at launch, with more to be added over time. Note that "Deals" is in pink in the Gov Doc. Personally I'm not sure it belongs here (but it's important that it's available somewhere). The top level navigation in the site map includes:
That's a lotta top level links, we could consider merging or removing some, but I won't go into that now. It's nice to have the visualization. |
|
In the #exec-committee meeting on March 3rd it was affirmed that the Members Portal WG has the mandate to create a structure for the future site. @ian-bloom has the lead as the site will replace the current critical infrastructure in members.rchain.coop. The question "What is the site for?" came up. My answer is: “member.rchain.coop is the gateway to getting involved”, but that's for the WG to nail down. |
|
@kitblake do you have time for a chat and we can add some color to the sitemap for hierarchy and timeline of development. |
|
Great stuff with sitemap Aaron. Would all of that fit into something like this |
|
Having only 5 items in the (initial) top level navigation is sensible. This is what @patrick727's site map looks like in text. Things in italics are future items, not necessarily included for launch (once this coalesces we should MoSCoW these items to plan for the launch). I added one item in bold that comes from @AyAyRon-P's site map, with the idea that most, if not all, should be added. As @AyAyRon-P said, it would be good to make color coded site map diagrams. But let's first agree on an outline structure, otherwise the mappers will spend a lot of time revamping diagrams.
Please either edit this message directly, or edit and copy the indent code for a new post, to make a revised structure. @patrick727 what are you thinking about for the chat? Yet another chat app? A special chat for onboarding? I'd rather make a 'gangplank' channel in Discord for newbies and onboarding. |
|
I looked through the suggestions and this is what I came up with: # About This is not the best of formatting to create a better visual. See attached for better visual. |
|
@patrick727 Yes I can create a more vertical sitemap if we need to but my recommendation is still to add color to show particular segments of the navigation. @kitblake I agree with your outline structure I think that cleans up much of what was in question as far as what is needed/wanted/nice-to-have. It would be good to use some of the sub-cats from @makys in your structure. What I like about yours is the naming - it's navigation on a more relaxed level using terms like "GET INVOLVED" and "ECOSYSTEM" @kitblake when you say "CHAT" do you mean a bot? Or do you mean a direct message link to someone? I think your recommendation to join a discord channel would be more functional and makes more sense to drive the interested party to discord for communication. Once we have consensus on the MAIN CATEGORIES we can then worry about flushing out the sub categories and at that point I will update the site map. |
|
I agree, but I think the sub categories are what will define the main categories @kitblake for chat, greg mentioned if it would make sense to have a members only discord again, and I added that this should be a chat instance in the member site, so this chat could be an integrated discord instance or mattermost if we want to go with that. |
|
Ok @patrick727, an integrated chat (of a Discord or Mattermost channel) would be cool. No duplication. |
|
Eek, a proprietary doc format! :) @makys I appended your outline to the Member Service Portal doc: |
|
Anyone on here have experience with wordpress? Looking for help mocking up this in a wordpress test instance |
|
@patrick727 I have some experience - do you have an account? |
|
@AyAyRon-P cool i just made you an editor of the test instance |
|
Someone called Chiamaka Igweka in gdocs added this to this week's agenda (#469). I'm interested to know why. Just FYI? Or is this issue stuck? What's the goal of the agenda item? @Tonyprisca13 do you know that person? |
|
I see people referring to this issue from discord discussion, so I suppose it's important to note that @patrick727 has handed the lead over to @ian-bloom (for a time, at least). @ian-bloom are you still inclined to follow the approach in this issue? |
|
@dckc Yes. I'm mostly in accord. Since WordPress is flexible, and member.rchain.coop will be inward facing (like an intranet) I'm not overly concerned about getting the navigation hierarchy right on day one. We can play and iterate. My biggest concerns for the site are:
|
OK, so what list of tasks does that suggest? "read architecture document" was a huge part of onboarding, for me, but is it part of what you have in mind? How about "find a first coding issue to work on"? Are folks onboarded when we have their $20 or when they are productively engaged? |
|
We could start with the most basic stuff (e.g. leave email => pay => passport => Discord => KYC => Github) or something like that. Once we have that, we can widen the scope to include more and more stuff. End-goal is either "productively engaged" or (better yet) "so enthusiastic they tell their friends about it" |
|
Do we actually know what is "small" scope and what is not? Hopefully in our meeting soon we talk through some of the requirements for implementing this navigation in an M.V.P like manner. it's important to remebmer the demand from the governance forum was for better communications/collaboration tools. Fluid member onboarding does play into that as well. Registration/sign in - member onboarding and then we can build out features from there. @kitblake great point in regards to the pre-registration nav and post registration nav. The wiki & calendar could definitely sit pre-registration. But I think proposals & voting should be behind an authentication wall. Thoughts? |
No. Not if you want my participation, anyway. If I can't share it (e.g. link to it) freely with all the communities I work in, I'm not going to put my effort there. |
|
It's important to keep in mind this solution is an attempt to be the interim solution before an RChain based solution goes live. Not an interim of an interim solution. Not saying "all or nothing" but it definitely should be used to solve most of the problems highlighted in the governance forum and in the service doc. We can/should contract help to develop so difficulty to development would be less of a critical factor if we can hire the help to do it. The most important factor to me is UX and if there is a small scope, it should flow alot like the large scope so as to keep consistency and avoid losing members engagement by requiring to many behavior changes. |
|
@dckc i should have said specifically for member related votes. Like if we wanted to answer the question "what do members think of this" |
You think we're going to get even an interim solution right the first time? Surely an incremental approach is the way to go. |
|
I think we can approach "good enough" quickly yes for most of the proposed navigation pieces. I guess i should have framed it as this question "what parts of what you called "all or nothing" approach should be left out and why?" That'll help me understand the specifics. |
|
@patrick727 , @pmoorman , @ian-bloom and I talked this stuff over. We used Pats take on member.rchain.coop to capture the results. After about 8 slides is an MVP dividing line; the stuff below that is "nice to have", at least for the next week or so. Jeremy spun up a coop-member-v1 wordpress instance for Patrick a little while back; Ian is to arrange access for Dan and Pieter. By the end of the month, we should know more about some technical details behind the existing member.rchain.coop set-up. Migrating to LDAP (#513) is still the plan. We agreed to put a page including benefits of membership (#520) between the Join Membership link on the coop homepage and the "enter your registration details" page. And a calendar seems cost-effective. For now, the rest would just be a page of links or some such. For follow-up on Email-based onboarding, see #219 where @pmoorman has the ball to put together something that Dan and Ian can perhaps take to the executive committee. |
|
Yes @patrick727, I think I know what you were gunning for with those wireframes. You were envisioning a special entertaining space for Members which would in itself provide another reason for becoming a Member (as stated in the the post-conf doc). But all of information we want to have on the site, including how the Co-op operates and functions, is already public info. There's no reason to have any of it behind a login. In fact there's only one task that I see that actually requires logging into to the Member site (to set a preference). However I think we can still create that Members space you're looking for, even though it's a few steps away. First we need to get the Members site working for onboarding. Then we can expand with 'Member retention' features. For the services that you embedded, like Discord and Github, those do require a login. But they also want to be full screen, so I think we need to just accept that users will open a new tab for those interfaces. Embedding the Calendar should be doable because it won't be interactive. It would indeed be great if we could get some OAuth happening that allows some of the services, like Discord and Loomio, to interchange authorization. |
|
Question: for the above-described MVP, are we going to keep using the registration app? By that I mean the javascript-driven single page KYC application? |
|
Hard to say just now, but...
|
|
Finally had an opportunity to catch up on this. Point to what Kit said "There's no reason to have any of it behind a login. In fact there's only one task that I see that actually requires logging into to the Member site (to set a preference)." I think we need to have a site that has more open information. We have a site already that shows very little about us and tracking down information once someone is a member is still hard to do. This has been a pain point for some time and I still don't see this being addressed, unless I missed it and all that information will be on the rchain.coop page? @kitblake you asked about the KYC application and I had an opportunity to speak with Ian about this there are several that we discussed - Gemalto, Jumio, ShuftiPro, Yodlee, and SynapseFI. Even with all of these applications/products available there still seemed to be missing the 'personal' touch that we like to welcome/verify a new member, it was my impression he wanted to continue doing a 1-1 verification. @patrick727 I saw you needed someone for UI/UX development - how soon do you need this? Is there already a team in place? I saw Dan mention Jeremy doing a wordpress mock up. Let me know at your earliest convenience so I can plan for production. |
|
I don't look at the coop-member-v1 wordpress instance as a mock-up. I expect / hope it will replace member.rchain.coop as soon as it handles the MVP functionality. About KYC services: be sure to share your notes in #511 as well. |
|
#511 is the issue of KYC services. I'm asking nicely one more time that you move that discussion there. Then I will start deleting comments that belong there. |
|
It looked to me like #511 is about "non-USD membership payments: evaluate alternative payment providers" with no discussion of KYC, but I'm happy to keep this thread focused so I've transposed my comment and deleted it here. |
|
Oops! Sorry... looks like I got my wires crossed... I could have sworn I opened an issue about scalable KYC, but it looks like I got it confused with #511 ... in about 3 places now. Sigh. |
|
@patrick727 I added a few notes to your slides. Right now the wireframes are a mish-mosh of pre-MVP thinking mixed with the minimal. They provide no guidance for the implementation which is asking for trouble. |
|
The ranked choice poll has closed and here's the top ten. To review, the question was: This is my thinking per item:
|
|
@kitblake I just gave you access to coop-member-v1 too. Wordpress gave me the impression that it sent you a mail message. Let us know if you're not able to log in. |
|
@ian-bloom what news?
|
|
@dckc I haven't received any mail from Wordpress so logging in to coop-member-1 hasn't happened. |
|
What I have done is update the site structure outline (at the end of the doc) in: @eedsilva, this could be mocked up if you have time. |
|
I gather the next step is #595. |
Lets take the feedback from issue #400 and use it to inform mock ups for the member website
current mock-up:
We used Dan's office hours (#403) Saturdays 9am Chicago time a couple times (17 Mar, 24 Mar) to discuss this and other member-site issues. It's a pattern that seems likely to continue.
earlier discussion documents:
Governance Document
Member service portal
The text was updated successfully, but these errors were encountered: