Contrib.social

AI KR4 - AI Installer works for the ambitious sitebuilder

Open on Drupal.org →
Created on 12 November 2024, 5 months ago

Problem/Motivation

The current approach to getting AI setup is quite complicated for someone who will eventually want AI help them perform relatively simple Drupal config tasks such as adding a field. It requires to sign up for an AI provider go to the keys module, add a key, go to a provider, add the key to it, set some default models. Then the AI Agents will work.

We ideally would like to improve the install process to make it easier to get started with AI right away.

Proposed resolution

Different Approaches.

  • We can make it easier in the Drupal CMS install to choose if you want AI or not. If you do, you can choose a provider and then put the API key in before Drupal is fully set up. This will guarentee the AI features are working as they should.
  • We could create a task within a dashboard to do the above steps. It means the user might get confused if AI isn't working if they ignore the dashboard but means they can get on with other areas of Drupal before setting up AI.
  • We could find some third-party AI provider that will give everyone who signs up with Drupal a limited number of credits.
  • With WASM we could have had a small model that was finely tuned for Drupal hosted on your machine. With WASM not happening this might still work for whoever hosts Starshot.

Remaining tasks

User interface changes

API changes

Data model changes

📌 Task
Status

Active

Component

Track: AI

Created by

🇬🇧United Kingdom yautja_cetanu

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @yautja_cetanu
  • Comment 4 months ago →
    🇬🇧United Kingdom yautja_cetanu

    We created an approach to the installer that we showed at Drupalcon Singapore where when you click AI support you get "Set up AI in the dashboard". But this doesn't work because the dashboard might not be there. We need to find an agreed upon approach to install prior to building it ideally:

    Next steps:

    Create a Google Slides that shows the UX of each approach to AI installing:

    • The proposed one we had as an MR
    • Adding a new "block" into the dashboard just for AI
    • Creating a "Warning" across the whole site
    • Having the API key selector built into the installer itself

    Complicated thing. How can we assume a marketeer or site builder with no Drupal experience will know to "Click a link on a dashboard" and if they accidently click away how will they know to get back?

  • Comment 3 months ago →
    🇩🇪Germany marcus_johansson

    Related issue: https://www.drupal.org/project/drupal_cms/issues/3496952 📌 Use custom config action for setting up the AI Providers Active

    Based on discussions on Slack on how to solve this.

  • Comment 3 months ago →
    🇩🇪Germany marcus_johansson
  • Comment 3 months ago →
    🇺🇸United States phenaproxima Massachusetts

    With WASM we could have had a small model that was finely tuned for Drupal hosted on your machine. With WASM not happening this might still work for whoever hosts Starshot.

    Wasm could still "happen", it is just not likely to power the entire Drupal experience. But there's no particular reason you couldn't still have a small Wasm-powered model, as long as JavaScript can communicate with it (which it should be able to).

  • Comment 3 months ago →
    🇬🇧United Kingdom yautja_cetanu

    Re: a small WASM powered-model. The Chatbot library we're using now actually has out of the box support for a model in the browser. So its definitely something we can explore for 1.x

    Descisions for the install experience now.

    • We have AI installation working nicely with the dev version of Project Browser. So when PB reaches alpha7 and we have it appearing in the recipe browser in this issue. This issue can be closed. 📌 [PP1] Add AI recipe to project browser allowed list Active
    • We've decided for 1.0 not to include AI in the installer at all. We will work seperately in exploring options for how we can have AI in the installer with no API keys necessary.
    • We will explore whether or not for 1.1 we want to bring the API key back into the installer. There are differing views on how easy getting hold of an API key will be for the target persona. We can test that with the recipe.
    • The Recipe should be "AI Support" as people liked that at singapore (unless there is strong pushback and people prefer AI Assistant)
  • Comment 3 months ago →
    🇬🇧United Kingdom yautja_cetanu
contrib.social Blog FAQ Discussions
Production build 0.71.5 2024