Build Service

OJS Theme Design Services

OJS theme design builds a custom visual theme for Open Journal Systems using child-theme architecture, so a journal gets a distinct, brand-aligned appearance without editing OJS core files directly — keeping the theme upgrade-safe across future OJS releases.

OJS 3.5.0-5 LTS OJS 3.4.0-10 OJS 3.3.0-22 LTS Verified 2026-07-23

Who This Is For

  • Journals running OJS's unstyled or lightly modified default theme
  • Publishers who need a theme matched to institutional or society branding
  • Journals whose current theme breaks or looks wrong after an OJS update
  • Multi-journal publishers who need visual consistency across titles with per-journal branding

Common Problems This Solves

  • A theme that looks generic or clearly unfinished to readers and prospective authors
  • A previous custom theme that broke after an OJS core update because it edited core files directly
  • Poor color contrast or inaccessible layout in the current theme
  • A theme that isn't responsive on mobile devices

What's Included

Child-theme built on OJS's theming API, not core file edits
Responsive, mobile-first layout
WCAG 2.2 AA color contrast and semantic heading structure
Homepage, article, issue, and search-result template styling
Cross-browser testing (current major browsers)
Theme source files and basic customization documentation

How the Process Works

Brand & requirements review

We gather your brand assets (or help establish a simple visual identity) and any layout requirements.

Design direction

A visual direction — color, typography, layout — is agreed before build begins.

Theme build

The theme is built as a proper OJS child theme on a staging copy of your installation.

Review across devices

You review the theme across desktop and mobile before anything goes live.

Deployment

The theme is deployed to production and verified against your live content.

Access & Requirements

  • Admin access to the OJS installation (or a staging copy)
  • Brand assets: logo, color palette, fonts, if an identity already exists
  • A list of any journal-specific page types that need custom styling

Realistic Benefits

  • A theme that reads as a credible, established journal rather than a default install
  • Reduced risk of the theme breaking on the next OJS update
  • Accessible, readable presentation for both authors and readers

Limitations & Exclusions

  • This service covers the theme layer, not site structure/content pages (see Journal Website Development for the full build)
  • Complex custom interactive components may require plugin development in addition to theming
  • We don't design a new brand identity from scratch as part of this service — that's a separate design engagement

Documented, Not Improvised

Every engagement follows a written scope, a staging environment before production changes, and a validation checklist before anything is marked complete. Project write-ups are published as case studies once a client approves sharing them.

View case studies

Pricing for this service

Priced by theme complexity — number of custom templates, degree of brand customization, and whether a new visual identity needs to be established.

View Pricing Guidance

Frequently Asked Questions

Built correctly as a child theme against OJS's theming API, it should survive routine updates. Major version upgrades (e.g. 3.3 to 3.5) can still require a compatibility review, which we scope as part of our OJS Upgrade service if needed.

Yes, provided you can share the brand guidelines and assets (logo, color codes, fonts). We'll flag anything in the guidelines that would conflict with accessibility requirements.

Yes — you receive full source files and basic documentation, not a locked black-box theme.

Sometimes. If the existing theme was built as core-file edits rather than a proper child theme, rebuilding it correctly is often more reliable than patching it — we'll assess and tell you honestly which makes more sense.

It can be, if requested during scoping. It's not included by default since most academic journal readers scan long-form content, which reads better in a light theme.

Written by the CyberDairy OJS Engineering Team

Technically reviewed by: Senior OJS Developer

Last updated 2026-07-23

Build Service

Ready to talk about OJS Theme Design?

Tell us about your journal and current setup — we'll respond with a scoped recommendation.

Contact Us Request a Quote