Skip to content

Prune superseded/orphaned API reference pages #182

Description

@digitaldiina

en/api/reference/ contains 4 subfolders that are not referenced anywhere in config/nav-en.json (only config/redirects.json has stale /en/api/reference/soap/... redirect sources pointing at them) — only en/api/reference/restful/ (Agent + REST) is actually wired into the API tab:

  • en/api/reference/soap/ (1 file) — content self-describes as legacy: "Services88 only. Services84 through Services87 are supported but no longer documented."
  • en/api/reference/web/ (1 file) — "SuperOffice CRM Web Application API"
  • en/api/reference/webapi/ (1 file) — "SuperOffice WebApi Client Library"
  • en/api/reference/netserver/ (6 files: index + core/index.mdx, services/index.md, includes/toc)

Scope: for each of the 4 folders, decide keep-and-wire vs. delete-with-redirect vs. redirect-only, following the established single-hop redirect rule if anything is removed. Update the stale config/redirects.json sources pointing at soap/* regardless of the decision.

Explicitly out of scope: the near-duplicate "V2"/"shadow"/"combined" entity variants inside en/api/archive-providers/reference/ and en/api/mdo-providers/reference/ (e.g. appointmentselection, appointmentselectionv2, appointmentselectioncombined, ...). That content is machine-generated and already tracked for a source-level fix under #149 ("Fix archive-providers/mdo-providers reference generator; emit MDX directly") — pruning it here would just get regenerated.

Blocks: the "Improve en/api/ nav structure" follow-up issue (pruning decisions affect what that issue needs to wire).

Metadata

Metadata

Assignees

Labels

Type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions