RIVISTA.

RIVISTA is an editorial WordPress theme for fashion, design and lifestyle brands. It pairs a magazine-style front end with a complete WooCommerce storefront, and ships a one-click demo that builds the whole site for you.

Nothing in the theme depends on a page builder, an animation library or a remote service. Every layout is plain WordPress content styled by the theme, every script is vanilla JavaScript, and every font and photograph travels inside the package.

What is inside the download

What the theme does not do

So you can plan around it: RIVISTA does not register custom post types, does not include a page builder, does not ship a slider plugin, and does not add product filters, a currency switcher or a live-search plugin. Product data, stock, reviews, shipping and taxes all come from WooCommerce.

The only things it registers beyond templates and Customizer settings are one block style and one block pattern. The four section shortcodes — [rivista_products], [rivista_journal], [rivista_values] and [rivista_newsletter] (section 11) — are implemented by the bundled RIVISTA Core plugin: it owns both the tags and the render code behind them, so shortcode content keeps rendering even after a theme switch, while this theme’s stylesheets give the sections their full design. The front page’s values and newsletter bands come from the same plugin functions — without RIVISTA Core they are simply omitted and the rest of the front page is unaffected. Pages that use the shortcodes — including several of the imported demo homepages — need RIVISTA Core active, or the tags print as plain text.

RIVISTA runs on a standard WordPress host. The only firm numbers are the ones in the theme header.

A fresh WordPress install gives the cleanest result. If you are installing over an existing site, back up the database and the uploads folder first.

Install the theme

1. Unzip the package you downloaded from the marketplace and find rivista-theme.zip. That single file is the theme; the rest of the download is documentation and licences.

2. In WordPress go to Appearance → Themes → Add New → Upload Theme, choose rivista-theme.zip and press Install Now.

3. Press Activate.

4. Alternatively, upload the unzipped rivista folder to wp-content/themes/ over FTP or SFTP, then activate it from Appearance → Themes.

Plugins

After activation a dashboard notice appears and a new screen is added at Appearance → Install Plugins. Every plugin there is recommended, not required — the theme works without them, with the matching features simply absent.

1. Open Appearance → Install Plugins.

2. Install and activate WooCommerce, Contact Form 7 and One Click Demo Import before importing the demo — products and forms are skipped if their plugins are missing at import time.

3. Install RIVISTA Core — it implements the four section shortcodes the demo homepages use, and (with Elementor) the Elementor widgets.

4. Run the WooCommerce setup wizard when it offers itself, or skip it and configure the store later from WooCommerce → Settings.

One import builds the entire demo site: every page, the journal, ten products, the photography, the menus and the front-page settings. There is a single import package — all twenty homepage demos arrive together.

Before you start

• Use a fresh site, or back up an existing one. The import adds content; it does not remove yours, but it does delete WordPress’s own “Sample Page” and “Hello world!” when they are still untouched.
• Activate WooCommerce, Contact Form 7 and One Click Demo Import first.
• Make sure wp-content/uploads is writable and that the server can request its own URLs — the photographs are fetched from the theme folder over HTTP.

Run the import

1. Open Appearance → Import Demo Data.

2. The theme registers a single import — RIVISTA Complete Demo: “Pages, journal posts, products, media, and navigation from the complete RIVISTA demo.” Because it is the only one, One Click Demo Import shows the theme card rather than a list. Press Import Demo Data and confirm.

3. Leave the tab open. The importer works in batches and the photographs are copied one by one; on a modest host this takes a few minutes.

4. Wait for the completion screen before navigating away. The final step rebuilds menus, assigns pages and flushes permalinks.

5. Visit the site. You should land on the editorial home page with the announcement ticker running above the header.

What gets imported

What happens after the import

The theme finishes the setup for you. In order, it:

• Assigns the RIVISTA layout template and per-page styling to every imported layout page.
• Sets Settings → Reading to a static front page: Home as the front page and Magazine as the posts page.
• Points WooCommerce at the imported Shop, Cart, Checkout and My account pages, and removes any duplicate copies the importer created.
• Turns WooCommerce’s “Coming soon” site visibility off, so the store becomes publicly visible.
• Sets the header style to Standard and the layout direction to Left to right.
• Writes the announcement ticker text. It always ends with “New drop every Thursday | 30-day easy returns”. A free-shipping message is put in front of those only when your store already offers free shipping: “Free shipping over $80” in your own currency, rounded to whole units by WooCommerce’s own price formatting, when a Free shipping method carries a minimum order amount; a plain “Free shipping” when one carries none; and nothing at all when the store has no free-shipping method, or when WooCommerce is not active.
• Rebuilds all seven menus from scratch, flat, and assigns them to their locations.
• Moves WordPress’s five install-time widgets out of the footer into Inactive Widgets — they are never deleted, and widgets you added yourself are never touched.
• Flushes the permalink rules.

Your site title, tagline, store currency and permalink structure are deliberately left alone, as are the colour pack, font pairing, style switcher and newsletter shortcode.

Import troubleshooting

Ten minutes of settings turn the demo into your shop. Work down this list in order.

Front page and blog

The import already sets these, but this is where you change them. Open Settings → Reading, keep A static page selected, and choose your homepage — the built-in Home, or any of the twenty demos (section 06). The Posts page is the journal index; the demo uses Magazine.

One condition: the page you pick must have a page template assigned, because a front page left on the default template falls through to the theme’s own editorial homepage. Every imported layout page carries one — all sixty-six of them, the twenty demos included. The five live WooCommerce and blog pages (Shop, Cart, Checkout, My account and Magazine) deliberately do not, because WordPress and WooCommerce drive them; do not pick one of those as your homepage. For a page you built yourself, open it and set Page → Template to RIVISTA Demo Full Width (or Editorial Home if you want the built-in homepage on that page), then save.

Site title, tagline and logo

Go to Appearance → Customize → Site Identity. Upload a logo (the theme suggests 200 × 50 px and accepts flexible sizes); without one, the site title is used as the wordmark. The site description is shown as the eyebrow above the footer newsletter band, so keep it short.

Menus and their locations

Menus live under Appearance → Menus. The theme registers eight locations:

Empty locations simply do not render. The Social location is the one the demo leaves for you: create a menu of custom links to your profiles and assign it there.

WooCommerce pages, currency and tax

1. Check WooCommerce → Settings → Advanced — Cart, Checkout, My account and Terms should point at the imported pages. The import sets Shop, Cart, Checkout and My account for you.

2. Set your country, currency and currency position under WooCommerce → Settings → General. Demo prices are plain numbers, so they pick up the new currency immediately.

3. Configure tax under WooCommerce → Settings → Tax if you charge it.

Shipping — and the free-shipping chip

Set your zones and rates under WooCommerce → Settings → Shipping. One setting feeds the front end directly:

1. Open a shipping zone and choose Add shipping method → Free shipping.

2. Edit the method and pick a requirement such as A minimum order amount, then enter the amount.

3. The homepage chip strip reads that configuration and shows “Free shipping over <amount>” in your store currency. With a Free shipping method but no minimum it shows simply “Free shipping”; with no Free shipping method anywhere, no free-shipping chip is shown at all. Nothing is invented.

Payments

Add gateways under WooCommerce → Settings → Payments and place one real test order end to end — cart, checkout, order received, and the order inside My account → Orders. All four screens are styled by the theme, so this is the fastest way to confirm everything is wired up.

Pre-launch checklist

1. Choose the homepage, colour pack and font pairing.

2. Upload the logo and write the tagline.

3. Replace demo products and photography with your own.

4. Finish shipping, tax and payments; place a test order.

5. Write the Privacy, Terms and Shipping & Returns pages.

6. Build the Social menu; review all seven menus.

7. Replace the static demo contact form with a real Contact Form 7 form and set its mail addresses.

8. Delete the six theme-showcase pages listed in section 04.

9. Set the announcement text, or clear it to hide the ticker.

10. Turn the style switcher off (it already is) before going live.

Twenty demo homepages arrive with the import, alongside the theme’s own live editorial front page. They are ordinary WordPress pages, so switching between them takes one setting and no rebuild.

The built-in editorial home

“Outfit of the day” is rendered in PHP from your real catalogue: a hero look carousel built from WooCommerce products, category tiles with live product counts, the chip strip (section 11), a product grid, an editorial teaser and the shared values and newsletter bands. It is the default front page, and it is also available as the page template Editorial Home so you can put it on any page. The imported Home page uses it.

Switching the homepage

1. Open Settings → Reading.

2. Select A static page and choose your demo in the Homepage dropdown.

3. Save. The page keeps its own layout, styles and scripts — a demo looks the same as the front page as it did as an inner page.

The twenty layouts

Each thumbnail is the top of that demo as the import builds it, on a 1440 px screen. Preview any of them at /index-<name>/.

Seventy-two pages arrive with the demo. Some are live — they read your real data. The rest are hand-built editorial layouts you edit like any other page.

Live reads real WordPress or WooCommerce data. Layout is demo copy stored in the page content: edit the text, prices and names directly in the editor.

Page templates

The theme registers exactly two page templates, selectable in the editor under Page → Template:

Shop & commerce

Account

Six designed account screens — account, account-orders, account-order, account-addresses, account-settings and sign-in — all Layout. They exist so you can show a branded account experience and style-match plugins. The functional account area is my-account.

Editorial & content

Company, help and legal

• Company — about (Studio), sustainability (Our Materials), stores, careers, press.
• Help — faq, shipping-returns, size-guide, contact, order-tracking. The order-tracking page looks up sample order numbers for demonstration; it does not query WooCommerce orders, so replace it with WooCommerce’s own order-tracking form or a tracking plugin.
• Legal — privacy, terms. Both hold placeholder copy. Write your own before launch.

Utility, system and showcase

• search is a designed results page; real search results are rendered by the theme’s own search template at ?s=.
• coming-soon, sliders (twelve slider patterns) and elements (the style guide: colours, type and components) are reference pages — elements is genuinely useful while you customise.
• presentation, demos, all-pages, map, promo and documentation describe the theme, not your store. Delete them before launch.

Every theme option lives in one panel: Appearance → Customize → RIVISTA Settings. There is no separate options page, and nothing is hidden behind a licence key.

Colour packs

All 22 packages, grouped by how they treat the footer:

A pack sets the page background, accent and ink colour for the whole site. Individual demo pages that are designed dark stay dark under any pack.

Typography

Header styles

Layout direction

Automatic follows the site language and switches to right-to-left for Arabic, Persian, Hebrew and Urdu. Left to right and Right to left force the public site regardless of the dashboard language, which is what you want when you administer an RTL store in English. See section 13.

Announcement bar

Whatever you type is announced politely to screen readers and scrolls as a ticker. Separate messages with a pipe, exactly as the import does: Free shipping over $80 | New drop every Thursday | 30-day easy returns. Keep it plain text. (The import writes that first message only when your store really offers free shipping — section 04.)

Newsletter band in the footer

Build a form in Contact Form 7 (or your mailing provider’s plugin), copy its shortcode, and paste it into RIVISTA Settings → Footer Settings → Newsletter form shortcode. The band then shows your tagline as an eyebrow, the site name as a wordmark, and your form. Leave the field empty and the band disappears entirely.

The style switcher

Turned on, a floating button opens a panel where visitors try all 22 colour packs, four typefaces and light or dark mode. Choices are stored in that visitor’s own browser only and never change your site for anyone else.

WordPress settings the theme uses

Outside the RIVISTA panel, these core Customizer sections matter: Site Identity (logo, title, tagline, site icon), Background, Menus, Widgets (one area, Footer Widgets, shown above the footer navigation), Homepage Settings and Additional CSS for small tweaks.

The storefront is WooCommerce, re-drawn. Every feature below works with the plugin alone — no extensions, no accounts, no external service.

Shop archive

• Editorial header with the result count set as a serif superscript beside the title.
• A row of category tabs with live product counts, plus WooCommerce’s sorting select and result count.
• An optional full-width “story” tile woven into the grid after the fourth product, linking to your lookbook. It appears on page one of the main shop only, and only when that page lists at least eight products and a published Lookbook page exists.
• Hairline pagination, or an end-of-collection line that points to the collections page.

Product cards

Used on the shop, category archives, related products, upsells and cross-sells: a 4:5 photograph, badges for Sold out, Sale and “Only N left” when stock is managed and low, a hover stack of wishlist / compare / quick-view buttons, the title, price, category and star rating. The real WooCommerce add-to-cart link sits over the photograph, so AJAX add-to-cart and cart fragments keep working. Simple, purchasable, in-stock products read Add to bag; every other product type keeps WooCommerce’s own wording.

Product page

• WooCommerce’s own gallery with zoom, lightbox and a thumbnail slider — images you add under Product gallery appear automatically.
• The title splits on an em dash, so “Linen Crewneck — Stone” sets the colour in serif italic.
• Price with a computed discount label, star rating (or an invitation to write the first review), short description and the real add-to-cart form for every product type.
• A quantity stepper that respects the product’s minimum, maximum and step values.
• An expandable block of store guarantees — editable through a filter (section 11).
• SKU, categories and tags; the standard Description / Additional information / Reviews tabs; upsells; and the theme’s own “Pair with” block, which shows related products and tops the row up when there are fewer than four.
• A sticky add-to-bag bar that slides in once the buy box scrolls out of view.
• Variable products get a styled attribute picker.

Wishlist

Every card and product page carries a heart. Saved products live in the visitor’s browser — no account, no plugin, nothing stored on your server — and the header shows a live count. The wishlist page renders the real products with prices, a running total, a share link, add-all-to-bag and four suggestions.

Compare

Shoppers can compare up to four products. A sticky tray follows them around the site (a full row on desktop, a “Compare · N” pill on phones that expands on tap and closes with Esc), staying in sync across browser tabs. The tray hides itself on cart, checkout, account and order pages. The compare page builds a real table — price, rating, availability, category, SKU and one row per product attribute — with a switch to highlight only the differences.

Quick view and quick add

The eye icon opens a modal with the product image, category, title, rating, short description, price, a working add-to-cart and a link to the full page. It traps focus and closes with Esc. The plus icon on a card adds a simple product straight to the bag and flips to a tick.

Mini-cart drawer

The header cart button opens a drawer containing WooCommerce’s own mini-cart, refreshed through cart fragments. The theme adds a free-shipping progress meter, a quantity stepper on each line, a clean subtotal row and the note that shipping and taxes are calculated at checkout.

Cart, checkout and orders

The demo cart and checkout pages use the WooCommerce Cart and Checkout blocks, restyled in detail: line items, quantity pills, the coupon field, the order summary, express payment buttons and the phone checkout flow. The empty cart gets its own heading and a “Continue shopping” button. Classic shortcode cart and checkout pages still work and inherit the shared styling. The order-received page and My account → View order are styled too, with the grand total picked out.

Compatibility with other plugins

All shop templates fire the standard WooCommerce hooks — woocommerce_before_main_content, the shop-loop hooks, woocommerce_single_product_summary and the rest — so badge, size-chart, wishlist and review plugins hook in where they expect to. The callbacks the theme draws itself are unhooked in one place, rivista_wc_hook_layout() in inc/commerce-features.php, which a child theme can re-add or reorder.

The Elementor integration lives in a companion plugin, not in the theme, so your content keeps working if you ever change themes.

1. Install RIVISTA Core from Appearance → Install Plugins. It ships inside the theme, so nothing is downloaded.

2. Install and activate Elementor.

3. Edit any page with Elementor and look in the Basic widget category.

Beyond the widgets, the only other thing the plugin ships is the four section shortcodes of section 11 — the tags, the render code behind them, and a small base stylesheet that keeps the sections presentable under other themes — no post types, no settings screen, no demo content. It carries its own translation template at languages/rivista-core.pot with the text domain rivista-core, and its own right-to-left stylesheet.

Everything below belongs in a child theme’s functions.php (section 12) or a small site plugin — never in the parent theme, which an update will overwrite.

Filters the theme provides

Eleven filters, and that is the whole list: RIVISTA fires no custom actions of its own, so anything else you want to move sits on a WordPress or WooCommerce hook. The file under each name is where the filter runs, in case you want to read the surrounding code.

The homepage chip strip

The row of chips under the homepage hero is a filterable array. Each chip is an array with:

The defaults are built to be true for any store, not just the demo:

• A free-shipping chip built from your real WooCommerce settings: “Free shipping over <amount>” in your store currency when a Free shipping method with a minimum order amount exists, “Free shipping” when one exists without a minimum, and no chip at all when your store offers no free shipping.
• Chips that link to real pages the demo import creates — the shipping & returns page, the size guide, gift cards, and the journal article about mending — each shown only when that page or post actually exists on your site. Each label is the page’s own title, so renaming the page renames the chip.

Nothing is claimed that your store has not been configured to do. Add, remove or replace chips with the filter:

<?php
add_filter( 'rivista_home_chips', function ( $chips ) {

    // Add one chip that links to a page.
    $chips[] = array(
        'label' => __( 'Made in our own studio', 'rivista-child' ),
        'url'   => home_url( '/about/' ),
        'style' => 'outline',
    );

    // Or replace the whole strip:
    // $chips = array(
    //     array( 'label' => 'Complimentary gift wrapping', 'style' => 'butter' ),
    //     array( 'label' => 'Ships in 24 hours',          'style' => 'ink' ),
    // );

    return $chips;
} );

The homepage hero tags

The hero carousel shows up to four looks, taken from the first products in your catalogue (menu order, then newest) that have a featured image. It prints one tag per look in the bottom bar and highlights the tag belonging to the look on screen, so no two tags may read the same. Each label is therefore the look’s first product category — ignoring the store’s default category — if no earlier look has used it; otherwise the product name shortened to the part before the em dash; and if that still collides, the full product name. Nothing to configure: rename a category or a product and the tags follow.

Overriding the mini-cart meter

The meter already reads the smallest minimum order amount among your enabled WooCommerce free-shipping methods, and hides itself when the store has none — so most shops never touch this. Use the filter when you want a different figure from the one in your shipping zone.

<?php
// The number is in store currency, with no symbol. Return 0 to hide the meter.
add_filter( 'rivista_free_shipping_threshold', function () {
    return 120;
} );

Rewriting the store guarantees

<?php
add_filter( 'rivista_trust_badges', function () {
    return array(
        array(
            'icon'  => 'truck',
            'title' => __( 'Free UK delivery', 'rivista-child' ),
            'sub'   => __( 'On orders over 75', 'rivista-child' ),
            'url'   => home_url( '/shipping-returns/' ),
        ),
        array(
            'icon'  => 'refresh',
            'title' => __( '30-day returns', 'rivista-child' ),
            'sub'   => __( 'No questions asked', 'rivista-child' ),
        ),
    );
}, 20 );

Section shortcodes

Four ready-made bands can be dropped into any page or post, and are used by several demo layouts. Both the tags and the sections’ render code live in the bundled RIVISTA Core plugin (section 10), so the content keeps rendering even if you later switch themes — under a foreign theme the plugin adds a small base stylesheet, while RIVISTA styles the sections in full. The theme’s front page draws its values and newsletter bands through the same plugin functions, so keep the plugin active; without it those two bands are simply omitted. They are shortcodes, not blocks — there is nothing to find in the block inserter under a RIVISTA heading. Add them with the editor’s Shortcode block, or simply type them into the content. Add tone="dark" to any of them on a dark page.

Other things worth knowing

• AJAX actions (front end, logged in or out, all nonce-checked): rivista_quick_view, rivista_wishlist_items, rivista_compare_items, rivista_compare_bar, rivista_set_cart_qty.
• Pluggable functions a child theme can redefine: rivista_setup(), rivista_posted_on(), rivista_posted_by(), rivista_entry_footer(), rivista_post_thumbnail().
• Theme mods behind the Customizer panel, readable with get_theme_mod(): rivista_premium_pack, rivista_style_switcher, rivista_font_pack, rivista_header_style, rivista_layout_direction, rivista_announcement_text, rivista_newsletter_shortcode.
• Browser storage (all local to the visitor): rivista-wishlist, rivista-compare, rivista-compare-meta, rivista-pack, rivista-type, rivista-theme, rivista-newsletter-subscribed, plus two session keys for the preloader and the newsletter popup.
• Image sizes: the theme registers none of its own and uses WordPress and WooCommerce sizes, so WooCommerce’s image settings under Appearance → Customize → WooCommerce → Product Images control the catalogue crop.
• Editor extras: a “RIVISTA Frame” block style for the Image block and an “Editorial Introduction” block pattern.

No child theme is bundled, because a good one is six lines long and belongs to your project. Create it before you change any PHP or CSS — edits to the parent theme are lost on the next update.

1. Create the folder wp-content/themes/rivista-child/.

2. Add style.css with the header below.

3. Add functions.php with the enqueue block below.

4. Add an empty custom.css for your own rules.

5. Activate RIVISTA Child under Appearance → Themes.

rivista-child/style.css

/*
Theme Name: RIVISTA Child
Template: rivista
Version: 1.0.0
Text Domain: rivista-child
*/

rivista-child/functions.php

<?php
add_action( 'wp_enqueue_scripts', function () {

    // The parent's style.css is enqueued as get_stylesheet_uri(), which points at
    // the CHILD once a child theme is active, so load the parent sheet explicitly.
    wp_enqueue_style(
        'rivista-parent-style',
        get_template_directory_uri() . '/style.css',
        array(),
        wp_get_theme( 'rivista' )->get( 'Version' )
    );
    wp_style_add_data( 'rivista-parent-style', 'rtl', 'replace' );

    // Put your own rules in a separate file that depends on the LAST theme sheet,
    // otherwise the theme's own stylesheets win the cascade.
    wp_enqueue_style(
        'rivista-child-custom',
        get_stylesheet_directory_uri() . '/custom.css',
        array( 'rivista-custom-cards' ),
        '1.0.0'
    );
}, 20 );

What a child theme can and cannot override

• Templates and the woocommerce/ overrides can be copied into the child and edited normally — keep the same file names.
• The child’s own style.css loads automatically, but before the theme’s main stylesheets, so rules there lose at equal specificity. Use the extra custom.css above.
• Demo media and the Customizer control assets are child-overridable; the shared CSS and JavaScript always load from the parent.
• rivista_setup() and the four template tags are pluggable, so a child can replace them wholesale.

Every user-facing string in the theme’s PHP is translatable, and every stylesheet ships a mirrored right-to-left twin.

Translating the theme

With Loco Translate (in the dashboard)

1. Install Loco Translate and open Loco Translate → Themes → RIVISTA.

2. Press New language, pick your locale, and choose the location “Custom” (languages/themes/) rather than the theme folder.

3. Translate the strings and press Save. Loco compiles the .mo file for you.

4. Repeat for the RIVISTA Core plugin if you use the Elementor widgets.

With Poedit (on your computer)

1. Open languages/rivista.pot in Poedit and choose Create new translation.

2. Select the language and translate.

3. Save as rivista-<locale>.po; Poedit writes the matching .mo beside it.

4. Upload both files to wp-content/languages/themes/.

Right-to-left layouts

Set the site language to an RTL locale under Settings → General, and WordPress swaps in the mirrored stylesheet for every theme sheet automatically — the main styles, the shared styles, the commerce styles and all 72 per-page stylesheets each ship an -rtl.css twin. On top of that the theme keeps prices, SKUs, counters and the wordmark reading left to right, and flips directional arrows.

Because direction is applied on the public site only, you can keep the dashboard in one language and run the storefront in another. If you edit the parent theme’s stylesheets directly, regenerate the mirrors with npm install once and then npm run build:rtl; hand-written RTL corrections belong in assets/css/_rtl.css. Working in a child theme, you do not need to regenerate anything.

The theme makes no outbound requests. What your visitors load comes from your own server, which is good for speed and simple for privacy law.

Data the front end stores

Wishlist, compare list, style-switcher choices and the “newsletter pop-up already seen” flag are kept in the visitor’s own browser storage. Nothing is sent to your server or to anyone else, and clearing site data removes it all. WooCommerce’s own cookies and any plugins you add are of course governed by their own policies — describe them in your privacy page.

Getting the most out of it

• Replace demo photographs with your own, exported at the size they are displayed, and serve WebP where you can.
• Set WooCommerce’s catalogue image size once and regenerate thumbnails after you change it.
• Add a page-cache plugin and enable your host’s object cache; nothing in the theme fights caching.
• Keep the announcement text short — it is the first thing painted.

1. Back up the database and the wp-content folder, or take a snapshot with your host.

2. Download the latest package from the marketplace and unzip it to get the new rivista-theme.zip.

3. Go to Appearance → Themes → Add New → Upload Theme, choose the file and confirm Replace current with uploaded. Alternatively replace the rivista folder over FTP.

4. If you use the Elementor widgets, update RIVISTA Core from Appearance → Install Plugins, which serves the version bundled with the new theme.

5. Clear any page cache or CDN cache, then reload the site and check the homepage, a product and the checkout.

Your content, menus, widgets and Customizer settings are untouched by an update. There is no need to re-run the demo import, and you should not: it rebuilds menus and reassigns pages.

The full, per-file credits list ships with the theme in THIRD-PARTY-CREDITS.md. This is the summary.

The canonical list lives in readme.txt inside the theme.

1.4.0

• The four editorial section shortcodes moved into the bundled RIVISTA Core plugin (updated to 1.3.0) — tags, render functions and a minimal base stylesheet — so shortcode content survives a theme switch. The theme keeps the sections’ full design in its CSS, and the front page’s values and newsletter bands are omitted cleanly when the plugin is inactive.
• Honest store copy by default. The homepage chip strip is now built from the store’s own settings — a free-shipping chip only when WooCommerce actually has a free-shipping method, carrying its real minimum in the store currency, and policy chips only for pages that exist. The mini-cart meter reads the same threshold from WooCommerce instead of assuming one, and the trust badges, values marquee, newsletter band, product-page guarantees and demo template scripts lost their hard-coded amounts, currency symbols and policy promises. The whole strip is filterable through rivista_home_chips.
• The demo importer writes the announcement ticker in the store’s own currency at import time, so the shipped copy matches the shop it lands in.
• Nothing freezes on one season. The homepage kicker and the mega-menu feature heading are seasonless and filterable (rivista_home_season_label, rivista_mega_feature_heading), dates print live, each hero look carries its own tag, and the Magazine index takes its lede from the blog page excerpt or the site tagline instead of a fictional editor.
• The theme’s own script no longer declares jQuery as a dependency, so a site without WooCommerce loads no jQuery for the theme at all. Every theme script is vanilla JavaScript; the only jQuery touch points are guarded calls that fire WooCommerce’s cart-fragment event on stores where WooCommerce has already loaded it.
• Right-to-left support throughout: every stylesheet ships a generated mirrored twin, and prices, SKUs and counters stay left-to-right.
• WooCommerce templates now fire the standard hooks. The product page uses the core gallery (zoom, lightbox, thumbnails), tabs, reviews and upsells; variable products get a styled attribute picker.
• Added the “Outfit of the day” editorial front page, built from real products with bundled local imagery.
• Restored the front-end style switcher, branded preloader, scroll-progress bar and back-to-top button, rewritten without any animation library. The style switcher is off by default.
• Restored the header mega menu with a local featured image.
• Added the Typography font-pairing control, using system-safe fonts.
• Added automatic SVG icons for social menu links, inline SVG header icons, and a search form matching the header overlay.
• Fixed the preloader stacking below the sticky header, and the dark demo losing contrast under a light colour pack.

1.3.3

• Version synced across the theme header, functions, readme and release package.
• Direct-access guards added to include and template files; the theme screenshot re-saved as a valid PNG; front-end layout-direction handling hardened.

1.3.0

• Language-aware layout-direction control and per-locale body classes.
• Better WooCommerce cart fragments and mini-cart handling.
• Template-specific asset loading with file-based cache busting.

1.2.0

• Added the RIVISTA Complete Demo one-click import, with portable local demo media, page layouts, products, posts, forms and menus.
• Duplicate WooCommerce pages prevented and imported form references repaired.
• Product cards switched to real WooCommerce data only.

1.1.0

• WordPress core feature support and marketplace-compliance fixes.
• Elementor widgets moved into the companion plugin.
• Accessibility, translation readiness and demo-data handling improved.

1.0.0

• Initial release.

Support for RIVISTA is provided through the support channel of the marketplace item you purchased it from. Open a ticket there and it reaches us.

Before you write, two minutes of preparation usually saves a whole round trip:

• Read the section of this manual that covers the area — the import, Customizer and FAQ sections answer most questions.
• Check Tools → Site Health → Info and note your WordPress, PHP and WooCommerce versions, plus the theme version (1.4.0 for this manual).
• Deactivate other plugins one at a time to find out whether the problem is a conflict; say what you found.

What to include in a ticket

• The page URL where the problem appears, and a screenshot or short screen recording.
• WordPress, PHP, WooCommerce and theme versions; whether a child theme is active.
• The exact steps that reproduce it, and what you expected instead.
• Any error text, including anything in the browser console or your host’s PHP error log.