help: update community submission policy settings #151
Conversation
There was a problem hiding this comment.
I kept the URL to be .../review-policy/ since I don't want to break any existing links... We should find a way though to handle "archived" pages and redirect them possibly (unfortunately for static docs this means some JS, that says "Redirecting you to the new location of this page..." )
There was a problem hiding this comment.
we can also redirect without JS https://sentry.io/answers/redirect-from-an-html-page-without-using-javascript/
There was a problem hiding this comment.
Ah nice, I didn't know about this <meta> + http-equiv= sorcery.
I was more concerned about crawlers, who might only rely on HTTP response codes, but I guess many of them are running a headless browser nowadays and might follow these meta tags as well.
* The "Review policy" settings page was renamed to "Submission policy". * There's is a new "Records submission policy" setting for controlling who is allowed to submit to the community.
slint
force-pushed
the
update-community-submission-policy
branch
from
0b61b7c to
9daf846
Compare
content/help/docs/communities/manage-community-settings/review-policy/contents.lr
Show resolved
Hide resolved
2 participants
who is allowed to submit to the community.
Before
After