Skip to content
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

Styling hgroup p #408

Merged
merged 2 commits into from
Nov 7, 2022
Merged

Styling hgroup p #408

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
181fc16
Styling hgroup p
annevk Nov 3, 2022
eec3993
Attempt at finishing things off
domenic Nov 4, 2022
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
4 changes: 2 additions & 2 deletions convert_policy.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,11 +34,11 @@ def header_text_to_id(header_text):


def adjust_header(line):
search = re.search(r'<h([2-5])>(.+)</h([2-5])>', line)
search = re.search(r'<h([2-6])>(.+)</h([2-6])>', line)
if not search:
return line

header_level = str(int(search.group(1)) + 1)
header_level = search.group(1)
header_text = search.group(2)
header_id = header_text_to_id(header_text)

Expand Down
2 changes: 1 addition & 1 deletion convert_sg_db.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -85,7 +85,7 @@ def create_workstreams(db, template):
introduction = introduction.replace("<!-- This ends up being included at https://whatwg.org/workstreams -->\n", "")
content = markdown(introduction, obtain_link_mapping())
for workstream in db["workstreams"]:
content += "\n<h3>{}</h3>".format(workstream["name"])
content += "\n<h2>{}</h2>".format(workstream["name"])
content += """\n<dl class="compact">"""
content += "\n <div>"
content += "\n <dt>Scope</dt>"
Expand Down
2 changes: 1 addition & 1 deletion resources.whatwg.org/standard-service-worker.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@

const standardShortname = location.host.split(".")[0];

const cacheKey = "v8";
const cacheKey = "v9";
const toCache = [
location.origin + "/",
"https://resources.whatwg.org/spec.css",
Expand Down
6 changes: 3 additions & 3 deletions resources.whatwg.org/standard.css
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -368,12 +368,12 @@ td.non-rectangular-cell-indentation { border-top-style: hidden; min-width: 2em;
.hide { display: none }

.head { margin: 0 0 1em; padding: 1em 0 0 0; display: block; }
.head p { margin: 0; }
.head p:not(hgroup p) { margin: 0; }
.head h1 { margin: 0 100px 0 0; }
hgroup p { margin: 0 100px 1em 0; }
hgroup p, .head h2 { margin: 0 100px 1em 0; }
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does .head h2 still exist then?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, seems unlikely, not sure why I did that...

@media (max-width: 767px) {
.head .logo img { width: 4em; height: 4em; }
.head h1, hgroup p { margin-right:5rem; }
.head h1, .head h2, hgroup p { margin-right: 5rem; }
}
.head dl { margin: 1em 0; }
p.copyright { font-size: 0.6em; font-style: oblique; margin: 0; }
Expand Down
2 changes: 1 addition & 1 deletion resources.whatwg.org/website-service-worker.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@

*/

const cacheKeyToUse = "v3_" + (self.cacheKey || "v0");
const cacheKeyToUse = "v4_" + (self.cacheKey || "v0");
const everythingToCache = [
"/",
"https://whatwg.org/style/shared.css",
Expand Down
2 changes: 1 addition & 1 deletion site-template.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ <h1>
WHATWG
</a>
</h1>
<h2>@TITLE_GOES_HERE@</h2>
<p>@TITLE_GOES_HERE@</p>
</hgroup>
</header>

Expand Down
2 changes: 1 addition & 1 deletion whatwg.org/404
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@
WHATWG
</a>
</h1>
<h2>File Not Found</h2>
<p>File Not Found</p>
</hgroup>
</header>

Expand Down
2 changes: 1 addition & 1 deletion whatwg.org/410
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@
WHATWG
</a>
</h1>
<h2>Gone</h2>
<p>Gone</p>
</hgroup>
</header>

Expand Down
10 changes: 5 additions & 5 deletions whatwg.org/charter
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@
WHATWG
</a>
</h1>
<h2>Charter (Historical)</h2>
<p>Charter (Historical)</p>
</hgroup>
</header>

Expand All @@ -33,7 +33,7 @@ the WHATWG operates. For a more up to date description read
<a href="/policies">Policies</a>. The text below remains solely for the historical record.</p>

<div id="obsolete-container">
<h3 id="intro">Introduction</h3>
<h2 id="intro">Introduction</h2>

<p id="the-good">Software developers are increasingly using the Web
to deploy their applications. User Agents serve as front ends for
Expand All @@ -52,7 +52,7 @@ the WHATWG operates. For a more up to date description read
Web applications, but these are often designed to address other
needs and only consider Web Applications in a peripheral way.</p>

<h3 id="deliverables">Deliverables</h3>
<h2 id="deliverables">Deliverables</h2>

<p id="address">The goal of the Web Hypertext Applications
Technology Working Group is to address the need for one coherent
Expand Down Expand Up @@ -114,7 +114,7 @@ the WHATWG operates. For a more up to date description read

-->

<h3 id="process">Process</h3>
<h2 id="process">Process</h2>

<p id="list">Working group contributors will contribute to this
activity through a publicly-archived and open-subscription mailing
Expand Down Expand Up @@ -182,7 +182,7 @@ the WHATWG operates. For a more up to date description read
returned to the draft stage to address the issues raised and reasons
for implementation differences.</p>

<h3 id="member">Membership</h3>
<h2 id="member">Membership</h2>

<p id="contributors">Anyone can contribute by subscribing to the <a
href="mailing-list">mailing list</a>. The list of subscribers to the
Expand Down
10 changes: 5 additions & 5 deletions whatwg.org/chat
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@
WHATWG
</a>
</h1>
<h2>Chat</h2>
<p>Chat</p>
</hgroup>
</header>

Expand All @@ -27,19 +27,19 @@
<a href="https://participate.whatwg.org/">Participate</a>
</nav>

<h3 id="chat">Chat<a class="self-link" href="#irc"></a></h3>
<h2 id="chat">Chat<a class="self-link" href="#irc"></a></h2>

<p>We have a <a href="https://app.element.io/#/room/#whatwg:matrix.org">WHATWG</a> room in the <a href="https://en.wikipedia.org/wiki/Matrix_(protocol)">Matrix</a> network. Join us!</p>

<p>Note that if you ask a question, it might take a while to get a reply. It can pay off to stick around for a couple of hours or more.</p>

<p>We are committed to providing a friendly, safe, and welcoming environment for all. So please read the <a href="/code-of-conduct">WHATWG Code of Conduct</a> and respect it when participating in discussions.</p>

<h3 id="getting-started-with-matrix">Getting Started With Matrix<a class="self-link" href="#getting-started-with-matrix"></a></h3>
<h2 id="getting-started-with-matrix">Getting Started With Matrix<a class="self-link" href="#getting-started-with-matrix"></a></h2>

<p>A quick way to get started is by opening the <a href="https://matrix.to/#/#whatwg:matrix.org">WHATWG room launch page</a>, which will prompt you to choose a Matrix client to connect from. Choosing the <a href="https://app.element.io/#/room/#whatwg:matrix.org">Element web app</a> will let you connect to the room right away, directly from your browser. Or you can choose from any of the available <a href="https://matrix.org/clients/">Matrix desktop clients and native mobile apps</a>.</p>

<h3 id="logs">Logs<a class="self-link" href="#logs"></a></h3>
<h2 id="logs">Logs<a class="self-link" href="#logs"></a></h2>

<p>Chat logs can be found in the following places:</p>

Expand All @@ -51,7 +51,7 @@
</ul>


<h3 id="bots">Bots<a class="self-link" href="#bots"></a></h3>
<h2 id="bots">Bots<a class="self-link" href="#bots"></a></h2>

<p>If you want to run a bot, let us know. If they are useful, e.g., providing logging facilities, then they are more than welcome.</p>

Expand Down
42 changes: 21 additions & 21 deletions whatwg.org/faq
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@
WHATWG
</a>
</h1>
<h2>FAQ</h2>
<p>FAQ</p>
</hgroup>
</header>

Expand All @@ -30,9 +30,9 @@
<p><i>See also the
<a href="https://github.com/whatwg/html/blob/main/FAQ.md">HTML Standard FAQ</a>.</i>

<h3 id="the-whatwg">The WHATWG<a class="self-link" href="#the-whatwg"></a></h3>
<h2 id="the-whatwg">The WHATWG<a class="self-link" href="#the-whatwg"></a></h2>

<h4 id="what-is-the-whatwg">What is the WHATWG?<a class="self-link" href="#what-is-the-whatwg"></a></h4>
<h3 id="what-is-the-whatwg">What is the WHATWG?<a class="self-link" href="#what-is-the-whatwg"></a></h3>

<p>The Web Hypertext Application Technology Working Group (WHATWG) is a community of people
interested in evolving the web through standards and tests.
Expand All @@ -48,17 +48,17 @@ these concerns and the Web Hypertext Application Technology Working Group was bo
governance structure for the WHATWG, together forming a
<a href="https://github.com/whatwg/sg">Steering Group</a> to oversee relevant policies.

<h4 id="spell-and-pronounce">How do you spell and pronounce WHATWG?<a class="self-link" href="#spell-and-pronounce"></a></h4>
<h3 id="spell-and-pronounce">How do you spell and pronounce WHATWG?<a class="self-link" href="#spell-and-pronounce"></a></h3>

<p>It is spelled WHATWG, all uppercase, no spaces. It has various pronunciations: what-wee-gee,
what-wig, what-double-you-gee.

<h4 id="what-is-the-whatwg-working-on">What is the WHATWG working on?<a class="self-link" href="#what-is-the-whatwg-working-on"></a></h4>
<h3 id="what-is-the-whatwg-working-on">What is the WHATWG working on?<a class="self-link" href="#what-is-the-whatwg-working-on"></a></h3>

<p>The WHATWG’s focus is on standards implementable in web browsers, and their associated tests.
Our existing work can be seen on the <a href="https://spec.whatwg.org/">standards</a> page.

<h4 id="get-involved">How can I get involved?<a class="self-link" href="#get-involved"></a></h4>
<h3 id="get-involved">How can I get involved?<a class="self-link" href="#get-involved"></a></h3>

<p>There are lots of ways you can get involved! You might want to get started by reviewing
<a href="https://spec.whatwg.org/">the standards</a> and filing issues. You can also browse our
Expand All @@ -72,17 +72,17 @@ Also, feel free to join <a href="/chat">Chat</a> and ask questions of other comm
<a href="https://www.youtube.com/watch?v=hneN6aW-d9w">this video from Domenic Denicola</a> is a
good introduction to working with standards bodies.

<h4 id="is-participation-free">Is participation free?<a class="self-link" href="#is-participation-free"></a></h4>
<h3 id="is-participation-free">Is participation free?<a class="self-link" href="#is-participation-free"></a></h3>

<p>Yes, everyone can contribute. There are no memberships fees involved; it’s an open process. See
our <a href="https://participate.whatwg.org/">participation page</a> for more information.
Participation can be done entirely over the internet; no binding decisions are made during in-person
meetings. That is, decisions made during the odd meeting are tentative and subject to appeal from
those not present.

<h3 id="process">The WHATWG Process<a class="self-link" href="#process"></a></h3>
<h2 id="process">The WHATWG Process<a class="self-link" href="#process"></a></h2>

<h4 id="how-does-the-whatwg-work">How does the WHATWG work?<a class="self-link" href="#how-does-the-whatwg-work"></a></h4>
<h3 id="how-does-the-whatwg-work">How does the WHATWG work?<a class="self-link" href="#how-does-the-whatwg-work"></a></h3>

<p><a href="/working-mode">Working Mode</a> describes the day-to-day process in detail. Most of
the activity consists of <a href="https://github.com/whatwg">collaboration on GitHub</a>.
Expand All @@ -94,7 +94,7 @@ software project, a WHATWG standard undergoes
<a href="https://whatwg.org/working-mode#additions">new features</a>. This work is driven by the
community in collaboration with implementers.

<h4 id="what-happens-with-discussions">What happens in WHATWG GitHub issue discussions?<a class="self-link" href="#what-happens-with-discussions"></a></h4>
<h3 id="what-happens-with-discussions">What happens in WHATWG GitHub issue discussions?<a class="self-link" href="#what-happens-with-discussions"></a></h3>

<p>Much of the time, discussions in the WHATWG are straightforward, with everyone collaborating
on an effort to change the standard <a href="https://whatwg.org/working-mode#changes">according to
Expand All @@ -116,7 +116,7 @@ when they look at the thread. Similarly, as soon as threads start being meta-thr
people’s argumentation behaviour, we stop making any kind of useful progress, since that isn’t
input that can help the decision-making process later.

<h4 id="consensus">Does the WHATWG operate by consensus?<a class="self-link" href="#consensus"></a></h4>
<h3 id="consensus">Does the WHATWG operate by consensus?<a class="self-link" href="#consensus"></a></h3>

<p>The WHATWG strives for rough, informal consensus among contributors when drafting Living
Standards. After considering input from all parties, the editor of a Living Standard makes the
Expand All @@ -127,7 +127,7 @@ Steering Group, which does have a formal consensus policy.
<p>For more information on how decisions are made, see the
<a href="/working-mode">Working Mode</a>.

<h4 id="control">Who controls the WHATWG?<a class="self-link" href="#control"></a></h4>
<h3 id="control">Who controls the WHATWG?<a class="self-link" href="#control"></a></h3>

<p>The community working there. Living Standards are informed by input from contributors, driven
by workstream participants, articulated by editors, and coordinated by the Steering Group. If
Expand All @@ -136,7 +136,7 @@ organizations that develop browser engines, as a backstop to ensure the editor's
with what they will implement. Substantive technical objections are considered and resolved by the
Steering Group, consistent with the <a href="/principles">principles of the WHATWG</a>.

<h4 id="how-to-interact">How should tool developers, screen reader developers, browser vendors, search engine vendors, and other implementers interact with the WHATWG?<a class="self-link" href="#how-to-interact"></a></h4>
<h3 id="how-to-interact">How should tool developers, screen reader developers, browser vendors, search engine vendors, and other implementers interact with the WHATWG?<a class="self-link" href="#how-to-interact"></a></h3>

<p>File an issue on the <a href="https://spec.whatwg.org/">relevant standard</a> as indicated at
the top of that standard. All feedback is supposed to be addressed in due course. You are also
Expand All @@ -148,7 +148,7 @@ feedback, let the editors know by either emailing them, or contacting them on
<a href="/irc">IRC</a>. Requests for priority feedback handling are handled confidentially if
desired so other implementers won’t know that you are working on that feature.

<h4 id="removing-bad-ideas">Is there a process for removing bad ideas from a standard?<a class="self-link" href="#removing-bad-ideas"></a></h4>
<h3 id="removing-bad-ideas">Is there a process for removing bad ideas from a standard?<a class="self-link" href="#removing-bad-ideas"></a></h3>

<p>In general, it is very hard to remove features from the web platform, as implementers are
hesitant to break web pages. Remember that WHATWG standards are intended to align with the reality
Expand All @@ -169,7 +169,7 @@ are the <a href="https://github.com/whatwg/html/pull/1399"><code>applet</code></
removal, which may or may not be successful, is
<a href="https://xhr.spec.whatwg.org/#sync-warning">synchronous <code>XMLHttpRequest</code></a>.

<h4 id="adding-new-features">How should I go about proposing new features to WHATWG standards?<a class="self-link" href="#adding-new-features"></a></h4>
<h3 id="adding-new-features">How should I go about proposing new features to WHATWG standards?<a class="self-link" href="#adding-new-features"></a></h3>

<p>The process is rather informal, but basically boils down to this:

Expand Down Expand Up @@ -242,15 +242,15 @@ removal, which may or may not be successful, is
<p>For more information on the formalized requirements for adding new features, see
<a href="https://whatwg.org/working-mode#additions">our working mode</a>.

<h4 id="should-i-send-new-proposed-text">Should I send new proposed text when I have a suggestion?<a class="self-link" href="#should-i-send-new-proposed-text"></a></h4>
<h3 id="should-i-send-new-proposed-text">Should I send new proposed text when I have a suggestion?<a class="self-link" href="#should-i-send-new-proposed-text"></a></h3>

<p>This is a great idea for grammatical or typographical errors! However, usually, you want to
open an issue first. Although sending a pull request is eventually part of the process, doing so
before discussion with the community and editor(s) can result in wasted work on your part. For
suggestions that are actually new features, this is especially important; see the answer above for
how things usually work.

<h4 id="living-standard">What does “Living Standard” mean?<a class="self-link" href="#living-standard"></a></h4>
<h3 id="living-standard">What does “Living Standard” mean?<a class="self-link" href="#living-standard"></a></h3>

<p>The WHATWG standards are described as Living Standards. This means that they are standards
that are continuously updated as they receive feedback, either from web developers, browser
Expand All @@ -269,7 +269,7 @@ implementations (not just browsers, of course) can do the same thing. Instead of
browsers do, we fix the standard to match what the browsers do. Instead of leaving the standard
ambiguous, we fix the the standard to define how things work.

<h4 id="change-at-any-time">Does that mean the standards can change at any time?<a class="self-link" href="#change-at-any-time"></a></h4>
<h3 id="change-at-any-time">Does that mean the standards can change at any time?<a class="self-link" href="#change-at-any-time"></a></h3>

<p>The standards do not change arbitrarily: we are extremely careful! As parts of a standard
mature, and implementations ship, the standard can generally not be changed in
Expand All @@ -287,7 +287,7 @@ process by which each change to the standard (embodied in a commit) triggers the
frozen snapshot of the said standard. These snapshots are published as historical references. The
WHATWG intends to keep these frozen snapshots available at their published URL permanently.

<h4 id="stable">Doesn't this mean your standards are not stable?<a class="self-link" href="#stable"></a></h4>
<h3 id="stable">Doesn't this mean your standards are not stable?<a class="self-link" href="#stable"></a></h3>

<p>We think of stability for standards in the same way as we do for software. When one says that
software is stable, one doesn't mean that it never changes: one instead means that it evolves
Expand All @@ -298,15 +298,15 @@ Software that is never patched has a low chance of being stable, as bugs sit una
Living Standards are quite stable: they endeavor to eliminate all of their bugs, instead of
leaving them unaddressed.

<h4 id="patent-policy">What’s the patent story for WHATWG standards?<a class="self-link" href="#patent-policy"></a></h4>
<h3 id="patent-policy">What’s the patent story for WHATWG standards?<a class="self-link" href="#patent-policy"></a></h3>

<p>In non-normative layperson's terms: roughly every six months, a Living Standard is
“snapshotted” to create a Review Draft suitable for patent review. All workstream participants, by
virtue of signing the <a href="/ipr-policy">IPR Policy</a>, commit to licensing any essential
claims they may have, unless they exclude those claims within 45 days of the publication of that
snapshot.

<h4 id="translating">What is the process for translating WHATWG standards?<a class="self-link" href="#translating"></a></h4>
<h3 id="translating">What is the process for translating WHATWG standards?<a class="self-link" href="#translating"></a></h3>

<p>Many WHATWG standards have been translated into other languages by the WHATWG community. This
is great, and highly encouraged!
Expand Down
6 changes: 3 additions & 3 deletions whatwg.org/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,12 +23,12 @@
align-items: center;
}

header > hgroup > h1, header > hgroup > h2 {
header > hgroup > h1, header > hgroup > p {
margin: 0;
font-weight: normal;
}

header > hgroup > h2 {
header > hgroup > p {
font-size: 16px;
}

Expand Down Expand Up @@ -146,7 +146,7 @@
<img id="main-logo" crossorigin src="https://resources.whatwg.org/logo.svg" alt>
<hgroup>
<h1>Welcome to the WHATWG community</h1>
<h2>Maintaining and evolving HTML since 2004</h2>
<p>Maintaining and evolving HTML since 2004</p>
</hgroup>
</header>

Expand Down
2 changes: 1 addition & 1 deletion whatwg.org/news/future-of-html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@
WHATWG
</a>
</h1>
<h2>Looking for feedback on HTML5</h2>
<p>Looking for feedback on HTML5</p>
</hgroup>
</header>

Expand Down
4 changes: 2 additions & 2 deletions whatwg.org/news/index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ <h1>
WHATWG
</a>
</h1>
<h2>News</h2>
<p>News</p>
</hgroup>
</header>

Expand All @@ -29,7 +29,7 @@ <h2>News</h2>

<p>For the most up to date news, read the <a href="https://blog.whatwg.org/">WHATWG Blog</a>.</p>

<h3>History</h3>
<h2>History</h2>

<p>The following historical news items were posted before the blog was created:</p>

Expand Down
Loading