Making JOSS more forkable

[arfon]

Currently there's a bunch of things that are hard-coded into the JOSS codebase that make it hard to repurpose the journal:

• HTML content - e.g. page titles and other HTML content
• Content of review checklists
• Hard-coded editor lists

In addition there are some enhancements we need to make to support JOSE:

• Custom/multiple review templates/checklists
• Submission 'type' field available in submission form for user to select and matching review template

[labarba]

@arfon Do you have any updates to report on the enhancements we need for JOSE?
/cc. @kyleniemeyer @tracykteal

[labarba]

@arfon 👋
I'm actually getting some enquiries by email from folks that are interested in submitting to JOSE. Any updates?

[parrish]

👋 Hi @labarba, I'm currently working on this and am prioritizing this issue as well as openjournals/whedon-api#8

I'm estimating I'll finish this up by the end of next week.

[labarba]

What's the status of this WiP, @parrish ?

[parrish]

Looks like about a week left here. There was a bit more to do here than suspected. I’ll be sure to keep this issue updated.

[labarba]

Looking forward to getting an update of the things still under development. Thanks!

[parrish]

My estimate was a lot closer the second time around! 😄

There is still some work remaining to get multiple submission types tested out. I'll tidy up and link to a PR tomorrow or Wednesday. We're still sorting out how we want to handle staging/demo deploys, but we ought to have something up pretty soon.

[parrish]

PR is at #353

Happy to continue working through issues over there! 😄

[arfon]

This is now complete.