RDBTC-221 Migrate technical guides Migrating RDBTC-191

[Netzach-Nyss]

Issue link

RDBTC-191 Step-by-step: How to set up ElasticSearch ETL
RDBTC-221 Migrate technical guides and how-tos from ravend.net/articles to docs.ravendb.net/guides

Additional description

Content Quality & E-E-A-T Analysis (fourth pass)

File: feed-elasticsearch-from-your-ravendb.mdx
Prose: 1,716 words · 16-row table · 7 alt-texted screenshots · 8/8 fences tagged · 22 internal / 8 external links · 12 lists

Content Quality Score: 90/100 (76 → 84 → 89 → 90)

E-E-A-T Breakdown

Factor	Score	Key Signals
Experience	19/25 (=)	Unchanged across all four passes. Screenshots and tested config are real first-hand signals; there is still no measured outcome from an actual run. Nothing in this round's fixes could move it.
Expertise	24/25 (=)	The ProductId: id(this) fix removed the last rendering error that made a code reference look sloppy, but that's a presentation repair, not new expertise.
Authoritativeness	24/25 (=)	22 internal links, unchanged.
Trustworthiness	23/25 (+1)	Resolved: dateModified works. docusaurus.config.ts:155 sets showLastUpdateTime: true on the guides instance, so Docusaurus feeds git mtime to lastUpdatedAt, and DocPageMetadata.tsx uses it for schema dateModified in preference to publishedAt. Once committed, the page reports today's date, not Dec 2025. Issue 2 from pass three is closed, and it was closed by verification, not by an edit.

Total E-E-A-T: 90/100

AI Citation Readiness: 92/100 (71 → 84 → 91 → 92)

Marginal gain. The ## Setup intro sentence gives that section a extractable opening, and the ReportId list is now real list markup rather than soft line breaks, so it survives HTML conversion as <ul>. Both are small.

The freshness signal confirmed above matters more than either: dateModified updating on commit is a real GEO input, and it was already wired correctly.

Issues Found

Medium

1. Version drift. Line 56 still pins RavenDB v7.1 against 7.2 current. Fourth pass, still open. Now the only substantive issue in the file.

Low
2. Table Notes column has 11 empty cells of 16. Raised in pass three, not selected for fixing. Either fill them or collapse to two columns.
3. Wide table on mobile will scroll horizontally. Unverified; I have not opened the browser pane.

Recommendations

The honest read: this file is done, apart from the version pin.

Four passes have taken it from 76 to 90. The first pass found real structural problems and fixing them moved the score 8 points. This pass moved it 1, and that point came from verifying something rather than changing anything. That's the signal that the mechanical work is exhausted.

What remains splits cleanly:

• Issue 1 (version pin) is a genuine content decision needing someone to compare seven screenshots against Studio 7.2. Worth doing, cannot be automated, and it's the last thing standing between this guide and a clean bill.
• Issue 2 (Notes column) is cosmetic and arguably fine as-is; sparse Notes cells are normal in comparison tables where most rows need no qualifier.
• Issue 3 needs a browser check I haven't run.
• Experience at 19/25 is the largest remaining scoring gap and the only one I genuinely cannot close. It needs one real number from a real ETL run: backfill duration for a known document count, or observed steady-state lag. I'd be inventing data if I supplied it.

Type of change

• Content - docs
• Content - cloud
• Content - Quill
• Content - guides
• Content - start pages/other
• New docs feature (consider updating /templates or readme)
• Bug fix
• Optimization
• Other

Changes in docs URLs

• No changes in docs URLs
• Articles are restructured, URLs will change, mapping is required (update /scripts/redirects.json file, set Documents Moved PR label)

Changes in UX/UI

• No changes in UX/UI
• Changes in UX/UI (include screenshots and description)