Skip to content

docs: link Discord community in org profile + brand README - #1

Open
hoainho wants to merge 1 commit into
mainfrom
docs/discord-community-readme
Open

docs: link Discord community in org profile + brand README#1
hoainho wants to merge 1 commit into
mainfrom
docs/discord-community-readme

Conversation

@hoainho

@hoainho hoainho commented Jul 25, 2026

Copy link
Copy Markdown
Contributor

Summary

Add the img2threejs Discord community invite (https://discord.gg/8DS8RTyuR) to two org-level READMEs so visitors who land on github.com/img2threejs find the community immediately.

Changes

  • profile/README.md (org home on GitHub)

    • Added Discord badge to the existing badge row (matches the style=flat of the stars + license badges).
    • New ## Community section between ## Contributing and ## Brand, with a for-the-badge CTA + 4 bullets covering: showcase feedback, spec & gate questions, roadmap proposals, reconstruction cook-alongs.
  • brand/README.md (asset docs)

    • Linked the existing discord-avatar-glim row in the Files table to the community invite (so designers know which Discord the avatar ships in).
    • New ## Community section before ## Regenerating the PNGs, pointing brand-change proposals at the #brand channel.

Why a section, not just a badge

The badge answers "is there a Discord?" — the section answers "why should I join?". Each bullet is concrete enough that a reader can tell whether the community is relevant to them without clicking through.

Verification

  • Identity: Hoài Nhớ <nhoxtvt@gmail.com>
  • Branch: docs/discord-community-readme (from origin/main, local main is 0 ahead / 0 behind)
  • Commit: 07c70b6 docs: link Discord community in org profile + brand README
  • Author: Hoài Nhớ <nhoxtvt@gmail.com>
  • Push: git@github-personal.com:img2threejs/.github.git (via personal SSH key)
  • No Co-Authored-By trailer

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.

1 participant