Skip to content

RDBTC-221 Migrate technical guides Migrating RDBTC-86 - #2602

Open
Netzach-Nyss wants to merge 1 commit into
ravendb:mainfrom
Netzach-Nyss:RDBTC-86
Open

RDBTC-221 Migrate technical guides Migrating RDBTC-86#2602
Netzach-Nyss wants to merge 1 commit into
ravendb:mainfrom
Netzach-Nyss:RDBTC-86

Conversation

@Netzach-Nyss

Copy link
Copy Markdown
Contributor

Issue link

RDBTC-221 Migrate technical guides and how-tos from ravend.net/articles to docs.ravendb.net/guides
RDBTC-86 Article about AWS Lambda and RavenDB Amazon SQS ETL

Additional description

Migrating article "New in 7.0: RavenDB and Amazon SQS ETL" to guides

H3 restructure landed cleanly — full H1 → H2 → H3 hierarchy, all links version-less. Here's the refreshed scorecard.

Content Quality & E-E-A-T Analysis

Content Quality Score: 90/100 (76 → 86 → 90)

Structure is now the file's strong suit. Two sections cleanly decomposed into 10 numbered H3 steps, correct heading nesting, all code fenced+tagged, three semantic Admonitions, version-independent links throughout.

E-E-A-T Breakdown

Factor Score Key Signals
Experience 23/25 Unchanged — authentic hands-on walkthrough, real scenario, 6 original screenshots, working code, genuine gotchas.
Expertise 23/25 Accurate, well-scoped, correctly structured. Ceiling held by a few casual asides ("It's not fancy", "let's do something cool", "even though it is indeed").
Authoritativeness 21/25 (+1) Three inline links to official RavenDB docs (now version-independent) + AWS official sources + curated see_also. Well-cited.
Trustworthiness 20/25 (+1) Clean, date-stamped, HTTPS, license gate as a warning callout. Only remaining gap: no "last updated" field on an 18-month-old post naming Python 3.13.

AI Citation Readiness: 85/100 (72 → 80 → 85)

  • Strong: Clean H1→H2→H3 flow with descriptive, step-based headings — each step is now an addressable anchor AI systems can extract and cite. All code language-tagged. Summary's 4 self-contained bullets remain ideal quotable facts. Structured Admonitions.
  • Remaining lever: No FAQ/Q&A block. A short "Common questions" section (e.g. Which license do I need? / Why is my data nested? / Why isn't SES sending mail?) would map directly to the three Summary gotchas and capture question-intent AI queries.

Issues Found

Minor only — no defects remain:

  • Unused imports (lines 25–29): Tabs, TabItem, CodeBlock, LanguageSwitcher, LanguageContent imported but never used. Dead code.
  • Freshness: no updated_at/last-reviewed field; Python 3.13 + v7.0 framing unverified against current.
  • Style (non-blocking): casual filler asides noted above; line 158 uses - (plain hyphen, fine).

Recommendations

  1. Remove the 5 unused imports — safe, zero-judgment cleanup (keep Admonition, Image).
  2. Add a last-reviewed date and confirm the Python 3.13 / v7.0 specifics still hold.
  3. (Optional, highest AI-readiness upside) Add a 3-question FAQ section mirroring the Summary gotchas.

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)

* [AWS account](https://aws.amazon.com/free/)
* [RavenDB](https://ravendb.net/) database

Let’s cover an actual usage scenario. We’ve written a speeding tickets data [generator](https://gist.github.com/Netzach-Nyss/afe7b3c89ce4421bceccd7eee071ea73) to simulate the continuous data stream. It will fill our database with fresh data. We'll create a new ETL task to route the data flow down to the SQS.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

make sure this gist won't expire at some point
reply back here once assured


### 1. Create a new ETL task

Open your chosen database and select the tasks menu. There, you want to choose ‘Ongoing Tasks’ and click ‘Add Database Task.’ In this menu, you can select which task you want to add; we need ‘[Amazon SQS ETL](https://ravendb.net/docs/article-page/csharp/studio/database/tasks/ongoing-tasks/amazon-sqs-etl).’

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

legacy docs link

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

fix other ones as well


## Introduction

In version 7.0, we introduced a new ongoing task: [Amazon SQS ETL](https://ravendb.net/docs/article-page/csharp/server/ongoing-tasks/etl/queue-etl/amazon-sqs). Amazon SQS, short for Simple Queue Services, is a fully managed queuing service that is part of AWS.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

legacy docs link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants