Skip to main content

Themes

A theme is how an organization's website looks. As a partner you create it, publish its versions and decide who can use it.

Development happens locally: see Creating and developing a theme. Here you manage creation, cover image and distribution.

Creating a theme​

From Themes > Add theme enter:

  • the name shown to organizations;
  • the identifier, which goes into the theme's manifest.json.
The identifier is permanent

Riseact uses it to recognise the theme's versions. It cannot be changed: a different identifier is a different theme, and those who installed the first one would stop receiving updates.

This step is optional: the first riseact theme release creates the theme with the identifier in the manifest. Creating it here reserves the identifier.

Publishing a version​

From the CLI:

riseact theme release

From the panel, with Actions > Upload theme as ZIP: you upload the archive, prepared with riseact theme package, and describe the changes.

The version is read from manifest.json and must be higher than the previous one. If a file is not valid the release is refused, with the list of every problem found.

Organizations read the description of the changes before deciding whether to update.

Who can see the theme​

On the theme page, the Visibility box offers two choices:

  • Not shared: you can only install it on the organizations you are developing with.
  • My organizations: the organizations you administer find it under Website > Theme store and can install it, with no approval. It is the most direct way to deliver a bespoke theme.

Installing a theme does not publish it: it lands in the organization's library, and the organization decides when to switch to it.

Publishing to the store​

On the theme store the theme is visible to every Riseact organization, subject to approval. At least one published version is required.

  1. Upload the cover image from the theme page: it appears on the store card, ideally a wide screenshot of the homepage.
  2. Press Submit for Approval. You can attach a message: the most useful thing is an address where the theme can be seen in action. The reply comes by email.

Updates and customizations​

When you publish a new version, the organizations that have the theme decide whether to update. The update replaces the theme's code but not their choices: colours, texts and page composition stay.

What gets replaced and what is kept is explained in the theme development guide.