At Internet Scientific Publications, we have since day one marked up submitted manuscripts using an in-house developed Microsoft Word macro. After 14 years, we feel that this approach is not ideal for two reasons: 1) most errors that exist in the finished XML are introduced during the data-entry / markup stage, and 2) markup represents a significant time expense for our staff that could be better spent elsewhere. Since we only charge at the point an article is accepted for publication, there is a time investment marking up manuscripts that may never be monetarily recouped. Consequently, we have explored the option of allowing authors to mark up their own documents from our submission frontend website. There are draw-backs to this approach, namely the complexity and completeness of JATS and the huge learning curve a non-technical author would encounter, but we have in-turn concluded that a majority of the JATS definition does not need to be made available to an author in our frontend application. If an article requires more specific markup that we do not support in the application, we can always fallback to publisher side markup using our tried and tested Word macro. Quality control occurs later in the pipeline during copy-editing regardless of which markup pathway is followed.To facilitate this, we have created a self-contained Symfony2 bundle that supports manuscript markup utilizing a subset of the JATS Journal Publishing 3.0 tag suite. Much of the front and back matter is captured using simple form inputs and is validated using regular expressions developed using common input patterns. For the body, an HTML5 DOM based WYSIWYG editor is used. Although the generated markup is HTML5, by using a subset of JATS, we can unambiguously map between the two markup languages. We speculate that Amazon Mechanical Turk could be used to simplify certain article markup tasks like, for example, endnotes, where it would be off-putting for the author to tokenize the citation string. While the distribution model of a final product has not been determined, it will most likely be made available in a dual-licensed manner depending on the commerciality of the customer.