Medical Journal Website Setup

Job ID: 40248996

Budget: $750 – $1,500 AUD

I am launching a new peer-reviewed medical journal and need a complete, production-ready website. The build should mirror the structure of established journals: a clean top-level menu linking to our mission statement, editorial board, ethics and AI policies, author guidelines, and similar reference pages. Those pages can remain largely static, while articles, issues, and user data will be dynamic and searchable.

Article workflow
• Authors must be able to register, upload manuscripts (PDF, DOCX), and receive an automatic email acknowledging receipt.
• On my side, I need an admin panel to assign reviewers, track revisions, and flag papers for publication. A simple, intuitive dashboard is essential.

Access control
Most articles will remain open access, but certain premium sections and downloadable material should sit behind a subscriber login. Please implement role-based access so we can differentiate between editors, reviewers, subscribers, and casual visitors.

Payments
The site has to collect two kinds of fees:
1. Article processing charges for accepted papers.
2. Individual or institutional subscriptions.
Please integrate Credit/Debit Cards, PayPal, and Bank Transfer options and tie successful payment to automatic access activation.

Technology
I have not fixed the CMS; WordPress, Drupal, or Joomla are all acceptable if you can demonstrate reliability, security, and an upgrade path. Whichever you choose, build with standard medical-journal conventions—meaning a mix of static informational pages and a database-driven article repository.

Deliverables
• Fully configured CMS with the pages and workflows above
• Responsive design matching current journal aesthetics (I can supply examples)
• Payment gateway setup and tested for the three methods listed
• Email templates for submission acknowledgement and payment confirmation
• Documentation so my editorial team can manage future issues without coding

Please outline your recommended platform, any plugins or modules you’ll rely on (e.g., OJS integrations, WooCommerce, Drupal Commerce, etc.), and a realistic timeline for initial launch and acceptance testing.