Skip to content

Commit 47a22d4

Browse files
Say how to explain developer-focused features. (#30)
SHA: 0d4cb99 Reason: push, by jyasskin Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
1 parent df642c4 commit 47a22d4

File tree

1 file changed

+91
-9
lines changed

1 file changed

+91
-9
lines changed

index.html

Lines changed: 91 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -5,10 +5,10 @@
55
<title>Writing Effective Explainers</title>
66
<meta content="NOTE-ED" name="w3c-status">
77
<link href="https://www.w3.org/StyleSheets/TR/2021/W3C-ED" rel="stylesheet">
8-
<meta content="Bikeshed version 618007319, updated Thu Jun 26 17:23:55 2025 -0700" name="generator">
8+
<meta content="Bikeshed version 3f621ba99, updated Mon Jul 28 15:38:36 2025 -0700" name="generator">
99
<link href="https://www.w3.org/TR/explainer-explainer/" rel="canonical">
1010
<link href="https://www.w3.org/2008/site/images/favicon.ico" rel="icon">
11-
<meta content="30c67e473eb0f9ef2f5c6ff660e6c7028e76187c" name="revision">
11+
<meta content="0d4cb9984d7393667d67859b553396e02192e5c8" name="revision">
1212
<meta content="dark light" name="color-scheme">
1313
<link href="https://www.w3.org/StyleSheets/TR/2021/dark.css" media="(prefers-color-scheme: dark)" rel="stylesheet" type="text/css">
1414
<style>/* Boilerplate: style-autolinks */
@@ -538,7 +538,7 @@
538538
</p>
539539
<h1 class="p-name no-ref" id="title">Writing Effective Explainers</h1>
540540
<p id="w3c-state"><a href="https://www.w3.org/standards/types/#ED">Editor’s Draft</a>,
541-
<time class="dt-updated" datetime="2025-07-03">3 July 2025</time></p>
541+
<time class="dt-updated" datetime="2025-08-27">27 August 2025</time></p>
542542
<details open>
543543
<summary>More details about this document</summary>
544544
<div data-fill-with="spec-metadata">
@@ -577,8 +577,7 @@ <h2 class="no-num no-toc no-ref heading settled" id="sotd"><span class="content"
577577
publication. A list of current
578578
<abbr title="World Wide Web Consortium">W3C</abbr> publications and the
579579
latest revision of this technical report can be found in the <a href="https://www.w3.org/TR/"><abbr title="World Wide Web
580-
Consortium">W3C</abbr> standards and drafts index</a>
581-
.</em>
580+
Consortium">W3C</abbr> standards and drafts index</a>.</em>
582581
</p>
583582
<p>
584583
This document was published by the <a href="https://www.w3.org/groups/other/tag/">Technical Architecture Group</a>
@@ -602,7 +601,7 @@ <h2 class="no-num no-toc no-ref heading settled" id="sotd"><span class="content"
602601
licensing requirements or commitments on this document.
603602
</p>
604603
<p>
605-
This document is governed by the <a href="https://www.w3.org/policies/process/20231103/" id="w3c_process_revision">03 November 2023 W3C
604+
This document is governed by the <a href="https://www.w3.org/policies/process/20250818/" id="w3c_process_revision">18 August 2025 W3C
606605
Process Document</a>.
607606
</p>
608607
</div>
@@ -623,6 +622,20 @@ <h2 class="no-num no-toc no-ref" id="contents">Table of Contents</h2>
623622
<li><a href="#deep-linking"><span class="secno">3.6</span> <span class="content">Enable Easy Deep Linking</span></a>
624623
</ol>
625624
<li><a href="#template"><span class="secno"></span> <span class="content">Appendix A: Markdown Template</span></a>
625+
<li>
626+
<a href="#boilerplate-user-benefit"><span class="secno"></span> <span class="content">Appendix B: Boilerplate Explanations of User Benefit</span></a>
627+
<ol class="toc">
628+
<li><a href="#accessibility-user-benefit"><span class="secno"></span> <span class="content">Accessibility</span></a>
629+
<li><a href="#authoring-user-benefit"><span class="secno"></span> <span class="content">Ease of Authoring</span></a>
630+
<li><a href="#performance-user-benefit"><span class="secno"></span> <span class="content">Performance</span></a>
631+
<li><a href="#security-user-benefit"><span class="secno"></span> <span class="content">Security</span></a>
632+
</ol>
633+
<li>
634+
<a href="#references"><span class="secno"></span> <span class="content">References</span></a>
635+
<ol class="toc">
636+
<li><a href="#normative"><span class="secno"></span> <span class="content">Normative References</span></a>
637+
<li><a href="#informative"><span class="secno"></span> <span class="content">Informative References</span></a>
638+
</ol>
626639
</ol>
627640
</nav>
628641
<main>
@@ -703,8 +716,12 @@ <h3 class="heading settled" data-level="3.1" id="end-user-need"><span class="sec
703716
even if this requires breaking the “be brief” rule.
704717
For example, see the
705718
<a href="https://github.com/mikewest/deprecating-document-domain/#a-problem">explainer for deprecating <code>document.domain</code></a>,
706-
although even that could perhaps use another sentence
707-
explaining why security boundaries are important for users.</p>
719+
and see <a href="#boilerplate-user-benefit">Appendix B: Boilerplate Explanations of User Benefit</a> for text to
720+
explain why security boundaries are important for users.</p>
721+
<p>Some features are intended to help authors and
722+
have no effect on end-users aside from websites being developed more easily.
723+
If your feature doesn’t cause any harm or benefit to users,
724+
use <a href="#authoring-user-benefit">the boilerplate for ease of authoring</a>.</p>
708725
<h3 class="heading settled" data-level="3.2" id="write-simply"><span class="secno">3.2. </span><span class="content">Write Simply</span><a class="self-link" href="#write-simply"></a></h3>
709726
<p>Use common words to help readers who aren’t native or even fluent English speakers.</p>
710727
<p>Be concise.</p>
@@ -904,5 +921,70 @@ <h2 class="heading settled" id="template"><span class="content">Appendix A: Mark
904921
<c- k>-</c-> [Proposal 3]
905922
<c- k>-</c-> [etc.]
906923
</pre>
924+
<h2 class="heading settled" id="boilerplate-user-benefit"><span class="content">Appendix B: Boilerplate Explanations of User Benefit</span><a class="self-link" href="#boilerplate-user-benefit"></a></h2>
925+
<p>Some classes of features are meant to
926+
help authors achieve some kind of user benefit,
927+
like security, accessibility, or performance,
928+
more easily.
929+
Explainers for these features should say why that general area helps users,
930+
but explainer authors should
931+
spend most of their time explaining why the feature improves the area.
932+
This section provides some boilerplate for some common areas
933+
so that authors don’t need to rewrite it every time.</p>
934+
<h3 class="heading settled" id="accessibility-user-benefit"><span class="content">Accessibility</span><a class="self-link" href="#accessibility-user-benefit"></a></h3>
935+
<blockquote>
936+
<p>This feature is meant to improve website accessibility,
937+
which ensures all users can browse the web,
938+
even if they need to interact with their computers
939+
differently from the majority.</p>
940+
</blockquote>
941+
<h3 class="heading settled" id="authoring-user-benefit"><span class="content">Ease of Authoring</span><a class="self-link" href="#authoring-user-benefit"></a></h3>
942+
<p>End-users come before authors
943+
in the <a href="https://w3ctag.github.io/design-principles/#priority-of-constituencies">priority of constituencies</a>,
944+
so when explaining features designed for authors,
945+
you need to clearly establish that there’s no negative effect on end-users.</p>
946+
<p>For example, <a data-biblio-display="inline" data-link-type="biblio" href="https://drafts.csswg.org/css-nesting/">CSS nesting</a> primarily makes it easier to write stylesheets,
947+
and the potential reduction in file sizes wasn’t measured as part of justifying the feature.
948+
On the other hand,
949+
a feature like <a data-biblio-display="inline" data-link-type="biblio" href="https://w3c.github.io/ppa/">Privacy-Preserving Attribution</a>
950+
isn’t in this category because it does have some negative effect on end-users
951+
(via bandwidth costs and information exposure under its privacy budgets),
952+
so its specification argues that these costs are justified by greater end-user benefits.</p>
953+
<blockquote>
954+
<p>This feature is meant to make it easier to write websites
955+
and to have no negative effects on end-users.
956+
When websites are easier to write,
957+
users get more of them
958+
and don’t need to pay as much (in fees or ads)
959+
to access them.
960+
[If it’s not obvious:]
961+
See <code>&lt;a href="#<var>later-section</var>"></code>below<code>&lt;/a></code>
962+
for an analysis of why the proposed solution doesn’t harm end-users.</p>
963+
</blockquote>
964+
<h3 class="heading settled" id="performance-user-benefit"><span class="content">Performance</span><a class="self-link" href="#performance-user-benefit"></a></h3>
965+
<blockquote>
966+
<p>This feature is meant to improve website performance,
967+
which helps users waste less time waiting
968+
and helps users on low-end devices and slow connections
969+
browse the web at all.</p>
970+
</blockquote>
971+
<h3 class="heading settled" id="security-user-benefit"><span class="content">Security</span><a class="self-link" href="#security-user-benefit"></a></h3>
972+
<blockquote>
973+
<p>This feature is meant to improve website security,
974+
which reduces the frequency of breaches that compromise user data.</p>
975+
</blockquote>
907976
</main>
908-
<script src="https://www.w3.org/scripts/TR/2021/fixup.js"></script>
977+
<script src="https://www.w3.org/scripts/TR/2021/fixup.js"></script>
978+
<h2 class="no-num no-ref heading settled" id="references"><span class="content">References</span><a class="self-link" href="#references"></a></h2>
979+
<h3 class="no-num no-ref heading settled" id="normative"><span class="content">Normative References</span><a class="self-link" href="#normative"></a></h3>
980+
<dl>
981+
<dt id="biblio-design-principles">[DESIGN-PRINCIPLES]
982+
<dd>Martin Thomson; Jeffrey Yasskin. <a href="https://w3ctag.github.io/design-principles/"><cite>Web Platform Design Principles</cite></a>. URL: <a href="https://w3ctag.github.io/design-principles/">https://w3ctag.github.io/design-principles/</a>
983+
</dl>
984+
<h3 class="no-num no-ref heading settled" id="informative"><span class="content">Informative References</span><a class="self-link" href="#informative"></a></h3>
985+
<dl>
986+
<dt id="biblio-css-nesting">[CSS-NESTING]
987+
<dd>Tab Atkins Jr.; Adam Argyle. <a href="https://drafts.csswg.org/css-nesting/"><cite>CSS Nesting Module</cite></a>. URL: <a href="https://drafts.csswg.org/css-nesting/">https://drafts.csswg.org/css-nesting/</a>
988+
<dt id="biblio-privacy-preserving-attribution">[PRIVACY-PRESERVING-ATTRIBUTION]
989+
<dd>Andrew Paseltiner; et al. <a href="https://w3c.github.io/ppa/"><cite>Privacy-Preserving Attribution: Level 1</cite></a>. URL: <a href="https://w3c.github.io/ppa/">https://w3c.github.io/ppa/</a>
990+
</dl>

0 commit comments

Comments
 (0)