| name | qdrant-site |
| description | Edit and create content on the Qdrant website (Hugo static site). Code agent for page structure, content agent for writing. |
Qdrant Website Agent
You edit and create content on the Qdrant website — a Hugo static site at /Users/thierrydamiba/landing_page/qdrant-landing/.
Site Stack
| Layer | Tech | Location |
|---|
| Generator | Hugo | config.toml, base URL https://qdrant.tech |
| Theme | qdrant-2024 | themes/qdrant-2024/ |
| Templates | Go templates | themes/qdrant-2024/layouts/ |
| Styles | SCSS + Bootstrap 5.3 | themes/qdrant-2024/assets/css/ |
| Content | Markdown + YAML frontmatter | content/ |
| Build | hugo -b 'https://qdrant.tech/' | build_and_sync.sh |
| JS | Webpack 5 + Splide + Bootstrap | package.json (pnpm) |
Decision Table: What To Edit
| Want to... | Edit |
|---|
| Change page text/copy | content/<section>/<file>.md — edit YAML frontmatter fields |
| Add a new page section | 1. Create content/<section>/<section-name>.md with frontmatter, 2. Create partial themes/qdrant-2024/layouts/partials/<section-name>.html, 3. Include partial in list layout |
| Change page layout/structure | themes/qdrant-2024/layouts/<section>/list.html |
| Change visual styling | themes/qdrant-2024/assets/css/partials/_<section>.scss |
| Add a blog post | content/blog/<slug>.md with standard frontmatter |
| Edit the AI agents page | Content in content/ai-agents/ai-agents-*.md, layout in layouts/ai-agents/list.html |
Content Frontmatter Formats
Page Section (e.g., AI agents)
---
title: Section Title
description: Section description text
startFree:
text: Button Text
url: https://cloud.qdrant.io/signup
learnMore:
text: Learn More
url: "#anchor"
image:
src: /img/vectors/vector-4.svg
alt: Alt text
sitemapExclude: true
---
Blog Post
---
draft: false
title: "Post Title"
short_description: "Brief description"
description: "Full SEO description"
preview_image: /blog/slug/image.jpg
social_preview_image: /blog/slug/image.jpg
date: 2025-07-10
author: "Author Name"
featured: true
tags:
- vector-search
- ai-agents
---
Markdown body here.
AI Agents Page Structure
The page at /ai-agents/ is composed from 8 content files, assembled by layouts/ai-agents/list.html:
| Partial | Content File | What It Does |
|---|
use-cases-vector-hero | ai-agents-hero.md | Hero with CTA buttons |
ai-agents-features | ai-agents-features.md | Feature grid |
use-cases-vector-integrations | ai-agents-integrations.md | Integration logos/links |
ai-agents-webinar | ai-agents-webinar.md | Webinar embed |
use-cases-vector-cases | ai-agents-use-cases.md | Use case cards |
ai-agents-video | ai-agents-video.md | Video section |
get-started-small | ai-agents-get-started.md | Bottom CTA |
Gotchas
- Go template syntax:
{{ .Params.title }}, {{ range }}, {{ partial "name" . }}. Not Jinja2.
- Shared partials:
use-cases-vector-hero and use-cases-vector-cases are reused across pages (vector-search, ai-agents, recommendations). Changes affect ALL pages using them.
- SCSS imports: New SCSS files must be
@imported in the main stylesheet. Check assets/css/main.scss or similar.
- Hugo content ordering: Files in a section folder are ordered by
weight frontmatter field, not filename.
- Images: Go in
static/img/. Reference as /img/path/file.svg.
- sitemapExclude: true: Set on section sub-files so they don't appear as standalone pages in sitemap.
- Build test: Run
hugo from the repo root to verify no template errors before committing.
Qdrant Voice & Quality Bar
Content must match this voice profile (benchmarked from existing blog/docs):
Voice: Senior engineer who cares about production readiness. Confident but not arrogant. Shows rather than tells. Uses concrete numbers and real examples.
Do:
- Lead with the technical problem, not the product
- Use specific numbers: "p95 latency under 50ms" not "fast"
- Include architecture diagrams or code snippets
- Reference real use cases (e-commerce, RAG, recommendations)
- Keep paragraphs short (3-4 sentences max)
- Use subheadings every 2-3 paragraphs
Don't:
- Start with "In today's rapidly evolving..." or similar filler
- Use "revolutionary", "game-changing", "cutting-edge"
- Write walls of text without code or diagrams
- Make claims without supporting evidence
- Over-explain basics the audience already knows (they're engineers)
Quality thresholds:
- Flesch-Kincaid grade: 10-14 (technical but readable)
- Code/diagram ratio: at least 1 per 500 words
- CTA clarity: every page ends with a specific next step
- Internal linking: reference at least 2 related pages
