Databases
StackOverflow2013
Postsdbo
POCMS which is not a portal system
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCMS which is not a portal system
    text
    copied!<p>this is a repost of a <a href="https://stackoverflow.com/questions/107494/cms-without-front-end">question not correctly answered</a> -- sorry about that.</p> <p>We are looking for a reasonably priced <a href="http://en.wikipedia.org/wiki/Content_management_system" rel="nofollow noreferrer">CMS</a> , with source code, in which we can ditch the portal system. There are notorious examples of something similar which are way too expensive: <a href="http://www.eidosmedia.com/Feature_Update/MethodePortalServer.html" rel="nofollow noreferrer">Methode</a>, <a href="http://www.broadvision.com" rel="nofollow noreferrer">Broadvision</a>, <a href="http://www.microsoft.com/cmserver/" rel="nofollow noreferrer">Microsoft CMS</a>.</p> <p>There are a lot of systems in which the portal part is too tightly coupled with the backend to do that. Basically <a href="http://www.joomla.org" rel="nofollow noreferrer">Joomla</a>, <a href="http://drupal.org" rel="nofollow noreferrer">Drupal</a>, <a href="http://phpnuke.org" rel="nofollow noreferrer">phpNuke</a>, <a href="http://www.dotnetnuke.com" rel="nofollow noreferrer">dotNetNuke</a>, <a href="http://umbraco.org" rel="nofollow noreferrer">Umbraco</a> are all examples of what we don't want.</p> <p>We want a back office system that can store heterogeneous information with versioning, workflow and so on. This information should be statically publishable (to files, xml, etc...). Also we would like to have a set of APIs for accessing the information in a custom front-end.</p> <p>We would use this system in a large number of websites. Platform is not important as we develop sites on multiple stacks.</p> <p>Thank you in advance</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload