A test attempt at moving some of the Product team feature definition and prioritisation into GitHub. The aim is to create more detailed feature definitions, provide more transparent prioritisation and more effective "linking" of product design to development tickets (currently in the xPub project board).
It would make sense at some point to move from these static pages that require updating to something based on the people API. Our two options are to a) update static content for now and move to API based in future. Or b) move to API based sooner.
It could also benefit from being converted to a single page instead of split into 3 pages with side menu.
It would be a shame to push back updates to this page too far, however it is low priority because few users appear to be using this page - in the past 3 months we've had approx 570 unique pageviews of contact-us by approx 9,500 users. It is hard to say how many, if any, have viewed the editorial team or production team pages as GA doesn't appear to have any data for these.
These pages no longer reflect the teams at eLife (do we simply update static content or improve to always reflect https://elifesciences.org/about/people/staff?)
It would make sense at some point to move from these static pages that require updating to something based on the people API. Our two options are to a) update static content for now and move to API based in future. Or b) move to API based sooner.
It could also benefit from being converted to a single page instead of split into 3 pages with side menu.
It would be a shame to push back updates to this page too far, however it is low priority because few users appear to be using this page - in the past 3 months we've had approx 570 unique pageviews of
contact-usby approx 9,500 users. It is hard to say how many, if any, have viewed the editorial team or production team pages as GA doesn't appear to have any data for these.