Update the Getting started docs to use pyflyte init

[eapolinario]

This is the corresponding changes to the Getting Started docs in order to reflect the introduction of cookiecutter templates in flytekit.

This should only be merged after we cut the new flytekit release.

The Getting started docs now look like: https://flyte--1801.org.readthedocs.build/en/1801/getting_started.html

Signed-off-by: Eduardo Apolinario [email protected]

[kumare3]

here is where we can add a comment saying, myflyteapp or your own app name?

[kumare3]

should we also say, it uses cookie-cutter underneath?

[eapolinario]

the paragraph right above mentions the choice of myflyteapp. I'll make it more explicit that it's actually part of the invocation (and that the user is free to pick whatever name they want).

As for letting them know that it's using cookie-cutter, do you really think it's needed? From a beginner user perspective they shouldn't need to know that it uses this or that templating engine. WDYT?

[eapolinario]

We can trust that the users that want to know what's going on under the covers will find out about cookie-cutter from the cli itself:

❯ pyflyte init --help
...
Usage: pyflyte init [OPTIONS] PROJECT_NAME

  Create flyte-ready projects.

Options:
  --template TEXT  cookiecutter template folder name to be used in the repo -
                   https://github.com/flyteorg/flytekit-python-template.git

  --help           Show this message and exit.