Skip to Content
Configuration

Theme configuration

Venom reads its options from themes/venom/theme.php, but you edit values in the Paymenter admin (theme / appearance settings for the active Venom theme). Changes are stored in the database and exposed to Blade as theme('setting_name').

For licensing and support, see Support & purchase.

Where to configure

  1. Sign in to the Paymenter admin panel.
  2. Open Settings (or Appearance / Theme, depending on your Paymenter version).
  3. Select Venom as the active theme if it is not already.
  4. Use the theme-specific fields listed below. Save after edits.

No frontend rebuild is required for text, URLs, or color pickers — only clear caches if you use config/view caching (see Caching).


Store & layout behaviour

SettingTypeWhat it does
Direct CheckoutCheckboxWhen enabled, skips the product detail page and goes straight to checkout when the flow supports it.
Small ImagesCheckboxUses more compact images on category and product cards.
Show Category DescriptionCheckboxShows category descriptions on the store and on landing marketplace sections.
Logo displaySelectLogo only or Logo and Name (site name next to the logo in navigation and footer).

Home page content

SettingTypeWhat it does
Home Page TextMarkdownRich block rendered on the landing page (headings, emphasis, lists). Use it for your value proposition or announcement.
Landing — Hero titleTextMain headline in the hero.
Landing — Hero subtitleTextareaSupporting paragraph under the headline.
Landing — Primary CTA labelTextLabel on the primary green button (e.g. “Explore marketplace”).
Landing — Hero badgeTextSmall pill above the headline (e.g. your platform name). Leave empty to use the theme’s default translated string.
Footer — Brand textTextareaParagraph under the logo in the footer. Leave empty to use the default translation. Line breaks are preserved.
Show “Powered by Paymenter” in footerCheckboxOn by default. Shows the paymenter.org credit in the footer bar. Turn off for a cleaner white-label footer; you are still responsible for complying with Paymenter and other licenses.

SettingTypeWhat it does
Landing — Documentation URLText (optional)If set, the “Documentation” navbar item opens this URL (external or internal). If empty, it scrolls to the FAQ section on the home page.
Landing — Privacy policy URLText (optional)If set, a Privacy link appears in the footer legal column.

Prefer HTTPS links in production.


Images (URLs)

All image fields accept a full URL (e.g. https://cdn.example.com/hero.png) or, if your app serves them publicly, a path Paymenter can resolve. Use HTTPS in production to avoid mixed-content warnings.

SettingWhere it appears
Landing — Hero mockup image URLInside the hero “dashboard” frame on the home page. Empty = built-in placeholder UI.
Landing — Panel section image URLControl panel / product story section on the landing. Empty = placeholder.
Landing — Marketplace section image URLMarketplace split section on the landing. Empty = placeholder.

Auth screens (login / register / password)

These same Panel and Marketplace images are reused on auth split layouts when configured:

  • Login and forgot passwordPanel image (landing_panel_image).
  • Register and password resetMarketplace image (landing_marketplace_image).

If a URL is empty, Venom uses an illustrated placeholder consistent with the landing layout.

Tips

  • Use high-resolution assets (roughly 1200px+ on the long edge) so they stay sharp on retina displays.
  • Keep file sizes reasonable (WebP or optimized PNG/JPEG) for faster LCP.
  • After changing URLs, hard-refresh the browser or bypass CDN cache if you use a CDN.

Colors (light & dark)

Venom ships two palettes: one for light mode and one for dark mode. The client UI (and shared Tailwind tokens) use HSL values from the admin color pickers. Defaults are green-forward branding; you can re-skin to match your company colors.

Light mode

SettingRole
Primary — Brand (Light)Main brand / accent (buttons, links, highlights).
Secondary — Brand (Light)Secondary accent.
Borders / chrome (Light)Borders and dividers.
Text primary (Light)Main body text.
Text muted (Light)Secondary text.
Text on accent (Light)Text on primary-filled buttons and similar.
Background (Light)Page background.
Surface (Light)Cards and elevated surfaces.

Dark mode

The dark-* fields mirror the same roles when the user (or your layout) uses dark appearance — e.g. Primary — Neon (Dark), Background (Dark), Surface / cards (Dark), etc.

Format & behaviour

  • Values are stored as HSL, e.g. hsl(151, 100%, 35%). The theme converts them to CSS custom properties (--color-primary, --color-background, …) in layouts/colors.blade.php.
  • theme-color in the document head uses your light primary for mobile browser chrome.
  • Tweak primary / background / base first for the biggest visual change; then adjust muted and neutral for contrast and hierarchy.
  • The landing page also uses some dedicated CSS variables (--vt-lp-*); panel chrome and many components still inherit from the shared palette, so admin colors have a wide effect across the storefront and client area.

If something looks low-contrast after a big change, restore readability by nudging muted or neutral before publishing.


Localization

Copy that is not overridden by theme fields comes from Laravel language files:

  • lang/*/venom.php — landing strings, footer column labels, etc.
  • lang/*/dashboard.php, lang/*/services.php, lang/*/auth.php, … — shared UI.

Set APP_LOCALE (and optional APP_FALLBACK_LOCALE) in .env. After editing PHP lang files, clear caches if needed.


Extensions

Some Blade views optionally integrate extensions (e.g. marketplace). Missing routes or tables are guarded with @if / Route::has so the theme stays safe; enable the extension for the full UI.


Caching

After changing theme settings or translations:

php artisan optimize:clear

Paymenter-wide options (currencies, gateways, legal URLs in core settings) are documented in the official Paymenter documentation , not in this theme-only guide.