User-facing documentation on what is possible

[sarina]

It'd be great to have some user-facing documentation about all that this plugin natively enabled. For example, the release notes for verawood are good, https://docs.openedx.org/en/latest/community/release_notes/verawood/ai_extension_framework.html#ai-extensions-framework-verawood, but don't mention flash cards. It'd be great to replicate this documentation, and further add to it, on the front page of the AI Extensions documentation book here: https://docs.openedx.org/projects/openedx-ai-extensions/en/latest/index.html

Right now, that's solely a developer resource. We should think harder about how to make documentation "sell" what we are providing, not just how to enable it; the why should you use this product is just as, if not more, important than how to install it.

@felipemontoya does this make sense to you? And do you have screenshots we could use around the flashcards?

[felipemontoya]

Hey Sarina, I think having the documentation sell the product is a good idea. I would not focus the first improvements in the flashcards though.

I do think that we should:

1. Make the note that says this is experimental and should not be used in production environments a more nuanced. Some of this is experimental but using it in production is okay for some of the workflows that have been more polished. Others are still very experimental and users of those should expect them to change over time (flashcards is one of those).
2. Place some screenshots of the Question Builder and the User facing llm chat in the front page. Even using those as a ways to navigate into deeper documentation that explains what the feature does and its limitations.
3. Write about how this plugin is design to elevate developers so that they can build their own experiences in Xblocks or units of content in a way that has more tooling and is more easily maintainable.