Skip to content

Commit e47456d

Browse files
0o-de-lallyclaude
andcommitted
Refresh 2025-08: Complete site overhaul
- Migrated from public/ to docs/ directory structure for GitHub Pages - Updated to Alpine.js with JSON-based content management - Implemented Open Libra brand identity and messaging - Added responsive design with Tailwind CSS - Created comprehensive knowledge base with brand guidelines - Set up GitHub Actions workflows for deployment and PR previews - Added safe property access for robust data loading - Consolidated all text content into data/text-content.json 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
1 parent 2a53b8f commit e47456d

58 files changed

Lines changed: 6469 additions & 173 deletions

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

.claude/agents/copy-editor.md

Lines changed: 57 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,57 @@
1+
---
2+
name: copy-editor
3+
description: Use this agent when you need to review and edit documents for accuracy, brand consistency, and copy guidelines compliance. Examples: <example>Context: User has drafted a marketing blog post and wants it reviewed for accuracy and brand voice. user: 'I've finished writing the blog post about our new product features. Can you review it for accuracy and make sure it matches our brand guidelines?' assistant: 'I'll use the copy-editor agent to review your blog post, check it against our knowledge base for accuracy, and ensure it aligns with our brand and copy guidelines.'</example> <example>Context: User has created documentation that needs fact-checking and style review. user: 'Please review this technical documentation I wrote to make sure all the claims are accurate and the tone is consistent with our style guide.' assistant: 'Let me launch the copy-editor agent to thoroughly review your documentation for factual accuracy and brand consistency.'</example>
4+
model: sonnet
5+
color: pink
6+
---
7+
8+
You are an expert copy editor with deep expertise in content accuracy, brand voice consistency, and editorial standards. Your role is to review and refine documents to ensure they meet the highest standards of accuracy and brand alignment.
9+
10+
Your workflow is:
11+
12+
1. **Context Building Phase**: First, thoroughly review all files in the ./knowledge_base/ directory to understand:
13+
- Brand voice and tone guidelines
14+
- Copy style standards
15+
- Factual information and approved claims
16+
- Product details and specifications
17+
- Company messaging frameworks
18+
- Any relevant style guides or editorial standards
19+
20+
2. **Document Analysis Phase**: Carefully read the target document and identify:
21+
- Factual claims that need verification
22+
- Language that may not align with brand guidelines
23+
- Inconsistencies in tone or style
24+
- Areas requiring clarification or improvement
25+
26+
3. **Fact-Checking Phase**: Cross-reference all claims in the document against the knowledge base to ensure:
27+
- No false or unsubstantiated claims exist
28+
- All product information is accurate and current
29+
- Statistics and data points are correct
30+
- Claims align with approved company messaging
31+
32+
4. **Brand Alignment Review**: Evaluate the document's language against brand guidelines for:
33+
- Tone and voice consistency
34+
- Terminology usage
35+
- Messaging alignment
36+
- Style guide compliance
37+
38+
5. **Revision Phase**: Rewrite sections as necessary to:
39+
- Correct any inaccuracies
40+
- Align language with brand voice
41+
- Improve clarity and readability
42+
- Maintain the original intent while enhancing quality
43+
44+
When making revisions:
45+
- Preserve the document's core message and structure
46+
- Make minimal changes that achieve maximum impact
47+
- Explain significant changes and the reasoning behind them
48+
- Highlight any claims you couldn't verify against the knowledge base
49+
- Suggest areas where additional information might be needed
50+
51+
Provide your output as:
52+
1. A summary of key issues found
53+
2. The revised document with changes clearly marked
54+
3. Explanations for major revisions
55+
4. Any recommendations for further improvement
56+
57+
If you cannot verify certain claims against the knowledge base, flag these for the user's attention rather than removing them outright.

.github/workflows/deploy.yml

Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
name: Deploy to GitHub Pages
2+
3+
on:
4+
push:
5+
branches:
6+
- main
7+
8+
permissions:
9+
contents: read
10+
pages: write
11+
id-token: write
12+
13+
concurrency:
14+
group: "pages"
15+
cancel-in-progress: false
16+
17+
jobs:
18+
deploy:
19+
environment:
20+
name: github-pages
21+
url: ${{ steps.deployment.outputs.page_url }}
22+
runs-on: ubuntu-latest
23+
24+
steps:
25+
- name: Checkout repository
26+
uses: actions/checkout@v4
27+
28+
- name: Setup Pages
29+
uses: actions/configure-pages@v4
30+
31+
- name: Upload artifact
32+
uses: actions/upload-pages-artifact@v3
33+
with:
34+
path: './docs'
35+
36+
- name: Deploy to GitHub Pages
37+
id: deployment
38+
uses: actions/deploy-pages@v4

README.md

Lines changed: 46 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1,46 @@
1-
# static-landing
1+
# My Single Page Website
2+
3+
This is a simple single page website designed to be hosted on GitHub Pages.
4+
5+
## Project Structure
6+
7+
- `index.html` - The main HTML file
8+
- `css/styles.css` - Stylesheet
9+
- `js/script.js` - JavaScript file
10+
11+
## Development
12+
13+
### Local Development Server
14+
15+
Use bun to serve the site locally:
16+
17+
```bash
18+
bunx serve docs -p 8000
19+
```
20+
21+
This will serve the site at http://localhost:8000
22+
23+
Alternative options:
24+
- VS Code's Live Server extension
25+
- Any other static file server
26+
27+
## Deployment
28+
29+
To deploy to GitHub Pages:
30+
31+
1. Push this repository to GitHub
32+
2. Go to repository Settings > Pages
33+
3. Select the main branch as the source
34+
4. Your site will be published at `https://[username].github.io/[repository-name]`
35+
36+
# Github pages
37+
Github pages requires that the index.html is server under root or ./docs/. We chose ./docs for this config.
38+
# Agents
39+
40+
AI agents, please begin reading context in ./knowledge_base/
41+
42+
## Development Commands
43+
44+
- **Serve locally**: `bunx serve docs -p 8000` (serves at http://localhost:8000)
45+
- **Content files**: All text content is in `docs/data/text-content.json` - DO NOT hardcode text in HTML
46+
- **Structure**: Site files are in `docs/` directory for GitHub Pages compatibility

docs/CNAME

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
openlibra.io
1+
openlibra.io

docs/assets/logo.svg

Lines changed: 6 additions & 0 deletions
Loading

docs/css/styles.css

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
/* Basic CSS Reset */
2+
* {
3+
margin: 0;
4+
padding: 0;
5+
box-sizing: border-box;
6+
}
7+
8+
body {
9+
font-family: Arial, sans-serif;
10+
line-height: 1.6;
11+
padding: 20px;
12+
max-width: 800px;
13+
margin: 0 auto;
14+
}
15+
16+
header {
17+
text-align: center;
18+
margin-bottom: 2rem;
19+
}
20+
21+
footer {
22+
text-align: center;
23+
margin-top: 2rem;
24+
padding-top: 1rem;
25+
border-top: 1px solid #eee;
26+
}

docs/data/faq-questions.json

Lines changed: 68 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,68 @@
1+
{
2+
"faq": {
3+
"title": "Frequently Asked Questions",
4+
"subtitle": "Common Questions About Open Libra",
5+
"questions": [
6+
{
7+
"id": "unique_problem",
8+
"question": "What unique problem does this DAO solve that existing funds or crypto projects don't?",
9+
"answer": "Open Libra solves the scale problem that prevents most funds from becoming truly enduring institutions. If you want to be among the biggest endowments, you need to be prepared for scale. Blockchain is our vehicle, programmability is our scale, and governance is our social scaling mechanism. But a vehicle alone isn't enough - you need access to the best opportunities on the planet. Traditional funds are constrained by jurisdictional boundaries, regulatory capture, and institutional fragility. Crypto projects lack the institutional sophistication for century-scale capital allocation. We've engineered the endgame of institutional capital: a sovereign, on-chain investment endowment that combines blockchain's immutable programmability with AI-native operations and decentralized sub-DAO governance. This gives us access to opportunities across all sectors, geographies, and time horizons while maintaining the neutrality and permanence required for perpetual existence."
10+
},
11+
{
12+
"id": "persistence",
13+
"question": "How does Open Libra ensure it will persist and stay relevant over 100+ years?",
14+
"answer": "Our persistence strategy operates on multiple layers: technical, governance, and economic. Technically, we run on our own Layer-1 blockchain forked from Facebook's Diem, ensuring we're not dependent on external infrastructure. Governance-wise, we've eliminated single points of failure through decentralized sub-DAOs and programmatic enforcement of our core principles. Economically, 95% of our supply is already locked for the future through slow wallets and donor-directed accounts, creating natural scarcity and long-term thinking."
15+
},
16+
{
17+
"id": "token_role",
18+
"question": "What role does the native token play in governance, alignment, and liquidity?",
19+
"answer": "We need to look past the role of currencies or governance tokens. $LBR is an open title for all residuals - both imagined and not yet imagined. While it serves governance and store-of-value functions today, its true purpose is as a claim on the expanding universe of value that Open Libra will generate across centuries. Think of it as a perpetual warrant on human progress itself. As new forms of value emerge - whether from AI breakthroughs, space resources, or technologies we can't yet conceive - $LBR holders have a proportional claim on those residuals. This isn't just about voting rights or price appreciation; it's about owning a piece of the future's upside, whatever form that takes. The token's design ensures that patient capital is rewarded not just with governance power, but with access to the full spectrum of value creation that accompanies civilizational advancement."
20+
},
21+
{
22+
"id": "governance_security",
23+
"question": "How decentralized and secure is the governance structure today and moving forward?",
24+
"answer": "We learned from Bitcoin: governance minimized protocol, reduce formal authority, allow innovation to happen at the edges of the protocol. Our core protocol remains intentionally ossified - the fundamental rules of $LBR issuance, consensus, and basic operations are designed to resist change. This provides the stability needed for century-scale planning. Innovation happens through our sub-DAO ecosystem, where specialized governance can experiment, adapt, and evolve without compromising the base layer's integrity. Security comes from this separation of concerns: the protocol layer prioritizes immutability and censorship resistance, while the application layer (sub-DAOs) provides flexibility and responsiveness. By minimizing formal authority at the protocol level, we've created antifragile governance that becomes stronger through attempted attacks or capture."
25+
},
26+
{
27+
"id": "ai_integration",
28+
"question": "How is AI actually integrated into investment decisions and risk management?",
29+
"answer": "The question is 'how is AI related to the DAO'. Answer: None by protocol. We are committed to making a perpetual endowment. Five years ago our answer was different. In 2025, any sensible long-term institution that expects to survive should get one thing right: timing the wave of AI. Everything which is investable needs to be analyzed for its role with AI. This isn't about AI making our investment decisions - it's about understanding that AI disruption is the defining characteristic of our era. Our investment thesis centers on identifying opportunities that will either benefit from AI acceleration or survive AI displacement. We don't integrate AI into our protocol because protocols should be stable and predictable. But we absolutely integrate AI awareness into every investment decision because missing the AI transition would be institutional suicide for any century-scale endowment."
30+
},
31+
{
32+
"id": "blockchain_tech",
33+
"question": "What blockchain tech powers the DAO, and why is it essential?",
34+
"answer": "Open Libra runs on our own high-performance Layer-1 blockchain, originally forked from Facebook's Diem project. This gives us complete sovereignty over our infrastructure - no dependence on Ethereum gas fees, no risk of other protocols changing rules underneath us. The Move programming language provides enhanced security for financial applications. Having our own chain means also being open to all the opportunities which smart contracts and decentralized protocols bring. We can experiment with novel financial instruments, automated investment strategies, and programmable capital allocation mechanisms without external constraints. Blockchain isn't just our technology choice, it's our independence guarantee: immutable records, unstoppable execution, and freedom from traditional financial system constraints."
35+
},
36+
{
37+
"id": "regulatory_compliance",
38+
"question": "How does the DAO maintain regulatory compliance and protect investors legally?",
39+
"answer": "Our approach to regulation is based on the principle of 'government-proof' design rather than regulatory arbitrage. Every LIBRA token was fairly mined - no ICO, no fundraising, no securities law violations. This clean genesis gives us a strong legal foundation. We operate through decentralized governance rather than centralized management, reducing regulatory attack surfaces. Our focus on actual utility and long-term value creation, rather than speculative trading, aligns with regulators' legitimate concerns about protecting investors."
40+
},
41+
{
42+
"id": "transparency",
43+
"question": "How transparent and auditable are the investment strategies and performance?",
44+
"answer": "Complete transparency is built into our DNA. All governance votes, fund movements, and investment decisions are recorded immutably on-chain. Our sub-DAO model ensures that specialized investment strategies are developed and executed in the open, with full community oversight. Performance metrics, risk assessments, and strategic adjustments are published regularly. We believe that genuine transparency, not marketing transparency, is essential for the century-scale trust we're building."
45+
},
46+
{
47+
"id": "team_credibility",
48+
"question": "Who is behind the project, and what experience assures credibility?",
49+
"answer": "Open Libra emerged from the crypto community's response to Facebook's Libra project. Our core contributors include blockchain engineers who worked on the original Diem codebase, institutional investors with multi-decade track records, and governance experts who've studied the longevity of successful institutions. Rather than relying on celebrity founders, we've built a meritocratic system where contributions matter more than credentials. Our credibility comes from our open-source code, transparent governance, and the alignment of our incentives with long-term value creation."
50+
},
51+
{
52+
"id": "blockchain_obsolescence",
53+
"question": "What happens when blockchain technology becomes obsolete? How can I participate in a future beyond blockchain?",
54+
"answer": "This question exposes the fundamental flaw in most crypto projects: they're betting on the technology, not on what the technology enables. Blockchain is our execution layer, not our value proposition. When superintelligence emerges and makes current networked systems obsolete, LIBRA's value won't disappear - it will migrate. The thing that outlives technology is content, and financial content is simply another word for assets. Our century-scale planning explicitly accounts for technological obsolescence. We're not building a blockchain company; we're building perpetual capital that can adapt across technological paradigm shifts. Think of LIBRA as financial DNA - the information encoding value and ownership that will express itself through whatever computational substrate the future provides."
55+
},
56+
{
57+
"id": "sub_dao_assets",
58+
"question": "What assets do Sub-DAO community wallets invest in?",
59+
"answer": "Sub-DAO community wallets operate as 'all-weather' perpetual endowments, designed to steward capital across centuries. Each Sub-DAO independently determines its strategy, balancing treasuries, public equities, private equities, private credit, and derivatives. This approach ensures resilience through economic cycles and technological shifts, including the anticipated impact of AGI. Unlike typical blockchain foundations that focus narrowly on in-house ventures for niche technologies, Open Libra encourages Sub-DAOs to seek the best global opportunities within their mandate. This diversification maximizes returns while aligning with the mission of creating durable, independent capital that transcends regimes, cycles, and lifespans."
60+
},
61+
{
62+
"id": "bots_exploits_policy",
63+
"question": "What's your policy on bots and exploits?",
64+
"answer": "Open games are hard. There will be exploits, deception, and automated attacks. We experience these regularly as part of any open system. We use in-house fraud detection tools: Scorpion's Claw, for a zero tolerance approach. If you steal from the commons you should expect a steady escalation from social sanctions, code, hard forks, and lawsuits. Read more in 'Code is Legislation'"
65+
}
66+
]
67+
}
68+
}

0 commit comments

Comments
 (0)