Index settings tutorials

[guimachiavelli]

Closes #2634.

Instead of the two options listed in the issue, I have opted for creating a short tutorial using the Cloud interface. This solves the issue of documenting an increasing number of interface elements with almost identical usage.

Since many users will prefer to use the API instead of the interface, this guide also adds a second tutorial teaching users to do the exact same thing with the API.

Notes for reviewers

• @Strift: as usual, all feedback is welcome, but if you're short on time my main request is that you take a look at the fathom URL params and see if they align with how dev rel is handling them.

[meili-bot]

How to see the preview of this PR?

⚠️ Private link, only accessible to Meilisearch employees.

Go to this URL: https://website-git-deploy-preview-mei-16-meili.vercel.app/docs/branch:cloud-index-settings

Credentials to access the page are in the company's password manager as "Docs deploy preview".

[Strift]

The UTMs parameters are correct. 👌

You can add in the UTM tracking sheet to document it.

Regarding the content, I think we should not encourage API usage. The API should be seen as a fallback—a way to convey that Meili works with any stack.

Instead, I think we should demonstrate that Meilisearch integrates easily with our ICP stack via the following options:

1. Via the UI (less tech work to do)
2. Via the JavaScript SDK (target ecosystem n°1)
3. Via the PHP SDK (target ecosystem n°2)
4. Other options

I hope this helps!

[guimachiavelli]

Thanks for the feedback, @Strift!

I'm interested on the product team feedback on this too, but for the moment I want to clarify a few things.

If I understand correctly, by API you mean curl, right? If that's the case, no need to worry. I left the code samples in code blocks so it's easier to see them in context, but once I get the ok from the technical reviewers I will move them to the code samples component and notify integrations we need new samples for JS and PHP (and potentially other SDKs, eventually). curl will remain available as an option because we still want users to follow along without having to set up a whole environment.

[Strift]

Great. I think we'll have to handle the code samples ourselves since there isn't an integration team anymore. :p

[macraig]

LGTM!