Site specific AI prompt libraries #61
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This reverts commit e99f618.
stoerr
changed the title
* develop: Revert "Bump wikitext.version from 3.0.42 to 3.0.48.202308291007" mention that it's now AEM 6.5 capable in the documentations
stoerr
force-pushed
the
feature/4-site-specific-ai-preferences
branch
from
3333625
to
f60690c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since the necessary AI prompts will vary from site to site we support now configuring prompt libraries for the content creation dialog and the side panel AI for sites or page trees via Sling Context Aware Configuration (CAC). With CAC it's possible to configure the paths to prompt libraries. The path can be to a JSON file in the repository, that contains a map of prompt titles to prompt texts, or a content page, where one parsys contains the library of prompts. This way it's possible for an editor to edit a prompt library without us having to provide a special editor. The standard prompt libraries as content pages are located at:
For Composum a prompt library page should have a number of text components in one parsys where the title is the name of the prompt and the text is the prompt itself. The standard prompt library pages are:
/libs/composum/pages/options/ai/dialogs/create/defaultprompts
/libs/composum/pages/options/ai/tools/sidebar/defaultprompts
For AEM a prompt library page should have one parsys with a number of components that have a
jcr:titleortitleorsubtitleproperty that contains the prompt, and ajcr:description,descriptionortextproperty that contains the prompt. The standard prompt library pages are:/conf/composum-ai/settings/dialogs/contentcreation/predefinedprompts
/conf/composum-ai/settings/dialogs/sidepanel-ai/predefinedprompts
The paths are configured with Sling CAC with com.composum.ai.backend.slingbase.model.GPTPromptLibrary .
Also: to better support a workflow where somebody performs the same task on several pages / components, we save the last state the content creation workflow was in and restore the same state when a content creation workflow is opened on a new page or component where it wasn't opened in this session.