Security & compliance
- HTTPS and force_ssl
- Files directory outside web root
- Role-based access controls
What we deliver
- Server installation: OJS 3.x on Linux with PHP 8.1+, MySQL/MariaDB, HTTPS, and hardened file permissions.
- Editorial workflow design: Single/double-blind review, section editors, copyediting stages, and decision paths.
- Submission & metadata forms: ORCID, affiliations, ethics statements, funding, and keyword fields aligned with indexing requirements.
- Policy pages & static content: About, aims & scope, peer review policy, ethics, OA policy, and author guidelines.
- Theme & branding: Professional journal theme, mobile-responsive, with license and citation metadata on article pages.
- Email & deliverability: SMTP configuration (not PHP mail()) so reviewer invitations and decisions actually arrive.
Implementation process
- 01
Discovery & workflow mapping
We document your review model, sections, roles, and indexing targets before touching the server.
- 02
Install & configure OJS
Clean OJS install, context settings, ISSN, publisher data, locales, and plugin baseline.
- 03
Content & policy setup
Editorial board pages, submission checklist, copyright/license prompts, and author guidelines.
- 04
Training & handover
Editor and admin walkthrough, documentation, and 30-day post-launch support window.
Configuration modules
Indexing readiness
- DOAJ metadata fields
- Google Scholar clean URLs
- Abstract & keyword structure
Editorial roles
- Editor-in-chief, section editors
- Reviewers and authors
- Custom permission matrix
Communications
- SMTP with Amazon SES / Gmail
- Email template customization
- DKIM/SPF guidance
FAQ
Do you only install, or also host?
Both. We can install on your server or pair setup with our managed hosting service.
Which OJS version do you support?
OJS 3.3 and 3.4 on PHP 8.1+. We recommend 3.4 for new journals.
Can you migrate from OJS 2 or another CMS?
Yes — see our migration service for data mapping and cutover planning.