Use Cases
Maker turns your plain-English prompts into real, responsive web pages and front-end apps—instantly. Here are some common use cases:
What can you build with Maker?
💡 Web Pages
Marketing Landing Pages
Launch product, campaign, or event pages with sections like hero banners, testimonials, pricing tables, and FAQs.
Blog Pages
Generate blog layouts with featured images, author bios, tags, and rich text formatting—perfect for content marketing.
Product FAQ Pages
Build organized, searchable FAQ sections that match your brand and update easily as questions evolve.
Company Homepages
Create professional homepages with navigation, mission statements, featured products/services, and contact forms.
Link-in-Bio Microsites
Generate compact mobile-optimized pages to highlight key links, announcements, or promotions.
Team or About Pages
Highlight your people, values, and story with profile grids, timelines, and quote sections.
Coming Soon Pages
Create branded “Coming Soon” or waitlist pages with email capture and countdown timers.
Portfolio Sites
Build project showcases with image galleries and case study layouts—perfect for designers and creatives.
Lookbook
Showcase seasonal refreshes, collabs, or new drops with beautifully styled lookbooks.
Event Pages
Set up pages for events, including schedules and speaker sections.
Enhanced A+ Product Pages
Create elegant, customizable A+ content with image carousels, specs, and more.
Job Boards or Career Pages
Feature open roles, testimonials, and apply links to support recruiting.
🧩 Web Components
Hero sections
With animation
CTAs
On-hover effects
Image galleries
With optional hotspots and quickview
Before/after sliders
Compare visuals interactively
FAQs & accordions
With built-in search bars and filters
Comparison tables
For product or service comparisons
Pricing tables
With monthly/yearly toggles
Interactive charts
Size charts, calculators
Interactive maps
With zoom and pin support
Flip/hover cards
Reveal content on hover
Product recommendation quiz
For guided product discovery
Testimonial sliders
Showcase customer quotes with carousel
Cards & feature grids
Visual content layouts
Buttons, badges, and tags
Styled, responsive elements
Tabs & modals
For toggling views or showing dialogs
Countdown timers
Great for launches and promos
Embedded video blocks
Add Vimeo/YouTube or other embeds
Carousels & sliders
For images, products, or testimonials
Step-by-step flows
For onboarding or guided experiences
Timelines
Visual representation of milestones
Responsive grid layouts
Auto-adjust across breakpoints
Announcement banners
For key alerts or promos
Social media link blocks
Easily link out to platforms
Scroll-based animation triggers
Bring content to life as users scroll
Language switcher toggle
Enable multilingual interfaces
Toggle switches
Light/dark mode, pricing plans, etc.
Autoplay marquee
For announcing features, updates, or promos
Geotargeting Use Case
Can I show different default content based on a visitor’s location?
Yes. Maker can adapt content using the browser’s built-in location permission. When a visitor grants location access, the page can set defaults (e.g., category, region, module) according to your prompt rules. If permission is denied or unavailable, your defined fallback shows.
How it works
Add a plain-English rule to your Maker project prompt describing what to show for specific regions.
Browser asks for location permission when the page needs it (standard popup).
Maker AI applies your rule if location is available; otherwise it uses your fallback.
Example prompt snippet
Use geotargeting to set the default content.
If the visitor is in San Francisco, show the California category by default.
If location is not available or permission is denied, default to All Products.
Never block the page while waiting for location.
(Adjust regions, categories, and fallbacks to fit your use case.)
Best practices
Always define a fallback for “deny/no location” cases.
Don’t block initial render. Load default content immediately; let location update the UI if/when available.
Be transparent. Visitors must opt in to share location; no consent means no geotargeting.
For more technical details, see the official browser documentation for the Geolocation API.
Good use cases
Auto-select a regional category or module
Show local events, stores, or promos by default
Display region-specific copy or shipping notes
Additional Notes:
Does this work without consent? No. The browser requires explicit permission. If declined, the fallback shows.
Will it slow down the page? Not if you avoid blocking. Render defaults first, then apply geotargeted changes after permission is granted.
Is any location data stored? This approach is designed for in-browser use after consent. Maker does not store or track location data.
Last updated
Was this helpful?