Success! +I’m the right file to include, +nested one folder deep, +not two!
+diff --git a/bikeshed/boilerplate/whatwg/computed-metadata-LS-COMMIT.include b/bikeshed/boilerplate/whatwg/computed-metadata-LS-COMMIT.include new file mode 100644 index 0000000000..c37680545b --- /dev/null +++ b/bikeshed/boilerplate/whatwg/computed-metadata-LS-COMMIT.include @@ -0,0 +1,16 @@ +{ + "Title": "[SPECTITLE] Standard Commit [COMMIT-SHA] Snapshot", + "Logo": "https://resources.whatwg.org/logo-[SHORTNAME]-snapshot.svg", + "!Participate": [ + "GitHub whatwg/[SHORTNAME] (new issue, open issues)", + "IRC: #whatwg on Freenode" + ], + "!Commits": [ + "GitHub whatwg/[SHORTNAME]/commits", + "Go to the living standard", + "@[TWITTER]" + ], + "!Tests": "web-platform-tests [SHORTNAME]/ (ongoing work)", + "Warning": "obsolete", + "Text Macro": "H1 [SPECTITLE] (Commit [COMMIT-SHA])" +} diff --git a/bikeshed/boilerplate/whatwg/computed-metadata-LS-PR.include b/bikeshed/boilerplate/whatwg/computed-metadata-LS-PR.include new file mode 100644 index 0000000000..c99137b7b7 --- /dev/null +++ b/bikeshed/boilerplate/whatwg/computed-metadata-LS-PR.include @@ -0,0 +1,16 @@ +{ + "Title": "[SPECTITLE] Standard Pull Request #[PR-NUMBER] Preview", + "Logo": "https://resources.whatwg.org/logo-[SHORTNAME]-snapshot.svg", + "!Participate": [ + "GitHub whatwg/[SHORTNAME] (new issue, open issues)", + "IRC: #whatwg on Freenode" + ], + "!Commits": [ + "GitHub whatwg/[SHORTNAME]/commits", + "Go to the living standard", + "@[TWITTER]" + ], + "!Tests": "web-platform-tests [SHORTNAME]/ (ongoing work)", + "Warning": "custom", + "Text Macro": "H1 [SPECTITLE] (PR #[PR-NUMBER])" +} diff --git a/bikeshed/boilerplate/whatwg/computed-metadata-RD.include b/bikeshed/boilerplate/whatwg/computed-metadata-RD.include index deb5507cdd..aa2183790a 100644 --- a/bikeshed/boilerplate/whatwg/computed-metadata-RD.include +++ b/bikeshed/boilerplate/whatwg/computed-metadata-RD.include @@ -1,4 +1,5 @@ { "Title": "[SPECTITLE] Standard Review Draft [DATE-MMY]", - "Logo": "https://resources.whatwg.org/logo-[SHORTNAME]-snapshot.svg" + "Logo": "https://resources.whatwg.org/logo-[SHORTNAME]-snapshot.svg", + "Text Macro": "H1 [SPECTITLE]" } diff --git a/bikeshed/boilerplate/whatwg/computed-metadata.include b/bikeshed/boilerplate/whatwg/computed-metadata.include index 77ae6886e1..4a7d81a73c 100644 --- a/bikeshed/boilerplate/whatwg/computed-metadata.include +++ b/bikeshed/boilerplate/whatwg/computed-metadata.include @@ -7,8 +7,9 @@ ], "!Commits": [ "GitHub whatwg/[SHORTNAME]/commits", - "[SNAPSHOT-LINK]", + "Snapshot as of this commit", "@[TWITTER]" ], - "!Tests": "web-platform-tests [SHORTNAME]/ (ongoing work)" + "!Tests": "web-platform-tests [SHORTNAME]/ (ongoing work)", + "Text Macro": "H1 [SPECTITLE]" } diff --git a/bikeshed/boilerplate/whatwg/header-RD.include b/bikeshed/boilerplate/whatwg/header-RD.include index ae76e6e046..d521ea1458 100644 --- a/bikeshed/boilerplate/whatwg/header-RD.include +++ b/bikeshed/boilerplate/whatwg/header-RD.include @@ -10,7 +10,9 @@
To the extent possible under law, the editors have waived all copyright +and related or neighboring rights to this work. +In addition, as of 1 January 1970, +the editors have made this specification available under the Open Web Foundation Agreement Version 1.0, +which is available at http://www.openwebfoundation.org/legal/the-owf-1-0-agreements/owfa-1-0. +Parts of this work may be from another specification document. If so, those parts are instead covered by the license of that specification document.
+Success! +I’m the right file to include, +nested one folder deep, +not two!
+Conformance requirements are expressed with a combination of descriptive assertions and RFC 2119 terminology. + The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” + in the normative parts of this document + are to be interpreted as described in RFC 2119. + However, for readability, + these words do not appear in all uppercase letters in this specification.
+All of the text of this specification is normative + except sections explicitly marked as non-normative, examples, and notes. [RFC2119]
+ Examples in this specification are introduced with the words “for example”
+ or are set apart from the normative text with class="example"
, like this:
Informative notes begin with the word “Note”
+ and are set apart from the normative text with class="note"
, like this:
Note, this is an informative note.
+To the extent possible under law, the editors have waived all copyright +and related or neighboring rights to this work. +In addition, as of 1 January 1970, +the editors have made this specification available under the Open Web Foundation Agreement Version 1.0, +which is available at http://www.openwebfoundation.org/legal/the-owf-1-0-agreements/owfa-1-0. +Parts of this work may be from another specification document. If so, those parts are instead covered by the license of that specification document.
+Failure! +I’m nested two deep, +so the only way to reach me is if the nested include’s path +was resolved relative to its own location, +rather than the parent doc’s location!
+Conformance requirements are expressed with a combination of descriptive assertions and RFC 2119 terminology. + The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” + in the normative parts of this document + are to be interpreted as described in RFC 2119. + However, for readability, + these words do not appear in all uppercase letters in this specification.
+All of the text of this specification is normative + except sections explicitly marked as non-normative, examples, and notes. [RFC2119]
+ Examples in this specification are introduced with the words “for example”
+ or are set apart from the normative text with class="example"
, like this:
Informative notes begin with the word “Note”
+ and are set apart from the normative text with class="note"
, like this:
Note, this is an informative note.
+To the extent possible under law, the editors have waived all copyright +and related or neighboring rights to this work. +In addition, as of 1 January 1970, +the editors have made this specification available under the Open Web Foundation Agreement Version 1.0, +which is available at http://www.openwebfoundation.org/legal/the-owf-1-0-agreements/owfa-1-0. +Parts of this work may be from another specification document. If so, those parts are instead covered by the license of that specification document.
+Failure! +I’m nested two deep, +so the only way to reach me is if the nested include’s path +was resolved relative to its own location, +rather than the parent doc’s location!
+Conformance requirements are expressed with a combination of descriptive assertions and RFC 2119 terminology. + The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” + in the normative parts of this document + are to be interpreted as described in RFC 2119. + However, for readability, + these words do not appear in all uppercase letters in this specification.
+All of the text of this specification is normative + except sections explicitly marked as non-normative, examples, and notes. [RFC2119]
+ Examples in this specification are introduced with the words “for example”
+ or are set apart from the normative text with class="example"
, like this:
Informative notes begin with the word “Note”
+ and are set apart from the normative text with class="note"
, like this:
Note, this is an informative note.
+To the extent possible under law, the editors have waived all copyright +and related or neighboring rights to this work. +In addition, as of 1 January 1970, +the editors have made this specification available under the Open Web Foundation Agreement Version 1.0, +which is available at http://www.openwebfoundation.org/legal/the-owf-1-0-agreements/owfa-1-0. +Parts of this work may be from another specification document. If so, those parts are instead covered by the license of that specification document.
+This first include should fail—
Failure! +I’m nested two deep, +so the only way to reach me is if the nested include’s path +was resolved relative to its own location, +rather than the parent doc’s location!
+This second include should work, +and report success:
+Failure! +I’m nested two deep, +so the only way to reach me is if the nested include’s path +was resolved relative to its own location, +rather than the parent doc’s location!
+Conformance requirements are expressed with a combination of descriptive assertions and RFC 2119 terminology. + The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” + in the normative parts of this document + are to be interpreted as described in RFC 2119. + However, for readability, + these words do not appear in all uppercase letters in this specification.
+All of the text of this specification is normative + except sections explicitly marked as non-normative, examples, and notes. [RFC2119]
+ Examples in this specification are introduced with the words “for example”
+ or are set apart from the normative text with class="example"
, like this:
Informative notes begin with the word “Note”
+ and are set apart from the normative text with class="note"
, like this:
Note, this is an informative note.
+