RDBTC-221 Migrate technical guides Migrating RavenDB-22024 Akka.NET Tutorial

[Netzach-Nyss]

Issue link

RDBTC-221 Migrate technical guides and how-tos from ravend.net/articles to docs.ravendb.net/guides
RavenDB-22024 Akka.NET - Tutorial

Additional description

Content Quality & E-E-A-T Analysis

Content Quality Score: 91/100 (was 72)

Metric	First pass	Now
Prose words	1,805	2,084
Structure	4 H2, 0 H3	5 H2, 8 H3, ## Summary
RavenDB in first 100 words	no	yes, first word
First H2 on-target	no (What is Akka?)	yes (What is Akka.NET Persistence?)
Prose sentences over 30 words	9	0
Avg sentence length	21.0	17.6
Internal docs links	1	4 (+3 see_also)
Package links	0	2 (NuGet)
keywords in schema	absent	9 terms
Legacy/redirecting links	1	0

Keyword density is healthy and unforced: RavenDB 1.58%, snapshot 1.78%, persistence 1.54%, all inside the 1 to 3% band with no stuffing.

E-E-A-T Breakdown: 78/100 (was 83)

Factor	Score	Key Signals
Experience	21/25 (=)	Five original screenshots from real runs, process documented with concrete values (repeats at 6, 10, 15), non-fabricable gotchas about debug-only collection deletes and old-format replay failures.
Expertise	15/25 (=)	Technical depth is unchanged and strong.
Authoritativeness	22/25 (+1)	Both NuGet packages now linked at first mention, on a guide published by the vendor of the package it teaches. Three first-party docs cluster links in body plus three in see_also, all re-verified present on this branch. Cites official getakka.net with a working anchor.
Trustworthiness	20/25 (−2)	HTTPS, canonical, TechArticle schema with datePublished and keywords, all links verified resolving with zero redirect hops. Loses points on the same issue: transparency about who wrote the content is currently broken, and there is still no version pinning.

AI Citation Readiness: 82/100 (was 58)

Issues Found

Open, needs a fact I do not have

• M3. No version anchors. No .NET version, no Akka.Persistence.RavenDB.Hosting version, no server version, on a package-integration tutorial.

Minor

• n3. No comparative structure. The snapshot tradeoff is stated well in prose and in a Summary bullet, never as a table.
• n4. event sourcing appears once (0.05%) despite being in the title's semantic core, the description, and the new keywords. A second natural use in the journal section would strengthen semantic coverage.
• n5. Freshness. 368 days since published_at. dateModified will refresh from git on commit, so this resolves itself when the work lands.

Recommendations

1. State versions once near the dotnet add package step at line 57. Tell me the tested versions and it is a one-line edit.
2. Optional: a three-row table for the snapshot tradeoff, and one more natural use of "event sourcing".

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)