Last modified: 2014-02-06 03:10:38 UTC
Currently, we avoid serving users semi-protected or fully protected pages to edit in GettingStarted by checking for editability when they request a page. As a future enhancement, we might consider throwing out protected pages when the collection of pages is generated, so that we never have a protected pages cluttering up the list of pages to choose from. I cannot think of a case where we would serve a new user a page that's protected.
Ori, assigning this to you since you authored CategoryRoulette and can tell me how feasible/desirable this really would be, or if you think it's unnecessary.
After discussion with the team, I am resolving this as wontfix. Users cannot be served pages that they cannot edit, even if they are in the collection, because there is a manual check for this.
