Skip to content

platform documentation#884

Merged
yannickmonney merged 1 commit into
tale-project:mainfrom
naveed-jameel-comsian:platform-documentation
Mar 26, 2026
Merged

platform documentation#884
yannickmonney merged 1 commit into
tale-project:mainfrom
naveed-jameel-comsian:platform-documentation

Conversation

@naveed-jameel-comsian
Copy link
Copy Markdown
Contributor

@naveed-jameel-comsian naveed-jameel-comsian commented Mar 26, 2026

Added platform documentation

Summary by CodeRabbit

  • Documentation
    • Consolidated multiple standalone guides into a single comprehensive platform documentation page
    • New unified documentation covers architecture, setup (local and production), major features (AI Chat, Knowledge Base, Automations, Custom Agents), integrations, role-based permissions, SSO, API documentation, and operational guidance
    • Updated documentation navigation structure

Copy link
Copy Markdown

@greptile-apps greptile-apps Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Mar 26, 2026

📝 Walkthrough

Walkthrough

This PR consolidates fragmented documentation into a unified platform guide. Four separate markdown documentation files are removed: chat-agent-guide.md (252 lines), permissions.md (123 lines), workflow-guide.md (1,250 lines), and zero-downtime-deployment.md (231 lines). A new comprehensive docs/platform-documentation.md file (936 lines) is created, containing consolidated information about platform architecture, deployment, features, and operations. The navigation configuration in docs.json is updated to reference the single new documentation file instead of the four individual guides.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'platform documentation' accurately summarizes the main change: consolidating scattered documentation into a single comprehensive platform documentation file.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 4

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@docs/platform-documentation.md`:
- Line 191: Change the phrase "platform ready message" to the hyphenated
compound adjective "platform-ready message" in the sentence "Wait for the
platform ready message, then open https://tale.local." so the compound adjective
correctly precedes the noun.
- Line 290: Reword the last sentence to place "also" between the auxiliary and
main verb for smoother flow: change "Custom agents your team has built also
appear here." to "Custom agents your team has also built appear here." in the
sentence that begins "The agent selector is in the bottom-left corner of the
input area..."
- Around line 25-52: The Markdown ASCII diagram block is missing a language
identifier; update the opening triple-backtick for the diagram in
platform-documentation.md to include a language tag such as text or plain (e.g.,
```text) so the ASCII art renders correctly; locate the code fence that begins
the big Caddy Proxy diagram and add the identifier to the opening ``` line.
- Around line 256-258: The ordered list entries "Copy the key from the output.",
"Open https://tale.local/convex-dashboard in your browser.", and "Paste the
admin key when prompted." use inconsistent numbering (2., 3., 4.); update the
list so numbering is correct (either restart at 1. for the three steps or
continue the preceding sequence properly) by editing those three lines to use
the correct numeric prefixes (e.g., 1., 2., 3. or the continuing numbers) so the
list renders in order.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 0d4f1d7d-a745-4bb0-a348-23450c86eb01

📥 Commits

Reviewing files that changed from the base of the PR and between b04b60c and 38023e7.

📒 Files selected for processing (6)
  • docs/chat-agent-guide.md
  • docs/docs.json
  • docs/permissions.md
  • docs/platform-documentation.md
  • docs/workflow-guide.md
  • docs/zero-downtime-deployment.md
💤 Files with no reviewable changes (4)
  • docs/permissions.md
  • docs/chat-agent-guide.md
  • docs/zero-downtime-deployment.md
  • docs/workflow-guide.md

Comment on lines +25 to +52
```
┌─────────────────────────────────────────────────────────────┐
│ Caddy Proxy │
│ (Routes traffic to healthy backend) │
└─────────────────────────┬───────────────────────────────────┘
┌─────────────────┴─────────────────┐
▼ ▼
┌───────────────────┐ ┌───────────────────┐
│ Blue Services │ │ Green Services │
│ (Active) │ │ (Standby) │
├───────────────────┤ ├───────────────────┤
│ platform-blue │ │ platform-green │
│ rag-blue │ │ rag-green │
│ crawler-blue │ │ crawler-green │
│ operator-blue │ │ operator-green │
└───────────────────┘ └───────────────────┘
│ │
└─────────────────┬─────────────────┘
┌───────────────────┐
│ Shared Services │
│ (Stateful) │
├───────────────────┤
│ db (TimescaleDB) │
│ proxy (Caddy) │
└───────────────────┘
```
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Add language identifier to the code fence.

The ASCII diagram code block should specify a language identifier for proper rendering. Use text or plain for ASCII art.

📝 Proposed fix
-```
+```text
 ┌─────────────────────────────────────────────────────────────┐
 │                         Caddy Proxy                          │
🧰 Tools
🪛 markdownlint-cli2 (0.22.0)

[warning] 25-25: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@docs/platform-documentation.md` around lines 25 - 52, The Markdown ASCII
diagram block is missing a language identifier; update the opening
triple-backtick for the diagram in platform-documentation.md to include a
language tag such as text or plain (e.g., ```text) so the ASCII art renders
correctly; locate the code fence that begins the big Caddy Proxy diagram and add
the identifier to the opening ``` line.


1. Open Docker Desktop and wait until the engine status shows green.
2. In your terminal, go to the `tale` folder and run `docker compose up`.
3. Wait for the platform ready message, then open https://tale.local.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Add hyphen to compound adjective.

"platform ready message" should be "platform-ready message" when the compound adjective precedes the noun.

📝 Proposed fix
-3. Wait for the platform ready message, then open https://tale.local.
+3. Wait for the platform-ready message, then open https://tale.local.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
3. Wait for the platform ready message, then open https://tale.local.
3. Wait for the platform-ready message, then open https://tale.local.
🧰 Tools
🪛 LanguageTool

[grammar] ~191-~191: Use a hyphen to join words.
Context: ...er compose up`. 3. Wait for the platform ready message, then open https://tale.lo...

(QB_NEW_EN_HYPHEN)

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@docs/platform-documentation.md` at line 191, Change the phrase "platform
ready message" to the hyphenated compound adjective "platform-ready message" in
the sentence "Wait for the platform ready message, then open
https://tale.local." so the compound adjective correctly precedes the noun.

Comment on lines +256 to +258
2. Copy the key from the output.
3. Open https://tale.local/convex-dashboard in your browser.
4. Paste the admin key when prompted.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Fix ordered list numbering.

The list item numbering is inconsistent. Start from 1 or continue the sequence properly.

📝 Proposed fix
 1. Run this to generate an admin key:
 
 ```bash
 docker exec tale-platform /app/generate-admin-key.sh

-2. Copy the key from the output.
-3. Open https://tale.local/convex-dashboard in your browser.
-4. Paste the admin key when prompted.
+2. Copy the key from the output.
+3. Open https://tale.local/convex-dashboard in your browser.
+4. Paste the admin key when prompted.

</details>

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 markdownlint-cli2 (0.22.0)</summary>

[warning] 256-256: Ordered list item prefix
Expected: 1; Actual: 2; Style: 1/2/3

(MD029, ol-prefix)

---

[warning] 257-257: Ordered list item prefix
Expected: 2; Actual: 3; Style: 1/2/3

(MD029, ol-prefix)

---

[warning] 258-258: Ordered list item prefix
Expected: 3; Actual: 4; Style: 1/2/3

(MD029, ol-prefix)

</details>

</details>

<details>
<summary>🤖 Prompt for AI Agents</summary>

Verify each finding against the current code and only fix it if needed.

In @docs/platform-documentation.md around lines 256 - 258, The ordered list
entries "Copy the key from the output.", "Open
https://tale.local/convex-dashboard in your browser.", and "Paste the admin key
when prompted." use inconsistent numbering (2., 3., 4.); update the list so
numbering is correct (either restart at 1. for the three steps or continue the
preceding sequence properly) by editing those three lines to use the correct
numeric prefixes (e.g., 1., 2., 3. or the continuing numbers) so the list
renders in order.


</details>

<!-- fingerprinting:phantom:triton:puma -->

<!-- This is an auto-generated comment by CodeRabbit -->


#### Selecting an Agent

The agent selector is in the bottom-left corner of the input area, shown as a bot icon. Use it to choose which AI agent handles your conversation. The default is the system chat agent. Custom agents your team has built also appear here.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick | 🔵 Trivial

Improve word order for natural flow.

Move "also" between the auxiliary verb and main verb for more natural English.

✨ Suggested improvement
-The default is the system chat agent. Custom agents your team has built also appear here.
+The default is the system chat agent. Custom agents your team has also built appear here.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
The agent selector is in the bottom-left corner of the input area, shown as a bot icon. Use it to choose which AI agent handles your conversation. The default is the system chat agent. Custom agents your team has built also appear here.
The agent selector is in the bottom-left corner of the input area, shown as a bot icon. Use it to choose which AI agent handles your conversation. The default is the system chat agent. Custom agents your team has also built appear here.
🧰 Tools
🪛 LanguageTool

[style] ~290-~290: To make your writing flow more naturally, try moving ‘also’ between the auxiliary and the verb.
Context: ...tem chat agent. Custom agents your team has built also appear here. #### Chat History Click ...

(ALSO_PLACEMENT)

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@docs/platform-documentation.md` at line 290, Reword the last sentence to
place "also" between the auxiliary and main verb for smoother flow: change
"Custom agents your team has built also appear here." to "Custom agents your
team has also built appear here." in the sentence that begins "The agent
selector is in the bottom-left corner of the input area..."

@yannickmonney yannickmonney merged commit a822e0c into tale-project:main Mar 26, 2026
1 check passed
yannickmonney pushed a commit that referenced this pull request Apr 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants