Over in another thread about WYSIWYG editors
https://openacs.org/forums/message-view?message_id=124965 , a discussion about how to get content into OpenACS started. To keep focused I have started a new thread.
OpenACS coding efforts have mainly focused on the community aspects of the software. One area that is important, but not focused on as much is content management. While those who use OpenACS believe community aspects are important, most web sites also need some plain old content.
The content repository package offers some good basic features to handle content, but no user interface. The existing CMS package has many good features hidden beneath a confusing user interface.
Here is what content management features OpenACS supports currently, with a bit of coding effort to expose them from a user interface.
* Addition of content through traditional browser based textarea, simple richtext widget, or file upload.
* Storage of content in the database, or in the filesystem
* Assignment of templates to style content, including the ability to assign different templates to content depending on the context.
* Upload of content through a web browser form including binary formats such as .DOC, .PDF and images.
* CR supports muli-part content items, such that a "page" can consist of several content items, which can be text, images etc.
* Publish of content, combined with templates if applicable, to the filesystem under the www pageroot.
* Probably some other stuff I am not thinking of right now.
There is currently work on fixing up ETP, although it is quite ans effort because it goes off on it's own, instead of using built in features.
There is also another CMS project called BCMS that is available from the contrib directory.
Here are notes on discussion of where to take content management:
https://openacs.org/forums/message-view?message_id=113657