diff --git a/client/pages/docs/DocsGettingStarted.tsx b/client/pages/docs/DocsGettingStarted.tsx index 49eeb01a..eef1df5c 100644 --- a/client/pages/docs/DocsGettingStarted.tsx +++ b/client/pages/docs/DocsGettingStarted.tsx @@ -60,7 +60,7 @@ const prerequisites = [ description: "You will need an active AeThex account to access the dashboard, API console, and deployment tools.", actionLabel: "Create account", - actionHref: "/get-started", + actionHref: "/onboarding", }, { title: "Node.js 18+ & npm", @@ -209,34 +209,79 @@ export default function DocsGettingStarted() {

+ {/* NEW: Create an AeThex Account - Full step-by-step */} +
+
+ +

Create an AeThex account (full)

+
+ +
+ + + Step 1 — Choose sign-in method + AeThex supports Email/password, OAuth providers, and Web3 wallet sign-in. + + +
    +
  1. + Email sign-up: go to /signup, provide your email and a secure password. A verification email will be sent — click the link to confirm. +
    2. +
  2. + Google / GitHub: click the provider button on /login. The first time you sign in we'll create your account automatically using the provider email. +
    3. +
  3. + Discord: use "Continue with Discord" on the login page. Existing accounts with the same email will be linked, otherwise a new account is created. For linking flows for existing staff, see the Dashboard > Connections. +
    4. +
  4. + Web3 (optional): sign-in with Ethereum wallet via MetaMask — used only for wallet verification and account linking (no custody). +
    5. +
+ + + + + + Step 2 — Verify & complete profile + After initial login you'll be prompted to complete onboarding (profile, bio, primary arm). + + +
    +
  1. Check your email and follow the verification link (email provider flow).
    2. +
  2. Complete the onboarding steps including name, bio, interests, and primary arm selection.
    3. +
  3. Link any additional providers from Dashboard → Connections if needed.
    4. +
  4. Once finished click "Finish & Go to Dashboard" to start using the platform.
    5. +
+ + +
+ +
+ Notes & troubleshooting + +
+
+
-

- Documentation categories -

+

Documentation categories

- Jump into the area you need most. Each category below is mirrored in - Builder CMS for collaborative editing. + Jump into the area you need most. Each category below is mirrored in Builder CMS for collaborative editing.

{docCategories.map((category) => ( - + -
+
{category.docs} docs
- - {category.title} - - - {category.description} - + {category.title} + {category.description}
    @@ -263,16 +308,9 @@ export default function DocsGettingStarted() { - - {item.description} - + {item.description}
+
+
+ +

Onboarding — what to expect

+
+
+

Onboarding is a guided, multi-step flow that helps users complete the essential profile and platform setup. Typical onboarding steps:

+
    +
  1. Personal Info — name, display handle, avatar.
    2. +
  2. Profile Type — select experience level and role (creator, studio, enterprise).
    3. +
  3. Interests & Skills — choose tags so we can recommend opportunities and mentors.
    4. +
  4. Choose Primary Arm — pick the arm that best represents your work (Labs, GameForge, Corp, Foundation, Dev-Link).
    5. +
  5. Creator Profile — optional portfolio, bio, links (recommended for discoverability).
    6. +
  6. Finish — background tasks run (profile refresh) and you land on the dashboard.
    7. +
+

You can always update these later from Profile → Settings.

+
+
+
-

- Explore the platform -

+

Explore the platform

{platformHighlights.map((item) => { const Icon = item.icon; return ( - + @@ -304,9 +356,7 @@ export default function DocsGettingStarted() { - - {item.description} - + {item.description} ); @@ -323,20 +373,12 @@ export default function DocsGettingStarted() { {setupSteps.map((step, index) => ( - - Step {index + 1} - - - {step.title} - - - {step.description} - + Step {index + 1} + {step.title} + {step.description} - 
-                  {step.command}
-
+ 
{step.command}
 ))} @@ -347,101 +389,44 @@ export default function DocsGettingStarted() { {deploymentChecklist.map((item) => ( - - - {item.title} - + {item.title} -

- {item.description} -

+

{item.description}

 ))}
-
-
- -

Next steps

+
+

Staff editing & governance

+
+

This public documentation is the platform-facing view. Internal operational documents remain private under /internal-docs.

+

Editors (staff) can edit public docs using Builder CMS. After changes are reviewed in Builder, create a GitHub PR to push finalized content into the repository so it can be deployed with site updates.

+
    +
  • Edit in Builder: Open the MCP popover and select Builder.io to edit live doc components and page content. (Staff only)
    • +
  • Publish workflow: Use the Builder preview to validate changes, then export or commit the markdown/content and open a GitHub PR for review. CI runs will deploy the updated public docs.
    • +
  • Security: Internal API references are intentionally not included in public docs. If you need to publish API guides for partners, request a gated partner docs area.
    • +
+
+ +
+

Next steps

{explorationLinks.map((link) => ( - + - - {link.title} - - - - {link.description} - + {link.title} + {link.description} - + ))}
- -
-
-
-

- Ready to automate your first deployment? -

-

- Run{" "} - - aethex deploy - {" "} - once you have verified environment variables, migrations, and - smoke tests. Ship changes with confidence knowing guardrails are - enabled by default. -

-
-
- - -
-
-
); -} +} \ No newline at end of file