-
Notifications
You must be signed in to change notification settings - Fork 18
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
Integrate all pages together to produce final MVP #119
Comments
hi @anoura12 could you possible add the tasks that need to be done for this please - such as linking the pages and figuring out the flow, and integrating into Django/Website version etc. (not sure if that's the correct wording) |
Yes sure, @lottycoupat |
@jhlink @lottycoupat Would it be a good idea to make separate issues on the integration of each page because as I'm making the checklist, it may come out to be lengthier than usual. |
@anoura12 , let's complete the checklist first. If it's really big, then sure, split the issue into multiple tickets. |
@jhlink I've added the tasks to the issue. Is this the right way to go about integrating the pages? Please feel free to make any changes to this as I think this is still in its early stages. Here's some points which I had some doubts on.
Should we go ahead with this idea for the home page? That way the user can refer to this page to understand the working of site without having to go to the landing page altogether. Regarding the sign up flow, would we be having different views for each frame of the sign up? |
@anoura12 , I'm not really sure what you mean here. If the landing page becomes the home page, how would the user understand the site while avoiding the landing page?
Different views? Do you mean the post-signup questions? This might be a bit of challenge to handle since it's dependent on how we define the signup process with OpenHumans. Let's handle this in Milestone 3. To reiterate, the goal of this ticket is to ensure that all the nav bar items direct to the appropriate pages. There is no expectation of any changes beyond this. If you consider, for example, the |
@jhlink Oh, what I meant was the home page has the same design as the landing page but with the updated navbar and sign in and sign up buttons removed like you saw in the MVP on Thursday. Basically, there should be some home page after the confirmation page. I thought keeping some of the content of the landing page same would help the user refer to the instructions easily. Should we have a different design for the home page if the two pages look too similar?
Okay, I think i got bit mixed up there. Thanks for the clarification! Is the checklist fine then or do I need to make any changes? |
All tagged issues are complete. Milestone #2 is complete at last. |
Summary
With respect to the user flow diagram, all pages need to be integrated together to follow this flow and user interaction.
Currently, each page in the prototype vary in navigation bar style, orientation, and selection options. This issue tracks progress for each web page that requires modification.
What needs to be done?
Home
page navigation bar #134)View Experiences
page nav bar #135)My Stories
page nav bar #136)Moderation
page nav bar #137)Share Experience
page nav bar #138)Confirmation
page nav bar #139)Who can help?
Dev team.
Updates
Ticket captures remaining navigation tasks that must be updated now that all placeholder webpages have been created.
The text was updated successfully, but these errors were encountered: