view_quilt
Every template and module
Page templates, blog listing and post, the system pages, and the modules this page is built from. Nothing is held back for the paid version, because there is no separate paid version.
Tell us which portal you would evaluate it in and what you would build with it. A licence covers one portal, so a test portal and a live portal are two separate things -- worth knowing before you plan the evaluation.
Name the portal you would use and what you want to build. We will come back with how an evaluation would run.
An evaluation that hides half the modules answers the wrong question. What is described below is the whole theme, not a cut-down version of it.
Page templates, blog listing and post, the system pages, and the modules this page is built from. Nothing is held back for the paid version, because there is no separate paid version.
HubL you can read, partials you can reuse and field groups named the same way in every module. Open it in the design manager and judge it before you own it.
Written for the person who inherits a site rather than the person who built it. It is open at nopethemes.com/docs, so you can read it before asking for anything.
Anything looks good on a fresh install. The question worth answering is what happens on the day the brand changes and you are not the one changing it.
Pick one of the five presets, then change the accent colour and the two font fields. Anything you set beats the preset; anything you leave alone keeps it.
Not the homepage. The pricing table, the case study or the careers list, whichever page is the reason the last theme was a fight.
Primary, secondary, accent, background, foreground, border and muted, plus the error, success, info and warning states.
Change the accent and reload a page with a dark section on it. The heading stays readable because text, muted text, borders and card surfaces each have a value for a light ground and a value for a dark one. That pair is what usually forces per-page overrides, and it is the fastest way to tell a token set from a colour picker.
A heading font and a body font, then every element on its own: body text, h1 through h6, paragraphs, links, lists, blockquotes and code.
Set a mobile size on h1 and look at a page at phone width. Responsive type is a field here rather than a media query somebody has to write, which is also why a size you change stays changed after the next theme update.
The icon library is a setting: Material, Lucide, Phosphor, Font Awesome, Tabler, Remix, Bootstrap, Heroicons, HugeIcons or HubSpot. Switch it and every icon on the site switches with it.
Turn transitions and scroll animation off with the single switch, then read a page. Everything should still be legible and in the right order, because reveal animations move things that are already there rather than supplying them.
A licence covers one HubSpot portal. The portal you test in and the portal that serves your domain are two portals, and the second one needs its own licence before it serves the theme to the public.
Existing pages keep the template they were built on. Seeing this theme on your content means rebuilding a page with it, which is what we would suggest doing during the trial anyway.
We install it and answer questions. If you want the pages rebuilt for you, that is a scoped piece of work and a different conversation.
Change any file you like during the trial. Keep the list, because an edited theme file is the one an update overwrites, and a module you write from scratch against the tokens is yours rather than ours.
If what you need is one landing page and no site, or a shape this theme does not have, we will tell you instead of installing something you will not use.
One that is not serving your domain. A sandbox or a test account is the usual answer, and it keeps the evaluation away from anything a customer can see.
No. A theme sitting in a portal changes nothing until a page is built on it and published, and the trial portal is not the portal your domain points at.
They stay in that portal. Pages are content and they do not travel between portals, so treat trial pages as something you are learning on rather than the first pages of the real site.
Not to install it, pick a preset, set the colours and fonts or build a page. You need one when you want a module that does not exist yet.
Better to use your own. When the client site goes ahead, the licence is issued in their portal so it is already in the right place at handover. The details are on the partners page.
One HubSpot portal, and the work you do with the theme in it. It never covers reselling the theme source. Full terms are at nopethemes.com/license.
The page worth testing is the one that was a fight last time -- the pricing table, the case study, the careers list. Then hand it to whoever will be editing the site.
The whole theme in a portal that is not serving anybody
A licence covers one HubSpot portal. The portal you test in and the portal that serves your domain are two portals.