Contact

Write to us about the theme.

Questions before buying, licence questions, defects found mid-build, and work that needs more than a field. Say which one it is and the first reply answers it. Written replies on working days; there is no phone line.

  • mail

    hello@studionope.com

  • schedule

    Written replies only. There is no phone line and we would rather say so than list one nobody answers.

  • schedule

    Written replies, on working days. Say if a date is attached and we will tell you what is possible.

Send us a message

Writing the message

What makes the first reply useful.

Most exchanges take three messages because the first one was missing one of these. Any of them is enough to skip a round.

link

The URL

The page you are looking at, even if it is a preview link or a private page. A description of a layout is guesswork; a URL is not.

hub

Which portal

Your own, a client one, or a sandbox. It decides the licence answer and it decides whether a fix can be tested where the problem is.

widgets

The module or template

The name shown in the page editor is enough. It turns a search of the whole theme into opening one file.

compare_arrows

What you expected instead

Two sentences: what happened, and what should have. Half of what gets reported as a defect is a setting, and this is the line that tells the two apart.

devices

Where you saw it

Browser and roughly how wide the window was. Layout reports that cannot be reproduced are usually a breakpoint nobody thought to check.

schedule

Whether a date is attached

A launch on Friday changes what a useful answer looks like. Say so, and we will tell you what is possible before it becomes a problem.

Somewhere else

Six of these are answered faster elsewhere.

The form reaches the people who write the theme. These do not need to.

menu_book

How something works

Every setting, module and template, shown rendered rather than described.

history

What an update changed

Each release says what it does to files you edited, and what counts as breaking.

help

A question before buying

What it needs, what a licence covers, and an honest list of what it does not do.

handshake

You build for clients

Who the licence is issued to, what you can charge for, and what happens at handover.

newspaper

You are writing about it

Logos, screenshots and boilerplate, cleared for use. Take what you need without asking.

work

You want to work on it

Open roles and what applying involves. Send work rather than a covering letter.

The questions page, a long accordion of answers
Answers

The questions page

The changelog page, with dated release entries
Releases

The changelog

A filterable grid of downloadable reference documents
Downloads

The reference sheets

Module demo

This is the Store Locator, running.

Example pins, not our offices. Search by name, filter by type, or let it find the nearest one. Street mode draws without any API key, so it works the moment the theme is installed.

  • Flagship

    Placeholder location. Replace with your own.

    Categories drive the filter chips above the list.

  • Branch

    Placeholder location. Replace with your own.

    A note field renders under the address when it is filled in.

  • Branch

    Placeholder location. Replace with your own.

  • Partner

    Placeholder location. Replace with your own.

    Pins cluster automatically as you zoom out.

What happens next

Send it half-finished.

You do not need a scope, a brief or a decision to write. Most useful exchanges start from a problem described badly and get sharper in the second message.

One inbox, read by the people who built it no ticket number, no queue

  • visibility Somebody opens the URL you sent before replying to it
  • mail The reply comes from a person, at their own address
  • block When the answer is no, the reply says no
  • task_alt A defect you report goes on the register and into the changelog

Say which portal you are on and what you are trying to build. That is usually enough for the first reply to be an answer.