Open
Conversation
This PR restructures the Tally documentation to prioritize token sales
and ICO content, following a user-journey-focused model similar to
MetaDAO's documentation.
## Changes
### New Structure (7 sections, ~25 new pages)
- **How Token Sales Work**: The Basics, Why Token Sales, Are You Ready?,
Choosing Sale Type, Running Your Sale, After Your Sale
- **Sale Types**: LBPs, CCAs, Fixed-Price (deep dives)
- **Compliance**: KYC, Geo-Restrictions, Vesting & Lockups
- **Post-Launch Tooling**: Governance, Voting, Staking, Security Councils
- **Benefits**: For Projects, For Participants
- **Developers**: API Documentation, Smart Contracts
### Key Improvements
- Shallower navigation (max 2 levels vs previous 4-5)
- Clear user journey: Why → Ready? → Choose → Run → After
- Explicit persona paths (For Projects vs For Participants)
- Governance deprioritized to "Post-Launch Tooling"
- Problem/solution framing before diving into features
### Content Notes
- Pages with `<<TODO: ... >>` markers indicate content that needs
to be written by the team (specific metrics, case studies,
compliance details, API specs, etc.)
- Existing content from token-sales-and-icos.md incorporated
- GPT-5.2 review feedback included in code-reviews/
### GPT-5.2 Review Feedback (see code-reviews/)
Key recommendations for follow-up:
1. Add participant journey pages (how to participate, claims, troubleshooting)
2. Complete compliance TODOs (geo list, KYC providers, disclaimers)
3. Add contract addresses + audit links
4. Include case studies with metrics
5. Consider role-based entry points ("I'm a project" / "I'm a participant")
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR restructures the Tally documentation to prioritize token sales and ICO content, following a user-journey-focused model similar to MetaDAO's documentation.
New Structure (7 sections, ~25 new pages)
Key Improvements
Content Notes
<<TODO: ... >>markers indicate content that needs to be written by the team (specific metrics, case studies, compliance details, API specs, etc.)token-sales-and-icos.mdhas been incorporatedGPT-5.2 Review Recommendations (for follow-up PRs)
Test plan
<<TODO>>markers with actual content🤖 Generated with Claude Code