[SBTW-2685] Add website repeating sync and auto deployment to Knowledge guide#116
[SBTW-2685] Add website repeating sync and auto deployment to Knowledge guide#116sd-katherinekim wants to merge 9 commits intodevelopfrom
Conversation
- Add daily/weekly repeating sync support for website knowledge type - Add Configure repeating sync section with step-by-step instructions - Add Auto deployment section for website knowledge sources - Add sync history mention - Replace *** dividers with --- Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Editor fixes: - Replace * bullets with - per aadocs.md - Fix heading hierarchy: H4 → H3 under H2 - Replace parentheses with em dash for Genesys qualifier - Fix inconsistent dash in bullet list - Remove redundant bold from H3 headings (Save, Sync, Delete) - Move punctuation outside bold formatting - Fix typo "in to" → "into" - Simplify Delete section list formatting - Clarify Genesys Voice-only qualifier User reviewer fix: - Fix grammar "These are information" → simplified sentence Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Update SUMMARY.md reference accordingly. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
| Knowledge is a shared asset created and managed at the **workspace level**, but it can be selectively enabled or disabled per AI agent. This two-level setup allows you to centrally manage knowledge while still tailoring usage per agent without duplicating content. | ||
|
|
||
| #### 1. Workspace-level (Shared asset) | ||
| ### 1. Workspace-level (Shared asset) |
There was a problem hiding this comment.
Minor — Parentheses in headings violate shared-conventions.md §3.6, which says to avoid parentheses and use em dashes for inline clarification. (Shared asset) is not an abbreviation (the only acceptable parentheses use) and should be set off with an em dash instead. Also apply sentence case: the label is lowercase elsewhere in the document.
| ### 1. Workspace-level (Shared asset) | |
| ### 1. Workspace-level — shared asset |
| - Acts as the central repository for the entire workspace. | ||
|
|
||
| #### 2. Agent-level (per AI agent) | ||
| ### 2. Agent-level (per AI agent) |
There was a problem hiding this comment.
Minor — Same parentheses issue (shared-conventions.md §3.6). (per AI agent) is a supplementary label, not an abbreviation.
| ### 2. Agent-level (per AI agent) | |
| ### 2. Agent-level — per AI agent |
There was a problem hiding this comment.
Style Guide Review
Files reviewed: 2
Summary: Critical 0 | Major 0 | Minor 0
The knowledge.md changes are clean and guide-compliant. Bullet characters normalised to dash (aadocs.md s5), dividers changed to dashes (aadocs.md s3), H4 headings under H2 corrected to H3 (shared-conventions.md s9), bold stripped from the Save/Sync/Delete headings, em dash and serial-comma fixes are correct.
Non-diff issues
dashboard-guide/ai-agent-home/deployment.md (renamed with no content changes, pre-existing issues):
Lines 42 44 48 - All three img elements carry empty alt attributes. These screenshots show meaningful UI and do not qualify for the decorative-image exception. Descriptive alt text is required for each (shared-conventions.md s8.1).
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
There was a problem hiding this comment.
Style Guide Review\n\nFiles reviewed: 2\nSummary: Critical: 0 | Major: 0 | Minor: 0\n\nThis PR has been reviewed multiple times. Only critical issues are flagged.\n\nNo critical issues found. The rename of gradual-deployment.md to deployment.md is fully consistent. SUMMARY.md and the cross-reference link in knowledge.md both point to the new path, and no stale references to the old filename remain.
There was a problem hiding this comment.
Style Guide Review
Files reviewed: 2
Summary: Critical: 0 | Major: 0 | Minor: 0
This PR has been reviewed multiple times. Only critical issues are flagged.
No critical issues found. The changes are:
deployment.md: pure rename fromgradual-deployment.md— no content changes,SUMMARY.mdlink updated correctly.knowledge.md: formatting corrections (bullet style*→-, dividers***→---, heading level H4 → H3 fixing a hierarchy skip) and new "Configure repeating sync" / "Auto deployment" sections. All new content is technically accurate and cross-reference links are correct post-rename.
There was a problem hiding this comment.
Style Guide Review
Files reviewed: 2
Summary: Critical: 0 | Major: 0 | Minor: 0
This PR has been reviewed multiple times. Only critical issues are flagged.
✅ No critical issues found.
dashboard-guide/ai-agent-home/deployment.md— rename only, no content changes.dashboard-guide/shared-assets/knowledge.md— diff lines reviewed against all style guide layers. No factually incorrect, technically wrong, or dangerously misleading content detected.
1 participant
Summary
***dividers with---per style guideContext
Website knowledge sources now support repeating sync, which was previously available only for integrations such as Confluence, Zendesk, and Salesforce. Auto deployment — previously limited to a single customer — is now GA for website knowledge.
Still needed
🤖 Generated with Claude Code