Repository navigation
docs: integrate extension publishing guide into documentation site - #5163
Merged
Merged
Conversation
Move the guide into docs/extensions, wire DocFX navigation, update references, and clarify the required submission process. Assisted-by: GitHub Copilot (model: GPT-6.1 Sol, autonomous) Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
No active review issues remain for the publishing-guide relocation and related documentation updates.
No open issues 🎉
What changed in this PR
Publishes the Extension Publishing Guide on Spec Kit’s documentation site and connects it to the community contribution documentation.
Changes:
- Moves the guide into
docs/extensions/and adds DocFX inclusion and community navigation. - Updates references to the relocated guide and repairs outgoing documentation links.
- Clarifies that submissions must use the issue template.
| File | Description |
|---|---|
extensions/template/README.md |
Links starter projects to the published guide. |
extensions/README.md |
Updates the catalog submission guidance link. |
extensions/EXTENSION-USER-GUIDE.md |
Updates the publishing resource link. |
extensions/EXTENSION-DEVELOPMENT-GUIDE.md |
Links publishing instructions to the documentation site. |
docs/toc.yml |
Adds Publishing Extensions under Community. |
docs/reference/catalogs.md |
Uses a site-relative publishing-guide link. |
docs/README.md |
Lists the guide in the documentation structure. |
docs/extensions/publishing.md |
Relocates the guide, repairs links, and clarifies submission policy. |
docs/docfx.json |
Includes extension documentation in the site build. |
docs/community/overview.md |
Links contributors to the relocated guide. |
docs/community/extensions.md |
Updates the extension submission guidance link. |
.github/skills/add-community-extension/SKILL.md |
Updates the publishing-rules source path. |
.github/ISSUE_TEMPLATE/extension_submission.yml |
Points the submission form to the published guide. |
Review effort: Max
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Move the Extension Publishing Guide from
extensions/EXTENSION-PUBLISHING-GUIDE.mdtodocs/extensions/publishing.mdso it is published on the documentation website.docs/.Testing
uv run specify --helpuv sync && uv run pytestDocumentation-only change; CLI tests and sample-project testing were not run.
docfx docs/docfx.json— passed with zero errors and three existing warnings about parent-directory globs and an unrelated link indocs/reference/core.md.git diff --check— passed.AI Disclosure
AI disclosure: Authored with GitHub Copilot using GPT-6.1 Sol (model ID: gpt-6.1-sol), default reasoning settings, autonomous editing under human direction. AI assistance covered the documentation move, navigation and link updates, submission-policy wording, local preview, validation, commit, and PR preparation. No CLI runtime code was changed.