Merged with main

plehegar · plehegar · commit e32e9aad5d7d · 2025-08-18T16:00:09.000-04:00
diff --git a/editor/index.md b/editor/index.md
@@ -17,10 +17,10 @@ If you are a newly appointed editor in your Working Group, here is some advice t
 
 - Get an [idea of the role of an editor](role.md) at W3C
 - Check the most popular editing tools: [Bikeshed](https://speced.github.io/bikeshed/), [respec](https://github.com/speced/respec/wiki)
-- [Pubrules](https://www.w3.org/pubrules/) ([publication requirements](https://www.w3.org/pubrules/doc)) and links to related policies (e.g., [namespaces](editor/namespaces.md), [media type registration](editor/mediatypes.md), [version management](editor/versioning.md), and [in-place modifications](standards-track/republishing.md))
-    See also [Pubrules issue management](https://github.com/w3c/specberus/issues)
+- When using Github, check [Using GitHub for Spec Work](../github/specs.md) and [Workflow for editors and other contributors](./github/workflow.md)
+- [How to Organize a Recommendation Track Transition](../transitions/) explains the process to get a document published as a technical report. The [step finder](../transitions/nextstep.md) will help you finding which transition to do next and what the requirements are.
+- [Pubrules](https://www.w3.org/pubrules/) ([publication requirements](https://www.w3.org/pubrules/doc)) and links to related policies (e.g., [namespaces](namespaces.md), [media type registration](mediatypes.md), [version management](versioning.md), and [in-place modifications](standards-track/republishing.md)). See also [Pubrules issue management](https://github.com/w3c/specberus/issues)
 - Publications can only happen on Tuesdays and Thursdays ([Member-only archive of announcement](https://lists.w3.org/Archives/Member/chairs/2009JanMar/0192.html)), unless you use the [automated publication system](https://github.com/w3c/echidna/wiki)
-- [How to Organize a Recommendation Track Transition](../transitions/) explains the process to get a document published as a technical report.
 - Review [WCAG](https://www.w3.org/TR/WCAG/)
 - All W3C editors are invited to join the [publicly archived mailing list &lt;spec-prod@w3.org&gt;](https://lists.w3.org/Archives/Public/spec-prod/) to share and discuss the techniques and tools used to produce W3C specifications.
 
diff --git a/github/specs.md b/github/specs.md
@@ -22,7 +22,7 @@ toc: false
    cd reponame
    ```
 1. **Note: this step and the following are not needed if you set up your repository using the W3C Repository Manager as it can create a basic ReSpec document for you**.  
-Now we want to create the spec document itself. I use [ReSpec](https://respec.org/docs/), so I simply copy the content of the [default template](https://respec.org/docs/#getting-started) into an `index.html` page at the root of my repository. And then add it to the repository.
+Now we want to create the spec document itself. I use [ReSpec](https://respec.org/docs/), so I simply copy the content of the [default template](https://respec.org/docs/#getting-started) into an `index.html` page at the root of my repository. And then add it to the repository. See also the requirements for [Group-internal Drafts](../editor/editors-draft.md#reqs).
    
    ```shell
    git add index.html
