We would like to see some additional features within MODX, specifically around running both a dev and a production system, and moving content between the two. We are willing to pay for the development and to donate the code back to the community.
The high level requirements follow, however, we would like this done quickly, and the work to start asap. Duration and budget - you tell me how long this will take! We’ll pay 1/3 upfront and 2/3 upon successful completion.
There are 2 main areas we are interested in. Firstly, an approvals system, where changes in dev would be routed for approval and secondly, an “automated” push to move changes from dev system to prod system.
We had envisaged that this could be done as per below, but I’m open to suggestions.
1) Modify MODx roles and permissions to support additional content publishing module and new publishing procedures.
2) Existing MODx page management module will be modified to support additional statuses to support new publishing workflow.
• Test – All new and modified content pages will be set to this status until a tester has validated all new and modified pages.
• Approved – This status is used once new or modified content page has been validated by a tester.
3) New MODx module will be created to allow for page replication to other servers (test, stage, public).
• Push to other Servers – Once the content page has been approved admin will have the ability to push content to other servers (testing, staging or public). List of servers will be configured through a module admin interface.
• Default status for new pages will be “Not Published”. Existing pages that have been modified will take on existing status.
Please contact me directly at
[email protected] if you are interested.
