Creating a token

1. Go to Admin → Auth tokens Click Add, select the user the token acts as
2. Save - the generated token string is shown once; copy it immediately

Using a token

Send it with requests, e.g. as Authorization: Bearer <token> (or per integration instructions). Requests run with the permissions of the linked admin user.

Security

• Treat tokens like passwords - revoke any token you can't account for
• Delete tokens that are no longer used from the list
• All token usage appears in logs like normal admin activity

It provides a collection of free and premium plugins that you can browse, preview, and install directly from your admin dashboard.

Plugins extend your site with new features, integrations, and enhancements that are not included in the Vvveb core.

What You Can Do in the Marketplace

From the marketplace, you can:

• Browse available plugins
• View plugin descriptions and compatibility information
• Check when each plugin was last updated
• Install plugins with a single click
• Open plugin detail pages for more information

All plugins listed in the marketplace are compatible with your current Vvveb version.

Accessing the Marketplace

You can open the Plugins Marketplace directly from your admin panel:

Admin Dashboard → Plugins → Add New

This will display all available plugins that you can install.

Installing a Plugin

To install a plugin from the marketplace:

1. Browse or search for a plugin
2. Click Install After installation, activate the plugin from the Plugins page

Installed plugins can be activated, deactivated, configured, or removed at any time.

Why Use Marketplace Plugins

Marketplace plugins allow you to:

• Add payment methods
• Improve SEO
• Add security features like 2FA
• Integrate external services
• Add forms, newsletters, and widgets
• Enhance ecommerce functionality
• Improve performance (e.g., minification, caching)

They make your Vvveb site more powerful and customizable.

Builtin honeypot anti spam filter.

Contact form component allows visual customization of forms from the page builder, add any fields visually.

This plugin is included and activated by default

Quick start

1. Activate the plugin from Plugins Run the Setup Wizard (Settings → SEO → Setup Wizard): it verifies site basics, sets up Google/Bing verification codes, social profiles and enables the recommended modules
2. Edit any post or product - a new SEO tab shows the live SERP preview and content score

Modules

See plugin settings for every option.

Creating a field group

1. Go to Custom Fields → Field groups Click Add and give the group a name (e.g. "Book details")
2. Add the fields that belong to the group - any type from Text to Gallery or Relationship
3. Choose which content type(s) the group applies to
4. Save

How groups appear in the editor

When editing a post/product that matches the group's content type, the group shows up as a separate section with all its fields. Editors only see groups relevant to what they are writing.

Displaying values in themes

Field values are stored per post and can be rendered in themes through template variables or components, keyed by the field slug. See the individual field type docs for output details.

Each field type defines how data is entered in the admin panel and how it can be displayed in your theme. All fields share a consistent set of settings, making them predictable and easy to configure.

How Custom Fields Work

A Custom Field consists of:

• A field type (e.g., Text, Image, Gallery, Date, Product)
• A label (what editors see)
• A slug (used to retrieve the value in templates)
• Optional settings (default value, required, instructions, etc.)

When a field is added to a post type, it appears in the editor and stores its value in the database. You can then display it in your theme using components or template variables.

Shared Field Settings

All field types include the following settings:

• Default Value - The value shown when creating a new post or product.
• Required - Prevents saving if the field is empty.
• Instructions - Helper text shown to editors.
• Placeholder Text - Text displayed when the field has no value.
• Prepend - Text displayed before the input.
• Append - Text displayed after the input.

These settings ensure consistency across all field types and make the editing experience intuitive.

Field Types

Each field type is designed for a specific kind of data. The following list summarizes the purpose of each field type.

Accordion Field

Creates an accordion-style input for storing expandable/collapsible list items.
Useful for FAQs, feature lists, or structured content sections.

Checkbox Field

Stores a true/false value using a checkbox input.
Ideal for toggles such as “Featured”, “Published”, or “Show in menu”.

Color Field

Provides a color picker for selecting HEX/RGB values.
Useful for theme settings, UI customization, or product color attributes.

Date Field

Stores a date value using a calendar picker.
Commonly used for events, schedules, or publication dates.

Date Time Field

Stores both date and time.
Useful for appointments, event start times, or timed promotions.

Email Field

Validates and stores email addresses.
Useful for contact information or form submissions.

File Field

Allows uploading files that can be downloaded on the website.
Useful for PDFs, documents, or downloadable resources.

Gallery Field

Stores multiple images as a gallery.
Ideal for product galleries, portfolios, or image collections.

Google Map Field

Stores map coordinates or addresses using a Google Maps input.
Useful for locations, stores, or event venues.

Image Field

Stores a single image.
Used for featured images, banners, or thumbnails.

Link Field

Stores a URL or internal link.
Useful for buttons, CTAs, or external references.

Message Field

Displays a static message in the editor (info, warning, instructions).
Does not store data.

Month Field

Stores a month value (YYYY‑MM).
Useful for archives, billing cycles, or monthly scheduling.

Number Field

Stores numeric values.
Useful for quantities, prices, ratings, or measurements.

Oembed Field

Accepts media URLs and automatically embeds them (YouTube, Twitter, etc.).
Ideal for rich media content.

Password Field

Stores password values (masked input).
Useful for protected content or integrations.

Post Field

Autocomplete selector for choosing a post.
Useful for related posts, featured posts, or linking content.

Product Field

Autocomplete selector for choosing a product.
Useful for cross‑selling, related products, or product references.

Radio Field

Displays a list of radio buttons for selecting one value.
Useful for predefined options such as sizes, types, or modes.

Range Field

Creates a slider for selecting a numeric value within a range.
Useful for ratings, filters, or adjustable settings.

Select Field

The Select field displays a dropdown list of predefined options, allowing the user to choose a single value. It is ideal for categories, types, modes, or any controlled vocabulary.

Tab Field

The Tab field stores tabbed content, enabling editors to organize information into multiple labeled sections. This is useful for product specifications, multi-section content blocks, or structured layouts.

Taxonomy Field

The Taxonomy field links a post to a taxonomy item, such as a category, tag, or custom taxonomy. It is essential for organizing content and enabling taxonomy-based filtering.

Telephone Field

The Telephone field stores phone numbers using a tel input. It is suitable for contact information, business listings, or user profiles.

Text Field

The Text field provides a simple single-line input for short strings. It supports an optional character limit and is one of the most commonly used field types.

Textarea Field

The Textarea field stores multi-line text, making it ideal for descriptions, notes, summaries, or any longer content that does not require rich formatting.

Time Field

The Time field stores time values using a time picker. It is useful for schedules, opening hours, or event times.

Toggle Field

The Toggle field stores true/false values using a switch-style UI. It is a more visual alternative to the Checkbox field and works well for enabling or disabling features.

URL Field

The URL field stores website addresses and validates them as URLs. It is useful for external links, social profiles, or reference resources.

User Field

The User field allows selecting a user from the system, storing a relationship between the post and a user account. It is useful for authorship, ownership, or assigning responsibility.

Week Field

The Week field stores week values (year + week number). It is useful for scheduling, weekly reports, or time-based categorization.

WYSIWYG Field

The WYSIWYG field provides a full rich-text editor, identical to the editor used for posts and products. It supports formatted text, images, embeds, and multimedia.
This field is ideal for long-form content, flexible layouts, and any scenario where editors need full control over formatting.

A combined reference table helps compare all Vvveb CMS custom field types at a glance and clarifies when each one is most appropriate. The table below summarizes every available field type, including its purpose and ideal use cases.

Custom Fields Reference Table

Using Custom Fields in Themes

Custom field values can be displayed in templates using components or Vtpl selectors. For example:

<span data-v-post-custom_field_slug></span>

Or inside a component:

<div data-v-product-custom_field_slug></div>

This makes it easy to integrate custom data into any theme layout.

Custom Fields are one of the most powerful ways to tailor Vvveb CMS to different content models. They allow you to build flexible, structured, and editor‑friendly content types without writing custom code.

Name

The name of your page

Slug

The slug is unique for the page and is used to generated the url that points to the page. The slug will be generated automatically from the name but you can change it if you wish. It should not contain punctuation marks and spaces, use - or _ to separate words.

Content

Content of the page

Excerpt

Depending on template used this might not be visibile, by default is not visible.

Meta description and Meta keywords

This content is used for search engines.

Featured media

Depending on template used this image can be visible or not, usually pages don't have featured media visible.

Open in page editor

With this action you can edit the content of the page inside the page builder exactly how is displayed to users.

Page options

Publish date

Unlike posts publish date is not visible on frontend and is used only internally.

Status

Only with publish the page is visible on the frontend.

Template

If you wish your page to have a different layout you can select a different theme template, for example for contact page you can use a template with a contact form.

Page Editing

Pages are static content entries used for sections like About, Contact, Services, or any non‑blog content.

The page editor allows you to manage text, media, SEO settings, templates, and multi‑site visibility.

Content

Name

The title of your page.
This is used in the admin panel and may appear in menus or breadcrumbs depending on your theme.

Slug

The slug is the unique identifier used in the page URL.

• Automatically generated from the page name
• Can be edited manually
• Should not contain spaces or punctuation
• Use - or _ to separate words

Example:
about-us → https://example.com/about-us

Content

The main body of the page.
This is where you add text, images, embeds, and other content elements.

Excerpt

A short summary of the page.
Depending on the template, this may or may not be displayed.
By default, excerpts are not visible on standard page templates.

Meta Description & Meta Keywords

Used for SEO purposes:

• Meta description appears in search engine results
• Meta keywords are optional and used by some search engines

These fields help improve search visibility.

Featured Media

A featured image or video for the page.

• Visibility depends on the selected template
• Many page templates do not display featured media
• Some custom templates may use it as a header or banner

Open in Page Editor

You can open the page in the Page Builder for advanced layout customization.

• Save as new template - applies changes only to this page
• Default template - applies changes to all pages using the same layout

This is ideal for creating unique landing pages or custom layouts.

Page Options

Sticky

Displays the page before other non‑sticky pages in listings.
Useful for highlighting important pages.

Password Protected

Restricts access to the page.

• Visitors must enter a valid password to view the content
• Useful for private content, client pages, or internal documentation

Publish Date

Unlike posts, the publish date for pages:

• Is not shown on the frontend
• Is used internally for sorting and organization

Status

Controls page visibility:

• Publish - visible on the frontend
• Draft / Pending / Private - hidden from visitors

Only published pages appear on your site.

Sites

If you are using a multi‑site setup, you can choose which sites the page belongs to.

• Check one or multiple sites
• Each site can have its own navigation and visibility rules

Template

Select a layout template for the page.

Examples:

• A Contact template with a built‑in form
• A Full‑width template for landing pages
• A Default template for standard content pages

Templates allow you to change the structure and design without modifying content.

Menus are fully editable using drag‑and‑drop, making it easy to reorder, nest, or regroup items.

Menu Structure & Organization

Menu items support hierarchical nesting, allowing you to create:

• Simple top‑level navigation
• Dropdown menus
• Multi‑level submenus
• Mega menu layouts

You can reorder items at any time by dragging them into a new position or nesting them under another item.

Sites

If you are running a multi‑site installation, you can choose which websites a menu belongs to.

A menu can be:

• Assigned to one site
• Shared across multiple sites
• Customized per site if needed

This is useful for multi‑brand setups or websites with different navigation structures.

Menu Items

Each menu item can link to different types of content. When adding a new item, choose from the following types:

Page

Links to a specific page.
An autocomplete field helps you quickly find the page.

Post

Links to a specific blog post.

Product

Links to a product in your store.

Link

Links to any internal or external URL.

Text

Displays custom HTML content.
Useful for mega menus, section headers, or non‑clickable labels.

Home Page

Automatically links to the homepage.
In multi‑language sites, it generates the correct homepage URL for each language.

Blog

Links to the blog posts list.

Shop

Links to the product catalog.

Multi‑Language Support

Menu item names and text fields support multiple languages.
When editing a menu item, you can switch languages and provide translations for each one.

Menu Item Actions

Each menu item includes the following actions:

• Edit - open the menu item editor
• Add child - create a submenu item under the current item
• Delete - remove the item from the menu

These actions make it easy to build complex navigation structures.

Bulk Delete

You can delete multiple menu items at once:

1. Select multiple items using the checkboxes
2. A Bulk Delete button will appear
3. Confirm deletion

This is useful when cleaning up large menus.

Comment Moderation

From the Comments section, you can manage every comment submitted on your posts. Each comment can be:

• Approved - Makes the comment visible on the frontend
• Edited - Modify the comment text or author details
• Trashed - Moves the comment to the trash (recoverable)
• Deleted - Permanently removes the comment
• Marked as spam - Flags the comment as spam and hides it

These tools help you keep discussions clean, relevant, and safe.

Anonymous Comments

You can choose whether visitors must be logged in to comment.

To disable anonymous comments, go to:

Site Settings → Commentssite settings

This prevents unregistered users from posting and helps reduce spam.

Comment Display

Approved comments appear on the post page, usually below the content.
Depending on your theme, comments may include:

• Author name
• Date and time
• Reply threading
• Gravatar or avatar support

Unlike tags, which describe specific topics, categories define the broader sections of your content.

Hierarchy & Organization

Categories can be arranged in a tree structure, meaning you can create:

• Parent categories (e.g., Technology)
• Subcategories (e.g., Software, Hardware)
• Nested structures for more complex blogs

This helps visitors browse content more easily and improves SEO by creating meaningful content groupings.

Drag‑and‑Drop Management

You can reorder and reorganize categories using drag and drop:

• Move a category up or down
• Nest a category under another
• Restructure your entire category tree at any time

Changes are applied instantly and reflected across all posts using those categories.

Assigning Categories to Posts

When editing a post, you can:

• Select one or multiple categories
• Create new categories directly from the post editor
• Manage categories separately from the Categories page

This makes it easy to keep your content organized as your site grows.

Posts are entries that display usually in reverse order on your blog page or posts/blog sections. Posts can have user comments and are included in your site’s RSS feed.

Each table row contains the following columns:

• Thumbnail
• Post Name
• Number of commments

Quick actions

When hovering a post quick action buttons will be visible to allow you to quickly view or design the post page.

• Edit button will open the post edit page.
• View button will show the post page how is visible to your site visitors.
• Design button will load the post page in the page builder for post specific customizations. You can save the changes to a custom template with the Save as new template option that will apply the changes only for this post, choosing default template will apply the changes to all posts.

Bulk delete

Selecting more than one post or clicking on the top checkbox will show the bulk delete button.

Filters

Available post filters:

• Search
• Month
• Status
• Author

Posts Management

Posts are content entries that typically appear in reverse chronological order on your blog page or in any posts/blog components. They can include comments, metadata, featured media, and are automatically included in your site’s RSS feed.

Posts List Overview

Each row in the posts table displays key information about a post:

• Thumbnail - Preview of the featured image
• Post Name - Title of the post (shown in the currently selected language)
• Author - Admin user who created the post
• Comments - Number of comments received
• Date Updated - Last modification date
• Status - Publish, Draft, Pending, Private, Scheduled
• Actions - Quick access to editing tools

Quick Actions

When hovering over a post, quick action buttons appear, allowing you to manage the post efficiently:

• Edit - Opens the post edit page
• View - Shows the post as visitors see it on the frontend
• Design - Loads the post in the Page Builder for layout customization

Using the Design option, you can:

• Save changes as a new template (applies only to this post)
• Use the default template (applies to all posts using that layout)

Bulk Delete

You can delete multiple posts at once:

1. Select multiple posts using the checkboxes
2. A Bulk Delete button will appear
3. Confirm deletion

This is useful for cleaning up old or test content.

Filters

The posts list includes several filters to help you quickly find specific content:

• Search - Searches through post titles and content
• Month - Filters posts by month and year
• Status - Publish, Draft, Pending, Private, Scheduled
• Author - Filters posts by admin user

These filters make it easy to manage large blogs or multi‑author sites.

You can add tags directly from the post edit page:

• Start typing in the tag field
• Choose an existing tag from the autocomplete list
• Or enter a new tag - it will be created automatically when the post is saved

Why Use Tags?

Tags allow you to:

• Connect posts with similar themes
• Improve content discoverability
• Create tag‑based archive pages
• Enhance SEO by organizing topics more precisely than categories

While categories define broad structure, tags describe specific details.

Managing Tags

Tags are created automatically when added to a post, but you can also:

• Edit or delete tags from the Tags section in the admin
• Merge or rename tags to clean up duplicates
• Translate tag names in multi‑language setups

This keeps your taxonomy organized as your blog grows.

Just like comments they have different status like pending, spam, trash etc.

Answer them under Products → Questions: new questions stay pending (hidden on the storefront) until approved. Replies notify the asker, building a public Q&A that reduces support load.

You can reorder or move categories with drag and drop from one place to another.

Manage them under Products → Taxonomy → Categories. Each category has a name, slug, description and image; the slug sets the category page url. Assign products to categories from the product edit page (Links tab) so they appear in the storefront navigation, filters and the category pages.

If the user has an order that included the product then a verified bought badge is displayed in the review.

Just like comments they have different status like pending, spam, trash etc.

Moderate them under Products → Reviews: approve or reject new reviews, reply, and remove spam. Reviews waiting for approval stay hidden on the storefront until you publish them.

Translating a string

From the editor's translate dialog you can enter one source text and provide the translated value for each available language at once. The values are stored in the matching language translation files (locale/<lang>/LC_MESSAGES).

Translation domains

Strings live in domains - groups per theme/plugin/admin core. When translating you pick the domain matching where the string is used, which keeps themes and plugins independent from each other.

Workflow

1. Choose the target language
2. Pick the domain (theme, plugin or app)
3. Search for the string or add a new one
4. Save - the translation is compiled and used immediately on the frontend

For content translations (the same post in multiple languages) use the language tabs in the post editor instead - see Posts.

Open it from the admin menu under Themes → Code editor (it is also used by plugins, e.g. the SEO plugin's schema templates and robots.txt editing link to it).

What you can edit

The editor works on the folders that make up your site's front-end:

• themes/ - the active theme's HTML, CSS and JS files
• plugins/ - public assets of installed plugins
• public/ - site-level files like robots.txt / vrobots.txt

A file tree on the left lets you browse directories; clicking a file loads it with syntax highlighting.

Safety rules

To protect the site from accidental breakage:

• Executable extensions cannot be saved (php, tpl, phtml, htaccess, exe, phar, …)
• Files are saved in place - create a backup before bulk edits
• Changes to theme HTML trigger recompilation of templates so changes appear immediately

Tips

• Use the editor for small tweaks; for larger development work edit files on disk with your own tools
• After saving a .css/.js file, clear the assets cache from Cache if changes don't appear
• Plugin-provided files (like SEO schema templates) are documented by each plugin

Restoring

1. Open the page in the page builder
2. Open the revisions panel / menu entry
3. Pick a previous save to preview its layout
4. Restore to make it current

Like post revisions, restoring keeps the replaced version in history so nothing is lost. Use it to experiment freely with redesigns.

Saving global sections

Any element or section in the page builder can be marked as global (for example data-v-save-global="index.html,.header" on shared parts of a page). When a section is saved as global:

1. It is stored once (by default in index.html)
2. Every page that includes it renders the same content
3. Editing it in one place updates all pages using it

This is ideal for headers, footers, navigation menus and promotional banners.

The Reusable section group

Saved blocks appear in the page builder's left panel under the Reusable group alongside the theme's own sections. From there they can be dragged onto any page like any other block.

Workflow tips

• Keep global content truly generic - per-page content belongs on the page itself
• If a global section must differ slightly between pages, save two variants under different names
• Global blocks are regular theme files, so they are included in file backups and can be edited with the code editor

There are three kinds of elements that can be added to pages: sections, components and blocks.

Sections

Sections are groups of elements that are grouped in a horizontal box on your page such as heroes, navigation bars, call to action etc.

See the sections list for details.

Components

Components are elements that have properties that can be edited when clicked, elements such as images, headings, paragraphs etc.

See the components list for details.

Blocks

Blocks are groups of elements that are used as quick templates that can be dropped on the page such as contact forms, product or post lists, carousels, sliders, image galleries etc.

See the blocks list for details.

Styles

Styles can be used to change a theme appearance/style like typography or color palette.

Plans vs subscriptions

• Plans (under Settings) define the billing schedule - period, interval, price
• Subscriptions listed here are active agreements created by customers when they buy such a product

Managing subscriptions

Open a subscription to see its plan, next billing date, cycle count and current status. Depending on the payment plugin you can cancel or suspend it; provider webhooks keep the state in sync afterwards.

Manage them under Ecommerce → Warehouses. Open a warehouse to edit its address, toggle enabled status, and assign products to it; unassigned products fall back to the default (first active) warehouse.

Permissions are based on module paths, which correspond to the sections and actions inside the admin panel. Each role contains two rule lists:

• Allow list - explicitly grants access
• Deny list - restricts or overrides access

Vvveb checks the allow list first, then applies deny rules to limit or block specific actions.

Understanding Module Paths

Every admin page or action has a module path.
For example:

• Posts list: content/posts
• Post editor: content/posts/edit
• Product list: product/list
• Plugin settings: plugins/contact-form

You can see the module path directly in the URL when navigating the admin panel.

Allowing or Denying Access

To control access:

• Add a module path to the allow list to grant permission
• Add a module path to the deny list to block permission

This gives you fine‑grained control over what each role can do.

Using Wildcards

Wildcards (*) let you apply rules to entire groups of modules or actions.

Examples

Allow access to all content modules

content/*

This covers posts, pages, categories, menus, and more.

Deny delete actions for all content modules

content/*/delete

Users can still view and edit content, but cannot delete anything.

Deny delete actions globally

*/delete

Blocks delete actions across the entire admin panel.

Allow access to all plugin settings

plugins/*

Allow or deny access to a specific plugin

plugins/contact-form

How Allow and Deny Rules Interact

Vvveb processes rules in this order:

1. Allow list - grants access
2. Deny list - restricts or overrides access

This means you can allow broad access, then selectively block sensitive areas.

Example

Allow full access to products:

product/*

Then deny delete and category management:

product/*/delete
product/categories

This gives users access to products and orders, but prevents them from deleting items or modifying categories.

Practical Use Cases

Content‑only roles

Allow:

content/*
editor/*
media/*

Deny:

content/*/delete

Ecommerce manager

Allow:

product/*
order/*

Deny:

settings/*
tools/*

Restricted demo account

Allow:

content/*
product/*

Deny:

*/save
*/delete
settings/*
tools/*

Summary

Admin roles give you powerful control over who can access what inside Vvveb.
Using allow/deny rules and wildcards, you can build roles tailored to:

• Editors
• Authors
• Ecommerce managers
• Developers
• Demo users
• API integrations

This ensures your site stays secure while giving each team member exactly the access they need.

Creating a token

1. Go to Admin → Auth tokens Click Add, select the user the token acts as
2. Save - the generated token string is shown once; copy it immediately

Using a token

Send it with requests, e.g. as Authorization: Bearer <token> (or per integration instructions). Requests run with the permissions of the linked admin user.

Security

• Treat tokens like passwords - revoke any token you can't account for
• Delete tokens that are no longer used from the list
• All token usage appears in logs like normal admin activity

With the ActivityPub plugin installed, your Vvveb website functions as a federated profile, along with profiles for each admin user.

If your website is example.com, then the profile can be found at @example.com@example.com, and authors like Joe would have their individual profiles at @joe@example.com

Once you follow Jane’s @jane@example.com profile, any blog post she crafts on example.com will show in your Home feed.

1. Install the ActivityPub plugin.
2. Go to Mastodon or another federated platform, and search for your profile and follow it.
3. Your profile will be in the form of either @your_username@example.com eg @admin@demo.vvveb.com.
4. On your site, publish a new post.
5. From Mastodon, check to see if the new post appears in your feed.

Plugin repository https://github.com/Vvveb/activitypub.

Recommended microblogging microblogging theme https://themes.vvveb.com/products/manny.

The plugin works with the following tested federated platforms, but there may be more that it works with as well:

• Mastodon
• Pleroma
• Akkoma
• friendica
• Hubzilla
• Pixelfed
• Socialhome
• Misskey

It may take a few minutes for the new post to show up in your federated feed.

Once ActivityPub is installed, only new posts will be available in the fediverse.

Users will never see previously published posts in their feed.

With ActivityPub, if someone follows your site, they will only receive new blog posts you publish from then on.

Plugin repository https://github.com/Vvveb/editor-js.

Plugin repository https://github.com/Vvveb/sun-editor.

Plugin repository https://github.com/Vvveb/minify.

Plugin repository https://github.com/Vvveb/catalog-mode.

Plugin repository https://github.com/Vvveb/hide-language-selector.

Plugin repository https://github.com/Vvveb/dicebear.

Example plugin that adds a menu entry in the admin dashboard and a new page on frontend with a list of products.

Plugin repository https://github.com/Vvveb/graphql.

Plugin repository https://github.com/Vvveb/tinymce-plugins

Used in production on docs.vvveb.com.

Behavior

• Scans post content for headings and generates anchor links
• Clicking an entry scrolls to the section; the current section is highlighted while scrolling
• Long posts become easier to scan, which also helps search engines show jump links

Uses adminer for database management.

Usage

1. Activate the plugin
2. Open its settings page (Settings link on the Plugins list)
3. Paste code in Header scripts and/or Footer scripts Save - snippets are injected site-wide on every page

Common use cases: Google Analytics / Tag Manager, Facebook Pixel, cookie consent widgets, schema markup.

Plugin repository https://github.com/Vvveb/file-manager

Modules

The plugin is modular - enable only the feature areas you need from Settings → SEO → Modules:

Core (v1)

• On-page SEO & Content Score - focus keywords, SERP preview, real-time score in the editor
• Schema Builder - per-page structured data without writing JSON-LD
• XML Sitemaps - auto-generated /sitemap.xml plus section sitemaps
• Redirections & 404 Monitor - redirect manager with automatic slug-change suggestions
• SEO Audit - site-wide technical checks with a prioritized fix list
• Setup Wizard - guided configuration flow

Local, ecommerce & AI (v2)

• Local SEO, Ecommerce SEO, Search Console & Rank Tracker, llms.txt, AI Content Assist, Instant Indexing, AI Search Tracking

Documentation

• Plugin settings

Shows a debug bar on the bottom of the page with sql queries, filters etc

Plugin repository https://github.com/Vvveb/brevo-email.

The popup can be customized from the page builder. Open the plugin settings to choose banner style, consent categories and which regions see the notice.

Settings

Open Plugins > AI Assistant > Settings and save once after enabling. The three fields that matter most are provider, key and model - the rest have working defaults. Bulk-translation overrides (provider, model, key, glossary) live on the separate Translate tab; writer voice, disclosure and stock covers live on the Writer tab.

Provider

Type to search all providers from the models.dev catalog (around two hundred, e.g. OpenAI, Anthropic, Google, DeepSeek, Groq, Mistral, xAI, OpenRouter, OpenCode Zen, NVIDIA NIM). The dropdown option shows the display name and model count.

Unknown slugs stay typable on purpose: a brand-new models.dev provider works for chat immediately, and rebuilding the catalog below adds it to the list with full metadata.

API key

One key for the active provider - the placeholder hint follows the selection (sk-ant-…, AIza…, …). Switching providers keeps each provider's key server-side; only the active one is ever used. Installations that saved per-provider keys before keep working: the old key is carried over the first time you save.

Model

Type to search the selected provider's models. Picking a known model auto-fills context size and max tokens from the catalog and stores a metadata snapshot used at runtime. The info line under the field shows context window, max output, per-1M pricing, reasoning support (including which API dialect a routed model uses, e.g. via responses API), attachment kinds and tool support. Free text stays allowed for ids missing from the catalog - the manual context fields apply then.

Refresh fetches the live model list through the proxy (or directly from the provider in direct mode). Catalog rebuilds the whole local catalog from models.dev on the server (php cli.php admin module=plugins/ai-assistant/settings action=buildModels does the same from the command line) and reloads the current list.

Endpoint override (Url)

Optional custom endpoint for the active provider, e.g. a self-hosted gateway speaking its API. Empty means the catalog endpoint. Changing provider empties the field automatically with a notice, so a stale override can never silently misroute the new provider.

General tab - connection, model, shared behavior

• Api mode - proxy relays requests through the site backend so keys never reach the browser; direct calls the provider from the browser (the key travels client-side, and the provider must allow the browser origin - e.g. OLLAMA_ORIGINS for Ollama). For a local server: direct reaches the LLM on your own computer, proxy reaches the LLM on the web server.
• Proxy URL - the address the browser calls for relayed requests. Leave the default unless the admin path is customized; only used in proxy mode.
• Session header - upstream header carrying the chat session id on proxied requests (default x-vvveb-session), so provider-side logs correlate with a conversation. It never lands in the provider body; empty disables it.
• System prompt - appended to every chat request to set assistant behaviour. Keep it short; bulk jobs use their own task prompts plus this line.
• Temperature - sampling randomness for chat (0 = deterministic). Omitted automatically for reasoning models that reject it; bulk translate/write set their own values (0 and 0.7).
• Context size / Max tokens - auto-filled from the catalog when you pick a known model. Context size drives the usage bar and auto-compact; max tokens caps each answer and is clamped to the model's own output limit, so an oversized value fails safe instead of 400ing upstream.
• Image model / provider / key / size - the editor's Generate image from text button and writer cover art. Provider and key empty inherit the main ones above (e.g. chat locally, images via OpenAI); local servers have no images API, so covers need a compatible provider here. Size examples: 1024x1024, 1792x1024.
• Monthly token cap - max bulk tokens per admin per calendar month (0 = off). Every bulk action checks it before spending and fails fast with used/cap numbers; previews show month-to-date next to the estimate.
• Job webhook - HTTPS URL posted to (JSON, fire-and-forget) when a bulk job finishes. Your own endpoint: automation tools, not the provider.

Translate tab - bulk translation overrides

All four fields are optional and share one rule: empty inherits the main setting (provider → model → key, in that order; task keys resolve server-side so secrets never travel). The classic setup is a cheap fast model here while chat stays on the strong one. Precedence for keys everywhere in the plugin is task key, then active key, then legacy per-provider keys from older versions.

• Translate provider / model / key - used by Bulk Translate, the write → translate pipeline, and translation cron. A model with a catalog entry also brings its output cap and pricing into estimates.
• Translate glossary - one Original = Replacement per line (e.g. checkout = checkout), always used exactly: bulk translation, pipeline translations, and article writing all inject it. Brand and product names belong here.
• Translate reasoning - Off by default. Sends reasoning_effort: none/minimal only when the model's catalog entry declares it and only on bearer chat dialects, retrying plain if a gateway rejects it. Field translation needs no chain of thought, and you stop paying output rates for discarded thinking.

Writer tab - article voice, disclosure, stock covers

• Tone presets - one Name | instruction per line (e.g. Playful | Write with light humor and vivid examples). The names appear in the writer's Tone dropdown; the text is appended server-side, so clients can only pick, never inject.
• AI disclosure text - appended as a footer when Disclose AI is ticked on a run; empty uses the default reviewed-by-editors sentence. Opt-in per run, never silent.
• Stock provider - source order for Stock link covers: Auto tries each configured API key in order with the keyless Unsplash search last; explicit Unsplash/Pexels API or scrape-only are also selectable.
• Unsplash / Pexels keys - free tiers (Unsplash developers: 50 requests/hour) enable the official search APIs; empty skips straight to the next source. Every candidate is host-allowlisted, IP-checked, downloaded and image-verified before it touches a post.
• Write reasoning - On by default (model behavior unchanged). Turn off once outlines carry your planning - same suppression mechanics as Translate reasoning above.

Using the assistant

• Thinking level (Off/Low/Medium/High) follows the selected model: provider-specific effort values where the catalog defines them, generic levels otherwise, disabled with an explanation when the model cannot reason. Reasoning blocks and tool calls render as collapsible cards with a Running/Done/Failed status pill: thinking streams open and collapses when finished, tool calls stay collapsed throughout (a manual expand pins a card open), errors stay open, and everything hides behind the thinking/tools toggles.
• Attachments - the file picker only offers formats the model takes; anything else is refused with a message naming what is supported. Text files (.txt, .md, .csv, …) are inlined as text so they work on every model including text-only ones; long files are truncated with a marker. Image-capable models also receive page screenshots as vision.
• Costs - every assistant message shows its estimated cost from catalog pricing; the usage footer totals the session and shows cache-hit savings. Encrypted reasoning never renders - it is preserved invisibly so multi-turn tool calls keep working.
• Failures - dropped connections and overloaded providers retry automatically with backoff (1s → 2s → 4s, longer for rate limits) and a live countdown; Stop cancels the wait. Deterministic errors (bad key, unknown model, full context) surface immediately with guidance instead.
• Sessions survive reloads and sync server-side; Compact shrinks a long conversation into a summary when context runs out. When browser storage nears its quota, sessions upload automatically and older local copies trim to metadata (reloaded on open) - a warning replaces the old silent failure.
• The assistant UI follows the admin language through the CMS-wide Vvveb.i18n runtime (public/js/libs/gettext.js, gettext-compatible plurals): sidebar, manager and editor strings translate from the same catalogs as the backend (translators add the msgids from plugins/ai-assistant/system/i18n-data.php to locale/<lang>/LC_MESSAGES/vvveb.po; English always works untranslated).
• Article writer (Plugins → AI Article Writer) turns a topic list (one per line, up to 200) into draft posts: pick language, site, categories (multi), tags, length (short/medium/long) and status (draft default - bulk AI content never auto-publishes), preview the call/token estimate, then run the resumable stepper with per-topic results. Uses the active chat model (writing wants the strongest model) with temperature 0.7, JSON mode + repair retry, and core post creation (headline, HTML body, excerpt, meta description/keywords, cover alt, slug, site link). Re-running the same topics skips already-written ones (topic-hash ledger, reported with the original post id). Outlines runs a cheap planning pass first - tick approved topics and Start writes only those. Completion notices report tokens used; the last run summary persists on the page. Cover image switch: No cover, AI-generated (paints one cover per article via the image task settings), or Stock link. Stock mode resolves sources through a provider registry (system/stock.php - implement StockProvider and add one line to register the next one): the Stock provider setting picks Auto (every configured API key in order, keyless scrape last), Unsplash API, Pexels API, or scrape-only. API results carry photographer credit into the run log; a random hit from the first 10 is verified and stored, failures fall through to a model-suggested URL and then to generation, each step logged. Every candidate is validated (allowlisted CDN host, public IP, real image ≥200×200) before it touches a post; anything suspicious is rejected down the chain. Covers save under media/ai-assistant/; a failed cover still saves the post, imageless, with a warning. Stock photos carry the source URL in the log - check the license before publishing.
• Drip publishing. Set Publish from + Every N days and articles are created scheduled with staggered dates on the ledger instead of the chosen status. Release due (also checked automatically at each run start) flips due posts to published - never overriding a status you changed by hand. Cron it with php cli.php admin module=plugins/ai-assistant/generate action=release for hands-free drip.
• Unattended jobs (cron). Three idempotent CLI actions, safe on a schedule: …/generate action=release (publish due drip), …/generate action=refreshcron language=1 limit=5 (rewrite the oldest posts), …/translate action=translatecron source=1 targets=2,3 limit=10 (translate the newest missing items). CLI skips CSRF (no session exists there); every step lands in the runs ledger with a cron-YYYYMMDD job id.
• Write → translate pipeline. Also translate to fans every finished article out to more languages in the same run (same provider call path as bulk translate, translations linked on the ledger so re-runs skip them).
• Grounded writing. Source URLs are fetched once per run and injected as background material (budget-capped) so articles can cite real facts instead of hallucinating them.
• Refresh stale posts. Switch to Refresh mode, Find stale posts lists candidates by age with checkboxes, Start rewrites the checked ones in place (slug untouched, honors tone + budget).
• Internal linking. After a write, Add links appends a related-reading block (keyword search over published posts, idempotent marker, skipped when nothing related).
• Social pack. Tick Social pack for an X thread, LinkedIn post and newsletter teaser per article, with copy buttons right in the result row.
• AI performance report. The writer page reports AI-written vs human posts and views over the ledger (proving whether any of this earns its keep).
• Upstream timeouts. A step failing with Upstream request failed … timed out … 0 bytes received means the provider never started answering within 180s (queue, reasoning prefill, cold model, huge prompt) - not a stalled download, so raising max_tokens won't help. The item fails individually and resumes on re-run; check provider status, trim grounding sources, switch reasoning off, or try a faster model before reaching for longer timeouts.
• Token budgets. A per-run token cap on both bulk pages halts the stepper (stays resumable) with a notice; the server double-checks the client-reported spend.
• Writer extras. Tone presets (Settings, Name | instruction lines), per-topic model tags merged with run-wide tags, alternative headlines in each result, multi-site fan-out, CSV topic upload, multi-category, auto-categorize (the model files each article from your category list, validated server-side), QA sieve (thin/tell flags in the log), series mode (part numbering + series plan in every prompt), and a translate glossary (Original = Replacement lines in Settings) for consistent bulk translation.
• Reasoning toggles. Chain-of-thought is pure overhead on strict bulk tasks (you pay output rates for tokens nobody reads). Translate reasoning defaults off and Write reasoning stays on; either sends reasoning_effort: none/minimal only when the model's catalog entry declares it, only on bearer chat dialects, and silently retries without the flag if a gateway rejects it.
• Product writer. The writer's Write switch covers products: descriptions with meta, disabled-by-default (publish = enable explicitly), covers, pipeline translation and social on the same runner. Scheduled drip and categories are post-only; product duplicates ledger separately.
• Refresh, SEO, links. Refresh mode rewrites stale posts in place (slug untouched); SEO backfill fills only missing excerpt/meta. Add links appends related-reading blocks found by keyword search. Every overwrite records a content revision first, so the editor's revision history is your undo.
• Review & bulk publish. Needs review lists recently written posts and products from the ledger with editor links; tick and Publish listed flips drafts/scheduled (or disabled products) live, skipping anything already published. Every bulk overwrite records a content revision first, so the editor's revision history is your undo.
• Product writer & parity. The Write switch covers products end-to-end: descriptions, disabled-by-default, covers (+gallery from extra stock hits), pipeline translation, social, refresh, SEO backfill and internal links all branch on post/product, with separate duplicate ledgers and a product performance report.
• Cost & transparency. Preview shows a dollar forecast at the active model's catalog rates; completion notices report tokens used; every bulk step lands in the Recent bulk runs ledger; an opt-in Disclose checkbox appends the configured AI note (Settings → AI disclosure text).
• Runs ledger & report. Every bulk step records calls + tokens grouped by job id (Recent bulk runs table); the performance card compares AI vs human posts/views with click-through drill-down to the actual posts; Upcoming drip lists scheduled releases (posts and products). Script tags carry mtime cache-busting so fixes actually arrive in the browser.
• Social viewer. Saved packs rehydrate per post: the result-row Social button expands the full channel texts with copy buttons, backed by the ai_social table instead of the volatile run response.
• Prompt playground. Settings page lab for trying system/user prompts against the active model (templates included for every job shape: chat, writer, translate, outline, SEO, social), with token usage per run. Nothing is saved.
• Product SEO preview. The stale/SEO finder and all runners honor the post/product switch, so backfill and refresh cover catalogs too. Note: scraping is against Unsplash's ToS (they prefer the API); if they block it, stock mode degrades gracefully to suggestion → generation.
• Taxonomy & menu translation. The Type dropdown on AI Translate also covers Taxonomies (category/tag names across all taxonomies) and Menus (item labels): same source/target pickers, title search, preview matrix and stepped runner, translating name (+ empty content) with glossary and JSON mode. Slugs are preserved (menus) or left for core to regenerate (categories, empty); categories carrying SEO meta in any language are skipped, because the category save rewrites every language row and cannot preserve meta.
• Translation memory. Identical source text is translated once and reused from the ai_memory table (keyed by normalized text + language pair + model), so repeated boilerplate, specs and headers stop costing tokens on every run. Same text on a different model still translates fresh; prune old rows manually if the table grows.
• Media alt text. The writer's fourth mode describes library images into their caption field: Find images missing alt lists the first captioned-less images, Start sends each (downscaled to 1024px) to a vision model. Requires an image-capable active model (modalities in the catalog) - otherwise the run errors with guidance instead of burning calls. Results log per image; failures skip individually.
• Monthly token cap. Monthly token cap (Settings, 0 = off) gates every bulk action per admin and calendar month: runs fail fast with used/cap numbers once reached, and both previews show month-to-date spend next to the estimate. CLI cron counts under its own (usually zero) admin, so cap cron separately if it matters.
• Presets & webhooks. Export downloads the current filter set as JSON; Import loads it back (review, then Preview). Job webhook (Settings) POSTs {page, processed, usage, at} fire-and-forget when a bulk job finishes - point it at your own HTTPS endpoint for n8n/Zapier handoffs.
• Bulk translate (Plugins → AI Translate) translates posts and products across languages in resumable steps: filter by type, status, site, category (with children), date and title, preview the missing-translation matrix with a call estimate, then run with progress, per-item skip-and-report errors, stop/resume, and bulk JSON export. Only empty translations are touched by default. Oversized documents translate piece by piece (block-boundary chunking) instead of skipping via the old context guard. Uses the translate provider/model/key settings, so a cheap model keeps it affordable; strict tasks request JSON mode with automatic fallback.
• Sessions manager (Plugins → AI Sessions) lists every chat with title search (or Everywhere mode, which also scans message text), sorting and paging; sessions open at #uuid links for sharing. Each row opens a read-only transcript each row opens a read-only transcript with the same collapsible thinking/tool cards plus a message/token/cost summary priced at the session's own model when known, and offers rename, fork (independent copy under a fresh id), pin (per-browser favorites sort first), delete (bulk included), single or bulk JSON export (with an attachments checkbox for a small text-only file) and Continue in sidebar, which hands the session to the site-editor sidebar. Sessions living only in the browser (never synced - e.g. from installs predating the server store, which self-creates on first use) are flagged with a one-click Sync to server banner instead of silently missing.
• Sidebar sessions can be filtered from the dropdown itself and pinned favorites always list first.

Troubleshooting

• 401 / invalid key - re-enter the key for the active provider and save.
• 404 / no such model - the id was retired or mistyped; Refresh the list or pick from the dropdown.
• 429 / rate limit - the assistant waits and retries on its own; lower pace or raise quota for persistent limits.
• Context full - use Compact, start a new session, or lower max tokens.
• Attachment refused - the message names the supported kinds; switch to a multimodal model for images, PDFs or audio.
• Empty model list - rebuild with the Catalog button (or the CLI command above).
• 500 from the upstream gateway - almost always a dialect mismatch: a chat-shaped body (messages/max_tokens) sent to a /responses endpoint, or the reverse. It happens with unrouted model ids plus a stale endpoint override. The proxy now rejects these with a plain-language 400 before relaying; fix by re-selecting the model in settings (stores its route) and saving, or by pointing the override at the matching endpoint.

Setup

1. Activate the plugin and open its settings (/admin/index.php?module=plugins/stripe/settings)
2. Enter your publishable + secret keys (test keys first: pk_test_… / sk_test_…)
3. Enable the payment method for the site - it appears in checkout alongside other methods

Test with card 4242 4242 4242 4242 before switching to live keys. Webhooks handle renewals, failed-payment retries and subscription status sync.

Plugin repository https://github.com/Vvveb/stripe.

Builtin honeypot anti spam filter.

Contact form component allows visual customization of forms from the page builder, add any fields visually.

This plugin is included and activated by default