Skip to content

Quill troubleshooting and FAQ pages - #2684

Merged
ppekrol merged 10 commits into
ravendb:mainfrom
reebhub:quill_ts_faq
Oct 26, 2026
Merged

ppekrol merged 10 commits into
ravendb:mainfrom
reebhub:quill_ts_faq

Conversation

@reebhub

@reebhub reebhub commented Sep 29, 2026

Copy link
Copy Markdown
Contributor

Issue link

RDoc-4067 Quill troubleshooting
RDoc-4117 Quill FAQ

Additional description

Added /quill/troubleshooting and /quill/faq, fixes and updates to other Quill pages

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)

Comment thread quill/developer-access/ravendb-client-access.mdx Outdated
Comment thread quill/troubleshooting.mdx Outdated
@reebhub
reebhub requested a review from Lwiel September 30, 2026 13:12
Comment thread quill/faq.mdx Outdated
Comment thread quill/faq.mdx Outdated
Comment thread quill/faq.mdx Outdated
Comment thread quill/faq.mdx Outdated
Comment thread quill/faq.mdx Outdated
Comment thread quill/faq.mdx Outdated
…he channel pages' Troubleshooting sections with term and link changes after unifying channel terms, and add `Deleting a connection string fails with a list of its uses` and `The dashboard shows no WRU figures` troubleshooting entries.
Comment thread quill/troubleshooting.mdx

`docker run` fails with an error that port 443 is already allocated, already in use, or not available.

<Admonition type="note" title="">

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.

I don't like using admonition here, it looks cluttered
Image

@reebhub reebhub Oct 26, 2026 •

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

you mean the admonition for the cause / likely cause?
true, for the short entries this is not really needed. but many of the entries include multiple cases/answers for the same cause / likely cause, and for these (e.g. in "The agent's configuration is refused" and many others) it is really important to make the cause stand out above them, and trying out many kinds of formats showed me that framing the cause is the best (and least cluttering) option.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

or if you mean the content frames, same thing - many of the entries include multiple sub-entries and discussions, not gathering them in distinct frames produces a very confusing organization, hard to tell the entries apart and see the relations within each entry clearly

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

e.g.
image

@ppekrol
ppekrol merged commit af16e62 into ravendb:main Oct 26, 2026
1 check passed
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.

5 participants