Skip to content

docs: Add "How Promptless Learns Your Docs" page explaining doc analysis#248

Merged
frances720 merged 5 commits intomainfrom
promptless/doc-analysis-explained
Feb 18, 2026
Merged

docs: Add "How Promptless Learns Your Docs" page explaining doc analysis#248
frances720 merged 5 commits intomainfrom
promptless/doc-analysis-explained

Conversation

@promptless
Copy link
Contributor

@promptless promptless bot commented Feb 18, 2026

Open this suggestion in Promptless to view citations and reasoning process

Creates a new documentation page explaining what happens during doc analysis—the "behind the scenes" processes that make Promptless work. Covers:

  • Initial Ingestion: What happens when you first connect your docs (5-30 min indexing process)
  • Product Ontology: How Promptless understands your product's features, terminology, and relationships
  • Voice and Style Learning: How Voice Match analyzes your writing patterns to match your style
  • Trigger Processing: Step-by-step breakdown of context gathering, change analysis, content drafting, and suggestion creation
  • Continuous Learning: How feedback and ongoing updates improve suggestions over time

Added to the Getting Started section after Core Concepts.

Trigger Events

Internal discussion about whether documentation exists explaining what happens during doc analysis, including the product ontology and ingestion process.

Agent Response

I've completed the documentation request. Here's a summary of what was created:

Summary

Created a new documentation page "How Promptless Learns Your Docs" that explains what happens during doc analysis. The page covers:

  1. Initial Ingestion - What happens when you first connect your docs (5-30 minute indexing process, relationship mapping)

  2. Product Ontology - How Promptless understands your product's structure, features, terminology, and relationships between concepts

  3. Voice and Style Learning - How Voice Match analyzes your writing patterns (tone, terminology, structure, conventions) to match your team's style

  4. What Happens When a Trigger Fires - Step-by-step breakdown of context gathering, change analysis, content drafting, and suggestion creation

  5. Continuous Learning - How feedback incorporation and style evolution improve suggestions over time

The new page is added to the Getting Started section after "Core Concepts" in the navigation.

Suggestion URL: https://app.gopromptless.ai/suggestions/b62079d7-3ac4-453d-8dda-51d58d480873


Tip: Attach PDFs in Slack messages to Promptless—it can even extract images from them 📎

@@ -0,0 +1,64 @@
---
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Citation: Frances requested documentation about "what happens during doc analysis" including the product ontology. This new page addresses those topics: product ontology building, voice/style learning, and what happens when triggers fire.
View source

@github-actions
Copy link

Copy link
Contributor

@frances720 frances720 Feb 18, 2026

Choose a reason for hiding this comment

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

Suggested change
When you connect your documentation, Promptless analyzes it to understand your product, your writing style, and how your docs are organized.
Before creating the first suggestion, Promptless analyzes your existing docs to understand the product, writing style, and how your docs are organized.

Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
When you first connect your documentation platform, Promptless ingests and indexes all your existing docs. This typically takes 5-30 minutes, depending on the size of your documentation.

@promptless
Copy link
Contributor Author

promptless bot commented Feb 18, 2026

I've added new changes to address this PR review in commit 4a1cbfb

@github-actions
Copy link

- Understand your product's concepts and terminology
- Identify connections between features that might require coordinated documentation updates

For example, if your product has a "Workspaces" feature with sub-features like "Permissions" and "Invitations," Promptless understands these relationships and can update all relevant pages when workspace behavior changes.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
For example, if your product has a "Workspaces" feature with sub-features like "Permissions" and "Invitations," Promptless understands these relationships and can update all relevant pages when workspace behavior changes.
For example, if your product has a "Workspaces" feature with sub-features like "Permissions" and "Invitations," Promptless understands these relationships and can update all relevant pages when "Workspace" behavior changes.

@promptless
Copy link
Contributor Author

promptless bot commented Feb 18, 2026

I've added new changes to address this PR review in commit ea766c0

Copy link
Contributor

Choose a reason for hiding this comment

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

This section doesn't belong in this doc, it can be a separate page, though

@github-actions
Copy link

@promptless
Copy link
Contributor Author

promptless bot commented Feb 18, 2026

I've added new changes to address this PR review in commit 7b4e532

@github-actions
Copy link

@promptless
Copy link
Contributor Author

promptless bot commented Feb 18, 2026

I've added new changes to address this PR review in commit eb02014

@github-actions
Copy link


When drafting content, Promptless references similar existing pages to match their style.

## Continuous Learning
Copy link
Contributor

Choose a reason for hiding this comment

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

This doesn't make sense as a section in this doc either

@frances720 frances720 merged commit 84c71ce into main Feb 18, 2026
2 checks passed
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.

1 participant

Comments