Packages and themes (.vndext)
Structure of a package file (.vndext) with blocks and theme files, params.json, site-wide blocks, import rules, theme CSS and a complete mini theme as an example.
Overview#
A package is a ZIP file with the extension .vndext. It contains one or more blocks (components) and, optionally, the shared files of a theme (CSS, images, fonts). The import only checks the content: a .zip file with params.json works exactly like a .vndext file.
- Single block:
componentshas exactly one entry. The block is imported directly. - Theme package:
componentshas more than one entry. The import shows a selection with the preview images of all blocks; the blocks you choose go into the project's library or directly onto the page.
Ways to bring a package into the program:
| Way | Place in the program | Result |
|---|---|---|
| Choose or drag in a file | Add block › tab “File (.vndext)” | Default: only added to the library; with the switch “Insert directly into project” it goes straight onto the page |
| Themes folder | Add block › tab “Themes” | All .vndext/.zip files of the chosen folder appear as a catalog, plus the bundled starter themes |
| Online gallery | Add block › tab “VN Block Gallery” | The package is loaded unchanged and goes through the same import |
| Extension | ctx.blocks.importPackage, ctx.blocks.importToLibrary | see Extensions |
ZIP structure#
This is how the package vn-kinetic-theme.vndext (16 blocks) is structured; files that have no meaning for the import are marked.
params.json Pflicht: Name, Alias, Liste der Bausteine
thumbnail.jpg Vorschau für die Online-Galerie (nur dort gelesen)
CREDITS.txt, cover.png, splash.html ohne Bedeutung für den Import
plugins/plugin.json ohne Bedeutung für den Import
plugins/theme/css/style.css Theme-CSS (wird einmal pro Projekt geladen)
components/
_images/hero1.jpg … Bilder, auf die Bausteine verweisen
menu1/
template.html Pflicht: Markup + <vn-parameters>
style.less optional: Stil des Bausteins (LESS oder CSS)
thumb.png optional: Vorschau in der Auswahl
hero1/ … footer1/params.json#
This file describes the package. The program reads only the fields below; other fields (version, minAppVersion, description, plugins, logo, ampCompatible, _isSecondary) are ignored.
Syntax
{
"name": "Mini Theme",
"title": "Mini Theme",
"alias": "mini-theme",
"components": [
{ "path": "components/menu1", "_group": "Menü", "_title": "Menü (einfach)" }
]
}Fields
| Field | Type | Default | Meaning |
|---|---|---|---|
name | text | alias | Display name of the package. For a single block it is the name of the block; for a theme package it precedes the name of each block (“Mini Theme – Footer”) and is the name of the themes group in the library |
alias | text | block-<time> | Identifier of the package. The alias and CSS class of each block are derived from it, see Identifiers |
title | text | alias | Determines the identifier of the theme CSS (vn-theme-css-<title>), see Theme CSS |
components | list | – | Required. Each entry is an object with path (folder in the ZIP, required). If components is missing or the list is empty, the import rejects the package |
components[].path | text | – | Folder of the block, e.g. components/menu1. It must contain template.html and optionally style.less (or style.css) and thumb.png |
components[]._title | text | folder name | Display name of the block in the selection, library and catalog (“Hero mit Hintergrundbild”) |
components[]._group | text | – | Group in the theme selection (“Menü”, “Header”, “Footer”); without _title, a name such as “Header 7” is built from _group and the number in the folder name |
components[]._once | text | – | Display only: if you set a value here, the selection and catalog add the suffix “· site-wide”. The actual behavior is controlled by the once attribute in the block, see Site-wide blocks |
theme | object | – | Optional: settings (list of theme variables) and customLESS (path to a LESS file in the package), see Theme properties |
appScript | value | – | A package with appScript and without components is rejected. With components, these are imported as usual and the script remains unused |
template.html#
The markup of the block. The first element is the root of the block (usually section). It contains a <vn-parameters> block with the input fields of the Properties panel, followed by the actual markup with {{placeholders}} and directives such as vn-if, vn-class, vn-style. Everything about these is in the chapter Input fields; here only the behavior during import:
- All references of the form
…/_images/<file>(also../_images/…or a longer path in front) are translated into real project files, see Images and file names. - The
<vn-parameters>block is removed when rendering and is never exported. - Your own
<script>blocks stay in the markup. They run on the finished page. In the editor, the program runs them by default as well (site setting “Run block scripts in the editor”, on), but with stand-ins for timers,loadevents andlocation; each new render pass stops the timers of the previous one. Write scripts so that they useel.closest('#canvas')to detect whether they are running in the editor, and do not move or hide anything there.
style.less or style.css#
The style of the block. The program looks for style.less first, then style.css. It recompiles it each time a property value changes; every parameter name is available in it as a LESS variable (@paddingTop, @bg-type, @bg-value …). The style applies only to this block instance: the program prepends the instance class.
thumb.png#
The preview image of the block for the selection and the library. The program reads only this name (thumb.png, PNG). From 30 KB on, it is scaled down to at most 480 px width and stored in the project as WebP. If the file is missing, the selection shows a placeholder icon.
components/_images#
Shared image folder of the package. References in template.html, style.less and in the theme CSS read ../_images/<file>. Files with the extensions jpg, jpeg, png, gif, svg and webp are allowed.
plugins/ and fonts/#
All .css files under plugins/ as well as fonts/style.css belong to the theme CSS, see Theme CSS. The program copies JavaScript files under plugins/ into the project only if the package is a Bootstrap 4 theme (Bootstrap mode).
No script file per block#
For each block, the import reads only template.html, style.less/style.css and thumb.png. A separate script file next to the block (script.js) is not read. JavaScript belongs in template.html as a <script>; do not use fixed IDs or flags stored as JavaScript properties on the element, because the same block can appear several times on a page.
thumbnail.jpg and the gallery preview#
As the preview of the package, the online gallery takes the first matching file in the order thumbnail, thumb, preview, screenshot, card, block, cover (extension .jpg/.jpeg/.png, at most 2 MB; files with “splash” in the name do not count). The comparison uses the file name without the folder: thumbnail.jpg wins against the thumb.png of the blocks. The program itself never reads thumbnail.jpg.
Identifiers: alias, label, group#
From the entries in params.json, the import derives these names (example alias: mini-theme, block components/hero1, block ID bmw3s2mqdbf95):
| Name | Single block | Theme package | Example |
|---|---|---|---|
| Alias of the block | alias | <alias>-<folder name> | mini-theme-hero1 |
| Label (display name) | name | <name> – <_title> | “Mini Theme – Hero mit Hintergrundbild” |
| Root class | vn-imp-<alias> | vn-imp-<alias>-<folder name> | vn-imp-mini-theme-hero1 |
| Instance class in the finished HTML | <root class>-<block ID> | same | vn-imp-mini-theme-hero1-bmw3s2mqdbf95 |
| Anchor ID of the root | blk-<block ID> (or the anchor ID set by the user) | same | blk-bmw3s2mqdbf95 |
The root class is built from the alias (only a-z0-9; everything else becomes -). Each block instance gets its own instance class; therefore two identical blocks on one page do not interfere with each other. {{vn-id}} in the markup stands for the anchor ID of the instance.
The group (_group) serves as a category in the theme selection, in the themes catalog and in the gallery search. A block that is already in the library no longer knows _group (it is not stored with the block); its category there is its name without the trailing number (“Hero 3” → “Hero”).
Site-wide blocks: global and once#
Menu and footer belong on every page. A block becomes site-wide (“global”) if its root element carries the attribute global.
Syntax
<section class="mini mini-menu" global once="menu"> … </section>
<section class="mini mini-footer" global once="footers"> … </section>Attributes
| Attribute | Value | Meaning |
|---|---|---|
global | – | Makes the block site-wide: it does not sit in a page but in the list of global blocks and appears on every exported page |
once | text, e.g. menu, footers | Name of the group. Each group has at most one block in the project: a newly inserted one replaces the old one (message “previous global block replaced”). Without once, the group is called global |
The group name determines the position in the export: if it contains menu, nav or header (case-insensitive), the block is placed before the page content; all other groups come after it. In the example above, the menu is therefore at the top and the footer at the bottom. Their CSS ends up in style.css only once.
The import step by step#
For each block, importVndextComponent() in src/vndext-import.js performs these steps in exactly this order:
- Read
template.htmlandstyle.less(orstyle.css). - Rewrite Bootstrap 4 attributes to Bootstrap 5.
- Remove known demo traces of foreign package sources (see below).
- Remove a leading language marker in the style (“css:”).
- Rewrite old directive names to
vn-. - Translate
../_images/…into project files (template and style). - Load the theme CSS if the package contains one (once per theme).
- Take over theme variables (
params.theme.settings) assiteVars. - Read and scale down the preview image.
- Build the alias name and root class; detect a site-wide block (
global/once). - Copy image defaults with a
file:///path into the project if the file exists on this computer. - Build fields and default values from
<vn-parameters>. - Mark image fields, running text, buttons, icons and free images so that they become clickable in the editor.
The result is an entry with templateHtml, lessText, fields, defaults, wrapperClass, siteVars, thumb, isGlobal, globalGroup and a render function. It is saved with the project; when the project is opened, the program only rebuilds the render function and runs the marking steps again (they are repeatable; existing identifiers are kept).
Cleaning up old packages#
Packages from older sources bring peculiarities that the import cleans up itself. New packages should avoid them from the start.
| Finding in the package | Handling |
|---|---|
data-toggle, data-target, data-dismiss, data-ride, data-slide, data-slide-to, data-parent | The Bootstrap 5 attribute data-bs-… is additionally set with the same value (an existing data-bs-… is kept) |
| Demo links and names of the originating program (social links, short URLs, alt texts, running text) | Links become #, alt texts become empty, names in the text are replaced by a made-up name |
| “Is running in the builder?” check in the script | Simplified to the plain iframe check |
mbr-parameters, mbr-if, mbr-class, mbr-style, mbr-buttons, mbr-menu, mbr-video, mbr-icon, mbr-article | Renamed to vn-… (mbr-icon becomes data-vn-icon) |
mbr-theme-style="display-N" in themes with displayNSize variables | Becomes vn-theme-style, so that the class matches the theme CSS and not the larger display classes of Bootstrap |
value="file:///…" in image fields | See Images and file names |
<mbr-parameters> in template and style | Renamed to <vn-parameters> |
Images and file names#
- Target: Images from
_imagesend up as real files in the project'sassets/images/, fonts inassets/fonts/, theme CSS inassets/theme/. An entry in the template becomes afile://address of this file. - Names are preserved. If the name is free, a file with the original name is created. If a file with the same content already exists (under any name), it is reused. If the name is taken by different content, the program appends
-2,-3… There is no prompt, not even for many files of a theme. - Size: at most 15 MB per file; empty files are rejected.
- Foreign paths: An image default with
value="file:///C:/…"points to the author's computer. The program accepts it only if it points into the project folder; otherwise it tries to copy the file from this computer into the project (image formats only) and otherwise leaves the field empty. In packages, therefore always use../_images/….
Bootstrap attributes and Bootstrap mode#
The program ships Bootstrap 5.0.1 (vendor/bootstrap.min.css, vendor/bootstrap.bundle.min.js) and the Bootstrap Icons. Packages for Bootstrap 5 need nothing more. A package with its own plugins/bootstrap/css/bootstrap.min.css whose header line names “Bootstrap v4.x.x” counts as a Bootstrap 4 theme: on the first import, the program copies the theme's scripts (plugins/*/*.js, without .map and without *.full.js) to assets/theme-js/ and records the entry under siteSettings.themeAssets. The user can then switch the project to “Bootstrap from the theme”. In the export, each page then loads jQuery (vendor/jquery.min.js), Popper, the theme's Bootstrap JS, the smooth-scroll script, the scripts of the plugins that its blocks request, and finally the theme script. Which plugins a block needs is written by the attribute plugins="DropDown, TouchSwipe" on the root element.
If a plugin folder is missing in the package, the program does not load it. Packages for Bootstrap 5 carry data-bs-version="5.1" on the root element; the program reports if such a block ends up in a Bootstrap 4 project.
Theme CSS#
The theme CSS is the shared CSS of a theme package (base typography, buttons, helper classes). It is not in the individual blocks but is loaded once per project.
Which files are loaded#
When the first block of a package is imported, the program looks for these files in the ZIP and merges them in this order into one file:
plugins/bootstrap/css/bootstrap.min.cssplugins/theme/css/style.cssfonts/style.css- all other
plugins/**/*.css, alphabetically (exceptbootstrap-grid*andbootstrap-reboot*) - the LESS file translated from
params.theme.customLESS(if given)
A theme CSS is created only if at least one of these sources exists. A single block without these files (the usual case) does not trigger a theme CSS. A package with its own Bootstrap thus brings the Bootstrap CSS along; packages for the bundled Bootstrap 5 deliver only their own rules in plugins/theme/css/style.css.
In the editor: layer and scope#
In the editor, the theme CSS sits in a <style id="vn-theme-css-<name>"> in the document head:
@layer theme-base {
@scope (#canvas) {
/* Theme-CSS */
}
}The layer order is app-ui, bootstrap-base, theme-base, vn-blocks; later layers win. The CSS of the blocks sits in vn-blocks and therefore beats the theme CSS for ordinary declarations even with lower specificity. With !important this is reversed: there the earlier layer wins, i.e. the theme CSS beats an !important declaration in the block (in the export, specificity and order decide instead, see Precedence). @scope (#canvas) limits the theme to the canvas so that it does not change the program's interface. Write theme CSS normally, without @scope and without @layer.
In the export#
The pages load a single file style.css. Its structure: first the theme CSS unscoped (there is no #canvas in the export), then the CSS of all blocks, then the font rules, the program's fixed helper rules (menu, mobile menu, links) and finally the user's Custom CSS. In the export, theme CSS and block CSS are in the same level; with equal specificity, whatever comes later wins.
Only once per project#
The identifier of the theme CSS is vn-theme-css- plus title (or alias as a fallback), all in lowercase and every character other than a-z and 0-9 as - (“Mini Theme” → vn-theme-css-mini-theme). If a style with this identifier already exists in the project, the program loads nothing again:
- Two different packages with the same
titleshare one theme CSS: the one loaded first wins. - An update of a package does not replace the theme CSS of an existing project (in the test: new rules in the package's CSS, imported again, the project still shows the old CSS). The new block arrives, the old theme CSS stays. A refresh is not provided; in a new project, the new theme CSS applies. For updates, therefore expect that blocks must run with the old theme CSS.
Fonts and images in the theme CSS#
In every CSS file of the package, url(…) references are resolved relative to the file's location in the ZIP. Files with the extensions woff2, woff, ttf, otf, eot go to assets/fonts/, images (jpg, jpeg, png, gif, svg, webp) go to assets/images/; the references in the CSS become file:// addresses (in the export, assets/…). data:, http: and // addresses remain unchanged.
Theme properties (params.theme)#
A theme can define its variables in one place so that all blocks use them in LESS. This is done in params.theme.settings:
Syntax
{
"theme": {
"settings": [
{ "var": "primaryColor", "type": "color", "default": "#0f766e", "title": "Hauptfarbe" },
{ "set": [
{ "var": "successColor", "default": "#28a745" },
{ "var": "dangerColor", "default": "#dc3545" }
] }
],
"customLESS": "plugins/theme/css/custom.less"
}
}Fields
| Field | Meaning |
|---|---|
settings[].var | Name of the variable; it is available in every style.less of the package as @primaryColor. Entries without var (headings) are skipped |
settings[].default | Start value |
settings[].type | color, range, checkbox (also switch → boolean), otherwise text. If type is missing, the program infers it from the value: boolean → checkbox, number → range, #hex → color, otherwise text |
settings[].set | List of entries of the same kind without a group field of their own (e.g. color variants) |
customLESS | Path to a LESS file in the ZIP; it is compiled with the variables and its CSS is appended to the theme CSS |
Without these entries, every style.less that uses a theme variable fails (variable @primaryColor is undefined). For individually imported blocks, the program keeps a neutral set of known names ready (primaryColor, secondaryColor, successColor, infoColor, warningColor, dangerColor, mainFont, display1Font/display1Size … display7Size, isRoundedButtons and others); the real values of the package take precedence. The variables are saved with the block (siteVars).
Storage and self-healing#
The finished theme CSS is stored as the file assets/theme/vn-theme-css-<name>.css in the project; the reference is in siteSettings.themeCssFiles (identifier → path). When a project is opened, the program loads these files into the editor again and includes them in the export.
If, on opening, it finds files in assets/theme/ that no reference points to (remnants of older imports without a following save), it only notes them as “rediscovered”. These remnants are neither applied in the editor nor exported nor saved; otherwise the button colors of several long-unused themes would collide. A theme becomes active again only when it is imported again.
Themes folder and catalog#
A themes folder is any folder with .vndext or .zip files. From each file, the program reads only params.json and the thumb.png of the blocks (cached by file name, size and modification time); the actual import runs only when a block is chosen.
- The starter theme “VN Studio” (
assets/starter-themes/) is bundled. If a fileName.vndexthas a twin fileName.en.vndext, the program shows the English one in a non-German interface. - Packages with errors (not a ZIP, no
params.json, no blocks) are missing from the catalog; the status line gives the number of skipped files (“not a valid package”). - From the gallery, the button “To themes folder” saves a package as
.vndextunder its gallery name into the folder. File names are shortened to letters, digits and.-_ ()(at most 80 characters).
Package Tool#
The extension VN Package Tool (vn-paketwerkzeug) processes many packages at once. It only reads the files, does not change the program, and shows for each package: block, theme package, tool or defective. Findings (each “Note” or “Error”):
- Image defaults or
url(file:///…)that point to the author's computer - Bootstrap 4 traits (
data-toggle,ml-/mr-,text-left…) - jQuery in the script (runs only in the Bootstrap mode “from the theme”)
- PHP in the block (the page must be named
.php) - own script blocks and references to external addresses (need the internet on the visitor's side)
- plugin files (used only in the Bootstrap mode “from the theme”)
- missing preview image
thumb.png
Actions: write cleaned .vndext files into a folder (the originals stay untouched; local image paths, url(file:///…) and foreign markers are removed) or put all selected packages into the open project's library in one go (theme packages with all blocks; an identical alias replaces the previous entry; requires the program field ctx.blocks.importToLibrary). See also Extensions.
Example: a minimal theme package#
The package consists of a menu, a hero and a footer, a shared CSS and an image. It was imported and exported in the program; in the export, the menu and footer were at the top and bottom respectively, the image became assets/images/foto.jpg and the theme CSS came before the block CSS.
Files
mini-theme.vndext
params.json
thumbnail.jpg
plugins/theme/css/style.css
components/_images/foto.jpg
components/menu1/{template.html, style.less, thumb.png}
components/hero1/{template.html, style.less, thumb.png}
components/footer1/{template.html, style.less, thumb.png}params.json
{
"name": "Mini Theme",
"title": "Mini Theme",
"alias": "mini-theme",
"components": [
{ "path": "components/menu1", "_group": "Menü", "_title": "Menü (einfach)" },
{ "path": "components/hero1", "_group": "Header", "_title": "Hero mit Hintergrundbild" },
{ "path": "components/footer1", "_group": "Footer", "_title": "Footer" }
]
}plugins/theme/css/style.css
.mini { font-family: "Segoe UI", Arial, sans-serif; color: #1f2937; }
.mini h1, .mini h2 { margin: 0 0 .5em; line-height: 1.15; }
.mini .btn-mini { display: inline-block; padding: .6rem 1.4rem; border-radius: 999px; background: #0f766e; color: #fff; text-decoration: none; }components/menu1/template.html (site-wide, group menu)
<section class="mini mini-menu" global once="menu">
<vn-parameters>
<header>Farben</header>
<input type="color" title="Hintergrund" name="barBg" value="#ffffff">
<input type="checkbox" title="Beim Scrollen oben festhalten" name="sticky" checked>
</vn-parameters>
<nav class="navbar navbar-expand-lg" vn-class="{'navbar-fixed-top': sticky}">
<div class="container">
<a class="navbar-brand" href="index.html">Mein Betrieb</a>
<ul class="navbar-nav ms-auto flex-row gap-3">
<li class="nav-item"><a class="nav-link" href="index.html">Start</a></li>
<li class="nav-item"><a class="nav-link" href="kontakt.html">Kontakt</a></li>
</ul>
</div>
</nav>
</section>components/menu1/style.less
.navbar {
background: @barBg;
box-shadow: 0 1px 0 rgba(0, 0, 0, 0.08);
}components/hero1/template.html (background widget, image field with a default from the package)
<section class="mini mini-hero">
<vn-parameters>
<header>Größe</header>
<input type="range" inline title="Abstand oben" name="paddingTop" min="2" max="16" step="1" value="8">
<input type="range" inline title="Abstand unten" name="paddingBottom" min="2" max="16" step="1" value="8">
<header>Anzeigen</header>
<input type="checkbox" title="Bild neben dem Text" name="showImage" checked>
<select title="Ausrichtung" name="align">
<option value="left" selected>Links</option>
<option value="center">Zentriert</option>
</select>
<header>Farben</header>
<fieldset type="background" name="bg">
<input type="image" title="Bild" value="">
<input type="color" title="Farbe" value="#e6f4f1" selected>
</fieldset>
<input type="color" title="Textfarbe" name="textColor" value="#1f2937">
<input type="image" title="Foto" name="photo" value="../_images/foto.jpg">
</vn-parameters>
<div class="container">
<div class="row align-items-center">
<div class="col-lg-7">
<h1>Willkommen in unserem Betrieb</h1>
<p>Hier steht ein kurzer Text. Klicken Sie hinein, um ihn zu ändern.</p>
<a class="btn-mini" href="kontakt.html">Kontakt aufnehmen</a>
</div>
<div class="col-lg-5" vn-if="showImage">
<img src="{{photo}}" alt="" class="img-fluid">
</div>
</div>
</div>
</section>components/hero1/style.less
padding-top: (@paddingTop * 1rem);
padding-bottom: (@paddingBottom * 1rem);
color: @textColor;
text-align: ~"@{align}";
& when (@bg-type = 'color') { background-color: @bg-value; }
& when (@bg-type = 'image') { background-image: url(@bg-value); background-size: cover; background-position: center; }components/footer1/template.html (site-wide, group footers)
<section class="mini mini-footer" global once="footers">
<vn-parameters>
<header>Farben</header>
<input type="color" title="Hintergrund" name="bg" value="#134e4a">
</vn-parameters>
<div class="container py-4">
<p class="mb-0">© Mein Betrieb · <a href="impressum.html">Impressum</a></p>
</div>
</section>components/footer1/style.less
background: @bg;
color: #ffffff;
a { color: #ffffff; }Building the package (Python, standard library only plus Pillow for the images)
import io, json, zipfile
from PIL import Image
def bild(w, h, farbe, fmt):
b = io.BytesIO(); Image.new('RGB', (w, h), farbe).save(b, fmt); return b.getvalue()
komponenten = [('menu1', 'Menü', 'Menü (einfach)'),
('hero1', 'Header', 'Hero mit Hintergrundbild'),
('footer1', 'Footer', 'Footer')]
params = {'name': 'Mini Theme', 'title': 'Mini Theme', 'alias': 'mini-theme',
'components': [{'path': 'components/' + n, '_group': g, '_title': t} for n, g, t in komponenten]}
with zipfile.ZipFile('mini-theme.vndext', 'w', zipfile.ZIP_DEFLATED) as z:
z.writestr('params.json', json.dumps(params, ensure_ascii=False, indent=2))
z.write('src/plugins/theme/css/style.css', 'plugins/theme/css/style.css')
z.writestr('components/_images/foto.jpg', bild(800, 600, (15, 118, 110), 'JPEG'))
for n, g, t in komponenten:
z.write('src/components/%s/template.html' % n, 'components/%s/template.html' % n)
z.write('src/components/%s/style.less' % n, 'components/%s/style.less' % n)
z.writestr('components/%s/thumb.png' % n, bild(320, 180, (15, 118, 110), 'PNG'))
z.writestr('thumbnail.jpg', bild(640, 360, (15, 118, 110), 'JPEG'))Result in the export (shortened): menu first, hero, footer last; each instance with its own class; theme CSS before the block CSS.
<section class="mini mini-menu vn-imp-mini-theme-menu1-bmw3s2mqu4wym" global="" once="menu" id="blk-bmw3s2mqu4wym">…</section>
<section class="mini mini-hero vn-imp-mini-theme-hero1-bmw3s2mqdbf95" id="blk-bmw3s2mqdbf95">
… <img src="assets/images/foto.jpg" alt="" class="img-fluid"> …
</section>
<section class="mini mini-footer vn-imp-mini-theme-footer1-bmw3s2mqy6gzj" global="" once="footers" id="blk-bmw3s2mqy6gzj">…</section>/* style.css (Anfang) */
/* plugins/theme/css/style.css */
.mini { font-family: "Segoe UI", Arial, sans-serif; color: #1f2937; }
…
.vn-imp-mini-theme-hero1-bmw3s2mqdbf95 { padding-top: 8rem; padding-bottom: 8rem; color: #1f2937; text-align: left; background-color: #e6f4f1; }Checklist before passing it on#
- Import the package into a new project (library) and insert every block. Look at the Properties groups: each
headerline appears as a group. - Export and open the page in the browser; check the menu and footer.
- No
file:///paths, no fixed IDs, no references to foreign servers (fonts, scripts, images). - One
thumb.pngper block (width about 480 px) and athumbnail.jpgin the package if it is meant for the online gallery. - Images and fonts as files in the package; no videos.
- Describe the sample texts without real names and addresses (
example.com).