Skip to content

docs: normalize legacy server product name to "ownCloud Classic"#222

Merged
DeepDiver1975 merged 2 commits into
masterfrom
docs/rebrand-owncloud-classic
Jun 23, 2026
Merged

docs: normalize legacy server product name to "ownCloud Classic"#222
DeepDiver1975 merged 2 commits into
masterfrom
docs/rebrand-owncloud-classic

Conversation

@DeepDiver1975

Copy link
Copy Markdown
Member

What

Normalizes the legacy ownCloud server product to its canonical name ownCloud Classic across all user-facing documentation in this repo. Version (10/11) is retained only as trailing information where relevant (e.g. "ownCloud Classic 10").

Normalized: ownCloud Server, owncloud Server, ownCloud Classic Server, and bare ownCloud 10/11.

Why

Part of owncloud/docs#5111 — a coordinated, docs-only rebranding so the legacy product is consistently named ownCloud Classic across the owncloud / owncloud-docker orgs. Reference implementation: owncloud/docs-main#187.

Out of scope (intentionally untouched)

  • xref:/include:: targets, module slugs (classic_ui, oc10-app), URLs, attribute names (e.g. oc10-api-url), image paths, anchors
  • The new product names: ownCloud Infinite Scale / oCIS

Verification

  • All target variants normalized; only prose / headings / link display text changed.
  • Every xref/include/URL target byte-for-byte identical before/after.
  • oCIS / Infinite Scale occurrence count unchanged.
  • No internal xref depends on any heading whose auto-generated anchor changes.

Reviewer checklist

  • No xref targets / module slugs / URLs altered
  • oCIS / Infinite Scale untouched
  • Version shown only as additional info ("ownCloud Classic 10")

🤖 Generated with Claude Code

Rename the legacy ownCloud server product to its canonical name
"ownCloud Classic" across all user-facing documentation text. The
version (10/11) is kept only as trailing information where relevant
(e.g. "ownCloud Classic 10").

Normalized variants: "ownCloud Server", "owncloud Server",
"ownCloud Classic Server", and bare "ownCloud 10/11".

Scope is limited to prose, headings and link display text.
xref/include targets, module slugs (classic_ui, oc10-app), URLs,
attribute names (e.g. oc10-api-url), image paths, anchors, and the
new product names (ownCloud Infinite Scale / oCIS) are unchanged.

Verified: every URL/xref target byte-identical and oCIS/Infinite
Scale occurrences unchanged.

Part of owncloud/docs#5111

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Signed-off-by: Thomas Müller <1005065+DeepDiver1975@users.noreply.github.com>

@DeepDiver1975 DeepDiver1975 left a comment

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 Automated review by Claude Code review agent.

Verified prose-only product-name normalization ("ownCloud Server" → "ownCloud Classic"). 7 files, 16 lines — the largest of the fleet, checked carefully:

  • README.md: prose + Markdown link text only; the GitHub URLs are unchanged.
  • index.adoc / web_for_users.adoc / index.adoc(owncloud_web) / nav.adoc: every xref: change touches only the bracketed display text — targets ({latest-server-version}@server:classic_ui:index.adoc, web_with_oc_server.adoc, owncloud_web:web_with_oc_server.adoc) are byte-for-byte unchanged. The image: macro target and {oc-marketplace-url} attribute are untouched.
  • web_with_oc_server.adoc: page title (= ...) and :description: attribute are display text; the file is NOT renamed, so no broken inbound xref/alias.
  • web-configuration.adoc: a table cell value ("ownCloud Classic address"); the server config key it documents is unchanged.

No :page-aliases:, module slugs, file names, anchors, or code/command literals altered. "Build documentation" + lint checks pass (Antora build is the authoritative xref guard, and it's green). No changelog in this repo (n/a). LGTM.

Two follow-ups to the "ownCloud Classic" rename:

1. Strip the now-redundant "10" from bare "ownCloud Classic 10"
   references where the version carries no meaning. Specific release
   references (e.g. "ownCloud Classic >= 10.8") keep their version.

2. Where replacing the noun "Server" with the adjective-final
   "Classic" left a dangling sentence, restore the common noun
   ("...used with an ownCloud Classic server.").

xref/include targets, module slugs, URLs and oCIS / Infinite Scale
references are unchanged.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Signed-off-by: Thomas Müller <1005065+DeepDiver1975@users.noreply.github.com>

@DeepDiver1975 DeepDiver1975 left a comment

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 Automated review by Claude Code review agent.

Re-reviewed the current HEAD (7 files, prose-only) for the legacy server product-name → "ownCloud Classic" normalization.

Verified:

  • All edits are display-text/prose only. No xref: targets, file names, module slugs, anchors, image refs, or attribute names altered.
  • xref:{latest-server-version}@server:classic_ui:index.adoc[ownCloud Classic UI] and xref:web_with_oc_server.adoc[...] (incl. nav.adoc) — only the bracketed link labels changed; targets and the web_with_oc_server slug are untouched.
  • image:{latest-server-version}@server:classic_ui:files_page.png and {oc-marketplace-url} refs unchanged.
  • :description: value and page title = heading are rendered prose — appropriate to change.
  • README.md links unchanged (only surrounding text).
  • Version strings left intact where genuine ("ownCloud Server >= 10.8" → "ownCloud Classic >= 10.8" is a correct product-name swap, version preserved).
  • Checks green: Build documentation (Antora xref guard) pass, lint pass.

No changelog in this repo — n/a.

LGTM. Clean prose normalization; previous clean review still holds for the updated HEAD.

@DeepDiver1975 DeepDiver1975 merged commit 24b4f22 into master Jun 23, 2026
2 checks passed
@DeepDiver1975 DeepDiver1975 deleted the docs/rebrand-owncloud-classic branch June 23, 2026 13:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants