At its core <pagebreak /> is a cloud-based application which waits for input using CSS for formatting from an outside app, web or desktop based, and returns output in the form of a PDF with its associated PPML (Personalized Print Markup Language) document ready for print.

In addition to this core functionality, the <pagebreak /> API goes far beyond creating PDFs for print, with options for handling the entire publishing process from users management, to permissions, workflow and more.

While there are other applications available that offer similar functionality, <pagebreak /> is unique in some key features:

- CSS used for templates;

Cascading style sheets are a standard that goes well beyond desktop publishing. Creating these templates requires no more skills then the ability to use a simple text-editor.

- True multi-user;

Several people can work on the same publication at the same time, even on page lay-out

- Honoring the publishing process;

Publishing is a dynamic process. Articles can be smaller or bigger then originally envisioned. The number of pages can change during the process as needed. Without being forced to change templates.

- Cross-media;

Content can also be distributed as a "flipbook", RSS feed or used as CMS for websites.

The flexibility offered by <pagebreak /> means that it’s uses are limited only by imagination. Businesscards, magazines, photobooks or even packaging could be created by using the possibilities of <pagebreak />.

The simplest way to get a quick understanding of what <pagebreak /> is capable of is to take a look at an existing instance of its use, the online publishing portal SMIC.

SMIC is a full-service publishing portal where customers can collaborate, write, edit, design and publish – all via a web-based application.

The entire SMIC application suite is built in HTML & JavaScript and all the functionality is called via the <pagebreak /> API. SMIC shows off many of the capabilities of the <pagebreak /> backend, and all the code used to build SMIC is provided to users of <pagebreak /> to help get you started with your first apps.

While the SMIC use case is a strong one, and one which has proven very successful for <pagebreak /> creators Jonge Helden in The Netherlands, the possibilities of the platform are only limited by imagination. Just a few use cases where <pagebreak /> could prove valuable are:

Brochures / Catalogs

Already a well-proven use case, the sample code provided will give you the ability to let your users produce their own customized brochures and catalogues.

Corporate image

Because of it ability to repurpose incoming content, corporate image materials could prove a particularly strong use case. Users could provide the system with employee details and easily produce any needed collateral, from business cards, to envelopes, to letterhead.

Packaging

Packaging hasn’t yet been explored to its full potential, but there is no reason an application couldn’t be written to use the <pagebreak /> engine to produce smallrun, custom packaging for clients. With a few templates in the system, users could easily update, customize, and produce materials as needed.

Photobooks

A straightforward way to take advantage of <pagebreak />'s capabilities would be to produce photobooks. <pagebreak /> automatically scales to any size publication, allowing users to put out a book of almost any size. It addition, it would be possible to write an application as a plug-in for other applications such as iPhoto or Picassa, enabling users to very easily take advantage of the system.

Web

While the print functionality of <pagebreak /> is core to its value, it is also very capable of feeding online channels via RSS or JSON. These online outputs can be used standalone, or in conjunction with any print-based workflow.

And more...

An exciting aspect of <pagebreak /> for us is to see where users take it.

It is also worth noting that any and all work you put into your front end, as well as any data held in <pagebreak /> are your sole property – you retain full intellectual rights on everything you do.

Others

Following companies in some way make use of technology from <pagebreak />:

Publishers

Peel en Maas uitgevers (NL)

Gilsing uitgevers (NL)

Aristo (NL)

Die Zeit (DE)

Country Wide Publications (NZ)

Z-Press (NL)

Starters Pers (NL)

Telstar Uitgevers (NL)

Van den Munckhof BV (NL)

van Helvoort Grafisch bedrijf (NL)

Regiobode (NL)

De Uitkijkpost (NL)

Heno (NL)

Drukkerij van Lieshout (NL)

Delft op Zondag (NL)

De Heraut (NL)

Het Kontakt Edities (NL)

Gouw Uitgevers (NL)

Anzeiger Region Bern (CH)

.CH (CH)

Anonza (DE)

Real estate agents

REMAX (NL)

Witte Woning Makelaars (NL)

Assink ERA Makelaars (NL)

Best Living Makelaars (NL)

Other

Rabobank (NL)

Wageningen University (NL)

University Hospital Utrecht (NL)

Coca Cola Enterprises (NL)

McDonald's (NL)

Euroconcept groep (NL)

Zepvertising (NL)

Top Consultants (B)

Supreme Reclame (NL)

Nijhof RSB (NL)

PEEK Traffic (NL)

Invacare (NL)

Heijberg Academy (NL)

Generali Insurances (NL)

The <pagebreak /> API is the method by which your application will leverage the power of the system. The API is fully documented, and the examples provided (which call the API with HTTP and Javascript) should help you make a quick start in developing your own application.

Your application

There is little limit to how you might choose to write and deploy your application. The <pagebreak /> engine is based on REST services, and is called via HTTP requests. <pagebreak /> will talk back to your application either using XML or JSON.

What’s needed

At a minimum, you will need to have proficiency with HTML and Javascript in order to modify the sample code we will provide. Ideally, you should have access to expertise in the language, or languages, you wish to deploy your application with.

The <pagebreak /> API is relatively straightforward, but to truly leverage its power some coding background is strongly recommended.

<pagebreak /> lives in Amazon’s cloud. The advantages of this are many-fold.

Amazon’s cloud architecture is massive, and world-wide. An application deployed with the <pagebreak /> backend should perform as quickly from New York as it does from London or Sydney. This performance is also enhanced by the scalability offered by the system. If <pagebreak /> experiences unexpected load, virtual servers can be added on the fly.

Another advantage is simply that of uptime. Amazon has a great deal of experience keeping their servers online – if they go down it is a very costly experience. It hardly surprising that they don’t go down often.

In short, <pagebreak /> is deployed on a flexible,scalable, reliable and redundant architecture.

The business case for deploying a solution are quite simple, the costs are very low and the potential rewards quite high.

Cost

Licensing the <pagebreak /> engine requires no upfront cost, and is based on a nominal monthly subscription based on your throughput.

The precise cost will vary depending on your needs, but it would not be unusually for a licensee to see their <pagebreak /> expenditure be less than €750 / month based on a throughput of 100 orders. If you would like a quote for your specific needs, please contact us.

Putting your investment to work

While it is possible to utilize the printing services of Jonge Helden, we have seen the most interest in <pagebreak /> from owners of digital presses. Jonge Helden has set an internal goal of having 16 hours of jobs for their presses delivered via SMIC and <pagebreak /> per day. (current total output of 12000 A4 sheets per hour)

When comparing the cost of <pagebreak /> to the opportunity cost of your expensive equipment sitting idle, we believe that the value proposition of <pagebreak /> becomes evident.