Skip to content

docs: drop the organization from the name - #513

Merged
uniqueg merged 2 commits into
devfrom
docs/drop-org-from-name
Oct 29, 2026
Merged

uniqueg merged 2 commits into
devfrom
docs/drop-org-from-name

Conversation

@uniqueg

@uniqueg uniqueg commented Oct 29, 2026 •

Copy link
Copy Markdown
Member

Summary

Renames the project from "ELIXIR Cloud Components" to "Cloud Components" in the README (title and text), the contributing guide and the documentation app (site title, introduction, installation, customization, contribute pages): names and titles don't carry organization names.

The ecc- prefix of the components, the ECC abbreviation and the npm scope @elixir-cloud stay, as renaming them would break users. No component code changes.

Closes #512

Verification

Light lane: text only (7 lines in 7 files), diff reviewed by hand, no reviewer subagents. git grep "ELIXIR Cloud Components" finds no other occurrences (outside package-lock.json, which has none either). CI on this PR.

🤖 Generated with Claude Code

Summary by Sourcery

Remove the organization name from the project’s public-facing name without changing its existing package or component identifiers.

Enhancements:

  • Rename the project’s user-facing name to “Cloud Components” across repository and documentation content while retaining existing component identifiers and abbreviations.

Documentation:

  • Update README, contributing guidance, documentation pages, and documentation site metadata to remove the organization name from the project name.

Chores:

  • Refresh the package description to reflect the shortened project name and current community attribution.

Rename "ELIXIR Cloud Components" to "Cloud Components" in the README, the contributing guide and the documentation app. The ecc- prefix, the ECC abbreviation and the npm scope stay.

Closes #512

Co-Authored-By: Claude Opus 5.5 <[email protected]>
@uniqueg
uniqueg requested a review from anuragxxd as a code owner October 29, 2026 15:33
@sourcery-ai

sourcery-ai Bot commented Oct 29, 2026 •

Copy link
Copy Markdown
Contributor
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Removes the organization name from user-facing project and documentation branding, changing “ELIXIR Cloud Components” to “Cloud Components” across seven text and documentation files without modifying component code or compatibility-sensitive identifiers.

File-Level Changes

Change Details Files
Updates public-facing project naming to “Cloud Components” while preserving compatibility identifiers.
  • Renames the README heading and project description.
  • Updates the contributing guide wording.
  • Rebrands documentation site title, introduction, installation, customization, and contribution text.
  • Retains the ECC abbreviation, ecc- component prefix, and @elixir-cloud npm scope.
README.md
CONTRIBUTING.md
apps/documentation/pages/about/contribute.mdx
apps/documentation/pages/docs/customization.mdx
apps/documentation/pages/docs/installation.mdx
apps/documentation/pages/docs/introduction.mdx
apps/documentation/theme.config.tsx

Assessment against linked issues

Issue Objective Addressed Explanation
#512 Rename the project in README text and titles, the contributing guide, and the documentation app’s title and relevant pages from “ELIXIR Cloud Components” to “Cloud Components,” while retaining the ecc- prefix, ECC abbreviation, and @elixir-cloud npm scope. ✅

Possibly linked issues


Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Hey - I've found 2 issues

Prompt for AI Agents
Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="apps/documentation/theme.config.tsx" line_range="13" />
<code_context>
     <div className='flex gap-3 items-center'>
       <Image src={withBasePath('/elixir-cloud/logo.svg')} alt='Logo' width={44} height={44} />
-      <span className='tracking-wide font-semibold'>ELIXIR Cloud Components</span>
+      <span className='tracking-wide font-semibold'>Cloud Components</span>
     </div>
   ),
</code_context>
<issue_to_address>
**Old names remain in page titles**

When a visitor opens a documentation page, `useNextSeoProps` still appends “Elixir Cloud Components” to page titles and SEO metadata, so the renamed site shows the retired name in browser tabs and search results. The default app title also retains the old name.

Update the title template and default app title to use “Cloud Components”.

Also at `apps/documentation/pages/docs/introduction.mdx:12`.
</issue_to_address>

### Comment 2
<location path="apps/documentation/theme.config.tsx" line_range="13" />
<code_context>
     <div className='flex gap-3 items-center'>
       <Image src={withBasePath('/elixir-cloud/logo.svg')} alt='Logo' width={44} height={44} />
-      <span className='tracking-wide font-semibold'>ELIXIR Cloud Components</span>
+      <span className='tracking-wide font-semibold'>Cloud Components</span>
     </div>
   ),
</code_context>
<issue_to_address>
**Old project name remains visible**

When users view a documentation page or inspect the root package metadata, browser titles, the app title, the Providers Overview, and the root package description still use the old organization-bearing project name, so visitors see inconsistent branding despite the updated logo.

Update the remaining project-name references in the SEO title, app title, Providers Overview, and root package description.
</issue_to_address>

Sourcery assessment

Approval pending. 2 findings to address first.

Blocking findings: apps/documentation/theme.config.tsx:13, apps/documentation/theme.config.tsx:13


Sourcery is free for open source - if you like our reviews please consider sharing them ✨

Comment thread apps/documentation/theme.config.tsx Resolved
Comment thread apps/documentation/theme.config.tsx Resolved
@read-the-docs-community

read-the-docs-community Bot commented Oct 29, 2026 •

Copy link
Copy Markdown

Documentation build overview

📚 cloud-components | 🛠️ Build #35501711 | 📁 Comparing 72d7203 against latest (c2c0e1d)

  🔍 Preview build  

5 files changed · ± 5 modified

± Modified

Also the docs' page title template, the providers page and the root package description, which spelled the name "Elixir Cloud Components".

Co-Authored-By: Claude Opus 5.5 <[email protected]>

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Sourcery assessment

Approved.

@uniqueg
uniqueg merged commit 7104e17 into dev Oct 29, 2026
12 checks passed
@uniqueg
uniqueg deleted the docs/drop-org-from-name branch October 29, 2026 15:43
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.

docs: drop the organization from the project name

1 participant