molecule-ai/.github
35
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(profile): add org-profile README + branding assets, document layout convention #1

Merged
claude-ceo-assistant merged 1 commits from docs/profile-readme-and-assets-2026-05-06 into main 2026-05-07 09:24:07 +00:00
Conversation 0 Commits 1 Files Changed 4 +141 -2
claude-ceo-assistant commented 2026-05-07 00:11:14 +00:00
Owner
Copy Link

First content for molecule-ai/.github. Mirrors GitHub's <org>/.github/profile/README.md convention so once GitHub access is restored and repo-sync activates, the file lands on the org page automatically — no path translation step.

What's in the PR

  • profile/README.md — comprehensive org-level intro. Different shape from molecule-core's product-deep README:
    • 1-paragraph pitch
    • 4-bullet "what we ship"
    • "Where to start" routing table (load-bearing — if a visitor only reads this, they still know which repo to open)
    • Repos-in-this-org index split by purpose (product / adapters / marketing)
    • License + community footer
  • profile/assets/molecule-icon.svg + profile/assets/molecule-logo.svg — same brand SVGs that landed on molecule-core PR #5; light/dark adaptive via prefers-color-scheme. Lives self-contained under profile/assets/ so the README is portable.
  • README.md (repo root) — documents the layout convention + names the other cross-org defaults GitHub picks up (CONTRIBUTING.md, SECURITY.md, SUPPORT.md, issue/PR templates, workflow templates).

Diff

README.md                        | 28 +++++++++++--
profile/README.md                | 70 ++++++++++++++++++++++++++++++++
profile/assets/molecule-icon.svg | 28 +++++++++++++
profile/assets/molecule-logo.svg | 17 ++++++++
4 files changed, 141 insertions(+), 2 deletions(-)

Out of scope (parked)

  • CONTRIBUTING.md, SECURITY.md, SUPPORT.md — file when org-wide policy needs cross-repo defaults.
  • GitHub Actions workflow templates — not relevant while we're on Gitea + operator-host deploys.

Review note

Per your guidance, NOT auto-merging — org-profile content is user-visible, deserves a human glance even if the diff looks LGTM.

🤖 Generated with Claude Code

First content for `molecule-ai/.github`. Mirrors GitHub's `<org>/.github/profile/README.md` convention so once GitHub access is restored and repo-sync activates, the file lands on the org page automatically — no path translation step. ## What's in the PR - **`profile/README.md`** — comprehensive org-level intro. Different shape from molecule-core's product-deep README: - 1-paragraph pitch - 4-bullet "what we ship" - **"Where to start" routing table** (load-bearing — if a visitor only reads this, they still know which repo to open) - Repos-in-this-org index split by purpose (product / adapters / marketing) - License + community footer - **`profile/assets/molecule-icon.svg`** + **`profile/assets/molecule-logo.svg`** — same brand SVGs that landed on molecule-core PR #5; light/dark adaptive via `prefers-color-scheme`. Lives self-contained under `profile/assets/` so the README is portable. - **`README.md` (repo root)** — documents the layout convention + names the other cross-org defaults GitHub picks up (`CONTRIBUTING.md`, `SECURITY.md`, `SUPPORT.md`, issue/PR templates, workflow templates). ## Diff ``` README.md | 28 +++++++++++-- profile/README.md | 70 ++++++++++++++++++++++++++++++++ profile/assets/molecule-icon.svg | 28 +++++++++++++ profile/assets/molecule-logo.svg | 17 ++++++++ 4 files changed, 141 insertions(+), 2 deletions(-) ``` ## Out of scope (parked) - `CONTRIBUTING.md`, `SECURITY.md`, `SUPPORT.md` — file when org-wide policy needs cross-repo defaults. - GitHub Actions workflow templates — not relevant while we're on Gitea + operator-host deploys. ## Review note Per your guidance, NOT auto-merging — org-profile content is user-visible, deserves a human glance even if the diff looks LGTM. 🤖 Generated with Claude Code
claude-ceo-assistant added 1 commit 2026-05-07 00:11:14 +00:00 
GitHub renders `<org>/.github/profile/README.md` as the org's public
landing page. Mirroring the same path here on Gitea so once GitHub
access is restored and repo-sync pushes this content over, it lands
in the right place automatically — no path translation step.

## Adds

- `profile/README.md` — comprehensive org-level intro (different from
  molecule-core's product-deep README): pitch in 1 paragraph, "what we
  ship" in 4 bullets, "where to start" routing table, repos-in-this-org
  index split by purpose (product / adapters / marketing), license +
  community footer.
- `profile/assets/molecule-icon.svg` — same SVG that landed on
  molecule-core's README in PR #5; light/dark adaptive via
  prefers-color-scheme styles.
- `profile/assets/molecule-logo.svg` — wordmark variant.

## Updates

- `README.md` (repo root, not user-visible on the org page) — documents
  the layout convention + lists the other cross-org defaults GitHub
  picks up from `<org>/.github/` (CONTRIBUTING.md, SECURITY.md,
  SUPPORT.md, issue/PR templates, workflow templates) so a future
  contributor knows where to add things.

## Why this content shape

GitHub org-profile READMEs are user-visible on the org's public page.
Standard wisdom for that surface:

- short — 1-2 screens, not the deep product pitch (which lives at
  molecule-core)
- routes the reader to the right repo for what they actually want
  (product / SaaS / Claude integration / docs / new runtime)
- lists the major repos with one-line descriptions so a visitor can
  navigate without 30 tabs
- names the license model (BSL 1.1 → Apache 2.0 on 2029-01-01)

The "Where to start" table is the load-bearing piece — the rest is
context. If a visitor only reads the table, they still know where to
go.

## Out of scope (parked)

- CONTRIBUTING.md, SECURITY.md, SUPPORT.md — would normally live here
  too. Skipping for now; current per-repo guidance is fine. File when
  the org has enough cross-cutting policy to warrant it.
- GitHub Actions workflow templates — not relevant while we're on
  Gitea + operator-host deploys.

🤖 Generated with [Claude Code](https://claude.com/claude-code)
claude-ceo-assistant merged commit fbfe7069f5 into main 2026-05-07 09:24:07 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: molecule-ai/.github#1
No description provided.
Delete Branch "docs/profile-readme-and-assets-2026-05-06"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?