Determine approach for steps in guides

[TheDutchCoder]

Decide how to handle the steps within each guide

[TheDutchCoder]

@skipjack I was wondering if we should just include the "starter files" for each guide, or also all the intermediate "steps".

I'm leaning towards just the starter files, so that people can follow along and adjust the code themselves, might be beneficial for them to input actual code and see the result.

What do you think?

[skipjack]

@TheDutchCoder agh sorry for such a delayed response.

I was wondering if we should just include the "starter files" for each guide, or also all the intermediate "steps".

I'm leaning towards just the starter files, so that people can follow along and adjust the code themselves, might be beneficial for them to input actual code and see the result.

I'm a little confused what you mean here... by "steps" you mean should we include each a version of each file (or patch files) to replicate every step in the guide? If that's what you mean then no, I think I agree with you -- imo we should just include what the final example should look like (e.g. when the user has reached the end of the guide). In my mind, these examples should just prove that what we've put together in the guide works and they should be linked to at the bottom of the guide for reference.

Ideally people will complete the guide/example creation on their own and only use these if to test against or to see what went wrong in their version.

[TheDutchCoder]

@skipjack hmm, interesting idea to include the "final "files.

Currently I've set the repo up to include the starting point instead, but maybe we can split them up into "start" and "end" or something, so that people can check if they followed the guides correctly.

I think it's a good idea to link people to the "end state" so they can check their work, I like that idea.

Would you recommend linking to the start files at the start of each guide and link to the end files at the bottom? Or only link to the end files?

[skipjack]

Currently I've set the repo up to include the starting point instead, but maybe we can split them up into "start" and "end" or something, so that people can check if they followed the guides correctly.

Ah interesting, I was just thinking end state but I guess that makes sense. FYI the ones I've submitted do represent the end state.

Would you recommend linking to the start files at the start of each guide and link to the end files at the bottom? Or only link to the end files?

Actually now that I think about it... except for Getting Started most of the start states are actually just the end states of previous guides. So maybe way can get away with mostly end states except in a few cases?