Rewrite landing to El component architecture
Full El component split: nav, hero, pillars, inference, pricing, footer, about, enterprise, mission, viral, local_first, comparison, efficiency, environmental. - About page rewritten first-person (Will's voice), photo included, no product spoilers - Stripe checkout wired: env() reads STRIPE_SECRET_KEY/PRICE_* at startup - Minor parent-onboarding callout added to pricing section - Inference pricing: "at cost" removed, now "priced below competitors" - Nav: wordmark image, About link active on /about - .gitignore: excludes .env, dist/, generated HTML
This commit is contained in:
@@ -0,0 +1,89 @@
|
||||
// components/mission.el — Origin story + manifesto + problems grid.
|
||||
|
||||
fn mission() -> String {
|
||||
return "
|
||||
<section id=\"mission\" aria-label=\"Mission\">
|
||||
<div class=\"container\">
|
||||
|
||||
<div class=\"navy-line\" style=\"margin-bottom:5rem\"></div>
|
||||
|
||||
<div class=\"mission-origin\">
|
||||
<div class=\"mission-label-row reveal\">
|
||||
<div class=\"navy-line-left\" style=\"width:4rem;flex-shrink:0\"></div>
|
||||
<span class=\"label\">The mission</span>
|
||||
<div style=\"height:1px;width:4rem;background:linear-gradient(to left,transparent,rgba(0,82,160,.35));flex-shrink:0\"></div>
|
||||
</div>
|
||||
<h2 class=\"display-lg mission-headline reveal\" style=\"transition-delay:80ms\">Why I built this</h2>
|
||||
|
||||
<p class=\"mission-body-para reveal\" style=\"transition-delay:160ms\">
|
||||
Every AI tool you use today resets when you close the tab. It doesn't know you tomorrow. It doesn't remember what mattered yesterday. It can't grow with you over years.
|
||||
</p>
|
||||
<p class=\"mission-body-para reveal\" style=\"transition-delay:240ms\">
|
||||
I built Neuron because intelligence should compound. The same way a great mentor gets more valuable the longer you work with them — knowing your context, your patterns, your goals — your AI should too.
|
||||
</p>
|
||||
<p class=\"mission-body-para mission-body-emphasis reveal\" style=\"transition-delay:320ms\">
|
||||
Neuron is private by design. It runs on your hardware. <strong>Your data never leaves your machine.</strong> No training on your data. No telemetry. No cloud dependency.
|
||||
</p>
|
||||
<p class=\"mission-body-para reveal\" style=\"transition-delay:400ms\">
|
||||
This isn't a chat interface. It's the AI that becomes yours.
|
||||
</p>
|
||||
</div>
|
||||
|
||||
<div class=\"mission-bigtech reveal\" style=\"transition-delay:600ms\">
|
||||
<p class=\"mission-bigtech-label\">Why I stopped trying to partner with Big Tech</p>
|
||||
<p>
|
||||
I didn't just approach one of the largest technology companies in the world — I got the meeting. Got the NDAs signed. Created deliverables in real time. Showed them industry benchmarks with full auditability. Some of their own people could see exactly what it meant — what I had built and what it could do.
|
||||
</p>
|
||||
<p>
|
||||
They saw it. Seemed to engage meaningfully. Then, within two days, lawyers were engaged. Their stated concern: defending against me accusing them of stealing my IP. I laughed to myself — <em>wait, are they going to steal my IP?</em> — and decided to just finish the project on my own.
|
||||
</p>
|
||||
<p class=\"muted\">
|
||||
By the way: everything you see here, and more, is protected by six patents — and more are coming. They know about the patents. Are they going to try?
|
||||
</p>
|
||||
<p class=\"muted\">
|
||||
Not: how do we solve this at scale? Not: what does this mean for the people we serve? Their instinct was to protect enterprise revenue and manage legal exposure. The actual human impact of their technology — the people whose lives those enterprises touch — didn't enter the conversation.
|
||||
</p>
|
||||
<p class=\"muted\">
|
||||
That's the difference. <strong style=\"color:var(--t1)\">They're optimizing for the enterprise. I'm building for the people those enterprises are supposed to serve.</strong>
|
||||
</p>
|
||||
<p>
|
||||
I told them I could build and distribute this by myself. Maybe they didn't believe me. That meeting was April 22nd, 2026. I'm writing this on April 25th. You're looking at the proof. <a href=\"/marketplace/plans\">I hope you'll download it.</a>
|
||||
</p>
|
||||
</div>
|
||||
|
||||
<div class=\"mission-problems\">
|
||||
<div class=\"mission-sub-row reveal\">
|
||||
<div class=\"mission-sub-line\"></div>
|
||||
<span class=\"label\">What I'm building against</span>
|
||||
</div>
|
||||
|
||||
<div class=\"problems-grid\">
|
||||
<div class=\"problem-item reveal\">
|
||||
<p class=\"problem-label\">Synthetic media without accountability</p>
|
||||
<p class=\"problem-body\">Generative AI makes it trivially easy to produce harmful content at scale — and nearly impossible to trace. This is a problem the industry is largely ignoring. I'm not. I'm engaged with it seriously and expect to have answers in place before it becomes unmanageable.</p>
|
||||
</div>
|
||||
<div class=\"problem-item reveal\" style=\"transition-delay:120ms\">
|
||||
<p class=\"problem-label\">Epistemic collapse</p>
|
||||
<p class=\"problem-body\">AI can now generate persuasive content at any volume, on any position. The next generation is growing up in an environment where signal and noise are becoming indistinguishable. I think deeply about what it means to build tools that contribute to that problem — and how to build ones that don't.</p>
|
||||
</div>
|
||||
<div class=\"problem-item reveal\" style=\"transition-delay:240ms\">
|
||||
<p class=\"problem-label\">Concentration of inference</p>
|
||||
<p class=\"problem-body\">Four companies control nearly all frontier AI inference. Every query strengthens their position. I think that concentration of power is a structural risk — not just a pricing problem — and I'm building with that in mind.</p>
|
||||
</div>
|
||||
<div class=\"problem-item reveal\" style=\"transition-delay:360ms\">
|
||||
<p class=\"problem-label\">The accountability gap</p>
|
||||
<p class=\"problem-body\">When an AI agent takes a bad action, there is currently no clear legal or technical accountability. That's going to matter more as agents do more. I take this seriously. I'm building toward answers — not waiting for regulators to force the question.</p>
|
||||
</div>
|
||||
<div class=\"problems-grid-bottom\"></div>
|
||||
</div>
|
||||
|
||||
<div class=\"mission-closer reveal\">
|
||||
<p>The industry built tools to make AI easier to use. <span>I'm building tools to make it safer to trust.</span></p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
</div>
|
||||
<div class=\"container\" style=\"margin-top:5rem\"><div class=\"navy-line\"></div></div>
|
||||
</section>
|
||||
"
|
||||
}
|
||||
Reference in New Issue
Block a user