Skip to content

Rebuild README.md for the Hexclave rebrand#1474

Draft
BilalG1 wants to merge 16 commits into
devfrom
cl/brave-keller-9ac5a8
Draft

Rebuild README.md for the Hexclave rebrand#1474
BilalG1 wants to merge 16 commits into
devfrom
cl/brave-keller-9ac5a8

Conversation

@BilalG1
Copy link
Copy Markdown
Collaborator

@BilalG1 BilalG1 commented May 22, 2026

Summary

Rebuilds the project README from scratch for the Stack Auth → Hexclave rebrand. The previous README was out of date. The README rewrite also surfaced a few stale Stack-Auth references in adjacent docs, which are fixed in the same PR.

README

New structure:

  • Top section: name, "The user infrastructure platform" tagline, intro paragraph, links, and badges
  • Get started: a single AI-agent setup prompt (Read try.hexclave.com and help me setup hexclave in this project)
  • What's included: a catalog of the non-alpha apps (Authentication, Teams, RBAC, API Keys, Payments, Emails, Analytics, Webhooks, Data Vault, Launch Checklist), each with a logo, blurb, and screenshot
  • Contributing: pointer to CONTRIBUTING.md, Discord, and the security contact
  • Contributors: restored at the bottom, now pointing at the correct hexclave/stack-auth repo on contrib.rocks

Note: an explicit SDKs section was intentionally dropped for now — the @hexclave/next, @hexclave/react, @hexclave/js packages aren't yet published under that scope, and surfacing install instructions for unpublished packages would just confuse landing users. The badges in the header still call out the supported SDKs, and the setup prompt routes users to docs. We'll add a dedicated SDKs section once the packages exist.

CONTRIBUTING.md & SECURITY.md

Both still referenced Stack Auth after the README rewrite. Updated:

  • CONTRIBUTING.md: "Stack Auth" → "Hexclave", discord.stack-auth.comdiscord.hexclave.com, docs.stack-auth.comdocs.hexclave.com, security@stack-auth.comsecurity@hexclave.com
  • .github/SECURITY.md: "Stack Auth" → "Hexclave", team@stack-auth.comteam@hexclave.com, security@stack-auth.comsecurity@hexclave.com

This keeps the disclosure flow consistent across the three docs.

Markdown lint / a11y polish

  • Added a text language tag to the bare fenced block under "Get started" (markdownlint MD040)
  • Added alt="" to the 10 inline heading logos (markdownlint MD045) — empty alt is correct here because the heading text immediately to the right already names the section, so the logo is decorative

Open items

A few rebrand details still need confirmation; this PR assumes them and uses them in copy:

  • Domains assumed: hexclave.com, docs.hexclave.com, app.hexclave.com, discord.hexclave.com, security@hexclave.com, team@hexclave.com. Only try.hexclave.com is confirmed.
  • The try.hexclave.com setup-prompt page needs to exist for the Get started flow to work.
  • License and Self-hosting sections were intentionally omitted; the header badges were kept.

Summary by CodeRabbit

  • Documentation
    • Rebranded project from "Stack Auth" to "Hexclave" with a new streamlined README and updated feature list
    • Updated contribution guide to include Hexclave-specific links, require coordination with maintainers on Discord before starting work, and adjusted setup instructions
    • Updated security contact information and policy references
    • Refined table-of-contents workflow to target the contributing guide only

Review Change Stack

Rewrite the README around the new Hexclave name with a revised intro,
an AI-agent setup flow, the apps catalog, an SDK table, and a
contributing section. Fix a stale anchor in CONTRIBUTING.md that
pointed to a README section removed in the rewrite.
@vercel
Copy link
Copy Markdown

vercel Bot commented May 22, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
stack-auth-hosted-components Ready Ready Preview, Comment May 23, 2026 1:28am
stack-auth-mcp Ready Ready Preview, Comment May 23, 2026 1:28am
stack-auth-skills Ready Ready Preview, Comment May 23, 2026 1:28am
stack-backend Ready Ready Preview, Comment May 23, 2026 1:28am
stack-dashboard Ready Ready Preview, Comment May 23, 2026 1:28am
stack-demo Ready Ready Preview, Comment May 23, 2026 1:28am
stack-docs Ready Ready Preview, Comment May 23, 2026 1:28am
stack-preview-backend Ready Ready Preview, Comment May 23, 2026 1:28am
stack-preview-dashboard Ready Ready Preview, Comment May 23, 2026 1:28am

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 22, 2026

📝 Walkthrough

Walkthrough

This PR rebrands repository content from Stack Auth to Hexclave, replaces the README with a Hexclave landing-page and app catalog, updates CONTRIBUTING.md with Hexclave links and a Discord coordination step, narrows the TOC workflow to only process CONTRIBUTING.md, and updates SECURITY.md contacts to Hexclave.

Changes

Documentation Rebranding and Contribution Flow

Layer / File(s) Summary
README Hexclave rebranding and restructure
README.md
README is completely replaced with Hexclave branding: new centered header and tagline, "Get started" quick-prompt section, "What's included" catalog listing Hexclave apps, and new "Contributing" and "❤ Contributors" sections.
Contributing instructions update
CONTRIBUTING.md
CONTRIBUTING.md updated to use Hexclave links and branding, add an explicit step to coordinate with maintainers on Discord before starting code work, adjust the README anchor link, change security contact email to security@hexclave.com, and update Vibecoding .envrc reference.
TOC workflow TARGET_PATHS narrowed
.github/workflows/table-of-contents.yaml
The TOC generator workflow's TARGET_PATHS was narrowed to only CONTRIBUTING.md instead of also matching README patterns.
Security policy contact updates
.github/SECURITY.md
SECURITY.md updated to reference Hexclave and replace support/reporting email addresses and related wording.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

  • hexclave/stack-auth#1448: Pins technote-space/toc-generator action version in the same workflow file; this PR modifies the TARGET_PATHS configuration for that workflow.

Poem

🐰 From Stack to Hexclave, the branding takes flight,
A landing page shines with features in sight,
Ten trusty apps gather in cards so bright,
Discord first, then code—contributions done right! ✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and specifically identifies the main change: rebuilding the README for the Hexclave rebrand, which is the primary focus of the PR.
Description check ✅ Passed The description is comprehensive and well-structured, covering the README changes, updates to CONTRIBUTING.md and SECURITY.md, linting improvements, and open items requiring confirmation. It exceeds the minimal template requirement.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch cl/brave-keller-9ac5a8

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

BilalG1 and others added 3 commits May 22, 2026 15:17
Embed the Hexclave header SVG at the top of the README. Replace the
"What's included" table with a per-app pattern: logo, app name,
description, and dashboard screenshot. Remove the SDKs section.

New assets in .github/assets/: hexclave-header.svg, 10 app logos
cropped from the dashboard apps catalog, and dashboard screenshots
for Analytics and Launch Checklist. The existing storeDesc-*.png
files in apps/dashboard/public/ are reused for the other 8 apps.
BilalG1 added 2 commits May 22, 2026 15:31
Remove the doctoc-generated TOC at the top of the README since it
sat above the centered header and contained stale entries. Embed
the Jersey 10 web font directly into hexclave-header.svg as a
base64 data-URI so the wordmark matches the landing page when
rendered standalone.

In "What's included", drop the per-app dashboard screenshots and
extend each app's one-liner into 1-2 sentences pitching its
specific features. Copy adapted from the per-app pages on the
hexclave landing site. Delete the now-unused screenshot files
from .github/assets/screenshots/.
- Drop the doctoc-generated TOC from README.md. It sat above the
  centered header and contained stale entries after the rewrite.
- Exclude README*.md from the table-of-contents.yaml workflow so
  the bot stops re-adding the TOC on every push. CONTRIBUTING.md
  still gets its TOC generated.
- Embed the Jersey 10 web font into hexclave-header.svg as a
  base64 data-URI so the wordmark matches the landing page when
  rendered standalone.
- In "What's included", drop the per-app dashboard screenshots
  and extend each app's one-liner into 1-2 sentences pitching
  its features. Copy adapted from the per-app pages on the
  hexclave landing site.
- Delete now-unused screenshot files from .github/assets/screenshots/.
- Replace "and many more features, so you don't have to build it
  yourself" with the tighter "and much more" in the intro paragraph.
- Tighten the hexclave-header.svg viewBox from 200x48 to 162x48 so
  it fits the actual content. The old viewBox left ~22% empty space
  on the right, which made the centered logo appear shifted left
  on GitHub.
- Drop "Python" from the SDKs badge. Hexclave does not ship a
  Python SDK; the JS SDK and REST API cover that use case.
Replace the old README with the README-1 experiment (full image-based
'What's included' section) and add a comparison chart above the Get
started section. The chart shows where Hexclave sits on the dev
infrastructure stack (Auth -> Analytics) relative to Vercel, Convex,
Supabase, and Cloudflare.
The original README ended with a '❤ Contributors' section that
rendered the contributor avatar grid via contrib.rocks. The rewrite
dropped it; this puts it back, unchanged, at the very bottom after
Contributing.
@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps Bot commented May 23, 2026

Greptile Summary

This PR replaces the Stack Auth README with a new Hexclave-branded document (feature catalog, AI-agent setup prompt, updated links and badges) and removes README.md from the automated TOC generator. It also patches one broken anchor in CONTRIBUTING.md.

  • README.md: Fully rewritten with a visual feature catalog, comparison diagram, and a one-prompt "Get started" flow; the ## ❤ Contributors image URL still points to the old stack-auth/stack repository, and the SDKs section described in the PR description is missing from the final file.
  • CONTRIBUTING.md: Only the broken anchor was updated — the file title, Discord link, docs links, and security contact email all remain on the old Stack Auth domains, which will send contributors and security reporters to the wrong destination.
  • .github/workflows/table-of-contents.yaml: README.md correctly removed from TOC target paths since the new README has no generated TOC.

Confidence Score: 3/5

The README rewrite itself is clean, but two files carry live broken references that will mislead contributors and security reporters before this is merged.

The contributors image will silently pull from the wrong GitHub repository, and CONTRIBUTING.md still routes Discord, docs, and security emails to the old Stack Auth domains — including the security contact, which could cause real security reports to be missed. These are not theoretical risks; the wrong links are present in the diff as-is.

README.md (contributors image URL) and CONTRIBUTING.md (title, Discord, docs, and security email still reference Stack Auth).

Important Files Changed

Filename Overview
README.md Full rewrite for Hexclave rebrand — new layout, feature catalog with screenshots, and AI-agent setup prompt. Contributors image URL still references the old stack-auth/stack repo; SDKs section described in the PR description is absent.
CONTRIBUTING.md Only the internal anchor link was updated; the file title, Discord URL, docs URLs, and security email all still reference the old Stack Auth brand rather than Hexclave.
.github/workflows/table-of-contents.yaml Removed README.md from the TOC-generator target paths since the new README no longer uses a generated table of contents; CONTRIBUTING.md remains covered.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Visitor opens README.md] --> B{Section}
    B --> C[Get started]
    B --> D[What's included]
    B --> E[Contributing]
    B --> F[❤ Contributors]

    C --> C1["Paste prompt into coding agent\n(tries try.hexclave.com — unconfirmed)"]
    D --> D1[Feature catalog\nAuthentication · Teams · RBAC\nAPI Keys · Payments · Emails\nAnalytics · Webhooks · Data Vault\nLaunch Checklist]
    E --> E2["Links to CONTRIBUTING.md\n(still has old Stack Auth branding)"]
    F --> F1["contrib.rocks image\n⚠ points to stack-auth/stack\nnot hexclave/stack-auth"]
Loading

Comments Outside Diff (2)

  1. README.md, line 180 (link)

    P1 The contrib.rocks URL still points to stack-auth/stack. It should point to the new hexclave/stack-auth repo to reflect the correct contributor list.

    Prompt To Fix With AI
    This is a comment left during a code review.
    Path: README.md
    Line: 180
    
    Comment:
    The `contrib.rocks` URL still points to `stack-auth/stack`. It should point to the new `hexclave/stack-auth` repo to reflect the correct contributor list.
    
    
    
    How can I resolve this? If you propose a fix, please make it concise.
  2. CONTRIBUTING.md, line 1-33 (link)

    P1 Old Stack Auth branding left in CONTRIBUTING.md

    The file title, Discord link (discord.stack-auth.com), documentation links (docs.stack-auth.com), and security contact (security@stack-auth.com) all still use the old Stack Auth identity. The PR updates one anchor in this file but leaves the rest of the Stack Auth references in place. Visitors following those links — including security reporters — will be pointed to the wrong destination now that the rebrand is live.

    Prompt To Fix With AI
    This is a comment left during a code review.
    Path: CONTRIBUTING.md
    Line: 1-33
    
    Comment:
    **Old Stack Auth branding left in CONTRIBUTING.md**
    
    The file title, Discord link (`discord.stack-auth.com`), documentation links (`docs.stack-auth.com`), and security contact (`security@stack-auth.com`) all still use the old Stack Auth identity. The PR updates one anchor in this file but leaves the rest of the Stack Auth references in place. Visitors following those links — including security reporters — will be pointed to the wrong destination now that the rebrand is live.
    
    How can I resolve this? If you propose a fix, please make it concise.
Prompt To Fix All With AI
Fix the following 3 code review issues. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 3
README.md:180
The `contrib.rocks` URL still points to `stack-auth/stack`. It should point to the new `hexclave/stack-auth` repo to reflect the correct contributor list.

```suggestion
  <img src="https://contrib.rocks/image?repo=hexclave/stack-auth&columns=9" width="100%" />
```

### Issue 2 of 3
CONTRIBUTING.md:1-33
**Old Stack Auth branding left in CONTRIBUTING.md**

The file title, Discord link (`discord.stack-auth.com`), documentation links (`docs.stack-auth.com`), and security contact (`security@stack-auth.com`) all still use the old Stack Auth identity. The PR updates one anchor in this file but leaves the rest of the Stack Auth references in place. Visitors following those links — including security reporters — will be pointed to the wrong destination now that the rebrand is live.

### Issue 3 of 3
README.md:27-33
**SDKs section absent despite being listed in the PR description**

The PR description explicitly lists a **SDKs** section (`@hexclave/next`, `@hexclave/react`, `@hexclave/js`, plus the REST API and a docs link) as part of the new structure, but no such section appears in the final README. Developers landing on this page have no quick reference for which packages to install or where the SDK docs live.

Reviews (1): Last reviewed commit: "Restore Contributors section at the bott..." | Re-trigger Greptile

Comment thread README.md
Comment thread CONTRIBUTING.md
Comment thread README.md
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 3

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
README.md (1)

179-180: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Fix contributors image repository mismatch.

The anchor and image point to different repos, so the displayed contributor grid is likely incorrect.

Proposed fix
-  <img src="https://contrib.rocks/image?repo=stack-auth/stack&columns=9" width="100%" />
+  <img src="https://contrib.rocks/image?repo=hexclave/stack-auth&columns=9" width="100%" />
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@README.md` around lines 179 - 180, The contributors anchor and image
reference different repos, causing the wrong contributor grid to display; update
the two attributes so they point to the same repo (make the contrib.rocks ?repo=
value match the anchor href repo). Specifically, edit the anchor href and/or the
img src query param so both reference the same repository identifier (e.g.,
change the img src repo=... or the anchor href to use "hexclave/stack-auth" or
whichever canonical repo name you want) so the contributor image matches the
linked contributors page.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@README.md`:
- Line 43: The inline heading images in README.md (e.g., the heading containing
"### <img src=\".github/assets/logos/authentication.png\" .../> &nbsp;
Authentication") are missing alt attributes; update each heading image tag to
include a descriptive alt attribute (for example alt="Authentication logo" or
alt="Authentication") so they satisfy MD045 and improve accessibility, and apply
the same change to the other similar headings referenced (lines for the logos at
the listed occurrences).
- Around line 31-33: The fenced code block in README.md is missing a language
specifier (triggering markdownlint MD040); update the block around the line
containing "Read try.hexclave.com and help me setup hexclave in this project" to
include a language token (e.g., "text" or "markdown") after the opening triple
backticks so the block becomes ```text ... ``` and the linter passes.
- Line 13: Replace outdated security contact "security@stack-auth.com" with the
canonical "security@hexclave.com" across repository security docs; update
.github/SECURITY.md and CONTRIBUTING.md (and any other files containing the old
address) so the disclosure flow matches README.md, ensuring the security contact
lines and any example report templates or headers reference
security@hexclave.com exactly.

---

Outside diff comments:
In `@README.md`:
- Around line 179-180: The contributors anchor and image reference different
repos, causing the wrong contributor grid to display; update the two attributes
so they point to the same repo (make the contrib.rocks ?repo= value match the
anchor href repo). Specifically, edit the anchor href and/or the img src query
param so both reference the same repository identifier (e.g., change the img src
repo=... or the anchor href to use "hexclave/stack-auth" or whichever canonical
repo name you want) so the contributor image matches the linked contributors
page.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: f906af1f-1aab-48e5-9896-ded558072482

📥 Commits

Reviewing files that changed from the base of the PR and between 05e22e1 and 0719111.

⛔ Files ignored due to path filters (22)
  • .github/assets/app-shots/analytics.png is excluded by !**/*.png
  • .github/assets/app-shots/api-keys.png is excluded by !**/*.png
  • .github/assets/app-shots/authentication.png is excluded by !**/*.png
  • .github/assets/app-shots/data-vault.png is excluded by !**/*.png
  • .github/assets/app-shots/emails.png is excluded by !**/*.png
  • .github/assets/app-shots/launch-checklist.png is excluded by !**/*.png
  • .github/assets/app-shots/payments.png is excluded by !**/*.png
  • .github/assets/app-shots/rbac.png is excluded by !**/*.png
  • .github/assets/app-shots/teams.png is excluded by !**/*.png
  • .github/assets/app-shots/webhooks.png is excluded by !**/*.png
  • .github/assets/comparison.png is excluded by !**/*.png
  • .github/assets/hexclave-header.svg is excluded by !**/*.svg
  • .github/assets/logos/analytics.png is excluded by !**/*.png
  • .github/assets/logos/api-keys.png is excluded by !**/*.png
  • .github/assets/logos/authentication.png is excluded by !**/*.png
  • .github/assets/logos/data-vault.png is excluded by !**/*.png
  • .github/assets/logos/emails.png is excluded by !**/*.png
  • .github/assets/logos/launch-checklist.png is excluded by !**/*.png
  • .github/assets/logos/payments.png is excluded by !**/*.png
  • .github/assets/logos/rbac.png is excluded by !**/*.png
  • .github/assets/logos/teams.png is excluded by !**/*.png
  • .github/assets/logos/webhooks.png is excluded by !**/*.png
📒 Files selected for processing (3)
  • .github/workflows/table-of-contents.yaml
  • CONTRIBUTING.md
  • README.md

Comment thread README.md
Comment thread README.md Outdated
Comment thread README.md Outdated
… lint and contrib.rocks URL

- CONTRIBUTING.md: replace Stack Auth branding/domains/security email with Hexclave equivalents
- .github/SECURITY.md: same rebrand (security@hexclave.com, team@hexclave.com) so disclosure flow matches README
- README.md: add language to fenced code block (markdownlint MD040), add alt="" to 10 decorative heading logos (MD045), fix contrib.rocks URL to point at hexclave/stack-auth
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@CONTRIBUTING.md`:
- Around line 24-25: Check and correct the contributor-facing Discord link and
security mailbox info: verify that the Discord URL
"https://discord.hexclave.com" resolves publicly (or replace it with the
canonical invite/Discord URL if it does not), ensure the docs link
"https://docs.hexclave.com" remains listed, and update the CONTRIBUTING.md entry
that currently contains those links to the working Discord URL or a note about
alternate community channels; separately verify that the email
"security@hexclave.com" is backed by valid MX records and is actively monitored
for vulnerability reports and, if not, replace or add a monitored contact (or a
vulnerability disclosure process link) in the CONTRIBUTING.md so reporters have
a working, monitored channel.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: cc77d083-54ed-4963-98c2-2c8cf6e12e18

📥 Commits

Reviewing files that changed from the base of the PR and between 0719111 and 3d5e3a1.

📒 Files selected for processing (3)
  • .github/SECURITY.md
  • CONTRIBUTING.md
  • README.md
✅ Files skipped from review due to trivial changes (2)
  • .github/SECURITY.md
  • README.md

Comment thread CONTRIBUTING.md
@github-actions github-actions Bot assigned BilalG1 and unassigned N2D4 May 23, 2026
@BilalG1
Copy link
Copy Markdown
Collaborator Author

BilalG1 commented May 23, 2026

waiting to merge until app.hexclave.com, try.hexclave.com, etc. are all setup

@BilalG1 BilalG1 marked this pull request as draft May 23, 2026 01:48
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