Inference documentation improvements

[capjamesg]

Description

This PR contains several improvements to the Inference documentation.

The philosophy for this change maps to our strategy to be Workflows-first. Running a model should be a one-block Workflow. Users should be able to build complex, multi-stage Workflows as easily as possible.

The following changes have been made:

• The Start section has been re-written and refactored. The goal is to get someone to a trained model as fast as possible. With this in mind, the introduction material is now condensed into one page, and the second link on the page is a new quickstart tutorial that gets someone using Workflows on images and their webcam in five minutes.

• A new Tutorials tab lists tutorials from our blog. These are programmatically retrieved based on tags from the Roboflow blog when the documentation site is built. This means the marketing team can add tags in their same publishing platform and have the post show up on the relevant Inference docs page when the documentation site is next built.

• Workflow Blocks documentation pages now link to tutorials, also programmatically retrieved from Ghost and manually set via tag by the marketing team.

• Documentation that was reference but not named as such has been moved to the Reference section.
• Documentation for running models via the SDK has been moved to the Reference section. We should encourage users to add models as Workflow blocks rather than running via the SDK since running in Workflows gives them access to the 100+ blocks we have made.

Type of change

• Documentation update

How has this change been tested, please provide a testcase or example of how you tested the change?

This change can be tested by running mkdocs serve and clicking around.

Any specific deployment considerations

We need to set a GHOST_API_KEY constant in our Actions secrets so the docs build can pull the latest posts from the Roboflow blog that have been marked as tutorials.

Docs

N/A

[PawelPeczek-Roboflow]

I like the changes so far, @capjamesg lmk when done

[hansent]

first link on getting started page goes to non exitent page

[hansent]

this link 404s

[hansent]

I pushed a commit to fix the links to the install / setup page and add the download buttons to it. I also updated the redirect on the /download page that is used from the app to go to the setup page.

I'm a bit worried we might have to go through and check all of the links though. At least there seems to be a ton of relative links that don't work. Like all the links that are just /some/route/ for the destination don't work for (they open a new tab and then some of them load some of them don't. I think we may need to link directly to md files like e.g. /some/route.md instead (at least thats what I did for the setup links. Maybe thats only an artifact of when I run it locally? Maybe we should give it a closer comb over to make sure the links all work before mergin the docs PR?

[grzegorz-roboflow]

@capjamesg , I only noticed, can you sign your commits?

[hansent]

@capjamesg are these still desired updates? the merge conflicts are blocking I think