Docs could use extended info to implement tasks fully supporting the files selector.

[Bartvds]

The documentation on how to configure tasks and specify the files filter options is excellent but there is no counterpart for it in the creating tasks section, which has does have good info on the basics of building tasks but skips over using the selected files.

It's a bit odd as everything else is very specced out and the selector options and filters are very powerful feature to leverage.

Now we have to root through the contrib tasks and find one which works similar to what we try to do and just voodoo-cargo-cult it cross referenced with the fragmented info that exists until it starts to makes sense.

For me as grunt n00b there seems to be a few common scenario's that could be covered: the read-only scenario (only using src's), the conversion scenario (multiple src's in, multiple dest's out) and a concat scenario (multiple src's in, single dest out).

If I look at the existing plugins there seems to be a lot of different ways with expansions and filters and nested loops over getters, even in the contrib tasks. For example grunt-contrib-copy does a lot of stuff more then others would and it's hard to grasp why.

Looking at non contrib plugins I might not be the only one who makes a mess and doesn't support cwd and flatten properly so it might be an improvement if a veteran could add some quality demo code to the project.

[JKVeganAbroad]

Just to clarify, you're requesting more comprehensive documentation on ONE of the following things:

1. Creating your own Gruntfile.js task plugin (e.g. Creating an open-source grunt task to release to the world)
2. Creating your own task embedded within the Gruntfile.js file itself (e.g. Creating a very specific task tailored to your specific project)

@Bartvds, Would you be able to clarify which of the above things you were requesting about?