Chris Dostert

```yaml name: internal inputs: foo: boolean: ``` after parsing by yaml parser is identical to ```yaml name: internal inputs: foo: string: null dir: null file: null number: null boolean: null...

I guess if we hydrated into a map rather than a struct it could work but then we lose typing; adding implementation complexity... I'm not necessarily convinced having to have...

Thanks for filing! We want to do something to support this use case. An issue that comes with referencing things not in scope in defaults (like env vars of the...

@tallen94 nice, I've been chewing on this too. What about: ```yaml inputs: arraySize: number: run: inputs: arraySize: number: run: if: condition: - lte: [$(arraySize), 1] then: op: ref: ../aws-cmd inputs:...

@gunnarg-remitly How do you see this applying to material that serves multiple audiences? The one I have in mind is reference docs. For sure advanced users will be using it...

> @gunnarg-remitly How do you see this applying to material that serves multiple audiences? The one I have in mind is reference docs. For sure advanced users will be using...

1. If we are only having Reference docs and Training docs; can we not simplify and literally just have a template w/ the boilerplate form of a "Training Doc"? 2....

Personally I think I like the idea of starting with 2 types and then adding more over time if we see value. There's not meaningful difference between guide and tutorial...

example https://github.com/containers/storage/blob/master/pkg/archive/archive.go#L951

@apexskier maybe you'd be interested/willing to take on