Improve Documentation for Creating Third-Party Providers

This MR is 148 commits behind the upstream repository, and adds an AI Provider within the AI module structure: AI Providers should now be separate projects of their own (see https://www.drupal.org/project/openai → as an example) and all the providers within the codebase are deprecated.

I think this should be reworked to meet the issue raised (improve documentation) and remove any changes not related to that (implementing a new provider).

Thank you for the feedback @mrdalesmith

The dropai_provider included, is not actually a provider, but an example module for the fictional provider explained in the documentation and the files are linked there. My motivation was that ic can help other developers and can be used as a starter code to build new providers.

Alternatively, I can create a separate project and put that module there.

Hi Giorgi - thank you for the documentation. As @mrdalesmith writes, we should not have it in visible modules directory. The providers and vdb_providers folders will be removed completely before the prod version is released.

if we want an example module, I think you can put it under docs/examples.

Another option is under tests/modules - we already have a provider module there for testing, but having one to showcase how it works as well would be all ok. I've seen that's how they do things with Experience Builder as well.

You should also add "hidden: true" in the info.yml just to make sure it doesn't show up, but modules under tests or docs should not show up anyway.

@marcus_johansson @mrdalesmith

Thanks, it makes sense- moved module under docs/examples.

Your branch is still way behind so the tests aren't running: you need to update the fork and rebase your branch so this can be reviewed properly.

Thank you Giorgi, merged.

Automatically closed - issue fixed for 2 weeks with no activity.

Issue cleanup per 📌 Unassign closed AI issues and update issue metadata Active