Is your feature request related to a problem? Please describe.
As a preprints repository moderator or admin, I expect to provide explicit instruction to submitting authors about the requirements for new submissions on Step 3: Upload Files of the submission process. Currently preprint repositories may only provide such instruction on Step 1, which is hidden on another page from the submitting author.
Describe the solution you'd like
Add to Step 3 of the template the ability to add custom text in places where the author may upload files, such as the submission file as well as supplemental data (if that feature is built in). It would also be nice to be able to use custom wording in the "Repository requires that all author uploads be PDF files" statement.
Finally, it would be nice to have a link to "Review submission requirements" which opens a popup or modal widow which displays the same requirements text as displayed in Step 1 (submission start text).
Mockup
Additional context
This has some overlap with #3227; let me know if it would be preferable to split the two.
Is your feature request related to a problem? Please describe.
As a preprints repository moderator or admin, I expect to provide explicit instruction to submitting authors about the requirements for new submissions on Step 3: Upload Files of the submission process. Currently preprint repositories may only provide such instruction on Step 1, which is hidden on another page from the submitting author.
Describe the solution you'd like
Add to Step 3 of the template the ability to add custom text in places where the author may upload files, such as the submission file as well as supplemental data (if that feature is built in). It would also be nice to be able to use custom wording in the "Repository requires that all author uploads be PDF files" statement.
Finally, it would be nice to have a link to "Review submission requirements" which opens a popup or modal widow which displays the same requirements text as displayed in Step 1 (submission start text).
Mockup
Additional context
This has some overlap with #3227; let me know if it would be preferable to split the two.