I think the schema section of the documentation is less clear now

[etienne-monier]

Hi,

Warning: This is not a "that was better before" post. I just want to provide a user experience for the good of everyone. Someone else could share the same experience.

I just want to point out a need the Schema reference do not address any more.

This section was awesome to quickly navigate among the YAML structure of the Taskfile. Its global usage is defined in the guide section and the schema aimed at providing a quick way to know what fields an interface accepted. For an interface, all possible fields were listed. This was a great complement to the usage guide.

The new schema guide is ... more a guide than a reference. It provides a lots of use cases, but do not provide fast way to get the Taskfile format. Two comments:

• e.g. in the includes key, the type is written to be map[string]Include, but there is no more link to get to the Include schema. I need to get to this definition, which is more slow.
• Before I wrote this post, I wanted to know how to write a command which uses another task. The documentation now provides a list of use case and I found the desired use case, but I wanted to know if I needed another key in the data structure, which I couldn't.

To sum up, I find this documentation less natural than it was to get the Taskfile structure.

I just wanted to point out an amazing reference: The documentation system

In the reference page, I read:

By all means technical reference can contain examples to illustrate usage, but it should not attempt to explain basic concepts, or how to achieve common tasks.

Reference material should be simple and to the point.

Have a nice day :)