docs: move community presets table to docs site, add missing entries#2341
Open
mnriem wants to merge 2 commits intogithub:mainfrom
Open
docs: move community presets table to docs site, add missing entries#2341mnriem wants to merge 2 commits intogithub:mainfrom
mnriem wants to merge 2 commits intogithub:mainfrom
Conversation
- Move the full community presets table from README.md to the docs site at docs/community/presets.md, replacing the README section with a short link (matching the pattern used for Walkthroughs and Friends). - Add missing Jira Issue Tracking and Screenwriting rows to the docs table so it reflects all entries in catalog.community.json.
Add step to update docs/community/presets.md when submitting a community preset, and add corresponding PR checklist item. Matches the pattern used in the extensions publishing guide.
Contributor
There was a problem hiding this comment.
Pull request overview
Moves the canonical Community Presets listing out of the repository README and into the DocFX docs site, and updates the presets publishing workflow so future submissions keep the docs table in sync with the community catalog.
Changes:
- Replace the README “Community Presets” section with a link to the docs site page.
- Add missing “Jira Issue Tracking” and “Screenwriting” entries to the docs Community Presets table.
- Update
presets/PUBLISHING.mdto require adding a row todocs/community/presets.mdand include it in the PR checklist.
Show a summary per file
| File | Description |
|---|---|
presets/PUBLISHING.md |
Adds a publishing step + checklist item to keep the docs presets table updated when the community catalog changes. |
docs/community/presets.md |
Becomes the full community presets table and adds the previously missing rows. |
README.md |
Removes the inline presets table and replaces it with a docs-site link. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 3/3 changed files
- Comments generated: 1
| | Your Preset Name | Brief description of what your preset does | N templates, M commands | — | [repo-name](https://github.com/your-org/spec-kit-preset-your-preset) | | ||
| ``` | ||
|
|
||
| Insert your preset in alphabetical order in the table. |
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.
Moves the full community presets table from
README.mdto the docs site (docs/community/presets.md), replacing the README section with a short link — matching the pattern already used for Community Walkthroughs and Community Friends.Also adds two missing entries to the docs table so it reflects all presets in
catalog.community.json:speckit.taskstoissuesfor Jira via Atlassian MCP toolsUpdates the Presets Publishing Guide to include a "Update Community Presets Table" step (matching the pattern in the extensions publishing guide), with a corresponding PR checklist item.