Skip to content
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

Closed
6 tasks done
lottycoupat opened this issue Jun 23, 2021 · 8 comments
Closed
6 tasks done

Integrate all pages together to produce final MVP #119

lottycoupat opened this issue Jun 23, 2021 · 8 comments
Assignees
Labels
Milestone 2 Build MVP
Milestone

Comments

@lottycoupat
Copy link
Collaborator

lottycoupat commented Jun 23, 2021

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?

Who can help?

Dev team.

Updates

Ticket captures remaining navigation tasks that must be updated now that all placeholder webpages have been created.

@lottycoupat lottycoupat added the Milestone 2 Build MVP label Jun 23, 2021
@lottycoupat lottycoupat added this to the 2: Create MVP milestone Jun 23, 2021
@lottycoupat
Copy link
Collaborator Author

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)

@anoura12
Copy link
Collaborator

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

@anoura12
Copy link
Collaborator

anoura12 commented Jul 2, 2021

@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.

@jhlink
Copy link
Collaborator

jhlink commented Jul 2, 2021

@anoura12 , let's complete the checklist first.

If it's really big, then sure, split the issue into multiple tickets.

@anoura12
Copy link
Collaborator

anoura12 commented Jul 5, 2021

@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.

  • Home

    • Change to landing page without sign up and sign in buttons and add additional items in the navbar

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?

@jhlink
Copy link
Collaborator

jhlink commented Jul 8, 2021

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.

@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?

Regarding the sign up flow, would we be having different views for each frame of the sign up?

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 public experiences page that @sowmya9507 is working on, the buttons are static. After she adds the requested change, the next step would be update the buttons, such that the nav bar buttons are functional.

@anoura12
Copy link
Collaborator

anoura12 commented Jul 11, 2021

@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?

@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?

Regarding the sign up flow, would we be having different views for each frame of the sign up?

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 public experiences page that @sowmya9507 is working on, the buttons are static. After she adds the requested change, the next step would be update the buttons, such that the nav bar buttons are functional.

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?

@jhlink jhlink assigned jhlink and unassigned anoura12 Jul 22, 2021
@jhlink
Copy link
Collaborator

jhlink commented Aug 8, 2021

All tagged issues are complete. Milestone #2 is complete at last.
Congrats to everyone!!

@jhlink jhlink closed this as completed Aug 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Milestone 2 Build MVP
Projects
None yet
Development

No branches or pull requests

3 participants