Skip to content

Annotation sidebar to the sample spec #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: gh-pages
Choose a base branch
from
Open

Annotation sidebar to the sample spec #9

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions index.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ Introduction</h2>

A lot can get in the way of writing a good specification. The formalism, while necessary, can
inhibit creativity and eat up precious time.

WebSpecs use a specific variant of Markdown called "Bikeshed" (after the famous
<a href="https://en.wikipedia.org/wiki/Parkinson%27s_law_of_triviality">Parkinson law of triviality</a>
which is commonly known as "bikeshedding" in the standards world). It does a lot of things for
Expand All @@ -25,7 +25,7 @@ Exemplify</h3>
<div class='example'>
Examples can be included at any time, and here we have a great specimen, even given its own
subsection.

<pre>#webspecs { will-change: all; }</pre>
</div>

Expand All @@ -49,3 +49,5 @@ Element Definitions</h2>
<div class='note'>
This includes generating the right <code>dfn</code> elements, table of elements, etc.
</div>

<script src="https://notes.webplatform.org/embed.js" async defer></script>