From 90e79512615b99230049445f2e7a95c2e03a0575 Mon Sep 17 00:00:00 2001 From: Gabor Szarnyas Date: Mon, 28 Oct 2024 18:03:49 +0100 Subject: [PATCH] Community Extensions: Extend sidebar tree, use Jekyll links --- _data/menu_ce.json | 4 ++++ _posts/2024-09-09-announcing-duckdb-110.md | 2 +- _posts/2024-09-27-sql-only-extensions.md | 2 +- community_extensions/development.md | 4 ++-- docs/archive/1.0/extensions/community_extensions.md | 2 +- .../operations_manual/securing_duckdb/securing_extensions.md | 2 +- docs/dev/repositories.md | 2 +- docs/extensions/community_extensions.md | 2 +- docs/operations_manual/securing_duckdb/securing_extensions.md | 2 +- 9 files changed, 13 insertions(+), 9 deletions(-) diff --git a/_data/menu_ce.json b/_data/menu_ce.json index 8ca12e831e..07a9844158 100644 --- a/_data/menu_ce.json +++ b/_data/menu_ce.json @@ -12,6 +12,10 @@ "page": "Development", "url": "/community_extensions/development" }, + { + "page": "Download Metrics", + "url": "/community_extensions/download_metrics" + }, { "page": "FAQ", "url": "/community_extensions/faq" diff --git a/_posts/2024-09-09-announcing-duckdb-110.md b/_posts/2024-09-09-announcing-duckdb-110.md index 62210b91d3..3d32e41fd5 100644 --- a/_posts/2024-09-09-announcing-duckdb-110.md +++ b/_posts/2024-09-09-announcing-duckdb-110.md @@ -95,7 +95,7 @@ SELECT (SELECT unnest(range(10))) AS result; ## Community Extensions -Recently we introduced [Community Extensions]({% post_url 2024-07-05-community-extensions %}). Community extensions allow anyone to build extensions for DuckDB, that are then built and distributed by us. The [list of community extensions](/community_extensions/list_of_extensions) has been growing since then. +Recently we introduced [Community Extensions]({% post_url 2024-07-05-community-extensions %}). Community extensions allow anyone to build extensions for DuckDB, that are then built and distributed by us. The [list of community extensions]({% link community_extensions/list_of_extensions.md %}) has been growing since then. In this release, we have been working towards making community extensions easier to build and produce. This release includes a new method of registering extensions [using the C API](https://github.com/duckdb/duckdb/pull/12682) in addition to a lot of extensions to the C API allowing [scalar functions](https://github.com/duckdb/duckdb/pull/11786), [aggregate functions](https://github.com/duckdb/duckdb/pull/13229) and [custom types](https://github.com/duckdb/duckdb/pull/13499) to be defined. These changes will enable building extensions against a stable API, that are smaller in size, that will work across different DuckDB versions. In addition, these changes will enable building extensions in other programming languages in the future. diff --git a/_posts/2024-09-27-sql-only-extensions.md b/_posts/2024-09-27-sql-only-extensions.md index 7ed013b32d..6505dcca58 100644 --- a/_posts/2024-09-27-sql-only-extensions.md +++ b/_posts/2024-09-27-sql-only-extensions.md @@ -219,7 +219,7 @@ Once you are happy with your extension, it's time to share it with the DuckDB co Follow the steps in [the Community Extensions post]({% post_url 2024-07-05-community-extensions %}#developer-experience). A summary of those steps is: -1. Send a PR with a metadata file `description.yml` that contains the description of the extension. For example, the [`h3` Community Extension](/community_extensions/extensions/h3) uses the following YAML configuration: +1. Send a PR with a metadata file `description.yml` that contains the description of the extension. For example, the [`h3` Community Extension]({% link community_extensions/extensions/h3.md %}) uses the following YAML configuration: ```yaml extension: diff --git a/community_extensions/development.md b/community_extensions/development.md index cb88debaf4..0e83b472dc 100644 --- a/community_extensions/development.md +++ b/community_extensions/development.md @@ -14,7 +14,7 @@ The CI/CD chain will automatically build your extension for all supported DuckDB To publish an extension in the DuckDB Community Repository, a Pull Request can be opened in the [Community Repository](https://github.com/duckdb/community-extensions). In the PR, a descriptor file needs to be specified containing all the relevant information of the extension, such as its source repository and version. Checkout the [already existing community extensions](https://github.com/duckdb/community-extensions/tree/main/extensions) for examples. -The Community Repository builds extensions using DuckDB's [CI toolchain](https://github.com/duckdb/extension-ci-tools), this means that +The Community Repository builds extensions using DuckDB's [CI toolchain](https://github.com/duckdb/extension-ci-tools), this means that for your extension needs to be buildable with this toolchain. Fortunately, this is the exact same toolchain as is used by the Extension Template, so for extensions based on the template, this works out of the box. @@ -27,7 +27,7 @@ With DuckDB's Community Extensions being a [relatively new]({% post_url 2024-07- * [extension template](https://github.com/duckdb/extension-template) * [Community Extensions Repository](https://github.com/duckdb/community-extensions) -However, because of the batteries-included nature of the extension template and the [large](/community_extensions) [amount]({% link docs/extensions/core_extensions.md %}) or example extensions, extension development should be relatively straightforward. +However, because of the batteries-included nature of the extension template and the [large]({% link community_extensions/index.md %}) [amount]({% link docs/extensions/core_extensions.md %}) or example extensions, extension development should be relatively straightforward. ## Getting Help diff --git a/docs/archive/1.0/extensions/community_extensions.md b/docs/archive/1.0/extensions/community_extensions.md index 554dcf54f0..67b31d1a3f 100644 --- a/docs/archive/1.0/extensions/community_extensions.md +++ b/docs/archive/1.0/extensions/community_extensions.md @@ -68,4 +68,4 @@ See the [Securing Extensions page]({% link docs/archive/1.0/operations_manual/se ## List of Community Extensions -See the [DuckDB Community Extensions repository site](/community_extensions). +See the [DuckDB Community Extensions repository site]({% link community_extensions/index.md %}). diff --git a/docs/archive/1.0/operations_manual/securing_duckdb/securing_extensions.md b/docs/archive/1.0/operations_manual/securing_duckdb/securing_extensions.md index fa8602bbad..337efd10fd 100644 --- a/docs/archive/1.0/operations_manual/securing_duckdb/securing_extensions.md +++ b/docs/archive/1.0/operations_manual/securing_duckdb/securing_extensions.md @@ -12,7 +12,7 @@ DuckDB extensions are checked on every load using the signature of the binaries. There are currently three categories of extensions: * Signed with a `core` key. Only extensions vetted by the core DuckDB team are signed with these keys. -* Signed with a `community` key. These are open-source extensions distributed via the [DuckDB Community Extensions repository](/community_extensions). +* Signed with a `community` key. These are open-source extensions distributed via the [DuckDB Community Extensions repository]({% link community_extensions/index.md %}). * Unsigned. ## Overview of Security Levels for Extensions diff --git a/docs/dev/repositories.md b/docs/dev/repositories.md index a87c1aecdd..4e4feaef80 100644 --- a/docs/dev/repositories.md +++ b/docs/dev/repositories.md @@ -36,4 +36,4 @@ Several components of DuckDB are maintained in separate repositories. ## Extensions * Core extension repositories are linked in the [Official Extensions page]({% link docs/extensions/core_extensions.md %}) -* Community extensions are built in the [Community Extensions repository](https://github.com/duckdb/community-extensions) +* Community extensions are built in the [Community Extensions repository]({% link community_extensions/index.md %}) diff --git a/docs/extensions/community_extensions.md b/docs/extensions/community_extensions.md index 770097e1fe..a2359e266a 100644 --- a/docs/extensions/community_extensions.md +++ b/docs/extensions/community_extensions.md @@ -32,7 +32,7 @@ HAVING cnt > 10; On load, the extension’s signature is checked, both to ensure platform and versions are compatible, and to verify that the source of the binary is the community extensions repository. Extensions are built, signed and distributed for Linux, macOS, Windows, and WebAssembly. This allows extensions to be available to any DuckDB client using version 1.0.0 and upcoming versions. -For more details, see the [`h3` extension’s documentation](/community_extensions/extensions/h3). +For more details, see the [`h3` extension’s documentation]({% link community_extensions/extensions/h3.md %}). ## Developer Experience diff --git a/docs/operations_manual/securing_duckdb/securing_extensions.md b/docs/operations_manual/securing_duckdb/securing_extensions.md index 15f01f1ffa..fe0bfe25e3 100644 --- a/docs/operations_manual/securing_duckdb/securing_extensions.md +++ b/docs/operations_manual/securing_duckdb/securing_extensions.md @@ -12,7 +12,7 @@ DuckDB extensions are checked on every load using the signature of the binaries. There are currently three categories of extensions: * Signed with a `core` key. Only extensions vetted by the core DuckDB team are signed with these keys. -* Signed with a `community` key. These are open-source extensions distributed via the [DuckDB Community Extensions repository](/community_extensions). +* Signed with a `community` key. These are open-source extensions distributed via the [DuckDB Community Extensions repository]({% link community_extensions/index.md %}). * Unsigned. ## Overview of Security Levels for Extensions