Say that explainer contents should move into specifications.#25
Merged
jyasskin merged 6 commits intow3ctag:mainfrom Jul 2, 2025
Merged
Say that explainer contents should move into specifications.#25jyasskin merged 6 commits intow3ctag:mainfrom
jyasskin merged 6 commits intow3ctag:mainfrom
Conversation
Member
|
I like where this is going – AND I feel we should leave room for spec developers to maintain a separate explainer if that's how they want to operate, as long as they keep it up to date. |
torgo
reviewed
Jun 17, 2025
jyasskin
commented
Jun 17, 2025
alice
reviewed
Jun 18, 2025
index.bs
Outdated
Comment on lines
55
to
57
| Start your specification using whatever tool you prefer | ||
| (e.g. [Bikeshed](https://speced.github.io/bikeshed/) or [Respec](https://respec.org/)). |
Contributor
There was a problem hiding this comment.
This seems a bit out of place to me. I think most (?) spec writing is in the form of edits to existing specs, or at least additional documents in an existing collection, meaning that the choice of tool is not really up to the author.
Co-authored-by: Daniel Appelquist <dan@torgo.com>
Co-authored-by: Alice <95208+alice@users.noreply.github.com>
jyasskin
commented
Jun 25, 2025
Contributor
Author
|
Breakout B was happy with the latest version of this PR. I'll merge at the end of June 26 if I don't hear other comments/objections. |
github-actions bot
added a commit
that referenced
this pull request
Jul 2, 2025
SHA: 6e6adaf Reason: push, by jyasskin Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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
5 participants
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.
This is meant to fix #6. Also see #19 for some frustration that I used as input.
It's still fairly rough, and I'm expecting to refine it based on feedback. @slightlyoff and @alice, you're likely to have comments.
Preview | Diff