Repository navigation
[Content editor] Review static page content editor for ORE #239
Description
Related to:
The client will soon be editing the static content on the ORE VM. The editor tools available are inconsistent across the pages. This ticket is to define what tools for content structure and styling will be available.
Example 1:
Settings > Website > Setup > Navigation > "Reviewer benefits"
Reader UI: About > Reviewer benefits
Example 2:
Settings > Workflow > Submission > Author Guidelines
Reader UI: For Author > Author Guidelines
To be discussed in the next dev leads mtg.
Metadata
Metadata
Assignees
Labels
No labels
Activity
asmecher commentedon Jun 11, 2026
This is a known issue and will be resolved via eventual refactor of old forms. The navigation management tools use old server-side forms, and the workflow settings use a newer VueJS-based implementation. These both use TinyMCE for rich text editing, but are configured differently in different places. Is there a particular difference here that needs addressing, or is it just flagging an inconsistency?
mreiko commentedon Jun 11, 2026
@asmecher Maybe less important than consistency between the two is that you can't seem to create your own headers and sub-heads and the I think the styles are off-brand
asmecher commentedon Jun 11, 2026
@mreiko By "the styles are off-brand", do you mean the output generated by the TinyMCE fields, or something else?
@jardakotesovec At a glance I think headers would be useful to include in the VueJS-based TinyMCE fields, at least in setup, but I'm not sure how differentiated our set of controls is (or can be, easily). Do you know off the top of your head?
mreiko commentedon Jun 11, 2026
Yes, for example, the headers on this page edited via the navigation tool don't have CERN styles: http://ore.testing.publicknowledgeproject.org/index.php/ore/incentives @asmecher
asmecher commentedon Jun 11, 2026
@mreiko Ah, OK -- that's a copy/paste issue, not strictly speaking about TinyMCE. TinyMCE tries to preserve formatting when content is pasted in, and this will result in a mixture of stripped elements (those that aren't allowed) and incomplete styles (those that were coded in an external .css and still referred to from the pasted content). Long story short, copy/paste doesn't work on the web in a way that preserves formatting. The solution is to either paste that content in stripping styles (control+shift+V) and then re-style it using TinyMCE, or to edit the source and remove any inappropriate styling.
mreiko commentedon Jun 17, 2026
Jarda will investigate what basic content structuring tools need to be included
blesildaramirez commentedon Jun 22, 2026
Created an issue in pkp-lib: pkp/pkp-lib#12937
mreiko commentedon Jul 28, 2026
Hi @agata-morka the editor tools have been updated and are now consistent anywhere static content can be edited.
Since this ticket requires an Author Guidelines link, maybe this is a good place to start.
Please note that the OJS editor supports basic functionality via the editor tools. To support sophisticated styles, you'll need to use HTML.