You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are various reasons for that, mainly to simplify process on our side and use @szarnyasg competence to the fullest.
We already have a process for updating / iterating the main website, and moving there would allow to centralize a lot of the work.
Extension endpoint will still be (it's baked in duckdb) at: http(s)://community-extensions.duckdb.org/VERSION/PLATFORM/NAME.duckdb_extension[.wasm]
And redirects will be set-up from old to new location.
This would allow shorter iterations in contributing to the docs, and shorter latency in having docs updated.
Extension pages (those at community_extensions/extensions/NAME, for example: https://duckdb.org/community_extensions/extensions/lindel) will still be autogenerated using as source of truth the descriptors AND doing difference between function/settings/etc lists before and after extension is loaded.
This means that to modify a given extension description, example or such a PR would need to be made at duckdb/community-extensions, and this barred minor nit has to be greenlighted by one of the extension maintainers.
It's not properly done, but opening this to inform you of what's happening. This might generate some confusion but it's better done now that later down the road.
If you have feedbacks or improvements you would like to see, feel free to comment here or on the community-extension's channel at https://discord.duckdb.org.
Thanks all!
The text was updated successfully, but these errors were encountered:
We are in the process of move hosting of the documentation from https://community-extensions.duckdb.org/
to https://duckdb.org/community_extensions/
There are various reasons for that, mainly to simplify process on our side and use @szarnyasg competence to the fullest.
We already have a process for updating / iterating the main website, and moving there would allow to centralize a lot of the work.
Extension endpoint will still be (it's baked in duckdb) at:
http(s)://community-extensions.duckdb.org/VERSION/PLATFORM/NAME.duckdb_extension[.wasm]
And redirects will be set-up from old to new location.
This would allow shorter iterations in contributing to the docs, and shorter latency in having docs updated.
Extension pages (those at
community_extensions/extensions/NAME
, for example: https://duckdb.org/community_extensions/extensions/lindel) will still be autogenerated using as source of truth the descriptors AND doing difference between function/settings/etc lists before and after extension is loaded.This means that to modify a given extension description, example or such a PR would need to be made at
duckdb/community-extensions
, and this barred minor nit has to be greenlighted by one of the extension maintainers.General pages (top level at
https://duckdb.org/community_extensions
) like for example https://duckdb.org/community_extensions/development or such will be generated starting from the markdown files at https://github.com/duckdb/duckdb-web/tree/main/community_extensions, and to improve those a PR has to be made atduckdb/duckdb-web
.It's not properly done, but opening this to inform you of what's happening. This might generate some confusion but it's better done now that later down the road.
If you have feedbacks or improvements you would like to see, feel free to comment here or on the community-extension's channel at https://discord.duckdb.org.
Thanks all!
The text was updated successfully, but these errors were encountered: