StockLrn
Stock market education where no page render ever waits on a market-data API.
- Type
- Product
- Industry
- FinTech / education
- Platform
- Web application
- Role
- Design, build, deploy
What made this hard.
A stock market education platform built on real data: company profiles, financial statements, dividends, earnings, analyst ratings and congress trades, presented through interactive charts and backed by flashcard drills and long-form articles.
A data-heavy education site has two failure modes that look the same to a visitor: a slow page and a stale page. Calling a market-data API while rendering gives you both, plus a bill that scales with crawlers.
And a site with this many page types drifts visually fast (a stray hex colour here, a bespoke utility there) until nothing quite matches and every fix is a one-off.
What we built.
- Moved all market-data ingestion into explicit refresh and ingest jobs. The render path never makes a synchronous external call; read paths are cache-wrapped in the controller layer, with indexes on every column that gets sorted or filtered.
- Ran a site-wide design-system conformance programme: CSS custom-property tokens plus a named component layer, executed as multiple parallel review rounds against the live tree. Raw palette utilities and hardcoded hex disappeared outside admin, the CSS bundle shrank materially, and axe-core violations went to zero.
- Captured the build gotchas as durable patterns rather than folklore: framework purging of component-layer rules with no consumer, rules appended outside the component layer defeating utilities, and stale backup files inside the views directory keeping retired utilities alive in the bundle.
- Built an automated short-form video pipeline (script, text-to-speech, assemble, publish to several social platforms) driven by a scheduled job with a tiered LLM client that falls through providers.
- Encoded a hard policy in code: scheduled jobs refuse paid model slugs, so a provider withdrawing a free tier fails loudly instead of quietly spending. The multi-tier outage that taught us this is written up with a live-probe method for re-qualifying models.
- Seeded educational content through versioned seeder classes, with quizzes modelled as question and answer rows, so the curriculum is reproducible rather than hand-entered.
What it runs on.
Chosen to be maintainable for years, not to win an argument on the internet.
- PHP 8.2+
- Laravel
- Blade
- Vue.js
- Alpine.js
- ApexCharts
- Tailwind CSS
- MySQL
Where it landed.
Profiling confirmed what the architecture promised: no N+1 loops and no synchronous external calls on the render path.
The design-system pass is the one we'd repeat first on any older codebase: tokens plus a named component layer turn “change the palette” from a week of grep into a single file.
Need something in this territory? This is Custom web app development work. Start from all services or see pricing.
Related case studies.
Your project
Tell us what you're building. We reply within two business days.