Skip to content

RDBTC-221 Migrate Technical Guides: RDBTC-56 Setting Up RavenDB with Docker and HTTPS#2519

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

RDBTC-221 Migrate Technical Guides: RDBTC-56 Setting Up RavenDB with Docker and HTTPS#2519
Netzach-Nyss wants to merge 1 commit into
ravendb:mainfrom
Netzach-Nyss:RDBTC-56

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

Additional description

Migrating Setting Up RavenDB with Docker and HTTPS with its image and adding a new author.


Content Quality Score: 84/100

E-E-A-T Breakdown

Factor Score Key Signals
Experience 20/25 Named author, first-person voice, screenshot of working result, real commands from a genuine setup
Expertise 21/25 Accurate UID/GID explanation, correct cert chain guidance, env-var table is precise, self-signed cert risks properly caveated
Authoritativeness 16/25 Official RavenDB docs domain, Docker Hub links, relative internal links now consistent
Trustworthiness 24/25 Named author, ISO date, security warnings, "not recommended for production" caveat, HTTPS

AI Citation Readiness: 78/100

The env-var table, Summary bullets, and the new /etc/hosts step are all well-structured for AI extraction. The remaining drag is the generic Introduction paragraph.


Remaining Issues

Only two are left, both minor:

  1. Generic Docker boilerplate in the Introduction — the first paragraph ("Running applications in Docker containers offers numerous advantages…") adds no RavenDB-specific value. The guide becomes useful at the second paragraph. Removing or replacing the opener would improve E-E-A-T and AI citation quality.

  2. "What you will learn" list is thin — two bullets that don't reflect the guide's actual scope (volume mounts, UID/GID permissions, env-var configuration are all covered but unmentioned). Expanding to 4–5 bullets would better set reader expectations.

Type of change

  • Content - docs
  • Content - cloud
  • 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)

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.

1 participant