You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reading through, say a filtered set of 15 job posts, requires the user to click through every job post to read its contents. We would like to move towards using a 'continuous scrolling' pattern which lets the user read through job posts by simply scrolling through them.
When the user scrolls to the bottom of a job post, the next job post should be shown with the URL updated through pushState (see quartz for an example of this pattern).
Scenarios
User lands on the homepage and clicks on a job post. The original list of job posts shown on the home page should be shown on the right-hand side, and the job post itself should be shown on the left-hand side.
User lands on a job post directly from an external link. The job post should be shown on the left-hand side, and the related job posts should be shown on the right-hand side.
On mobile, the right-handed sidebar containing job posts should be collapsible/viewable by swiping to/from the right edge.
UI mockup
In both the scenarios presented above, the job posts on the right-hand side should get updated when the user applies filters. What would be interesting to find out, is if this particular interface improves engagement.
The text was updated successfully, but these errors were encountered:
Reading through, say a filtered set of 15 job posts, requires the user to click through every job post to read its contents. We would like to move towards using a 'continuous scrolling' pattern which lets the user read through job posts by simply scrolling through them.
When the user scrolls to the bottom of a job post, the next job post should be shown with the URL updated through pushState (see quartz for an example of this pattern).
Scenarios
UI mockup
In both the scenarios presented above, the job posts on the right-hand side should get updated when the user applies filters. What would be interesting to find out, is if this particular interface improves engagement.
The text was updated successfully, but these errors were encountered: