Welcome to the scratch_tweeter wiki!

This wiki will serve as a companion to the commit-tutorial style of this repo. If you haven't read the read.me, first, way to follow instructions, but, second, it explains that this repo is structured very much in the style of a tutorial.

How is a Github repo structured as a tutorial you ask?

Well, you may have noticed by now that this repo has a very high number of commits. This is because each commit serves as a mini lesson along the way of creating this app.

Each time a file is generated, tweaked or changed it is accompanied by a ton of comments that explain the reasoning behind the changes.

Now, this commit-tutorial style repo will probably be something pretty cool once I work out the kinks, but I haven't. This project is being built on the fly and unstructured.

That means that after the bulk boilerplating is done, the commits are going to start getting weighed down with every updated colon or syntax correction that is apart of debugging.

At that point, I may branch it or... Well I'm not too sure. Just know that I am aware of the upcoming problems and am going to do what I can to keep the commit as fluid and structured as possible in order to maintain a functional tutorial.

Send me any questions, comments or concerns you may have.