docs: "user guide" section cleanup

[zilto]

Changes

• Renamed the section from "How To Guides" to "User Guide".
• Changed the title of "User Guide" pages to be easier to visually scan. Essentially, this consists of shorter titles with the most important word at the beginning
• changed the order of user guide items
• updated the list of integrations

Before:

After:

How I tested this

• build docs locally

Notes

Checklist

• PR has an informative and human-readable title (this will be pulled into the release notes)
• Changes are limited to a single goal (no scope creep)
• Code passed the pre-commit check & code is left cleaner/nicer than when first encountered.
• Any change in functionality is tested
• New functions are documented (with a description, list of inputs, and expected output)
• Placeholder code is flagged / future TODOs are captured in comments
• Project documentation has been updated if adding/changing functionality.

[skrawcz]

To me the purpose of the how-to section is for goal oriented people - "I want to do X with Hamilton" where X is a broad concept -- while the integrations section is when X is a specific narrower technology/topic.

So I think the changes mostly look good. Left comments where appropriate.

[zilto]

To me the purpose of the how-to section is for goal oriented people - "I want to do X with Hamilton" where X is a broad concept -- while the integrations section is when X is a specific narrower technology/topic.

I agree on the purpose of the "how-to" / "user guide" section. I believe "User guide" pages should mirror frequent Q/A on Slack. Pages on "Feature engineering", "pre-commit", "jupyter notebooks" are good examples.

Many of the current pages are too introductory / generic. In that case, it should be reframed to be part of the "Concepts" section (e.g., "Load data" doesn't add much compared to the materialization page).