I think the decision you are trying to make is wether the admin overheads of a CMS system and learning new skills (CMS APIs.. Etc) is worth it for 3-4 pages.
It depends largely on the level of the technical knowledge (or willingness to learn) of the network administrators. Considering that they want to be able to edit the pages, they are likely to have some level of technical knowledge. CMSs are usually used for non-technical users to be able to edit content. They are very efficient in managing large amounts of content too.
If you are not going to use a CMS there are a number of considerations you need to keep in mind:
A. Where to store the content:
This can be in a repository or a database (or combination of both).
The network administrators can checking in their changes just as developers would do into the repository or use a database client to update the database (or write scripts to update the database).
Or you can build your own user friendly client (A couple of web pages) to admin the content.
If you are using a repository, use a built script to move the content to an apache server. For content in a database, write your own code to pull the content from the database onto the webpages.
C. Authentication and Authorisation (Who can edit what)
If you are using a repository or a database client you can use the user management they provide for this. If you are building your own client then you'll need to build this yourself.
If its not a requirement for the changes to take effect directly on the live site, Ideally you'll want the network administrators to be able to view and test their changes in a staging environment before going on the live site.
You can use your existing dev/test/live environments to manage the release process.
I have seen several implementations of similar systems not all were using a CMS.
A CMS system will take care of of all of the above considerations for you, however you need to decide what's best for your requirements and environment.
On 11 Jan 2013, at 07:07, Richard Nduka <[address removed]> wrote:
We have a requirement currently in our hosted web based procurement platform (Java/Spring MVC) to enable organisation administrators manage the content of about 3 or 4 static pages and specify the content they want their users to see (text, video, images, etc). Typically this would have been easily achieved with a CMS (with our application build within the CMS) but ours is a mature product. We are looking at a possible solution whereby a CMS hosts the content and we can get the content via an API for rendering within our application but not quite sure yet if this is workable. Have any of you ever encountered a similar problem? How did you solve it? Is a CMS indeed neccessary at all for this 4 pages or is there some other framework/solution that can be used?
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
This message was sent by Richard Nduka ([address removed]) from LJC - London Java Community.
To learn more about Richard Nduka, visit his/her member profile
Set my mailing list to email me As they are sent | In one daily email | Don't send me mailing list messages
Meetup, POB 4668 #37895 NY NY USA 10163 | [address removed]