Synchronized build

Author: lektor-bot

contributing-code/github-repo-guidelines/index.html

@@ -342,8 +342,9 @@ <h2 id="optional-items">Optional items</h2><ul>
 <li>A <a href="https://help.github.com/en/articles/creating-a-pull-request-template-for-your-repository">pull request template</a>. GitHub pulls the default template from our <a href="https://github.com/creativecommons/.github"><code>.github</code> repository</a> automatically, but if you want/need to customize it, create it in your repository.</li>
 <li><a href="https://help.github.com/en/articles/adding-support-resources-to-your-project">Support resources</a>. GitHub pulls the default <code>SUPPORT.md</code> file from our <a href="https://github.com/creativecommons/.github"><code>.github</code> repository</a> automatically, but if you want/need to customize it, create it in your repository.</li>
 </ul>
-<h2 id="standard-labels">Standard Labels</h2><p>All repositories must contain a set of standard labels, <a href="https://github.com/creativecommons/ccos-scripts/blob/master/normalize_repos/labels.py">documented here</a>. You don't have to set these up manually. CC staff can run <a href="https://github.com/creativecommons/ccos-scripts/tree/master/normalize_repos">a script</a> that to make sure all repositories have this label.</p>
-<p>Repositories may contain additional custom labels as well. It is recommended that custom labels be explained in the contribution guidelines for that project.</p>
+<h2 id="standard-labels">Standard Labels</h2><p>All repositories must contain a set of standard labels, <a href="https://github.com/creativecommons/ccos-scripts/blob/master/normalize_repos/labels.json">listed here</a>, in addition to repository-specific skill labels, <a href="https://github.com/creativecommons/ccos-scripts/blob/master/normalize_repos/skills.json">listed here</a>.
+You don't have to set these up manually. The labels are <a href="https://github.com/creativecommons/ccos-scripts/tree/master/normalize_repos">automatically managed</a> on all CC repositories, and so, must not be renamed.</p>
+<p>Repositories may contain additional custom labels as well which will remain unaffected by the sync. It is recommended that custom labels be explained in the contribution guidelines for that project.</p>
 <h2 id="branch-protections">Branch Protections</h2><p>Branch protections are automatically set up by CC staff via <a href="https://github.com/creativecommons/ccos-scripts/tree/master/normalize_repos">this script</a>. By default, pushing directly to the <code>master</code> branch is disabled and all pull requests require review by at least one person before merge.</p>
 <h2 id="cc-metadata-file">CC Metadata file</h2><p>Each repo should have a <code>.cc-metadata.yml</code> file in the root directory with the following structure:</p>
 <pre>