Skip to main contentSkip to footer
    Back to Case Studies
    CubriksProduction audiovisuelle, Paris
    WordPressMaintenanceParis

    Cubriks

    A Paris audiovisual production agency on the Champs-Élysées, with a Divi one-page site built around a video hero. We took the site into version control, documented every layer, hardened what needed hardening, and gave the team a blog pipeline that publishes without touching the builder.

    Project Preview

    Live website preview - cubriks.com

    14
    Pages mapped and documented, from homepage to cookie policy
    18
    Client logos in the Références grid
    11
    Active plugins inventoried with their purpose and admin location
    2
    Restore paths written and tested: .wpress import and manual

    One-page French site, video-first

    A looping MP4 hero, animated logo reveal, service cards, a 2x2 project category grid, team grid with hover swap, client references and a news section, all in Divi.

    GDPR consent that actually blocks

    Complianz configured for EU opt-in: functional cookies only until consent, statistics and marketing gated, Google Maps blocked until the marketing category is accepted, Do Not Track honoured.

    Security hardening

    All In One WP Security for brute-force and firewall rules, HSTS and HTTP security headers via a dedicated plugin, and a REST namespace whitelist so the blog pipeline is not blocked by the firewall.

    Three-layer caching

    WP-Optimize page cache with gzip and minification, Divi dynamic CSS with inlined critical styles and async late CSS, Imagify compression with WebP, and conservative speculative loading.

    Yoast SEO and schema

    Site-wide title format, French meta descriptions, WebSite, WebPage, BreadcrumbList and ImageObject JSON-LD, Open Graph and Twitter cards, and split post and page sitemaps.

    Automated blog publishing

    A REST-authenticated publishing plugin lets articles land on /blog-cubriks/ with their Yoast meta description already set, so the agency's blog grows without a Divi session.

    The situation

    Cubriks is an audiovisual production agency at 66 avenue des Champs-Élysées in Paris. Corporate films, interviews, advertising, luxury and fashion shoots, motion design. Its client references include Chanel, L'Oréal Paris, Dassault Systèmes, AXA, SNCF, Société Générale, Accor, Samsung and TF1. The tagline is "Vous briefez, on shoot !".

    The website was originally designed by another studio on WordPress and Divi. It is a good-looking one-page site: a full-width video hero, three logo variants animating on scroll, parallax project categories, a team grid whose black-and-white portraits swap to green on hover, and a dark references section with eighteen client logos folding in. What it did not have was any of the things that keep a site like this alive for years: version control, a documented restore path, a plugin inventory, a written record of how consent and security were configured, or a way to publish blog content without opening the page builder.

    What Frenchy Digital was asked to do

    • Own the site technically: Capture everything, understand everything, and be able to rebuild it on a new server without the original designers.
    • Keep it compliant and safe: An EU agency with a Google Tag Manager container and embedded maps needs consent that blocks by default and security headers that are actually set.
    • Make content cheap to add: Team members, client logos, hero videos and blog posts should each be a documented, repeatable task.

    What we built

    A repository that can rebuild the site

    The whole wp-content tree, the Divi parent and child themes, every plugin, the French language files and a full database export went into a private repository. The 1.3 GB media library, roughly 25,000 files, is excluded from git and restored from the All-in-One WP Migration archive instead. Two restore methods are documented step by step: import the .wpress archive on a fresh install, or copy wp-content, import the SQL, rewrite the site URL and fix permissions by hand. A fifteen-point checklist closes each restore, from the cookie banner appearing to the custom cursor working on desktop.

    Four documents instead of tribal knowledge

    Architecture

    The Divi section, row, column and module hierarchy, the six column layouts in use, the caching strategy across WP-Optimize and Divi dynamic CSS, the security measures, and the responsive breakpoints.

    Pages

    A page-by-page content map: title, meta description, template, and every section on the homepage with its animation and its link target.

    Deployment

    Prerequisites, PHP extensions, licences, both restore methods, environment-specific wp-config settings and the post-deployment checklist.

    Plugins

    Eleven active plugins with their purpose and where each one lives in the admin, plus the security and REST API notes an operator needs before touching them.

    Consent, security and speed

    Complianz runs in EU opt-in mode with four cookie categories, a 365-day consent expiry, Do Not Track support and Google Maps blocked until marketing consent is given. Security is layered: All In One WP Security for brute-force protection and firewall rules, a dedicated headers plugin for HSTS and the other HTTP security headers, right-click and text selection disabled site-wide at the client's request, and wp-config and .env kept out of the repository. Performance comes from WP-Optimize page caching with gzip and minification, Divi's inlined critical CSS with late CSS loaded asynchronously, Imagify compression with WebP, responsive srcset at three breakpoints, and speculative prefetch hints set to conservative eagerness.

    Blog publishing without the builder

    The agency wanted a blog that grows without someone opening Divi for every article. We integrated a REST-authenticated publishing plugin: articles are pushed to a namespaced endpoint with an API key sent in a request header, land on /blog-cubriks/, and arrive with their Yoast meta description already set. The key lives in WordPress options, is rotated by regenerating it, and never enters the repository. Because the security plugin can block unauthenticated REST calls, the namespace whitelist step is documented alongside.

    How the site is maintained

    Content edits go through the Divi Builder in WP Admin, followed by a WP-Optimize cache clear
    Code edits go through the child theme in the repository, then rsync or FTP to the server, then Divi and WP-Optimize cache clears
    The Divi parent theme is never edited, so theme updates cannot overwrite custom work
    Adding a team member, a client logo, a hero video or a project page is a written procedure
    Cache is cleared in a fixed order: Divi dynamic CSS, WP-Optimize, browser, then CDN if present
    Yoast per-page titles, descriptions and social images are edited in the metabox below the builder

    Where it stands

    What we can and cannot claim

    The site is live at cubriks.com in French. The original design is credited to another studio; Frenchy Digital's scope is the repository, documentation, deployment, consent, security and caching configuration, and the blog publishing integration described above. We have no analytics access for this client, so this page carries no traffic, ranking or lead figures. The page count, logo count and plugin count are taken from the project documentation and the repository.

    Vous briefez, on shoot !

    — Cubriks, homepage tagline

    What This Project Does Well

    The entire site, theme, child theme, plugins and a 54 MB database export live in a private repository with a git-ignored .wpress backup, so the site can be rebuilt from scratch
    Two restore procedures documented end to end, with prerequisites, PHP extensions, permissions, URL replacement and a 15-point post-deployment checklist
    A single rule for all code changes: nothing in the Divi parent theme, everything in the child theme, which keeps Divi updates safe
    Cache-clearing order documented so an edit is never reported as 'not working' because a stale layer served it
    Consent, security headers and content-protection settings written down rather than living only in one admin's head
    Blog publishing decoupled from the page builder, with the API key stored in WordPress options and never in the repository

    Technologies Used

    WordPress 7.0, Divi 4.27.6 with a Divi Child theme, Divi Builder, Yoast SEO 27.6, Complianz GDPR 7.4.6, WP-Optimize, All In One WP Security, Headers Security Advanced & HSTS, Imagify, WPForms Lite, Smart Slider 3, Redirection, Better Search Replace, All-in-One WP Migration, RankPill Integration, Google Tag Manager, PHP 8.2, MySQL/MariaDB, Open Sans, custom cursor and scroll-motion JavaScript

    Ready to Build Something Similar?

    Let's discuss how we can help transform your business with a custom digital solution.

    Visit cubriks.com📅 Schedule Consultation