Directory structure and naming scheme about gltf-tutorials

[pjcozzi]

Also +1 for HTML. It would be nice to have an md-to-html build step so these could be published on khronos.org or elsewhere.

As for the others, they can probably happen organically as the need arises so we don't over build.

[javagl]

Regarding the HTML: Initially, I used http://markdownpad.com/ for the editing, but the the free version has some limitations (most importantly: No Github-Code-Highlighting), so I now switched to https://atom.io/ . Both editors (as probably most others) allow exporting the MD as HTML, and in doubt, there are standalone tools for this conversion.

The question rather was whether the tutorial should be solely written in HTML, for the increased formatting options (globablly, referring to CSS, and locally, e.g. for defining an image size).

I'll have a look at some of the available tools to see

• whether they support exporting multiple MDs as a set of nicely browsable HTML files
• how well they support "inline HTML"
• whether they can be ran as an automated ("command line") tool

[pjcozzi]

The question rather was whether the tutorial should be solely written in HTML, for the increased formatting options (globablly, referring to CSS, and locally, e.g. for defining an image size).

As the project initiator here, this is up to you. Markdown is so easy to edit that I prefer it even if it limits formatting options. The glTF spec was written in Markdown, with some of it generated from the schema. We are doing the same for the 3D Tiles spec.

[pjcozzi]

@javagl should we keep this open?

[javagl]

We might sooner or later consider exporting this repo or parts of it as standalone (HTML) pages. But for now, I think that MD is fine, considering that navigation/relative links works here as well. So I'll close it, if there are no objections.