Skip to content

Promote Vector Database quickstart on docs homepage - #3921

Open
kosabogi wants to merge 1 commit into
mainfrom
vector-full-text-search-homepage
Open

Promote Vector Database quickstart on docs homepage#3921
kosabogi wants to merge 1 commit into
mainfrom
vector-full-text-search-homepage

Conversation

@kosabogi

Copy link
Copy Markdown
Member

Summary

  • replace the AI agent skills homepage promotion with the new Vector Database quickstart
  • highlight semantic and hybrid search in the reader's preferred language
  • link the CTA directly to the tutorial

Depends on elastic/docs-content#7923.

Test plan

  • Preview the updated homepage locally using the current docs-content source
  • Confirm the CTA path matches the Vector Database quickstart URL

Made with Cursor

Replace the AI agent skills promotion with a direct path to the new Vector Database tutorial.

Co-authored-by: Cursor <cursoragent@cursor.com>

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

No actionable issues found.


What is this? | From workflow: PR Review

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

Mpdreamz added a commit that referenced this pull request Aug 25, 2026
…rker resolution

Adds the `link:` field to `ChangelogEntryDto`, `ChangelogEntry`, and
`BundledEntry` so markers survive the scrub round-trip.

`ChangelogContentScrubber` fast-paths a bare `link:`-only entry unchanged;
a marker combined with content fields (title, type, prs) throws to catch
authoring errors early.

`ChangelogEntryMatcher` now detects markers in both `MatchChangelogsAsync`
and `MatchChangelogContents`, suppresses them from bundle output, and resolves
each to its parent entry after the main pass:
- parent not found → hard error (a pipeline promise was broken)
- parent is itself a marker (depth > 1) → hard error
- parent found → marker silently dropped; parent included once

No markers exist in S3 today so all new paths are inert on merge.
Step 7 of the two-anchor plan (#3921).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants