Black Friday: 50% off all products for the first 50 customers. Only 10 left. Use code
40/50 claimed
See pricing →
November 15, 2026

Build a Quasar Landing Page From Components

Build a Quasar landing page section by section: hero, logos, features, CTA and footer, responsive with the grid classes, then assembled from Components.
Quasar
Landing Page
Vue
QuasarUI

A Quasar landing page is a stack of five sections: a hero with the headline and the main button, a row of customer logos, a feature grid, a call to action, and a footer. Each one is a few Quasar components and the grid classes, and none of them needs JavaScript to be responsive. This post builds that page in plain Quasar, section by section, explains the choices that keep it fast and readable on a phone, and then shows how to assemble the same page from ready-made QuasarUI Components. The code targets Quasar 2.35.2 and works in a Nuxt page or a Quasar CLI page alike.

The structure of a Quasar landing page

SectionJobQuasar pieces
HeroSay what it is, give one actionHeadings, q-btn, optional q-img
LogosShow who uses itq-img in a row
FeaturesExplain three to six benefitsrow + col-*, q-icon
CTAAsk again, after the reader is convincedq-btn, a background color
FooterLinks, legal, socialrow + col-*, flat q-btns

One rule holds the page together: every section gets the same inner width. Here that's a .section class with a max width of 1200px, centered, with side padding that grows on wider screens.

.section {
  max-width: 1200px;
  margin: 0 auto;
  padding: 64px 16px;

  @media (min-width: $breakpoint-md-min) {
    padding: 96px 24px;
  }
}

$breakpoint-md-min is Quasar's own md breakpoint (1024px), so the spacing switches at the same width as the grid classes below.

A hero section in Vue and Quasar

The hero carries the page's only <h1>.

<template>
  <section class="section text-center">
    <div class="text-overline text-primary">Invoicing for small teams</div>
    <h1 class="text-h3 text-weight-bold q-my-md">Send an invoice in under a minute</h1>
    <p class="text-body1 text-grey-8 q-mx-auto" style="max-width: 600px">
      Create, send and track invoices from one screen. Your clients pay by card,
      and you see it the moment they do.
    </p>
    <div class="row justify-center q-gutter-md q-mt-lg">
      <q-btn unelevated color="primary" size="lg" no-caps label="Start free" to="/signup" />
      <q-btn flat color="primary" size="lg" no-caps label="See how it works" icon-right="arrow_forward" href="#features" />
    </div>
  </section>
</template>

A few decisions in there:

  • One primary button. The flat button is a secondary path for readers who aren't ready. Two filled buttons compete with each other.
  • A real <h1> with a typography class. text-h3 sets the size, the tag sets the meaning. The heading level and the font size are independent, so don't pick <h3> because you like its size.
  • A max width on the paragraph. Around 600px keeps lines at a readable length on wide screens.

On phones, the text-h3 headline is 48px, which is large for a 375px-wide screen with a long sentence. A short media query on your own class fixes it without JavaScript:

.hero-title {
  @media (max-width: $breakpoint-xs-max) {
    font-size: 2rem;
    line-height: 2.5rem;
  }
}

Logos and features

The logo row and the feature grid are both row + col-* layouts. The features section gets the id the hero's second button points to:

<script setup lang="ts">
const logos = ['/logos/acme.svg', '/logos/globex.svg', '/logos/initech.svg', '/logos/umbrella.svg']

const features = [
  { icon: 'bolt', title: 'Invoices in seconds', text: 'Pick a client, add lines, send. Tax and totals are calculated for you.' },
  { icon: 'credit_card', title: 'Card payments', text: 'Every invoice has a pay button. Money lands in your account in two days.' },
  { icon: 'notifications', title: 'Automatic reminders', text: 'Late invoices get a polite reminder, so you never chase a client.' },
]
</script>

<template>
  <section class="section">
    <p class="text-center text-grey-7">Used by teams at</p>
    <div class="row items-center justify-center q-col-gutter-lg">
      <div v-for="logo in logos" :key="logo" class="col-6 col-sm-3 text-center">
        <q-img :src="logo" alt="" height="40px" fit="contain" />
      </div>
    </div>
  </section>

  <section id="features" class="section">
    <h2 class="text-h4 text-weight-bold text-center q-mt-none q-mb-xl">Everything an invoice needs</h2>
    <div class="row q-col-gutter-xl">
      <div v-for="feature in features" :key="feature.title" class="col-12 col-md-4">
        <q-icon :name="feature.icon" size="32px" color="primary" />
        <h3 class="text-h6 q-mt-md q-mb-sm">{{ feature.title }}</h3>
        <p class="text-grey-8">{{ feature.text }}</p>
      </div>
    </div>
  </section>
</template>

col-12 col-md-4 gives one feature per row below 1024px and three in a row from there. The logo row goes from two per row on phones to four from 600px. q-col-gutter-* puts the spacing on the columns, so the spans still add up to 12.

Decorative logos get an empty alt. If a logo is the only place a company is named, give it the company name instead.

The CTA repeats the hero's action after the reader has seen the features. A colored band makes it stand out from the white sections around it:

<template>
  <div class="bg-primary text-white">
    <section class="section text-center">
      <h2 class="text-h4 text-weight-bold q-mt-none">Your next invoice could already be paid</h2>
      <p class="text-body1">Free for your first ten invoices. No card needed.</p>
      <q-btn unelevated color="white" text-color="primary" size="lg" no-caps label="Start free" to="/signup" />
    </section>
  </div>

  <footer class="bg-grey-2">
    <div class="section row q-col-gutter-lg">
      <div class="col-12 col-md-4">
        <div class="text-weight-bold">Acme Invoicing</div>
        <p class="text-grey-7">Invoices for small teams.</p>
      </div>
      <nav v-for="group in footerLinks" :key="group.title" class="col-6 col-md-2" :aria-label="group.title">
        <div class="text-weight-bold q-mb-sm">{{ group.title }}</div>
        <q-btn v-for="link in group.links" :key="link.to" flat dense no-caps class="block" :label="link.label" :to="link.to" />
      </nav>
    </div>
  </footer>
</template>

footerLinks is an array of { title, links: [{ label, to }] } groups. The band itself is full width while the content inside stays at the section width, which is why the bg-primary sits on an outer div.

That's the page: wrap the five sections in a page component (app/pages/index.vue in Nuxt), and it's responsive at every width without a single $q.screen check.

Things that make a landing page feel slow or broken

  • Images without a size. Give q-img a height or a ratio, so the page doesn't jump while images load.
  • The hero image as the largest paint. If the hero has a screenshot, keep it light (WebP, sized for its slot) and set loading="eager" on its q-img: QImg loads lazily by default, which delays an image that's above the fold.
  • Layout decided in JavaScript. With server rendering, $q.screen doesn't know the window size until the app has hydrated, so anything sized by it can change after the first paint. Grid and visibility classes don't have that problem.
  • Several <h1>s. One per page. Sections below the hero use <h2>.
  • Breakpoint spacing classes that do nothing. Classes like q-pa-md-xl or justify-md-start only exist when Quasar's CSS addon is on: cssAddon: true in the quasar options of nuxt.config.ts, or framework: { cssAddon: true } in the Quasar CLI config. Without it they're silently ignored.

Building a Quasar landing page from Components

Writing the sections yourself is a good way to learn the grid. If you'd rather start from designed sections, each part of the page has a QuasarUI Block:

  • Hero Sections: 5 designs, 1 of them Free. The Free one includes its own navigation: a toolbar with the links from md up, a menu button and a drawer below that, an announcement pill, a centered headline, two buttons and a blurred gradient behind them.
  • Feature Sections: 10 designs, 3 of them Free. The Free ones open with a centered heading and intro, then list the features in two or three columns, each with a title and a short text (two of them add an icon).
  • CTA Sections: 8 designs, 1 of them Free: a headline, a short text and two buttons beside an image, stacked on small screens.
  • Footers: 6 designs, 1 of them Free: a logo, a tagline and social buttons, then link columns and a copyright line.
  • Logo Sections: 6 designs, 1 of them Free, for the row of customer logos.

One Component in each of those Blocks except Logo Sections is a Themeable Component, which follows the colors you set in the Theme Builder. There's also a Landing Pages Block with 2 complete pages (1 Free) if you want to see all the sections already stacked.

Assembled in Nuxt, the page is a list of Components:

<!-- app/pages/index.vue -->
<template>
  <HeroSection01 />
  <LogoSection01 />
  <FeatureSection01 />
  <CtaSection01 />
  <Footer01 />
</template>

Copy each Component into app/components/ under the name you use, replace the placeholder text and images, and check the heading levels: CTA Section 01 uses an <h1> for its headline, which should become an <h2> on a page that already has a hero. Several of the Components use the breakpoint spacing classes mentioned above, so turn on the CSS addon. Free Components can be copied without signing in.

Common questions about Quasar landing pages

Should a landing page use q-layout? It isn't required. A landing page that scrolls as one document works with plain sections. Use q-layout when you want a fixed header that reveals on scroll or a drawer for the mobile menu.

How do I scroll to a section from the hero button? Give the section an id and the button href="#features". Add scroll-behavior: smooth on html for a smooth scroll.

Is Quasar a good choice for a marketing page? If the rest of your app is Quasar, yes: same components, same theme, one build. For SEO, render the page on the server (Nuxt or Quasar SSR mode) so the content is in the HTML.

Next step

Browse the Hero Sections, pick the opening that fits your product, and stack the rest of the page under it. Every hero has a live preview you can switch between desktop, tablet and phone width.