docs(website): publish v0.9.6 and NoSQL plugin community blog posts

Author: debba

src-tauri/Cargo.lock

@@ -0,0 +1,71 @@
+---
+title: "Tabularis Goes NoSQL: Redis Ships, MongoDB and ClickHouse Need You"
+date: "2026-03-07"
+tags: ["nosql", "plugins", "community", "redis", "open-source", "extensibility"]
+excerpt: "The plugin ecosystem is growing beyond SQL. Two Redis drivers have already shipped thanks to community contributors. Now we need experts to push DuckDB, MongoDB, and ClickHouse across the finish line."
+og:
+  title: "Tabularis Goes NoSQL:"
+  accent: "Redis Ships, More Coming."
+  claim: "Two Redis drivers shipped by the community. DuckDB, MongoDB, and ClickHouse need your expertise."
+  image: "/img/screenshot-9.png"
+---
+
+# Tabularis Goes NoSQL: Redis Ships, MongoDB and ClickHouse Need You
+
+When I shipped the plugin system in v0.9.0, the promise was simple: you should not need to wait for us to support your database. Build a driver, list it in the registry, and Tabularis users can use it today. That promise is being kept — and the NoSQL world is where the community has moved fastest.
+
+## Redis: Two Independent Drivers, Both Excellent
+
+Redis is the first NoSQL database to land in the official plugin registry, and it arrived not once but **twice** — two independent implementations from two different contributors, each with a distinct design philosophy.
+
+### Redis (Go)
+
+The first Redis driver comes from [@gzamboni](https://github.com/gzamboni) and is written in Go. It models Redis as a set of **virtual tables**: Strings, Hashes, Lists, Sets, and ZSets each get their own tab in the Tabularis data grid. Write operations — SET, HSET, LPUSH, and the rest — are available directly from the UI without dropping to a terminal. If your team uses Redis as a primary data store and you want a visual interface for daily operations, this is the driver to reach for.
+
+:::plugin redis:::
+
+### Redis (Rust)
+
+The second implementation comes from [@nicholas-papachriston](https://github.com/nicholas-papachriston) and takes a different approach. Written in Rust, it focuses on **Hash and RedisJSON row storage** — treating Redis keys as structured records rather than raw key-value pairs. If you store JSON documents in Redis and want to query and browse them like rows in a table, this driver fits more naturally.
+
+:::plugin redis-rust:::
+
+Two drivers for the same database is not redundancy — it is a sign that the plugin system is working as intended. Different use cases, different mental models, different implementations. Users can pick the one that matches how they use Redis.
+
+## The Next Frontier: DuckDB, MongoDB, and ClickHouse
+
+Redis proved the model. Now the ecosystem needs to grow into the rest of the NoSQL and analytical space. Three databases are in active development, and all three could use experienced contributors.
+
+### DuckDB
+
+DuckDB is the reference plugin — the first one we ever shipped — but being first does not mean it is finished. The current driver covers the basics: open a local `.db` file, run queries, browse results. What it does not yet handle well: **in-memory databases**, **Parquet and Arrow file sources** passed directly as connection targets, deeper **type fidelity** for DuckDB-native types like `HUGEINT`, `MAP`, and `UNION`, and **ATTACH/DETACH** multi-database workflows. If you know DuckDB internals and want to make the Tabularis integration best-in-class, the codebase is a Rust project with a clean JSON-RPC interface.
+
+:::plugin duckdb:::
+
+### MongoDB
+
+MongoDB is the most-requested NoSQL database on the issue tracker. A driver is in development but has not yet reached a releasable state. The core challenge is the impedance mismatch: MongoDB documents are schema-less and deeply nested, while Tabularis renders data in a tabular grid. Solving this well — flattening documents intelligently, handling arrays, surfacing the right projection controls in the UI — requires someone who has built against the MongoDB wire protocol before.
+
+If you have experience with the MongoDB Rust driver, the Node.js driver, or the Go official driver, and you want to bring full MongoDB support to Tabularis, [open a discussion on GitHub](https://github.com/debba/tabularis) or reach out directly. The JSON-RPC protocol is documented in the [Plugin Guide](https://github.com/debba/tabularis/blob/main/plugins/PLUGIN_GUIDE.md) and a skeleton implementation is included to get you started quickly.
+
+### ClickHouse
+
+The ClickHouse plugin landed in the registry at v0.1.0 — it connects, authenticates, and runs queries. That is a foundation, not a finished product. ClickHouse has a rich type system (tuples, maps, nested arrays, nullable variants), a native HTTP and binary protocol, and features like **distributed tables**, **materialized views**, and **TTL policies** that deserve first-class representation in the UI. The driver today exposes none of that.
+
+If you work with ClickHouse at scale and know what a power user actually needs from a GUI client, the v0.1.0 driver is a starting point. Help shape what v1.0 looks like.
+
+:::plugin clickhouse:::
+
+## How to Contribute
+
+The plugin protocol is language-agnostic. MongoDB contributors have used Go, Rust, Python, and Node.js in existing plugins — pick the runtime you are most productive in. What matters is the JSON-RPC 2.0 interface over stdin/stdout.
+
+Start here:
+
+1. Read the **[Plugin Guide](https://github.com/debba/tabularis/blob/main/plugins/PLUGIN_GUIDE.md)** — covers the full protocol, manifest format, and type system.
+2. Clone an existing plugin as a reference. The [DuckDB plugin](https://github.com/debba/tabularis-duckdb-plugin) (Rust) and the [CSV plugin](https://github.com/debba/tabularis-csv-plugin) (Python) are both intentionally simple and well-commented.
+3. Open an issue or discussion on the [main repo](https://github.com/debba/tabularis) before starting, so we can coordinate and avoid duplicate work.
+
+The Redis contributions showed what happens when someone with domain expertise builds for their own use case: two production-quality drivers shipped in a matter of weeks. DuckDB, MongoDB, and ClickHouse deserve the same treatment. If you have the expertise, we have the platform.
+
+:::contributors:::

website/content/posts/nosql-plugins-community.md

@@ -0,0 +1,76 @@
+---
+title: "Smarter Filters, Close Tab, and a Better Plugin Install: v0.9.6"
+date: "2026-03-07"
+release: "v0.9.6"
+tags: ["release", "filters", "plugins", "ux", "bugfix"]
+excerpt: "v0.9.6 ships a structured filter toolbar with ORDER BY autocomplete, a close-tab keyboard shortcut, a cleaner plugin install error experience, and a handful of focused bug fixes."
+og:
+  title: "Smarter Filters,"
+  accent: "v0.9.6."
+  claim: "Structured filter toolbar, ORDER BY autocomplete, close-tab shortcut, and a cleaner plugin install flow."
+  image: "/img/screenshot-9.png"
+---
+
+# Smarter Filters, Close Tab, and a Better Plugin Install: v0.9.6
+
+**v0.9.6** focuses on the day-to-day editing experience: a structured filter toolbar that handles the common filtering case without writing SQL, ORDER BY autocomplete in the toolbar, a close-tab keyboard shortcut, and a plugin install error modal that finally tells you what went wrong.
+
+---
+
+## Structured Filter Toolbar and ORDER BY Autocomplete
+
+The table toolbar has grown two new capabilities that make filtering and sorting larger datasets faster without writing raw SQL.
+
+### Structured Filter UI
+
+The filter toolbar now supports **structured filter expressions** — column, operator, and value entered as discrete fields rather than as a typed WHERE clause. The column list is autocompleted from the schema; operators adapt to the column type (text gets `=`, `!=`, `LIKE`, `NOT LIKE`; numbers and dates get the full comparison set). Multiple filters chain with AND by default.
+
+This does not replace the ability to type a raw WHERE clause — the raw input is still there for complex predicates. The structured mode handles the common case of "show me rows where status = active and created_at > last week" without requiring SQL knowledge.
+
+### ORDER BY Autocomplete
+
+The ORDER BY field in the toolbar now autocompletes column names from the current table or query result. Start typing a column name and a dropdown narrows the list. Selecting a column appends `ASC` by default; a toggle switches it to `DESC`. Compound sorts across multiple columns are supported.
+
+---
+
+## Close Tab Keyboard Shortcut
+
+The editor tab bar now responds to a close-tab shortcut:
+
+| Platform | Shortcut |
+| :--- | :--- |
+| macOS | `⌘+W` |
+| Windows / Linux | `Ctrl+W` |
+
+If the tab has unsaved query changes, a confirmation prompt appears before closing. If the content is clean, the tab closes immediately. The shortcut is rebindable from **Settings → Keyboard Shortcuts** like all other custom bindings.
+
+---
+
+## Plugin Install Error Modal
+
+Until now, a failed plugin installation was silent — the progress spinner would stop and the registry panel would return to idle with no indication of what went wrong. v0.9.6 adds a dedicated **Install Error modal** that surfaces the full error output from the installer.
+
+If a download times out, an asset hash mismatches, or the archive is malformed, you now see the exact error message and which step failed. The modal includes a copy button for sharing the log when opening an issue. Installer logging is also more detailed internally, so the stack trace reaching the modal is actionable rather than a generic failure code.
+
+---
+
+## Bug Fixes
+
+### Connection Dialog: Autocomplete and Autocorrect Disabled
+
+Browser and OS autocomplete surfaces were interfering with connection form inputs — particularly the host, port, username, and database fields. On macOS, autocorrect was silently mangling hostnames. Both issues are fixed:
+
+- `autoComplete="off"` is now set on all connection dialog inputs, preventing browser credential and history suggestions from appearing.
+- The macOS `autoCorrect`, `autoCapitalize`, and `spellCheck` attributes are disabled on the same fields.
+
+### Website: Badge Image CSP Rule Scoped to shields.io
+
+A Content Security Policy rule for badge images was written too broadly, allowing any external image source where only `shields.io` badge URLs are used. The rule is now scoped to `shields.io` specifically.
+
+---
+
+:::contributors:::
+
+---
+
+_v0.9.6 is available now. Update via the in-app updater, or download from the releases page._

website/content/posts/v096-redis-clickhouse-filters.md

@@ -1,6 +1,6 @@
 /// <reference types="next" />
 /// <reference types="next/image-types/global" />
-import "./.next/types/routes.d.ts";
+import "./.next/dev/types/routes.d.ts";
 
 // NOTE: This file should not be edited
 // see https://nextjs.org/docs/app/api-reference/config/typescript for more information.

website/next-env.d.ts

@@ -1739,7 +1739,7 @@ pre {
     text-decoration: none;
     color: var(--text-bright);
     transition: border-color 0.15s, background 0.15s, transform 0.15s;
-    min-width: 88px;
+    width: 100px;
 }
 
 .contributor-item:hover {
@@ -1749,12 +1749,16 @@ pre {
     color: var(--accent);
 }
 
-.contributor-avatar {
+.contributor-avatar,
+.post-content .contributor-avatar {
     width: 52px;
     height: 52px;
-    border-radius: 50%;
+    border-radius: 8px;
     border: 2px solid var(--border);
     display: block;
+    object-fit: cover;
+    margin: 0;
+    box-shadow: none;
     transition: border-color 0.15s;
 }
 
@@ -1767,6 +1771,9 @@ pre {
     font-size: 0.75rem;
     font-weight: 500;
     white-space: nowrap;
+    overflow: hidden;
+    text-overflow: ellipsis;
+    max-width: 100%;
 }
 
 /* SEARCH OVERLAY */

website/src/app/globals.css

@@ -156,7 +156,7 @@ function renderContributorsHtml(usernames: string[], release?: string): string {
     .map(
       (u) =>
         `<a class="contributor-item" href="https://github.com/${u}" target="_blank" rel="noopener noreferrer">` +
-        `<img src="https://github.com/${u}.png?size=64" alt="${u}" class="contributor-avatar" />` +
+        `<img src="https://github.com/${u}.png?size=64" alt="${u}" class="contributor-avatar" width="52" height="52" />` +
         `<span class="contributor-name">@${u}</span>` +
         `</a>`,
     )