Needs some design / product thinking before implementing.
User story: knowing what content people find useful will give us insight into what kinds of content are being used most and help highlight that content more. This will also help us measure success of the Content Library overall.
Adding one of the following to per-file pages + data will help us get that:
[ ] upvote/downvote
[ ] upvoting it in a certain category, i.e. "used for Growth", "used for Training", "not relevant"
technically, this will probably require storing this in Datastore
maybe model this after the Google developer pages, that have this widget + flow on all pages:
Needs some design / product thinking before implementing.
User story: knowing what content people find useful will give us insight into what kinds of content are being used most and help highlight that content more. This will also help us measure success of the Content Library overall.
Adding one of the following to per-file pages + data will help us get that:
technically, this will probably require storing this in Datastore
maybe model this after the Google developer pages, that have this widget + flow on all pages:
