Improves import and installation documentation

morganzellers commented 3 years ago

Linked Issue:

Checklist:

[x] Is the linter reporting 0 errors?
[x] 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?
[x] 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.

NOTES from card that created this: Document SPM import in Onboarding Docs

Add imports for pods and spm to Installation determine how to address package managers/imports in Getting Started

morganzellers commented 3 years ago

Lots of whitespace changes in the first commit - my Markdown preview VSCode extension came with a linter, and it suggested these. I'm happy to undo if we don't want em!

morganzellers commented 3 years ago

EOD: Updated Installation.md to contain instructions for importing Workflow in the following situations: