nextcloud / nextcloud/assistant
Cross-Reference: Custom template support for AI-generated Office documents
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 88
- Forks
- 43
- Avg merge
- 18h 49m
- Merged PRs (30d)
- 3
Description
Summary
This is a cross-reference to a feature request filed in nextcloud/richdocuments:
➡️ nextcloud/richdocuments#5431 — Custom template support for AI-generated Office documents (DOCX, XLSX, PPTX)
Context for this repo
When the Nextcloud Assistant generates Office documents (DOCX, XLSX, PPTX) from a user prompt, the resulting files always use default Collabora styling. There is currently no way for users or administrators to select a custom template so that AI-generated documents match organizational branding or formatting standards.
While the core implementation work belongs in nextcloud/richdocuments (where the TaskProcessing providers and TemplateManager live), a UI change is also required in this repository: a template selection step needs to be added to the Assistant’s document generation dialog, similar to the template picker already present in the Files “+” / new document flow.
What would need to change here
- Add an optional template selector to the DOCX/XLSX/PPTX generation dialog in the Assistant UI.
- The selector would query available templates via the existing
TemplateManagerAPI inrichdocuments. - The selected
templateIdwould be passed as an additional input parameter to the respective TaskProcessing provider. - When no template is selected, the current default behavior is preserved (fully backward-compatible).
Related
nextcloud/richdocuments#5431— Main feature request with full implementation proposal (primary issue)nextcloud/richdocumentsPR #3798 — PDF Template Workflow (introducesTemplateFieldService, the technical foundation)nextcloud/server#22426— File templates (broader unified template handling)
This cross-post is intended to make the Assistant team aware of the UI work involved. All technical discussion should happen in the primary issue linked above.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Assistant UI's DOCX/XLSX/PPTX generation dialog and compare it with the template picker in the Files “+” / new document flow. Read nextcloud/richdocuments#5431 for the TemplateManager API and provider inputs; done means an optional template selection is passed through while no selection preserves current behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100