-
Notifications
You must be signed in to change notification settings - Fork 70
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
Generate HTML term page(s) from normative document #17
Comments
Perhaps just a stylesheet? Tim,
|
I definitely want a stylesheet, but I'm not sure I understand you completely: do you think the rdf document + stylesheet would be enough to render it in a browser? I know nothing about RDF. 😊 |
It should be enough to render part of some pages, with the rest of the page http://rs.tdwg.org/dwc/terms/index.htm On Wed, Nov 5, 2014 at 8:30 PM, Peter Desmet notifications@github.com
|
we could use an XSLT as it is XML based rdf, but honestly I found that harder to read, maintain and Im not convinced it works fine on all browsers. A simple example are the IPT extensions which reference an XSLT for rendering: http://rs.gbif.org/core/dwc_occurrence.xml |
Fair enough - was just a suggestion. There are some fairly mature static site generators now, which might be worth considering (e.g. they let you do common headers, footers, menus, static pages in MD syntax, and then plug in bits like a transformation of RDF-XML -> HTML). I haven't been involved in the design discussions, so I don't know how much of github TDWG plan to use (e.g. relying on the built in readme.MD transformations) versus just hosting of HTML on pages.github.io . If it is the later, a simple SSG might help, as you're likely to grow your own anyway (e.g. stitching in common headers and basic scaffolding stuff). Disclosure: I've tinkered with SSGs, but not extensively so can't actually point at a preferred one. I'd like to explore assemble.io at some point though, and it looks like a good framework and build pipeline. No RDF->HTML support, but supports handlebar templating so I'd expect a simple template and grunt transformation would be very clean solution. |
FYI, I've listed some SSGs that could be useful in the documentation repository: https://github.com/tdwg/dwc-documentation/issues/3. My preference would go to something simple and not reinventing the wheel. |
A new https://github.com/tdwg/dwc/tree/dwc_cleanup/build folder was created that contains artifacts like yaml files, a cheetah template and the main update_terms.py script. That script now generates the terms/index.html file and all resource files (former downloads). See #68 The term version history is not maintained any longer as an RDF file and will be manually curated as the final html |
The text was updated successfully, but these errors were encountered: