Driver: Add page about Elixir

[amotl]

About

What the title says.

Preview

https://cratedb-guide--408.org.readthedocs.build/connect/elixir/

[coderabbitai]

Walkthrough

Adds a new Elixir connection guide using Postgrex and updates the Connect index to include an Elixir driver card and toctree entry. Changes are documentation-only (no code or API modifications) and include examples, Docker instructions, and links to an external example repo.

Changes

Cohort / File(s)	Summary
Elixir connect docs docs/connect/elixir.md	New page describing how to connect to CrateDB from Elixir using the Postgrex driver; includes synopsis, sample Mix project, connection/query examples, Docker run instructions, CrateDB Cloud/SSL guidance, external example link, and Postgrex reference.
Connect index updates docs/connect/index.md	Adds an Elixir driver grid-item-card (metadata and image) and inserts elixir into the toctree listing; minor formatting adjustments around the new card.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• Connect: Improve index page #231 — Edits docs/connect/index.md and restructures driver/cards layout; directly related to adding an Elixir card.
• Drivers: Fix broken links. Improve wording. #338 — Adjusts the drivers/grid and connect navigation that this PR extends with an Elixir entry.
• Connect: Reorganize and clean up section #361 — Reorganizes drivers/cards and toctree entries in docs/connect/index.md, overlapping the same area.

Suggested labels

new content, guidance

Suggested reviewers

• kneth
• surister

Poem

A rabbit found docs, bright and spry,
Postgrex crumbs beneath the sky.
I hopped through examples, snug and light,
Elixir + CrateDB — feels just right. 🥕

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description Check	❓ Inconclusive	The pull request description states "What the title says" with a preview link, which is directly related to the changeset that adds an Elixir driver documentation page to the CrateDB guide. The description is not off-topic and does reference the general nature of the changes (adding Elixir documentation). However, the description uses a non-descriptive term ("What the title says") that does not convey any meaningful information about the specific changeset, such as what files are being added, what content is included, or what aspects of Elixir driver integration are being documented.	To make the description more informative and clear, the author should provide specific details about the changeset, such as mentioning that a new Elixir documentation page is being added with usage examples, configuration instructions for both local and cloud deployments, or other key content included in the documentation. This would transform the description from vague placeholder text into something that meaningfully describes the changes being made.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The pull request title "Driver: Add page about Elixir" is clear, concise, and directly related to the main change in the changeset. The raw summary confirms that two documentation files were modified: a new Elixir documentation page was added to docs/connect/elixir.md, and an Elixir entry was added to the drivers section in docs/connect/index.md. The title accurately summarizes this primary objective without being vague or misleading.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch elixir

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}