Your homepage sells the vision. Your pricing page sells the plan. Your Features page sells the substance—and for HubSpot themes, SaaS platforms, and component libraries, substance is what separates a refund request from a five-star review. The Aura Features page template is a six-section product marketing page built for buyers who need detail before they commit: developers evaluating code quality, designers auditing UI systems, and marketing leaders confirming the platform covers their use cases.
Features pages serve three audiences simultaneously:
Aura answers all three with two feature grids, a component inventory module, a conversion story section, and closing CTA—without drowning visitors in unstructured bullet lists.
Path: templates/Features.html. DnD area: Features. CSS: aura-features-sections.css. Six full-width sections alternating cream and sand.
Centered Aura Hero: "Powerful Features for Modern Websites" with platform subheading. Sets expectation that this page is comprehensive, not a teaser.
Six cards via Aura Feature Grid module (3-column):
Objective: Establish baseline parity with premium theme expectations. These are table stakes—presenting them crisply builds confidence before advanced capabilities.
The Aura Component Library module is a Features-page differentiator. Eight inventory cards quantify what ships in the theme:
Why inventory modules convert: Buyers fear hidden upsells. Explicit counts ("48 modules," "18 sections") reduce uncertainty and support premium pricing psychology.
Developer benefit: Technical buyers scan for architecture signals—modular components, token-driven styling, documented patterns. This section speaks their language.
Second Feature Grid with six advanced cards: Theme Settings Panel, Team Collaboration, SEO Optimized, Analytics Ready, Secure & Reliable, CMS Integration.
Objective fulfilled: Move from "what it includes" to "why it wins." Advanced grid addresses enterprise-adjacent concerns without requiring a separate enterprise page visit.
Aura Conversion Split module defaults: "Built for Conversion," 40% improvement stat, bullets on Optimized CTAs, Trust Elements, Mobile First design.
Bridge role: Features pages can feel abstract. This section reconnects capabilities to business outcomes—critical for marketing leaders who approve budget but do not read code.
Full-bleed Aura CTA Banner: "Experience the Difference" with Get Started Today → Pricing and View Style Guide → Style Guide page.
Dual CTA strategy: Commercial buyers click pricing; design buyers click style guide—both paths advance the sale.
| Module | Role on Features page |
|---|---|
| Aura Hero | Page framing |
| Feature Grid (×2) | Core + advanced capabilities |
| Component Library | Quantified inventory |
| Conversion Split | Business outcome linkage |
| CTA Banner | Conversion routing |
Target keywords: "HubSpot CMS theme features," "modular HubSpot components," "responsive HubSpot theme." Use H2/H3 headings matching search intent. Internal link to Pricing, Documentation, and Style Guide.
Features depth creates price justification. Once evaluators confirm capability coverage, they need tier comparison and billing clarity—the natural next click is Pricing.
Dive into plan structure, enterprise upsell, and pricing FAQ in our Aura Pricing page template guide to close the evaluation loop.
Technical buyers often arrive at Features via homepage or search—this page must stay accurate as your product evolves. HubSpot editing workflow:
Features pages are reference documents—mobile behavior prioritizes scannable grids over narrative flow.
Hero: Centered headline scales down. Gradient highlight text on "Modern Websites" wraps naturally if kept concise.
Core Feature Grid (3-column): Six cards reflow to 2-column tablet, 1-column mobile. Long feature descriptions wrap without truncation—edit copy if cards exceed five lines on phone.
Component Library module: Eight inventory cards typically display 2×2 or 4×2 grids depending on breakpoint. Count badges ("5+ variants") remain legible at smaller sizes. This module is dense—verify no horizontal overflow on 320px width devices.
Advanced Feature Grid: Same responsive behavior as core grid. Visual alternation with sand/cream backgrounds maintains section boundaries on long mobile scrolls.
Conversion Split: Checklist and stat card stack on mobile. Animated stat still triggers—ensure number readable at reduced size.
CTA Banner: Dual buttons stack. Full-bleed gradient edge-to-edge on mobile Safari.
Features page showcases design system depth—token consistency proves "premium theme" claim.
Colors: Feature card icons use accent token. Component Library card borders and backgrounds use neutral tokens. Conversion Split stat card gradient pulls primary/secondary accents. Section background alternation uses cream and sand globals.
Typography: Feature card titles use h4 heading scale. Component Library counts use larger heading weight for emphasis. Body descriptions use standard readable size—technical buyers read long copy; do not shrink below accessible minimums.
Buttons: CTA Banner dual buttons use primary and secondary tokens—matching homepage and Pricing for cross-page consistency during evaluation journeys.
Aura Hero (centered): Badge optional, headline with gradient span support, subheading, no default CTAs.
Aura Feature Grid (×2): Section badge, heading, subheading, card repeater (icon picker, title, description), column count (3 recommended for core, 3 for advanced), card style variant, background token.
Aura Component Library: Section heading, subheading, inventory repeater (category name, count/variant text, description, optional image), layout columns, total count headline optional ("48 modules included").
Aura Conversion Split: Heading, benefit repeater, stat numeric value, stat label, animation toggle, background style.
Aura CTA Banner: Heading, subheading, primary CTA + link, secondary CTA + link, style variant.
For marketers: Features page supports mid-funnel nurture emails ("see everything included"). Track scroll depth to Component Library—indicates serious evaluation. Align feature language with sales deck and homepage. Use page as SEO destination for "HubSpot theme features" queries. A/B test CTA Banner primary button copy ("Get Started" vs "See Pricing").
For developers: Component Library module documents what ships—use as internal reference during client scoping. Feature grid cards map to actual module folders in theme. Conversion Split stat should reflect benchmarked Lighthouse scores or measurable metrics when possible. Extend page by duplicating Feature Grid module instance for niche capabilities (e-commerce, multilingual) without editing template HTML.
For agency owners: Features page pre-sells implementation scope. Prospects who read Component Library understand deliverable depth—reduces "I thought that was included" disputes. Link from proposals. Customize Advanced grid for agency-specific differentiators (HubSpot certified, SLA, migration included). Pair with Services page for buyers needing custom work beyond theme defaults.
Features pages target evaluation-intent keywords with high commercial value. Structure H2/H3 around searchable phrases: "Design Token System," "HubSpot CMS Components," "Responsive HubSpot Theme." The existing link to the Pricing guide closes the evaluation loop in blog content; on your live site, internal link from homepage "View Demos" and "Learn More" CTAs, plus footer Product column.
Add links to Documentation, Style Guide, and blog technical posts from Component Library card descriptions where natural. External links to HubSpot developer docs boost E-E-A-T for developer audience segments.
Features page doubles as sales enablement asset. Share URL in pre-demo emails so prospects arrive prepared—shorter calls, higher close rates. Create PDF export of page sections for RFP appendices (HubSpot page print-to-PDF works adequately). Maintain internal doc mapping each Feature grid card to competitor differentiators—sales reps counter "Theme X includes Y" with specific Component Library counts. When prospects request technical audit, link directly to Component Library anchor if available, or Conversion Split section for performance claims. Update page within 48 hours of major theme releases—stale feature counts undermine sales during competitive deals.
Features page visitors are mid-funnel—track time on page over 3 minutes, scroll to Component Library, and CTA Banner clicks. Create HubSpot list: "Viewed Features page 2+ times in 14 days" for sales outreach. Compare Features → Pricing vs Features → Contact click paths.
Developers evaluating Aura often bookmark Features page—avoid marketing fluff. Use absolute links in CTA Banner if Documentation lives on subdomain.
Features page is where evaluators compare you to alternatives. Without naming competitors directly, address common evaluation criteria: module count, Theme Settings depth, HubSpot CMS Hub compatibility, performance benchmarks, support SLAs. Component Library inventory is your strongest differentiation—keep counts current. If evaluators request comparison docs, export Features page sections into sales battle cards.
When shipping new modules in theme updates, update Component Library counts in the same release—marketing copy lagging code releases confuses evaluators comparing release notes to the Features page.
Link each Component Library card to its Documentation anchor when available—evaluators who click through stay engaged longer and return fewer pre-sales support tickets.
The Aura Features page template turns technical depth into a structured story. Two grids for breadth, one inventory module for specificity, one conversion split for business relevance, one CTA for action. Evaluators get answers. Your sales team gets shorter calls. Publish it before your next launch—and let the product speak for itself.