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.

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

Dev edition: add introduction, plus various tweaks #2837

Merged
merged 2 commits into from
Jul 14, 2017
Merged

Conversation

domenic
Copy link
Member

@domenic domenic commented Jul 13, 2017

  • Adds an "About this specification" introduction, like the previous
    version had. Closes Dev edition: add "about this specification" #2780.
  • Fixes the header logo positioning; the recent introduction of the
    search box in cfb8b9e made the title
    spill onto multiple lines, causing the logo to no longer be centered.
  • Changes the <title> to "HTML Standard, Developer's Edition" to
    distinguish it better from the full standard. Make <title> element content use split heading content wattsi#50 remains
    open for making the <title> more useful in general.
  • Adds the full standard's favicon to the developer's edition too.
  • Removes the useless Google fonts download, as we ended up deciding to
    serve Droid Serif ourselves.

* Adds an "About this specification" introduction, like the previous
  version had. Closes #2780.
* Fixes the header logo positioning; the recent introduction of the
  search box in cfb8b9e made the title
  spill onto multiple lines, causing the logo to no longer be centered.
* Changes the <title> to "HTML Standard, Developer's Edition" to
  distinguish it better from the full standard. whatwg/wattsi#50 remains
  open for making the <title> more useful in general.
* Adds the full standard's favicon to the developer's edition too.
* Removes the useless Google fonts download, as we ended up deciding to
  serve Droid Serif ourselves.
@domenic domenic force-pushed the dev-edition-about branch from 87df37a to c8c5680 Compare July 14, 2017 00:10
source Outdated
developer, in mind.</p>

<p>The focus of this specification is readability and ease of access. Unlike the <a
href="/multipage">full HTML Standard</a>, this "developer's edition" removes information that only
Copy link
Member

Choose a reason for hiding this comment

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

Make that /multipage/ to avoid a needless redirect.

source Outdated

<p>The focus of this specification is readability and ease of access. Unlike the <a
href="/multipage">full HTML Standard</a>, this "developer's edition" removes information that only
browser vendors need know. It is automatically produced from the full specification by our build
Copy link
Member

Choose a reason for hiding this comment

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

full specification -> HTML Living Standard?

Copy link
Member Author

Choose a reason for hiding this comment

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

I thought that might be confusing, as the developer's edition has a large h1 of "HTML: The Living Standard", with a h2 subtitle of "Developer's Edition"

Copy link
Member

Choose a reason for hiding this comment

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

Okay, I think we might need to rebrand somehow that since we don't want both of them to be standards.

Copy link
Member Author

Choose a reason for hiding this comment

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

I mean, both the multipage edition and the singlepage edition are still branded as the HTML Standard; I think it's reasonable for the dev edition too.

Copy link
Member

Choose a reason for hiding this comment

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

It seems a tad different, but I'm okay with leaving this as-is for now.

@domenic domenic merged commit 85e81a6 into master Jul 14, 2017
@domenic domenic deleted the dev-edition-about branch July 14, 2017 18:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

2 participants