Improved ftrack admin docs

[Dreamink-Official]

Changelog Description

I found it challenging to set up the connection between AYON and Ftrack. To address this, I enhanced the documentation in my PR to make it more precise.

[MustafaJafar]

Hello @Dreamink-Official,
Thank you for your contribution.

---

Generally speaking,
I think the ftrack docs needs an overhaul. e.g. Ftrack credentials in the Login section is pointing to ayon kitsu addon docs.

Also, the ftrack badge is referring to 0.2.4 version while the current version is 1.2.2.

For information, I've started creating issues for updating different addon docs like this one for deadline
#264

---

Notes for your PR:
The current workflow is to create an issue (from here) and add some bullet points about things to change.

Next step: to create branch to apply your fix, it's recommended to use a descriptive name e.g. improve-ftrack-docs
Then you push that and create a PR.

[Dreamink-Official]

Hey @MustafaJafar, thanks for highlighting additional areas in the docs that need improvement! I've created an issue (#306) and included the points you mentioned.

If you come across anything else that could be improved, feel free to reach out anytime!

By the way, is this workflow—creating an issue and linking the PR to it—standard across all AYON repositories, or is it specific to the documentation repo?

[MustafaJafar]

Hey @MustafaJafar, thanks for highlighting additional areas in the docs that need improvement! I've created an issue (#306) and included the points you mentioned.

If you come across anything else that could be improved, feel free to reach out anytime!

Thank you for your contribution.

By the way, is this workflow—creating an issue and linking the PR to it—standard across all AYON repositories, or is it specific to the documentation repo?

yes, it's standard across all AYON repos.