-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New "unlisted" status in Coda #762
Comments
What would the contents of the banner be? |
I realize "linkable" is probably not the best name if it gets shown to the user. I temporarily added "Unvetted" to this page, but the phrasing could change when I discuss it with editors Yes, it would point to a nice page with a banner like it does for "in progress" at the moment. |
In the end, we settled on calling this "Unlisted" |
Things that need (or needed) to be done
|
@mruwnik I'm having issues ensuring that the updates to Banners are taken into account. Is there some job that I need to run to update the banners? |
the run parser job should do it automatically. Though it only updates answers where the actual contents have changed. So if you change the banner contents, it might take a while (quite a while, in the case of seldomly edited articles) for that to propagate. Adding a space or something the the article you're interested in should be enough to trigger it, though |
Context: https://docs.google.com/document/d/12NicU1N-ijHuM8J6gIAcp3snOZKUQ6zlguB8Cs21JIQ/edit#heading=h.bxchuroysqj9
We want a status in coda that lives between "in progress" and "live on site" that is partially discoverable.
Articles tagged as "unlisted" would
Articles could be changed to "unlisted" by people in the "@editor" role on discord (subject to change)
There is some uncertainty on how "unlisted" should interact with "in review". The simple option is that anything "in review" would inherit the permissions of "unlisted", but this means that we would need to clamp down on permissions to send to "in review". Another option is to make "in review" a tag instead of a status, TBD
The text was updated successfully, but these errors were encountered: