What PDF-first usually gets wrong
In many traditional workflows, the PDF becomes the center of editorial production too early. That makes it hard to maintain structured metadata, reuse content in web formats or correct the article efficiently across different outputs.
Why this creates friction
- Corrections happen in the visual output instead of the structured source.
- Metadata tends to become secondary or inconsistent.
- HTML publication requires rebuilding or reinterpreting content later.
- Issue closure becomes vulnerable to late-stage layout dependency.
What changes with XML JATS
XML JATS puts the article structure first. Once the core content is marked and validated, derivative outputs such as HTML5, web PDF and print-ready PDF can be generated from the same reliable base.
Strategic shift
When structure comes first, every output becomes easier to manage
The value of XML JATS is not that it removes PDF. It is that PDF becomes one of several controlled outputs, instead of the place where editorial logic gets trapped.
Signs your journal is still suffering from PDF-first logic
- Web and PDF versions do not stay aligned.
- Metadata needs repeated manual intervention.
- Platform publication feels slower than it should.
- Each issue closure depends on heroic last-minute corrections.
What a healthier sequence looks like
- Normalize the manuscript.
- Build and validate XML JATS.
- Generate HTML5, web PDF and print PDF as derivatives.
- Deliver publication packages for OJS or the target platform.
Conclusion
Moving from PDF-first to XML JATS is not about abandoning design quality. It is about putting structure where it belongs so that design, discoverability and publication can all work from a stronger editorial foundation.