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

WG dependent Conformance templates #273

Closed
dirkschulze opened this issue Sep 23, 2013 · 1 comment · Fixed by #2659
Closed

WG dependent Conformance templates #273

dirkschulze opened this issue Sep 23, 2013 · 1 comment · Fixed by #2659
Labels
Milestone

Comments

@dirkschulze
Copy link
Contributor

The conformance section of the CSS WG is significant longer than the predefined one.

Is it for example possible to upload the template for the CSS WG, which is just chosen when one of the WG strings in the meta data section is CSS Working Group or SVG Working Group for instance?

@darobin
Copy link
Member

darobin commented Sep 23, 2013

That's not a feature that's currently supported, and while I'm sympathetic with the idea I also hesitate to add too much stuff that's WG-specific. I'm also not sure that I like the idea of supporting WGs in adding their own boilerplate on top of the already-excessive amount that the W3C imposes (e.g. a Note pointed to by all documents would be better).

One option that could work assuming you always edit using a local web server that's pointing to the root of a directory shared by multiple specs from the same group is to use data-include.

Say for instance you're in the Cryptozoology WG and every conformance section starts with a lot of boilerplate, you could have:

/cryptozoology/conformance-template.html
/cryptozoology/your-spec/index.html
/cryptozoology/some-other-spec/index.html

And then in those spec documents, use:

<div data-include="../conformance-template.html"></div>

To include the boilerplate at that point.

@darobin darobin added this to the v4 milestone Dec 23, 2014
shikhar-scs pushed a commit to shikhar-scs/respec that referenced this issue Feb 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants