feat(posts): render contributors block for release posts

Fetch release contributors from GitHub, inject HTML into markdown, and
add CSS

Author: debba

website/content/posts/ai-assistant.md

@@ -48,6 +48,8 @@ v0.8.0 also adds one-click CSV and JSON export for query results. Run your query
 
 AI assistance is always optional and explicitly opt-in. If you prefer to write every query by hand, nothing changes. But when you need it, it's one tab away.
 
+:::contributors:::
+
 ---
 
 ![AI Settings in Tabularis v0.8.0](../img/screenshot-8.png)

website/content/posts/dump-schemas-and-grid-context-menu.md

@@ -23,9 +23,9 @@ Dump and import operations now work at the **schema level** for PostgreSQL, not
 
 Previously, the only entry point for dump and import was a right-click on a database node. That worked fine for MySQL, but PostgreSQL workflows tend to be organized around schemas — and grabbing a snapshot of a single schema while leaving the rest of the database untouched wasn't possible from within Tabularis.
 
-Now it is. Right-click any schema node in the sidebar and you'll find **Dump Schema** and **Import into Schema**. The workflow is identical to the database-level version: choose what to include (structure, data, table selection), pick a destination file, and Tabularis streams the dump to disk with live elapsed-time feedback. Import works the same way — select a `.sql` file and watch the progress bar.
+Now it is. Right-click any schema node in the sidebar and you'll find **Dump Schema** and **Import into Schema**. Pick a destination file and Tabularis streams the dump to disk with live elapsed-time feedback. Import works the same way — select a `.sql` file and watch the progress bar.
 
-This is especially useful on shared PostgreSQL servers where each application owns its own schema. You can snapshot `app_schema` at any point without having to touch `analytics_schema` or any of the others sitting in the same database.
+This is especially useful on shared PostgreSQL servers where each application owns its own schema. You can snapshot `billing` at any point without having to touch `inventory`, `reporting`, or any of the others sitting in the same database.
 
 ---
 
@@ -63,6 +63,8 @@ Both are fixed. The updater now bypasses the cache when checking for updates, an
 
 ---
 
+:::contributors:::
+
 ## What's Next
 
 Tabularis is growing fast — and with growth comes complexity. The roadmap is full, but so is the bug tracker. Stability and polish will always be a priority alongside new features.

website/content/posts/multi-database-and-shortcuts.md

@@ -110,6 +110,8 @@ When you edited a row in the data grid, the sidebar row counter and summary pane
 
 ---
 
+:::contributors:::
+
 ## What's Next
 
 Multi-database support opens the door to **cross-database autocomplete** in the SQL editor and **ER diagrams spanning multiple databases on the same server**. Both are on the roadmap for the next releases.

website/content/posts/plugin-ecosystem.md

@@ -50,6 +50,8 @@ We shipped the plugin system alongside a reference implementation: [tabularis-du
 
 Install it from Settings → Plugins, point it at your `.db` file, and you have full DuckDB support in under a minute.
 
+:::contributors:::
+
 ## What's Next
 
 The [plugin guide](https://github.com/debba/tabularis/blob/main/plugins/PLUGIN_GUIDE.md) covers the full JSON-RPC protocol, manifest format, data types, and includes a Rust skeleton to get you started. Build a driver for your database, list it in the registry, and Tabularis users can discover it without waiting for an official release.

website/content/posts/plugins-unleashed.md

@@ -142,3 +142,5 @@ The resource data comes from `sysinfo`, a cross-platform Rust crate for system m
 
 The plugin system shipped in v0.9.0 was the foundation. v0.9.2 is the first release where it feels complete: you can install, update, rollback, enable, disable, and monitor plugins without touching the filesystem manually. The CSV plugin shows that building a driver does not require a compiled language. The Task Manager ensures that the processes powering your connections are never a black box.
 
+:::contributors:::
+

website/content/posts/schema-management.md

@@ -45,6 +45,8 @@ It's the clearest way to understand an unfamiliar database at a glance, and it u
 
 Schema work used to mean context-switching to a terminal or opening another tool. v0.5.0 closes that loop.
 
+:::contributors:::
+
 ---
 
 ![Schema Creation Wizard in Tabularis v0.5.0](../img/screenshot-3.png)

website/content/posts/security-and-i18n.md

@@ -45,6 +45,8 @@ A smaller addition from this release: right-clicking an editor tab opens a conte
 
 Neither keychain integration nor i18n is a shiny demo feature. They're infrastructure. Getting them right in v0.6.0 means future releases can focus on capabilities rather than catching up on correctness. That was the point.
 
+:::contributors:::
+
 ---
 
 ![Connection Setup in Tabularis v0.6.0](../img/screenshot-4.png)

website/content/posts/tabularis-in-a-month.md

@@ -62,6 +62,8 @@ This is intentional. Documentation written only by the maintainers reflects only
 
 The wiki belongs to whoever writes it. Consider this an open invitation.
 
+:::contributors:::
+
 ## What's Next
 
 The plugin ecosystem is still young. We want to see drivers for DuckDB, ClickHouse, CockroachDB, and more. We want the registry to grow. We want the community to build things we haven't thought of yet.

website/content/posts/visual-query-builder.md

@@ -39,6 +39,8 @@ Each tab is fully isolated — its own query, its own results, its own paginatio
 
 It sounds basic, but working across multiple queries simultaneously is a fundamental part of how database work actually happens. This change made Tabularis feel like a proper tool.
 
+:::contributors:::
+
 ## What's Next
 
 The visual builder covers the common case well. Future iterations will handle subqueries and CTEs in the canvas. For now, the handoff to the SQL editor is clean enough that there's no real gap.

website/content/wiki/dump-import.md

@@ -36,7 +36,7 @@ The import can be cancelled at any time. Tabularis will close the modal automati
 
 ## Schema-Level Dump & Import (PostgreSQL)
 
-For PostgreSQL connections, dump and import operations are also available at the **schema** level. Right-click any schema node in the sidebar to access **Dump Schema** or **Import into Schema**. The options and workflow are identical to the database-level counterparts, but scope is limited to the selected schema.
+For PostgreSQL connections, dump and import operations are also available at the **schema** level. Right-click any schema node in the sidebar to access **Dump Schema** or **Import into Schema**. The operation covers the entire selected schema and follows the same streaming and cancellation model as the database-level dump.
 
 This is particularly useful when working with multi-schema databases where you want to snapshot or restore a single schema without touching the rest of the database.