Lookup - Definitive API Landing Page Template
Lookup is a split-screen landing page template built for Framer API documentation. It leads with an interactive bundle estimator, follows with a side-by-side API comparison section, and drives developers toward a full reference without any email gate. The design uses a deep dark-mode palette with electric indigo accents and phosphor green status indicators.
by Rocket studio
Quick summary
Lookup is a single-page Framer template designed for API reference documentation. It opens with a live calculator that estimates bundle size and dependency compatibility, then guides developers through staggered comparison rows that pit the Framer API against common alternatives. The result is a landing page that earns developer trust before asking for a single click.
Who this template is for
This template is built for the developers who live inside API documentation and need to share findings fast. It speaks directly to builders who value clarity, speed, and proof over marketing copy.
- Indie plugin builders shipping weekend side-projects who need a clear, credible reference page
- Design engineers wiring prototypes to live data who want quick stack comparisons before committing
- Agency teams building white-label templates who need to show clients what changed before a site breaks
What problem this template solves
Most API documentation pages are static walls of text. Developers waste time reverse-engineering changelogs, running manual bundle checks, and hunting for side-by-side comparisons that simply do not exist. This template removes that friction.
- No more late-night changelog archaeology to understand what a version update actually changed
- No guesswork about bundle cost when mixing API modules across frameworks
- No scattered comparisons across multiple tabs when evaluating the API against other animation tools
What you get with this template
You get a complete, conversion-ready landing page layout built around an interactive estimator and a structured comparison section. Every visual element serves a functional purpose, and the page flows from proof to action without detours.
- A live split-screen estimator header with framework selection, module toggles, and real-time output
- A staggered comparison section mapping the API against alternative tools row by row
- A sticky call-to-action bar and a shareable secondary action that resets the calculator with a unique URL
Feature list
This template is built around functional sections that demonstrate value before asking for anything in return.
Live Bundle Estimator Header
The header is a 50/50 split-screen calculator. The left panel lets developers choose a framework (React, Vanilla, or Hydrogen), select API modules (Motion, Scroll, Navigation, or CMS), and toggle between stable and canary versioning. The right panel instantly outputs an estimated bundle size in kilobytes, a dependency tree drawn with thin indigo lines, and a compatibility score badge.
Animated Real-Time Output Panel
Every input change triggers live feedback. Counters tick to new values, the dependency tree redraws, and the compatibility badge pulses phosphor green for passing scores or amber for warnings. The animation makes the estimator feel alive rather than static.
Staggered Comparison Section
Below the estimator, a versus breakdown maps the Framer API side by side against raw Framer Motion, GSAP, and vanilla CSS. Each row covers a common task: scroll-triggered animations, page transitions, layout shifts, and CMS binds. Rows slide in with staggered entrance animations, escalating from simple use cases to complex orchestrations.
Embedded Micro-Demo Column
Each comparison row includes a live embedded micro-demo on the right column alongside a lines-of-code count on the left. Developers see the proof in motion, not just in numbers.
Sticky Conversion Bar
A sticky "Explore the Full Reference" bar appears after the visitor interacts with the estimator or scrolls past the first comparison row. It surfaces at the right moment without interrupting the reading flow.
Shareable Calculator URL
The secondary call-to-action, "Compare Your Stack," resets the calculator and generates a shareable URL. Developers can send their exact configuration to a teammate without screenshots or copy-pasting.
Page sections overview
| Section | Purpose |
|---|---|
| Split-Screen Estimator | Interactive header tool for bundle and compatibility estimates |
| Real-Time Output Panel | Live dependency tree and compatibility badge display |
| Versus Comparison Rows | Side-by-side API task breakdowns with staggered animations |
| Micro-Demo Column | Embedded live demos paired with lines-of-code counts |
| Sticky call to action Bar | Persistent action trigger after estimator or scroll interaction |
| Shareable URL Action | Secondary call to action that generates a team-shareable calculator link |
Design & branding system
The visual identity follows a Directory and Discovery theme built for dark-mode developer audiences. Every color in the palette earns its role and does not appear arbitrarily.
- Void black (#0D0D12) is the primary canvas, cool slate (#1E1F2B) surfaces cards and secondary panels, and electric indigo (#5B4CFF) drives interactive elements and hover states
- Phosphor green (#39FF85) is reserved strictly for live-status indicators and success confirmations, keeping its meaning unambiguous
- The overall aesthetic resembles a terminal window at golden hour, where syntax-highlight glow meets deep dark mode and every accent color signals something specific
Mobile & speed optimization
The layout is designed to stay usable and readable across screen sizes. The split-screen structure adapts so the estimator and output panels remain accessible without horizontal scrolling.
- The 50/50 split-screen layout is built to reflow cleanly on narrower viewports
- Animated counters and tree redraws are scoped to interactive triggers, so they do not run unnecessarily on load
How this template helps you convert
This template converts by proving value first and asking for action second. The sequence is deliberate: demonstrate, compare, then direct.
- The live estimator immediately shows developers something useful, making the first interaction functional rather than promotional and building credibility before any call to action appears
- The comparison rows escalate complexity row by row, so by the time the sticky bar surfaces, the developer has already seen concrete evidence that fewer lines and smaller bundles are achievable
- The shareable URL secondary action extends reach to team members without requiring a separate sign-up or demo request, lowering the barrier to conversion at the team level
Other information about this template
This template is categorized under Documentation and Support, specifically within the Framer Documentation subcategory and the Framer API Reference niche. It is a strong fit for any team or individual building a reference hub around the Framer platform.
- The template style is Split Screen (50/50), making it well suited for tools or reference pages that need input and output displayed simultaneously
- The creative direction follows a Launch Energy approach, meaning the scroll experience accelerates in complexity and energy as the visitor moves down the page
- The header concept is a Calculator/Estimator, which is a higher-engagement entry point than a static hero for developer audiences
- The landing page direction is Comparison/Versus, positioning the documented API against real alternatives rather than describing it in isolation




Theme
Directory & Discovery
Creative direction
Launch Energy
Color system
Electric Indigo
Style
Split Screen (50/50)
Direction
Comparison/Versus
Page Sections
Live Split-screen Bundle Estimator
Animated Counter and Tree Redraws
Staggered API Comparison Rows
Embedded Live Micro-demos
Sticky Call-to-action Bar
Shareable Calculator URL
Related questions
Does this template require coding to customize?
Can I use this template for a different API, not just the Framer API?
Is there an email gate before the call to action?
What frameworks and modules does the estimator include?
Can developers share their estimator results with a teammate?