Split the Subresource Loading with Web Bundles Explainer into two parts 1) core part and 2) extension parts.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 125
- PR merge metrics
- No merged PRs in 30d
Description
It would be better to split the Subresource Loading with WebBundles Explainer into two parts 1) core part and 2) extension parts.
- Core part, which explain the common basic APIs for Subresource Loading
- Extension parts:
- Support urn::uuid resources and opaque origins (for use case #624)
- Any other extensions...
We might want to split an explainer into two files, physically, so that separation (and API boundary) would become clear.
By having a core part, we hope we can find a common part in various proposals, and we can write extension parts on the top of it and discuss separately.
Related issue: #623
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with subresource-loading.md and review related issue #623. Identify the common Subresource Loading APIs versus extension-specific material, then separate the explainer into core and extension documents with a clear API boundary. Done means the files and their scope clearly reflect that separation.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100