php2press

CMS? DTP? Or both?

The php2press project aims to create a web-based system by which one can create content only once, then distribute it in any number of ways. The project itself will focus on the php2press core and a basic set of modules. The modules will do the actual work, interacting with each other and the core to generate and manipulate a php2press deployment site. Following is the list of the basic modules this project will aim to create.

The php2press core will act as a mediator between the various modules, coordinating the processing and output of php2press site pages. The core will provide a programmatic interface through which the various modules can access and manipulate the current page - both content and layout - from initial creation to final output. The current page will be stored in the core itself until the request for that page has been processed.

The basic principle of php2press is that you shouldn't have to create your content four different times for three different output formats. Why redo the work of writing an article in a desktop publishing (DTP) application when you've already written it for the web? Why rewrite a website line by line for viewing on cell phones? Why not just create the content once, and have it automatically propagate through to all of your output formats? php2press promises to do a lot for those who would like to publish their work to multiple resources at once.


If you check our SourceForge page, you'll see that this project was started in 2004. If you check your calendar (or a nearby clock), you'll see that it is currently 2017. Yeah, it's been a few years.

php2press has been going through our minds for some time now, but other commitments have kept most of us from making any significant progress. This is not to say that no progress has been made - to the contrary, several pages of code have been churned out since the project's inception 13ish years ago. Unfortunately, we may end up starting over from scratch.

The biggest challenge we've faced, after time itself, has been knowing what it is we're trying to accomplish. Our end goal was never written down anyplace where it could be referred to later. No summary of intended features was ever generated. Most of the development has been seat-of-the-pants output, generated as things came to mind - and this doesn't exactly help with creating a well-oiled, fully-integrated machine such as a CMS. So regardless of whether we decide to keep the existing code or not, we are going to sit down in the near future and discuss what exactly it is we're looking to do here, and from there we can figure out how.

How long of a wait can be expected? Your guess is as good as ours at this point. Hopefully our recent change in leadership will help move things along a bit, but we make no guarantees. If you wish to give things a bit of a nudge and make sure we're still working on the project, feel free to drop by our IRC channel on FreeNode. You can also shoot me an email using the link at the bottom of this page.

Until next time,

- Richard Pisca

Key Developers

Developer's Name Developer's Role(s)
Richard Pisca Project Leader / Developer / Website Maintenance
Aaron Mathis Project Founder / Developer / Standards Compliance
Eugene Miller Project Admin / Developer / Tester