Feature/Connectivity: Rework page

[amotl]

Problem

The Feature » Connectivity page wasn't in a good shape yet. @kneth discovered that recently.

Solution

This patch intends to converge the page into the same layout/shape/style like all the others in the "All Features" section, using the same compact backbone made of "Intro", "Synopsis", and "Learn" subsections.

Preview

https://cratedb-guide--135.org.readthedocs.build/feature/connectivity/

Review

• Please visit inline comments.
• We believe the "tabs" approach will not scale, so we diverted using the "dropdowns" approach, currently showing both variants. Please advise.

Details

This refactors a bit of content from a few sibling pages in crate-clients-tools. ¹

• https://github.com/crate/crate-clients-tools/tree/main/docs/connect
• https://cratedb.com/docs/crate/clients-tools/en/latest/connect/

Demonstrate two different variants for single-page client-/driver-snippets presentation, one using tabs, and another one using dropdowns.

Footnotes

1. crate-clients-tools might be dissolved in the future, in order to reduce maintenance overhead, so it's a good idea to migrate content gradually. ↩

[amotl]

That's the "tabbed" variant. We think it will not scale, and nesting tabs is also debatable.

[kneth]

I agree, on a small screen (14 in laptop) it is not an optimal solution

[amotl]

That's the "dropdown" variant, already using nested dropdowns, immediately applicable with PHP and Python for example, as there are many driver variants for them, across two families (HTTP vs. PostgreSQL), which stretches all axes of the system needed to represent those.

We are biased to use this variant, and drop the "tabbed" variant again. wdyt?

[amotl]

The main question to you here is if you agree to continue with the "dropdown" variant, because the "tabbed" variant doesn't scale well. Thanks!

[kneth]

If we go with the "tabbed" variant, I think we should pick 3-4 items only. So if we want to have all items, the "dropdown" variant might be better.

[amotl]

Thanks. I tried to present both variants without many initial plans, and just related to a recent comment from your pen that you like "tabbed" approaches of information conveyance, if I got that right.

What do you think how we should proceed on this particular matter?

[amotl]

I agree, on a small screen (14 in laptop), "tabbed" variant is not an optimal solution.

It looks like I've missed your other reply. Thanks!

[amotl]

Thanks for your suggestions. I've diverted corresponding updates into a separate patch that needs more love, in order to get this one merged.

• Feature/Connectivity: Add minimal code snippets for individual drivers #138

[kneth]

I have only minor suggestions

[kneth]

Suggested change

	All the CrateDB connectivity options at a glance.
	CrateDB connectivity options at a glance.

[kneth]

please consider to add a comment here about the two different drivers

[amotl]

Thanks. Do you agree with that variant?

cratedb-guide/docs/feature/connectivity/index.md

Lines 183 to 197 in 525483f

	// You can use both drivers, vanilla pgJDBC, or CrateDB's pgJDBC.
	String dburi = "jdbc:crate://localhost:5432/";
	String dburi = "jdbc:postgresql://localhost:5432/";
	public class Main {
	public static void main(String[] args) {
	try {
	Properties properties = new Properties();
	properties.put("user", "crate");
	properties.put("password", "");
	properties.put("ssl", false);
	Connection conn = DriverManager.getConnection(
	dburi,
	properties
	);

• => See: Feature/Connectivity: Add minimal code snippets for individual drivers #138. Please respond there to further improve that section. For example, we could add inline comments or a link to the relevant documentation page, when applicable.