diff --git a/content/support/accounts-and-roles/account-management.md b/content/support/accounts-and-roles/account-management.md
index d79acbb4..005036e8 100644
--- a/content/support/accounts-and-roles/account-management.md
+++ b/content/support/accounts-and-roles/account-management.md
@@ -2,61 +2,72 @@ title: Managing user accounts
# Managing user accounts
-The **Users and Roles** section of the manager has various controls for
-different permission levels.
+The **Users and roles** section of the Manager dashboard has various controls for managing users and permissions. Who can manage what will depend on their role and permissions associated with it.
-Editors have control of:
+**Editors** and **Journal managers** can:
-- User accounts at the journal level.
-- Account roles in the journal.
-- Account activation.
+- Manage user accounts at the journal level.
+- Assign and remove roles for users on the journal.
+- View and update account activation status.
-Staff have additional controls for:
+**Staff** have additional controls for:
-- Viewing all accounts for the Janeway installation, including their journal roles and activation status.
-- Merging user accounts.
- Both of these are only available at the press level.
+- Viewing all accounts for the press (Janeway installation), including their journal roles and activation status.
+- Merging duplicate user accounts.
+
+These additional controls are only available at the press level.
## Journal users
-If you are an editor or staff member, you can manage user accounts for a
-journal via the **Journal Users** page.
+If you are an editor, journal manager or staff member, you can manage user accounts for a journal via the **Journal users** page.
-
+
-You can search by various fields, including name, email, ORCID,
-institution, and biography. You can filter by role and whether an account
-is active.
+From this page you can:
-You can also add and remove roles, edit accounts, and, if needed create
-accounts.
+- Search by name, email address, ORCID, institution, or biography.
+- Filter users by role and account activation status.
+- Add or remove journal roles.
+- Edit user account details.
+- Create new user accounts where required.
-Each user's assignment history is also available from this view.
+Each user's assignment history (for example, editorial or review activity) is also available from this view.
-## All users
+This page cannot be used to delete accounts, only deactivate them. Accounts can only be deleting using through the **Admin area** .
-If you are staff, you can see all users across a press (a.k.a. Janeway
-installation) - this view is only available from the Press Manager interface.
+## All press users
-
+Staff users can access a press-wide view of all accounts across press / the Janeway installation. This view is available from the **Press manager** interface only.
-At this level, you can filter by journal and staff-member status and
-manage roles across journals, in addition to the actions an editor can
-take.
+
-## Editing user accounts
+At press level you can:
-When clicking **Edit** next to a user, you will be taken to the Edit User interface, where you make changes to a user's details. There are a few things to note regarding permissions, see the Permissions page for more information .
+- Filter users by journal role and staff status.
+- Manage roles across multiple journals.
+- Perform all actions available to editors at journal level.
+
+## Editing user accounts
-TBC
+Click **Edit** next to a user to open the **Edit user** interface, where you can update a user’s account details.
-- information about how editing an account won't affect metadata on articles that have already been accepted: to do that you'll need to edit the frozen author record on the article metadata page.
+Some changes are restricted by permission level. For more information, see the **Permissions** page.
-## Merge users (Press manager only)
+> [!IMPORTANT]
+> Editing a user account does **not** change author metadata on articles that have already been accepted.
+> To update author details on an accepted article, you must edit the _frozen author record_ on the article’s metadata page.
-The press manager interface enables staff members to merge two accounts to eliminate duplicates. All associated objects, such as tasks, articles, roles, and files, will be moved from the source account to the destination account. The account profile remains unchanged, meaning any profile information in the source account will be lost.
+## Merge users (staff only)
-
+When users have multiple accounts (often due to different email addresses having been used), it may be helpful to merge accounts. Users with staff permission can merge two user accounts to remove duplicates, using the **Press manager interface**. When searching for users to merge, note that the user account in the left column (source account) will be merged into the user account in the right column (destination account).
> [!WARNING]
-> When searching for users to merge, note that the user account in the left column will be merged into the user account in the right column.
+> An account merge **cannot** be undone. Only merge account when you are certain they can be merged.
+
+When accounts are merged:
+
+- All associated items (including articles, tasks, roles and files) are transferred from the source account to the destination account.
+- The destination account profile is retained.
+- Any profile information from the source account is permanently lost.
+
+
diff --git a/content/support/accounts-and-roles/accounts-and-roles-index-placeholder.md b/content/support/accounts-and-roles/accounts-and-roles-index-placeholder.md
index 106ac9b1..23982a24 100644
--- a/content/support/accounts-and-roles/accounts-and-roles-index-placeholder.md
+++ b/content/support/accounts-and-roles/accounts-and-roles-index-placeholder.md
@@ -1,3 +1,25 @@
-title: Accounts and Roles
+title: Accounts and roles
-# Accounts and Roles
+# Accounts and roles
+
+This section explains how user accounts and permissions work in Janeway, including how roles are assigned and managed. Read the following pages for more information:
+
+
+
+- Managing user accounts
+- Roles and permissions
+- Activating accounts
+- ORCID login
+- Single sign-on (SSO)
+
+## New accounts
+
+
+
+## Single sign-on (SSO) login
+
+Janeway supports single sign-on (SSO), allowing users to log in using their institutional credentials without creating a separate Janeway account.
+
+SSO must be configured by your system administrator. If you are interested in enabling SSO for your journal or press, contact your system administrator for further information.
+
+
diff --git a/content/support/accounts-and-roles/activating-accounts-placeholder.md b/content/support/accounts-and-roles/activating-accounts-placeholder.md
deleted file mode 100644
index 0b875ece..00000000
--- a/content/support/accounts-and-roles/activating-accounts-placeholder.md
+++ /dev/null
@@ -1,17 +0,0 @@
-title: Activating accounts
-
-# Activating accounts
-
-**WIP**
-This section will explain how to find out if an account has been activated and, if not, how to activate it.
-Inactive accounts are a common cause of login issues.
-
-## Inactive users
-
-The inactive users page is accessible to staff only and lists all users who have not yet activated their accounts. You are cautioned only to activate accounts for which you've confirmed ownership with the user.
-
-- Users who have not yet activated their account cannot log in to Janeway.
-
-## Authenticated users
-
-It presents a list of users who are currently logged into your Janeway installation. This page is only accessible to users with 'Staff' permission.
diff --git a/content/support/accounts-and-roles/activating-accounts.md b/content/support/accounts-and-roles/activating-accounts.md
new file mode 100644
index 00000000..5d68afdf
--- /dev/null
+++ b/content/support/accounts-and-roles/activating-accounts.md
@@ -0,0 +1,57 @@
+title: Activating accounts
+
+# Activating accounts
+
+This page explains how to check whether a user account has been activated and how to activate inactive accounts. As users must activate their account before they can log in to Janeway, inactive accounts are a common cause of login issues.
+
+## Inactive users
+
+There are two places from which to check and manage the activation status of accounts:
+
+- **Journal users**
+- **Inactive users**.
+
+Both are found under **Users & roles** on the Manager dashboard. The **Journal users** page is available to editors and journal managers, where as the **Inactive users** page is accessible to staff only.
+
+To view inactive users:
+
+1. Open **Journal users**.
+2. Use the filter on the left-hand side.
+3. Set **Status** to **Inactive**.
+4. Click **Apply**.
+
+This will list all inactive users on the journal. You can also search by name or email address.
+
+The **Inactive users** page lists all inactive users across the press who have not yet activated their accounts.
+
+## Activating accounts
+
+Once you have identified an inactive account through either **Journal users** or **Inactive users**:
+
+1. Click **Edit** next to the user to open the account page.
+2. Under **Is active**, select **Yes**.
+3. Save your changes.
+
+
+
+The user will now be able to login into the journal.
+
+
+
+## Authenticated users
+
+The **Authenticated users** page shows a list of users currently logged in to your Janeway installation.
+
+This page is only accessible to users with staff permission.
diff --git a/content/support/accounts-and-roles/janeway-roles-and-permissions.md b/content/support/accounts-and-roles/janeway-roles-and-permissions.md
index d8da6743..863dcea2 100644
--- a/content/support/accounts-and-roles/janeway-roles-and-permissions.md
+++ b/content/support/accounts-and-roles/janeway-roles-and-permissions.md
@@ -1,81 +1,98 @@
-title: Roles and Permissions on Janeway
+title: Roles and permissions on Janeway
-# Roles and Permissions on Janeway
+# Roles and permissions on Janeway
-**WIP**
-Needs some further work, checks and dev input on a few bits. Need to check out the granular permissions still.
+This page explains the different roles available in Janeway and how permissions are managed.
+
+
## Janeway roles
-- Author
- - When someone registers with the journal or submits an article, they are given this role.
+Janeway has a variety of roles available that can be assigned to users, some of which will affect the permissions of the user. Roles do not exclude each other, e.g. having one role will not prevent you another one.
+
+- Author
+ Assigned automatically when a user registers with a journal or submits an article. This can be considered the 'base role'.
- Reviewer
-- Editor
- - Handles processing of articles and assignment of tasks
-- Journal Manager
- - Has a similar level of permission to the editor role but can be given extra access (see below)
-- Section Editor
+- Editor
+ Editors handle processing of articles and assignment of tasks. An editor has access to the journal workflow, manager dashboard and journal settings, certain plugins and is able to do general journal management.
+ An editor does not have access to the admin area, press level settings and certain plugins.
+- Journal manager
+ Journal managers have a similar level of permission to the editor role, but can be given additional access (see below).
+- Section editor
+ Section editors have access only to the workflow elements of articles assigned to them. They cannot access any articles not assigned to them, journal settings or plugins. This role is well-suited for (guest) editors who only need to handle specific articles within the journal.
- Copyeditor
- Typesetter
- Proofreader
-- Reader
- - This is not a role as such, but it is used to indicate whether a user is signed up for article publication notifications. For more information, see Email notifications
+- Reader
+ This is not a role as such, but it is used to indicate whether a user is signed up for article publication notifications. For more information, see Email notifications
> [!NOTE]
-> Whilst the Production Manager and Proofing Manager are still assignable in Janeway, they have been deprecated in 1.4 and are no longer in use.
+> Whilst the Production manager and Proofing manager are still assignable in Janeway, they have been deprecated in 1.4 and are no longer in use.
## Permissions
-In addition to the roles and their respective permissions, separate permission levels can be assigned. Editors also have specific permissions associated with their roles.
+In addition to the roles and their respective permissions, separate permission levels can be assigned for certain settings for journal managers and editors. Editors also have specific permissions associated with their roles.
### Editor permission
-Editors have permissions that allow:
+Editors can:
-- Managing roles within their journal.
-- Viewing and editing the account activation status of journal users.
-- Editing basic account information on behalf of journal users.
-- Viewing a user's history (review/editorial/proofing etc. assignments).
+- Manage roles within their journal.
+- View and edit account activation status for journal users.
+- Edit basic account information on behalf of users.
+- View a user’s assignment history (editorial, review, proofing, etc.).
- The user history page also displays emails sent directly to the user - excluding 'automated' emails such as reminders, notifications and invitations.
### Staff permission
-The ‘Staff’ permission should only be given to Journal Managers/Publishers and can only be assigned by other users with the Admin and/or Superuser permission. Staff have additional controls for:
+Staff permission should only be assigned to press-level users (for example, publishers or system administrators). It can only be granted by another user with staff permission.
+
+Staff users can:
-- The same controls as editors, but for all the journals belonging to the press.
-- Merging duplicate user accounts (available at the press level).
+- Perform all editor-level actions across all journals in the press.
+- Merge duplicate user accounts at press level.
+- Use all installed plugins.
+- View additional manager pages (for example: inactive users, authenticated users).
+- View the **All articles** page.
+- Access the **Admin area**.
### Superusers permission
-- ‘Superuser’ will assign a user all roles across the system.
+‘Superuser’ will assign a user all roles across the system.
-### Admin permission
+## Granular manager permissions
-- ‘Admin’ grants access to Janeway's admin data layer.
+
-## Granular Manager Permissions
+Janeway allows more granular permissions for journal managers and editors, using the **Permissions** setting group. This can be used on the configuration of licences and sections as following:
-In version 1.5, we introduced more granular manager permissions. Initially, these roles were centred around journal manager and editor roles. We are introducing a new setting group, "Permission", and within this group, we will be adding new permission controllers starting with:
+- Licenses
+ Permissions control whether users can access the licenses control pages based on their roles, defaulting to Editor and Journal Manager.
-- Licenses
- - Controls whether users can access the licenses control pages based on their roles, defaulting to Editor and Journal Manager.
+- Sections
+ Permissions control whether a user can access the sections control pages based on their roles, defaulting to Editor and Journal Manager.
-- Sections
- - Controls whether a user can access the sections control pages based on their roles, defaults to Editor and Journal Manager.
+### Editing granular permissions (staff only - advanced)
-Currently, there is no interface for updating the roles that can access these pages and the setting is JSON stored in the database.
+> [!NOTE]
+> The following sections contain information on configuring granular permissions. This requires more advanced technical knowledge, though you are unlikely to need this (often).
+
+There is no interface for updating the roles that can access these pages and the setting is JSON stored in the database. If you are not comfortable or able editing this, contact your system administrator.
> [!WARNING]
-> You should only edit the Permission settings if you are sure about the change you are making.
+> Only modify granular permissions if you are confident in the change you are making.
By default, both settings read `["editor", "journal-manager"]`. If, for example, you wanted to stop editors from editing licenses, you could change it to read `["journal-manager"]`. Once saved, only users with the journal manager role will be able to access the licenses
pages.
-### Granular settings permissions
+### Granular settings permissions (staff only - advanced)
-In version 1.5, we introduced permissions for granular settings. Staff can now determine which roles can edit any given setting object. This is done via the Django Admin panel (Core \> Settings), using the `editable_by` field. Staff can alter the roles that are allowed to see and edit a setting.
+Users with staff permission can control which roles can view and edit individual settings via the **Admin area** (Core \> Settings), using the `editable_by` field.
-> [!NOTE]
-> If a setting is also displayed on a settings group page (for example, the General or Submission settings page) and a user does not have the appropriate permission to edit that setting, it will be filtered out of the form and not be visible.
+If a setting is displayed on a settings group page (for example, the **General** or **Submission settings** page) and a user does not have the appropriate permission to edit that setting, it will be hidden from the form.
+
+By default, setting permissions are only editable by editors and journal managers. When upgrading to a Janeway version with the granular permissions, no changes will be made to the default.
-As with the manager permissions changes, the default to settings permission maintains the status quo, and by default, all settings are editable by editors and journal managers.
+If you wish to make these changes and are not confident using the Admin interface, contact your system administrator.
diff --git a/content/support/accounts-and-roles/orcid-login-placeholder.md b/content/support/accounts-and-roles/orcid-login-placeholder.md
index 4a097644..63451363 100644
--- a/content/support/accounts-and-roles/orcid-login-placeholder.md
+++ b/content/support/accounts-and-roles/orcid-login-placeholder.md
@@ -2,35 +2,23 @@ title: ORCID login
# ORCID login
-**WIP**
+_Coming soon_
Janeway supports ORCID login.
- How to register
- How to login
-
+
+
+
+If you don't have ORCID, you will need one. missing hyperlink
Start with:
### Linking ORCID to an existing account
-
-## Technical information
-
-### Enable ORCID login
-
-To enable ORIC login, you need to add the following to your settings file:
-
- ENABLE_ORCID = True
- ORCID_CLIENT_SECRET = ''
- ORCID_CLIENT_ID = ''
-
-As the URLs for the ORCID API are fixed, setting them is unnecessary.
-
-### Callback URLs
-
-You will need to set the callback URLs in the ORCID interface. If using domain-mode you will need to add each domain, if using path-mode you can set just the main domain.
+-->
diff --git a/content/support/analytics/google-analytics-placeholder.md b/content/support/analytics/google-analytics-placeholder.md
index 99cfd939..a58822c9 100644
--- a/content/support/analytics/google-analytics-placeholder.md
+++ b/content/support/analytics/google-analytics-placeholder.md
@@ -2,17 +2,19 @@ title: Google analytics
# Google analytics
-**WIP**
+_Coming soon_
+
+
diff --git a/content/support/analytics/janeway-statistics-and-index-placeholder.md b/content/support/analytics/janeway-statistics-and-index-placeholder.md
index 9b13ee07..d2ebbb1b 100644
--- a/content/support/analytics/janeway-statistics-and-index-placeholder.md
+++ b/content/support/analytics/janeway-statistics-and-index-placeholder.md
@@ -2,21 +2,35 @@ title: Janeway analytics
# Janeway analytics
+_Coming soon_
+
+
diff --git a/content/support/reporting.md b/content/support/analytics/reporting.md
similarity index 100%
rename from content/support/reporting.md
rename to content/support/analytics/reporting.md
diff --git a/content/support/article-management/article-metadata-placeholder.md b/content/support/article-management/article-metadata-placeholder.md
index 225c4831..4916658f 100644
--- a/content/support/article-management/article-metadata-placeholder.md
+++ b/content/support/article-management/article-metadata-placeholder.md
@@ -2,6 +2,10 @@ title: Article metadata
# Article metadata
+
+
+
+
There are various ways to access an article's metadata depending on the status of an article. This page will provide an overview, for more general information on metadata, see: metadata on Janeway.
For unpublished articles, you can either scroll to the bottom-right corner with the decisions and select **View metadata** (granted an article is no longer in the unassigned stage), or you can:
@@ -49,3 +53,70 @@ Affiliation metadata in Janeway is managed using the [Research Organization Regi
Publisher notes appear on the article page below the abstract and how to cite block. These can be used to notify readers of small changes to the paper like a post-publication update to fix spelling etc. The publisher notes can be edited from the **Article archive** page.
+
+
+
+
+
+_Coming soon_
+
+
+
+Article metadata can be edited through either the **Archive** page or through **Edit metadata**. Both can be found under **Logs, documents and more** in the blue workflow bar.
+
+
+
+The first block of the **Article archive** page lists most of the article's metadata. To change it you can click **Edit** button.
+
+
+
+This will take you to the following page, where you can edit the article's metadata:
+
+
+
+Make sure you scroll down and click **Update metadata** to save any changes.
+
+
+
+On this page, after the block for the article metadata, you can also edit the author metadata and funder information.
+
+## Metadata fields
+
+_Coming soon_
+
+## Identifiers
+
+Janeway can mint CrossRef and DataCite DOIs and if working with data imported from other platforms can also maintain existing publisher IDs, such as an OJS ID.
+
+Identifiers associated with an article can be found through **Identifiers** under **Logs, documents and more**. Though DataCite DOIs will not show up here and need to be managed through the DataCite plugin.
+
+
+
+> [!TIP]
+> You can also manage CrossRef DOIs at the journal level as an editor (and at the press level as a staff user) using the DOI Manager.
+
+## Google Scholar
+
+Google Scholar indexing is automatic; they use a webcrawler that looks for relevant materials (articles, monographs, preprints, reports, etc). It takes some time for new journals to appear on Google Scholar and for changes to existing content to show. [Google Scholar advises](https://scholar.google.com/intl/en/scholar/inclusion.html#troubleshooting) it may take 6-9 months for changes to appear.
+
+If your journal is not properly indexed, contact support, we work with Google Scholar to make sure all journals are captured
+
+
+
+
diff --git a/content/support/article-management/articles-management-placeholder.md b/content/support/article-management/articles-management-placeholder.md
new file mode 100644
index 00000000..1bdc0daf
--- /dev/null
+++ b/content/support/article-management/articles-management-placeholder.md
@@ -0,0 +1,60 @@
+title: Articles
+
+# Articles
+
+_To be edited_
+
+Once an article is published, you may need to change it, e.g., upload a new galley or tweak the metadata if there is an error.
+
+All published articles can be found on the Articles page under Back Content. The Article back content page lists both published and rejected papers. You can search and then select an article to edit.
+
+> [!TIP]
+> You can also edit papers by going to their page and using the account drop-down to select **Edit article**.
+
+
+
+## Article Archive
+
+From this page you can:
+
+- Edit metadata
+- Edit publication information
+- Add/remove images
+- Create Publisher Notes
+- Manage identifiers
+- Manage galley files
+- Manage which issues an article appears in
+- If an article is rejected, unreject the article
+
+### Publisher Notes
+
+Publisher notes appear on the article page below the abstract and how to cite block. These can be used to notify readers of small changes to the paper like a post-publication update to fix spelling etc.
+
+
+
+### Issues
+
+You can see the issues that an article is part of at the bottom of the Article Archive page. You can edit each of the issues or jump to the issue manager.
+
+
+
+### Actions
+
+You can unreject a previously rejected article using this button. You will have the opportunity to write an email to the author before the change takes effect.
+
+If the article was previously assigned to an editor, the article will move to the Review stage. Otherwise, it will move to the Unassigned stage.
+
+### Article Display Settings
+
+The Article Display Settings page has settings for controlling the way articles look and for deciding how metrics are displayed.
+
+- Disable Article Images
+- Display Guest Editors
+- Suppress How to Cite
+- View PDF Option
+- Disable Metrics Display
+- Suppress Citation Metrics
+
+How To Cite is an auto-generated citation based on a custom OLH citation style. Note that a previous version of the citation included "p" before page ranges. To get this back, enter a custom value in Page Numbers in the Edit Metadata pane for each article.
+
+You can suppress How To Cite for all articles with Suppress How To Cite. You can also override it for individual articles by entering a custom citation in the Edit Metadata pane for each article.
diff --git a/content/support/article-management/publication-scheduling-placeholder.md b/content/support/article-management/publication-scheduling-placeholder.md
new file mode 100644
index 00000000..ce8c9c85
--- /dev/null
+++ b/content/support/article-management/publication-scheduling-placeholder.md
@@ -0,0 +1,10 @@
+title: Publication schedule
+
+# Publication schedule
+
+**WIP**
+Any articles that you publish with a publication date in the future will appear in a list on this page.
+
+
+
+
diff --git a/content/support/email-and-reminders/email-index-placeholder.md b/content/support/email-and-reminders/email-index-placeholder.md
index d8a8084d..b5259109 100644
--- a/content/support/email-and-reminders/email-index-placeholder.md
+++ b/content/support/email-and-reminders/email-index-placeholder.md
@@ -1,3 +1,43 @@
title: Emails and reminders on Janeway
# Emails and reminders on Janeway
+
+Janeway uses email to support many key editorial and publishing workflows; including reviewer invitations, decision notifications, revision requests, publication alerts, and automated reminders.
+
+This section explains:
+
+- How to check what emails were sent and when.
+- How to customise email content through templates and how to work with email template variables.
+- How to set up automated reminders.
+- How to set up publication notifications.
+
+
+
+## How email works in Janeway (at a glance)
+
+- Emails are sent automatically or manually as part of article workflows.
+- All outgoing emails related to an article are logged.
+- Depending on your email service, delivery status information is available through the email log as well.
+- Some emails (such as reminders and notifications) are sent automatically based on dates or events.
+- Email content can be customised per journal using templates.
+
+> [!NOTE]
+> Due to GDPR restrictions, Janeway does not offer any options for email campaigns.
+
+## Common questions
+
+- _“A reviewer says they didn’t get the email — what should I do?”_
+ Start with Email logs to confirm whether the email was sent and, if necessary, resend it.
+
+- _“I want to change the wording of reminder emails.”_
+ Edit the relevant template under Email templates. Use information in Email template variables to insert information safely.
+
+- _“Why didn’t a reminder email send?”_
+ Check Scheduling reminders and confirm that due dates were set correctly. If reminders still do not send, contact your system administrator.
+
+- _“Can readers (un)subscribe to/from publication notifications?”_
+ Yes. Readers manage their notification preferences via their profile page. See Publication notifications for more information.
+
+
+
+If something is unclear or you are unsure whether a change is safe to make, contact your system administrator.
diff --git a/content/support/email-and-reminders/email-logs-placeholder.md b/content/support/email-and-reminders/email-logs-placeholder.md
index 1617db23..90b9019f 100644
--- a/content/support/email-and-reminders/email-logs-placeholder.md
+++ b/content/support/email-and-reminders/email-logs-placeholder.md
@@ -2,18 +2,82 @@ title: Email logs
# Email logs
-All outgoing emails sent through Janeway are tracked in the article log.
+All outgoing emails sent through Janeway are tracked in the article log. This allows editors, journal managers and staff to confirm which emails have been sent, when they were sent, and (where supported) their delivery status.
-You can view an article's log by accessing an article either through its workflow stage or through the archive (Dashboard -\> Left hand menu
--\> Back Content -\> Articles) and using the Stages, Logs and More.
-drop down select Log
+Email logs are commonly used when:
-
+- A reviewer or author reports not receiving an email.
+- You need to confirm that a decision or notification was sent.
+- An email needs to be resent.
+
+## Accessing email logs
+
+You can view an article's logs through **Logs, docs and more**, which appears in the blue workflow progress at the top of the article screen.
+
+You can access this through:
+
+- The article's workflow stage, or
+- The archive (Dashboard -\> Left hand menu
+ -\> Back Content -\> Articles).
+
+
+
+## Understanding the log entries
+
+Each entry in the log records an action that has taken place on the article. The following information is shown:
+
+- Entry type
+ The type of action that was logged ("Review request accepted" or "Typesetting complete" for example).
+- Date
+- Actor
+ The user or system process that intiated the action.
+- Level
+
+
+If the logged action relates to an email, additional details are available:
+
+- Addressees
+ The recipient(s) of the email, including any CC or BCC addresses.
+- Subject
+- Email status
+ Information about the delivery status of the email. See **Interpreting statuses** below for more information.
+- There is an option to click through to see the email content.
+
+
## Interpreting statuses
-- what do the statuses mean?
+Emails sent through Janeway may display a delivery status, indicated with both text and coloured dots.
+
+> [!NOTE]
+> If your installation does not use Mailgun, but another email service (for example, Googlemail), the coloured dots will not display meaningful status information.
+
+Janeway can only track events that occur within the system and the configured email service. It cannot track what happens after an email leaves that service (for example, if an email is blocked by the recipient’s local mail server).
+
+If you suspect persistent email delivery issues, contact your system administrator.
+
+### Email status meanings
+
+The following statuses can appear:
+
+- No information
+ No delivery information is available from the email service.
+- Accepted
+ The email has been accepted by the email service for delivery.
+- Delivered
+ The email has been delivered to the recipient’s mail server.
+- Failed
+ The email could not be delivered.
+
+> [!NOTE]
+> Seeing "No information" under email status does not necessarily mean an email was not sent.
## Actions
-- what do the buttons do, explain.
+From this page there are also two things you can do:
+
+- Refresh the email status
+ This checks the latest delivery status for the email. This can be used to check the delivery status. This cannot detect issues on the recipient’s side (such as local spam filtering).
+
+- View email content
+ This displays the email message that was sent From this screen, you can also resend the email.
diff --git a/content/support/email-and-reminders/email-publication-notification-placeholder.md b/content/support/email-and-reminders/email-publication-notification-placeholder.md
index c9be6f6e..2d18824d 100644
--- a/content/support/email-and-reminders/email-publication-notification-placeholder.md
+++ b/content/support/email-and-reminders/email-publication-notification-placeholder.md
@@ -2,14 +2,49 @@ title: Publication notifications
# Publication notifications
-Janeway supports publication notifications via a new role called "reader". This feature can be toggled on or off for any given journal. Once the setting is toggled on, anyone with an account can sign up to receive emails when new articles are published via their profile page. This feature has been designed with continuous publication in mind but will also work well for those who publish full issues.
+Janeway supports publication notifications through the **Reader** role. This feature allows users to receive email notifications when new articles are published in a journal.
+
+Publication notifications can be enabled or disabled on a per-journal basis. When enabled, any user with a Janeway account can opt in to receive notifications via their profile page.
+
+This feature is designed primarily for continuous publication workflows, but also works for journals that publish complete issues.
-Journal staff can toggle the feature by visiting Manager \> Publication Notification (Readers) and using the link displayed on that page (see figure above).
+## Enabling publication notifications
+
+Journal staff can enable or disable publication notifications from the Manager dashboard (Manager \> Publication notification (readers)). On this page, use the toggle or link displayed on that page to enable or disable the feature for the journal.
-Readers can sign up for notifications by logging into a journal and selecting the Edit Profile link from the account menu (top right hand of any page).
+Once enabled, users will be able to subscribe to notifications from their profile.
+
+## Subscribing to notifications
+
+Users can sign up for publication notifications by:
+
+1. Logging in to the journal.
+2. Opening the account menu in the top-right corner of the screen.
+3. Selecting **Edit profile**.
+4. Enabling publication notifications (Reader role).
+
+
+
+The **Reader** role is not a workflow role and does not grant access to editorial or journal management features. It is used only to manage publication notification preferences.
+
+For more information about roles, see **Roles and permissions**.
+
+
+
+## How notification emails are sent
+
+Publication notifications are sent as a daily email digest:
+
+- All articles published on a given day are included in a single email.
+- If no articles are published on a particular day, no notification is sent.
+- Emails are sent using BCC, so recipients do not see other subscribers’ email addresses.
-Emails are sent in a digest format (all published articles are sent in one email) once per day. On days when no articles are published no notifications are sent. Emails are sent using BCC so only a single email is sent.
+
diff --git a/content/support/email-and-reminders/email-reminders.md b/content/support/email-and-reminders/email-reminders.md
index 3ad94036..39c27665 100644
--- a/content/support/email-and-reminders/email-reminders.md
+++ b/content/support/email-and-reminders/email-reminders.md
@@ -2,47 +2,76 @@ title: Scheduling reminders
# Scheduling reminders
-Janeway lets you define your own email reminders for overdue Reviews and Revision assignments. They are defined using the following:
+Janeway allows you to schedule automated email reminders for review\*\* and revision assignments. These reminders help prompt reviewers and authors when deadlines are approaching or have passed.
-- Type
- - Review (new), Review (accepted) or Revision reminder.
+Reminders are configured at the journal level and are sent automatically based on the due dates set by editors.
-- Run Type
- - Whether to run before or after the request is due.
+## Reminder types
-- Days
- - The number of days before or after the request is due this reminder should be sent.
+Janeway supports three types of reminder emails:
-- Template Name
- - The template name should be used when sending the reminder. If this template does not exist, you will be asked to create it.
+- **Review (invited)**
+ Sent when a reviewer has been invited but has not yet accepted the review request.
-- Subject
- - The email subject to send with the reminder.
+- **Review (accepted)**
+ Sent when a reviewer has accepted a review request but has not yet submitted their review.
-Janeway supports three types of reminder emails:
+- **Revision**
+ Sent to authors who have an active revision request.
+
+Review reminders are sent based on the **review assignment due date** set by the editor.
+Revision reminders are sent based on the **revision due date** set by the editor.
+
+For all reminder types, you can choose to send reminders **before or after** the due date.
+
+Multiple reminders can be created for the same task (for example, one before and one after the due date).
+
+## Configuring a reminder
+
+Each reminder is defined using the following settings:
+
+- Type
+ The reminder category: "Review (invited)", "Review (accepted)", or "Revision".
+
+- Run type
+ Whether the reminder should be sent before or after the assignment due date.
-- Review (Invited)
- - Sent when a reviewer has been invited but not accepted a review request.
-- Review (Accepted)
- - Sent when a reviewer has accepted a review request but not yet completed it.
-- Revision
- - Sent to authors with active revision requests.
+- Days
+ The number of days before or after the due date that the reminder should be sent.
-Review reminders, both invited and accepted, are sent based on the review assignment due date set by the editor. Revision reminders are sent based on the revision request due date set by the editor. You can set reminders to be sent either before or after the set due date.
+- Template name
+ The email template used for the reminder.
+ If the selected template does not exist, you will be prompted to create it.
-A reminder email has access to three objects in the template:
+
+
+- Subject
+ The subject line of the reminder email.
+
+## Reminder email templates
+
+Reminder emails use standard email templates and have access to specific objects, depending on the reminder type:
- Review_assignment or revision (depending on which type of reminder)
-- Journal
- - The journal sending the reminder.
-- Article
- - The appropriate article
-On the edit template page, there is a guide that shows some of the variables you can use when generating these templates.
+- Journal
+ The journal sending the reminder.
+
+- Article
+ The appropriate article.
+
+The **Edit template** page includes guidance and examples showing some of the variables available for use in reminder emails.
-Once a reminder is created, a Cron job on the server will start processing requests, but it will not process these for Review and Revision requests that have passed the reminder dates.
+## How reminders are sent
+
+Once a reminder has been created, it is processed automatically by a scheduled background task (sometimes called a 'cron job' ) on the server.
+
+This task checks for review and revision assignments that match the reminder criteria and sends emails when appropriate.
+
+> [!IMPORTANT]
+> Reminders will not be sent for review or revision requests where the reminder date has already passed at the time the task runs.
> [!TIP]
-> If automated reminders are not being sent for your journal the most likely explanation is that the cron job has not been setup properly. You should contact your administrator, who can set up the call to the send_reminders management command.
+> If automated reminders are not being sent, the most likely cause is that the scheduled background task (cron job) has not been set up correctly. You should contact your administrator, who can set up the call to the send_reminders management command.
diff --git a/content/support/email-and-reminders/email-template-variables.md b/content/support/email-and-reminders/email-template-variables.md
index cc666b26..6e4c7397 100644
--- a/content/support/email-and-reminders/email-template-variables.md
+++ b/content/support/email-and-reminders/email-template-variables.md
@@ -2,18 +2,68 @@ title: Email template variables
# Email template variables
-This section needs dev input. (Some stuff below looks like it needs backticks, but idk dawg)
-Also needs a little more info on how to put this into use. Probably part on this page, part on other pages.
+Email template variables allow Janeway to automatically insert information into emails, such as article titles, reviewer names or due dates.
-## Templates
+You do not need technical knowledge to use variables, but it is important to use them _exactly as shown_, unless you are confident about what they do. Changing or removing parts of a variable can cause emails to display incorrectly. If you are unsure, contact your system administrator or Janeway support.
-### Review Assignment
+This page explains:
-Template Code: review_assignment
+- What variables are.
+- Which variables are available in common templates.
+- How to use them safely.
-This template is sent to potential reviewers inviting them to submit a review.
+For general guidance on editing templates, see Email templates .
-Objects in this Template's context:
+## What are email template variables?
+
+Variables are placeholders that Janeway replace with real information when an email is sent.
+
+For example:
+
+- The reviewer’s name.
+- The article title.
+- A review deadline.
+- A link to a review task.
+
+Variables always appear inside double curly brackets, for example:
+
+`{% raw %}{{ review_assignment.date_due }}{% endraw %}`
+
+When the email is sent, Janeway replaces this with the actual due date.
+
+> [!IMPORTANT]
+> Variables must be copied exactly (if copying from reference). Do not add spaces, punctuation or text inside the brackets. You can safely change the surrounding text.
+
+## Example template: Review assignment
+
+Template code: review_assignment
+
+This email is sent to potential reviewers when they are invited to review an article.
+
+The following information can be inserted into the email using variables:
+
+- Article information (title, abstract, journal name).
+- Reviewer information.
+- Editor information.
+- Review details, such as the due date.
+- A secure review link.
+
+Commonly used variables include:
+
+- `{% raw %}{{ article.safe_title }}{% endraw %}`
+ The article title.
+- `{% raw %}{{ editor.first_name }}{% endraw %}`
+ The editor’s first name.
+- `{% raw %}{{ review_assignment.reviewer.full_name }}{% endraw %}`
+ The reviewer's full name.
+- `{% raw %}{{ review_assignment.date_due }}{% endraw %}`
+ The review due date.
+- `{% raw %}{{ review_url }}{% endraw %}`
+ The link the reviewer uses to access the review.
+
+### Review assignment objects (advanced users)
+
+If you are a technical user and/or familiar with objects, here is a list of objects in this template's context:
- article, an Article object.
- editor, an Account object.
@@ -21,7 +71,44 @@ Objects in this Template's context:
- review_url, a reversed URL with FQDN.
- article_details, a string with article and review information in it, inc. Title, due date etc.
-## Objects
+## Using variables in practice
+
+Here are some common examples you can copy and reuse.
+
+- Review due date
+ `{% raw %}{{ review_assignment.date_due }}{% endraw %}`
+
+- Article title
+ `{% raw %}{{ article.safe_title }}{% endraw %}`
+
+- Journal name
+ `{% raw %}{{ article.journal.name }}{% endraw %}`
+
+- Review link
+ `{% raw %}{{ review_url }}{% endraw %}`
+
+- Revisions link
+ `{% raw %}{{ do_revisions_url }}{% endraw %}`
+
+- The title of the issue this article is projected to be part of
+ `{% raw %}{{ article.projected_issue.display_title }}{% endraw %}`
+
+- The article's correspondence author
+ `{% raw %}{{ article.correspondence_author.full_name|se_can_see_pii:article }}{% endraw %}`
+
+If you use a variable with information that isn't available; e.g. a middlename for a user who has not provided one, it will be ignored and display a blank space instead.
+
+> [!NOTE]
+> Certain variables, such as the title, have `safe_` appended to the second half of the object. This is to ensure they display correctly.
+
+> [!NOTE]
+> In certain templates, the author name variable will include "`|se_can_see_pii:article`". This determines the visibility of the variable's information to section editors when using triple anonymous review. You do not need to edit this or otherwise worry about this when not using triple anonymous review.
+
+## Commonly used objects (advanced reference)
+
+The sections below describe the main objects you may encounter.
+
+### Objects
Listed here is a non-exhaustive list of the objects that you may have access to in an email template.
@@ -38,7 +125,7 @@ KEY
- DateTime is a field that stores a internationalised date and time.
- Email is a validated email address.
-### Account
+### Account object reference
The account object stores information about users.
@@ -63,7 +150,7 @@ The account object stores information about users.
- is_staff (Bool)
- date_joined (DateTime)
-### Article
+### Article object reference
The article object contains the following attributes:
@@ -83,7 +170,7 @@ The article object contains the following attributes:
- rights (Str)
- article_number (Int)
-### Journal
+### Journal object reference
The journal object contains the following attributes:
@@ -109,7 +196,7 @@ The journal object contains the following attributes:
- sequence (Int)
- disable_front_end (Bool)
-### ReviewAssignment
+### ReviewAssignment object reference
- article (FK `Object Article`)
- reviewer (FK `Object Account`)
@@ -128,18 +215,3 @@ The journal object contains the following attributes:
- comments_for_editor (Str)
- review_file (FK File)
- display_review_file (Bool)
-
-## Using Object Variables in Templates
-
-If I wanted to display the due date I could use:
-
-`{% raw %}{{ review_assignment.date_due }}{% endraw %}`
-
-If I wanted to display the title of the issue this article is projected
-to be in I can use:
-
-`{% raw %}{{ article.projected_issue.display_title }}{% endraw %}`
-
-If I wanted to display an article's journal's name I would use:
-
-`{% raw %}{{ article.journal.name }}{% endraw %}`
diff --git a/content/support/email-and-reminders/email-templates.md b/content/support/email-and-reminders/email-templates.md
index 83f3813b..9a8a1819 100644
--- a/content/support/email-and-reminders/email-templates.md
+++ b/content/support/email-and-reminders/email-templates.md
@@ -2,19 +2,27 @@ title: Email templates
# Email templates
-The email templates system allows you to search through and edit all of the email templates for a given journal.
+The email templates system allows you to view, search and edit the email templates used by a journal. These templates control the content of both automated and manually sent emails (for example, review invitations, reminders and decision emails).
> [!WARNING]
-> Editing an email template could cause it to break.
+> Editing an email template can cause emails to display incorrectly if placeholders are changed or removed.
-Each email template has access to different objects, making documenting this quite difficult. We have a list of objects available and will provide examples below. If you are uncertain about how to update an email template or uncomfortable, you can reach out to your administrator or Janeway Support.
+Each email template has access to a specific set of objects (such as an article, review assignment or journal). Because this varies by template, there is no documentation for every possible option. However, more information can be found on the Email variables page and template examples are available as well. If you are uncertain about how to update an email template or uncomfortable, you can reach out to your administrator or Janeway Support.
## Editing templates
-When editing a template, you will see the default version of the email at the top and a rich-text editor below. If you do not have a specific setting for your journal (i.e. you've never overwritten the default setting) the rich text box will appear blank. To get started, copy the default version into the rich-text box and edit it.
+When editing an email template, you will see:
-> [!TIP]
-> When editing an email that has a URL placeholder (like `{% raw %}{{ review_url }}{% endraw %}`) it is important that you do not add anything immediately after this placeholder as email clients may interpret them as part of the link.
+- The default version of the email at the top of the page.
+
+- A rich-text editor below, where you can create a customised version for your journal.
+
+If your journal has not previously customised a template, the rich-text editor will appear blank.
+
+To get started, copy the default version into the rich-text box and edit it.
+
+> [!WARNING]
+> When editing an email that includes a URL placeholder (for example `{% raw %}{{ review_url }}{% endraw %}`), do not add text immediately after the placeholder. Email clients may treat added characters as part of the link, which will break it.
diff --git a/content/support/guides/account-set-up-placeholder.md b/content/support/guides/account-set-up-placeholder.md
deleted file mode 100644
index c09726e6..00000000
--- a/content/support/guides/account-set-up-placeholder.md
+++ /dev/null
@@ -1,9 +0,0 @@
-title: Set up an Account on Janeway
-
-# Set up an Account on Janeway
-
-## Account without a submission
-
-## Account with a submission
-
-## Setting up as an editor
diff --git a/content/support/guides/account-set-up.md b/content/support/guides/account-set-up.md
new file mode 100644
index 00000000..e59d46fe
--- /dev/null
+++ b/content/support/guides/account-set-up.md
@@ -0,0 +1,32 @@
+title: Creating an account on Janeway
+
+# Creating an account on Janeway
+
+From the front page of a journal, select **Register** to set up an account. Complete the form and activate your account using the link sent to you by email. Once your account is set up and activated, you can sign in to Janeway.
+
+If you are an author making a submission, you don't need to create an account. One will be created as part of the submission process.
+
+If you have been invited to review, you may be able to complete your review without creating an account if the journal has enabled one-click peer review.
+
+If the journal is part of a press and you have access to another journal in that press, you may already have an account. Sign in using your existing credentials. If you make a submission, you automatically receive the author role. If you need other roles on the journal, ask an editor or press manager to assign the relevant roles.
+
+## Setting up as an editor
+
+To create an editor account, first register using the steps above. An editor, press manager, or someone with **Staff** permission then needs to assign you the editor role.
+
+## Editing your account
+
+You can edit your account by clicking on the account icon in the top-right corner. This displays either your initials or a profile picture, if one has been set. Click **Profile** to open the profile page, where you can edit your profile.
+
+
+
+On this page, you can do the following:
+
+- Update your email address.
+- Change your password.
+- Update your affiliation.
+- Update personal details, such as name, ORCID, social media links, biography, and signature.
+- Set a profile picture.
+- Set review interests.
+- Set your timezone.
+- Set your profile visibility.
diff --git a/content/support/guides/account-troubleshooting-placeholder.md b/content/support/guides/account-troubleshooting-placeholder.md
index d0e3a8b2..6c594956 100644
--- a/content/support/guides/account-troubleshooting-placeholder.md
+++ b/content/support/guides/account-troubleshooting-placeholder.md
@@ -2,6 +2,29 @@ title: Account troubleshooting
# Account troubleshooting
+## Activate your account
+
+If you are sure your password is correct and you cannot login, your account has likely not been activated yet.
+This is usually resolved either by:
+
+- Requesting a password reset link. This will send you an account activation email, if your account has not yet been activated. If your account was not created by you (or an editor) but was imported into Janeway, this will not work. You will need to use the option below.
+
+- An editor or journal manager activating your account. (See Activating a user account for instructions )
+
+### Activating a user account
+
+1. Go to **Journal users** on the **Manager** interface.
+2. Find the user in question through the searchbox and/or filter by account activation status.
+ 
+3. Click **Edit** for the appropriate user
+ 
+4. Set the account activation toggle to **Yes**.
+ 
+5. Make sure to save the change made by clicking the **Save** button at the bottom of the page.
+6. The account is now active.
+
+
+
## New password
### Reset your password
@@ -15,7 +38,7 @@ If you have forgotten your password and need to reset it:
5. Click the link in the email.
6. Fill in the password fields to set a new password.
-
+
If you have not received the password reset email, contact **Support**.
@@ -27,5 +50,3 @@ If you know your Janeway password and want to update it:
2. Click on the circle with your initials or profile picture in the top-right corner and select **Profile**.
3. Go to the **Update password** block and fill in your current and new passwords in the respective fields.
4. Click the **Update password** button.
-
-## Activate your account
diff --git a/content/support/guides/getting-started-placeholder.md b/content/support/guides/getting-started-placeholder.md
index 2eb3fdb9..769da385 100644
--- a/content/support/guides/getting-started-placeholder.md
+++ b/content/support/guides/getting-started-placeholder.md
@@ -4,3 +4,5 @@ title: Getting started with Janeway
- Registering an account and setting up permissions.
- Navigating Janeway.
+
+_Coming soon_
diff --git a/content/support/guides/janeway-guides.md b/content/support/guides/janeway-guides.md
index 2a28855b..e0eea347 100644
--- a/content/support/guides/janeway-guides.md
+++ b/content/support/guides/janeway-guides.md
@@ -2,6 +2,10 @@ title: Janeway guides
# Janeway guides
+This is a landing page for guides available.
+_Coming soon_
+
+
+safety check
@@ -80,3 +84,5 @@ Testy test
| 👁️ | **View** | Opens the selected issue’s management view. |
| 🗑️ | **Delete** | Removes the issue permanently. |
| 🔘 | **Make current** | Marks the issue as the current active issue (used for public display). |
+
+-->
diff --git a/content/support/guides/janeway-metadata.md b/content/support/guides/janeway-metadata.md
index 99375484..cd9b4619 100644
--- a/content/support/guides/janeway-metadata.md
+++ b/content/support/guides/janeway-metadata.md
@@ -2,6 +2,8 @@ title: Metadata on Janeway
# Metadata on Janeway
+_This is a work in progress_
+
## Managing metadata
- How is metadata collected / created
diff --git a/content/support/guides/journal-design-placeholder.md b/content/support/guides/journal-design-placeholder.md
index c425ca05..4dc671df 100644
--- a/content/support/guides/journal-design-placeholder.md
+++ b/content/support/guides/journal-design-placeholder.md
@@ -2,15 +2,21 @@ title: Journal design
# Journal design
+_Coming soon_
+
+
+Image guidelines (missing hyperlink)
## Themes
-Janeway has three available themes that determine the appearance of a journal and its layout. These themes are Clean, Material and OLH. You can read more about the themes in this section. All three can be customised using CSS and the **Custom Styling** plugin .
+Janeway has three available themes that determine the appearance of a journal and its layout. These themes are Clean, Material and OLH. You can read more about the themes in this section (missing hyperlink). All three can be customised using CSS and the **Custom Styling** plugin (missing hyperlink).
## Custom styling
- Css ahoy
explain differs per theme.
+
+-->
diff --git a/content/support/guides/journal-setup-placeholder.md b/content/support/guides/journal-setup-placeholder.md
index 71c40b62..2609f714 100644
--- a/content/support/guides/journal-setup-placeholder.md
+++ b/content/support/guides/journal-setup-placeholder.md
@@ -2,6 +2,8 @@ title: Set up your journal
# Set up your journal
+_This is a work in progress_
+
Journal name
Journal domain
diff --git a/content/support/guides/workflow-author.md b/content/support/guides/workflow-author.md
index 0e45adab..540d6b5f 100644
--- a/content/support/guides/workflow-author.md
+++ b/content/support/guides/workflow-author.md
@@ -80,7 +80,7 @@ Metadata that may be requested on this page:
- Keywords
You can add keywords to your article to help people discover it. To add keywords, type the word or phrase into the textbox and press 'Enter' to add it. If you wish to delete a keyword, click the **X** icon next to it within the textbox. Keywords can include spaces and special characters.
- 
+ 
Individual journals can add more fields to this page. These will be displayed under **Additional fields**.
@@ -94,7 +94,17 @@ To add more authors to a submission, you can either search the journal's author
- This lets you search the journal's database of authors by using their email address or ORCID. You cannot search using a name or institution.
- If a matching record is found, they will be added as a co-author. If not, you will be notified that no account has been found.
- 
+ 
+
+- Adding authors through **Add author manually**
+ - The **Add author manually** button lets you create a new author record for authors if they do not already have one. The following fields are mandatory in Janeway:
+ - First name
+ - Last name
+ - Email address
+
+This will not create a new account for the additional author(s), it will only create an author record with no account attached. If they wish to login and check the article's progress, they can create an account with the same email address that was used on the author record (submission). Either the submitting author or an editor can then link the account to the author record.
+
+
If the search of the journal's author list or ORCID search are successful, author details will be added automatically. You can still make edits, by clicking on **Edit author details**. When an author already has an account with the journal or another journal under the press, this submission will be linked to their existing record.
@@ -116,7 +126,7 @@ To change the correspondence author, another author with a pre-existing (confirm
Janeway uses [Research Organization Registry (ROR)](https://ror.org/) to manage affiliation data. You can add author affiliation by clicking **Edit author details** and scrolling down to **Affiliations**. From here, you can add, remove and edit affiliations. If an author ORCID has been provided, their affiliation will be added automatically from their ORCID. You can still edit this, if it is incorrect.
-
+
After the submission is completed, co-authors will be notified and will be able to access the submission and update or edit their details.
@@ -138,8 +148,8 @@ While you can add only one manuscript file, multiple figures and/or data files c
You will then be asked to supply information about any relevant funding. You can search for your funding source using our **Search for funder** function or add them manually. When adding a funder, you will be given the option to provide an optional Funder DOI and Grant ID.
-
-
+
+
If you do not have any funders to add, you can skip this page by clicking **Save and continue** without adding any funders.
@@ -147,7 +157,7 @@ If you do not have any funders to add, you can skip this page by clicking **Save
The **Review** page displays a run-down of the article you've submitted, metadata, files and authors. From here, you can click **Complete** to submit or jump back to other stages to make changes. Once you have finalised your submission, you cannot make any changes until editors request revisions (if applicable).
-
+
## Revisions
@@ -168,7 +178,7 @@ When an editor requests revisions, there are two ways to start this process:
3. Scroll down to **Submitted articles**.
4. Click the **Revision request** button next to the article.
-
+
Once you have accessed the revision request, you can view the available peer reviews. You can also download, revise, and upload new files.
@@ -201,13 +211,15 @@ Typeset proofs are not an opportunity to make changes to the content or style of
1. Upload your revised manuscript by replacing the copyeditor's version of the file with your own updated version.
- 
+ 
2. Fill in the **Note to the editor** field with any additional information.
+
3. Select a Decision (either **Accept** or **Corrections required**).
+
4. Click **Complete copyedit task**.
- 
+ 
## Proofing
@@ -215,7 +227,11 @@ After your paper has been accepted and copyedited, the editors might send you a
You can access your proofing tasks either through the link sent to you by email or through the proofing task button on your dashboard.
-
+
+
+
+
+
For journals that publish content in multiple media formats (HTML, PDF, XML, etc.), it is important that you check all these files before publication. This will not require any technical knowledge; authors are not expected to be able to open and read XML/HTML code. Instead, Janeway provides a **View file** button, which allows you to preview how the article will look once it is published.
@@ -235,6 +251,8 @@ Once you've previewed the files, you can provide feedback in two ways:
It is important to proof all the files thoroughly in order to avoid unnecessary follow-up rounds. This saves everyone time, work, and money and makes the publishing process run much more smoothly.
-Click **Mark task as complete** to finish proofreading. Once you have provided your feedback, the editorial team might send you another proofing task once the requested corrections have been made. If this happens, the process will be exactly the same as in the first round of proofing. If there are no (or only very minor) corrections, you will likely not be asked to review again.
+To finish proofing, click **Mark task as complete**. Once you click this button, you will not be able to return to this page.
+
+Once you have provided your feedback, the editorial team might send you another proofing task once the requested corrections have been made. If this happens, the process will be exactly the same as in the first round of proofing. If there are no (or only very minor) corrections, you will likely not be asked to review again.
Once the article is published, all authors will receive a notification through the email addresses used when the article was submitted (except if this has been updated before publication).
diff --git a/content/support/guides/workflow-copyeditor.md b/content/support/guides/workflow-copyeditor.md
index c3d093e3..381e6095 100644
--- a/content/support/guides/workflow-copyeditor.md
+++ b/content/support/guides/workflow-copyeditor.md
@@ -41,7 +41,7 @@ Once you have clicked into a paper, the next page you see will be broken into fo
-This is where you can find the necessary files to complete the copyediting task. This will include the manuscript and other files, such as figures. You can upload the copyedited manuscript using the **Upload file** button.
+This is where you can find the necessary files to complete the copyediting task. This will include the manuscript and other files, such as figures. You can upload the copyedited manuscript using the 
**Upload file** button.
### Complete task
diff --git a/content/support/guides/workflow-editor-copyediting.md b/content/support/guides/workflow-editor-copyediting.md
index eb1f7faa..49f8f021 100644
--- a/content/support/guides/workflow-editor-copyediting.md
+++ b/content/support/guides/workflow-editor-copyediting.md
@@ -8,7 +8,7 @@ The copyediting stage allows you to assign, track and complete copyediting tasks
To start the copyediting of an article, the first thing you will need to do is open a copyediting task and assign a copyeditor. To do this, click **Add a copyedit assignment**.
-
+
This will open a new page where you can do the following:
@@ -40,7 +40,7 @@ Before the task is accepted, you can edit the notes and due date or delete the a
## Review copyediting
-
+
The review copyedit page presents the response from the copyeditor, including their notes and any files they uploaded. You can download the copyedited manuscript using the 
**Download** icon. You can also do one of three things under **Actions** on the right-hand side:
@@ -51,7 +51,7 @@ The review copyedit page presents the response from the copyeditor, including th
- **Reopen the task**
Ask the copyeditor to make further changes.
-
+
Requesting author review will ask the author to review the copyedit and inform the editor if any corrections are required. The author can also upload a file if they have made corrections or used track changes.
diff --git a/content/support/guides/workflow-editor-draft-decision.md b/content/support/guides/workflow-editor-draft-decision.md
index 5ac7acf1..ba276fea 100644
--- a/content/support/guides/workflow-editor-draft-decision.md
+++ b/content/support/guides/workflow-editor-draft-decision.md
@@ -4,7 +4,7 @@ title: Editor guide to draft decisions
Draft decisions (DD) are an optional element of the review workflow. It allows section editors to submit a draft of their editorial decision for approval by an editor. When enabled, a section editor will only see the draft decision feature on the **Decision helper** page.
-
+
The options for draft decision types are the same as those in the standard decision workflow:
@@ -34,13 +34,13 @@ For section editors, the workflow will look like this:
- Email to the editor
- Draft email to author
-
+ 
For editors, this process will look like the following:
1. Access the draft decision through the link in the notification email or **Decision helper > Draft decisions**. The draft decisions will be listed under **Existing drafts**.
- 
+ 
2. Review the draft decision and email by clicking **Edit**.
@@ -48,7 +48,7 @@ For editors, this process will look like the following:
3. If required, you can edit the decision type, due date and email to the author. You can also view any completed peer reviews on this screen.
- 
+ 
4. Accept or decline the draft. If accepted, the decision made by the section editor(s) will be actioned.
diff --git a/content/support/guides/workflow-editor-pandoc.md b/content/support/guides/workflow-editor-pandoc.md
index 6a8acc1b..976d1af8 100644
--- a/content/support/guides/workflow-editor-pandoc.md
+++ b/content/support/guides/workflow-editor-pandoc.md
@@ -6,7 +6,7 @@ The Pandoc plugin provides an option to generate HTML files from submissions in
To work on a file, find it under **Files for typesetting** and click **Options**. This will present two options:
-
+
- Convert: This option makes the file available for download to readers. This feature is useful when you want to make the original manuscript file available.
@@ -23,7 +23,7 @@ If needed, you can also edit galleys on Janeway. This is currently only availabl
> [!TIP]
> If your journal is 'examplejournal.com', it is 'examplejournal.com/file-editor'. If your journal link looks like 'example.com/journal', it is 'example.com/journal/file-editor'.
-On the file editor, you can find a table with all HTML and XML galleys in your journal - both published and unpublished. HTML galleys can be edited in either a rich-text editor or plain text editor, XML galleys can only be edited in a plain text editor (Pandoc will not generate XML files - so if you are using Pandoc exclusively, you will not see any XML files). You edit a galley file by clicking **Edit**.
+On the file editor, you can find a table with all HTML and XML galleys in your journal - both published and unpublished. HTML galleys can be edited in either a rich-text editor or plain text editor. XML galleys can only be edited in a plain text editor (Pandoc will not generate XML files - so if you are using Pandoc exclusively, you will not see any XML files). To edit a galley file, you can click **Edit**.
> [!NOTE]
> A rich text editor will display content as it will appear on the page (Like Microsoft Word or Google Drive). A plain text editor will display the code, rather than how the content will appear on the page.
diff --git a/content/support/guides/workflow-editor-prepub.md b/content/support/guides/workflow-editor-prepub.md
index d1492728..c02d0e58 100644
--- a/content/support/guides/workflow-editor-prepub.md
+++ b/content/support/guides/workflow-editor-prepub.md
@@ -40,7 +40,7 @@ Articles usually have a DOI (Digital Object Identifier) automatically assigned a
DOI links should redirect to the article, without intermediate steps. To ensure the redirect is working properly, you can check the number of "hops" shown in the bulleted list. There should be no more than two. See the image below for example.
-
+
If the DOI has more than two hops, or you see something else, you need to look more closely at the DOI's details. Select **Edit** and check the **Status** column for an indication of what to do next. See Interpreting DOI status for more information.
@@ -88,7 +88,7 @@ Check the **Mark as Complete** box to move on to the next step.
Once you have completed all the steps, you are ready to publish the article. The **Publish this article** button is located at the top of the page, on the right-hand side. Any remaining warnings, including options to address them, will accompany it.
> [!NOTE]
-> The warning regarding whether an article is marked as peer reviewed will always remain. This allows editors to double-check this and easily adjust, if needed.
+> The warning regarding whether an article is marked as peer reviewed will always remain. This allows editors to double-check this and adjust, if needed.
Once the **Publish this article** has been clicked, the article is now scheduled to publish at the specified time. Once an article is live, you can see it on the Articles page and you may wish to check if all files display correctly. For information on managing articles after publication, see: Content management.
diff --git a/content/support/guides/workflow-editor-review.md b/content/support/guides/workflow-editor-review.md
index 9f358fcc..eb11c113 100644
--- a/content/support/guides/workflow-editor-review.md
+++ b/content/support/guides/workflow-editor-review.md
@@ -14,14 +14,14 @@ If this is not the first round of review, you will need to open a new review rou
After the appropriate files have been selected, you can add the reviewers. You do this by clicking **Add new reviewer**.
-
+
Now, you can either select a reviewer from the list presented to you, select an existing user who does not yet have the reviewer role (**Enrol existing user**) or invite a new reviewer who does not yet have an account (**Add new reviewer**).
> [!TIP]
> It is recommended to turn on [one-click review]() . This allows reviewers to complete a review using a unique link without needing to register an account or log in.
-
+
When assigning the reviewer, you can also select the review form, review type (open, single or double anonymous) and set the due date. You can set defaults for these in review settings to minimise the customisation needed here. Once you have selected a reviewer and are happy with the review settings, click **Add reviewer** at the bottom of the page to confirm. You will then be shown the outgoing email on the next page, which you can edit or select the option to skip sending this email.
@@ -33,7 +33,7 @@ You can see how this appears to reviewers and what the review process looks like
Once a review has been requested, it will be listed on the review page. The initial stage of any review is "Awaiting acknowledgement" - this means the review has not yet responded to the review invitation.
-
+
Once a review has been requested, you can do one of the following:
@@ -86,7 +86,7 @@ Toggling the sections on or off will determine whether the author can see answer
If you are ready to make a decision after a round of review, you can click on **Make a decision** to open the **Decision helper** page. On this page, you will see a summary of reviewer recommendations, their review form answers and a list of uncompleted reviews.
-
+
In addition to this, the following buttons are available:
@@ -129,7 +129,7 @@ You can share completed peer reviews among reviewers. This can be set up through
- After the first round of review.
- Once the first round of review is complete, a new option will be present on the **Decision helper** screen to mark the reviews as shareable. It will send an email to the reviewers, providing them with a link to access and view the review content.
- 
+
- Sharing reviews in the second round and beyond
- Reviews from previous rounds can also be automatically shared with reviewers on the current round. When reviewers access the review interface, they will be given the choice to view anonymous reviews completed by their peers. Editors can modify the message to clarify why reviewers can view the reviews through the review settings .
diff --git a/content/support/guides/workflow-editor-submission.md b/content/support/guides/workflow-editor-submission.md
index 20c01821..787884bd 100644
--- a/content/support/guides/workflow-editor-submission.md
+++ b/content/support/guides/workflow-editor-submission.md
@@ -15,13 +15,13 @@ By default, editors are notified by email once a new article has been submitted.
When you click on an article in the list of new submissions, you will be taken to a page with an overview of the submission.
-
+
The left block of the page displays the article’s metadata and author metadata, whilst workflow actions and potential editors are displayed on the right.
Before the article can enter the workflow, it must be assigned to an Editor or Section editor through **Add editors**.
-
+
Once assigned, the editor can do one of the following through **Actions**:
@@ -31,7 +31,7 @@ Once assigned, the editor can do one of the following through **Actions**:
If you reject the article, there will be an opportunity to provide an explanation to the author.
-
+
Accepting the article will move it into Copyediting, skipping peer review. You can do this for editorials or other submissions that do not require peer review.
@@ -48,6 +48,6 @@ The projected issue functionality can be used internally to keep track of plans
On this page, you can also edit author details. This is done by clicking **Edit author metadata** which will take you to a screen where you can edit author details, change the author order, change the correspondence author, or add authors.
To edit an author's affiliation, click **Edit author details** and scroll down to the **Affiliations** block, where you can edit, add or remove an author's affiliation(s).
-
+
Janeway uses [Research Organization Registry (ROR)](https://ror.org/) to manage affiliation data, this ensures consistent formatting of affiliation data and links authors to their instituions, improving metadata quality. You can search for an institution or, if no match is found, add the details manually.
diff --git a/content/support/guides/workflow-editor-typesetting.md b/content/support/guides/workflow-editor-typesetting.md
index de7654fe..7438da24 100644
--- a/content/support/guides/workflow-editor-typesetting.md
+++ b/content/support/guides/workflow-editor-typesetting.md
@@ -25,19 +25,19 @@ After selecting an article, you will be taken to the typesetting page. This page
- At the top, you can see the rounds which are used for both typesetting and proofing, similar to the peer review page. From here, you start rounds and assign typesetters and proofreaders.
- 
+ 
- Under this, there is **Files for typesetting** where files used in typesetting are listed - this includes manuscript files, images and any pre-existing galleys.
- This is followed by **Galleys**, which lists typeset files (galleys) which will become available to readers.
- 
+ 
- Finally, **Optional files** contains the supplementary files (data files, appendices, etc.) and (if using) source files (intermediate files used by typesetters, e.g. Adobe InDesign files).
- The **Actions** block, where you can start new rounds or complete typesetting, is on the right-hand side - similar to the peer review and copyediting stages.
- 
+ 
You can see the typesetter's view and their experience of the workflow in the typesetter guide.
@@ -73,7 +73,7 @@ If you do not use a typesetter or file conversion through Janeway, you can uploa
When uploading an HTML or XML file with images, they must be uploaded separately, as HTML and XML files do not contain the images themselves (like a DOCX or PDF file might). Images can be uploaded by clicking the 
**Edit** icon and using the upload functions on the page it leads to, for more information see: Images and figure files . You can also **Download** the file or 
**Preview** it, using the respective icons.
-
+
> [!CAUTION]
> Do not use the image or galley upload for supplementary files. See Supplementary files for more information.
@@ -82,15 +82,15 @@ When uploading an HTML or XML file with images, they must be uploaded separately
Janeway also offers the option to convert manuscript files using the [Pandoc plugin](https://github.com/BirkbeckCTP/pandoc), which can generate HTML galleys from a MS Word document. For a full guide on how to manage typesetting with Pandoc, see Typesetting with Pandoc .
-If you are interested in using the Pandoc plugin, contact your System administrator (What is a system administrator?) .
+If you are interested in using the Pandoc plugin, contact your System administrator (What is a system administrator? ).
## Working with a typesetter
-This section outlines how to work with an external typesetter, including assigning tasks, reviewing their work, and assigning revisions (if needed). You will need to set up an account for your typesetter. If you have not done this yet, see Account Management for more information. .
+This section outlines how to work with an external typesetter, including assigning tasks, reviewing their work, and assigning revisions (if needed). You will need to set up an account for your typesetter. If you have not done this yet, see Account Management for more information.
### Assigning a typesetter
-Click **Add typesetter** to open the typesetter assignment page and start a new typesetting assignment.
+Click **Assign a typesetter** to open the typesetter assignment page and start a new typesetting assignment.
@@ -116,7 +116,7 @@ There is no limit on the number of typesetters you can assign at one time.
Once the typesetter has completed their task, you will receive an email notification.
-
+
You can now review the typesetting task and select one of the following three options:
@@ -127,7 +127,7 @@ You can now review the typesetting task and select one of the following three op
- **Accept**
If no (further) proofing or corrections are required, you can accept the files and end the typesetting stage.
-
+
## Proofing
@@ -167,7 +167,7 @@ If no further corrections are needed, you can click **Complete typesetting** und
If you require corrections, click **Request corrections**.
-
+
### Requesting corrections
@@ -184,7 +184,7 @@ You can now assign a typesetter to correct issues that were flagged in proofing,
Once typeset files are uploaded into Janeway, they become manageable within the system. To manage a typeset file, click the **Edit** icon next to it.
-
+
On this page, you can do the following:
@@ -201,12 +201,12 @@ HTML and XML files uploaded to Janeway will be scanned to detect graphic, figure
For each missing image file, Janeway will present you with a block where you can either upload a new image file or select an existing one from the images already linked to the article.
-
+
> [!TIP]
> For typeset files with a large number of images, you can also create a ZIP file containing all the images and upload it using the ZIP uploader. Janeway will match the images against the tags in the typeset files. Ensure the image names and file types are an exact match those in the typeset file.
-
-
+>
+> 
## Advanced styling
diff --git a/content/support/guides/workflow-reviewer.md b/content/support/guides/workflow-reviewer.md
index 1feb591f..393a9f71 100644
--- a/content/support/guides/workflow-reviewer.md
+++ b/content/support/guides/workflow-reviewer.md
@@ -39,9 +39,11 @@ If you accept the task, you will be taken to the page for this review. It is spl
This section displays information on how the editor would like you to undertake the review, an introduction to the review form, and metadata.
> [!NOTE]
-> This section may include both general review guidelines and guidelines specific to this review. These can differ depending on the journal and the type of submission. Please read through these even if you’ve reviewed a paper for this journal before, as they may not be the same as for a previous review task.
+> This section may include both general review guidelines and guidelines specific to this review. These can differ depending on the journal and the type of submission. Read through these even if you’ve reviewed a paper for this journal before, as they may not be the same as for a previous review task.
-At the bottom of this block, you will find an option to decline this review task if you are no longer able to complete it. If you opt to decline to review, you may be asked if you can suggest other suitable reviewers.
+At the bottom of this block, you will find another option to accept or decline this review task. If you initially accepted the task but are no longer available, decline it here so that it can be offered to someone else. If you opt to decline to review, you will be asked if you can suggest other suitable reviewers. This is optional, but highly encouraged.
+
+
### Review files
@@ -70,4 +72,4 @@ The sections of this form are:
## Review complete
-Once you have submitted your review, you will be presented with an overview of what you have written. Please note you will not be able to return to the review page or edit what you have written once you have clicked **Submit**.
+Once you have submitted your review, you will be presented with an overview of what you have written. Note you will not be able to return to the review page or edit what you have written once you have clicked **Submit**.
diff --git a/content/support/guides/workflow-typesetter.md b/content/support/guides/workflow-typesetter.md
index 368157db..a270a525 100644
--- a/content/support/guides/workflow-typesetter.md
+++ b/content/support/guides/workflow-typesetter.md
@@ -25,7 +25,7 @@ For completed assignments, it will display:
-You can then click **View Assignment** to display the assignment page.
+You can then click **View assignment** to display the assignment page.
## Typesetting assignments page
@@ -41,8 +41,8 @@ This page is divided into three sections.
- You can access the files to typeset (manuscript files) and any supplementary files.
- Under this, you will find space to upload your completed work and (if required) any source files.
-- Metadata
- - This is where you will find the metadata for the typesetting task.
+- Metadata
+ This is where you will find the metadata for the typesetting task.
- Complete typesetting
- Under this section, you can leave any notes to the editors.
@@ -67,19 +67,19 @@ Janeway will attempt to provide an appropriate label if this is left blank. Howe
## Editing typeset files and uploading additional files
-If you need to make changes to the typeset files, you can reupload them or upload additional files through the **Edit Typeset File** page. This page can be accessed by clicking **Edit**.
+If you need to make changes to the typeset files, you can reupload them or upload additional files through the **Edit typeset file** page. This page can be accessed by clicking **Edit**.
-The **Edit Typeset File** page is divided into three sections:
+This page is divided into three sections:
-- The typeset file
- - You can replace the typeset file and see the file history here.
+- The typeset file
+ You can replace the typeset file and see the file history here.
-- Typeset file details
- - This is where you can edit the file label, which denotes the file type.
+- Typeset file details
+ This is where you can edit the file label, which denotes the file type.
- Additional file uploads
- If authors or editors have already provided images, you can find and select them here.
@@ -103,7 +103,7 @@ When a file typeset in HTML or XML contains image links, Janeway will detect the
If the image files have already been uploaded onto Janeway, you can select them instead.
-If you need to upload a large number of images, it might be faster to use the zip uploader (see **Upload ZIP file** in the picture below). To do so, create a ZIP archive file with all the image files. The image filenames must match the links in the typeset file; otherwise, they will not be imported.
+If you need to upload a large number of images, it may be faster to use the zip uploader (click on **Upload zip file**, highlighted in the image below). To do so, create a ZIP archive file with all the image files. The image filenames must match the links in the typeset file; otherwise, they will not be imported.
## Styling
@@ -113,7 +113,7 @@ You can also select the XSL file used to render the HTML from the file. Unless e
### Finishing up
-Once you finish the typesetting (or correction) task, you can leave a note for the editor, click the button to complete the task and send it to the editor for review. Please note that you cannot return to this page once you complete the task.
+Once you finish the typesetting (or correction) task, you can leave a note for the editor, click the button to complete the task and send it to the editor for review. Note that you cannot return to this page once you complete the task.
> [!NOTE]
> If you attempt to complete the typesetting task with potential issues remaining (e.g. missing image files, typeset files that have not been corrected), Janeway will warn you about this.
@@ -128,14 +128,14 @@ default.
Here is an example in JATS XML of an isolated bit of Arabic text in a
document that is otherwise left-to-right:
-
+
Make sure you use a text editor that shows zero-width unicode
characters, like U-2067. The above screenshot is an XML file opened in
VS Code.
Here is the rendered output:
-
+
Notice the following about the code sample:
@@ -171,8 +171,4 @@ In some cases you might need to center-align text:
The output is:
-This is accomplished with the the [styled-content JATS
-element](https://jats.nlm.nih.gov/publishing/tag-library/1.3/element/styled-content.html)
-and a [style
-attribute](https://jats.nlm.nih.gov/publishing/tag-library/1.3/attribute/style.html)
-specifying CSS for center text alignment and block display.
+This is accomplished with the the [styled-content JATS element](https://jats.nlm.nih.gov/publishing/tag-library/1.3/element/styled-content.html) and a [style attribute](https://jats.nlm.nih.gov/publishing/tag-library/1.3/attribute/style.html) specifying CSS for center text alignment and block display.
diff --git a/content/support/identifiers/crossref-article-doi-placeholder.md b/content/support/identifiers/crossref-article-doi-placeholder.md
index 1231a190..281c9582 100644
--- a/content/support/identifiers/crossref-article-doi-placeholder.md
+++ b/content/support/identifiers/crossref-article-doi-placeholder.md
@@ -2,152 +2,138 @@ title: Crossref article DOI
# Crossref article DOI
+Janeway can automatically register (also called "mint" or "deposit") Digital Object Identifiers (DOIs) for articles with Crossref, provided the journal’s settings are correctly configured.
+
+This page explains:
+
+- When DOIs are created and updated
+- How to check and manage DOIs using the DOI Manager
+- How to interpret DOI registration statuses
+- Which Crossref settings are required
+
## When are DOIs minted?
-If all the settings are properly configured (see below), Janeway handles
-DOI registration for you, stepping in at a few key points in the
-publishing pipeline.
+If Crossref settings are correctly configured, Janeway handles DOI registration automatically at key points in the publishing workflow.
+
+By default, Janeway registers a DOI with Crossref when an article is accepted for publication.
+
+After acceptance, the DOI will exist in Crossref’s system. However, the web page it points to may not yet be live if the article has not been published. This is expected and does not indicate a problem.
+
+Provisional metadata is sent, but no author-identifiable details are shared.
-By default, a DOI is registered (a.k.a. minted, deposited) with Crossref
-when an article is accepted for publication. Some provisional metadata
-is sent at this time (No author-identifiable details are shared). When
-an article is scheduled for publication, a new request is sent to
-Crossref to update all metadata records.
+Later, when the article is scheduled for publication, Janeway sends a deposit to Crossref to update the metadata.
+
+When the article is published, the DOI becomes a working permalink to the published article.
> [!TIP]
-> You can let editors see a preview of the data that gets sent before
-> accepting an article. See **Accept Article Warning** under
-> Review Settings.
+> You can allow editors to preview the data that will be sent to Crossref before accepting an article. See **Accept article warning** under **Review settings**.
-At this stage, the DOI will be registered with Crossref, but the webpage
-it points to on your journal website may not be active yet if the
-article isn't published yet. That's normal.
+## When manual intervention may be needed
+
+The automatic workflow may be interrupted in some situations, for example:
-The DOI is deposited with Crossref again when the article is published,
-so any metadata updated in the interim will also be updated in
-Crossref's metadata feeds. This is also when the DOI starts working as a
-permalink, in addition to being a unique identifier.
+- Importing backlist content.
+- Missing or incomplete metadata.
+- Incorrect Crossref settings.
-There are things that might interrupt this default behavior. If you are
-importing backlist content, or there's an issue with the Crossref
-settings entered, or the required metadata isn't there, you may need to
-take a more active role. That's where the DOI Manager comes in.
+In these cases, you may need to take action using the **DOI Manager**.
## DOI manager
-You can see all the DOIs for a journal (if you are an editor) or for a
-press (if you are a staff member) in the DOI Manager.
+The **DOI Manager** allows you to view and manage DOI registration statuses. If you are an editor at journal level or if you are a staff member at press level.
+
+The DOI manager can handle up to 25 articles at a time. If your journal has more than 25 articles in total, use the filter to narrow the list of articles. You can filter by date, registration status, or primary issue until you have an actionable set of articles.
-First, filter by date, registration status, or primary issue until you
-have an actionable set of articles.
+Once you have filtered the list, you can:
-At the moment, the DOI Manager can handle small batches, such as 20
-articles, with no problems, but it may not be able to handle larger
-batches very well. We will optimize it to handle large batches in the
-future.
+- **Register DOIs**
+ Sends the article metadata to Crossref for registration.
-In some cases, you can preview the XML that will get sent to Crossref.
+- **Poll for status**
+ Checks the DOI status of Janeway articles.
-Once you have filtered the articles to your liking, you can take two
-actions: **Register DOIs** and **Poll for status**. **Register DOIs**
-will package up all the metadata into XML and send it to Crossref.
-Crossref will put all the deposits they receive in a queue to process,
-so the status may not be immediate. After a few moments (or longer if it
-is a large batch), you can use **Poll for status** to check the result.
+Crossref processes deposits in a queue, so status updates may not appear immediately. If you want to check the status of a DOI, you can use **Poll for status**.
> [!WARNING]
-> **Poll for status** on a large group of articles could take a long time,
-> so test it out on a smaller group first.
+> Using **Poll for status** on a large number of articles could take a long time. You may wish to test a small set first when investigating potential issues.
+
+In some cases, you can also preview the XML that will be sent to Crossref before registering.
## Interpreting registration status
-Unknown
-Janeway doesn't know the status. Try **Poll for status**.
+Each DOI in the DOI Manager shows a registration status:
+
+- Unknown
+ Janeway doesn't know the status. Try **Poll for status**.
-Not yet registered
-This DOI hasn't been registered yet. You can register it if what you see
-in the **DOI** column looks right (including pattern previews).
+- Not yet registered
+ This DOI hasn't been registered yet. You can register it if what you see in the **DOI** column looks right (including pattern previews).
-Queued at Crossref
-The deposit batch you sent is waiting to be read by the Crossref
-servers.
+- Queued at Crossref
+ The deposit has been received by Crossref and is waiting to be processed.
-Registered
-Success! Crossref understood all the metadata you sent and didn't find
-any problems with it.
+- Registered
+ Crossref successfully processed the metadata and didn't find any problems with it.
> [!TIP]
-> A status of **Registered** does not necessarily mean that the DOI will
-> resolve correctly, if the URL it points to isn't fully operational yet
-> on the Janeway side (i.e., the article isn't published).
+> A status of **Registered** does not necessarily mean the DOI will resolve correctly if the article is not yet published (or if the URL is not operational for other reasons).
+
+- Registered (but some citations not correctly parsed)
+ Article metadata was accepted, but citation parsing errors occurred. Check the XML shown in the **Response** column for details.
-Registered (but some citations not correctly parsed)
-Crossref understood the article-level metadata, but when it went to
-process the citations, there were errors. Check the XML in the
-**Response** column for details.
+- Registered with warning
+ The DOI was registered, but Crossref returned a warning. Check the **Response** column for more information.
-Registered with warning
-Crossref understood and registered the DOI, but sent back a warning.
-Check the XML in the **Response** column for details.
+- Registration failed
+ Crossref could not register the DOI due to an error. Check the **Response** column to identify the issue.
-Registration failed
-Crossref tried to register the DOI but couldn't because of a problem.
-Check the XML in the **Response** column for details.
+## Crossref settings
-## Crossref Settings
+Crossref settings are configured from the Manager interface under **Crossref settings**. On this page, you will find the following fields used to configure Crossref:
-To edit the Crossref settings, select **Crossref Settings** from the
-manager interface. The fields are as follows:
+- Use Crossref DOIs
+ Enables or disables DOI registration for the journal. If disabled, no DOIs will be minted.
-Use Crossref DOIs
-If disabled, no DOIs will be minted
+Use Crossref test deposit server
+ Sends DOIs to Crossref’s test system instead of the live system. Useful for testing only.
-Use Crossref Test Deposit Server
-If enabled, DOIs will be minted on Crossref's test system
+- Crossref username
+ Your Crossref account username.
-Crossref Username
-Your crossref username
+- Crossref password
+ Your Crossref account password.
-Crossref Password
-Your crossref password
+- Crossref depositor email
+ The email address of the depositor.
-Crossref Depositor Email
-The email address of the depositor
+- Crossref depositor name
+ The name of the depositor
-Crossref Depositor Name
-The name of the depositor
+- Crossref prefix
+ Your Crossref prefix, usually in the form `10.xxxx`.
-Crossref Prefix
-The prefix for your crossref account -- usually 10.XXXX
+- Crossref registrant name
+ The registrant name recorded with Crossref for this journal (for example, "Open Library of Humanities").
-Crossref Registrant Name
-The name of the registrant for this journal on Crossref's system (e.g.
-Open Library of Humanities)
+## DOI formatting settings
-DOI Display Prefix
-Text to prepend to DOIs -- used to generate DOI URLs
+- DOI display prefix
+ Text added before the DOI when generating display URLs. Usually `https://doi.org/`.
-DOI Display Suffix
-Text to append to DOIs -- also used to generate DOI URLs
+- DOI display suffix
+ Text added after the DOI when generating display URLs. Usually left blank.
-DOI Pattern
-The pattern for auto-generating DOIs. Defaults to using the journal code
-and article ID (e.g. `orbit.123`):
+- DOI pattern
+ The DOI pattern controls how article DOIs are generated automatically. By default, Janeway uses the journal code and article ID, for example: `orbit.123`. Using the following objects:
-> `{% raw %}{{ article.journal.code }}.{{ article.pk }}{% endraw %}`
+ > `{% raw %}{{ article.journal.code }}.{{ article.pk }}{% endraw %}`
-Title DOI
-The DOI (not in URL format) registered for this journal (e.g.
-`10.001/my-journal`). It is included on all deposits for this journal.
-It must be registered ahead of time.
+- Title DOI
+ The DOI for the journal itself (not in URL format), for example: `10.001/my-journal`. It is included on all deposits for this journal and, is using, must be registered ahead of time.
-It is mandatory for a journal to have a DOI registered **only** when an
-ISSN is not available for a journal, as Crossref requires at least one
-unique identifier for every journal.
+A journal DOI is only mandatory if a journal does _not_ have an ISSN, as Crossref requires at least one unique identifier per journal.
-However, even if your journal has an ISSN, Crossref still recommends
-registering a DOI for your journal. We recommend using your journal code
-as the DOI. For example, with the prefix of `10.0001` and the journal
-code of `abcd`, you could set the journal DOI to `10.0001/abcd`.
+However, Crossref recommends registering a journal DOI even when an ISSN exists. We recommend using your journal code
+as the DOI. For example, with the prefix of `10.0001` and the journal code `abcd`, you could set the journal DOI to `10.0001/abcd`.
diff --git a/content/support/identifiers/crossref-issue-doi-placeholder.md b/content/support/identifiers/crossref-issue-doi-placeholder.md
index e56d7b6b..388ea246 100644
--- a/content/support/identifiers/crossref-issue-doi-placeholder.md
+++ b/content/support/identifiers/crossref-issue-doi-placeholder.md
@@ -2,39 +2,44 @@ title: Crossref issue DOI
# Crossref issue DOI
-## Issue DOI pattern
+Janeway supports registering (minting) DOIs for journal issues, in addition to article-level DOIs. Issue DOIs are not registered independently. Instead, they are registered with Crossref when an article in the issue has its article DOI minted. The issue DOI is included in the XML send to Crossref, which will then mint the issue DOI. Only the primary issue to which an article is assigned will have its DOI minted.
-Janeway supports minting DOIs for journal issues automatically. With
-this setting, you can define the pattern used to generate the
-issue-level DOI that will be used for registration.
+> [!NOTE]
+> If an issue contains no articles for which it is the primary issue, its DOI will not be minted.
-With the default pattern, an issue with ID `1` (and prefix `10.0001`,
-and journal code `abcd`) will have a generated DOI of
-`10.0001/abcd.issue.1`.
+Issue-level DOIs can be generated automatically using a defined pattern or entered manually on a per-issue basis.
-A collection with an ID of `2` would have a generated DOI of
-`10.0001/abcd.collection.2`.
+This page explains how issue DOIs are generated, when they are registered with Crossref, and important limitations to be aware of.
## Auto-register issue-level DOIs
-When enabled, issues will have a DOI assigned and registered as soon as
-the first article in the issue is scheduled for publication. If an issue
+When **Auto-register issue-level DOIs** is enabled in the **Crossref settings**, Janeway will generate an issue DOI and register it with Crossref.
+
+The issue DOI is registered when the first article in the issue has its article DOI minted or is scheduled for publication (this will depend on what the article has its issue set, for more information see: Crossref article DOIs ). The issue DOI is included in the article’s XML metadata sent to Crossref, and no separate action is required to register it.
+
+> [!IMPORTANT]
+> If auto-registration for issue DOIs is enabled, issue DOIs should not be entered manually. To manually set issue DOIs, you must first disable automatic issue DOI registration.
+
+
+
+## Issue DOI pattern
+
+Janeway can automatically generate issue-level DOIs using a configurable pattern.
+
+Using the default pattern:
-### Issue DOIs
+- An issue with ID `1`, journal code `abcd`, and prefix `10.0001` will be assigned the DOI:
+ `10.0001/abcd.issue.1`.
-Issues can be assigned a DOI in Janeway. This can be done ad-hoc for
-each issue by editing the issue details and inputting the DOI manually,
-or by letting Janeway generate a DOI for you, based on a pattern (a DOI
-pattern can be set from the Crossref Settings page)
+- A collection with ID `2` will be assigned the DOI:
+ `10.0001/abcd.collection.2`
-When the Crossref integration is enabled, issue DOIs will be registered
-with Crossref whenever an article in that issue is registered with
-Crossref. This will be the case both for DOIs generated for Janeway as
-well as for those manually set.
+This pattern is used only if an issue DOI has not been entered manually.
> [!TIP]
> If you are migrating a Janeway installation from a version that did not
diff --git a/content/support/identifiers/identifiers-index-placeholder.md b/content/support/identifiers/identifiers-index-placeholder.md
index c9e0c7dc..ec0b904f 100644
--- a/content/support/identifiers/identifiers-index-placeholder.md
+++ b/content/support/identifiers/identifiers-index-placeholder.md
@@ -2,9 +2,11 @@ title: Identifiers
# Identifiers & discovery
-What do we offer and with whom, bla bla.
+_Coming soon_
-Support for minting Digital Object Identifiers (DOIs) with Crossref is built into Janeway's core.
+
diff --git a/content/support/images/activate-account.png b/content/support/images/activate-account.png
new file mode 100644
index 00000000..9da573d8
Binary files /dev/null and b/content/support/images/activate-account.png differ
diff --git a/content/support/images/active-toggle.png b/content/support/images/active-toggle.png
new file mode 100644
index 00000000..94457c20
Binary files /dev/null and b/content/support/images/active-toggle.png differ
diff --git a/content/support/images/article-archive-edit-metadata.png b/content/support/images/article-archive-edit-metadata.png
new file mode 100644
index 00000000..09daa294
Binary files /dev/null and b/content/support/images/article-archive-edit-metadata.png differ
diff --git a/content/support/images/article-identifiers.png b/content/support/images/article-identifiers.png
new file mode 100644
index 00000000..59e83cf0
Binary files /dev/null and b/content/support/images/article-identifiers.png differ
diff --git a/content/support/images/download-icon.png b/content/support/images/download-icon.png
new file mode 100644
index 00000000..428f4a70
Binary files /dev/null and b/content/support/images/download-icon.png differ
diff --git a/content/support/images/edit-icon.png b/content/support/images/edit-icon.png
new file mode 100644
index 00000000..4af8c8d0
Binary files /dev/null and b/content/support/images/edit-icon.png differ
diff --git a/content/support/images/edit-metadata.png b/content/support/images/edit-metadata.png
new file mode 100644
index 00000000..e82db500
Binary files /dev/null and b/content/support/images/edit-metadata.png differ
diff --git a/content/support/images/edit-user.png b/content/support/images/edit-user.png
new file mode 100644
index 00000000..2e8769c3
Binary files /dev/null and b/content/support/images/edit-user.png differ
diff --git a/content/support/images/forgotten_password.png b/content/support/images/forgotten-password.png
similarity index 100%
rename from content/support/images/forgotten_password.png
rename to content/support/images/forgotten-password.png
diff --git a/content/support/images/journal_users.png b/content/support/images/journal-users.png
similarity index 100%
rename from content/support/images/journal_users.png
rename to content/support/images/journal-users.png
diff --git a/content/support/images/logs-docs-more.png b/content/support/images/logs-docs-more.png
new file mode 100644
index 00000000..87a13306
Binary files /dev/null and b/content/support/images/logs-docs-more.png differ
diff --git a/content/support/images/logs-edit-metadata.png b/content/support/images/logs-edit-metadata.png
new file mode 100644
index 00000000..41dfc186
Binary files /dev/null and b/content/support/images/logs-edit-metadata.png differ
diff --git a/content/support/images/merge_users.gif b/content/support/images/merge-users.gif
similarity index 100%
rename from content/support/images/merge_users.gif
rename to content/support/images/merge-users.gif
diff --git a/content/support/images/press_all_users.png b/content/support/images/press-all-users.png
similarity index 100%
rename from content/support/images/press_all_users.png
rename to content/support/images/press-all-users.png
diff --git a/content/support/images/preview-icon.png b/content/support/images/preview-icon.png
new file mode 100644
index 00000000..189f4d01
Binary files /dev/null and b/content/support/images/preview-icon.png differ
diff --git a/content/support/images/profile-dropdown.png b/content/support/images/profile-dropdown.png
new file mode 100644
index 00000000..3b498ad2
Binary files /dev/null and b/content/support/images/profile-dropdown.png differ
diff --git a/content/support/images/repositories/repo-additional-fields.png b/content/support/images/repositories/repo-additional-fields.png
new file mode 100644
index 00000000..eff1e240
Binary files /dev/null and b/content/support/images/repositories/repo-additional-fields.png differ
diff --git a/content/support/images/repositories/repo-author-dash.png b/content/support/images/repositories/repo-author-dash.png
new file mode 100644
index 00000000..8660e4c9
Binary files /dev/null and b/content/support/images/repositories/repo-author-dash.png differ
diff --git a/content/support/images/repositories/repo-awaiting-moderation.png b/content/support/images/repositories/repo-awaiting-moderation.png
new file mode 100644
index 00000000..32514997
Binary files /dev/null and b/content/support/images/repositories/repo-awaiting-moderation.png differ
diff --git a/content/support/images/repositories/repo-edit-dash.png b/content/support/images/repositories/repo-edit-dash.png
new file mode 100644
index 00000000..2fce2721
Binary files /dev/null and b/content/support/images/repositories/repo-edit-dash.png differ
diff --git a/content/support/images/repositories/repo-licences.png b/content/support/images/repositories/repo-licences.png
new file mode 100644
index 00000000..7f312b77
Binary files /dev/null and b/content/support/images/repositories/repo-licences.png differ
diff --git a/content/support/images/repositories/repo-manager.png b/content/support/images/repositories/repo-manager.png
new file mode 100644
index 00000000..78041b0e
Binary files /dev/null and b/content/support/images/repositories/repo-manager.png differ
diff --git a/content/support/images/repositories/repo-parent-child-subject.png b/content/support/images/repositories/repo-parent-child-subject.png
new file mode 100644
index 00000000..3e2c17ad
Binary files /dev/null and b/content/support/images/repositories/repo-parent-child-subject.png differ
diff --git a/content/support/images/repositories/repo-preprint-controls.png b/content/support/images/repositories/repo-preprint-controls.png
new file mode 100644
index 00000000..f82cbef7
Binary files /dev/null and b/content/support/images/repositories/repo-preprint-controls.png differ
diff --git a/content/support/images/repositories/repo-pub-controls.png b/content/support/images/repositories/repo-pub-controls.png
new file mode 100644
index 00000000..9f0a9535
Binary files /dev/null and b/content/support/images/repositories/repo-pub-controls.png differ
diff --git a/content/support/images/repositories/repo-recommendations.png b/content/support/images/repositories/repo-recommendations.png
new file mode 100644
index 00000000..5c8bea63
Binary files /dev/null and b/content/support/images/repositories/repo-recommendations.png differ
diff --git a/content/support/images/repositories/repo-settings.png b/content/support/images/repositories/repo-settings.png
new file mode 100644
index 00000000..fa5a0178
Binary files /dev/null and b/content/support/images/repositories/repo-settings.png differ
diff --git a/content/support/images/repositories/repo-subjects.png b/content/support/images/repositories/repo-subjects.png
new file mode 100644
index 00000000..3b3d5f0b
Binary files /dev/null and b/content/support/images/repositories/repo-subjects.png differ
diff --git a/content/support/images/repositories/repo-submit-author-dash.png b/content/support/images/repositories/repo-submit-author-dash.png
new file mode 100644
index 00000000..fbf5e855
Binary files /dev/null and b/content/support/images/repositories/repo-submit-author-dash.png differ
diff --git a/content/support/images/repositories/repo-submit-frontend.png b/content/support/images/repositories/repo-submit-frontend.png
new file mode 100644
index 00000000..fcd4e41f
Binary files /dev/null and b/content/support/images/repositories/repo-submit-frontend.png differ
diff --git a/content/support/images/repositories/repo-submit-profile-backend.png b/content/support/images/repositories/repo-submit-profile-backend.png
new file mode 100644
index 00000000..fbedf9d2
Binary files /dev/null and b/content/support/images/repositories/repo-submit-profile-backend.png differ
diff --git a/content/support/images/repositories/repo-update-article.png b/content/support/images/repositories/repo-update-article.png
new file mode 100644
index 00000000..01364caa
Binary files /dev/null and b/content/support/images/repositories/repo-update-article.png differ
diff --git a/content/support/images/repositories/repo-version-moderation.png b/content/support/images/repositories/repo-version-moderation.png
new file mode 100644
index 00000000..12c53198
Binary files /dev/null and b/content/support/images/repositories/repo-version-moderation.png differ
diff --git a/content/support/images/repositories/repos-add-new.png b/content/support/images/repositories/repos-add-new.png
new file mode 100644
index 00000000..b960363c
Binary files /dev/null and b/content/support/images/repositories/repos-add-new.png differ
diff --git a/content/support/images/search-inactive.png b/content/support/images/search-inactive.png
new file mode 100644
index 00000000..953064e1
Binary files /dev/null and b/content/support/images/search-inactive.png differ
diff --git a/content/support/images/update-metadata.png b/content/support/images/update-metadata.png
new file mode 100644
index 00000000..372e14a3
Binary files /dev/null and b/content/support/images/update-metadata.png differ
diff --git a/content/support/images/upload-icon.png b/content/support/images/upload-icon.png
new file mode 100644
index 00000000..6a65e52c
Binary files /dev/null and b/content/support/images/upload-icon.png differ
diff --git a/content/support/images/workflow/author-article-files.png b/content/support/images/workflow/author-article-files.png
index 66d1814f..162b098f 100644
Binary files a/content/support/images/workflow/author-article-files.png and b/content/support/images/workflow/author-article-files.png differ
diff --git a/content/support/images/workflow/author-proofing-task.png b/content/support/images/workflow/author-proofing-task.png
new file mode 100644
index 00000000..cb8f12f8
Binary files /dev/null and b/content/support/images/workflow/author-proofing-task.png differ
diff --git a/content/support/images/workflow/author-proofreading.png b/content/support/images/workflow/author-proofreading.png
index b83e99a5..676f0a31 100644
Binary files a/content/support/images/workflow/author-proofreading.png and b/content/support/images/workflow/author-proofreading.png differ
diff --git a/content/support/images/workflow/author-submission-navigation.png b/content/support/images/workflow/author-submission-navigation.png
index 60e8b637..604cd1c1 100644
Binary files a/content/support/images/workflow/author-submission-navigation.png and b/content/support/images/workflow/author-submission-navigation.png differ
diff --git a/content/support/images/workflow/copyedit-complete-kanban.png b/content/support/images/workflow/copyedit-complete-kanban.png
index 5a566044..31a673df 100644
Binary files a/content/support/images/workflow/copyedit-complete-kanban.png and b/content/support/images/workflow/copyedit-complete-kanban.png differ
diff --git a/content/support/images/workflow/copyedit-page.png b/content/support/images/workflow/copyedit-page.png
index 4c25ab2c..ed1eaa6d 100644
Binary files a/content/support/images/workflow/copyedit-page.png and b/content/support/images/workflow/copyedit-page.png differ
diff --git a/content/support/images/workflow/copyedit-reopened-kanban.png b/content/support/images/workflow/copyedit-reopened-kanban.png
index 41378dc6..3e0fd5e3 100644
Binary files a/content/support/images/workflow/copyedit-reopened-kanban.png and b/content/support/images/workflow/copyedit-reopened-kanban.png differ
diff --git a/content/support/images/workflow/copyeditor-dashboard.png b/content/support/images/workflow/copyeditor-dashboard.png
index 1ee8ed2d..ec46c7ee 100644
Binary files a/content/support/images/workflow/copyeditor-dashboard.png and b/content/support/images/workflow/copyeditor-dashboard.png differ
diff --git a/content/support/images/workflow/copyeditor-requests.png b/content/support/images/workflow/copyeditor-requests.png
index ee930b85..738b3e34 100644
Binary files a/content/support/images/workflow/copyeditor-requests.png and b/content/support/images/workflow/copyeditor-requests.png differ
diff --git a/content/support/images/workflow/editor-copyedit-add-assignment.png b/content/support/images/workflow/editor-copyedit-add-assignment.png
new file mode 100644
index 00000000..a4147a62
Binary files /dev/null and b/content/support/images/workflow/editor-copyedit-add-assignment.png differ
diff --git a/content/support/images/workflow/editor-copyedit-review-page.png b/content/support/images/workflow/editor-copyedit-review-page.png
new file mode 100644
index 00000000..e41abf3f
Binary files /dev/null and b/content/support/images/workflow/editor-copyedit-review-page.png differ
diff --git a/content/support/images/workflow/editor-copyedit-review.png b/content/support/images/workflow/editor-copyedit-review.png
new file mode 100644
index 00000000..d590c8f5
Binary files /dev/null and b/content/support/images/workflow/editor-copyedit-review.png differ
diff --git a/content/support/images/workflow/editor-draft-decision-button.png b/content/support/images/workflow/editor-draft-decision-button.png
new file mode 100644
index 00000000..086827c0
Binary files /dev/null and b/content/support/images/workflow/editor-draft-decision-button.png differ
diff --git a/content/support/images/workflow/editor-draft-decision-edit.png b/content/support/images/workflow/editor-draft-decision-edit.png
new file mode 100644
index 00000000..47c65a29
Binary files /dev/null and b/content/support/images/workflow/editor-draft-decision-edit.png differ
diff --git a/content/support/images/workflow/editor-draft-decision-final.png b/content/support/images/workflow/editor-draft-decision-final.png
new file mode 100644
index 00000000..a91fa758
Binary files /dev/null and b/content/support/images/workflow/editor-draft-decision-final.png differ
diff --git a/content/support/images/workflow/editor-draft-decision-screen.png b/content/support/images/workflow/editor-draft-decision-screen.png
new file mode 100644
index 00000000..6fdc9386
Binary files /dev/null and b/content/support/images/workflow/editor-draft-decision-screen.png differ
diff --git a/content/support/images/workflow/editor-draft-decision.png b/content/support/images/workflow/editor-draft-decision.png
new file mode 100644
index 00000000..0d512d4d
Binary files /dev/null and b/content/support/images/workflow/editor-draft-decision.png differ
diff --git a/content/support/images/workflow/editor-review-add-reviewer.png b/content/support/images/workflow/editor-review-add-reviewer.png
new file mode 100644
index 00000000..2cbf8d40
Binary files /dev/null and b/content/support/images/workflow/editor-review-add-reviewer.png differ
diff --git a/content/support/images/workflow/editor-review-answer-visibility.png b/content/support/images/workflow/editor-review-answer-visibility.png
new file mode 100644
index 00000000..207a9640
Binary files /dev/null and b/content/support/images/workflow/editor-review-answer-visibility.png differ
diff --git a/content/support/images/workflow/editor-review-awaiting-acknowledgement.png b/content/support/images/workflow/editor-review-awaiting-acknowledgement.png
new file mode 100644
index 00000000..c8776095
Binary files /dev/null and b/content/support/images/workflow/editor-review-awaiting-acknowledgement.png differ
diff --git a/content/support/images/workflow/editor-review-decision-helper-share-reviews.png b/content/support/images/workflow/editor-review-decision-helper-share-reviews.png
new file mode 100644
index 00000000..ff256048
Binary files /dev/null and b/content/support/images/workflow/editor-review-decision-helper-share-reviews.png differ
diff --git a/content/support/images/workflow/editor-review-decision-helper.png b/content/support/images/workflow/editor-review-decision-helper.png
new file mode 100644
index 00000000..a51e26a4
Binary files /dev/null and b/content/support/images/workflow/editor-review-decision-helper.png differ
diff --git a/content/support/images/workflow/editor-review-setup.png b/content/support/images/workflow/editor-review-setup.png
new file mode 100644
index 00000000..1874db3c
Binary files /dev/null and b/content/support/images/workflow/editor-review-setup.png differ
diff --git a/content/support/images/workflow/editor-share-review-bulk.png b/content/support/images/workflow/editor-share-review-bulk.png
new file mode 100644
index 00000000..ccc0ddd3
Binary files /dev/null and b/content/support/images/workflow/editor-share-review-bulk.png differ
diff --git a/content/support/images/workflow/editor-share-review-individual.png b/content/support/images/workflow/editor-share-review-individual.png
new file mode 100644
index 00000000..4a525fca
Binary files /dev/null and b/content/support/images/workflow/editor-share-review-individual.png differ
diff --git a/content/support/images/workflow/editor-share-review.png b/content/support/images/workflow/editor-share-review.png
new file mode 100644
index 00000000..2ec8cc0f
Binary files /dev/null and b/content/support/images/workflow/editor-share-review.png differ
diff --git a/content/support/images/workflow/editor-typesetting-actions.png b/content/support/images/workflow/editor-typesetting-actions.png
new file mode 100644
index 00000000..b03ab7bd
Binary files /dev/null and b/content/support/images/workflow/editor-typesetting-actions.png differ
diff --git a/content/support/images/workflow/editor-typesetting-assign-proofreader.png b/content/support/images/workflow/editor-typesetting-assign-proofreader.png
new file mode 100644
index 00000000..7873d185
Binary files /dev/null and b/content/support/images/workflow/editor-typesetting-assign-proofreader.png differ
diff --git a/content/support/images/workflow/editor-typesetting-assign-typesetter.png b/content/support/images/workflow/editor-typesetting-assign-typesetter.png
new file mode 100644
index 00000000..fce517f3
Binary files /dev/null and b/content/support/images/workflow/editor-typesetting-assign-typesetter.png differ
diff --git a/content/support/images/workflow/editor-typesetting-choice.png b/content/support/images/workflow/editor-typesetting-choice.png
new file mode 100644
index 00000000..0bddb8f5
Binary files /dev/null and b/content/support/images/workflow/editor-typesetting-choice.png differ
diff --git a/content/support/images/workflow/editor-typesetting-edit-galley.png b/content/support/images/workflow/editor-typesetting-edit-galley.png
new file mode 100644
index 00000000..7ecb98e9
Binary files /dev/null and b/content/support/images/workflow/editor-typesetting-edit-galley.png differ
diff --git a/content/support/images/workflow/editor-typesetting-enroll-proofreader.png b/content/support/images/workflow/editor-typesetting-enroll-proofreader.png
new file mode 100644
index 00000000..3c8c12d6
Binary files /dev/null and b/content/support/images/workflow/editor-typesetting-enroll-proofreader.png differ
diff --git a/content/support/images/workflow/editor-typesetting-files-blocks.png b/content/support/images/workflow/editor-typesetting-files-blocks.png
new file mode 100644
index 00000000..f144b96c
Binary files /dev/null and b/content/support/images/workflow/editor-typesetting-files-blocks.png differ
diff --git a/content/support/images/workflow/editor-typesetting-galley-buttons.png b/content/support/images/workflow/editor-typesetting-galley-buttons.png
new file mode 100644
index 00000000..6a40b590
Binary files /dev/null and b/content/support/images/workflow/editor-typesetting-galley-buttons.png differ
diff --git a/content/support/images/workflow/editor-typesetting-imagefiles-image.png b/content/support/images/workflow/editor-typesetting-imagefiles-image.png
new file mode 100644
index 00000000..c0aab45c
Binary files /dev/null and b/content/support/images/workflow/editor-typesetting-imagefiles-image.png differ
diff --git a/content/support/images/workflow/editor-typesetting-imagefiles-zipfile.png b/content/support/images/workflow/editor-typesetting-imagefiles-zipfile.png
new file mode 100644
index 00000000..f5b110aa
Binary files /dev/null and b/content/support/images/workflow/editor-typesetting-imagefiles-zipfile.png differ
diff --git a/content/support/images/workflow/editor-typesetting-options.png b/content/support/images/workflow/editor-typesetting-options.png
new file mode 100644
index 00000000..efea820d
Binary files /dev/null and b/content/support/images/workflow/editor-typesetting-options.png differ
diff --git a/content/support/images/workflow/editor-typesetting-review-typesetting-decision.png b/content/support/images/workflow/editor-typesetting-review-typesetting-decision.png
new file mode 100644
index 00000000..52259c99
Binary files /dev/null and b/content/support/images/workflow/editor-typesetting-review-typesetting-decision.png differ
diff --git a/content/support/images/workflow/editor-typesetting-review-typesetting.png b/content/support/images/workflow/editor-typesetting-review-typesetting.png
new file mode 100644
index 00000000..b10b40c6
Binary files /dev/null and b/content/support/images/workflow/editor-typesetting-review-typesetting.png differ
diff --git a/content/support/images/workflow/editor-typesetting-rounds.png b/content/support/images/workflow/editor-typesetting-rounds.png
new file mode 100644
index 00000000..a3cb3a22
Binary files /dev/null and b/content/support/images/workflow/editor-typesetting-rounds.png differ
diff --git a/content/support/images/workflow/editor-typesetting-upload-new-typeset-file.png b/content/support/images/workflow/editor-typesetting-upload-new-typeset-file.png
new file mode 100644
index 00000000..1adead8c
Binary files /dev/null and b/content/support/images/workflow/editor-typesetting-upload-new-typeset-file.png differ
diff --git a/content/support/images/workflow/reviewer-block.png b/content/support/images/workflow/reviewer-block.png
index bf3d2246..820f872a 100644
Binary files a/content/support/images/workflow/reviewer-block.png and b/content/support/images/workflow/reviewer-block.png differ
diff --git a/content/support/images/workflow/reviewer-file-upload.png b/content/support/images/workflow/reviewer-file-upload.png
index 1dd02175..8008b383 100644
Binary files a/content/support/images/workflow/reviewer-file-upload.png and b/content/support/images/workflow/reviewer-file-upload.png differ
diff --git a/content/support/images/workflow/reviewer-kanban.png b/content/support/images/workflow/reviewer-kanban.png
index eaadd4d7..a7c3fe7d 100644
Binary files a/content/support/images/workflow/reviewer-kanban.png and b/content/support/images/workflow/reviewer-kanban.png differ
diff --git a/content/support/images/workflow/reviewer-review-files.png b/content/support/images/workflow/reviewer-review-files.png
index 97ad0aa5..6486e73f 100644
Binary files a/content/support/images/workflow/reviewer-review-files.png and b/content/support/images/workflow/reviewer-review-files.png differ
diff --git a/content/support/issues-volumes-and-collections/issues-and-volumes.md b/content/support/issues-volumes-and-collections/issues-and-volumes.md
index 70ee7531..67f4f403 100644
--- a/content/support/issues-volumes-and-collections/issues-and-volumes.md
+++ b/content/support/issues-volumes-and-collections/issues-and-volumes.md
@@ -2,39 +2,38 @@ title: Issues
# Issues
-On Janeway, issues organise articles for publication. While articles do not have to be part of an issue, some external services (such as Crossref) require that articles be assigned to an issue. As such, it is recommended to use issues where possible.
-If your journal uses continuous publication, it is recommended to create yearly issues to add articles to.
+On Janeway, issues organise articles for publication. While articles do not have to be part of an issue, some external services (such as Crossref) require that articles be assigned to an issue. As such, we recommend using issues where possible. If your journal uses continuous publication, we recommend creating yearly issues to add articles to.
Articles are typically assigned to issues during the **Pre-publication** stage, but can be assigned a projected issue at any point in the publication workflow. Issues can also be managed independently through the **Issue manager**, available from both the **Manager** page and the main sidebar.
## Issue types
-Janeway provides two built-in issue types :
+Janeway provides two built-in issue types:
- **Issue**
The standard publication issue.
- **Collection**
- Can be used to group related articles across volumes or years.
+ Used to group related articles across volumes or years.
## Volumes
-Issues will automatically be assigned to a volume. They can either have their own volume or share a volume with other issues (e.g., volume 1 - issue 1, volume 1 - issue 2, etc.).
+Issues are automatically assigned to a volume. They can either have their own volume or share a volume with other issues (for example, Volume 1 - Issue 1, Volume 1 – Issue 2).
-You can use volume 0 for (ongoing) thematic collections - especially those that are not tied to a specific year or publication sequence. Using volume 0 will also ensure they do not interrupt the listings of regular issues on the issue page.
+You can use Volume 0 for ongoing thematic collections — especially those that are not tied to a specific year or publication sequence. Using Volume 0 also ensures they do not interrupt the listings of regular issues on the issue page.
> [!NOTE]
> If no volume and issue numbers are specified when importing articles, they will be assigned to volume 0 issue 0. For this reason, it is recommended to avoid using volume 0 issue 0, as this may create duplicates when importing. This in turn can cause problems.
## Issue manager
-Articles are typically assigned to issues during the pre-publication stage. However, issues can also be managed independently through the **Issue manager**, accessible from both the manager page and the main sidebar. This page lists all existing issues and provides options for creating, editing, reordering, and managing them.
+This page lists all existing issues and provides options for creating, editing, reordering, and managing them.
-Using this page, you can perform the following general actions:
+From this page, you can perform the following actions:
- **Sort by date descending / ascending**
- Reorder issues by publication date. Sorting changes the display order of issues on the public site, and changes take effect immediately.
+ Reorders issues by publication date. Sorting changes the display order of issues on the public site, and changes take effect immediately.
- **Edit display settings**
Opens configuration options for how issue titles and metadata are displayed. For more information, see [Display settings](#display-settings).
@@ -51,7 +50,7 @@ In addition, the issue list is presented in a table format. For each issue, the
- **Make current** 
Sets the selected issue as the journal’s current issue. The current issue does not display this button.
-You can also drag and drop issues to manually change their order; the new order updates the public display immediately. You can also view publication data such as volume, issue number, publication date, and number of articles directly from the table.
+You can also drag and drop issues to manually change their order; the new order updates the public display immediately. You can view publication data such as volume, issue number, publication date, and number of articles directly from the table.
## Creating and editing issue details
diff --git a/content/support/journal-management/cache-temp.md b/content/support/journal-management/cache-temp.md
index 112e3730..9fcfcf03 100644
--- a/content/support/journal-management/cache-temp.md
+++ b/content/support/journal-management/cache-temp.md
@@ -2,7 +2,6 @@ title: Clearing the cache
# Clearing the cache
-Janeway uses a cache to speed up page loading, you can reset the cache
-from the Manager page by clicking the Clear Cache button.
+Janeway uses a cache to speed up page loading. You can reset the cache from the Manager page by clicking the **Clear cache** button.
-
+
+If an item does not have a large image:
+
+1. Janeway will use the default large image configured in **Images**.
+2. If no default image is configured, the system will fall back to the server default image.
+
+For best results, ensure items included in the carousel have suitable large images set. See **Image guidelines** for recommendations.
+
+## Exclude option
+
+The **Exclude** tickbox changes how the selection lists behave.
+
+- **Disabled (default):**
+ The selected items are **included** in the carousel.
+
+- **Enabled:**
+ The selected items are **excluded** from the carousel.
+
+
+
+## Selecting items for the carousel
+
+When selecting specific content for the carousel, Janeway uses a two-column interface:
+
+- **Available** (left column)
+- **Chosen** (right column)
+
+To include an item in the carousel, select it in **Available** and click the **right-facing arrow** to move it to **Chosen**.
+
+To remove an item, select it in **Chosen** and click the **left-facing arrow**.
+
+Buttons below each column allow you to **Select all** or **Remove all** items.
+
+
+
+### Articles
+
+Articles can be added automatically or selected manually.
+
+To show recent articles automatically, enable **Latest articles** and set the **Maximum number of articles** to display. For example, if **Latest articles** is enabled and the maximum is 4, the carousel will display the four most recently published articles.
+
+If you prefer to curate the carousel manually, move articles from **Available** to **Chosen** using the selection interface.
+
+### News
+
+Enable **Latest news** to automatically display recent announcements, and set the **Maximum number** of items to include Alternatively, you can manually select specific news items using the selector interface described above.
+
+### Issues and collections
+
+Issues and collections behave the same as articles and news in the carousel. However, instead of the option to show multiple recent issues, is has the option to enable **Current issue** to display the issue currently marked as current.
+
+> [!TIP]
+> If changes are not appearing on the homepage, trying clearing the cache.
+
+## Image contrast and carousel overlays
+
+In the carousel, Janeway will display a low-opacity grey overlay on top of the image. This is used to improve the contrast between the image and the text displayed over it (such as the article or news title).
+
+As a result, the image may appear darker than the original file and/or less vivid than expected. This does _not_ necessarily mean there is a problem with the uploaded image, but may cause issues if you have a strict housestyle.
+
+### Removing the overlay
+
+The overlay can be changed or removed through CSS styling (see Custom styling ). However, this should only be done with care.
+
+> [!WARNING]
+> Before removing or reducing the overlay, make sure the text remains clearly readable against the image.
+
+By default, carousel text is white, so removing the overlay may make text difficult to read if the image is pale, bright, or low-contrast.
+
+If you are using custom text colours or disable the overlay, make sure there is still sufficient contrast between the text and the background image.
+
+### Good practice
+
+- Keep the overlay if your carousel images vary in brightness.
+- Test carousel slides with both light and dark images.
+- Avoid using very pale or very busy images behind text unless you have checked accessibility impact.
+- If editing the CSS, review the carousel on mobile as well as desktop.
diff --git a/content/support/journal-management/cms.md b/content/support/journal-management/cms.md
index 4b060248..f6242496 100644
--- a/content/support/journal-management/cms.md
+++ b/content/support/journal-management/cms.md
@@ -2,37 +2,48 @@ title: Janeway content manager
# Janeway content manager
-The Content Manager is Janeway's CMS. Pages can be created and edited using our rich text editor.
+The **Content manager** provides access to Janeway’s built-in content management system (CMS). It allows you to create and edit static pages for your journal, such as privacy notices, policies, or "About" pages, using a rich-text editor.
-
+
-## Add a New Page
+## Add a new page
-To add a new page to your journal select "+ Add New Page" and fill in the fields as detailed in the text beneath each field.
+To add a new page to your journal website, click **+ Add new page** and fill in the fields as detailed in their helptexts.
+
+For information on embedding media files within a page, see Media files .
-The URL for the page will be generated with these parts:
+Pages are immediately public after saving them.
+
+### Page URLs
+
+When you create a new page, Janeway automatically generates its URL using the following parts:
+
+- Your journal’s domain name (for example, `orbit.openlibhums.org`).
+- The path element `/site/`, which is used as a namespace for custom pages.
+- The value entered in the **Link** field.
+
+An example: `https://orbit.openlibhums.org/site/privacy`
+
+For information on adding new pages to your site navigation, see **Navigation**.
-- Your journal's domain name (e.g. orbit.openlibhums.org)
-- The path element “site” (a namespace for custom pages)
-- The path you entered in the **Link** field.
+
-An example:
+## Edit a page
-
-
+The content manager displays a list of all custom pages currently available on your journal. Click **Edit** to make changes.
-## Edit a Page
+Changes take effect immediately once saved. If you do not see them displayed on the journal page, you may need to refresh your cache.
-From the Content page you can see a list of the pages currently on your journal. Select Edit to make changes.
+You can see a page's editing history by clicking **View history** at the bottom of the edit page.
-###Delete a Page
+### Delete a page
-To delete a page use the red Delete button.
+To delete a page use the **Delete** button, on the content manager page.
> [!WARNING]
-> Data cannot be recovered so ensure you really want to remove a page before pressing the delete button.
+> Deleted pages cannot be recovered. Make sure you no longer need the page before deleting it.
diff --git a/content/support/journal-management/editorial-team.md b/content/support/journal-management/editorial-team.md
index 0bd6ff32..0575b993 100644
--- a/content/support/journal-management/editorial-team.md
+++ b/content/support/journal-management/editorial-team.md
@@ -2,52 +2,72 @@ title: Editorial team
# Editorial team
-
-
+The Editorial team interface allows you to create and manage the groups displayed on your journal’s **Editorial team** page. It is accessed from the **Manager dashboard**, under **Content**.
-The Editorial Team interface is relatively complex and is made up of:
+On this page you can:
-- Editorial Groups
-- Editorial Group Members
+- Add and delete editorial groups.
+- Edit groups' details and manage members.
+- Configure the display name for the editorial team page.
+- Configure settings related to the display of editorial groups.
-You can create as many groups as you like and add as many members as you like.
+There is no limit on the number of editorial groups you can create or how many members they can contain.
-When you access the interface the form for making a new group is displayed on the right of the page and the existing groups listed on the left. For each group you can:
-
-- Edit the membership
-- Edit the group details
-- Delete the group
-- Drag and drop to re-order them
+Adding someone to an editorial group does not assign them the editor role and it does not affect the permissions given to a user. Editorial groups are used for display purposes only.
-> [!TIP]
-> The Group description field supports HTML and presents a rich-text editor. If you do not wish to add an account for each user you can simply list them in the rich text box using, for example, a bulleted list.
-
-## Adding a New Group
+## Creating a new group
Creating a new group allows you to add members and display them on the Editorial Team page. Each group is headed by the group name you supply.
-- Name
- - The group name, e.g. Editorial Team or Advisors.
+- Name
+ The group name, e.g. "Editorial team" or "Advisors".
-- Description
- - Displayed under the Name header on the Editorial Team page.
+- Description
+ Displayed under the group name on the editorial team page. This field supports rich text and can be used to add additional information about the group.
-- Sequence
- - The order in which the groups should be displayed. You can reorder the groups by editing their sequence or by dragging and dropping their record.
+- Sequence
+ Controls the order in which groups appear on the page. You can reorder the groups by editing their sequence number or by dragging and dropping them in the list.
-## Adding Members to a Group
+## Editing a group
-For an existing or newly created group you can use the Edit Members button (Green with a group of outlines) to change the membership of the group.
+To edit an existing group, click the **Edit members** button.
-On the left is a list of the current members, you can:
+On the left-hand side, you will see a list of current group members. From here you can:
+
+- Remove a member from the group.
+- Reorder members using drag and drop.
+
+To add someone to an editorial team, they need to have a Janeway account. A list of available journal users will be visible on the right-hand side of the page. You can search this list and use the **Add** button to include a user in the group.
+
+If someone does not have an account yet, you can either invite them to create an account or create one on their behalf by clicking **Add new user**.
+
+If you are setting up a group where multiple users do not have accounts yet, you may wish to use the editorial team import process instead. This process allows you to create editorial groups where the members do not yet have accounts.
+
+Alternatively, if you do not want to create a Janeway account for every individual, you can list names directly in the **Group description** box. This field supports HTML and uses a rich-text editor, so you ccould list the editors using formatted text (for example, a bulleted list).
+
+## Editorial group display settings
+
+The following settings control how editorial groups and members are displayed on the editorial team page.
+
+- Editorial group page name
+ The display name of the page that lists your editorial groups.
+
+- Hide editorial group names
+ When enabled, group names are not shown on the editorial team page.
+
+- Enable multi-page editorial team display
+ When enabled, each editorial group is displayed on its own page. This setting is overwitten by **Enable editorial team display**.
-- Delete a member from the group
-- Reorder the members by dragging and dropping a listing
+> [!NOTE]
+> **Enable editorial team display** is found in **All settings** and determines whether the editorial team page is available as a default option for the navbar (which presumes a single page for the editorial team).
-Journal users are listed on the right and you can add a user to the group using the _Add_ button. If a user account does not exist for the user you can use the _Add New User_ button to add them.
+
+- Display Country on Editorial Team Page
+ When enabled, and where a group member has set a country on their user profile, the country will be displayed next to their name.
+ If no country is set, nothing is shown.
+ -->
diff --git a/content/support/journal-management/form-elements.md b/content/support/journal-management/form-elements.md
index 59577020..1c1d021e 100644
--- a/content/support/journal-management/form-elements.md
+++ b/content/support/journal-management/form-elements.md
@@ -6,52 +6,63 @@ Custom forms in Janeway have the following aspects to them yada yada.
-- Name
- - This field provides the name of the submission element
- In case of a short question, you could put a question in this field. If using a longer question, you may wish to use a more generic description and provide further guidance in the help text.
+- Name
+ This field provides the name of the element.
+ In case of a short question, you could put a question in this field. If using a longer question, you may wish to use a more generic description and provide further guidance in the help text.
-- Kind
- - blabla kinds yada yada I am so tired besties.
+- Kind
+ This determines the type of element, e.g., text field, checkbox, dropdown etc. For an overview of element types available, see Element types
-- Required
- - Check this setting’s box to make this part of the form obligatory to complete.
+- Required
+ Check this setting’s box to make this part of the form obligatory to complete.
-- Order
- - This determines the order of elements on the submission form.
+- Order
+ This determines the order of elements on the form.
-- Help text
- - This text will display under the submission element and can provide further guidance or information for authors.
+- Help text
+ This text will display under the form element and can provide further guidance or information for authors.
-- Default visibility
- - If enabled, this element will be visible to the author by default once the editor has shared the review with them. If disabled, the author will not see this element unless the editor overrides it.
+- Default visibility (review forms only)
+ If this box is ticked, the answer to this form element will be visible to the author by default once the editor has shared the review with them. If disabled, the author will not see this element unless the editor overrides it.
## Element types (kind)
-A submission form element can be one of the following kinds:
+A form element can be one of the following kinds:
+
+- Text field
+ This is a single-line input area for short text answers such as names, keywords or subjects. It does not allow for formatting.
-- Text field - This is a single-line input area for short text answers such as names, keywords or subjects. It does not allow for formatting.
-- Text area - This is a larger, multi-line input area for longer texts such as comments and descriptions. It allows for formatting and line breaks.
+- Text area
+ This is a larger, multi-line input area for longer texts such as comments and descriptions. It allows for formatting and line breaks.
+
-- Checkbox - This element asks users to check a box, which can be used to declare no competing interests / agree to terms, for example.
+- Checkbox
+ This element asks users to check a box, which can be used to declare no competing interests / agree to terms, for example.
+
-- Select (dropdown) - Shows a predefined list of options, allowing users to select one. You will need to create the options. This is done through the ‘Choices’ field. The options should be separated by the bar " | " character, e.g. " choice 1|choice 2|choice 2 ".
+- Select (dropdown)
+ Shows a predefined list of options, allowing users to select one. You will need to create the options. This is done through the ‘Choices’ field. The options should be separated by the bar " | " character, e.g. " choice 1|choice 2|choice 2 ".
+
-- Email
- - Specific text field for emails. It checks if the input looks like an email address. / follows the format of an email address.
- 
+- Email
+ Specific text field for emails. It checks if the input looks like an email address. / follows the format of an email address.
+
+ 
+
+- Upload
+ Asks the users to upload a file from their device.
+
+ 
-- Upload
- - Asks the users to upload a file from their device.
- 
+- Date
+ Asks the user to provide a date.
-- Date
- -Asks the user to provide a date.
> [!NOTE]
-> When using an element kind other than 'Select', you can ignore the ‘Choices’ field.
+> When using an element kind other than 'Select', you can ignore the 'Choices' field.
diff --git a/content/support/journal-management/homepage-layout.md b/content/support/journal-management/homepage-layout.md
index f7f40661..bbec6533 100644
--- a/content/support/journal-management/homepage-layout.md
+++ b/content/support/journal-management/homepage-layout.md
@@ -2,34 +2,46 @@ title: Homepage customisation
# Homepage customisation
-Here, you can activate features for your journal home page.
+The Homepage customisation settings allow you to control which features appear on your journal’s home page and how they are displayed.
+
+From this page, you can:
+
+- Enable or disable homepage features.
+- Configure the content of each feature.
+- Change the order in which features appear.
-To add a homepage element, select **Add** under **Add Home Page Features** and then select **Configure** to view its options. You can also reorder elements by dragging and dropping them.
+## Adding and managing homepage features
+
+To add a homepage element, select **Add** next to the feature you want to add. Once it has been added, click **Configure** to view its options. You can reorder elements by dragging and dropping them. To delete a homepage element, click the **Delete** icon.
+
+Any changes take effect immediately, if you do not see them you may need to clear your cache.
+
+## Homepage features
-- About
- - Displays the journal description. If you edit the description here, it will also change in the other places it appears.
+- About
+ Displays the journal description. If you edit the description here, it will also change in the other places it appears.
-- Carousel
- - A rotating banner that can be configured to display one of the following:
- - Latest articles
- - Latest news
- - A combination of both
+- Carousel
+ A rotating banner that can be configured to display one of the following:
+ - Latest articles.
+ - Latest news.
+ - A combination of both.
-You can select the number of items to display and the items you want to include or exclude.
+You can select the number of items to display and the items you want to include or exclude. For more information, see carousel configuration.
-- Current Issue
- - Takes whichever issue is marked as current and displays its table of contents on the home page. To learn how to select a current issue, check the issue page.
+- Current issue
+ Takes whichever issue is marked as current and displays its table of contents on the home page. To learn how to select a current issue, check the issue page.
-- Featured Articles
-- This option allows you to select a series of articles to display on the homepage. The selected articles are displayed in a grid, cascading onto a new line every three articles.
+- Featured articles
+ This option allows you to select a series of articles to display on the homepage. The selected articles are displayed in a grid, cascading onto a new line every three articles.
-- HTML
- - A generic segment that you can customize according to your needs. It can hold text and more complex HTML, such as a social media feed.
+- HTML
+ A generic segment that you can customize according to your needs. It can hold text and more complex HTML, such as a social media feed.
-- News
- - Displays a list of the most recent news items. You can configure the number of items to display (the default is 5).
+- News
+ Displays a list of the most recent news items. You can configure the number of items to display (the default is 5).
-- Popular Articles
- - Displays the most-accessed articles. You can configure the number of items and how recent the articles should be.
+- Popular articles
+ Displays the most-accessed articles. You can configure the number of items and how recent the articles should be.
diff --git a/content/support/journal-management/journal-contacts.md b/content/support/journal-management/journal-contacts.md
index 2e40c539..3817307d 100644
--- a/content/support/journal-management/journal-contacts.md
+++ b/content/support/journal-management/journal-contacts.md
@@ -4,17 +4,17 @@ title: Journal contacts
You can control the contacts listing for your journal by adding and removing contacts through this interface. Only three fields are used for this:
-- Name
- - The contact's name.
+- Name
+ The contact's name.
-- Email
- - The email address that should be contacted.
+- Email
+ The email address that should be contacted.
-- Role
- - The contact's role, e.g. editor or reviewer.
+- Role
+ The contact's role, e.g. editor or reviewer.
-Each outgoing message is recorded in the database and can be viewed in the admin area by staff.
+ 
-
+Any contacts added will be contactable through a webform, but no email address will be displayed. Each incoming message sent through the contact form is recorded in the database and can be viewed in the admin area by staff.
-
+Contacts will also be listed on the contacts page, displaying a name and role. Any information added to the contacts field in general settings (such as a physical address) will also be added in this column.
diff --git a/content/support/journal-management/journal-management-index-placeholder.md b/content/support/journal-management/journal-management-index-placeholder.md
index 6e8becbf..a6306a69 100644
--- a/content/support/journal-management/journal-management-index-placeholder.md
+++ b/content/support/journal-management/journal-management-index-placeholder.md
@@ -1,3 +1,69 @@
title: Journal management
# Journal management
+
+This section brings together the tools and settings used to manage your journal’s website, content, and configuration in Janeway.
+
+From here you can customise the appearance of your journal site, manage editorial information, create pages and news items, and adjust system settings.
+
+Most of these tools are available from the Manager dashboard under **Content** or **Journal settings**.
+
+## Website content and pages
+
+These interfaces help you create and maintain the content that appears on your journal website, such as information pages, navigation links, and downloadable files.
+
+
+
+- Content manager
+ Create and edit static pages for your journal, such as About, Policies, or Privacy notices, using Janeway’s built-in content management system.
+
+- News manager
+ Create and publish news items on your journal website. News items can appear on the homepage or in the carousel.
+
+- Media files
+ Upload files such as author guidelines, templates, or other downloadable documents and embed links to them within your pages.
+
+- Navigation
+ Configure the journal’s navigation bar, including enabling built-in pages and creating custom navigation links.
+
+- Managing rich-text fields
+ Learn how Janeway’s rich-text editor works and how to avoid formatting issues when copying and pasting text from other applications.
+
+## Homepage customisation
+
+These settings control how your journal’s homepage elements are displayed.
+
+- Homepage elements
+ Configure homepage features such as the carousel, featured articles, popular articles, and other homepage components.
+
+- Carousel configuration
+ Additional guidance for configuring homepage carousel elements and troubleshooting common issues.
+
+- Journal images
+ Guidance on uploading and formatting images used across the journal website, including logos, cover images, and article images. See also: Image guidelines.
+
+## Editorial and contact information
+
+Use these interfaces to manage the people and contact details displayed on your journal website.
+
+- Editorial team
+ Create and manage editorial groups displayed on the Editorial team page, such as editors, advisory board members, or reviewers.
+
+- Journal contacts
+ Add and manage contacts that appear on the journal’s Contact page and receive messages through the contact form.
+
+## Journal configuration and integration
+
+- Journal settings
+ Set key journal details, configure email settings, and adjust various display and integration settings.
+
+- Image guidelines
+ Guidance on how and where images appear on the journal site, and image size guidelines.
+
+- Similarity checker
+ Configure the Crossref Similarity Check (iThenticate) integration for checking submitted manuscripts.
+
+- Clearing the cache
+ If recent changes are not appearing on your journal website, you may need to clear the system cache to refresh stored data.
+
+
diff --git a/content/support/journal-management/journal-settings.md b/content/support/journal-management/journal-settings.md
index a2895b05..49a0c467 100644
--- a/content/support/journal-management/journal-settings.md
+++ b/content/support/journal-management/journal-settings.md
@@ -6,13 +6,13 @@ In journal settings, you can set basic information about the journal, configure
If you have the Janeway role of editor or staff, you can access Journal Settings by selecting **Manager** under **Staff**.
-## All Settings
+## All settings
The All Settings page lists every underlying journal-level setting within Janeway and allows you to edit them. The setting groups are:
- Crossref
- Email
-- Email Subject
+- Email subject
- General
- Identifiers
- Preprints
diff --git a/content/support/journal-management/media-files.md b/content/support/journal-management/media-files.md
index 7ccf9a18..995624b5 100644
--- a/content/support/journal-management/media-files.md
+++ b/content/support/journal-management/media-files.md
@@ -2,16 +2,16 @@ title: Media files
# Media files
-The Media Files manager lets editors upload and host small files.
+The Media files manager lets editors upload and host small files, which can then have download links embedded within a page.
Examples include:
-- Author Guidelines
-- Proofing Guidelines
-- Article Submission Templates
+- Author guidelines
+- Proofing guidelines
+- Article submission templates
Once a file is uploaded a link is provided that you can then insert into CMS pages or templates.
> [!NOTE]
-> The Media Files section should not be used to upload videos unless you have sufficient storage space/bandwidth. If you use Janeway Hosting you should contact the support team.
+> The **Media files** should not be used to upload videos unless you have sufficient storage space/bandwidth. If you use Janeway hosting you should contact the support team.
diff --git a/content/support/journal-management/navigation.md b/content/support/journal-management/navigation.md
index dd3ba8b3..a5e06f77 100644
--- a/content/support/journal-management/navigation.md
+++ b/content/support/journal-management/navigation.md
@@ -2,30 +2,63 @@ title: Navigation
# Navigation
-The nav bar is made up of two kinds of items:
+A journal's navigation bar (navbar) is customised through the **Content manager**.
-- Fixed nav elements that you can turn on or off
-- Custom nav items that you can create and modify
+The navbar is made up of two types of items:
-Fixed nav elements include:
+- Fixed navigation elements that you can turn enable/disable.
+- Custom navigation items that you create yourself.
+
+Fixed navigation elements include:
- Home
- News
- Articles
- Issues
- Collections
-- Editorial Team
+- Editorial team
- Submissions
- Contact
-- Start Submission
-- Become a Reviewer
+- Start submission
+- Become a reviewer
+
+The default nav consists of a selection of enabled fixed navigation elements.
+
+
+
+To turn a fixed item on or off, click the **Enable** or **Disable** button next to it. The order of the fixed navigation elements cannot be edited directly. To see how to change the order of fixed navigation elements, see the section on **Modifying the navbar** following this section.
+
+## Modifying the navbar
+
+To add new, custom nav items or change the order of fixed nav items, click **Modify nav**.
+
+This interface has multiple fields:
+
+- Display name
+ The page title as it will display in the navigation bar.
+- Link
+ For internal pages hosted on Janeway, compare the URL of your home page with the URL of the page you wish to link to. Copy anything that comes after the main home page URL here. For page options which are provided by Janeway, this will likely be "/page-name" or "journalcode/page-name" (e.g. "/articles" or "journalcode/articles"). For custom pages you have created, this will likely be "/site/page-name" or "journalcode/site/page-name".
-To add a new custom nav item, from the content manager page, select
-"Edit Nav" and fill in the fields as desired. Details of how each field
-works are displayed below the field.
+ For external pages, this will be the full URL of the site or page you want to link to.
+ If you want to create a header for a dropdown on your navigation bar that doesn't also appear as a link in that dropdown, leave this field blank.
+
+- Is external
+ Tick this box if you want to link to an external web page.
+- Sequence
+ This controls the order in which custom items on your navigation bar appear in relation to one another.
+- Has subnavigation
+ Tick this box if you want to create a drop-down in your navigation bar from this item.
+- Top-level nav item
+ If you want this link to fall under an existing drop-down in your navigation bar, select which one it should fall under.
+The built-in page options provided by Janeway cannot be reordered directly. To reorder these pages, use 'Create a new nav item' to create a more customisable link to that page, following the same steps as you would for adding other pages to your nav bar, and disable the Janeway default version."
+
+
+
+For footer navigation, see footer navigation . This is only available at press level/
+
## Footer Navigation
With some themes, you can put a navigation link in the footer rather
@@ -58,5 +91,3 @@ No longer on this page:
- Enable Multi Page Editorial Team (splits the editorial team into pages
by Group)
-->
-
-
diff --git a/content/support/journal-management/news-manager.md b/content/support/journal-management/news-manager.md
index 86f5e586..b3a79b2d 100644
--- a/content/support/journal-management/news-manager.md
+++ b/content/support/journal-management/news-manager.md
@@ -6,34 +6,34 @@ The news manager allows you to create news items, assign them start- and end dat
News items can also displayed in the carousel.
-To add a new news item, select the _News Manager_. The interface displays existing news items on the left and a form for adding new items on the right.
+To add a new news item, select the **News manager**. The interface displays existing news items on the left and a form for adding new items on the right.
The form fields include:
-- Title
- - The title of the news item.
+- Title
+ The title of the news item.
-- Body
- - The HTML body of the news item.
+- Body
+ The HTML body of the news item.
-- Start display
- - The date to start displaying this news item.
+- Start display
+ The date to start displaying this news item.
-- End display
- - The date to stop displaying this news item (can be left blank to display indefinitely).
+- End display
+ The date to stop displaying this news item (can be left blank to display indefinitely).
-- Sequence
- - Use for sorting when news items are posted on the same day.
+- Sequence
+ Use for sorting when news items are posted on the same day.
-- Image file
- - An image file to fit the news piece; ensure you have the right to post it.
+- Image file
+ An image file to fit the news piece; ensure you have the right to post it.
-- Custom Byline
- - Lets you overwrite the name displayed as the author of the news item.
+- Custom byline
+ Lets you overwrite the name displayed as the author of the news item.
-- Tags
- - A series of tags/keywords for the piece, you can filter news items by tags.
+- Tags
+ A series of tags/keywords for the piece, you can filter news items by tags.
diff --git a/content/support/journal-management/similarity-check.md b/content/support/journal-management/similarity-check.md
index 93f0b360..157eb343 100644
--- a/content/support/journal-management/similarity-check.md
+++ b/content/support/journal-management/similarity-check.md
@@ -10,14 +10,14 @@ Janeway supports Crosscheck (also called Similarity Check), which is provided by
The settings are:
-- Enable
- - Enables display for Crosscheck buttons
+- Enable
+ Enables display for Crosscheck buttons
-- Username
- - Your iThenticate service username
+- Username
+ Your iThenticate service username
-- Password
- - Your iThenticate service password
+- Password
+ Your iThenticate service password
More info on Crosscheck/Similarity Check:
diff --git a/content/support/plugins/adverts.md b/content/support/plugins/adverts.md
index 7194ff15..4c5c6058 100644
--- a/content/support/plugins/adverts.md
+++ b/content/support/plugins/adverts.md
@@ -4,7 +4,7 @@ title: Adverts on Janeway
It is possible to show basic adverts on Janeway, this can be (done next to articles (left and right margin)).
-This plugin is not currently active and requires further development. If you are a hosted client and wish to show basic adverts on Janeway, please contact Support.
+This plugin is not currently active and requires further development. If you are a hosted client and wish to show basic adverts on Janeway, contact Support.
Recommended image dimensions :
diff --git a/content/support/plugins/books.md b/content/support/plugins/books.md
index 4a3b3642..a294e492 100644
--- a/content/support/plugins/books.md
+++ b/content/support/plugins/books.md
@@ -335,11 +335,7 @@ These headers are:
Books import headers
> [!Warning]
-> Due to a bug, UTF-8 does not seem to be properly recognised when
-> specific browser-editor combinations are used. We are investigating
-> this. If the file is not properly read upon upload, you may also wish to
-> try a regular .csv file (not UTF-8 encoded). If you still encounter an
-> error, please contact Support.
+> Due to a bug, UTF-8 does not seem to be properly recognised when specific browser-editor combinations are used. We are investigating this. If the file is not properly read upon upload, you may also wish to try a regular .csv file (not UTF-8 encoded). If you still encounter an error, contact Support.
Once the import file has successfully been uploaded, the imported books
will show on the main dashboard. You can now click on these to upload
diff --git a/content/support/plugins/pandoc-placeholder.md b/content/support/plugins/pandoc-placeholder.md
index 9510ce2a..adb1959f 100644
--- a/content/support/plugins/pandoc-placeholder.md
+++ b/content/support/plugins/pandoc-placeholder.md
@@ -4,6 +4,6 @@ title: Pandoc conversion
This Janeway plugin provides a button for typesetters to automatically generate HTML files from user article submissions in DOCX or RTF. These files are first converted to markdown, then to HTML, and then registered as galleys of the original article.
-You must have pandoc installed on your server to use this plugin. Please see pandoc's installation documentation **[here](https://pandoc.org/installing.html)**.
+You must have pandoc installed on your server to use this plugin. See pandoc's installation documentation **[here](https://pandoc.org/installing.html)**.
[GitHub Repo](https://github.com/openlibhums/pandoc_plugin)
diff --git a/content/support/press-management/all-users-placeholder.md b/content/support/press-management/all-users-placeholder.md
index 06b071b5..4894c60a 100644
--- a/content/support/press-management/all-users-placeholder.md
+++ b/content/support/press-management/all-users-placeholder.md
@@ -5,7 +5,7 @@ title: Managing users at press level
From the **Press manager** you can manage users across all journals through the **All users** interface.
You can filter users by whether they are active, are staff, their role(s), and their journal(s).
-You can easily see what roles and permissions any given user has across all journals. You can remove or grant additional roles and/or permissions for multiple journals without needing to go into each journal or the admin area. For each user, there is also a link available to view their history, edit their profile or 'control' the user.
+You can see what roles and permissions any given user has across all journals. You can remove or grant additional roles and/or permissions for multiple journals without needing to go into each journal or the admin area. For each user, there is also a link available to view their history, edit their profile or 'control' the user.
> [!NOTE]
> Explain what controlling a user is.
diff --git a/content/support/press-management/footer.md b/content/support/press-management/footer.md
index c761a71b..da4696a2 100644
--- a/content/support/press-management/footer.md
+++ b/content/support/press-management/footer.md
@@ -2,9 +2,9 @@ title: Journal footer
# Journal footer
-As a press manager, you can control some of the elements that appear in the website footer of every journal.
+As a press manager, you can control some of the elements that appear in the footer of every journal website.
-Some journal indexers require a postal address to be displayed on every journal website. You can add this kind of information with **Edit Press Details** \> **Journal footer text**.
+Some journal indexers require a postal address to be displayed on every journal website. You can add a postal address and similar contact information by clicking **Edit press details** and then editing the **Journal footer text** setting.
@@ -12,4 +12,10 @@ Some journal indexers require a postal address to be displayed on every journal
-You can also add custom links to the footer, such as to publisher policies, using the Content Manager at the press level.
+## Footer navigation
+
+You can also create footer navigation that extends to all journals. This feature is currently only supported in path mode (where journals are served from a shared press domain, such as `www.pressdomain.com/journal`), as opposed to domain mode (where each journal has its own domain, such as `www.journal.com`). This can be used for things such as links to publisher policies. To do this, create a navigation item and check the **Is external**, **For footer**, and **Extend to journals** boxes.
+
+
+
+
diff --git a/content/support/press-management/press-doi-manager.md b/content/support/press-management/press-doi-manager.md
index a4e23cbf..0909657d 100644
--- a/content/support/press-management/press-doi-manager.md
+++ b/content/support/press-management/press-doi-manager.md
@@ -2,6 +2,8 @@ title: DOI management - press level
# DOI management - press level
+_Work in progress_
+
## Settings
CrossRef settings can be set at press level (and then overridden at journal level).
diff --git a/content/support/press-management/press-management-placeholder.md b/content/support/press-management/press-management-placeholder.md
index 843cd84d..0b8f16b2 100644
--- a/content/support/press-management/press-management-placeholder.md
+++ b/content/support/press-management/press-management-placeholder.md
@@ -2,12 +2,15 @@ title: Press management
# Press management
+_Coming soon_
+
+
+
Many base press-level settings are available under **Edit Press Details**.
- what are these settings?
- key things to know
-- info / data sits are journal level and what sits at press level
+- info / data sits are journal level and what sits at press level -->
diff --git a/content/support/repository/repo-setup-placeholder.md b/content/support/repository/repo-setup-placeholder.md
deleted file mode 100644
index f686e9d8..00000000
--- a/content/support/repository/repo-setup-placeholder.md
+++ /dev/null
@@ -1,20 +0,0 @@
-title: Setting up a repository with Janeway
-
-# Setting up a repository with Janeway
-
-## About Janeway repositories
-
-Janeway supports hosting repositories for preprints, postprints, field reports, and other publication types within the same press environment as journals.
-
-
-
-## Getting started
-
-The first step is to enable the repository system in the press-level
-settings:
-
-1. Go to the **Press Manager**
-2. Open **Edit Press Details**
-3. Turn on **Enable repository system** and save
-
-
diff --git a/content/support/repository/repositories-index-placeholder.md b/content/support/repository/repositories-index-placeholder.md
index 660da234..13a459e5 100644
--- a/content/support/repository/repositories-index-placeholder.md
+++ b/content/support/repository/repositories-index-placeholder.md
@@ -1,3 +1,33 @@
-title: Repositories on Janeway
+title: Janeway repositories
-# Repositories on Janeway
+# Janeway repositories
+
+Janeway supports hosting repositories for preprints, postprints, field reports, and other publication types within the same press environment as journals. Repository managers can configure and moderate repositories from the Repository Manager.
+
+## For repository managers
+
+### [Setting up a repository](repositories-setup-placeholder.md)
+
+How to enable the repository system in your Janeway press and create a new repository. Covers the Press manager settings required before a repository can be configured.
+
+### [Repository settings](repositories-settings.md)
+
+A guide to the five-step repository setup wizard, used for both configuring a new repository and editing the settings of an existing one. Also covers additional configuration options, including licenses, subjects, submission fields, and review recommendations.
+
+### [Moderator guide](repositories-moderator.md)
+
+How to manage published and unpublished preprints from the Repository Manager. Covers reviewing and accepting submissions, moderating new versions, and handling review comments.
+
+### Linking a repository and journal
+
+_Coming soon_
+
+### Other settings
+
+_Content coming soon._
+
+## For authors
+
+### [Submitting to a Janeway repository](repositories-submission.md)
+
+How to submit a preprint to a Janeway repository, including the three submission entry points available in the system. Also covers how to update an existing submission, manage supplementary files, and track the status of pending changes
diff --git a/content/support/repository/repositories-moderator.md b/content/support/repository/repositories-moderator.md
new file mode 100644
index 00000000..b47a9ea8
--- /dev/null
+++ b/content/support/repository/repositories-moderator.md
@@ -0,0 +1,55 @@
+title: Moderator guide
+
+# Moderator guide
+
+As a moderator you can find (un)published preprints and preprint stats in the Repository manager, accessible from the left navigation menu.
+
+
+
+## Published preprints
+
+Click the title of a preprint to go to the preprint dashboard. Here, you can view the preprint's metadata, (supplementary) files, versions, and the control panel.
+
+### Controls
+
+- Edit metadata
+- Contact the owner
+ Lets you contact the primary author of the preprint by email. You can include attachments and BCC other recipients.
+- Log
+ Opens a log of all emails sent from the system about this preprint.
+- Comments
+ Displays comments made on the published preprint. From here, you can review, publish, and delete them.
+
+- Invited review comments
+ From here, you can invite reviews, see active reviews, and see declined and withdrawn reviews. To send a review invitation, the recipient must first be added as a reviewer — either through **Manage reviewers** on the Repository Manager page, or by clicking **Manage reviewers** on the review invitation screen.
+- Discussion
+ Lets you view and comment on internal discussion threads, and open new ones.
+- Edit published date
+- Un-published this article
+- Send to journal
+ Lets you send the preprint to a journal on the Janeway press. Select the license, section (article type), and the stage to send it to.
+
+## Unpublished preprints
+
+Similar to published preprints, click the title of an unpublished preprint in the Repository Manager to go to the preprint page. On this page, you can review the (supplementary) files and metadata.
+
+If the preprint is suitable after initial review, click **Create a version with this file**. After this, you can invite reviewers and take other actions to process the preprint. To reject the preprint, select **Reject article** in the control panel. An email prompt opens, where you can explain your decision to the authors. When the preprint is ready for publication, click **Accept article** in the control panel and set a publication date.
+
+### Controls
+
+
+
+Similar to published preprints, the control panel displays the preprint's status and primary identifier, and presents various options. These are the same as those for published preprints, except that **Edit published date** and **Unpublish this article** are replaced with **Accept article** and **Reject article**.
+
+## Moderating new versions
+
+On the Repository manager, in the Stats block, click **Versions awaiting moderation**.
+
+
+
+This displays a list of all versions awaiting moderation and their request type.
+Click **View detail** to review the version. Then click **Accept** or **Decline** to record your decision.
+
+
+
+## Handling review comments
diff --git a/content/support/repository/repositories-settings.md b/content/support/repository/repositories-settings.md
new file mode 100644
index 00000000..1ab9d7f3
--- /dev/null
+++ b/content/support/repository/repositories-settings.md
@@ -0,0 +1,54 @@
+title: Repository settings
+
+# Repository settings
+
+Clicking**Repository settings** opens the repository setup wizard, which is used for both configuring a new repository and editing the settings of an existing one.
+
+The wizard has five steps:
+
+1. **Repository details 1**
+ Key repository details, such as the name, custom domain, and the name of the objects in the repository (for example, "article" or "preprint"). Help text is available on the page.
+
+2. **Repository details 2**
+ Provides more detailed repository information, including the repository description and images, and review guidance for users.
+
+3. **Submission details**
+ Text shown to users on the submission page, and settings related to review.
+
+4. **Email templates**
+ Displays the email templates available on the repository. For more
+ information on editing email templates and email template variables,
+ see Email templates.
+
+## Licenses
+
+
+
+This page lets you choose which licenses are made available for preprints in this repository. The available licenses are all of those made available on the Janeway press, which is why you may see duplicates.
+
+## Subjects
+
+
+
+This page lets you set the subjects that preprints can fall into. These can be organised hierarchically, with child subjects; for example, "Biology" and "Marine biology". Subjects are grouped together, with the parent subject listed first.
+
+
+
+You can also select editors who should be notified of submissions made to this subject.
+
+## Additional submission fields
+
+
+
+You can set up additional, custom submission fields for your repository on this page.
+
+## Recommendations
+
+
+
+You can create, edit, and delete review recommendations for your repository using the interface here.
diff --git a/content/support/repository/repositories-setup-placeholder.md b/content/support/repository/repositories-setup-placeholder.md
new file mode 100644
index 00000000..39f9ce67
--- /dev/null
+++ b/content/support/repository/repositories-setup-placeholder.md
@@ -0,0 +1,44 @@
+title: Setting up a repository with Janeway
+
+# Setting up a repository with Janeway
+
+## About Janeway repositories
+
+Janeway supports hosting repositories for preprints, postprints, field reports, and other publication types within the same press environment as journals.
+
+
+
+## Navigating the Janeway repositories
+
+### Repository manager
+
+You can view unpublished preprints, preprint stats and published preprints.
+
+### Preprint stats
+
+- High-level stats overview
+- From here you can navigate to rejected preprints, versions awaiting moderation, orphaned preprints, and the reviewer management page.
+
+## Getting started
+
+The first step is to enable the repository system in the press-level
+settings:
+
+1. Go to the **Press manager**.
+2. Open **Edit press details**.
+3. Tick the **Enable repository system** box and click **Save**.
+4. Return to the **Press manager**.
+5. The **Add a new repository** option appears below the list of journals.
+ Click it.
+ 
+6. This opens the repository set-up wizard. See Repository settings for more information
diff --git a/content/support/review/review-settings.md b/content/support/review/review-settings.md
index 87edbfc4..e027479e 100644
--- a/content/support/review/review-settings.md
+++ b/content/support/review/review-settings.md
@@ -6,37 +6,37 @@ Review settings can be found under **Review** on the manager dashboard.
-Review settings control how peer review operates. The settings found in this section are the following:
+Review settings control how the peer review process operates. The settings found in this section are the following:
-- Review guidelines
- - A set of generic review guidelines that a reviewer should follow.
+- Review guidelines
+ A set of generic review guidelines that a reviewer should follow.
-- Default review visibility
- - Janeway provides three options for the default review visibility: open, single or double anonymous review. If open, authors can see reviewers and vice versa; if single anonymous reviewers can see authors, if double anonymous, neither can see information on the other. The editor must ensure the manuscript files are sufficiently anonymised when using double anonymous review. To configure triple anonymous review, consult the following page.
+- Default review visibility
+ Janeway provides three options for the default review visibility: open, single-anonymous, or double-anonymous. If open is chosen, authors can see reviewers and vice versa. If a single anonymous is chosen, reviewers can see the authors' names. If double anonymous is chosen, neither can see information of the other. The editor must ensure the manuscript files are sufficiently anonymised when using double-anonymous review. To configure triple anonymous review, consult the following page.
-- Default review days
- - This setting configures the default number of days a reviewer is given to complete a review. This number is then used to control reminders. This field is set to 56 days (8 weeks) initially. The due date can be changed when assigning a review.
+- Default review days
+ This setting configures the default number of days a reviewer is given to complete a review. This number is then used to control reminders. This field is set to 56 days (8 weeks) initially. The due date can be changed when assigning a review.
-- One-click access
- - When enabled, a unique access token is added to the reviewer link in the assignment email, allowing the reviewer to view the review without needing to log into the system. After the review is completed, the token is removed to prevent reuse. These tokens are Universally Unique Identifiers (UUID4s), which ensures the link sent to reviewers is unique.
+- One-click access
+ When enabled, a unique access token is added to the reviewer link in the assignment email, allowing the reviewer to view the review without needing to log into the system. After the review is completed, the token is removed to prevent reuse. These tokens are Universally Unique Identifiers (UUID4s), which ensures the link sent to reviewers is unique.
-- Draft decisions
- - If enabled, section editors cannot accept papers after review. Instead, they can make recommendations to editors.
+- Draft decisions
+ If enabled, section editors cannot accept papers after review. Instead, they can make recommendations to editors.
-- Enable open peer review
- - Turns on the open peer review feature.
+- Enable open peer review
+ Turns on the open peer review feature.
-- Default review form
- - This setting controls the default review form displayed when assigning a reviewer.
+- Default review form
+ This setting controls the default review form displayed when assigning a reviewer.
-- Reviewer form download
- - If enabled, reviewers can download a copy of the review form to complete offline.
+- Reviewer form download
+ If enabled, reviewers can download a copy of the review form to complete offline.
-- Enable save review progress
- - If enabled, reviewers can save the progress in a peer-review assignment and return to complete it later. We recommend only using this when working with particularly long review forms.
+- Enable save review progress
+ If enabled, reviewers can save the progress in a peer-review assignment and return to complete it later. We recommend only using this when working with particularly long review forms.
-- Accept article warning
- - This is a block of text displayed to the editor before they accept an article, prompting initial DOI and metadata registration with Crossref if the journal or press is set to use Crossref. You can use the setting to provide a readout of current metadata so the editor can check what will be sent to Crossref.
+- Accept article warning
+ This is a block of text displayed to the editor before they accept an article, prompting initial DOI and metadata registration with Crossref if the journal or press is set to use Crossref. You can use the setting to provide a readout of current metadata so the editor can check what will be sent to Crossref.
-- Enable expanded review details
- - When this setting is enabled, the editor's review dashboard will show all active reviews. Otherwise, it will show a count of completed reviews.
+- Enable expanded review details
+ When this setting is enabled, the editor's review dashboard will show all active reviews. Otherwise, it will show a count of completed reviews.
diff --git a/content/support/review/sharing-review.md b/content/support/review/sharing-review.md
index 6288ae50..cb108174 100644
--- a/content/support/review/sharing-review.md
+++ b/content/support/review/sharing-review.md
@@ -8,30 +8,30 @@ Completed peer reviews can be shared with authors and between reviewers, both wi
Janeway has various controls for how review data is shared with authors. All of these are off by default. These settings are found on the **Review settings** page under the **Author review display** header. These settings are:
-- Hide review data from authors before release
- - When this setting is enabled, authors will see no information about active peer reviews until the editor makes them available. Otherwise, they can see whether there are reviews in progress and their due dates.
+- Hide review data from authors before release
+ When this setting is enabled, authors will see no information about active peer reviews until the editor makes them available. Otherwise, they can see whether there are reviews in progress and their due dates.
-- Enable peer review data on the author page
- - When this setting is enabled, the dates for when this review was requested, when it was due and when it was completed will be displayed on the review page along with the content of the peer review. As with the review contents, this information will only appear once the review has been completed and the editor makes it available.
+- Enable peer review data on the author page
+ When this setting is enabled, the dates for when this review was requested, when it was due and when it was completed will be displayed on the review page along with the content of the peer review. As with the review contents, this information will only appear once the review has been completed and the editor makes it available.
-- Enable peer review data on review pages
- - When this setting is enabled, authors will have access to more information on the review page than just the content of the peer reviews (date the review was requested, date it was due and date it was completed). The data will be displayed on the review page, which is only available after review and once the editor makes it available.
+- Enable peer review data on review pages
+ When this setting is enabled, authors will have access to more information on the review page than just the content of the peer reviews, including the date the review was requested, the date it was due and date it was completed. The data will be displayed on the review page, which is only available after review and once the editor makes it available.
## Sharing reviews between reviewers
Editors have two options to share reviews with other peer reviewers. On the **Review settings** page, under the **Sharing peer reviews** header, there are four settings which control how editors can share peer reviews.
-- Enable share reviews decision
- - This setting needs to be turned on to enable the sharing of reviews between reviewers. It adds the option to share reviews to the decision helper.
+- Enable share reviews decision
+ This setting needs to be turned on to enable the sharing of reviews between reviewers. It adds the option to share reviews to the decision helper.
-- Display completed reviews in the review interface
- - This setting enables the sharing of reviews between rounds, giving reviewers access to completed reviews from previous rounds.
+- Display completed reviews in the review interface
+ This setting enables the sharing of reviews between rounds, giving reviewers access to completed reviews from previous rounds.
-- Display completed reviews in the review interface text
- - This text is displayed to reviewers when **Display completed reviews in the review interface** is enabled. It can be used to explain to reviewers why they have access to the reviews and what they have access to.
+- Display completed reviews in the review interface text
+ This text is displayed to reviewers when **Display completed reviews in the review interface** is enabled. It can be used to explain to reviewers why they have access to the reviews and what they have access to.
-- Automatically share author response letters
- - When this setting is enabled, author response letters (provided when doing revisions) will also be made available to reviewers as a part of sharing peer reviews.
+- Automatically share author response letters
+ When this setting is enabled, author response letters (provided when doing revisions) will also be made available to reviewers as a part of sharing peer reviews.
### Sharing reviews through the decision helper
diff --git a/content/support/review/triple-anonymous-peer-review.md b/content/support/review/triple-anonymous-peer-review.md
index c8d91c14..e1c8a593 100644
--- a/content/support/review/triple-anonymous-peer-review.md
+++ b/content/support/review/triple-anonymous-peer-review.md
@@ -2,23 +2,23 @@ Title: Triple anonymous peer review
# Triple anonymous peer review
-In addition to open, single and double anonymous review, Janeway provides the option to use triple anonymous peer review. When this is enabled, authors, reviewers, and editors are all anonymised until the review stage is complete. This review option is, however, slightly more complex than other forms of review.
+In addition to open, single and double anonymous review, Janeway provides the option to use triple anonymous peer review. When this is enabled, authors, reviewers, and editors are all anonymised until the review stage is complete. This review process is slightly more complex than other forms of anonymous review.
-Using triple anonymous review requires at least one member of the journal team to have non-anonymised access to screen articles at the submission stage. This editor will also need to act as a journal manager. The editors who require anonymised access to the submission need to be given the section editor role. These editors will not have full journal management permission, as this would inherently provide access to author data.
+Using triple anonymous review requires at least one member of the journal team to have non-anonymised access to screen articles at the submission stage. This editor will also need to act as a journal manager. The editors who require anonymised access to the submission need to be given the section editor role. These editors will not have full journal management permissions, as this would provide access to author data.
## Key settings for triple anonymous peer review
-Two settings must be configured for triple anonymous peer review to work: the personally identifiable information filter and the reply-to address.
+Two settings must be configured for triple anonymous peer review to work: the personally identifiable information filter and the reply-to address. These settings are accessible through the **All settings** page.
-- Section editor personally identifiable information filter (se_pii_filter)
- - Turning on this setting means that all relevant author data will be anonymised for section editors when they are accessing Janeway. This enables them to access the review stage without encountering the author’s personal details.
+- Section editor personally identifiable information filter (se_pii_filter)
+ Turning on this setting means that all relevant author data will be anonymised for section editors when they are accessing Janeway. This enables them to access the review stage without encountering the author’s personal details.
-
+
-- Reply-to address (replyto_address)
- - In order to make triple anonymous review possible, author email addresses need to be hidden. Janeway masks these email addresses with your journal’s reply-to address, which you will need to fill in here.
-
-
+- Reply-to address (replyto_address)
+ In order to make triple anonymous review possible, author email addresses need to be hidden. Janeway masks these email addresses with your journal’s reply-to address, which you will need to fill in here.
+ 
+ 
> [!NOTE]
> Be sure to check that this is correctly formatted as a valid email address, as an incorrect one will mean author email addresses will be displayed and the review will no longer be anonymous.
@@ -39,12 +39,12 @@ Janeway applies anonymisation to the following areas:
- Dashboards – this is applied not only on the main dashboard, but also on the kanban view and active submissions section.
-- Unassigned.
+- Unassigned.
- Review – the **Document manager** section will be disabled for section editors so that they cannot view any author details which might be stored there.
- View metadata – section editors can view an anonymised version of the metadata, but are blocked from editing it to ensure that they have no access to author information.
-- Article log.
+- Article log.
- Email templates – this allows section editors to send decision letters (e.g. revision requests, acceptances or rejections) without seeing author details.
diff --git a/content/support/submission/article-licence-manager.md b/content/support/submission/article-licence-manager.md
index c14c3e53..cf9aa64b 100644
--- a/content/support/submission/article-licence-manager.md
+++ b/content/support/submission/article-licence-manager.md
@@ -2,7 +2,7 @@ title: Licence manager
# Licence manager
-
+
The licence manager allows you to define what licenses are available for submissions to your journal. By default, Janeway provides all CC 4.0 licences and an All Rights Reserved licence. You can edit the list to fit your journal's needs and licence requirements.
diff --git a/content/support/submission/submission-index-placeholder.md b/content/support/submission/submission-index-placeholder.md
deleted file mode 100644
index f70155ec..00000000
--- a/content/support/submission/submission-index-placeholder.md
+++ /dev/null
@@ -1,27 +0,0 @@
-title: Managing submissions on Janeway
-
-# Managing submissions on Janeway
-
-There are multiple aspects to managing submissions on Janeway. The two key parts are the submission information page and the submission process. The submission page displays information for potential authors on the journal website. The submission process is where authors submit their manuscript and provide information about the submission. Certain fields, such as the copyright notice, publication fees and submission checklist, appear on both (by default). The textboxes for these are crosslinked; this ensures the information provided to authors regarding submission remains consistent regardless of where it is presented to them.
-
-
-
-## Submission page items
-
-This configures the text on the submission page, visible at `[yourjournalwebsite]/submissions`.
-
-## Submission settings
-
-This configures the submission process itself and how it functions. From here, you can also disable submissions.
-
-## Submission fields configurator
-
-This configures the submission fields used during the submission process. Any unchecked fields will not be presented during the submission process. If you do not enable the license, language and section (article type) fields, you must set a default value for these. This will set these fields to the default provided in the article metadata. If no default is provided and the field is disabled, the information will not be present in the article metadata.
-
-## Additional submission fields
-
-If you require any additional submission fields as part of the submission process, you can set them up through this page.
-
-## Other settings
-
-Other relevant settings you may wish to configure related to submissions are the license manager , which configures the licenses available for your journal, and sections , which set the article types available for the journal and submission.
diff --git a/content/support/submission/submission-index.md b/content/support/submission/submission-index.md
new file mode 100644
index 00000000..d646f921
--- /dev/null
+++ b/content/support/submission/submission-index.md
@@ -0,0 +1,21 @@
+title: Managing submissions on Janeway
+
+# Managing submissions on Janeway
+
+There are multiple aspects to managing submissions on Janeway. The two key parts are the submission information page and the submission process. The submission page displays information for potential authors on the journal website. The submission process is where authors submit their manuscript and provide information about the submission. Certain fields, such as the copyright notice, publication fees and submission checklist, appear by default on both. The textboxes for these fields are crosslinked; this ensures the information provided to authors regarding submission remains consistent regardless of where it is presented.
+
+
+
+- The submission page items
+ This configures the text on the submission page, visible at `[yourjournalwebsite]/submissions`.
+
+- Submission settings
+ This configures the submission process itself and how it functions. From here, you can also disable submissions.
+
+- Submission fields configurator
+ This configures the submission fields used during the submission process. Any unchecked fields will not be presented during the submission process. If you do not enable the license, language and section (article type) fields, you must set a default value for these. This will set these fields to the default provided in the article metadata. If no default is provided and the field is disabled, the information will not be present in the article metadata.
+
+- Additional submission fields
+ If you require any additional submission fields as part of the submission process, you can set them up through this page.
+
+Other relevant settings you may configure related to submissions are the **License manager** , which configures the licenses available for your journal, and **Sections** , which sets the article types available for the journal and submissions.
diff --git a/content/support/submission/submission-notifications.md b/content/support/submission/submission-notifications.md
index 47030046..678d0eac 100644
--- a/content/support/submission/submission-notifications.md
+++ b/content/support/submission/submission-notifications.md
@@ -2,7 +2,7 @@ title: Submission notifications
# Submission notifications
-Janeway allows editors and section editors to be notified when authors create submissions. It is possible to configure this by submission section (e.g. notifying book review editors only for submissions in the book review section) or by individual editors. If no editors are selected to receive submission notifications, all editors will receive notifications. This excludes section editors, they will always need to be manually assigned to relevant sections or will receive no submission notifications.
+Janeway allows editors and section editors to be notified when authors create submissions. It is possible to configure this by submission section (e.g. notifying book review editors only for submissions in the book review section) or by individual editors. If no editors are selected to receive submission notifications, all editors will receive notifications. This excludes section editors, as they will will receive no submission notifications if not manually assigned to relevant sections.
diff --git a/content/support/submission/submission-settings.md b/content/support/submission/submission-settings.md
index e7472847..7a97a859 100644
--- a/content/support/submission/submission-settings.md
+++ b/content/support/submission/submission-settings.md
@@ -3,7 +3,8 @@ title: Submission settings
# Submission settings
The submission settings are accessed through the manager dashboard under **Submission** and clicking **Submission settings**. From here, you can configure the submission process, text blocks which overlap with the submission page and submission notifications.
-
+
+
**Submission settings** provides access to five blocks of settings: