Features

Features turn optional parts of JORD on or off for this website. For example, enabling Events adds tools for entering a programme. It does not create any events for you.

Admin path: Website > Settings, section Features
Route: /instance

An ordinary text correction does not need a feature change. If you cannot find the content screen you need, ask the website administrator to check this page and your access.

How the Settings screen is organised

Settings shows Features first and Plugins below it, on one page. The Advanced settings button at the top opens Advanced settings. The features are grouped like this:

On sites with the webshop enabled, an E-commerce section with tax, shipping, and payment settings appears between Features and Plugins. See E-commerce settings.

Change a feature safely

1. Open Website > Settings and find Features.
2. Find the card with the feature’s name. Read its explanation below before changing it.
3. Turn on the card’s Turn on switch. Any fields the feature needs appear inside the card.
4. Complete those fields.
5. Select Save at the bottom of the screen.
6. Open the related content screen.
7. Create or check the content, then test the public page that uses it.

Contact form

Use Contact form when visitors should send a general enquiry from the website. This is different from the custom forms you build under Content > Forms.

After turning it on, complete these fields:

Enquiries are sent from the Sender email set in Advanced settings, so both addresses need to be filled in.

Save the settings. Then enable the form in Content > Contact, or in the Contact section where it should appear.

Send a test message from the public website. Confirm it reaches the recipient, including checking their spam folder. The public contact email and the form recipient serve different purposes. Changing one does not mean you changed the other.

Local newsletter

Local newsletter stores newsletter sign-ups in JORD and adds Subscribers under Website in the admin.

Use it when your website’s newsletter setup stores subscriptions in JORD. Ask the person responsible for newsletters which list the website should use before enabling it.

If the Mailchimp plugin is also on, sign-ups go to Mailchimp instead of Subscribers.

After saving, open Subscribers and test the public sign-up. Confirm the test address appears in the list. Turning this on does not write a newsletter or send a campaign.

Forms

Forms adds Content > Forms and allows Form sections on pages. Use it for a form with your own questions, such as an enquiry with a choice of service.

After enabling and saving:

1. Open Content > Forms.
2. Create the form and add its questions.
3. Complete notification and privacy settings.
4. Save and publish the form.
5. Add a Form section to the page that should display it and select the form.
6. Test a public submission and check the downloaded results.

The switch enables the tools. A published form still needs a place on the website where visitors can reach it.

JORD newsletter

JORD newsletter adds Newsletters, where you write newsletters in JORD and send them. It is separate from the Local newsletter sign-up list, although its automatic sending uses that list.

The Newsletters menu appears only for Super admins and accounts with the newsletter-manager role. See Newsletter access.

Use it only when your organisation intends to prepare and send newsletters through JORD. Ask the newsletter administrator to confirm the sender address and recipient list before sending.

After saving, check the Newsletters menu with an authorised account. Do not send a live newsletter to test whether the feature works. Send a test to your own address first, as described in Newsletters.

If the organisation sends through Mailchimp instead, see the Mailchimp plugin. JORD newsletters are not sent to a Mailchimp audience.

Events

Events adds both Events and Event series to the Content menu. An event is one occurrence; a series groups related events, such as a festival programme.

Enable it, save, then create an event. Use Event series only when several events need a shared group.

Check how visitors will find the events, such as through a list page or a collection section. Enabling the feature does not add a menu link to that listing for you.

Services

Services adds the screen for reusable descriptions of what the organisation offers.

After saving, create a service, complete its image and descriptions, and choose whether it needs its own detail page or a link elsewhere. Save and publish it.

To display selected services on another page, use a Manual collection. Check that each service card opens the intended destination.

References

References adds Content > References for past projects, clients, or case studies. It is different from the Reference block, which can link to several kinds of content.

After saving, create a reference. Add approved project details and images. Give it its own page only if it needs a separate case-study page.

Publish it and check the page or collection where it should appear. The switch does not create reference records or approve customer names and logos for public use.

Customer feedback

Customer feedback makes testimonial sections available in supported page editors.

After saving, open the relevant page and add a Customer feedback section. Enter the approved comments and customer details, then arrange them.

This displays feedback entered by an editor. It does not automatically collect reviews from another service or create a public review-submission form.

Authors

Authors adds Authors and author fields and filters on articles. Use it when an article needs a named writer.

Enable and save the feature, create or check the author record, then select it in the article. Check the author shown on the published article.

An author credit is not an admin login. To give someone permission to edit the website, use Users. A team member used for an event or staff list is also a separate kind of record.

Publisher Role

Publisher Role means only accounts with the Publisher role can publish articles. It is useful when one person writes an article and someone else approves publication.

Before enabling it, identify who will publish and ask the administrator to check their user roles. Turning it on also shows the Editor permissions box on each user’s screen. Otherwise, an editor may finish an article but be unable to publish it.

After saving, have an authorised publisher confirm they can publish an approved article. Editors can prepare and save content within their permissions. Do not assume this switch creates the same approval process for every content type.

Multipage

Multipage adds the Page break block to articles. Use it only when a long article should be split across separate public pages.

Enable it, save, and open the article. Insert Page break between complete parts, not at the very beginning or end. Check every part and the navigation between them after publication.

A heading starts a new topic on the same page. A page break makes readers navigate to another page. Choose a heading when that is all you need.

A feature or menu is still missing

First confirm the settings saved. Then check the correct website and your account’s permissions. Some tools require both an enabled feature and an authorised role.

Not every capability mentioned elsewhere has a switch on this screen. For example, article autosave depends on the website configuration. If you cannot find such a switch, ask the administrator rather than changing a similarly named setting.