Jazzy docs

[xtopolis]

Before you make a Pull Request, read the important guidelines:

Issue Link 🔗

• Is this a bug fix or a feature? **Feature**
• Does it break any existing functionality? **Unit Tests still pass**

Goals of this PR 🎉

• Why is the change important? hacktoberfest
• What does this fix? Add Jazzy Documentation #58
• How far has it been tested? N/A
• Remove docs/ from gitignore
• This is where the magic happens: .jazzy.yaml
• Preview: https://cardparts.surge.sh

How Has This Been Tested 🔍

Please let us know if you have tested your PR and if we need to reproduce the issues. Also, please let us know if we need any relevant information for running the tests.

• N/A

Test Configuration 👾

• Xcode version: 10.3

Things to check on 🎯

• My Pull Request code follows the coding standards and styles of the project
• [N/A] I have worked on unit tests and reviewed my code to the best of my ability
• I have used comments to make other coders understand my code better
• My changes are good to go without any warnings
• [N/A] I have added unit tests both for the happy and sad path
• All of my unit tests pass successfully before pushing the PR
• I have made sure all dependent downstream changes impacted by my PR are working

[xtopolis]

@croossin Need to do a little review, but it's at 100% documentation. A lot of it is redundant property name, or self explanatory property comments. Anything else you'd like done?

[xtopolis]

Ready for any final comments and whether or not I should add in build step or leave it to you.

[croossin]

Would be awesome to have as a build step @xtopolis - but how much of a lift is that?

[croossin]

@xtopolis Is it hard to get this in the build pipeline?

[xtopolis]

I'll be able to look into it by end of week/this weekend, sorry for the delay.

[xtopolis]

@croossin Merge away if ready