Quick Discover Fix about webmaker-core

[ryanwarsaw]

What are your thoughts on providing a user toggle-able option that allows them to choose whether they want to only see localized content or not? Surely we would need to build such a view in the future anyways (for other user related options).

[xmatthewx]

@ryanwse – you're right, that could be an ideal solution. We just don't have the time to design, build, test, and localize it. Adding a toggle is relatively easy. Figuring out where to put it, how to label it, and what to call it gets more complicated. Would sketch up a proposal to consider for later. In the meantime, Hashtags will also give people a chance to create a connection between local content.

[xmatthewx]

As a quick demo of the problem, hit both of these requests. You'll see that the english route doesn't return project ID 56558.

https://api.webmaker.org/discover/fr-US?page=1&count=50
https://api.webmaker.org/discover/en-US?page=1&count=50
https://api.webmaker.org/discover/?page=1&count=50

see: line 79 and line 13 in the project-list component.

[cadecairos]

Project 56558 shouldn't show up in the en-US route - it's lang is set to fr

edit - so is the problem is that you can't see a non-localized set of discover projects without changing the system locale?

[xmatthewx]

You are right that it's not a bug in the code. We don't have enough curators to feature activity, so discover is likely to feel stagnant. And, helper and how-to projects haven't been localized, so others don't see them.