🚀 Feature: Store Algolia Config in Source Code

[aramissennyeydd]

🔖 Feature description

Currently, the config is stored in crawler.algolia.com/.../configuration/edit. There are some limitations there:

1. Algolia expects a single constructor as the content of the editor, you can't easily separate out functions + other things.
2. Changes are questionably versioned.
3. Requires Admin access to make changes.

🎤 Context

Make it easier to make changes to the Algolia config.

✌️ Possible Implementation

Following this, we could explore inverting control of page rank + other algolia parameters to be part of each docs' front matter.

👀 Have you spent some time to check if this feature request has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

Are you willing to submit PR?

None

[jhaals]

Sounds good to have this in code instead of the UI 👍 Is there a guide on how to migrate?

[aramissennyeydd]

@jhaals It looks like we'd need to use the https://www.algolia.com/doc/rest-api/crawler/#tag/config/operation/patchConfig API to update the configuration. I don't see a full guide on a migration though.

[jhaals]

Oh I see. In that case I think we need to craft a github action that push changes as they come in. A bit limited on capacity to work on this and to my knowledge we only changed the ranking like once or twice in the last three years. Is there something that should be changed now? Happy to dump the config we have now and do a manual update if there are something specific that should be fixed.