Your explainer is a living document that describes the current state of your proposed web platform feature, or collection of features.
In the early phases of design, this may be as simple as a collection of goals and a sketch of one possible solution.
As your work progresses, the explainer can help facilitate multi-stakeholder discussion and consensus-building by making clear:
Once there is a reasonable amount of consensus on the approach and high-level design, the explainer can be used to guide spec writing, by serving as a high-level overview of the feature to be specified and the user need it serves.
Once the spec is written and the feature is shipped, the explainer can then provide a basis for author-facing documentation of the new feature.
Since your explainer may be referred to by a range of stakeholders, not all of whom are likely to be highly motivated to spend a lot of time on it, you should always try to keep your explainer as brief and easy to read as possible.
[You can generate a Table of Contents for markdown documents using a tool like doctoc.]
[The “executive summary” or “abstract”. Explain in a few sentences what the goals of the project are, and a brief overview of how the solution works. This should be no more than 1-2 paragraphs.]
[What is the end-user need which this project aims to address?]
[If there are “adjacent” goals which may appear to be in scope but aren’t, enumerate them here. This section may be fleshed out as your design progresses and you encounter necessary technical and other trade-offs.]
[If any user research has been conducted to inform the design choices presented discuss the process and findings. We strongly encourage that API designers consider conducting user research to verify that their designs meet user needs and iterate on them, though we understand this is not always feasible.]
[For each related element of the proposed solution - be it an additional JS method, a new object, a new element, a new concept etc., create a section which briefly describes it.]
// Provide example code - not IDL - demonstrating the design of the feature. // If this API can be used on its own to address a user need, // link it back to one of the scenarios in the goals section. // If you need to show how to get the feature set up // (initialized, or using permissions, etc.), include that too.
[Where necessary, provide links to longer explanations of the relevant pre-existing concepts and API. If there is no suitable external documentation, you might like to provide supplementary information as an appendix in this document, and provide an internal link where appropriate.]
[If this is already specced, link to the relevant section of the spec.]
[If spec work is in progress, link to the PR or draft of the spec.]
[If there are a suite of interacting APIs, show how they work together to solve the key scenarios described.]
[Description of the end-user scenario]
// Sample code demonstrating how to use these APIs to address that scenario.
[Talk through the tradeoffs in coming to the specific design point you want to make.]
// Illustrated with example code.
[This may be an open question, in which case you should link to any active discussion threads.]
[This should include as many alternatives as you can, from high level architectural decisions down to alternative naming choices.]
[Describe an alternative which was considered, and why you decided against it.]
[Implementors and other stakeholders may already have publicly stated positions on this work. If you can, list them here with links to evidence as appropriate.]
[If appropriate, explain the reasons given by other implementors for their concerns.]
[Your design will change and be informed by many people; acknowledge them in an ongoing way! It helps build community and, as we only get by through the contributions of many, is only fair.]
[Unless you have a specific reason not to, these should be in alphabetical order.]
Many thanks for valuable feedback and advice from: