mirror of
https://github.com/lancedb/lancedb.git
synced 2026-11-13 14:16:54 +00:00
docs: link home page sections through /index (#4740)
## Summary Changes links to home page sections from `/#<anchor>` to `/index#<anchor>`. The docs site's Assemble CI fails `mint broken-links --check-anchors` on every `/#architecture` link since #4732 moved the Architecture page onto the home page. The anchor exists; Mint 4.2.888's checker can't resolve any anchor on the root page `/`, but resolves `/index#…`. `docs.lancedb.com/index` serves the home page, so readers land in the same place. Verified by assembling the site with this change and the matching Enterprise docs change: `mint validate` passes and `mint broken-links --check-anchors --check-redirects` finds no broken links. The `docs.json` redirects keep `/#architecture`, which the checker accepts. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5.5
parent
1d15bb3ada
commit
dcddd541c8
@@ -88,4 +88,4 @@ cannot undo `drop_table`.
|
||||
- [Cleanup](/maintenance/cleanup): configure retention and understand protected versions.
|
||||
- [Jobs](/basics/jobs): distinguish submission, completion and cancellation.
|
||||
- [Refresh a computed column](/feature-engineering/refresh-column): understand partial progress.
|
||||
- [Architecture](/#architecture): understand storage and background maintenance.
|
||||
- [Architecture](/index#architecture): understand storage and background maintenance.
|
||||
|
||||
@@ -42,4 +42,4 @@ those fields together.
|
||||
- [Lance format specification](https://lance.org/format): how the format works.
|
||||
- [Table versioning](/management/table#versioning): read and manage table versions.
|
||||
- [Computed columns](/feature-engineering/add-computed-column): add derived features to your data.
|
||||
- [Architecture](/#architecture): how LanceDB Embedded and Enterprise build on Lance.
|
||||
- [Architecture](/index#architecture): how LanceDB Embedded and Enterprise build on Lance.
|
||||
|
||||
@@ -10,7 +10,7 @@ keywords: ["benchmarks", "performance", "throughput", "latency"]
|
||||
|
||||
This page describes a LanceDB Enterprise capability. The embedded form
|
||||
of LanceDB has no server to provide it. See
|
||||
[Architecture](/#architecture) for what differs between the two.
|
||||
[Architecture](/index#architecture) for what differs between the two.
|
||||
|
||||
Benchmark results are specific to a deployment's shape (cluster size, storage
|
||||
class, dataset), so they are published with LanceDB Enterprise.
|
||||
|
||||
@@ -10,7 +10,7 @@ keywords: ["kubernetes", "k8s", "aks", "deployment", "helm"]
|
||||
|
||||
This page describes a LanceDB Enterprise capability. The embedded form
|
||||
of LanceDB has no server to provide it. See
|
||||
[Architecture](/#architecture) for what differs between the two.
|
||||
[Architecture](/index#architecture) for what differs between the two.
|
||||
|
||||
The Kubernetes deployment procedure is published with LanceDB Enterprise. See
|
||||
[LanceDB Enterprise](/enterprise#deployment) for the general shape, and
|
||||
|
||||
@@ -11,7 +11,7 @@ availability:
|
||||
Distributed search spreads index execution, table-data reads, and caching across
|
||||
multiple serving machines in LanceDB Enterprise. Query nodes plan queries and
|
||||
combine results. Plan executors cache index structures and table data and execute
|
||||
the remote work. See [Architecture](/#architecture).
|
||||
the remote work. See [Architecture](/index#architecture).
|
||||
|
||||
## Embedded search {#embedded-search}
|
||||
|
||||
|
||||
@@ -10,7 +10,7 @@ keywords: ["enterprise", "deployment", "cluster"]
|
||||
|
||||
This page describes a LanceDB Enterprise capability. The embedded form
|
||||
of LanceDB has no server to provide it. See
|
||||
[Architecture](/#architecture) for what differs between the two.
|
||||
[Architecture](/index#architecture) for what differs between the two.
|
||||
|
||||
LanceDB Enterprise runs the lakehouse as a service: a control plane for
|
||||
configuration, identity and policy; a data plane serving reads and writes; and
|
||||
@@ -30,7 +30,7 @@ Draft for the Functions release. Add this row to the table above, after SQL:
|
||||
| [Functions](/management/function) | Python running on workers |
|
||||
*/}
|
||||
|
||||
See [Architecture](/#architecture) for the two shapes side by side.
|
||||
See [Architecture](/index#architecture) for the two shapes side by side.
|
||||
|
||||
## Getting a deployment {#deployment}
|
||||
|
||||
@@ -39,4 +39,4 @@ published with LanceDB Enterprise rather than here.
|
||||
[Contact us](https://www.lancedb.com/contact) to get started; see the
|
||||
[Kubernetes deployment guide](/enterprise/deployment/kubernetes) for a worked example.
|
||||
Embedded LanceDB has nothing to deploy: it is a library your process links
|
||||
against -- see [LanceDB Embedded](/#1-lancedb-oss).
|
||||
against. See [LanceDB Embedded](/index#1-lancedb-oss).
|
||||
|
||||
@@ -10,7 +10,7 @@ keywords: ["compliance", "security", "soc2", "encryption", "audit"]
|
||||
|
||||
This page describes a LanceDB Enterprise capability. The embedded form
|
||||
of LanceDB has no server to provide it. See
|
||||
[Architecture](/#architecture) for what differs between the two.
|
||||
[Architecture](/index#architecture) for what differs between the two.
|
||||
|
||||
Compliance posture (certifications, data residency, encryption at rest and in
|
||||
transit, audit logging) is a property of a deployment, so it is documented
|
||||
|
||||
Reference in New Issue
Block a user