memory parameter introduced in Qdrant v1.19. If you're using an older version, see the Legacy Settings section for how to map the new parameter to the old ones.
-If you would rather have an agent work through this with you, the following prompt asks it to find which component is actually using the memory before it suggests any changes.
+An agent can work through this with you. The Diagnose high memory usage prompt makes it find which component is actually using the memory before it suggests any changes.
{{< prompt "diagnose-memory-usage" >}}
diff --git a/qdrant-landing/content/documentation/production-checklist.md b/qdrant-landing/content/documentation/production-checklist.md
index 4c128be34..3a8676982 100644
--- a/qdrant-landing/content/documentation/production-checklist.md
+++ b/qdrant-landing/content/documentation/production-checklist.md
@@ -10,7 +10,7 @@ weight: 147
A practical checklist to ensure Qdrant is optimized, stable, and ready to handle real-world load.
-If you would rather have an agent run through this with you, use the following prompt to get a prioritized list of what would break first under real load.
+An agent can run the checklist with you. The Review my deployment prompt asks it for a prioritized list of what would break first under real load.
{{< prompt "review-before-launch" >}}
diff --git a/qdrant-landing/layouts/shortcodes/prompt-index.markdown.md b/qdrant-landing/layouts/shortcodes/prompt-index.markdown.md
index d683c069b..4ad6b6e74 100644
--- a/qdrant-landing/layouts/shortcodes/prompt-index.markdown.md
+++ b/qdrant-landing/layouts/shortcodes/prompt-index.markdown.md
@@ -7,6 +7,10 @@
Keep in step with prompt-index.html, which emits table markup instead of
pipes because shortcode output is not re-parsed as markdown.
+
+ Page links are absolute and index.md-suffixed to match every other link in
+ this output, which single.markdown.md rewrites that way. A bare site path
+ would be the one column an agent reading this table could not resolve.
*/ -}}
{{- $section := site.GetPage "documentation/headless/prompts" -}}
{{- if not $section -}}
@@ -15,5 +19,5 @@
| Prompt | Page | Agent skill |
|---|---|---|
{{ range $section.RegularPages.ByTitle -}}
-| {{ .Title }} | {{ with .Params.page }}{{ . }}{{ else }}None{{ end }} | {{ with .Params.skill }}https://skills.qdrant.tech/{{ . }}/SKILL.md{{ else }}None{{ end }} |
+| {{ .Title }} | {{ with .Params.page }}{{ with site.GetPage . }}{{ .Permalink }}index.md{{ else }}{{ . }}{{ end }}{{ else }}None{{ end }} | {{ with .Params.skill }}https://skills.qdrant.tech/{{ . }}/SKILL.md{{ else }}None{{ end }} |
{{ end -}}
diff --git a/qdrant-landing/themes/qdrant-2024/assets/css/components/_prompt.scss b/qdrant-landing/themes/qdrant-2024/assets/css/components/_prompt.scss
index 236925e8a..8d1a2f1cf 100644
--- a/qdrant-landing/themes/qdrant-2024/assets/css/components/_prompt.scss
+++ b/qdrant-landing/themes/qdrant-2024/assets/css/components/_prompt.scss
@@ -1,10 +1,22 @@
@use '../helpers/functions' as *;
+// Both themes are declared here so a palette change is a one-block edit. The
+// light values were previously written as literals at the use site, which is
+// how a palette silently stops being the palette.
$prompt-surface: $neutral-20;
$prompt-border: $neutral-40;
$prompt-text: $neutral-98;
$prompt-text-muted: $neutral-70;
$prompt-accent: $primary-60;
+// The body block sits deeper than the card. Without this it renders the same
+// $neutral-20 as the card and the prompt reads as loose monospace in a box.
+$prompt-block-surface: $neutral-10;
+
+$prompt-surface-light: $neutral-98;
+$prompt-border-light: $neutral-94;
+$prompt-text-light: $neutral-10;
+$prompt-text-muted-light: $neutral-50;
+$prompt-accent-light: $primary-40;
.prompt {
background: $prompt-surface;
@@ -79,9 +91,24 @@ $prompt-accent: $primary-60;
padding: 0 pxToRem(16) pxToRem(16);
}
- // The fenced block Chroma emits inside the body.
+ // The block Chroma emits inside the body.
.highlight {
margin: 0;
+ background: $prompt-block-surface;
+ }
+
+ // A prompt is prose, not code. Its line breaks come from how the author
+ // wrapped the source file, so a fixed-width clips every line at any
+ // window narrower than the wrap width instead of reflowing. Sideways
+ // scrolling is a fair bargain for code and a bad one for a paragraph.
+ // pre-wrap keeps the deliberate line structure in prompts that have one.
+ .highlight > pre {
+ white-space: pre-wrap;
+ overflow-wrap: break-word;
+ // copy-code.js absolutely positions its button at the top right of
+ // .highlight. Wrapped text now reaches the full width, so the first line
+ // would run underneath it.
+ padding-right: pxToRem(56);
}
&__skill {
@@ -99,9 +126,9 @@ $prompt-accent: $primary-60;
}
[data-theme='light'] & {
- background: $neutral-98;
- border-color: $neutral-94;
- border-left-color: $primary-40;
+ background: $prompt-surface-light;
+ border-color: $prompt-border-light;
+ border-left-color: $prompt-accent-light;
}
}
@@ -109,25 +136,25 @@ $prompt-accent: $primary-60;
// lands in the descendant position, where it can never match, because the
// theme attribute sits on .
[data-theme='light'] .prompt__summary {
- color: $neutral-10;
+ color: $prompt-text-light;
}
[data-theme='light'] .prompt__summary::before {
- border-right-color: $primary-40;
- border-bottom-color: $primary-40;
+ border-right-color: $prompt-accent-light;
+ border-bottom-color: $prompt-accent-light;
}
[data-theme='light'] .prompt__summary:hover {
- color: $primary-40;
+ color: $prompt-accent-light;
}
[data-theme='light'] .prompt__skill,
[data-theme='light'] .prompt__kind {
- color: $neutral-50;
+ color: $prompt-text-muted-light;
}
[data-theme='light'] .prompt__kind {
- border-right-color: $neutral-94;
+ border-right-color: $prompt-border-light;
}
@media (prefers-reduced-motion: reduce) {
diff --git a/qdrant-landing/themes/qdrant-2024/layouts/shortcodes/prompt.html b/qdrant-landing/themes/qdrant-2024/layouts/shortcodes/prompt.html
index 51ca27bc9..5b162db80 100644
--- a/qdrant-landing/themes/qdrant-2024/layouts/shortcodes/prompt.html
+++ b/qdrant-landing/themes/qdrant-2024/layouts/shortcodes/prompt.html
@@ -3,10 +3,15 @@
Usage: {{< prompt "set-up-monitoring" >}}
- The prompt file's body is plain text. This template wraps it in a fenced
- block and runs it through markdownify so Chroma produces a real
- `.highlight > pre`, which copy-code.js finds and adds a copy button to. That
- is why this element needs no JavaScript of its own.
+ The prompt file's body is plain text. `highlight` hands it to Chroma as a
+ value, producing a real `.highlight > pre`, which copy-code.js finds and adds
+ a copy button to. That is why this element needs no JavaScript of its own.
+
+ It is deliberately not wrapped in a fence and run through markdownify. A body
+ containing its own ``` would close that outer fence early, truncating the
+ prompt and spilling the rest of it onto the page as loose markdown, with a
+ clean build and a green check. `highlight` never re-parses the body, so a
+ prompt can contain any characters at all.
The Markdown output format has its own variant, prompt.markdown.md, which
deliberately drops the body so an agent reading index.md is not handed an
@@ -15,7 +20,7 @@
{{- $id := .Get 0 -}}
{{- $p := site.GetPage (printf "documentation/headless/prompts/%s" $id) -}}
{{- if not $p -}}
- {{- errorf "prompt: no prompt file found for id %q (looked in content/documentation/headless/prompts/). Called from %s" $id .Page.File.Path -}}
+ {{- errorf "prompt: no prompt file found for id %q (looked in content/documentation/headless/prompts/). Called from %s" $id .Page.RelPermalink -}}
{{- end -}}
@@ -27,7 +32,7 @@
{{ $p.Title }}
- {{ printf "```text\n%s\n```" (trim $p.RawContent "\n") | markdownify }}
+ {{ highlight (trim $p.RawContent "\n") "text" "" }}
{{- with $p.Params.skill }}
Uses the