Commit c5326f
2026-06-23 02:54:57 Anonymous: Revert accidental docs page content edits| developer-overview.md .. /dev/null | |
| @@ 1,46 0,0 @@ | |
| - | # Developer Overview |
| - | |
| - | This page is the starting point for developers building with AeThex. |
| - | |
| - | AeThex developer work usually falls into one of four categories: |
| - | |
| - | 1. Passport identity integration |
| - | 2. Game or experience integration |
| - | 3. Discord/community integration |
| - | 4. Backend/API automation |
| - | |
| - | --- |
| - | |
| - | ## Common Developer Tasks |
| - | |
| - | | Task | Read Next | |
| - | |---|---| |
| - | | Verify a Passport user | [[Authentication]] | |
| - | | Connect a game | [[Game-Integration]] | |
| - | | Use server APIs | [[API-Reference]] | |
| - | | Add client tools | [[SDKs]] | |
| - | | Receive events | [[Webhooks]] | |
| - | | Connect Discord | [[Discord-Integration]] | |
| - | | Debug an issue | [[Troubleshooting]] | |
| - | |
| - | --- |
| - | |
| - | ## Architecture Pattern |
| - | |
| - | Most integrations use this pattern: |
| - | |
| - | 1. Client requests identity/action. |
| - | 2. Your server validates with AeThex. |
| - | 3. AeThex returns scoped response. |
| - | 4. Your app stores local state as needed. |
| - | 5. Events are synced through APIs or webhooks. |
| - | |
| - | --- |
| - | |
| - | ## Developer Safety |
| - | |
| - | - Keep secrets server-side. |
| - | - Avoid storing unnecessary user data. |
| - | - Validate all callbacks. |
| - | - Retry idempotently. |
| - | - Monitor status and error codes. |