Updates README.md to be more compelling

[Richard-Gist]

Linked Issue:

Checklist:

• Is the linter reporting 0 errors?
• Did you comply with our styleguide?
• Is there adequate test coverage for your new code?
• Does the CI pipeline pass?
• Is the static analysis tool reporting 0 issues?
• Did you update the documentation?
• Did you update the sample app?
• Do we need to increment the minor/major version?
• Did you change the public API?
• Have you done everything you can to make sure that errors that can occur are compile-time errors, and if they have to be runtime do you have adequate tests and documentation around those runtime errors? For more details.

---

If Applicable:

• Did you test when the first item is skipped?
• Did you test when the last item is skipped?
• Did you test when middle items are skipped?
• Did you test when incorrect data is passed forward?
• Did you test proceeding backwards?

---

If Public API Has Changed:

• Did you deprecate (rather than remove) any old methods/variables/etc? Our philosophy for deprecation.
• Have you done the best that you can to make sure that the compiler guides people to changing to the new API? (Example: the renamed attribute)
• If necessary, have you tested the upgrade path for at least N-1 versions? For example, if data persists between v1 and v2 then that upgrade should be tested and as easy as we can make it.

[cla-bot]

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Megan Wiemer.
This is most likely caused by a git client misconfiguration; please make sure to:

1. check if your git client is configured with an email to sign commits git config --list | grep email
2. If not, set it up using git config --global user.email email@example.com
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[Richard-Gist]

EOD: Brought in Wiki files to source so that we can codify the changes. We also improved our tone and voice to be better on brand (more to go).

[Richard-Gist]

EOD: Decided that the original direction of Getting-Started was more suited as a Tutorial and a more slimmed down, succinct version should be used instead.

[Richard-Gist]

Just dropping a note here to run Jazzy again so that it has the updated README for its documentation.

[Tyler-Keith-Thompson]

@Tyler-Keith-Thompson How do you feel about turning these references to Workflow into links to the documentation for Workflow? I'm on the fence since these aren't all specifically calling out the type Workflow, but they are all formatted as code.

I was uncertain at the time myself. I don't have any issues with it per se but this feels like documentation that would be easily overlooked if we changed the name/link

[Richard-Gist]

Someone please create a Change Request to generate Jazzy documentation so we don't forget. I don't want to do it now because it obscures the important changes we made.

EOD: We rechecked our tone compared to what WWT expects in our branding, and revised Installation to match that voice.
We want to help people find the information needed to get started with our project, but we believe other resources will do a better job than this Github page.

[wiemerm]

The commented out gif to be added either make a card or finish it in this. The rest to be fixed.

[wiemerm]

Do the thing it says.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information