Include Schema Documentation about project-helix.io HOT 5 CLOSED

+1 for your implementation proposal of 4 for now.

Whatever we do, the resolution will have to somehow end up into the VCL (determine if template selector or content file name).

When we hlx publish can't we just build the list of known template selectors and add it to the dynamic.vcl. When parsing the request, if the selector is not in that list, than consider as part of content file name.

from project-helix.io.

DO you have a preference for 2 or 3?

2 could look like this:

strains:
  - name: default
    selectors:
      - nav
      - video

from project-helix.io.

oh sorry if this was not clear, I think it should be automatic, i.e. no extra config! You can compute this list based on the list of templates in the project folder and fallback to content if the selector is not part of this list.
Thus I assume this is 3 (but without a lookup, list is pre-computed on publish).

from project-helix.io.

Ah, inspecting the available templates is a good idea. We just have to find a way to carry that information forward.

from project-helix.io.

That was my initial proposal: generate a list in dynamic.vcl (or a dedicated file for that). If selector in the list, use as template, otherwise append to content path. Something like that ;)

from project-helix.io.